Koenkk / zigbee2mqtt

Zigbee šŸ to MQTT bridge šŸŒ‰, get rid of your proprietary Zigbee bridges šŸ”Ø
https://www.zigbee2mqtt.io
GNU General Public License v3.0
11.56k stars 1.63k forks source link

Bosch BMCT-SLZ Light/shutter control unit II: Failed to set Device mode (Status 'UNSUPPORTED_ATTRIBUTE') #22185

Open nice-tnetennba opened 3 months ago

nice-tnetennba commented 3 months ago

What happened?

After correctly pairing the device with Z2M (using the Home Assistant add-on gui), I'm trying to set the Device mode option in device properties > Expose, but I get an error: Publish 'set' 'device_mode' to 'Bosch' failed: 'Error: ZCL command Bosch/1 manuSpecificBosch10.write({"deviceMode":4}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":4403,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Status 'UNSUPPORTED_ATTRIBUTE')'

I also tried publishing {"device_mode": "light"} to zigbee2mqtt/FRIENDLY_NAME/set via HA development tools, as well as the MQTT Explorer app - with no result.

What did you expect to happen?

No response

How to reproduce it (minimal and precise)

Home Assistant > Zigbee2MQTT Add-on > click on the friendly name of the device > Expose tab > click on the "refresh" blue button next to Device mode.

Zigbee2MQTT version

1.36.1

Adapter firmware version

6.5.0.0 build 188

Adapter

EZSP v7

Setup

Add-on on Home Assistant, Virtual Machine

Debug log

No response

sopelt commented 3 months ago

Hi @tetemba ... I seem to be facing the same issue... 7 instances of BMCT-SLZ that no longer accept any changes to the mode or calibration settings citing UNSUPPORTED_ATTRIBUTE. I know that I set them up with 1.36.0 and calibrated them a few days later... then upgraded to 1.36.1 so it might be a regression between those two versions. Do you have an easy way to see if 1.36.0 works as expected? I probably won't be able to reproduce that right this moment ...

nice-tnetennba commented 3 months ago

Hi @sopelt and thank you for the advice. I restored the Z2M version 1.36.0 from backup and the problem does not occur - I can change the device mode option in the gui - so the problem is with Z2H version 1.36.1.

sopelt commented 2 months ago

@nice-tnetennba ... you don't happen to know if 1.37.0 works as expected? ;)