sgraystar

hi jishi, very handy api. I also see this issue when using sayall with my doorbell, if the visitor presses the doorbell button more than once the the sonos system...

@jishi Would it be practical to implement a lock per action? In my scenario a lock on Sayall would ensure that any duplicate doorbell keypress would be ignored until the...

@jishi I am still thinking about this, lots of people press the doorbell more than once!! I have submitted a pull request to restrict/allow concurrent clipall/sayall actions. Cheers

The dimmer led matches the indoor light, on during the ramp then off. Using MQTT Explorer you can see that when C-Bus issues the ramp to zero command it results...

This the wanted end state, so switching off without a ramp also reports brightness 0, {"state": "OFF", "brightness": 0, "transition": 0, "cbus_source_addr": 54}

Agreed. The debug log shows HA ignores the invalid brightness, and continues with the ON. > 2023-07-19 08:49:21.254 DEBUG (MainThread) [homeassistant.components.mqtt.client] Received message on homeassistant/light/cbus_10/state (qos=0): b'{"state": "ON", "brightness": 0,...

Hi Jason. Starting with the simplest config: ` { "type": "light", "application": 203, "id": 0, "name": "AC Power", "enabled": true }` This generates the error above for 'Method ramp not...

Config: ` { "type": "switch", "application": 203, "id": 0, "name": "AC Power", "enabled": true }` Error: `2020-09-02T02:16:24.031Z cbus:client sent command '[136] off //DENDY4/254/203/0' 2020-09-02T02:16:24.032Z cbus:client rx response { commandId: 136,...

No worries, it is a simple change for me. Cheers

If nobody has noticed until now I would not rush to implement something just for this case. Maybe a symptom of how widely EC is actually used.