stfnhmplr / node-red-contrib-homee

access the homee api with node-red
37 stars 8 forks source link

NodeRed crashes since update to v1.3.2 - log shows problem with homee plugin probably #21

Closed medicus07 closed 3 years ago

medicus07 commented 3 years ago

Hi Stefan,

yesterday I tried to update to the actual version of NR coming from v1.0.2. I'm using NR in a Synology docker. Since the update, NR crashes directly in the start process...

In the Log there seems to be a problem with your homee plugin:

`

2021-04-18 06:49:22 stdout npm ERR! Exit status 1
2021-04-18 06:49:22 stdout npm ERR! node-red-docker@1.3.2 start: node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"
2021-04-18 06:49:22 stdout npm ERR! errno 1
2021-04-18 06:49:22 stdout npm ERR! code ELIFECYCLE
2021-04-18 06:49:22 stdout at process._tickCallback (internal/process/next_tick.js:63:19)
2021-04-18 06:49:22 stdout at state.handle.lookup (dgram.js:249:7)
2021-04-18 06:49:22 stdout at startListening (dgram.js:128:10)
2021-04-18 06:49:22 stdout at Socket.EventEmitter.emit (domain.js:448:20)
2021-04-18 06:49:22 stdout at Socket.emit (events.js:198:13)
2021-04-18 06:49:22 stdout at Socket.server.on (/data/node_modules/node-red-contrib-homee/lib/discovery.js:29:5)
2021-04-18 06:49:22 stdout at Node.debug (/usr/src/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:532:5)
2021-04-18 06:49:22 stdout at log_helper (/usr/src/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:496:16)
2021-04-18 06:49:22 stdout 18 Apr 06:49:22 - TypeError: Cannot read property 'log' of undefined

` My version of node-red-contrib-homee is 0.8.1.

I attached the full log under this issue.

Can you please look into this. I went back to my backup version.

Thank a lot. Michael nodered-node-redTest.html.zip

Bildschirmfoto 2021-04-18 um 08 37 48
medicus07 commented 3 years ago

I did some tests with a new NR test docker...

So it seems, the problem is associated to the virtual homee configuration.

stfnhmplr commented 3 years ago

Thanks for reporting. With version 0.8.2 the bug should be fixed.