SONOFF ORB 4in1 Easy Setup

[pricesswg]

Hi! I created this simple automation that allow the user to integrate all the 16 automation in a single file. The only requirements is that you have to manually select the action trigger that start the reading, and then all kind of automation is supported by the device.

Here is the link of the github page where is all described with usage examples: GitHub - Pricesswg/Sonoff-ORB-Home-Assistant-blueprint: A little blueprint to enable the user to connect 16 devices to a Sonoff ORB, completely open to be edited by adding even a small automation

Feel free to contact me if you need a help configuring it!

Here is the link for the video review (coming tomorrow 24/11):

[francisp (Francis)]

What Sonoff Orb ? ORB-RBS, ORB-ZBW1L, ORB-MW1, ORB-ZBRBS ?

[pricesswg]

It’s the new SNZB-01M, but if the other one use the same sensor entity as trigger (wich you can find it here: SONOFF SNZB-01M control via MQTT | Zigbee2MQTT) i think it could be retrocompatible

[Plouf34]

My SNZB-01M button is well integrated to Zigbee2mqtt, but no event is created. I can’t use the blueprint.

[Sir_Goodenough ((SG) WhatAreWeFixing.Today)]

The githuib where you got this from clearly says:

Ensure your integration exposes the action sensor as text states matching the names above.

You likely have Z2M in the wrong mode.

[Plouf34]

Thanks, but how I can change the good option in Z2M?

in Z2M:

in MQTT:

[pricesswg]

Hi, you should see an action button sensor as this one. This is the value that pass the button press state to your automation:

You need to insert it on the first value and then use it to read the button press state for the automation defined in the following field.

[Plouf34]

As you could see, I don’t have it and I don’t know how.

[Sir_Goodenough ((SG) WhatAreWeFixing.Today)]

In the Z2m Add-on go to the UI, settings, Home Assistant, then add the ones you need.

[xavier38300FR]

Hello guys,
i have the same probleme with my configuration ! impossible to have the action button in MQTT, but it was ok into Z2M !?
Can you help me ? please

[pricesswg]

As the previous post is explaining, you need to have the experimental event button flagged in your zigbee2mqtt (even if it’s not so experimental anymore…), otherwhise you can’t see the action button inside of home assistant.
I didn’ know why it was disabled, it’s used in many other kind of devices now. Basically now, devices exposes action as event, so every time you press a button it only update one single field with the correc tvalue, as it was much more easier to use button like this one.

[xavier38300FR]

Hi, and thank you for your help …
ok i have configured Z2M with your advises …

Now when i want to save the configuration, i have this message:

another idea ?

[xavier38300FR]

Hi,
Thanks for your work, but, your blueprint does’t work properly on Z2M with ORB firmware 1.0.4.
We have a message: mesage malformed … (cf capture) …

[pricesswg]

What model of ORB are you using? I’m testing with the 4 in 1 but it still working fine

[FoxLuffy]

Seems like you need to have atleast one action for every event. Seems it cant cope with a field being empty

[logikgear]

Note this worked before I updated
I recently updated Home Assistant to Core2026.4.4 and OS17.2. The blueprint seems to be doing something wrong or Home Assistant isn’t. When I push a button that should trigger an automation, it sees the button was pushed The Activity log for the orb shows the following:

SONOFF SNZB-01M (office) Attribute Updated event was fired with arguments: {'attribute_id': 0, 'attribute_name': 'on_off', 'attribute_value': 0, 'value': 0}

I have a button on a dashboard that fires the same automation, and it is working fine.
If I go into the automation that the blueprint created, I can manually click “Run Action,” and it triggers the automation.

[kvazis]

My review. I’m showing you how to set up direct binding in zigbee2mqtt - https://youtu.be/aMHplMRU8Dw

[logikgear]

I’m using ZHA not zigbee2mqtt

[pricesswg]

Could be how the entity is managed by Zha. The blueprint was made to connect via zigbee2mqtt, so maybe Zha have different attributes and it give this kind of error. I forgot to mention on the main post.

[logikgear]

That part that sucks is it worked until the recent update. any suggestion on what I could do. these are really cool and it has been nice having them around the house.