Automation does not work on Panel Switch S100 relays

Developer Hub
,
1

I have several Panel Switch S100 and a S1E in my home which primarily is aqara based. I also have a M3 Hub controlling all my other aqara switches (H1 and Z1Pros) and lights (T1 and T2 bulbs).
I just discovered that automations to turn on/off relays on the S100 L1/L2/L3 do not work.

I am trying to create a 2-way switch to control lights connected to the upstairs S100 by the H1 switch (bound to the M3) downstairs. And even whent the automation is set correctly (tested via preview action), when clicking the switch, the S100 relay will not respond to the automation.

I tested to see if the problem is with M3, the H1 switch itself, or the S100 by adding another switch (Z1pro double soft click), and another light (connected to S1E) to the same automation. When I trigger via the H1 or the Z1Pro double click, the light connected to S1E turned on and off correctly, while the light connected to the S100 relay fails to do the same.

The strange thing is, when the automation is triggered thru the app (preview the automation), the S100 relay will respond correctly.

Also, if I bind the S100 relay light to a wireless switch on the S1E or a wireless switch on another S100, the light connected to the S100 will turn on/off correctly, but if I bind the wireless switch to an automation to turn on/off the S100 relay light, it will fail.

What can be the problem here?

1 Like
2

@mlaihk Thank you for your detailed description—this is exactly the kind of thorough troubleshooting that helps the community! Based on what you’ve shared, it sounds like you’ve methodically isolated the issue to automations involving the S100 relays, especially when triggered by other switches via the M3 hub, rather than direct app control or wireless switch bindings.

From the reference info, we know the Aqara Panel Switch S100 supports automation actions such as turning relays on/off, and these can be triggered by conditions like “Turn on/Turn off/Is on/Is off/Press the Wireless switch”. Direct bindings between wireless switches and the S100 seem to work, which matches your observation that direct wireless triggers are effective, but automations routed through the hub are not.

Given that the automations preview correctly (i.e., the relay responds via app), but fail when triggered by another switch or automation, this strongly suggests a potential issue with how automations are processed by the hub or with the communication between devices in automation scenarios, rather than a hardware fault in the S100 itself.

Here are a few things you might want to check or try:

  1. Network and Device Status: Ensure that all devices, especially the S100 and your M3 hub, are online and have up-to-date firmware. The S100 relies on both Wi-Fi and Zigbee, so a weak signal or a temporary network hiccup could cause missed automation triggers.
  2. Automation Compatibility: Double-check the automation logic and the supported triggers/actions for the S100. Sometimes, certain automation paths behave differently depending on whether they’re processed locally on the hub or via the cloud.
  3. Hub Processing: Since direct triggers work but automations do not, there could be a processing issue or a limitation in the hub’s firmware or the platform’s handling of multi-device automations.
  4. Device Binding vs Automation: You noted that wireless switch “binding” (likely direct Zigbee binding) works, but automations (which may be cloud or hub-processed) do not. This further points to a possible issue in automation relay via the hub.
  5. Test with Minimal Automation: Try creating a very simple automation: e.g., just one trigger (H1 switch) and one action (S100 relay). See if that works—sometimes complex automations or multiple device types can introduce bugs.

Unfortunately, the available reference information doesn’t provide a known solution for this exact scenario. It appears to be an edge case or possibly a firmware limitation or bug.

If you’ve already tried the above and the issue persists, I recommend reaching out to Aqara’s Customer Service Team for in-depth support, as this may require back-end log analysis or a firmware update. Please contact Customer Service Team by Aqara Home App (Profile>Help&Feedback>Customer Service) or scanning the QR code:

400Ă—400 9.45 KB
, which will be efficient; If no Aqara Home account, please click here to create a ticket. Sorry for the inconvenience, and thank you for helping the community pinpoint these issues—your feedback is invaluable!

If anyone else in the community has encountered and solved this, please jump in and share your experience!

3

I got a response and temporary solution from Aqara tech support. It is to REMOVE THE ZIGBEE BINDING to the M3 hub from the panel switch S100. And it worked.

From this I have a guess at what the actual issue is. The panel switch connects to the M3 hub as a Zigbee switch so that it can control other zigbee devices connected to the M3 hub if internet went down. It is quite possible that there is a bug in panel switch and M3 hub somewhere that the M3 thinks it can control the relays on the panel switch s100 via zigbee, and that the panel switch s100 is not firmware enabled to be controlled via zigbee.

So it is probably a software design issue of the devices. This makes binding the S100 to an M3 hub quite useless at the moment, as it breaks other switch triggered automation to control the relays on the S100.

4

Seeing same problem. Any automation that is trying to control the relay doesn’t work. My anutomation is simple, when there is no one in the room, it should turn off the relay for the fan. From the log, it shows that it failed to execute. Then I further tried to just create a scene, which the only operation of the scene is to turn off the fan. Clicking the play button doesn’t work, but pressing the preview button, it will turn off the fan successfully.

Unbinding M3 works. This is a firmware issue

1 Like