No last update info found [Solved]

[EddyG]

I have switched to 2020.1 with dzVents version 3.0.1 Almost everything is working fine, but for some Zwave problems.
2 Dummy devices get updated via NodeRed and MQTT, and are updated normally.
Every now and then I get these errors.

Code: Select all

2020-03-28 09:49:59.186 Error: dzVents: Error: (3.0.1) Discarding device. No last update info found: {["deviceType"]="General", ["lastUpdate"]="", ["changed"]=true, ["baseType"]="device", ["name"]="MH-Z19B load", ["id"]=841, ["signalLevel"]=9386552, ["switchTypeValue"]=0, ["subType"]="Percentage", ["rawData"]={"19"}, ["protected"]=false, ["timedOut"]=false, ["data"]={["_nValue"]=0, ["hardwareID"]=474740, ["_state"]="19"}, ["deviceID"]="", ["batteryLevel"]=0, ["switchType"]="On/Off", ["description"]="", ["lastLevel"]=255}
2020-03-28 09:49:59.283 Error: dzVents: Error: (3.0.1) Discarding device. No last update info found: {["description"]="", ["id"]=840, ["subType"]="Voltcraft CO-20", ["switchTypeValue"]=0, ["deviceID"]="", ["deviceType"]="Air Quality", ["rawData"]={}, ["lastLevel"]=255, ["timedOut"]=false, ["protected"]=false, ["data"]={["_nValue"]=435, ["hardwareID"]=474740, ["_state"]="435"}, ["signalLevel"]=9386552, ["name"]="CO2 Woonkamer", ["batteryLevel"]=0, ["baseType"]="device", ["switchType"]="On/Off", ["changed"]=true, ["lastUpdate"]=""}

The last update info is in the database and updated everytime.
How can I prevent this error?

[waaren]

Every now and then I get these errors.

Code: Select all

2020-03-28 09:49:59.186 Error: dzVents: Error: (3.0.1) Discarding device. No last update info found

Not sure but my guess is that this is a timing issue. One thread is updating the record in the database and another thread sends data to the event system. Anyway too complicated for me to solve it but I might be able to create a work-around.
To do that I changed the logic in the generic device adapter that sends the error message in such a way that it creates a last update time for devices that do not have one but should. I am testing with it now and if I do not find unexpected side effects it will be in one of the next beta's

If you can help testing the work-around please send me a PM

[EddyG]

Tnx, for your offer. I had to go back to the latest stable 4.10717, because I could not get the Zwave problem fixed.
Now everything is working fine again, including Zwave.
2 days of lost work.