I've been working on porting my Sonoff Connect over to Hubitat in my spare time. I have the discovery app working, firmware updated, and the driver for the Sonoff Basic done. The drivers are taking a little extra work as I've had to use some alternate LAN communication methods to get Basic Authentication working. That is for those that want to password protect their Sonoff devices.
There is a wealth of knowledge on the SmartThings forums. Probably a little too much knowledge and I haven't had time to keep up on it.
Here is the Connect app for Hubitat:
Here are the driver and firmware links. Source is here.
I'll work on the drivers that aren't finished yet, but if you take a look at what I had to do with the "Basic" driver, you can probably figure it out. If anyone does update them in the meantime, let me know!
I installed the driver for the TH16 I have which initially threw an error.
dev:3332018-07-10 19:24:52.755:errorgroovy.lang.GroovyRuntimeException: Could not find matching constructor for: hubitat.device.HubAction(hubitat.device.HubAction, null) on line 121 (updated)
I updated line 121 from
if (cmds != ) response(cmds)
if (cmds != ) sendHubCommand(cmds)
This then allowed, a Configure, and I can see in the logs its pulling back the data, but now having an issue with the Temp sensor connected, attempting conversion I think?
dev:3332018-07-10 19:28:28.994:errorgroovy.lang.MissingMethodException: No signature of method: dev1531247265336797493147.convertTemperatureIfNeeded() is applicable for argument types: (java.lang.Float, java.lang.String) values: [25.56, C] on line 175 (parse)
Any ideas? As I can see the Temp is being picked up.
Yeah, that driver wasn't quite finished. In the main post, if the "Driver" link is grayed out then I haven't fully converted them.
Good news is that I did just post the link for the TH though. I haven't had a chance to test the temperature conversion so I need to see if that is still throwing an error. Everything else is seeming to work though.
I updated, and its working GREAT! Many thanks for this @ericm, this was one piston I was really missing. Have to keep a check on the Aquarium I don't see any errors being thrown, and have it SMS the Temp which is also triggering very well.
I just moved my devices (about 20 or so s20's) into Hubitat from ST. Currently with the firmware I flashed onto em when I first set them up with ST. They don't report when they're turned on locally. I.E. Someone walks up to the thing and presses the button on the s20, and it doesn't report in Hubitat unless I go into the device settings and manually refresh it. Is there a difference between the ST and Hubitat firmwares? OR is auto refreshing not something that hubitat will do? I just want to know before I start opening all of them and re-flashing them.
Correct, there's a difference. ST polls every (ZWave) device every 10 seconds. For devices that a) don't need status and b) devices that return status already (Zwave Plus) it's a waste of Mesh resources. Hubitiat's in-built refresh rate is ZERO, as in Never. You can however, create a Rule Machine Rule to run periodically and refresh ONLY the few devices that need the status.
Good news! The new firmware works with your current HE drivers and code.
Since you are still in development one of the coolest features in HE for SmartLife RGBw could be the new Scenes capabilities. As of now the DH doesn't support what is needed to capture color. @mike.maxwell posted recommendations here for standardizing color for scenes to capture. Not sure if you can look at this and make changes too.