I think your scaling to get to kWh from total is wrong, but it was maybe coincidentally close enough to what the other app told you for the day that it was confusing.
What was your total value at the beginning of the day timestamp? What is the total number now? If you subtract those and divide by 60,000 (instead of 100,000), do the two apps match?
In your example, 237693 (watt-minutes) / 60000 = 3.96 kWh. What was your value at the beginning of the day in that example?
All good. I straightened out the scaling based on your last reply and confirmed it was accurate. Think it was just coincidental that the rabbit hole I ran down before was close.
So I tried to cut some corners in changing a device over to a shelly... But I've come unstuck. Then deleted the device and tried to add one again.
Now getting the error shown below. How do I fix this? It's not as simple as changing the device value in the device page is it? The child devices aren't being populated.
Seems changing the fixed IP address and rebooting the Shelly fixed this... Or coincidence?
So I added another Shelly wifi switch.. but this one won't update the status unless I go to refresh on the device page. Why would this particular device not update its status unless I click refresh? The others work fine.
I have checked the "output on" and output off and they both have the http://hubitathubaddress:39501/switch/0/on or off in them.. So I'm unsure why the status of the device in hubitat doesn't change when I turn the device in Shelly app.. but it works for the other wifi switches without needing to refresh them.
Bigger Problem is if I click to turn the switch on in a hubitat dashboard then the the status of that switch in the dashboard stays as greyed out with the hour glass...
Ok so I tried for while... But after posting this I went back into Google home app in hubitat and rechecked that this light was ticked.. not thinking that would make any difference .
Now updates of status seem to work for this device ...
Google home is NOT supported with Shelly drivers here as Google home sucks and no one should be using it.
I use Google home a lot, only for speech commands. The moment you make the decision to work with the cloud I think it is better to use the connection Shelly --> google and not via Hubitat.
Same here, only for speech commands. I expose them to google so they are recognised as switches purely for speech. All rules relating to them are run locally. However I hadn't considered adding the Shelly integration into Google home for speech
Whatever it was that made the status update work, without needing to click refresh, it's reliably worked since.
Hello, everyone!
I'd like to extend an invitation for others to join the driver project.
@Evilborg is still going to lead the project, do code review, and contribute, but it's time to allow others to help.
If you're interested, please contact Scott or me to talk about how you see contributing.
I have had 2 strokes in the past year and half and its time for help.. there are perks to this gig too.
Hi All. Newbie here, I'm afraid. I have successfully managed to get my Shelly Plus 2PM working fine, thanks to @Evilborg drivers. What I am struggling with is my Shelly EM. I am using the Shelly Energy Meter driver v 1.0.1 but I have no idea how to successfully put a tile an a dashboard showing how much energy is being used. Any 'pointers' would be very gratefully received. Many thanks
You might want to post that question in the drivers page, not same author...
Thanks for the suggestion @nclark . I have, however, already posted on there but received no response as yet. I suspect it is me doing something amateurish that is causing the problem and I thought also asking on here on what is a busier forum may yield some tips. Happy to remove from this page though if causing offence to anyone?
Ed13 Let me get back to you tomorrow. Friday is full. I will write up guided instructions.
Just a reminder that I am giving up my role as the official shelly drivers developer. I will be putting out 1 driver for the Smoke detector next week and that's it unless someone steps up and continues the work. There perks to this gig... you will be getting device for free that might or might not be prototypes but any case you will be getting free shelly devices in exchange for your time.
I will still head the actual github repo and verify the work until I am sure the person taking my place will carry on using the same structure.
Please contact me or @dougroberson if interested otherwise the official drivers will not be maintained or created anymore after this summer.
Thank you for all your work on this. While I do not use many Shelly devices, the ones that I have been able to incorporate into my Hubitat environment have been fantastic. Thank you again!
Hello, anyone here have a walkthrough or even just some tips getting the Shelly H&T Plus connected to hubitat? I am normally pretty good at figuring these things out but this one has me stumped for some reason. I currently have it connected to my home assistant but I will be attempting to add it to hubitat again in the next couple days so any tips would be greatly appreciated! Thanks in advance.
You will need a mqtt server or you will need to setup makerapi
Hi Doug,
The start of this thread states that Allterco Robotics took over the ownership of Scott's github repo. I would assume that someone from Allterco Robotics would therefore handle writing the device drivers, and/or work with the Hubitat devs to do so.
I just went looking for a driver for the Shelly Uni, for example, and was puzzled to find that Hubitat has built in drivers for 8 different Shelly devices, but not the Uni.
I'd like to use the Uni to monitor some temperature sensors and a water tank level sensor and I'd like to have that information displayed on one of my Hubitat dashboards. This seems like an obvious use case for the Uni so it also surprised me quite a bit to see several posts along the lines of "I don't see a use for having a driver for this."
Is a driver for the Uni planned? I bought the Uni because the Shelly website shows Hubitat as a supported Hub which led me to believe it would be supported.
Download the Hubitat app
