Enbrighten zwave led bulbs

Configuration
1

I just got a enbrighten zwave led bulb. I can see when i adjust the level in the the gui that the brightness property is what changes. I’ve tried to format it several ways based on examples in the forums, etc.

this works to turn off

- alias: Turn off at xx:xxPM
  trigger:
  -  platform: time
      at: '22:38'
  action:
    service: homeassistant.turn_off
      entity_id: light.level

this shows the bulb on but the brightness is 0.

- alias: Turn on at xx:xxPM
  trigger:
  -  platform: time
      at: '22:38'
  action:
    service: homeassistant.turn_on
      entity_id: light.level

this gives me an errors like this
2017-09-18 22:57:59 ERROR (SyncWorker_3) [homeassistant.util.yaml] mapping values are not allowed here
in “/config/automations.yaml”, line 44, column 9
2017-09-18 22:57:59 ERROR (MainThread) [homeassistant.components.automation] mapping values are not allowed here
in “/config/automations.yaml”, line 44, column 9

- alias: Turn  at xx:xxPM
  trigger:
  -  platform: time
      at: '22:38'
  action:
    service: homeassistant.turn_on
    data:
      entity_id: light.level
      brightness: 25
2

I have not tested it, but I think that entity_id should be at the same level as data, not inside it:

- alias: Turn  at xx:xxPM
  trigger:
  -  platform: time
      at: '22:38'
  action:
    service: homeassistant.turn_on
    entity_id: light.level
    data:
      brightness: 25
3

You want to use light.turn_on if you want to control the brightness of a light. So it’s either:

- alias: Turn on at xx:xxPM
  trigger:
  -  platform: time
      at: '22:38'
  action:
    service: homeassistant.turn_on
    entity_id: light.level

or

- alias: Turn  at xx:xxPM
  trigger:
  -  platform: time
      at: '22:38'
  action:
    service: light.turn_on
    data:
      entity_id: light.level
      brightness: 25
4

I tried it that was and got the same result.

5

Are you sure the light is called light.level?

6

i can turn it off with light.level. when i call “homeassistant.turn_on” with the “entity_id: light.level” it shows as on in the web gui, but the brightness is 0. .there is not other light.anything.

7

this worked. service, entity_id and data need to be lined up.

  action:
    service: light.turn_on
    entity_id: light.level
    data:
      brightness: 25
8

Yes. A suggestion - get a good editor that enforces YAML formatting. It will save you a ton of time ;). I use ATOM, but others also work.

9

I’m having trouble with these bulbs too. Seems like there’s an issue with the timing of turning them on/off which makes Home Assistant think they are still on when off, and vice versa. Refreshing the entity eventually works, but there’s kind of a weird flip flopping that happens to the state.

Here’s the logs from OZWave:

2017-09-20 22:49:39.841 Info, Node004, Value::Set - COMMAND_CLASS_SWITCH_MULTILEVEL - Bulb - 0 - 1 - 
2017-09-20 22:49:39.842 Info, Node004, SwitchMultilevel::Set - Setting to level 0
2017-09-20 22:49:39.842 Detail, Node004, Queuing (Send) SwitchMultilevelCmd_Set (Node=4): 0x01, 0x0a, 0x00, 0x13, 0x04, 0x03, 0x26, 0x01, 0x00, 0x25, 0x20, 0xc3
2017-09-20 22:49:39.842 Detail, Node004, Queuing (Send) SwitchMultilevelCmd_Get (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x26, 0x02, 0x25, 0x21, 0xc3
...
2017-09-20 22:49:39.887 Info, Node004, Request RTT 43 Average Request RTT 47
...
2017-09-20 22:49:39.955 Info, Node004, Request RTT 66 Average Request RTT 56
...
2017-09-20 22:49:40.066 Detail, Node004, Refreshed Value: old value=99, new value=98, type=byte
...
2017-09-20 22:49:40.847 Info, mgr,     Refreshing node 4: COMMAND_CLASS_SWITCH_MULTILEVEL index = 0 instance = 1 (to confirm a reported change)
...
2017-09-20 22:49:40.966 Info, Node004, Response RTT 118 Average Response RTT 135
2017-09-20 22:49:40.966 Info, Node004, Received SwitchMultiLevel report: level=66
...

Is there a cleaner solution to this problem that doesn’t result in the switch flipflopping?

10

They work fine for me, without anything odd. I am using a Aeon Zwave stick 5 on a rpi3.

11

Hmm, maybe it’s just me. I’m using the Razberry daughter card on a Raspberry Pi 2B.

12

Actually I found this github issue that seems to be related.

https://github.com/home-assistant/home-assistant/issues/7937

And there might be a workaround coming.

13

I played around and got it to do something weird.

From off to on is fine; but from on to off sometimes the light goes off but the GUI element stays on for up to 5 minutes or so after. I do not have polling on these devices so not sure why the lag on the GUI element. It seems like it could be related to what you point out in those GitHub tickets.