Home Assistant interpretation of ramp to zero?

Have any HA users encountered this scenario?

I decided to try out HA and have installed the cbus2mqtt add-on that uses cmqttd and run with default HA MQTT Discovery.
All C-Bus light GA’s appear in HA and all is good, until ...

The question comes about when a GA is already off, then ramped to OFF again within C-Bus, e.g. in a Goodbye Scene.
All lights in the scene then turn on in HA...

Using MQTT Explorer you can see that when C-Bus issues the command ramp to zero it results in cmqttd updating "homeassistant/light/cbus_10/state" with "{"state": "ON", "brightness": 0, "transition": 8, "cbus_source_addr": 54}"
In HA this changes the light to ON, at the previous retain level.
There is no cmqttd update to ".../set" and the binary sensor in HA stays OFF.

Since this has been around for a while I wondered how other people handled it.
Maybe it has something to do with the default HA Discovery and I should try a lights.yaml configuration?

 

Never mind, appears to be a bug in libcbus.

 

I run cbus2mqtt in a docker and I did the following to send the correct state value:

1. Enter the docker shell ("docker exec -it $(docker ps -f name=cbus2mqtt -q) bash") and edit cmqttd.py.
2. Find and edit the function below and change values in bold.

def lighting_group_ramp(self, source_addr: Optional[int], group_addr: int, duration: int, level: int):

"""Relays a lighting-ramp event from CBus to MQTT."""
state = 'ON if level > 0 else 'OFF'
self.publish(state_topic(group_addr), {

'state': state,
'brightness': level,
'transition': duration,
'cbus_source_addr': source_addr,​

})
self.publish_binary_sensor(group_addr, level > 0)​

 

Thanks @Ingo that will fix it.