Closed Marc-Berg closed 10 months ago
In case it hasn't become clear yet: I still can't see any restrictions, only the error messages.
It seems that it also affects other adapters, which you can see IF you switch off the filter. This needs further investigation by me.
I don't even know where the empty object!
text is generated. The node-red adapter doesn't contain that text. Maybe that is raised by the js-controller? Let me know if you have further information.
if this happens then an object exists in the database but without any content ... this should never happen normally
an object exists in the database but without any content
Empty means "completely empty"? Like {}
? Without any id or any other attributes?
How is it even possible to store such an object
as you see in your copied code it checks for falsy after JSON parse ... and JSON parse must have been successfull on the value in DB
I added some debug output (thanks @klein0r for the matching lines of code), but was not able to identify the problematic objects. So I converted my objects and states database from redis to jsonl and back, the errors are now gone. My assumption now is that after updating the Node-Red Adapter to version 5.0.0 the errors were caused by the initially missing credentials. Probably also due to a lack of error handling on my part in NodeRed. Thank you very much for looking into this.
Each time the instance is started, the error message "empty object!" appears three times without any reference as to where the message could have come from. The errors also appear when all flows are deactivated. I have already done this:
Any tips on how I could get closer to the cause?
js-controller: 5.0.16 Node.js: 18.18.2 Buanet Docker Image 9.0.1 Adapter Version 5.0.0