New Plugin - [pimatic-raspbee]

---

@jee67 said in New Plugin - [pimatic-raspbee]:

No more errors. I restarted both raspberries. Firstly the one with the Deconz gateway and next the one with Pimatic. Since then no more errors occur. Both system running for four days now. So, restarting both seem to be the solution.

Update: whenever network connection is lost, Pimatic cannot find the gateway after the network is up again. Since I have some ads, issues, I have to restart the modem frequently. I have to restart Pimatic first and then the connection with the deck a gateway is established again. Is there anyway to connect to the gateway, without the necessary restart of Pimatic?

@jee67 said in New Plugin - [pimatic-raspbee]:

@jee67 said in New Plugin - [pimatic-raspbee]:

No more errors. I restarted both raspberries. Firstly the one with the Deconz gateway and next the one with Pimatic. Since then no more errors occur. Both system running for four days now. So, restarting both seem to be the solution.

Update: whenever network connection is lost, Pimatic cannot find the gateway after the network is up again. Since I have some ads, issues, I have to restart the modem frequently. I have to restart Pimatic first and then the connection with the deck a gateway is established again. Is there anyway to connect to the gateway, without the necessary restart of Pimatic?

For now I automated the restart of Pimatic after a lost connection with Deconz, but it would be nicer if the connection is re-established automatically by Pimatic after a disconnect.

@jee67
the plugin makes a reconnect to the gateway every 30 seconds.
therefore the connection should be re-established.

do you use names or ip addresses in the configuration?
does pimatic have any other problems after a network loss?

please send me the complete log before and after a failure.

@kosta
I tried to reproduce the errors today, but (luckily) it wasn’t able too.
In the configuration I use IP numbers (Deconz = 10.0.0.184)

I shutdown my Rapsberry with Deconz at 16:40 and restarted it at 16:43. Pimatic had no problems reconnecting. Same when I restarted my router at 16:45 which was up again at 16:47. No problems reconnecting, no errors after 16:47:45.
The only thing I can think of. is that the connection might not be reestablished after a longer period. I will tried that in a couple of days. Have no time now for a long downtime of the router or the deconz.

    2019-09-11 16:47:45error [pimatic-raspbee]: Error: connect EHOSTUNREACH 10.0.0.184:80
    16:47:45error [pimatic-raspbee]: Connection could not be establised
    16:47:44error [pimatic-raspbee]: websocket keep alive error, try to reconnect
    16:47:14error [pimatic-raspbee]: Error: connect EHOSTUNREACH 10.0.0.184:80
    16:47:14error [pimatic-raspbee]: Connection could not be establised
    16:47:14error [pimatic-raspbee]: websocket keep alive error, try to reconnect
    16:46:46error [pimatic-raspbee]: Error: connect EHOSTUNREACH 10.0.0.184:80
    16:46:46error [pimatic-raspbee]: Connection could not be establised
    16:46:44error [pimatic-raspbee]: websocket keep alive error, try to reconnect
    16:42:48error [pimatic-raspbee]: Light with ID: 17 not found
    16:42:48error [pimatic-raspbee]: Light with ID: 15 not found
    16:42:48error [pimatic-raspbee]: Light with ID: 14 not found
    16:42:48error [pimatic-raspbee]: Light with ID: 13 not found
    16:42:48error [pimatic-raspbee]: Light with ID: 12 not found
    16:42:48error [pimatic-raspbee]: Light with ID: 11 not found
    16:42:48error [pimatic-raspbee]: Light with ID: 10 not found
    16:42:48error [pimatic-raspbee]: Light with ID: 8 not found
    16:42:48error [pimatic-raspbee]: Light with ID: 7 not found
    16:42:48error [pimatic-raspbee]: Light with ID: 6 not found
    16:42:48error [pimatic-raspbee]: Light with ID: 5 not found
    16:42:48error [pimatic-raspbee]: Light with ID: 4 not found
    16:42:48error [pimatic-raspbee]: Light with ID: 3 not found
    16:42:48error [pimatic-raspbee]: Light with ID: 2 not found
    16:42:48error [pimatic-raspbee]: Light with ID: 1 not found
    16:42:44error [pimatic-raspbee]: websocket keep alive error, try to reconnect
    16:42:17error [pimatic-raspbee]: Error: connect EHOSTUNREACH 10.0.0.184:80
    16:42:17error [pimatic-raspbee]: Connection could not be establised
    16:42:14error [pimatic-raspbee]: websocket keep alive error, try to reconnect
    16:41:47error [pimatic-raspbee]: Error: connect EHOSTUNREACH 10.0.0.184:80
    16:41:47error [pimatic-raspbee]: Connection could not be establised
    16:41:44error [pimatic-raspbee]: websocket keep alive error, try to reconnect
    16:41:16error [pimatic-raspbee]: Error: connect EHOSTUNREACH 10.0.0.184:80
    16:41:16error [pimatic-raspbee]: Connection could not be establised
    16:41:14error [pimatic-raspbee]: websocket keep alive error, try to reconnect
    16:40:59error [pimatic-raspbee]: Error: ETIMEDOUT
    16:40:59error [pimatic-raspbee]: Connection could not be establised
    16:40:44error [pimatic-raspbee]: websocket keep alive error, try to reconnect
    16:40:17error [pimatic-raspbee]: websocket closed

The info on reconnecting:

    info [pimatic-raspbee]: Event receiver connected.
    16:48:14info [pimatic-raspbee]: API key valid
    16:48:14info [pimatic-raspbee]: Software Version 2.5.65
    16:48:14info [pimatic-raspbee]: API 1.16.0
    16:48:14info [pimatic-raspbee]: Name Phoscon-jkd
    16:48:14info [pimatic-raspbee]: Connection establised
    16:42:47info [pimatic-raspbee]: Event receiver connected.
    16:42:47info [pimatic-raspbee]: API key valid
    16:42:47info [pimatic-raspbee]: Software Version 2.5.65
    16:42:47info [pimatic-raspbee]: API 1.16.0
    16:42:47info [pimatic-raspbee]: Name Phoscon-jkd
    16:42:47info [pimatic-raspbee]: Connection establised

Hey Kosta.

I finally received my conbee 2 stick in the mail.

I installed deconz on my pi which is running pimatic as well. Deconz start and so far I have added one blind and I can control it in the old deconz web app. I tried to setup pimatic raspee plugin to use the rest api but for some reason it fails to connect even though I can connect to the address in Chrome on my phone.

error [pimatic-raspbee]: 404 - "<html><head></head><body><h1>This is not the page you are looking for</h1><p>The file /:/api/853c7403937d8b62/config couldn't be found.</p></body></html>"

This error comes every 30 seconds.
The ip is 192.168.3.4 and the api port is 80.

I have removed my echo plugin as it was causing problems for pimatic to crash on start up. I guess because deconz is using port 80. But still no connection is established with the plugin and deconz rest api.

Do you know what is wrong?

Kind regards Simon

hey @simonbove,

can you give me some information about your environment?

On which port do Pimatic and Deconz run?
I think you have a port conflict.

=> howto change deconz port

Yes you are right. I had a port conflict.
It is now up and running. I can control my new ikea blinds from pimatic.
Wonderful
Thank you for your help.

Kind regards Simon

Hopefully I will receive my conbee 2 tommorow, so I’m already playing with some stuff.
Installed deconz in a docker (without an actuall raspbee yet) and installe the pimatic-raspbee plugin.
Did a discovery and the plugin paired with the deconz API and generated a API key. So far everything seems OK. Howver, the plugin is giving this error every few seconds these errors:

19:56:56error [pimatic-raspbee]: socket hang up
19:56:56error [pimatic-raspbee]: websocket error
19:56:56error [pimatic-raspbee]: websocket keep alive error, try to reconnect
19:56:26error [pimatic-raspbee]: websocket closed
19:56:26error [pimatic-raspbee]: socket hang up
19:56:26error [pimatic-raspbee]: websocket error
19:56:26error [pimatic-raspbee]: websocket keep alive error, try to reconnect
19:55:56error [pimatic-raspbee]: websocket keep alive error, try to reconnect
19:55:56error [pimatic-raspbee]: websocket error
19:55:56error [pimatic-raspbee]: socket hang up
19:55:56error [pimatic-raspbee]: websocket closed
19:55:26error [pimatic-raspbee]: websocket keep alive error, try to reconnect
19:55:26error [pimatic-raspbee]: websocket error
19:55:26error [pimatic-raspbee]: socket hang up
19:55:26error [pimatic-raspbee]: websocket closed
19:54:56error [pimatic-raspbee]: websocket keep alive error, try to reconnect

I’m running my deconz in a docker, so I have some port mappings in there. The GUI is exposed as port 1039 - the pimatic plugin is configured to use that port and that works.
But the error is talkin about websocket. The deconz websocket port is 443 but in my docker exposed as 1037
Could it be the plugin is trying to connect to port 443 ?

UPDATE : Had a configuration error in the environment variables for the contaciner. Correct it, ony to get other error:

20:08:56error [pimatic-raspbee]: websocket error
20:08:56error [pimatic-raspbee]: Unexpected server response: 400
20:08:56error [pimatic-raspbee]: websocket closed
20:08:26error [pimatic-raspbee]: websocket keep alive error, try to reconnect
20:08:26error [pimatic-raspbee]: websocket error
20:08:26error [pimatic-raspbee]: Unexpected server response: 400
20:08:26error [pimatic-raspbee]: websocket closed
20:07:56error [pimatic-raspbee]: websocket keep alive error, try to reconnect
20:07:56error [pimatic-raspbee]: websocket error
20:07:56error [pimatic-raspbee]: Unexpected server response: 400
20:07:56error [pimatic-raspbee]: websocket closed

@koffienl sorry for the late answer. Im on vacation right now. yes. The plug-in reads the websocket port from the deconz config on connect. Probably the problem is the port translation. You can set the websocket port with an environment variable DECONZ_WS_PORT=1345. Try to set the exposed port to the same as the configured port.

Totally forgot to update my latest post. Got it all working. Problem was the docker with exposed ports and environment vars for the docker.

@kosta I have a problem with temperature offset on my multisensors.
only possible value is in INT format witch means I can not input 1.5 or any other value with a decimal without an error but the values displayed in pimatic on some sensors do have 2 decimal numbers in it.
I would like to fine tune these sensors by offsetting also with a value with a + or - X.XX witch would be a NUMBER not an INT
is this possible in a future version.

error [pimatic]: Invalid config of device “raspbee_00158d0002a37121”: Property “#/temperatureOffset” Should have type integer, was: number in /temperatureOffset

Thanks

@ed-vrijmoet
i have created a github issue for that. this can be easily implemented.
https://github.com/treban/pimatic-raspbee/issues/48

It seems that last raspbee deconz rest plugin prevents pimatic from starting:

08:38:14.209 [pimatic-raspbee] info: Connection establised
08:38:14.214 [pimatic-raspbee] info: Name rpiz
08:38:14.221 [pimatic-raspbee] info: API 1.16.0
08:38:14.224 [pimatic-raspbee] info: Software Version 2.5.79
08:38:14.228 [pimatic-raspbee] info: API key valid
08:38:14.608 [pimatic-raspbee] info: Event receiver connected.
08:38:25.368 [pimatic-raspbee] debug: new message received
08:38:25.377 [pimatic-raspbee] debug: { attr:
08:38:25.377 [pimatic-raspbee] debug:> { lastannounced: null,
08:38:25.377 [pimatic-raspbee] debug:> lastseen: ‘2020-07-21T06:38:15Z’,
08:38:25.377 [pimatic-raspbee] debug:> manufacturername: ‘OSRAM’,
08:38:25.377 [pimatic-raspbee] debug:> modelid: ‘Classic A60 W clear - LIGHTIFY’,
08:38:25.377 [pimatic-raspbee] debug:> name: ‘Luz Habitacion Bebe’,
08:38:25.377 [pimatic-raspbee] debug:> swversion: ‘V1.05.10’,
08:38:25.377 [pimatic-raspbee] debug:> type: ‘Dimmable light’,
08:38:25.377 [pimatic-raspbee] debug:> uniqueid: ‘84:18:26:00:00:0f:83:d7-03’ },
08:38:25.377 [pimatic-raspbee] debug:> e: ‘changed’,
08:38:25.377 [pimatic-raspbee] debug:> id: ‘16’,
08:38:25.377 [pimatic-raspbee] debug:> r: ‘lights’,
08:38:25.377 [pimatic-raspbee] debug:> t: ‘event’,
08:38:25.377 [pimatic-raspbee] debug:> uniqueid: ‘84:18:26:00:00:0f:83:d7-03’ }
08:38:25.399 [pimatic] error: An uncaught exception occurred: TypeError: Cannot read property ‘bri’ of undefined
08:38:25.399 [pimatic] error:> at RaspBeeDimmer.parseEvent (/home/pi/pimatic-app/node_modules/pimatic-raspbee/raspbee.coffee:1013:10)
08:38:25.399 [pimatic] error:> at RaspBeePlugin.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic-raspbee/raspbee.coffee:997:12)
08:38:25.399 [pimatic] error:> at emitOne (events.js:121:20)
08:38:25.399 [pimatic] error:> at RaspBeePlugin.emit (events.js:211:7)
08:38:25.399 [pimatic] error:> at RaspBeeConnection.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic-raspbee/raspbee.coffee:252:10)
08:38:25.399 [pimatic] error:> at emitOne (events.js:116:13)
08:38:25.399 [pimatic] error:> at RaspBeeConnection.emit (events.js:211:7)
08:38:25.399 [pimatic] error:> at WebSocket.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic-raspbee/raspbee-connector.coffee:65:14)
08:38:25.399 [pimatic] error:> at emitOne (events.js:116:13)
08:38:25.399 [pimatic] error:> at WebSocket.emit (events.js:211:7)
08:38:25.399 [pimatic] error:> at Receiver.receiverOnMessage (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/websocket.js:720:20)
08:38:25.399 [pimatic] error:> at emitOne (events.js:116:13)
08:38:25.399 [pimatic] error:> at Receiver.emit (events.js:211:7)
08:38:25.399 [pimatic] error:> at Receiver.dataMessage (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/receiver.js:414:14)
08:38:25.399 [pimatic] error:> at Receiver.getData (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/receiver.js:346:17)
08:38:25.399 [pimatic] error:> at Receiver.startLoop (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/receiver.js:133:22)
08:38:25.399 [pimatic] error:> at Receiver._write (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/receiver.js:69:10)
08:38:25.399 [pimatic] error:> at doWrite (_stream_writable.js:396:12)
08:38:25.399 [pimatic] error:> at writeOrBuffer (_stream_writable.js:382:5)
08:38:25.399 [pimatic] error:> at Receiver.Writable.write (_stream_writable.js:290:11)
08:38:25.399 [pimatic] error:> at Socket.socketOnData (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/websocket.js:795:35)
08:38:25.399 [pimatic] error:> at emitOne (events.js:116:13)
08:38:25.399 [pimatic] error:> at Socket.emit (events.js:211:7)
08:38:25.399 [pimatic] error:> at Socket.emit (/home/pi/pimatic-app/node_modules/pimatic/startup.coffee:64:24)
08:38:25.399 [pimatic] error:> at addChunk (_stream_readable.js:263:12)
08:38:25.399 [pimatic] error:> at readableAddChunk (_stream_readable.js:250:11)
08:38:25.399 [pimatic] error:> at Socket.Readable.push (_stream_readable.js:208:10)
08:38:25.399 [pimatic] error:> at TCP.onread (net.js:601:20)

@mat1990dj

published new hotfix release 0.1.6 with the bugfix

I saw that and commented on the github thread that there might still be an issue.

Hotfix 0.1.7 released

the 0.1.6 was empty.
had me tangled with the branches.