I'm having similiar behaviour with my C8 pro since the last update. Some automation won't trigger or if triggered devices won't turn on or off.
Also zigbee devices are getting a command to change state but are not responding. It's looks like the zigbee network or radio is not working properly - this all started after the last update. Before the update everything worked flawlessly...
I don't know what to do... I am afraid to rollback (it can make the hub to work worse then now), I don't know if the next verion will fix something, I don't know if I need to do something with the zigbee radio (change frequency or similar)...
Can you show a matching event from your device some time after creating the rule? (Logs for the device have them by default, but the Events tab on the device detail page for the device is the authoritative source.)
The above doesn't show the switch turning on. You'd need "Events" from the switch instead for that. If if its turning on, you'll need to figure out what's doing that, but this tab on the switch would still be the best place to look.
Unless you changed the name of the app between your first post and this one, I also don't see the Basic Rule in question as being "triggered" (which doesn't necessarily mean it really did anything, just that it has a subscription to that event for one reason or another -- app logs are going to be the best clues after that).
I'm not sure what you mean with "default reaction." A device won't do anything you haven't configured it to do, whether by an app on your hub or some other means. A Basic Rule always makes you choose to turn on or off (or toggle) a device as part of an action if that's what you mean -- there's no "do something with a switch" action that doesn't make you specify what yo mean with it.
What app is "T_H-1control of SW/TR-9 for SrokaRack"? It's hard to know what disparate screenshots go with what log entries or other app screenshots without some context.
App logging, if enabled, will show you what Basic Rule is doing. If you don't see any log entries and have it enabled, something else must be going on, possibly another app.
I assumed so, but the question remains: is the same app you posted about originally? It is not clear because the name looks different in Logs, so either you changed it or are looking at a different one. Naturally, the latter is an important distinction for troubleshooting.
Your new screenshot is also of the parent Basic Rules app, not the particular Basic Rule you are troubleshooting. This information is not useful for troubleshooting, as everything you care about is going to pertain to the particular Basic Rule child app you created and possibly the device(s) involved as a "trigger" or action.
