@Thrusty the online attribute is for me only available for the tradfri remotes, not for the lights…
-
-
@quotschmacher
For none of the lamps is the online symbol visible? I have 12 of these bulbs. And I can see if everyone in pimatic is online or not. And also the condition on/off, at least when she’s online. Very funny what you tell.Maybe reinstall everything again? Delete the lamps from pimatic and reinstall them? Those would be my ideas, that’s how I would start. But maybe you have already done that.
"Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect." 09-28-2003, LINUS TORVALDS (http://www.nytimes.com)
-
@Thrusty device class is for example RaspBeeCT and the available parameters are
- dimlevel
- ct
- state
- presence
prexence is always true and state is only updated correctly when changed via pimatic - not with the wall switch
-
@quotschmacher
I’m afraid I’m out of it. Unfortunately I can only read, think and install. I think like you too."Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect." 09-28-2003, LINUS TORVALDS (http://www.nytimes.com)
-
all lights have an online status (presence attribute)
When deconz forwards a status update the device will be marked as online.
But currently the status is only set to offline if you want to switch the light via pimatic and then deconz reports that the bulb is not reachable.I will check if deconz send a offline event for lights and make a code modification, so that the offline event automatically handled.
but i expect that the offline event will appear definitely delayed, because deconz notices the absence of the lamp also delayed.
-
@Kosta:
I’m using Pimatic on my iPhone via a WebApp shortcut (‘add to homescreen’).
I added successfully Tradfri/Aqara motion sensors and Tradfri Power Plugs via the Raspbee plugin. No IOS issues.
I removed the Pimatic WebApp and cleared the cache on my iPhone. Added now the Tradfri CT Lamp and accessed Pimatic via Sarafi browser. That worked, no errors!
I reinstalled the Pimatic WebApp again (‘Add to Home Screen’ ) and the errors where back.
So it seems that around te WebApp something happens.Bert
-
@kosta my Problem is: the presence attribute is always true and never changes. But in phoscon app i can see the change.
-
@kosta here you can see my problem. The Light was switched off at 1 in the morning and this can’t be seen at the data in the picture -
Hey Kosta,
I have noticed, that when a temp sensor reaches a battery level of <52% (in my environment) I get sporadically a value of -100 °C. In the past as I used the Aqara plugin of @sweebee. The reason was the denied internet access for the Xiaomi gateway. The reason now is a different one, but the solution of Sweebees filter implementation could compensate this effect here as well. What you mean?
Maybe it could be an idea to add an algorithm which shows 100% battery still as 100% but 50% as 0%. From my point of view 50% battery means EOF for it. -
Nobody else with the -100°C problem here?
-
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.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...