It has been about 3 weeks since I submitted a form via the warranty page. I received an email asking me to upgrade the firmware, which I did. After that I received a message saying something to the effect that the support people were busy and they would get back to me.
They never did. I submitted an additional request with no response whatsoever. So, I'll try and post something here. The hub has not been working properly for about a month.
Here is some history. After replacing a failed hub with this one, everything worked fine for about a year or so. Then, the ZWAVE radio stopped working about a month ago (Zigbee is fine). Occasionally, after a power-on reset, the ZWAVE radio will communicate with devices for a few minutes but then always stops. I don't regularly update the firmware and I hadn't made any changes to the hub when it started to fail. I can communicate with the hub and everything other than the ZWAVE radio seems to be fine. Upgrading the firmware (as requested) doesn't seem to have any impact on the problem.
Based on your engineering log it appears that your radio is currently functional. You do not have issues with the Z-Wave cloud backups, either, which is also indicative of a functional radio. We noticed quite a few power interruptions. These may have been triggered by you performing the "power-on reset." If your hub is plugged into an UPS, you may want to remove the UPS to see if your problems persist.
Power-on reset means that I unplug the Habitat for 30 seconds and then plug it back in.
I switched to a 2A power supply - no change.
I will post a screen shot of the topology map once the hub is up for at least 12 hours.
I did more experimentation today. The Z-wave radio seems to be receiving but not transmitting. For example, once connected to the Hubitat via my browser, I select a specific light switch for viewing. When I click either the "on" or "off" button in the browser, a "Command Submitted" message appears but nothing happens at the switch. Also, nothing appears in the log. However, if I physically press the light switch on/off, a message appears in the log.
I noticed one other thing, if I unplug the Hubitat for 30 seconds and plug it back in, I can control the light switch via the browser for a very short time - about a minute. After about a minute the Hubitat can no longer turn the light switch on or off. I attached a screenshot of the log for the light switch. Note that I plugged in the Hubitat at about 5:14 PM.
Just curious how you can determine the functionality of the radio remotely? I can see that you could be able to determine the status of the digital side of the radio but how would you know if there was something wrong with the analog side of things? Also, as stated in my reply to jtp10181, it seems that the radio receives data from the light switch but doesn't transmit data to the light switch.
The radio would not start when the hub starts, and there would be persistent messages in your hub's engineering log that the radio is offline or crashes. Once the radio is functional, it's a matter of network's health, and more often than not, the mix of devices that directly impact radio's performance. A few offline devices or too many power reporting devices can bring a mesh to its knees. If you didn't see this document already, it's a good place to start: How to Troubleshoot Z-Wave | Hubitat Documentation
Yes, I've seen a couple similar reports here. Memory says they were resolved by a soft reset followed by a power cycle.
However, before making that recommendation, it would be useful to see your entire z-wave details page (as a screenshot), to evaluate it for ghosts and other anomalies that compromise function.
Hub has been up for about 4 hours (I power-cycled it when I changed to a new power supply as somebody mentioned). I think I count 3 ghost nodes if I am looking at this correctly.
I have seen this a few times as well. Might take a little bit but hopefully we can figure it out. We might go round in circles a couple times, its not an exact science. After I see your z-wave info I will have a better idea of where to start and can dig up some old threads.
Remove them if you can, it may help it may not. If you can wait the 12 hrs to get the screenshots that would be better so the stats can populate. I am looking deeper than just ghost nodes.
I am not able to remove the ghost nodes. They have been there for a long time so I don't know if they are the source of the problem. I will repost all of the stats tomorrow after the hub has been up for at least 12 hours.
We've had a few cases where the Z-Wave software can get in an odd state. Our engineers are aware of these edge cases and are working on addressing the problems. The fixes will be first released in the beta channel. If you'd like, I can enroll your hub into the beta program so that when the fixes are released you can get the update right away.
