pimatic crashes on start-up

---

Hello everyone, since last night I have a problem with pimatic. The system starts up to a certain point and then crashes. This Pimatic runs on a RaspberryPi 3b. The problem came seemingly out of nowhere. I had neither installed anything nor made an update.
When starting, I get the following output. Unfortunately I can’t do anything with it. I hope someone can give me a solution.

08:59:49.689 [pimatic] An uncaught exception occurred: TypeError: Cannot read property 'bri' of undefined
08:59:49.689 [pimatic]>    at RaspBeeDimmer.parseEvent (/home/pi/pimatic-app/node_modules/pimatic-raspbee/raspbee.coffee:1058:10)
08:59:49.689 [pimatic]>    at RaspBeePlugin.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic-raspbee/raspbee.coffee:1043:12)
08:59:49.689 [pimatic]>    at emitOne (events.js:82:20)
08:59:49.689 [pimatic]>    at RaspBeePlugin.emit (events.js:169:7)
08:59:49.689 [pimatic]>    at RaspBeeConnection.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic-raspbee/raspbee.coffee:222:10)
08:59:49.689 [pimatic]>    at emitOne (events.js:77:13)
08:59:49.689 [pimatic]>    at RaspBeeConnection.emit (events.js:169:7)
08:59:49.689 [pimatic]>    at WebSocket.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic-raspbee/raspbee-connector.coffee:53:14)
08:59:49.689 [pimatic]>    at emitTwo (events.js:87:13)
08:59:49.689 [pimatic]>    at WebSocket.emit (events.js:172:7)
08:59:49.689 [pimatic]>    at Receiver.ontext (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/WebSocket.js:841:10)
08:59:49.689 [pimatic]>    at /home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/Receiver.js:536:18
08:59:49.689 [pimatic]>    at Receiver.applyExtensions (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/Receiver.js:371:5)
08:59:49.689 [pimatic]>    at /home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/Receiver.js:508:14
08:59:49.689 [pimatic]>    at Receiver.flush (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/Receiver.js:347:3)
08:59:49.689 [pimatic]>    at Receiver.opcodes.1.finish (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/Receiver.js:541:12)
08:59:49.689 [pimatic]>    at Receiver.expectHandler (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/Receiver.js:499:31)
08:59:49.689 [pimatic]>    at Receiver.add (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/Receiver.js:103:24)
08:59:49.689 [pimatic]>    at realHandler (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/WebSocket.js:825:20)
08:59:49.689 [pimatic]>    at firstHandler (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/WebSocket.js:815:7)
08:59:49.689 [pimatic]>    at nextTickCallbackWith0Args (node.js:436:9)
08:59:49.689 [pimatic]>    at process._tickCallback (node.js:365:13)
08:59:49.689 [pimatic]> This is most probably a bug in pimatic or in a module, please report it!
08:59:49.693 [pimatic] exiting...

It seems that I have localised the problem for now. It seems to be related to the RaspBee plugin. I have deleted the plugin from the config and the system is running again for now.
But why is there this problem all of a sudden? All the time pimatic was running with this plugin and now it suddenly causes problems? How can this be?

Hi, which raspbee version are you using and are you using a sd-card?

@thrusty said in pimatic crashes on start-up:

RaspberryPi 3b

I use RaspberryPi 3b and the system runs on a USB stick. Not on the SD card.

Are you using the latest pimatic-raspbee from treban?
I’m asking this because otherwise i can’t find the code lines of the error message

I use an older pimatic version on the Raspberry because the update always failed. The raspbee version is also older.
pimatic 0.9.47
raspbee 0.0.10

But it ran without crashing until yesterday. That is very strange.

And node version?

I assume you are using deconz with a conbee II stick.
Is that software/firmware updated recently?

The error can be handled by a small patch in the code.
Are you interested in that?

npm 2.15.11
node 4.6.2
conbee version 2.07.01 firmware 26300500
I use the first ConBee stick.

You did also a complete reboot?

The patch is in the file rapbee.coffee, line 1058
Change

1058      if data.state.bri?

into

1058      if data.state?.bri?

@bertreb said in pimatic crashes on start-up:

The error can be handled by a small patch in the code.
Are you interested in that?

Yes, of course! I would like to try it out.

@bertreb I will try it out and get back to you.
Thanks for now.

@bertreb
Unfortunately, that did not work.

13:00:30.140 [pimatic] An uncaught exception occurred: TypeError: Cannot read property 'on' of undefined
13:00:30.140 [pimatic]>    at RaspBeeDimmer.parseEvent (/home/pi/pimatic-app/node_modules/pimatic-raspbee/raspbee.coffee:1064:11)
13:00:30.140 [pimatic]>    at RaspBeePlugin.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic-raspbee/raspbee.coffee:1043:12)
13:00:30.140 [pimatic]>    at emitOne (events.js:82:20)
13:00:30.140 [pimatic]>    at RaspBeePlugin.emit (events.js:169:7)
13:00:30.140 [pimatic]>    at RaspBeeConnection.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic-raspbee/raspbee.coffee:222:10)
13:00:30.140 [pimatic]>    at emitOne (events.js:77:13)
13:00:30.140 [pimatic]>    at RaspBeeConnection.emit (events.js:169:7)
13:00:30.140 [pimatic]>    at WebSocket.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic-raspbee/raspbee-connector.coffee:53:14)
13:00:30.140 [pimatic]>    at emitTwo (events.js:87:13)
13:00:30.140 [pimatic]>    at WebSocket.emit (events.js:172:7)
13:00:30.140 [pimatic]>    at Receiver.ontext (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/WebSocket.js:841:10)
13:00:30.140 [pimatic]>    at /home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/Receiver.js:536:18
13:00:30.140 [pimatic]>    at Receiver.applyExtensions (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/Receiver.js:371:5)
13:00:30.140 [pimatic]>    at /home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/Receiver.js:508:14
13:00:30.140 [pimatic]>    at Receiver.flush (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/Receiver.js:347:3)
13:00:30.140 [pimatic]>    at Receiver.opcodes.1.finish (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/Receiver.js:541:12)
13:00:30.140 [pimatic]>    at Receiver.expectHandler (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/Receiver.js:499:31)
13:00:30.140 [pimatic]>    at Receiver.add (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/Receiver.js:103:24)
13:00:30.140 [pimatic]>    at realHandler (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/WebSocket.js:825:20)
13:00:30.140 [pimatic]>    at firstHandler (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/WebSocket.js:815:7)
13:00:30.140 [pimatic]>    at nextTickCallbackWith0Args (node.js:436:9)
13:00:30.140 [pimatic]>    at process._tickCallback (node.js:365:13)
13:00:30.140 [pimatic]> This is most probably a bug in pimatic or in a module, please report it!
13:00:30.143 [pimatic] exiting...

Yes thats the second patch

1064       if (data.state.on?)

into

1064       if (data.state?.on?)

And this could be the last patch, but a restart will tell if thats true

@bertreb Now I get a lot of other errors from the Raspbee plugin when I restart. But the system runs again with the plugin installed.
And I can also switch Raspbee devices.
Thank you very much for your quick help.

Ok, success with the system.