Nice work finding the bug. That really helps us all in the long run. I have noticed with the newest release of Hubitat (probably the one your running too) some of my Zwave devices have been a little sluggish. I know they made major changes to Zwave from this firmware from the last large update.
For me the last large update worked great, but others not so much. I'm hoping I can get back to the snappier responses I was seeing on the last update, but with the better reliability of the new update. I'm sure it'll happen, it just takes time.
Also, if you have a C7 hub, it has the 700 series Zwave chip in it and it really is the first (and maybe still only) hub on the market offering it. So it's going to be a bit more experimental than the older hubs and chips with more users and hours on them.
Though as you mentioned in one of your earlier comments, the bleeding edge is always fun and new features are great to play with. As long as the wife is happy and the hub is doing what I want, then something to experiment with is always enjoyable!
Absolutely!!! - that is why I keep all the lighting on Hue Hubs - They have been absolutely solid and incredibly rare to have any issue. I am using some 16 Hue Motion Sensors that automate 95% of all lighting.
I have been using Indigo for 6 years, have worked through Vera, Homey, Homeseer and a few others looking for something that hits my core requirements.
Hubitat is the strongest contender by far - so much so I have just ordered a second one today.
Loving the Hubitat Community - all very helpful indeed
I've gone through the logs for the hub. The issue doesn't look like something it can recover from programmatically, and I couldn't hope to reproduce it, but 2.2.5 will have a location event and a main page red-font-in-your-face alert with instructions to shut hub down/unplug/wait/plug it back in.
If we find out more about root cause, I'll post here.
These things happen and appreciate you guys looking at it.
Once I get the second HE - I'll mesh and see if I can work out a way to do a hard reboot - power off wait restart using zigbee sockets once every 24 hours - and hopefully that will keep the issue at bay until resolved.
It looks like a shutdown, turn off power is required, I can put the HEs on a zigbee/zwave switch, so I need to find a way to set a rule say at 12:05 shutdown and on the 2nd HE turn off the switch to the 1st, wait 10 seconds and turn back on.
Newbie needs some help relative to the TH3060ZW integration. I'm confused or else messed this up on my new C7. Dumped Wink for obvious reasons and went to C7. The stat worked fine in Wink and I think it used to work ok into C7. But no longer, perhaps broken in an update? Unsure. The Dashboard seems to work allowing be to change setpoint, etc. But that is never carried out at the thermostat itself nor correct values it reads show back into Dashboard. I deleted and re-connected the thermostat via Zwave on Hubitat and the thermostat. No change.
Confused about using Generic, the Contoller driver, or the T6 one many say also works fine with the basic unit I have. What should I be looking for to get this working again. A few screen captures:
This is a z-wave thermostat (not z-wave+). The only built-in driver that might work with it is "Generic Z-Wave Thermostat". If you change drivers, be sure to click "Configure" after doing so.
And I would first make sure the thermostat works from the device page before getting it to work in a Dashboard.
