Patrick Winnertz

Here we go: First again the stacktrace: ``` TypeError: Cannot read properties of undefined (reading 'data') at EcovacsMQTT_JSON.handleMessage (/data/node_modules/ecovacs-deebot/library/950type/ecovacsMQTT_JSON.js:94:32) at MqttClient. (/data/node_modules/ecovacs-deebot/library/ecovacsMQTT.js:73:18) at MqttClient.emit (node:events:527:28) at MqttClient._handlePublish (/data/node_modules/mqtt/lib/client.js:1547:12) at MqttClient._handlePacket...

The output ist from the second console.error statement within the catch. The stack trace is from the first console.error Statement.

 This is the screenshot of the Deebot node which is causing that crash. So I just use it as input - till now I've never send a command to...

So after several days of running: It doesn't crash nodered anymore. However I see on a irregular basis these stacktraces in the error log: ``` [rgkiz ](http://localhost:2888/#/tasks/rgkizirt65zwvfn95z9low2af?log=1) TypeError: Cannot read...

Any news on this? There is a manual work around, however it would be cool to do this automatically

After playing a little bit with node-red & influxdb I get now this (slightly different) error: 

Any news on that? That's really a showstopper right now

I would second SpaceRichard. I've a lot of Roof Windows on a 45° Roof which could be closed depending on the angle of the sun in the sky. Just the...

I'll upload the new version to Debian within the next few days. Thanks for your fast response!