Hi,
i have 2 xiaomi sensors and havent the temp problem. How you can see the battery level? I have a battery-symbol in the RaspBeeMultiSensor-device and no messurepoints in the graph!
MfG, Jens.
-
New Plugin - [pimatic-raspbee]
Pimatic, my hobby.
-
You can find it in the variables list.
It is at the end$name-of-your-sensor.battery
I am using quite almost variable devices on the UI to customize the content.
this is the native raspbee device:
I have combined the window and the temp sensor in one device (with fresh batteries ):
-
@OrTiN just a question off topic: is the battery icon you use in the variable device static or is it also dynamically changing by battery state?
-
Its a static symbol
-
new version released pimatic-raspbee@0.1.0
-
Big problem after the update. My rules are not responding anymore on status change of the switches even after changing them to switch. I did a rediscover of the switches.
I can see the switch changing status in the front end so they work, but the rules do not respond. I use Trust ZYCT-202 and Aqara Smart switch. Until the update everything worked fine, now not anymore. I have no errors in the config.
Here’s an example of one of my rules:{ "id": "lamp-overloop-achter-aan", "name": "lamp overloop achter aan", "rule": "when switch of raspbee_ZYCT-202_01 = \"1002\" or switch of raspbee_ZYCT-202-02 = \"1002\" or $raspbee_ZYCT-202_01.switch = \"1002\" or $raspbee_ZYCT-202-02.switch = \"1002\" then turn raspbee_INNR_RB165_002 on for 30 minutes", "active": true, "logging": true },
as you can see, I tried through attribute comparison and variable comparison. Neither works. Anyone knows how to solve this?
-
sorry for the trouble.
i will check it.as a quick solution you could test the new predicate provider.
received from raspbee_ZYCT-202_01 event “2001”
-
You can use as well this format within the rule:
when $raspbee_ZYCT-202_01.switch = 1002...
-
@jee67 Problem found
a string conversion was missing. with bugfix-release 0.1.1 the problem should be solved
-> fixed@OrTiN In principle, I would prefer the exact value in pimatic received from deconz.
the question is, why is there a -100.
does the sensor send this? or is it caused by the deconz software.
it’s best to ask the deconz guys first. -
@kosta
Update installed and iT works again. -
Hello.
Would be awesome if you add the temperature value for Aqara windows contacts. In Phoscon the temp is shown, but in pimatic not. Thank you very much
-
@kosta said in New Plugin - [pimatic-raspbee]:
the question is, why is there a -100.
does the sensor send this? or is it caused by the deconz software.I can see the -100 in the pimatic UI of the sensor. So it seems that the sensor itself sends this. I saw this as well with the aqara plugin. The reason there was different (Gateway with denied internet access). Currently it only occures when the battery of the Sensor gets empty (<52%).
-
@Jaschkopf
the redesigned “RaspBeeMultiSensor” should already make this possible.make a pimatic device scan.
You should then get a multisensor device with the name of the sensor.
In this device all IDs and supported sensor values are stored in the arrays.
this device then has both, contact and temperature, valuesif this still doesn’t work out,
please switch on debug mode in plugin,
make a device discovery. In the log is then a JSON list
of the sensors found. You could send them to me and i will check it. -
@kosta nice. works very well. maybe you should add a function to apply a offset to the temperature value. My sensors have really big differences. In the same room two sensors have a diffenrence of 7°C (26°C-33°C)
-
the two following screenshots show the same group - one in pimatic and one in the phsocon app. the brightness slider is in both screenshots set to 100%, but raspbee shows it in the darker area and phoscon in the lighter area. maybe you could turn around the slider?
and i think the colour chooser does not have to bee visible, when the group has no colour attribute. -
@quotschmacher
i’ve never noticed that before. but i can change the gradient.a group can also contain RGB bulbs,
so I created the group with full color selector.
the easiest way will be to add an option to disable the selector. -
Since the last update I get very frequently errors, like:
rror [pimatic-raspbee]: websocket keep alive error, try to reconnect 22:55:35error [pimatic-raspbee]: Error: ETIMEDOUT 22:55:35error [pimatic-raspbee]: Connection could not be establised 22:55:20error [pimatic-raspbee]: websocket keep alive error, try to reconnect 22:45:35error [pimatic-raspbee]: Error: ETIMEDOUT 22:45:35error [pimatic-raspbee]: Connection could not be establised 22:45:20error [pimatic-raspbee]: websocket keep alive error, try to reconnect 21:48:19error [pimatic-raspbee]: websocket keep alive error, try to reconnect 21:48:16error [pimatic]: gateway not online 21:48:16error [pimatic-raspbee]: gateway not online 21:48:16error [pimatic-raspbee]: Error: ESOCKETTIMEDOUT 21:48:16error [pimatic-raspbee]: Connection could not be establised 21:47:50error [pimatic-raspbee]: Error: ETIMEDOUT 21:47:50error [pimatic-raspbee]: Connection could not be establised
and also error because of gateway not found
error [pimatic-raspbee]: websocket keep alive error, try to reconnect 21:45:06error [pimatic]: gateway not online 21:45:06error [pimatic-raspbee]: gateway not online 21:45:03error [pimatic]: gateway not online 21:45:03error [pimatic-raspbee]: gateway not online 21:44:39error [pimatic]: Error on evaluation of rule condition of rule av-klik-aan: gateway not online 21:44:39error [pimatic]: rule av-klik-aan error executing an action: gateway not online 21:44:39error [pimatic-raspbee]: gateway not online 21:44:38error [pimatic]: Error on evaluation of rule condition of rule av-klik-uit: gateway not online 21:44:38error [pimatic]: rule av-klik-uit error executing an action: gateway not online 21:44:38error [pimatic-raspbee]: gateway not online 21:44:36error [pimatic]: Error on evaluation of rule condition of rule av-klik-aan: gateway not online 21:44:36error [pimatic]: rule av-klik-aan error executing an action: gateway not online 21:44:36error [pimatic-raspbee]: gateway not online 21:44:35error [pimatic]: Error on evaluation of rule condition of rule av-klik-uit: gateway not online 21:44:35error [pimatic]: rule av-klik-uit error executing an action: gateway not online 21:44:35error [pimatic-raspbee]: gateway not online 21:44:15error [pimatic]: Error on evaluation of rule condition of rule lantaarn-zonzet-aan: gateway not online 21:44:15error [pimatic]: rule lantaarn-zonzet-aan error executing an action: gateway not online 21:44:15error [pimatic-raspbee]: gateway not online
I have to restart pimatic to get everything working again. This did not happen with the former version of pimatic-raspbee. What is the cause and what is the solution?
-
@jee67 that’s strange. i didn’t change the connection module in the update.
seems that the connection to deconz api is not stable.- does the problem occur often?
- can the problem only be solved by a pimatic restart or is the connection running later by itself?
- deconz and pimatic run on the same server?
- Have you also restarted deconz once?
“gateway not online” comes when an action is started but the deconz-api is disconnected.
the plugin “ping” every 30s the deconz websocket connection,
if it does not receive a response, a reconnection is initiated.this sequence means that the keep alive test failed and the reconnect does not work either.
3 [pimatic-raspbee]: Error: ESOCKETTIMEDOUT 2 [pimatic-raspbee]: Connection could not be establised 1 [pimatic-raspbee]: websocket keep alive error, try to reconnect
-
@kosta
I restarted the gateway and had to restart Pimatic because of the errors31error [pimatic-raspbee]: Error: ESOCKETTIMEDOUT 23:24:31error [pimatic-raspbee]: Connection could not be establised 23:24:30error [pimatic-knmi-weather]: [Plugin] Error: Error: No response from server (timeout) 23:24:30error [pimatic-knmi-weather]: [Plugin] Error: No response from server (timeout) 23:24:30error [pimatic-raspbee]: websocket keep alive error, try to reconnect 23:22:16error [pimatic-raspbee]: websocket closed 23:22:11error [pimatic]: gateway not online 23:22:11error [pimatic-raspbee]: gateway not online 23:22:09error [pimatic]: gateway not online 23:22:09error [pimatic-raspbee]: gateway not online
It’s quite annoying.