Open Silvrav opened 1 year ago
Hi @Silvrav , to troubleshoot this, we need more info. However, I believe this can happen if the addon is running on a device gaining its IP via DHCP. Are you assigning a static IP to the devices?
Both my xeon server and the HA instance runs on static IP's but the plugs/devices themself runs on HTPC. I can try and provide them with fixed IP reservations through my modem and see if that works.
I'm having this issue as well, despite my devices being on static IP reservations.
After rebooting my router, only a few devices came back online so I restarted HA for only 2 devices to come back. Switched between the various mqtt only, http first then mqtt, http for only get then mqtt only to see the last 2 devices go offline. I'm looking directly at the local Meross MQTT broker and not just the HA integration. All devices continue to function through the Meross app so I'm a bit confused on how that's working if the devices are paired to my local MQTT broker.
UPDATE: Perhaps I wasn't as successful in pairing my devices to the local MQTT broker as originally thought. I disabled it and power cycled the devices and all almost instantly reconnected to the cloud broker. I used the pairer app and the devices showed they were paired with the local broker until they were power cycled. Something made them revert back but without understanding how/what caused this I'm not sure how to move forward with this.
I'm having this issue as well, despite my devices being on static IP reservations.
After rebooting my router, only a few devices came back online so I restarted HA for only 2 devices to come back. Switched between the various mqtt only, http first then mqtt, http for only get then mqtt only to see the last 2 devices go offline. I'm looking directly at the local Meross MQTT broker and not just the HA integration. All devices continue to function through the Meross app so I'm a bit confused on how that's working if the devices are paired to my local MQTT broker.
UPDATE: Perhaps I wasn't as successful in pairing my devices to the local MQTT broker as originally thought. I disabled it and power cycled the devices and all almost instantly reconnected to the cloud broker. I used the pairer app and the devices showed they were paired with the local broker until they were power cycled. Something made them revert back but without understanding how/what caused this I'm not sure how to move forward with this.
Same issue here, on reboot devices fail back to the cloud, going to try blocking meross access for all devices aside from HA to see if I cant stop this from happening in the future, will leave my findings here once done.
Update at the moment when it cant connect to cloud it simply resets it self to defaults and just waits to be setup again. Weird.
On restarting the modem the devices dont automatically reconnect to the broker/wifi. I need to switch off the devices after a modem restart to enable them to reconnect. The problem with this is, I am using devices to monitor energy of the server rack so I cant switch off my entire network everytime.