Using Hubitat with SharpTools and having issues on my lower level. Between the hours of 3am and 8am (roughly) nothing is responding through wall switches or directly through SharpTools dashboard. I've looked at the logs to identify the problem, nothing is "scheduled" or "running" during this time. Eventually, the lights will turn on, but then they get stuck again and won't turn off after 3-5 minutes, the requested action will occur and show up on the logs. I've run the updates, rebooted the hub, I can't locate the issue and it's been happening for months. I use Aeotec Wallmote Quad switches and they are fully charged (set to auto charge 3 times a week). Can someone point me in the right direction?
First I would eliminate Sharptools as a potential issue and use a local HE dashboard for troubleshooting.
Second what happens when you try to manipulate the devices directly from the devices tab?
Third what kind of switches are they?
And fourth can you post a screen shot of your zwave details page?
Oh and last I see you're on the current HE platform release.. what about zwave radio firmware updates? There have been a couple in the last few months that have made significant improvements in zwave performance. They are not automatically applied, but instead when one is available there's an update button that appears on the zwave details page.
It sounds like it's happening with their physical Aeotec Wallmote Quads.
1 Like
I should have been more specific... I was wondering what kind of switches are being manipulated by the wall motes. In other words is the issue with the wall mote or at the other end? I'm thinking maybe zwave mesh issues but the zwave details page should help. Also if the devices can be manipulated directly from the devices page that would eliminate an issue on that side of the automation, which might very well mean it is the wall motes.
(the wall mote quads are not switches - they're just button controllers)
2 Likes
Thanks @brad5, I'm a newbie so you already helped by pointing me that direction. I went to the zwave details page and many of the "lower level" devices had "refresh" or "repair" next to them. So I'm running a zwave repair and firmware update. The aeotec wall mote quads are supposed to use zwave plus not needing repair but we'll see. Appreciate the help. I'll provide more info later.
Devices that are line powered will have a refresh and repair button. That's normal and not indicative of an issue. A full repair can actually cause more issues since it floods the zwave network with messages.
The firmware update will certainly do no harm and likely do quite a bit of good. But a screen shot of your zwave details page would be most helpful. What are the devices you're trying to control with the quads? The issue could be at that end too.
1 Like
@brad5 there are too many devices to screenshot them all but here is the "buttons" used as a light switch operating the can lights in the ceiling.
The zwave repair and the firmware updates didn't help. But when i reboot the hub everything works great. So i used RM to reboot the hub at 4am daily. That seems to be working is there any unintended consequences of rebooting the hub daily?
Thanks for all your help.
Here is the event log showing the reboots working:
I think what Brad (and others) are looking for with the screenshots is a device with incomplete pairing, ghosts, devices paired with S0, or devices that just aren't communicating well. It would be good if you could attach the complete Z-wave details even if you have to take multiple screenshots to do so.
No, but it would probably be better if you can find the root cause instead of covering it up with reboots. If everything is healthy, you shouldn't have to reboot.
1 Like
That is pretty bad, maybe even the worst I have ever seen. Everything that has [Discover], and is line powered, is a ghost or incomplete pairing. It is no wonder you are having troubles.
Battery powered sensors that have [Discover] may or may not be a ghost, they may just have not responded since a reboot, for example. They should be looked at eventually, but those line powered ghosts need attention first.
Removal might be tough with the mesh in this bad shape. You are probably going to have to find and de-power the device that caused the ghost. Typically the device that caused the ghost is immediately below the ones that say [Discover]. For example 0x79 through 0x82 are likely from failed pairings of 0x83. Did you have lots of trouble including that device or have to pair it multiple times to get it complete the inclusion process? If so, these are the result of that.
I would also remove a couple devices, and reboot the hub, and let things settle for a few minutes before trying again.
1 Like
I'm with @neonturbo on this one. I don't think I've ever seen one this bad. Have you tried a complete power down? f you haven't already, shut down the hub, disconnect the power from the wall (not by yanking the micro usb connector), wait 5 min, and restart. Those ghosts might magically all go away but I doubt it. If they don't it may actually be easier to reset the zwave radio, which removes all zwave devices. I know that sounds dramatic and a ton of work but it may be less work in the long run. But see how the power down works and then maybe we will get some additional input from the community. If you could re-post your zwave details page after the power down that would be helpful.
And to answer your question... a nightly reboot is definitely not the right solution.
@brad5 and @neonturbo
Want to make sure I understand, so if there is "discover" in the device column and/or "nothing" in the route column, it's likely a ghost node? Like this for example
If it is a ghost node, per the Hubitat Documentation I can click the "Refresh" button and a "Remove" button should pop up. I should first go through the list and remove all of these is that what you're saying?
If it has "discover" in the device but also has something in the "route" column, does that mean it is connecting to something but can't identify what it is? Like this for example:
I followed the instructions and hit refresh and the remove button appeared. Just making sure I understand everything you're suggesting as a first step.
Again, I appreciate all the help on this! Thank you.
Yes but for the remove to be successful the physical device that represents the ghost must be out of range or unpowered and unable to contact the hub.
Did you try the 5 min power down?
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
