UPDATE: We may have found an issue and there is a beta firmware that is addressing this. Good news is it’s with the switch, so it is OTA (with the right tools).
In a nutshell: Sometimes when the commands are being sent from the switch to the module via 2.4 GHz, and the module also sends data to the switch, there is a logic confusion which makes a separate command from the switch not send to the module.
We are internally testing this for two more days to make sure the release is stable and we’re talking about it further tonight at 9pm EST during our weekly meeting.
More to come, but this is encouraging!
@kitt001 – to answer your question:
The way it was explained to me is that the fan module will send data to the switch (relay’s to the hub) every hour (which is the default). Also, if you send a, “meter get” command, the switch will also get an energy/power report.
What may be happening with the disconnects is that since energy monitoring has been disabled, less commands are being sent to cause the conflict. Or if your fan is off (no energy reporting) and you turn it on (energy is now reported) and multiple commands are being sent between the switch and canopy, the conflict causes disconnect issues.
Anyway, more to come!