[APP] Aqara & Xiaomi Smart Home - A different kind of Smart Home solution (Zigbee App)

[Dennis_H74]

Pressure offset is working like a charm on the 10th floor

Thanks !!

[Hannes85]

As a reply to the “12 hour” period; it is still acting the same way, updating Lux every second or so.

[Angel_Escudero]

Hi @TedTolboom !!!

I am using NODERED and a temperature and humidity sensor (square).

The behavior is correct, it shows temperature, humidity …

The problem comes if Homey restarts. The sensor appears in homey and updates the values.

But it does not do it in NODERED. If I enter the MQTT Hub application and activate and deactivate the sensor at that time it starts sending data to the NODERED interface.

Do you have knowledge of this problem?

Thanks !!!

[TedTolboom]

No I don’t… I didn’t find time to play around with NodeRED before.

Only option I can imaging is star the Aqara app, with quite some sensors requires more time to initialize then MQTT; therefore MQTT marks the sensors as offline.

You could try to restart the MQTT app (by a flow) around 30 minutes after the reboot.

[Angel_Escudero]

Hi @TedTolboom

I appreciate the help. I got through a flow, restart the MQTT server.

Thank you!!!

[Roy_Hopman]

Could anyone tell me if there is a solution for the reset timer of the motion sensor?
I understand that the refresh time is long to preserve the battery. However,
i would like to have my lights activate automatically between sunset and sunrise when i walk
through the hall (nightly toilet visit - i have IKEA tradfri all over the house).

However, i dont want want my lights to stay active as long as the sensor is active.
I can set the light to be on for lets say 60 seconds after sensor triggering, but the sensor itself stays ‘‘active’’ for quite long. is there any soluion to reset the status to no movement or something like that?

ideally i would walk through the hallway, lights go on. motion sensor resets after approx 20 seconds and light stays on for approx 60 seconds. if i walk back, light is off, and would trigger on again.

Anyone has some advice for me on this?

[robertklep]

The Xiaomi sensors have a default blind time of 60 seconds, I think. There is a hack (see this comment) that will cut that down to 5 seconds. Instead of soldering, you can also use a soft(-ish) pencil to make the connection that is required for the hack, and you can set the lower blind time in the advanced settings of the Xiaomi app, I believe.

[Gas]

@TedTolboom
Aqara opple. Is this some help for the problem?
https://github.com/dresden-elektronik/deconz-rest-plugin/pull/2531

[Mario_Me]

Hey guys,
Any idea re: this?

Aqara sensors show red exclamation mark

Hiya, After the upgrade to 4.x my many many Aqara sensors are all marked with a nice looking but not nice-being red exclamation mark. When looking into the device it’s shown as „device not available“ / timeout. Funny thing: The devices and their flows seem to work plus in Apples Home App I can even see the correct status (eg door sensor open/close). PTP: Done Restart App: Done Updates: Done Any better idea here? Thx ! [image] [image]

[hplos]

You could try work with a countdown timer.
If the min value of the sensor is 60sec. I would start the timer for 90sec, because if you would walk back on the 60 sec, the light may go off (if the sensor didn’t see you already), now the sensor had 30 sec to spot you again

[Sharkys]

Try to re-add them without removing them, it will tell you upon add it’s duplicated device but the error state may disappear. Had this issue before on version prior to v4.

[Daniel_S]

How many zigbee devices you have? When i reach more than 20 this often happens to me too.

[Igy]

Currently 24 had 28 before with 2 Ikea plugs as a routers. Do you have all zigbee devices unavailable, or only Aqara models?

[Andrea_M]

Hi Daniel_S

Sorry for going off topic … How did you include those nice tags to the tiles?

[Daniel_S]

Only Aqara app devices were not working. Other or generic zigbee ok. So I linked this problem to Aqara app.

[TedTolboom]

@Gas

@TedTolboom
Aqara opple. Is this some help for the problem?
https://github.com/dresden-elektronik/deconz-rest-plugin/pull/2531

@Gas thank you for sending the link; didn’t see this comment (in this thread) yet.
So it appears that indeed the device behavior can be controlled.

• Multiple options per button is controlled by setting a specific attribute: endpoint.write('aqaraOpple', {'mode': 1}, {manufacturerCode: 0x115f});
• Preventing “hostile take-over” of other Zigbee devices is controlled by defining the right Group(s)

Unfortunately, both options to control these devices are not implemented in Homey’s current Zigbee Core… Manufacturer specific attributes not (also needed to e.g. control the Aqara Curtains direction), nor does defining Groups…

I will, once more (see comment on Aqara Curtains), check if there is a work around; but don’t get your hopes too high… likely will be one for the Zigbee rewrite.

[Daniel_S]

Just use your google keyboard emotikons in mobile.

[Andrea_M]

Thanks Daniel!!!

[Cory]

Thanks so much for your work on this app and continuing to look into these switches, even though they’re proving so much trouble. I/we really appreciate it.

Do you mean the multiple-options-per-button feature will have to wait for the Zigbee rewrite, or support of the switch altogether?

As far as the “hostile take-over” behavior - could that be circumvented by not having any Zigbee bulbs connected to mains during the pairing process?

[Mario_Me]

This is not possible because the App highlights all existing sensors w/ red exclamation mark

Has to be an error w/ the App, maybe Athom can investigate this, will report to

them.