I am using a Shelly Plus/Pro xPM driver for the Shelly I4 DC sensor with AddOn module handling temperature sensors. The device firmware was update few days ago to 1.7.x Now the driver generates a lot of error:
Despite this huge number of errors the device seems to be functional.
Do you have an idea what is wrong and could this be fixed?
I'll check it locally. At first glance it looks like missing some child device or missing component id from the device report.
Something similar were reported earlier somewhere on forums. And I made fix for that. So, in a mean time you could try to install the latest bundle (just in case if you happen to have not the latest version)
OK, I reinstalled the entire bundle and the error disapeared.
This Shelly I4 DC Device frecuently reports reconect to a network. The device is only 10ft away from the router and looks like it is functional. Is this a real WiFi connection problem or driver reports this warning for whatever reason?
Hard to say right away. There is a known issue with Shelly<->Netgear Wi-Fi connection (frequent disconnects).
Driver is simply monitoring websocket connection and triggers reconnection if lost. You may try to simply reboot (in case if some previous connection logic somehow remains active and causes contention). If after reboot the behavior remain the same, there is high chance of compatibility issues between router and device.
What also come to my mind is to ask/check about power supply reliability (in case if there could be some voltage drop that might impact device RF module operation).
It still could be some driver reconnection logic issue.
It might be helpfull to check detailed logs.
The device reboot did clear all these messages. No more errors and warnings.
The fix was very simple - update drivers and reboot a device.
Thank you very much.
UPDATE
My report was too soon. Unfortunately after a while connection related info/warnings statrted again:
From the other side Home Assistant (it did picked up this device automatically) is absolutely happy. HA does not report any warnings at all. So, it could be something in a HE driver which triggers this warnings (low threshold or so?).
Download the Hubitat app
