@mike.maxwell already has a 2.5 -- the roller/shutter is just not on his list to create. If people hadn't been so nasty to me all my drivers would still be available. FYI @Cobra took down all his apps/drivers for months because of his code being ripped off so I am not the only one who left.
I know now you have discontinued the driver, last thing I read was toy have a new work and you will be developing. It's unhappy read this. At last I hope you will be good on you work.
You're welcome... I hope others feel the same. I really had no plans to ever put my code back on the forum but the better of me decided to do this. Don't take this as weakness -- I can edit that post just as quick as posting it. 1 bitch about it from anyone and POOF
Thanks Scott,
I'm pretty new with hubitat and read a bit about all the drama and I felt so bad for you.
I bought Shelly before I know the drama and then I was struck for some time without your driver.
I will check it out now that you posted it again.... I'm very happy about you kind action.
Thanks again
I don't have any shelly products, and I know you don't care about my opinion, but for what it is worth I think it was very kind and generous of you to post that driver for others to use - you certainly were not obligated to, and had multiple reasons not to.
One is now built into the platform, introduced in 2.2.0 (a month and some weeks old now, but if you happen to be on old firmware, you won't see it). The process to add a device goes something like manually adding a "virtual" device to Hubitat, then filling in the required fields (like IP address) in the driver after you choose the correct driver ("Type:") from the list.
I'm using the native drivers but am having issues getting status back from the Shelly dimmer. I can turn the dimmer on/off successfully from Hubitat, but no status will report back.
It appears to be configured correctly on the Hubitat and Shelly, but I get this error message after I turn the Shelly on/off and I don't receive any status update. I'm also on the latest firmware for Hubitat and Shelly.
I shall be including direct Shelly discovery and support into the MQTT app in a future version (as long as you have the MQTT integration enabled on your Shelly devices). Haven't explored which devices will be supported yet but at least the ones I own. Unfortunately on MQTT I can't see anything that tells me what sort of device it is like a device 'id'
I started down the path of native driver support but when another developer also offered something I backed off. Maybe I will revisit that as I forsee issues with discovery just using MQTT in the way Shelly implement it currently. However that's not something that really belongs in an MQTT app.
I tried moving the Shelly Dimmer to the same vlan as my hubitat, changed the Shelly parent IP information, and that worked successfully.
I moved the Shelly Dimmer back to my IoT vlan and it gives me that error message again. I also removed all of my firewall rules to make sure they could communicate freely across vlans and subnets. However, it still didn't work.
Has anyone else gotten this to work across separate Vlans or Subnets?