@chris There were multiple instances of APP BUSY in my older logs. All were from Leviton devices. That seems to be the common thread w.r.t. APP BUSY.
So much for my theory!
I wouldnāt throw it out yet. Looking closer, Iām only seeing 3 (same second) from one other device from 6 months agoā¦ and this is a spare Monoprice Plugin that I move around a lot. Iām saving them to a file to parse out all the nodes.
grep -r "2018" * | egrep "Receive Message = [0-9A-F][0-9A-F] [0-9A-F][0-9A-F] [0-9A-F][0-9A-F] [0-9A-F][0-9A-F] [0-9A-F][0-9A-F] [0-9A-F][0-9A-F] [0-9A-F][0-9A-F] 22 01 00" > /opt/openhab2-backup/appBusy.txt
Do you keep all your old logs? Do you keep them all in userdata/logs
, or do you rotate them off to another directory? If the latter, would you mind sharing how you do that?
I use a script for upgrading that first saves a full backup. Itās a lot of data, so at times I go through and manually pull out some things, including logs, and delete the rest. So itās a mix. I have a task to write a script to clean up the old archives somewhere in my backlog. But rotating them off to another directory is a good ideaā¦
I have a NAS thatās shared between 2 locations that are connected via an IPSEC tunnel. Iād like to rotate the logs off to the NAS so I have them all in one place for analysis. Just havenāt gotten around to trying to figure out how to do it.
Please let me know if you have any hints about the āInvalid cross-device linkā error.
That sounds to me as though log4j is using a hardlink when rolling over a log for which the appenderās filePattern is set to a destination on a different partition from the log file.
Further analysis of my logs shows that all of the devices I have of this type also get APP BUSY, but nowhere near as regularly all of my Leviton devices. 791 total since the beginning of the year. Sorting all of the logs entries with APP BUSY by time does not show any pattern (daily heals, reboots, etc.), other than it looks like this happens continuously. I donāt always have logging in DEBUG, so there are gaps in time.
Since the last update, I have only seen two APP BUSY in my logs.
Power reset and updated binding didnāt help (had to return early because of storm)
Unfortunately Iām not sure what else to do. Both the old, and the new binding seem to be working the same with respect to the polling here. Maybe thereās something else different with the configuration, although I canāt think what that could be that would affect this.
Are you able to provide the log from the old binding from just prior to the 06:57:56.668 log that you provided earlier? Iād like to see what the device sent, and when - I donāt think itās likely to really help, but at the moment itās the only unanswered question I have to confirm that the old and new bindings are doing the same thing.
Thanks. I donāt believe that this is impacted by the binding, but I donāt know what else does influence it. For sure itās seen with other systems as well (such as Vera)ā¦
āTry again laterā is a pretty useless message really - it would be nice to have defined what ālaterā meansā¦ Ho-humā¦
I was confused thenā¦ I thought thisā¦
ā¦was a potential remedy. BTW, Iām now at eight in less than 24 hours.
Has anyone seen this in their logs?
21:20:07.168 [WARN ] [nding.zwave.handler.ZWaveThingHandler] - NODE 10: Invalid item type defined (DecimalType). Assuming DecimalType
Yes, it was an attempt at reducing the issue, but as I have no idea what is causing the device to report that itās busy, and as other home automation systems are also seeing this (eg Vera - as per the link I posted earlier) I donāt think itās directly related to the binding.
If you have any other ideas, Iām happy to give them a try, but at the moment the dev binding is doing the same thing as the master binding, so I have no idea why this would be any different - sorry .
I suspect you are using an old binding. This error message was changed recently so please use a newer version.
223 ā Active ā 80 ā 2.4.0.201807071112 ā ZWave Binding
Yes, its a bit older. Will update ! Thankyou
Ok, here is full log. From OH start, check node 6 and 12. https://anonfile.com/ZfP5xff0b4/openhab.log
I donāt think this is the right logā¦
Well I just restored to OH 2.2 with working Z-wave binding, enabled debug, confirmed that leviton devices work and uploaded logs. Why it is not right ?
Sorry - so this is a NEW log, not the ones provided earlier?
I was expecting the one that you posted earlier, but if youāve posted a new one thatās fine as well.