Node-RED Loxone & Miniserver Gen2 - (node-red-contrib-loxone 0.10.11) Broken ?

[Dave Charman]

Anyone else here using Node Red & Loxone with the node-red-contrib-loxone 0.10.11 ?

I use it personally at home with a Gen1 miniserver and it works 100% on the latest firmware.

Have tried today to get it to work with a Gen2 miniserver but it seems to crash NodeRED constantly

it connects momentarily an pulls the structure but then crashes once deployed

Have tried disabling HTTPS on the miniserver but still does not work.

The error message I get in Node Red is:


22 Dec 18:15:57 - [error] [loxone-miniserver:4da419b127d99a15] Miniserver connec tion error: Socket Error: undefined ERR_STREAM_WRITE_AFTER_END (1006)
Websocket Connection closed: 1006 Socket Error: undefined ERR_STREAM_WRITE_AFTE R_END
22 Dec 18:15:57 - [info] [loxone-miniserver:4da419b127d99a15] connection closed: Socket Error: undefined ERR_STREAM_WRITE_AFTER_END (1006)
22 Dec 18:15:57 - [info] [loxone-miniserver:4da419b127d99a15] connection closed: reconnecting
22 Dec 18:15:57 - [red] Uncaught Exception:
22 Dec 18:15:57 - [error] TypeError: Cannot read property 'closeDescription' of undefined
at Connection.<anonymous> (/home/pi/.node-red/node_modules/node-lox-ws-api/l ib/Connection.js:64:62)
at WebSocketClient.emit (events.js:400:28)
at ClientRequest.handleRequestError (/home/pi/.node-red/node_modules/websock et/lib/WebSocketClient.js:227:14)
at ClientRequest.emit (events.js:400:28)
at Socket.socketErrorListener (_http_client.js:475:9)
at Socket.emit (events.js:400:28)
at emitErrorNT (internal/streams/destroy.js:106:8)
at emitErrorCloseNT (internal/streams/destroy.js:74:3)
at processTicksAndRejections (internal/process/task_queues.js:82:21)

Anyone know of any work arounds to get it working ????

[13az13]

Hi,
this fork of the repository works for me on Gen2. The author of this has also forked a version of node-lox-ws-api with updates that are used in the below package.

give it a whirl and hopefully it sorts your issues on a gen2 too.

https://github.com/arsiesis/node-red-contrib-loxone

Aaron

[Dave Charman]

Thanks Aaron !

Is this the same fork that is added when adding node-red-contrib-loxone 0.10.11from the pallete manager within node red ?

Or do I have to install another way ?

Must admit I'm not totally familiar with how GitHub works...

Thanks ;-)

[13az13]

It’s not unfortunately, it’s. Fork of that published node that someone’s updated.

if you run this from the command line of the machine you have node-red installed on (assuming Linux based) it should do the trick for you.

In your userDir (~/.node-red) run the following:

npm install arsiesis/node-red-contrib-loxone

THIS(!) should be highlighted somewhere, because now everything works. You just made my day, 13az13!

[Dave Charman]

Thanks again Aaron

I managed to get this working !!

Seems like the issue is down to the new Loxone user permissions on latest versions of config
and if permissions are not set correctly in Loxone, causes the NodeRED to constantly crash

I found this link:
https://githubmemory.com/repo/codmpm...sues/58?page=4

[13az13]

Happy days, glad it’s sorted. If I can help with anything else just shout. Cheers, Aaron

[pmayer]

I've merged arsiesis changes into the main repo of node-red-contrib-loxone and these are in 0.10.12.
Next time please file a Pull Reuqest or at least tag me as I can't check every fork for fixes of issues of the main repo.

Reminder that the change had to be done in node-lox-ws-api and in 0.10.12 only the dependency has changed.

Nevertheless, thanks for your work :-)

[maxw]

Da node-red-contrib-loxone mein absolutes Lieblings-Plugin ist, war ich mal wieder so frei einen Feature Wunsch zu hinterlassen.

https://github.com/codmpm/node-red-contrib-loxone/issues/70