Bosh BSIR-EZ: Cannot set alarm state

lieblinger commented 9 months ago

What happened?

It's not possible to set the alarm state and sensor values are not available (see screenshot):

Z2M Bosch

Publish 'set' 'alarm_state' to '0x003c84fffee61514' failed: 'Error: Cluster 'ssIasWd' has no command '240''

What did you expect to happen?

No response

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

1.34.0

Adapter firmware version

6.10.3.0 build 297

Adapter

SONOFF Zigbee 3.0 USB Dongle-E

Debug log

No response

johnsethwatkins commented 9 months ago

I have the same issue with a new Bosch siren paired today.

Identical situation to original poster. 1.34.0 z2m, Sonoff 3.0 stick, firmware 20210708.

Debug log: log.txt

ParalaXEngineering commented 9 months ago

Hello, I've to report the same issue. As a complement:

Setting the warning sound to "burglar" set the alarm on, putting it back to "stop" set the alarm off
Getting the power source doesn't work either (Publish 'get' 'power_source' to 'Rue Sirène' failed: 'Error: Unhandled key toZigbee.rbshoszbeu.convertGet power_source')

Also on 1.3.4, with home assistant and home assistant stick as coordinator

ParalaXEngineering commented 8 months ago

I tried again to pair it multiple times, on a repeater or a coordinator, with or without power supply but no luck.

Some stuff works, for instance I can set the siren sound to "burglar", which make some noise, but it is not really a possible workaround. Any news on this?

ParalaXEngineering commented 8 months ago

I confirm the issue is still there on the latest version 1.35...

johnsethwatkins commented 8 months ago

Yes, I agree, still not working

DS-B-BB-G commented 7 months ago

Hi, i got my new ordered Bosch Outdoor Siren BSIR-EZ today and followed the docu on Zigbee2mqtt about the device integration. ALso ensured to take the code behind the QR code.

I can confirm the issue is still existing and the Siren will not work and is currently not supported as written under supported devices on Z2M homepage.

Same issues as other mentioned here e.g. Alarm State not working

Additionally errors i can trigger by playing around with the different options in the Detail tab for this device:

Error: Publish 'set' 'alarm_state' to 'Bosch Outdoor Siren' failed: 'Error: Cluster 'ssIasWd' has no command '240''
Error: Publish 'get' 'power_source' to 'Bosch Outdoor Siren' failed: 'Error: Unhandled key toZigbee.rbshoszbeu.convertGet power_source'
Publish 'get' 'siren_volume' to 'Bosch Outdoor Siren' failed: 'Error: Read 0x003c84fffeedc36f/1 ssIasWd([40962], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":4617,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))'

My HA is up-to-date, my Zonoff Stick is up-to-date and the Z2M is up-to-date

Archimede2 commented 7 months ago

Hello everyone.

I am experiencing exactly the same issue. I have two different system based on Raspberry 4 there are almost the same appart the zigbee Dongle. In my first system I'm using a zzh! CC2652R Multiprotocol RF Stick from Tindie and everything is working well including the Bosch alarme. In my second system I'm using a brand new SONOFF ZigBee 3.0 USB Dongle Plus, TI CC2652P Coordinator but in this case I'm not able to use properly the Bosch Alarm. the both alarme have the same firmware. The strange thing is the state respond and the both system are not giving the same answer. In the first system (the good one) I got this: { "ac_status": true, "alarm": false, "battery": 100, "battery_low": false, "linkquality": 24, "restore_reports": true, "supervision_reports": false, "tamper": false, "test": false }

and in the second one (the bad one) I got this: { "battery": 71, "linkquality": 90, "power_source": "solar_panel", "siren_and_light": "only_light", "siren_volume": "high", "voltage": 3700 } So some information are not able to go the Sonoff dongle. I don't know why. I'm gone wait few weeks, maybe someone will find a solution. Otherwise the only solution will be to buy an other dongle. Thanks for the next answer and the next solution !!!!! I can't wait to read the next message. !!!

WEZANGO commented 7 months ago

Same issue here. I've got Sonoff CC2652P as well. Will try my Skyconeect and see if that works. @danieledwardgeorgehitchcock would you be able to look into this please if you've got some time?

ParalaX002 commented 7 months ago

For me the Sky Connect doesn’t work :( I’ve got the same symptoms as described before.

WEZANGO commented 7 months ago

Was this working on previous z2m versions?

johnsethwatkins commented 7 months ago

No. this was a new device added in the release 1.34 and did not work then.

Archimede2 commented 7 months ago

Was this working on previous z2m versions?

I do not know. My second system with the dongle sonoff is a new one.

IsThisACow commented 7 months ago

+1 Just updated to 1.35.1 to get it working. Sonoff Dongle with 6.10.3.0 build 297 Availability is Disabled. Don't have any idea how to change that. Errormessage is the same as @lieblinger has it.

Multipage commented 7 months ago

To get the error 240 fixed. I asked a question about this in this topic: https://github.com/Koenkk/zigbee2mqtt/issues/19274 And they've responded by creating an update on the cluster.ts : https://github.com/Koenkk/zigbee-herdsman/pull/900

I think this will be added in the release of next month. As i don't know how to add this to my HA Zigbee2mqtt instance we'll just have to wait for the update.

ParalaXEngineering commented 7 months ago

Hi,

This is working now, thanks a lot to all :) I can set the state of the alarm so this is very nice.

A detail remaining is that the status of the energy source is not working correctly now, with this error:

Publish 'get' 'power_source' to 'Rue Sirène' failed: 'Error: Unhandled key toZigbee.rbshoszbeu.convertGet power_source'

Strangely, also, it seems that the battery level is not updated automatically, but that setting the power source (which doesn't make sense because I'm only solar), is getting the battery level. Someone else know how to get reliably the battery level?

Chrunchy commented 4 months ago

Besides the battery status, should everything now be working? I can set sirene on and off, by setting alarm_state to on. But shouldnt there be a state to put the alarm into some active state, so the siren goes off if the tamperswitch is touched? (Tamper switch status is also null for me).

Running 1.36.1-1.

{ "alarm_state": "OFF", "battery": 55, "battery_low": true, "light_delay": 0, "light_duration": 7, "linkquality": 102, "siren_and_light": "siren_and_light", "siren_delay": 0, "siren_duration": 7, "siren_volume": "medium", "voltage": 3600, "ac_status": null, "power_source": "solar_panel", "tamper": null, "test": null }

In the debug log, i see these two entries when i touch the tamper switch, but can't see the difference though.

Tamperswitch OK. Zigbee2MQTT:debug 2024-04-13 13:02:12: Received Zigbee message from 'Sirene', type 'commandStatusChangeNotification', cluster 'ssIasZone', data '{"extendedstatus":0,"zonestatus":164}' from endpoint 1 with groupID 0 Zigbee2MQTT:debug 2024-04-13 13:02:12: No converter available for 'BSIR-EZ' with cluster 'ssIasZone' and type 'commandStatusChangeNotification' and data '{"extendedstatus":0,"zonestatus":164}'

Tamperswitch tampered (not touching wall): Zigbee2MQTT:debug 2024-04-13 13:02:16: Received Zigbee message from 'Sirene', type 'commandStatusChangeNotification', cluster 'ssIasZone', data '{"extendedstatus":0,"zonestatus":164}' from endpoint 1 with groupID 0 Zigbee2MQTT:debug 2024-04-13 13:02:16: No converter available for 'BSIR-EZ' with cluster 'ssIasZone' and type 'commandStatusChangeNotification' and data '{"extendedstatus":0,"zonestatus":164}'

Chrunchy commented 4 months ago

I tried creating an external converter trough Z2M - that results in the tamperswitch working and reporting its currect state - but then other stuff stops working. I guess this device isn't fully compatible with Z2M yet before some code update has been performed by someone with the right knowledge :)

Alepat62 commented 4 weeks ago

I tried creating an external converter trough Z2M - that results in the tamperswitch working and reporting its currect state - but then other stuff stops working. I guess this device isn't fully compatible with Z2M yet before some code update has been performed by someone with the right knowledge :)

I've got the same issue with "tamper": null, did you found a solution ?

Chrunchy commented 4 weeks ago

I tried creating an external converter trough Z2M - that results in the tamperswitch working and reporting its currect state - but then other stuff stops working. I guess this device isn't fully compatible with Z2M yet before some code update has been performed by someone with the right knowledge :)

I've got the same issue with "tamper": null, did you found a solution ?

Unfortunately no, i was hoping some of the many other bosch fixes would help on it, but not yet.

As mentioned tamper does work by generating and loading the custom converter, but then other switches stop.

Koenkk / zigbee2mqtt