Description Text Logging

🛎️ Get Help Devices
1

This is just a curiosity question, but wondering why on vs off is different in the logging. Here is what I see.

Virtual Switch turned on
Virtual Switch turned off
Virtual Switch is off

As you can see there is no logging that says Virtual Switch is on like the off one. I don't need it, but wondering why the difference.

1 Like
2

Are you sure? Try turning it on when it's already on.

You'll get "was turned" when there is a command that results in a state change, i.e., event. You'll get "is" when a command is sent that isn't a state change, where the event is filtered out by default. (This can vary from driver to driver, but it's how this one works.)

3

Not sure I understand what you are saying, but it is difinitely different for on vs off. Here is the actual logging from this morning. It doesn't really make any difference to me I was just curious as to why.

dev:29902025-10-08 09:23:01.578 AMinfoJim Apple Presence was turned on
dev:29902025-10-08 08:53:32.994 AMinfoJim Apple Presence is off
dev:29902025-10-08 08:53:29.023 AMinfoJim Apple Presence was turned off
dev:29902025-10-08 08:52:15.250 AMinfoJim Apple Presence was turned on
dev:29902025-10-08 08:50:51.815 AMinfoJim Apple Presence is off
dev:29902025-10-08 08:50:48.090 AMinfoJim Apple Presence was turned off
dev:29902025-10-07 04:50:29.468 PMinfoJim Apple Presence was turned on
dev:29902025-10-07 04:15:31.911 PMinfoJim Apple Presence is off
dev:29902025-10-07 04:15:27.969 PMinfoJim Apple Presence was turned off
4

I mean that there are no gaps in this pattern, contrary to the claim, and that you will see what you are missing if you do as I suggested and:

As I noted:

And you can see that in my logs when I do exactly that. Each of these was generated after a command was issued, starting with the switch off:

dev:100 2025-10-08 12:51:36.621 PM info TEST Switch 1 is off
dev:100 2025-10-08 12:51:35.489 PM info TEST Switch 1 was turned off
dev:100 2025-10-08 12:51:34.229 PM info TEST Switch 1 is on
dev:100 2025-10-08 12:51:32.827 PM info TEST Switch 1 was turned on

Note as I mentioned above that this is not a general pattern, just the way this particular driver (and perhaps some other virtual ones; I didn't dig) works.

5

I understand what you are saying, but to get the ‘is’ it would not be a state change. Or in my case the on command coming twice, once to turn it on then another after already on. But that’s not happening with what I am doing. But no matter, I understand what you meant.

6

I demonstrated the behavior above using the built-in "Virtual Switch" driver in the specified states. Are you talking about a different driver? (If you have instant auto-off enabled, note that it would need to be disabled to see a manual "Off" as a state change, or it's likely to get there before you.)