I know there are quite a few versions of my original ported code from smartthings around on this forum. Since I've newly acquired a hubitat hub I'm now transitioning over and decided to port my own devices over. Here's my version of the handler/device-code developed for my personal use but sharing it here if anyone finds it useful:
EDIT: updated to allow better integration with dashboard slider and alexa when max open level is set. Also improved the final state reporting so should always end with an open or closed state so that dashboard is able to open or close blinds with single click.
EDIT: added standard hubitat toggles to hide all the debug messages and removed some smartthings only references
EDIT: updated to limit blind level reporting frequency to protect zigbee stack on hubitat
LOL.... So frustrated with what they're doing over at ST. I have been with them since the beginning with over 400 devices and a huge set of rules and custom automations. Have been running well and my setup has needed few changes over the last 2 years.
But their "new" app has trashed a large proportion of my configuration after migration and the recent echo speaks announcement was the last straw.
Will take me months to fully move over. So sad to see them go this way....
It does! Watching the number move made me smile. lol! Question - why does it say 'Opening' or 'Closing', leaving that the state of the shade? No big deal...
It should say either opening or closing during movement and then once stopped after a few seconds say either: Open, Closed or Partially Open. At least that's what it's supposed to do. I'll take a look later to see if I can spot anything wrong.
I thought somewhere buried in that huge other thread on these blinds that the zigbee pairing with Hubitat disables the pairing of the buttons. That is why the buttons do not work.
For us it's not a big deal since the Alexa integration works so well, even though it almost always says 'I'm not quite sure what went wrong' when in reality it worked.
Have you tried with my driver code? I also saw that error a few times early on but not seen that error occur after a few changes. Not sure if it fixed.
With your driver it still says that phase that something went wrong, but it worked.
I think you driver logic is opposite of the last driver - set to 10% will be 10% open, 90% closed. My rule to close the shades at night just opened them all the way. I'll update my rules and re-think this!
Yes, Welcome and thanks! I got the same email about echo speaks, it and HubConnect are the only things I still have on ST. It's about to stop working for me soon.
My very early versions of the smartthings handler were the wrong way round so if that was used as a source then this might have caused this. I needed it this way so that other integrations which made direct calls to blind level rather than call the open or close functions would still work.
If you think of the shade being the equivalent of a dimmer of a light then it makes sense. The higher the percentage the more light let through.
