Was troubleshooting a problem (my error) in a rule and looking through the logs is so annoying in large part because of duplicate entries for actions.
Examples:
Device and device drivers:
Basement Pantry and Cabinet Room Lights = Generic Z-Wave Plus Scene Switch
Garage Lights = GE Enbrighten Z-Wave Smart Switch
Pantry Shelf Lights = Generic Z-Wave Smart Switch
All are Z-Wave, all are Jasco devices, but the drivers are different. Still tons of duplicate logs all the time. This has been going on for years and I have seen others post about it, but no real resolution. Is this normal? Is it something I'm doing wrong?
Everything is working by the way, it only makes scouring through logs difficult and I have to believe its s resource/storage waste too.
You can look at the Events tab on the devices. It will tell you what produced each of those multiple events. I don't think they are duplicate logs, they look like distinct events sent by the driver, as there are milliseconds between them. A "duplicate" log entry would have the same timestamps.
I have been seeing logs do that for a long while. I can't figure out why either. Device events show only one operation not the several shown in the logs.
Well, I don't understand. I just used Alexa to turn on the "Basement Hallway Lights" because I could watch and confirm that they turned on. I have a rule that fires off in this case that turns that light off in 10 minutes. I get multiple entries:
Interestingly in the middle the multiple entries my workshop lights were turned off by the "Manage Workshop Lights" app which is a child of "Room Lighting." When it send the off command because of 10 minutes of inactivity, that device reported off 4 times. I'm beginning to think that most of you do not think this is normal, though I'm not alone in seeing this behavior.
It should be noted that info messages (or any messages) in the live logs may not produce events, in particular multiple logs specifying the same state will not produce multiple events, only one event is produced when a given attribute changes value, you can see this by looking at the events tab for the device details, there will only be one entry.
The device itself is reporting multiple times for a given command, some drivers will not send info messages to the live logs unless the state changes, some will, this driver does, but in either case only one event is committed to the database, and therefore only one app trigger will be processed if anything is subscribing to this particular event.
Me too.
Is the bottom line that the multiple reports as noted in logs would not affect rules, only events? That this is just a cosmetic thing?
C8Pro, 2.4.4.155, ZWJS, retracted Z-Wave radio update, ZEN78 relay paired LR:
I suspect it is the device and not the hub that is showing the duplicates in the log. That is when the device is commanded to turn on/off, it is tgat device that is sending the on/off that you see in the log. I can’t say why, but I suspect this is more informational than a double command. Maybe your device doesn’t get an ACK fast enough? Just speculation.
