Hi
Has anyone else notice that the maxcube2 nodes are suddenly crippling nodered installations? I finally managed to get my rather extensive flows back up and running after finding maxcube, again to be the root cause. Below is my debug output, if anyone could shed any light on what on earth is going on, I'd be forever in their debt.

4 Jun 12:50:49 - [info] Starting flows
4 Jun 12:50:49 - [info] Started flows
4 Jun 12:50:49 - [red] Uncaught Exception:
4 Jun 12:50:49 - TypeError [ERR_INVALID_ARG_TYPE]: The first argument must be of type string or an instance of Bu ffer, ArrayBuffer, or Array or an Array-like Object. Received undefined
at Function.from (buffer.js:330:9)
at new Buffer (buffer.js:286:17)
at Object.parseCommandMetadata (/home/pi/.node-red/node_modules/maxcube/maxcube-commandparser.js:65:24)
at Object.parse (/home/pi/.node-red/node_modules/maxcube/maxcube-commandparser.js:19:35)
at MaxCubeLowLevel. (/home/pi/.node-red/node_modules/maxcube/maxcube.js:41:46)
at MaxCubeLowLevel.emit (events.js:314:20)
at /home/pi/.node-red/node_modules/maxcube/maxcube-lowlevel.js:39:14
at Array.forEach ()
at Socket. (/home/pi/.node-red/node_modules/maxcube/maxcube-lowlevel.js:35:16)
at Socket.emit (events.js:314:20)
at addChunk (_stream_readable.js:297:12)
at readableAddChunk (_stream_readable.js:272:9)
at Socket.Readable.push (_stream_readable.js:213:10)
at TCP.onStreamRead (internal/stream_base_commons.js:188:23)
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Failed with result 'exit-code'.
nodered.service: Service RestartSec=20s expired, scheduling restart.
nodered.service: Scheduled restart job, restart counter is at 11.
Stopped Node-RED graphical event wiring tool.
Started Node-RED graphical event wiring tool.
4 Jun 12:51:11 - [info]
Welcome to Node-RED

4 Jun 12:51:11 - [info] Node-RED version: v1.2.6
4 Jun 12:51:11 - [info] Node.js version: v12.20.1
4 Jun 12:51:11 - [info] Linux 5.10.11-v7l+ arm LE
4 Jun 12:51:11 - [info] Loading palette nodes
^Z
[1]+ Stopped node-red-start

• Remove "initialized"
• Add update callbacks with auto-connection

hi i see you changed the way of reading wall thermostat since commit b2a8555

the new way breaks my WM readings:

• setpoint 81 (should be 17)
• temp 2.2 (should be 27.8)

{ "rf_address": "18eb18", "initialized": true, "fromCmd": false, "error": false, "valid": true, "mode": "AUTO", "dst_active": true, "gateway_known": true, "panel_locked": false, "link_error": false, "battery_low": false, "valve": 4, "setpoint": 81, "temp": 2.2, "device_type": 3, "device_name": "Termostato a parete", "room_name": "Piano terra", "room_id": 1 }

worked fine with my patch (ivesdebruycker#25), but i see for some don't.

Did you switched to this new way of reading because my fix didn't work for you?

please take a look at the issue on maxcube page ivesdebruycker#27

If the cube doesn't answer (e.g. disconnected from network), commands just go straight into nirvana.
The command is send and the promise is created for receiving data, but if no data is received, the promise is never resolved and just hangs around indefinitely.

It would be nice to have a timeout option that rejects the promise (and maybe emits some sort or error event) after a while.
net.socket supports a timeout, so probably that can be used.

First of all - thanks for your work! I really appreciate it.

I'd like to read the current room temperature from an external sensor (not from the MAX!Wall-Thermostat)
and feed it to the heating thermostat. Is there any method to do so?

Thanks in advance for your help!

When setting vacation mode the devices show a number of the month-1, i.e.
2019-01-05 results in 05.00. in the display, 2019-02-05 results in 05.01. etc.

In maxcube-commandfactory.js I have replaced line 24 to fix it by:
var month_until = padLeft((momentDate.get('month')+1).toString(2), 4);

Hope this is the right place to fix it :-)

Querying the MAX!Cube gave me the correct results already.