App not reliable yet?
It seems that room occupancy remains ON until app is restarted. Same when I get back in the room.
Not at my home… ghosting?
Nope. In the Aqara app everything is OK and in Homey, the values of the sensor are updated only when I restart the app.
I also tested the light sensor
4692bd5b-df98-4bac-b39f-1a427d88ace8
Update: I restarted the app once more and I did some tests. It works now.
I also created a flow to monitor if the app crashes.
App works only few minutes after restart.
The “App xxx has crashed” flow doesn’t detect anything.
Hi. Nice job.
Can you add support for vocolinc humidifier?
Weird … I do not see a crash in the app dashboard either…
Just hang on a bit until logging is released…
1 Like
for some reason the FP2 it disconnects from the network…resubscribe does not work, are you changing zone definitions in the FP2?
192.168.1.36:63003 Persistent connection client got disconnected
2023-11-03T12:08:17.527Z [log] [ManagerDrivers] [Driver:hapIP] [Device:31e095fe-b9fd-41d7-81e7-7299e3bfd87e] listenToEvents Disconnected: network connect will resubscribe
2023-11-03T12:08:17.528Z [log] [ManagerDrivers] [Driver:hapIP] [Device:31e095fe-b9fd-41d7-81e7-7299e3bfd87e] listenToEvents unsubscribe succes
Maybe that is when I restarted the sensor?
Local network seems stable and the FP2 has a reserved IP address.
Also I’m not using zones. sensor is in my office and is not big enough to use zones.
Then it will surely disconnect. The issue is the the FP2 will use the same IP but a different port. And Homeys discovery does not show the new port when the app runs, it only gets that when you reinit the app
Perhaps add a comment to MDNS discovery not having updated txt or port on lastseen events · Issue #322 · athombv/homey-apps-sdk-issues · GitHub
That’s me opening the issue…
Whoops 
Is there a way around using standard discovery from Athom? Tried other package but i guess the Homey environment does not allow for apps to do this themselves…
Did a little test with bonjour and it finds all my HomeKit devices just fine.
1 Like
Even in NL:
Het ziet er naar uit dat de kaartjes helderheid groter dan, helderheid kleiner dan, omgedraaid zijn.
Dus kleiner dan is eigenlijk groter dan en omgekeerd.
Mijn flow deed het niet en na het omdraaien van de waardes werkte het wel.
Daar doe ik eigenlijk niets aan, standaard door Homey gemaakt. Ga later checken waarom dit gebeurd…
1 Like
Helderheid werkt bij mij wel volgens verwachting in v0.0.3.
Ik heb wel een wens: de helderheid ook als EN voorwaarde in een advanced flow kunnen definieren. Voorbeeld: als de zone wordt betreden EN het is minder dan 75 lux, doe de lamp aan.
Dat moet middels een logica kaartje mogelijk zijn.
1 Like
I would like to make an advanced flow to prevent blinking lights with the FP2. For example: if x seconds after leaving a zone the zone is still not occupied, turn off the lights, otherwise keep lights on.
Anybody an example or solution how to define this?
This works
1 Like
