Ran across this thread, realize this a few months old and wanted to pass on something that might help…
- To solve the random disconnects on the Eagle 200, as one of the first to order one on Amazon, two things I would suggest…
-
Make sure you are using the power adapter that came with the unit. In theory this should be irrelevant, however, nothing is simple nowadays. I learned from my prior rainforest equipment and trying to use comparable power source on my EMU-200 (Standalone Smart Energy Zigbee Monitor from Rainforest) lead to the random disconnect behavior. Switching back to their power source solved the problem. This is likely not your issue, but mentioning just in case.
-
A kernel update is what actually solved all my disconnect problems (mostly)… Ask Rainforest support if your unit has the latest Linux Kernel installed. Kernel updates are not NOT reflected in the firmware status on https://rainforestcloud.com/ per RFA support and apparently, and are at present, offered only on a “by request” basis. Stupid, I know. They probably do not want to risk the drama or RMA’s if they brick your unit, but I digress. RFA is allegedly working to fix this. Since the Kernel update I’ve had little issue. Oh, and there is no way to see or verify this either online. There may be a way to poll the unit via API commands, but just getting to messing with that.
On distance/range - For reference, I keep my Eagle 200 for what has to be at least 50 feet away (LoS) from the meter, but that is as the crow flies, through a garage, two bedrooms, a hallway, and an all metal LAN Rack enclosure w/glass. Seeing all the drama with SmartThings connections, which I also experience, it amazes me that I’ve actually had LESS issues with the Eagle 200, a Zigbee SE product and the endpoints are farther away than SmartThings HA products which sit 5 feet from the hub. I digress.