ZWave control stopped working completely - although Power status works

🛎️ Get Help
6

And, what do you know: when I turned Hubitat and circuit breakers (although breaking power to the ZWave items did not seem to be key - a few of them already had the light off, and had power the whole time) on this morning, everything works again. HUGE thanks for the help!

As I said, I'm new to Hubitat: Does anyone have a theory as to why this happened? Is it common? Is this type of behaviour something that I should expect going forward as well? If so, I'm going to have to reconsider using Hubitat.

7

And wow, same thing happened today: I've connected a few more controllers during the day, everything went well, and after a break, the system stopped responding in the same way as the day before. Are there any low-level logs that I can have a look in to figure out what the problem is?

8

I suspect you have a failed pair aka ghost node on your network. You can pickup a UZB-7 USB controller and pair it to your Hubitat and it will allow you to delete these pesky ghost nodes that are causing havoc on your mesh.
https://www.mouser.com/ProductDetail/Silicon-Labs/SLUSB001A?qs=u16ybLDytRbJsMfgk3EnSA%3D%3D

If picking up the UZB isn't an option you could reset the zwave radio from settings and start again, but that is going to delete any devices you added.

In the meantime I suggest rebooting it and upgrading the the latest hub software in settings.

9

Thanks for the advice. I've been through the rebooting/poweroff for 30 mins sequence a cpuple of times already without any differences.

I was already at the latest version, and rolling back to 2.2.2.129 did not help either.

I'm beginning to suspect it depends on the time of dsay (crazy!) - it stopped working at about the same time both days. I know, it seems crazy, but I'm running out of ideas...

[Oh yes, another fact: I've built my automations with the Button Controllers if that matters?]

As to buying a UZB-7 and delete ghost nodes: I googled a bit, and it looks to me like a) they are visible in the UI, and I can't see any, and b) C-5 should delete them automatically from the stick. Remove Ghost Nodes

If I want to go that route, I have two questions: a) what software should I use with it? and b) I already have an Aeotec Z-stick Gen5 - could I use that instead?

10

The aeotec stick will work PC controller software v5. Yes I asked you to roll back to see if it was an issue with the hub version. With it still happening after a roll back every other time I've seen it's been a ghost device. Check if you have any devices in settings zwave details with nothing for in out clusters besides 1 at the top that is the hub radio.

It usually takes a while before the radio bugs out with ghosts. Depending on how many you have it could be anywhere from a few minutes to a few hours. The more you have usually the faster you have problems.

Button controller shouldn't matter. These problems just recently cropped up with the .119 and later updates. It always affected your mesh before but at least back then things would just run slower instead of crashing. They are working hard to clear up all the issues and it isn't the norm. Clearing out the ghosts with PC controller should clear things up.

If you don't have any ghosts it could possibly be a memory leak. I'll check and see if I can track down the post that talks about it.

11
12

Thanks a lot for the help @lewis.heidrick!

  • I could not find any ghosts no matter how hard I tried.
  • The system did not start to work after a night's rest like the day before.
    So i decided to exclude all devices, reset the Hub, and start over. I guess I should have tried to debug for longer, but we have a big party at home tonight, and I had to get everything to work before that.

And it worked for a while:

  • Hub fully reset and upgraded to 2.2.3.144
  • I only included the devices without any automation.
  • I connected to Google Home - quicketst way to make sure I had some control for when guests arrived. No other apps.
  • After I stopped configuring and left the system to itself, it worked for about 10 hours before stopping again, just as last time.
  • Reboot does not help
  • Memory status Green, memory 532028
  • http://hubitat.local/hub/zwave/nodeCleanup did not help
  • http://hubitat.local/hub/zwaveRepair did not help
  • Updated to 2.2.3.145 which just appeared as I was writing this. Did not help.
    This is getting ridiculous. I'm getting close to eating the cost of the Hubitat and just go and buy something else,

Here's my Z-Wave device list. In addition to that I have one Zigbee Hue Lamp. I did not have that the first time I set up the system though and it still did not work, so taht should not be it.

0x27 (039) 82 1 in: 0x5E, 0x86, 0x5A, 0x72, 0x73, 0x98, 0x27, 0x25, 0x26, 0x32, 0x71, 0x85, 0x8E, 0x59, 0x70, out: 0x26 Z13 Tevehörna - Taklampa
0x28 (040) 82 1 in: 0x5E, 0x86, 0x5A, 0x72, 0x73, 0x98, 0x27, 0x25, 0x26, 0x32, 0x71, 0x85, 0x8E, 0x59, 0x70, out: 0x26 Z21 Sovrum: Säng
0x29 (041) 85 1 in: 0x5E, 0x25, 0x26, 0x85, 0x59, 0x55, 0x86, 0x72, 0x5A, 0x70, 0x32, 0x71, 0x73, 0x98, 0x9F, 0x6C, out: Z22 Minihall - Taklampa
0x2C (044) 82 1 in: 0x5E, 0x86, 0x5A, 0x72, 0x73, 0x98, 0x27, 0x25, 0x26, 0x32, 0x71, 0x85, 0x8E, 0x59, 0x70, out: 0x26 Z11 Tevehörna - Tavelspot
0x2D (045) 82 1 in: 0x5E, 0x86, 0x5A, 0x72, 0x73, 0x98, 0x27, 0x25, 0x26, 0x32, 0x71, 0x85, 0x8E, 0x59, 0x70, out: 0x26 Z19 Sovrum - Garderob
0x30 (048) 4096 2304 in: 0x27, 0x72, 0x86, 0x26, 0x60, 0x70, 0x32, 0x31, 0x85, 0x33, out: Z04 Köksö - Vitrinskåp
0x32 (050) 85 1 in: 0x5E, 0x25, 0x26, 0x85, 0x59, 0x55, 0x86, 0x72, 0x5A, 0x70, 0x32, 0x71, 0x73, 0x98, 0x9F, 0x6C, out: Z20 Sovrum - Taklampa
0x33 (051) 82 1 in: 0x5E, 0x86, 0x5A, 0x72, 0x73, 0x98, 0x27, 0x25, 0x26, 0x32, 0x71, 0x85, 0x8E, 0x59, 0x70, out: 0x26 Z01 Kök - Taklampa
0x34 (052) 82 1 in: 0x5E, 0x86, 0x5A, 0x72, 0x73, 0x27, 0x25, 0x26, 0x32, 0x71, 0x85, 0x8E, 0x59, 0x70, out: 0x26 Y
0x35 (053) 82 1 in: 0x5E, 0x86, 0x5A, 0x72, 0x73, 0x98, 0x27, 0x25, 0x26, 0x32, 0x71, 0x85, 0x8E, 0x59, 0x70, out: 0x26 Z02 Köksö - Spotlight
0x36 (054) 85 1 in: 0x5E, 0x25, 0x26, 0x85, 0x59, 0x55, 0x86, 0x72, 0x5A, 0x70, 0x32, 0x71, 0x73, 0x98, 0x9F, 0x6C, out: Z07 Kök - Diskbänk
0x37 (055) 82 1 in: 0x5E, 0x86, 0x5A, 0x72, 0x73, 0x98, 0x27, 0x25, 0x26, 0x32, 0x71, 0x85, 0x8E, 0x59, 0x70, out: 0x26 Z16 Lounge - Spotcirkel 2020-09-06 15:47:07 CEST
0x38 (056) 82 1 in: 0x5E, 0x86, 0x5A, 0x72, 0x73, 0x98, 0x27, 0x25, 0x26, 0x32, 0x71, 0x85, 0x8E, 0x59, 0x70, out: 0x26 Z08 Hall - Taklampa 2020-09-06 15:38:53 CEST
0x39 (057) 82 1 in: 0x5E, 0x86, 0x5A, 0x72, 0x73, 0x98, 0x27, 0x25, 0x26, 0x32, 0x71, 0x85, 0x8E, 0x59, 0x70, out: 0x26 Z15 Lounge - Taklampa 2020-09-06 15:49:10 CEST
0x3A (058) 82 1 in: 0x5E, 0x86, 0x5A, 0x72, 0x73, 0x98, 0x27, 0x25, 0x26, 0x32, 0x71, 0x85, 0x8E, 0x59, 0x70, out: 0x26 Z17 Arbetsrum - Spotlight
0x3B (059) 85 1 in: 0x5E, 0x25, 0x26, 0x85, 0x59, 0x55, 0x86, 0x72, 0x5A, 0x70, 0x32, 0x71, 0x73, 0x98, 0x9F, 0x6C, out: Z10 Matbord - Glasklasen
0x3C (060) 175 3 in: 0x5E, 0x85, 0x59, 0x55, 0x70, 0x2C, 0x2B, 0x81, 0x71, 0x32, 0x25, 0x33, 0x26, 0x86, 0x72, 0x5A, 0x22, 0x75, 0x73, 0x98, 0x9F, 0x6C, 0x7A, out: Z99 Lounge - Bordslampa 2020-09-06 15:43:11 CEST
0x3D (061) 10 256 in: 0x5E, 0x25, 0x32, 0x27, 0x2C, 0x2B, 0x70, 0x85, 0x59, 0x72, 0x86, 0x7A, 0x73, 0x5A, out: Z98 Köksö - Snöflingor 2020-09-06 15:49:01 CEST
0x3E (062) 130 2 in: 0x5E, 0x85, 0x59, 0x8E, 0x60, 0x86, 0x70, 0x72, 0x5A, 0x73, 0x84, 0x80, 0x5B, 0x71, 0x7A, out: 0x25, 0x26 Q01 - Kök 2020-09-06 15:44:28 CEST 2020-09-06 15:44:23 CEST
0x3F (063) 130 2 in: 0x5E, 0x85, 0x59, 0x8E, 0x60, 0x86, 0x70, 0x72, 0x5A, 0x73, 0x84, 0x80, 0x5B, 0x71, 0x7A, out: 0x25, 0x26 Q02 - Köksö 2020-09-06 15:46:37 CEST 2020-09-06 15:46:33 CEST
0x40 (064) 130 2 in: 0x5E, 0x85, 0x59, 0x8E, 0x60, 0x86, 0x70, 0x72, 0x5A, 0x73, 0x84, 0x80, 0x5B, 0x71, 0x7A, out: 0x25, 0x26 Q03 - Matbord 2020-09-06 15:43:05 CEST 2020-09-06 15:43:03 CEST
0x41 (065) 130 2 in: 0x5E, 0x85, 0x59, 0x8E, 0x60, 0x86, 0x70, 0x72, 0x5A, 0x73, 0x84, 0x80, 0x5B, 0x71, 0x7A, out: 0x25, 0x26 Q04 - Hall 2020-09-06 15:45:41 CEST 2020-09-06 15:45:37 CEST
0x42 (066) 130 2 in: 0x5E, 0x85, 0x59, 0x8E, 0x60, 0x86, 0x70, 0x72, 0x5A, 0x73, 0x84, 0x80, 0x5B, 0x71, 0x7A, out: 0x25, 0x26 Q05 - Lounge 2020-09-06 15:46:05 CEST 2020-09-06 15:46:02 CEST
0x43 (067) 130 2 in: 0x5E, 0x85, 0x59, 0x8E, 0x60, 0x86, 0x70, 0x72, 0x5A, 0x73, 0x84, 0x80, 0x5B, 0x71, 0x7A, out: 0x25, 0x26 Q06 - Tevehörna 2020-09-06 15:42:26 CEST 2020-09-06 15:42:22 CEST
0x44 (068) 130 2 in: 0x5E, 0x85, 0x59, 0x8E, 0x60, 0x86, 0x70, 0x72, 0x5A, 0x73, 0x84, 0x80, 0x5B, 0x71, 0x7A, out: 0x25, 0x26 Q07 - Minihall 2020-09-06 15:44:48 CEST 2020-09-06 15:44:44 CEST
0x45 (069) 130 2 in: 0x5E, 0x85, 0x59, 0x8E, 0x60, 0x86, 0x70, 0x72, 0x5A, 0x73, 0x84, 0x80, 0x5B, 0x71, 0x7A, out: 0x25, 0x26 Q08 - Arbetsrum 2020-09-06 15:45:27 CEST 2020-09-06 15:45:22 CEST
0x46 (070) 130 2 in: 0x5E, 0x85, 0x59, 0x8E, 0x60, 0x86, 0x70, 0x72, 0x5A, 0x73, 0x84, 0x80, 0x5B, 0x71, 0x7A, out: 0x25, 0x26 Q09 - Sovrum
0x47 (071) 82 1 in: 0x5E, 0x86, 0x5A, 0x72, 0x73, 0x98, 0x27, 0x25, 0x26, 0x32, 0x71, 0x85, 0x8E, 0x59, 0x70, out: 0x26 Z09 Matbord - Vägglampa 2020-09-06 15:46:34 CEST 2020-09-06 15:49:15 CEST
0x48 (072) 82 1 in: 0x5E, 0x86, 0x5A, 0x72, 0x73, 0x98, 0x27, 0x25, 0x26, 0x32, 0x71, 0x85, 0x8E, 0x59, 0x70, out: 0x26 Z03 Hall - Glasbetong
0x49 (073) 82 1 in: 0x5E, 0x86, 0x5A, 0x72, 0x73, 0x98, 0x27, 0x25, 0x26, 0x32, 0x71, 0x85, 0x8E, 0x59, 0x70, out: 0x26 Z12 Tevehörna - Bordsspot
0x4A (074) 82 1 in: 0x5E, 0x86, 0x5A, 0x72, 0x73, 0x98, 0x27, 0x25, 0x26, 0x32, 0x71, 0x85, 0x8E, 0x59, 0x70, out: 0x26 Z23 Minihall - Dörröppning 2020-09-06 15:48:08 CEST
0x4B (075) 85 1 in: 0x5E, 0x25, 0x26, 0x85, 0x59, 0x55, 0x86, 0x72, 0x5A, 0x70, 0x32, 0x71, 0x73, 0x98, 0x9F, 0x6C, out: Z18 Arbetsrum - Taklampa 2020-09-06 15:39:12 CEST
0x4C (076) 82 1 in: 0x5E, 0x86, 0x5A, 0x72, 0x73, 0x98, 0x27, 0x25, 0x26, 0x32, 0x71, 0x85, 0x8E, 0x59, 0x70, out: 0x26 Z14 TVhörna - Bokhylla
0x4D (077) 10 3 in: 0x5E, 0x85, 0x8E, 0x59, 0x55, 0x86, 0x72, 0x5A, 0x73, 0x9F, 0x25, 0x32, 0x75, 0x70, 0x5B, 0x31, 0x6C, 0x7A, out: Z97 Terrass - Bollar
0x4E (078) 10 3 in: 0x5E, 0x85, 0x8E, 0x59, 0x55, 0x86, 0x72, 0x5A, 0x73, 0x9F, 0x25, 0x32, 0x75, 0x70, 0x5B, 0x31, 0x6C, 0x7A, out: Z96 Terrass - Slinga 2020-09-06 15:42:05 CEST
13

As part of my issues in this thread, I'm thinking about all the "java.lang.NumberFormatException" errors I'm getting in the log.

  • I have a super-basic setup so far. NO automation whatsoever. NO App; I did have the Google Home App installed for a while, but removed it just to eliminate any potential problems with it.
  • Devices; Aeon Wallmotes, Qubino Dimmer Modules [DIN], One Fibaro RGBW controller, Qubino Mini Dimmers, 1 Zooz power switch, 2 Popp Power Outlets (configured as generic)
  • The devices that are generating the errors are all Qubino Dimmer Modules, but it's not all of them, "only" 5 of 15.
  • When I click on or off for a device, no entry is genereated in the logs.
  • I do get log entries for energyDuration, power, energy, and such, so there seems to be SOME life in the network.
    Is it something I should be worried about? Can it be the reason for my general problem (no control of devices possible at all)? What can be the issue?
14

Those java errors will trash the hub and its operation for sure. Can you run the mesh without the badly behaving qubinos? Do the "bad boys" have a different firmware revision?

15

That the java errors would disturb the operation, I can get. But to the extent that a restart doesn't help? Sounds a bit unlikely to me, no? Is there any way to get more detailed error messages?

Firmware revision: How do I even find out which version they have?

And the java software should be the driver running on the Hubitat side of things, not the software on the devices themselves? Would I be better off by using a generic drive instead of the Qubino-specific ones?

I'll see what I can do about disconnecting the "bad boys". A quick look at the log this morning shows that it is at least one more, so I have to have a more careful look to see exactly which it is.

16

So, I finally gave up on Hubitat and bought a Samsung SmartThings. When I came home and should start to exclude the devicee from the Hubitat, it suddenly started to work again. I still have the "java.lang.NumberFormatException" errors (now on a different device) but they don't seem to matter.

The only thing I can think about that I changed was to deactivate/uninstall the Google Home app. I had already powered off/unplugged power/waited 30 mins once without result, but it seems like the threat of throwing the box out was enough for it to shape up. :stuck_out_tongue_winking_eye:

17

Works great on my kids. :grin:

18

Just wanted to let everyone know how this turned out.

The problem kept coming back after a few hours to a day, and I was not able to get the Hubitat to work reliably at all. Neither was support able to help me. So I bought a SmartThings hub, which, although far less capable, at least works for turning the lights off and on reliably.

I'm still keeping the Hubitat up and running, but it is only because the SmartThings hub has minimal support for any Zigbee buttons except Philips own, so the Hubitat continues to control my single(!) Hue lamp+Aqara switch combo (which it does well).

I can only guess that the problem is the driver for my Qubino DIN dimmer (after all, it's not officially supported). Hopefully Qubino and Hubitat can work something out, in which case I will be back with a full Hubitat system.

Thanks for the help everyone!

1 Like
19

What Qubino dimmer and driver are you using.
I have one that is using the HE driver and it is working well.

20

I have a mix of DIN and Mini Qubino dimmers. It's only the DIN dimmers that gives the "java.lang.NumberFormatException" errors. I've tried a few different drivers (Qubino Dimmer, Generic Z-Wave dimmer, etc), but all of them gives the same result.

More complete list * Devices; Aeon Wallmotes, Qubino Dimmer Modules [DIN], One Fibaro RGBW controller, Qubino Mini Dimmers, 1 Zooz power switch, 2 Popp Power Outlets (configured as generic)

21

I have the Qubino DIN Dimmers too, and each one spams out a java.lang.NumberFormatException error frequently. The rest of the functionality seems to be OK.

I think some of the default settings in the device are misleading - like the 8 hour power reporting interval (DEFAULT). That's supposed to be 5 minutes, according to the manual.
I suspect it is one of these settings that is causing the problem.

The status shows this, too, which is suspicious:

State Variables

  • energyTime : 1607898465117
  • pendingSwitch : false
22

I have no temperature probe attached, so I tried disabling the temperature reporting frequency. Now the log shows:

[dev:37] [error] java.lang.NumberFormatException
[debug] MeterReport(meterType: 1, precision: 1, scale: 2, size: 4, meterValue: [], rateType: 1, deltaTime: 0, previousMeterValue: [])

May be related to MeterReport, but it's hard to say.

23

Looks like you may have a null value for meterValue, is there an option in the driver to set it to a valid value?

24

This has beeb solved with the current release of Hubitat, which includes a proper driver for the Qubino DIN Dimmer.

1 Like
25

I had NOTHING but problems with that particular dimmer, my main issue was resolved by disabling the power reporting feature on the dimmers as I added them to the hub to cut down on data transmission. According to a member of Staff at Hubitat, it was due to the security settings on the dimmer being high and it needed to send much more data as a result.

A recent job we did, we used FIbaro Dimmer 2s that worked way better with a user-created driver I found after a quick google search. I also found some din rail mountable cases for them so they can be put into a proper enclosure near the fuse board.