search

openhab / org.openhab.binding.zwave

openHAB binding for Z-Wave
Eclipse Public License 2.0
170 stars 202 forks source link

WARN log: TODO: Implement Application Update Request Handling of New ID Assigned (64) #1889

Open lolodomo opened 9 months ago

lolodomo commented 9 months ago

Many warnings of this kind are now in my logs. They are produced by the zwave binding, I believe. What does they mean ? And what to do ?

2023-09-19 18:06:29.709 [WARN ] [essage.ApplicationUpdateMessageClass] - TODO: Implement Application Update Request Handling of New ID Assigned (64).
2023-09-19 18:32:04.708 [WARN ] [essage.ApplicationUpdateMessageClass] - TODO: Implement Application Update Request Handling of New ID Assigned (64).
2023-09-19 18:32:07.020 [WARN ] [essage.ApplicationUpdateMessageClass] - TODO: Implement Application Update Request Handling of New ID Assigned (64).
2023-09-19 18:32:14.206 [WARN ] [essage.ApplicationUpdateMessageClass] - TODO: Implement Application Update Request Handling of New ID Assigned (64).
2023-09-19 20:05:27.500 [WARN ] [essage.ApplicationUpdateMessageClass] - TODO: Implement Application Update Request Handling of New ID Assigned (64).
2023-09-19 20:32:33.461 [WARN ] [essage.ApplicationUpdateMessageClass] - TODO: Implement Application Update Request Handling of New ID Assigned (64).
2023-09-19 20:32:34.819 [WARN ] [essage.ApplicationUpdateMessageClass] - TODO: Implement Application Update Request Handling of New ID Assigned (64).
2023-09-19 20:32:35.444 [WARN ] [essage.ApplicationUpdateMessageClass] - TODO: Implement Application Update Request Handling of New ID Assigned (64).

It is with OH 4.1 M1.

lolodomo commented 8 months ago

Any feedback ?

kamakazie2 commented 5 months ago

Upgraded from Oh 4.0.2 to 4.1.1 and am now getting a few hundred of these a day.

2024-01-11 12:51:02.641 [WARN ] [essage.ApplicationUpdateMessageClass] - TODO: Implement Application Update Request Handling of New ID Assigned (64).

UPDATE: I found a dead node that was dead before the upgrade but started throwing this code after the upgrade.. i deleted the dead node and all is well.