@daniel.winks
First of all, thank you Daniel for this immense contribution to all of us using Shelly devices with Hubitat Elevation.
I just bought a Shelly Plus Uni for the purpose of monitoring the voltage of the 12 volt battery in my driveway gate operator (it's solar charged).
I'm trying to get the Plus Uni working on the bench before I install it outdoors(!).
First I powered up the Plus Uni and used the Shelly app on my phone to configure it for my WiFi network. Now I can access its settings using its web interface from my computer, and after poking around a bit I found where you can set up the analog input reading under Peripherals. I set up the voltage and named it "Gate Battery Voltage". In the web interface I can see that voltage, and it seems to be reading fairly accurately in real time.
I installed your application, created a new device using the "Shelly Plus Uni (Websocket)" driver, and after entering its URL, it generated some child devices, which I can see in the Devices list:
However the Gate Battery Voltage "peripheral" or "input analog" is not showing up.
I did try creating another new device using your driver type "Shelly Input Analog Component", but that device isn't showing any setting where I can enter a URL, and doesn't seem to be related at all to the "Shelly Plus Uni (Websocket)" device.
In the log for the "Shelly Plus Uni (Websocket)" device, I can see that the driver is getting information about the "peripheral" when it communicates with the Uni:
"voltmeter:100": {
"id": 100,
"name": "Gate Battery Voltage",
"range": 0,
"report_thr": 0.10,
"xvoltage": {
"expr": null,
"unit": null
}
},
But it doesn't seem to use that information to generate the analog input type of child device.
I did update the Uni to the latest firmware: 20250730-063243/1.7.0-gbe7545d.
I updated it before I tried to interface it to the Hubitat.
I hope that wasn't a mistake to do that!
Any suggestions?
Any logs I could upload that might show what's going on?
