search

bkorda / node-red-contrib-zway

GNU General Public License v3.0
5 stars 4 forks source link

Crash when z-zwave node not reachable ? #4

Closed Vinisz closed 4 years ago

Vinisz commented 4 years ago

Hi,

I see my docker container with node-red crashes sometimes. I think it is caused by the zway module, and most likely, when a device is not reachable. Here is the error from docker container, if you need more info, just let me know:

extractfromerrorlog.txt

bkorda commented 4 years ago

Thank you, will fix it.

Vinisz commented 4 years ago

Would be awesome, really like your work, thanks ! If you need more info, just let me know..

Greetings,

Vincent

Op 22 dec. 2019 om 18:48 heeft Bohdan Korda notifications@github.com het volgende geschreven:

 Thank you, will fix it.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

bkorda commented 4 years ago

Fixed in 0.2.1. Could you check please?

Vinisz commented 4 years ago

Ok, Installed… it’s now a matter of wait and see I guess…

Van: Bohdan Korda notifications@github.com Verzonden: zondag 22 december 2019 20:26 Aan: bkorda/node-red-contrib-zway node-red-contrib-zway@noreply.github.com CC: Vinisz vszabang@gmail.com; Author author@noreply.github.com Onderwerp: Re: [bkorda/node-red-contrib-zway] Crash when z-zwave node not reachable ? (#4)

Fixed in 0.2.1. Could you check please?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bkorda/node-red-contrib-zway/issues/4?email_source=notifications&email_token=AL2YLJGKWBRTHQTEJQZIZFTQZ65MVA5CNFSM4J6CTE5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHPYEMQ#issuecomment-568295986 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AL2YLJAQCOJ6275ASSYYMS3QZ65MVANCNFSM4J6CTE5A . https://github.com/notifications/beacon/AL2YLJCWFUB4YRA3F34FIBTQZ65MVA5CNFSM4J6CTE5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHPYEMQ.gif

Vinisz commented 4 years ago

Sorry, still the same happened just a couple of minutes ago:

Van: Bohdan Korda notifications@github.com Verzonden: zondag 22 december 2019 20:26 Aan: bkorda/node-red-contrib-zway node-red-contrib-zway@noreply.github.com CC: Vinisz vszabang@gmail.com; Author author@noreply.github.com Onderwerp: Re: [bkorda/node-red-contrib-zway] Crash when z-zwave node not reachable ? (#4)

Fixed in 0.2.1. Could you check please?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bkorda/node-red-contrib-zway/issues/4?email_source=notifications&email_token=AL2YLJGKWBRTHQTEJQZIZFTQZ65MVA5CNFSM4J6CTE5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHPYEMQ#issuecomment-568295986 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AL2YLJAQCOJ6275ASSYYMS3QZ65MVANCNFSM4J6CTE5A . https://github.com/notifications/beacon/AL2YLJCWFUB4YRA3F34FIBTQZ65MVA5CNFSM4J6CTE5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHPYEMQ.gif

bkorda commented 4 years ago

Could you send me logs?

Vinisz commented 4 years ago

Sure

Van: Bohdan Korda notifications@github.com Verzonden: maandag 23 december 2019 13:25 Aan: bkorda/node-red-contrib-zway node-red-contrib-zway@noreply.github.com CC: Vinisz vszabang@gmail.com; Author author@noreply.github.com Onderwerp: Re: [bkorda/node-red-contrib-zway] Crash when z-zwave node not reachable ? (#4)

Could you send me logs?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bkorda/node-red-contrib-zway/issues/4?email_source=notifications&email_token=AL2YLJCEB6DNG7JZ3QSS2G3Q2CU2ZA5CNFSM4J6CTE5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHRATGA#issuecomment-568461720 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AL2YLJGSTLKWLDZWIMQTSRTQ2CU2ZANCNFSM4J6CTE5A . https://github.com/notifications/beacon/AL2YLJESKXQAECMMFF73XLDQ2CU2ZA5CNFSM4J6CTE5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHRATGA.gif

23 Dec 12:57:44 - [info] Starting modified nodes 23 Dec 12:57:44 - [info] Started modified nodes ERROR: cant get fcc1356.2bf72c8 node, removed from list 23 Dec 12:57:48 - [red] Uncaught Exception: 23 Dec 12:57:48 - TypeError: Cannot read property 'devices' of null at ServerNode.onSocketMessage (/data/node_modules/node-red-contrib-zway/nodes/server.js:209:37) at ZWaySocket.ServerNode.node.socket.on (/data/node_modules/node-red-contrib-zway/nodes/server.js:34:57) at ZWaySocket.emit (events.js:198:13) at ZWaySocket.onMessage (/data/node_modules/node-red-contrib-zway/lib/zway-socket.js:140:18) at WebSocket.socket.on.data (/data/node_modules/node-red-contrib-zway/lib/zway-socket.js:60:48) at WebSocket.emit (events.js:198:13) at Receiver.receiverOnMessage (/data/node_modules/node-red-contrib-zway/node_modules/ws/lib/websocket.js:800:20) at Receiver.emit (events.js:198:13) at Receiver.dataMessage (/data/node_modules/node-red-contrib-zway/node_modules/ws/lib/receiver.js:423:14) at Receiver.getData (/data/node_modules/node-red-contrib-zway/node_modules/ws/lib/receiver.js:353:17) at Receiver.startLoop (/data/node_modules/node-red-contrib-zway/node_modules/ws/lib/receiver.js:139:22) at Receiver._write (/data/node_modules/node-red-contrib-zway/node_modules/ws/lib/receiver.js:74:10) at doWrite (_stream_writable.js:415:12) at writeOrBuffer (_stream_writable.js:399:5) at Receiver.Writable.write (_stream_writable.js:299:11) at Socket.socketOnData (/data/node_modules/node-red-contrib-zway/node_modules/ws/lib/websocket.js:875:35) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! node-red-docker@1.0.3 start: node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data" npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the node-red-docker@1.0.3 start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /usr/src/node-red/.npm/_logs/2019-12-23T11_57_48_485Z-debug.log

node-red-docker@1.0.3 start /usr/src/node-red node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data" 23 Dec 12:58:09 - [info] Welcome to Node-RED

bkorda commented 4 years ago

It happens when z-way is down?

Vinisz commented 4 years ago

No, not down, it looks like it happens when it has trouble finding a z-wave node, but not 100% sure.

Op 23 dec. 2019 om 16:46 heeft Bohdan Korda notifications@github.com het volgende geschreven:

 It happens when z-way is down?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

bkorda commented 4 years ago

How can I reproduce this? You are the first one with this issue...

Vinisz commented 4 years ago

Well, let’s close the issue… I have never faced it again so no idea where it went wrong… Very stable platform now with Z-way and Node-red, very happy that you made these nodes available, thank you..

Greetings,

Vincent

Van: Bohdan Korda notifications@github.com Verzonden: vrijdag 10 januari 2020 09:33 Aan: bkorda/node-red-contrib-zway node-red-contrib-zway@noreply.github.com CC: Vinisz vszabang@gmail.com; Author author@noreply.github.com Onderwerp: Re: [bkorda/node-red-contrib-zway] Crash when z-zwave node not reachable ? (#4)

How can I reproduce this? You are the first one with this issue...

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bkorda/node-red-contrib-zway/issues/4?email_source=notifications&email_token=AL2YLJFSRARVSAOY3NKJYSDQ5AXC5A5CNFSM4J6CTE5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEITDETA#issuecomment-572928588 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AL2YLJEBGQK5ZYPE2MWZV3DQ5AXC5ANCNFSM4J6CTE5A . https://github.com/notifications/beacon/AL2YLJE2H2OZK7E62CMSFQ3Q5AXC5A5CNFSM4J6CTE5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEITDETA.gif

bkorda commented 4 years ago

I can include one more fixe and close the issue