I had some sensors without battery status also, remove and reinclude resulted in battery info for those sensors.
Ok. Thx. I will see if I will do this. It is not do important for me.
@PhilS I can’t see based on the screenshot shared, if it is the Aqara door / window sensor that is reporting the battery levels or the Xiaomi door / window sensor (that is not reporting battery levels).
For a full list of supported devices and their capabilities, please see this topics opening post / or the readme on Github
Sorry ted, it is the aqara (not the rounded older one)
Or am I wrong? Could be, then sorry
I will readd them if I have time. No problem. Keep up the good work @TedTolboom
In that case, you included them already to Homey before I added the battery capability (~March 2018)…
In that case, you’ll need to follow the advice of @Erik_de_Vries to remove and reinclude the devices to add the battery capabilities.
Yes that was long before march 18 indeed. Ok i will. Thanks
… and still running on the first pair of batteries, right?
Yes!!! My fibaros had three Batterie changes since then. I think I will change them in the future with aqaras. Or is there a reason to have the fibaros?
I could have four aqaras for one Fibaro door/windows sensor. And battery level is also not working with the fibaros. So why not change again aqaras?
Secure for zwave plus… okay. But pfff
Thanks @TedTolboom for all the good work! My Xiaomi/Aqara sensors are also reporting 100% but let’s see how that develops. To be honest, don’t really care about an exact reading for everything over 20%
Hi Jeroen, I have the same strange behaviour in my wine cooler:
It goes up to 17,89 degrees almost every hour, while the cooler is completely off (the fridge is controled by Homey).
I use the Xiaomi Temp en Humidity sensor, the square one…
Since the update to 2.0 my volume turning on the cube does not work anymore.
Can somebody share their flow with the new 2.0 app if they managed to get the volume up / down of a sonos system by turning the cube clockwise / anti-clockwise? I can not figure out how to make it happen…Thanks in advance.
Since the 0.5.0 update yesterday i have not been able to use my buttons inside the Homey 2.0 app to trigger flows when pressing the device icon. Under the button info (longpress on device) i only see the following.
It´s the same for all of my buttons (all from Xiaomi). The buttons themself work fine when used “live” and run their respective flows whitout any problems.
I have tried to remove and add the buttons again without fixing this and restarting the Homey.
Anybody else have this problem?
i have it also.
thought it was only me
So I guess the parsing (core or driver) of the data received from the lifeline report contains a bug. I’ll investigate and look for a solution.
@Mole can you share the flow you use?
There was a bug in 2.0 that could have caused this issue, but that one is confirmed to be resolved…
@Mist that is correct; but hasn’t been different before app 0.5.0 or even Homey 2.0.0.
It was never possible to trigger the flows from the Homey app. Since the Xiaomi wireless switch also does not report it’s battery level, no further controls are visible.
And suddenly all my door/windows sensors are in the state Alarm???
All doors and windows are closed, weird…
Ah, Thanks a lot. Too bad they cant behave like the fibaro switches.
The cubes are quite fun to use.
In the Homey v1 it was in the tags possible to which side was up. In Homey v2 i don’t see this option anymore.
Now I discovered in the Xiaomi app the face numbering map. I know a little about technical drawings but this one I don’t understand.
In real the logo and the battery door are opposites, not in the numbering map.
Is there an easy way to discover the sides?
The face side is part of the arguments of the flow card: press “Any side up” and you’ll get all available options:
The alternative option is to use the “Cube motion” card:
Which will add the local tags “source face” and “target face”
Final alternative is to use any of the trigger cards (with any side up option where applicable) and use a build in logic condition card with the “face up” capability tag:
You’re referring to: https://github.com/TedTolboom/com.xiaomi-mi-zigbee/blob/master/docs/README_cube.md
1, 6, 4, 3 should be in one column.
The logo is located on face 6.
But to discover the face numbering, check the device sensor display. It has the actual face up shown there.