OZW: Can't use multiple light.turn_on service calls for the same light

[FuzzyMistborn]

The problem

I have a few automations where I turn the light on to a certain brightness, wait a period of time, and then increase/decrease it again. IE something like this:

    - service: light.turn_on
      data:
        entity_id: light.office
        transition: 15
        brightness_pct: 50
    - delay: '00:00:15'
    - service: light.turn_on
      data:
        entity_id: light.office
        transition: 15
        brightness_pct: 100

What happens is the first service call works but then the second doesn't take place. So the lights are stuck at 50% brightness. From watching MQTT it looks like the call is being made to OZW so I'm not 100% sure if this is a HASS thing or an OZW thing.

Environment

• Home Assistant Core release with the issue: 0.114.1
• Last working Home Assistant Core release (if known): N/A
• Operating environment (OS/Container/Supervised/Core): Container
• Integration causing this issue: OZW Beta
• Link to integration documentation on our website:

Problem-relevant configuration.yaml

None

Traceback/Error logs

None

Additional information

Switches are GE Dimmers.

[probot-home-assistant[bot]]

ozw documentation ozw source _{^{(message by IssueLinks)}}

[MartinHjelmare]

Please provide the MQTT logs and we can see where the issue is.

[FuzzyMistborn]

Weird. I ended up restarting MQTT, HASS and OZW just to get a fresh start on logs and everything is working as it should. Sorry about that.