Homey Community Forum

Xiaomi / Aqara Smart Home - Zigbee App (v0.5.3)

app
zigbee

#488

Excellent!


#489

Thank you! This was a big one for me, yet I have never report it as I used an workaround solution.
Thank you again!


#490

Sorry for asking again, but is there a limitation in the older Xiaomi sensors that makes it impossible to make it report the battery, or is this something that will come eventually?


#491

Some one who really knows will probably answer but the oval ones do not report battery status at my house but the rectagular (Aqara) do.


#492

if you have the the regular Aqara ones (not the old rounded), but installed them before may 2018, you have to readd them. @TedTolboom told me so.

only then they will have the new capabilities like battery status.


#493

No, I have the old Xiaomi:

It is clearly stated that they dont support battery reporting, but my question us basically if this is something that might come, or if there are hard limitions for these devices


#494

Thanks for the upate TED. This was my biggest issue lately where bulbs went out when not triggered.
Hopefully with 0.5.2 this wil be gone :slight_smile:


#495

Q&A time; more A then Q…

@Maurice_OT Initially, I thought about a mesh issue, but if you are using long motion alarm cancellation times, this could have been caused by the lifeline report directly updating the alarm state. That should be solved in v0.5.2

I’ll need to check if it is (already) possible to write to the device log from within the app.

@Jari_Tyrvainen and @edwintan I don’t have any control over Z-wave / Zigbee mesh-creation from within the app; this is all handled within the core. As well as showing the routes on the tooling.

Some simple checks:

  • Do the / all devices still work as they intend to work? If so, simply ignore the routing tables.
  • When going to the Zigbee tools section, please check that the ‘Current Command’ (bottom row of the system information) shows ‘generateMap’.
    • if not, force refresh the page, until it does show ‘generateMap’
    • if it does, wait for 2-3 minutes and the routes should start showing

I still fail miserably in mind reading…

Only the Xiaomi temperature and humidity sensor and the Xiaomi Cube are reporting battery levels. All other Xiaomi devices; e.g. occupancy sensor or door and window sensor are not.

This is indeed a device limitation. I haven’t seen any communication from these devices that could even hold the battery info.


#496

Anybody any thoughts on how to accomplish this?

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.


#497

@Mole did you try a similar setup as described in:


#498

Yes, but can not see where I go wrong:





#499

Step by step:

  1. I would recommend to combine both actions into one into the math.js calculation card
  2. does the first flow work? Manually set the volume of the Sonos to a different level and test this flow to see if the volume is changed
  3. Does after a rotation the BL variable change?

#500

Don"t see a command to actually SET the value (Sonos volume - keuken) to the Sonos speaker.

if you don’t SET these value to the speaker, it won’t work!
image


#501
  1. I would recommend to combine both actions into one into the math.js calculation card
  2. does the first flow work? Manually set the volume of the Sonos to a different level and test this flow to see if the volume is changed
  3. Does after a rotation the BL variable change?

Forgive me for being a noob. I tried several options but it does not respond. When i test the first flow it gives me an error: Token_out-of-range. So the answer on the 2 question is no. I do not get the first question, where and how can i combine both actions?
About the third question, if i turn the cube i see that the variable does change…

I made a “simple” flow to see if it works anyway, and in this setup it responds. It seems to go wrong with translating the turning into a volume step.


#502

Can u try the BL cards without the tags but with the names of the variables typed?


#503

My problem was bad Homey power supply. First devices drop from mesh, later Homey drop from Internet and booting. Then I take power off about 20min. After that Homey not start anymore. Then I change new USB power supply and everything works now.


#504

Ok. Good to hear it is solved now!


#505

Hello Ted,

I now also experience zigbee devices that drop out of the mesh network. It happen when i added an Ikea wall outlet to the mesh. When it was added too homey I have PullThePlug from homey placed my Ikea outlet upstairs and after 15 minutes i powered homey again. This is what i do to make sure the mesh is created with the routers i have placed all over the house.

I now see devices that donot connect to the homey and are actually in close proximity of the homey like MAX 4 meters.

I can add them again but everytime i reset the MESH network devices are dropping of in the list. When you just pull the plug for 10 seconds the mesh is not changed.


#506

@TedTolboom Will/can you add history to vibration sensor? I realy like that you added battery info on the other sensor btw. :slightly_smiling_face:


#507

Thanks @Kjelle, also for you donation! Much appreciated!

As mentioned above, it is not yet possible to choose as app developer which data is shown in the device history.

Currently Homey’s core only shows here the Boolean capabilities; onoff and alarm_. I’ll check with Athom if they will provide an option to be able to add data to this history.