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?).
Edit #4 Solved....or at least worked around. I will leave this here in case it helps someone else, or there is something that can be fixed in the code if that is where the issue is.
Hi, I am having an issue with adding 2 Shelly units to Hubitat. They are both identical Shelly 1 Gen 4 with the Sensor Addon. I am using 3-4 DS18B20s on each, and the Analog and Digital Inputs. Both are set up identically in the Shelly app and the data shown there follows any state changes of the devices without delay or any issues.
I made virtual devices and i am using the "Shelly Plus 1 & Plus 1 mini" device from Bundle1.zip
The first one (Stall Barn) works just as expected, when the state of the Digital input (Switch 100) changes it shows immediately in that child device, Temperature changes also show promptly in their child devices.
The second one (Hay Barn) will not show the state changes for the Digital input or Temperature probes in the child devices unless I click the Refresh button.
I have deleted the problem device from Hubitat and factory reset it 2 seperate times, but the results are the same,
Below are some logs of what i am seeing
This is the problem unit ( Hay Barn) it gets the status of Inputswitch:100 on its own, but when i activate the switch it comes in as "Setting Inputswitch:null to on"
On the working one (Stall Barn) it also references the "null" switch, but then goes on to show the change to Inputswitch:100
Also at the end of a config the good one starts showing temperature data
the problem one does not
Anyone have any ideas or advice?
Edit: i just received a third set of devices and set it up the same as the others, It acts the same as the bad one, the only difference i see is the Mac address of the working one is cc:ba:97:xx:xx:xx, and the nonworking ones are a0:85:e3:xx:xx:xx.
I had originally set up the good one as a matter device before i understood to make a virtual device, but i removed that before i set up the virtual device so i don't think that is what made it work. and i did try adding the bad one as matter device and then deleting on the first attempt at starting over.
Edit #2: More info
In the actions section of the web interface the working one has a bunch of actions created by Hubitat
The nonworking ones does not
Edit #3: I decided to duplicate all the actions from the working unit to the nonworking one and now it is acting as expected. I'm not sure why the rules did not create on their own.
The only other oddity i saw is an error on all 3 devices at the start of the config, I doubt it is related but putting it here incase someone wants to look at it
This might not be the right thread, but has anyone installed a Shelly Wave PM Mini? It was included in a previous release in 2024 as working with Hubitat, however I am struggling with kwh/energy reporting. Device reports power/watts, shows kwh in the debug logs, but doesn't show kwh/energy in the "states" of the device consistently.
When I refresh the device, it shows kwh/energy but reloading the page it goes away.
Hi @dmitry.rozovik , I installed the bundle back in July 2025, is there an updated version somewhere? I see in some posts there is mention of an update but the zip in the link is dated May 2025
Download the Hubitat app
