I’ve been having some trouble with GoControl LB602. After searching the forums it looks like others have had the same problem and found a solution.
Hi all,
I’ve recently picked up some LB60Z-1 bulbs and I’m having some issues with HA recognizing when the light is off.
I’ve paired to my Z-stick just fine and it shows up and turns on/dims just fine, but when I flip it off through HA the light itself turns off, but HA thinks it’s still on unless I dim it a bit first.
[image]
( This is right after turning it off. the light is physically off.The toggle flips back on if I expand it or refresh the page)
In the log as soon as I flip it off fro…
However when I make the recommended changes to the configuration.yaml file it fails a validation check.
zwave:
usb_path: /dev/ttyACM0
network_key: "_**MY KEY**_"
customize:
light.office_light_level:
polling_intensity: 1
refresh_value: true
This is the error I am receiving when running a configuration validation
Failed config
zwave:
customize: None
light.office_light_level:
[source/config/configuration.yaml:73]
polling_intensity: 1
refresh_value: True
network_key: _**my key**_
usb_path: /dev/ttyACM0
General Errors:
- Setup failed for zwave: Invalid config.
I am running hass.io and the above posts predate hass.io if that changes anything.
Tinkerer
(aka DubhAd on GitHub)
December 31, 2017, 11:08am
2
There should be the actual error just above that piece you posted.
Also, you can enable polling through the control panel these days, so that might be easier.
kylerw
(Kylerw)
December 31, 2017, 2:37pm
3
What version are you on? customize is now device_config so if you are on a recent version you need to update that.
Yep that was it. Looked a bit further up the error log and I found:
2017-12-31 11:56:26 ERROR (MainThread) [homeassistant.config] Invalid config for [zwave]: [customize] is an invalid option for [zwave]. Check: zwave->zwave->customize. (See /config/configuration.yaml, line 69). Please check the docs at https://home-assistant.io/components/zwave/
Changing the line from customize: to device_config cleared the error.
Thanks for the insight.