Zwave bulb not showing up in HASS, but is in the zwave log

Configuration Z-Wave
1

I am using a monoprice RGB bulb. I had it attached correctly to HASS a while back (as Node009), but removed it at some point. Trying to re-attach it now. No amount of add-node, repair-node, replace-node will get HASS to recognize it again. I do see it transmitting in the OZW_log when I turn it on, but it’s not on my list of known nodes in HASS.

2018-01-16 17:45:32.776 Detail, Node009,   Received: 0x01, 0x09, 0x00, 0x04, 0x10, 0x09, 0x03, 0x20, 0x03, 0x63, 0xa8
2018-01-16 17:45:32.776 Detail,
2018-01-16 17:45:32.784 Detail, Node009,   Received: 0x01, 0x09, 0x00, 0x04, 0x10, 0x09, 0x03, 0x20, 0x03, 0x63, 0xa8
2018-01-16 17:45:32.784 Detail,
2

Sometimes the following procedure can get you past z-wave configuration glitches:

  1. stop the z-wave network (or HA altogether)
  2. mv the zwcfg file to some other name
  3. restart HA

This should rebuild the zwcfg file from scratch, and may help getting you into a good state again.

3

Just tried this - didn’t help. Still couldn’t see or add Node009.

4

Does it exist in your zwcfg file?

5

No, there is no node 9 entry.

6

Ok, then the issue is it still needs to be included into your zwave network. Which zwave controller are you using? Aeotech? UZB?

What is the inclusion procedure for this bulb?

7

I have the Aeotech ZW090 gen 5. The bulb is goes into inclusion mode pretty much by turning it on (https://downloads.monoprice.com/files/manuals/27482_Manual_170720.pdf).

The bulb appears to be announcing itself as node 9 in the OZW_log, despite not being in the zwcfg file. Is that node 9 designation saved inside the bulb?

8

Are you sure you’re not seeing older log entries before regenerating the zwcfg file?

The included zwave devices are saved on the USB stick. With the Aeotec, if you unplug it and bring it to the bulb for inclusion, do you get the blinking lights that show the stick successfully included the bulb? If I remember, slow blink means inclusion mode, fast blink when it is communicating with the device, then it goes solid briefly to indicate successful inclusion.

If that happens, then you should get a new entry in the zwcfg log after shutting down your server, reinserting the USB stick, bringing it back up, then stopping the zwave network again. (The new zwcfg info gets fully written out when the network is stopped).

9

It doesn’t seem like I the Aeotec is successfully including it (or excluding it). Both maneuvers don’t seem to register with the stick. The bulb continues to broadcast as node 9 afterwards…

10

Well it is certainly strange that your z-wave device is communicating with the controller, but the controller is not writing out information for the node. Kind of sounds like it’s included, but in some hinky way, and the key might be to get it excluded first.

Is this the one?
https://www.monoprice.com/product?p_id=27482

Looks like it has an odd procedure for exclusion: controller into exclusion mode, then turn on, then toggle 3 times to initiate exclusion. Success is indicated by orange blinking of the bulb. Have you tried that?

11

Yeah I tried that. The bulb did blink once orange but not as expected, and the usb stick did not indicate exclusion occurred.

12

Sounds like this calls for extreme measures. If you don’t have a lot of devices on your z-wave network and don’t mind re-adding them, factory resetting the controller might be the easiest way forward.

13

Did a full reset of the zwave network and controller. Still can’t add these bulbs! No issues re-adding all the other devices (door switches, plugs, motion detectors).

2018-03-06 19:59:14.505 Info, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2018-03-06 19:59:14.505 Info, ADD_NODE_STATUS_NODE_FOUND
2018-03-06 19:59:14.505 Detail, Notification: ControllerCommand - InProgress
2018-03-06 19:59:17.941 Detail,   Received: 0x01, 0x07, 0x00, 0x4a, 0xc6, 0x07, 0x00, 0x00, 0x73
2018-03-06 19:59:17.941 Detail,
2018-03-06 19:59:17.941 Info, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2018-03-06 19:59:17.941 Info, ADD_NODE_STATUS_FAILED
2018-03-06 19:59:17.941 Detail, Removing current message
2018-03-06 19:59:17.941 Detail, contrlr, Queuing (Command) Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4
2018-03-06 19:59:17.942 Detail, Notification: ControllerCommand - Failed
2018-03-06 19:59:17.942 Detail,
2018-03-06 19:59:17.942 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x4a) - Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4
2018-03-06 19:59:17.995 Detail, contrlr,   Received: 0x01, 0x07, 0x00, 0x4a, 0xc6, 0x06, 0x00, 0x00, 0x72
2018-03-06 19:59:17.995 Detail,
14

I recently bought one too and I was able to add it, but I wasn’t able to control the brightness nor color. And at one point, HA reported it dead and couldn’t turn it on. Using the mechanical switch, it would light up briefly (orange) the turn off. Finally had to shut down and use the stick to un-pair it…I just kept on switching the light until the stick registered that it was unpaired. Then, I paired it up again and it’s now working fine (Monoprice Z-Wave RGB Light bulb ( Hank HKZW-RGB01 RGB ))

1 Like
15

I finally got it working. Had to unenroll with the stick, enroll with stick (now HASS though it was a light but not RGB) so unenrolled via HASS and reenrolled via HASS now it’s working fine as an RGB bulb.

16

I just bought the same bulb and I’m having similar issues. I’ve paird and repaired it a few times both with the Aotech stick and software. When I pair with the software, it shows up right, and has RGB color wheel controls, but changing the color won’t work. I can turn the bulb on, off, and dim, but no color change. Any help would be greatly appreciated.

17

I want to say I had this issue as well, and moving a zwave repeater in-between allowed it to see the color options.

18

How do you mean? Was the bulb far from the hub and so a repeater helped the signal? If that’s the case then this won’t work for me. My bulb is about 6ft away from the signal. Or did the repeater just help the bulb figure out the commands? I’m so confused by this. The color wheel shows up, and the states page shows the correct values for the selected colors. ie: Red selected shows 255, 0, 0. But the bulb stubbornly stays white!

19

For anyone having trouble with the Monoprice RGB bulb in the future. I figured out what my problem was. I was looking at the properties on the entity_id and found the parameter “white_value” was set to 255. I decided to set that to 0 in one of my automations, and BAM! now I can get colors both by the UI or mobile app, and through automations! Cheers.

action:
  service: light.turn_on
  data:
    rgb_color: [255, 0, 0]
    white_value: '0'
    entity_id: {your entity_id}
1 Like
20

@thefarelkid Wanted to stop in and say thanks. This worked.