Just FYI, shall be fixed as per confirmation from Athom…
I have an issue with the triggers “first_household_member_arrived“ and “last_household_member_left“probably not firing correctly.
This ist the timelime:
and this my latest status:
However, the above mentioned triggers appear not to have fired, because the Heimdal alarm system is still activated and deactivated, respectively, which should of course not be the case in the cases “first_household_member_arrived“ and “last_household_member_left“.
Could this be a bug in the app, or am I doing something wrong?
Thanks!
Hi, a simple question. Where do I add devices in the app?
Hard to say but nobody else complains on that so could be your flows - best is to have simple trigger to test desided behavior, eg. First household member arrived → Send notification
Simply as you would be adding any other device
Found, thanks. I thought it was in the app options or something.
sorry to bother you again.
I created the following test flow, which basically loops after “last household member left” until “somebody is at home” is false.
However, even 2 minutes apparently are not long enough for this to happen. Only using “last household member left” for activating Heimdal wasn’t accurate enough, that´s why I added this double check….
Any suggestion on where my mistake is?
If you would like to analyze how it behaves, only use SIMPLE trigger “last household member left” → send me notification (eg. to app). Then you can play with the timings for every device if needed (eg. Away period, Stress period etc). The reason for complexity of your Test flow - sorry, I don’t follow, maybe some other community member can advise. Also keep in mind that Heimdall has its own “Aways/Delays” settings.
Also one more tip - I’m using Wifi/SmartPresence detection but in combination with the Geo-fencing detection of Homey directly, it works quite well in this combo.
Thanks for your tips!
And I should add that I found the error in my flow “Somebody” in “Somebody is at home” is not referring to the same population as ““Last family member” left, which is anybody vs. family…. so everything it running fine ever since.
Hello,
I use this app. Since a few weeks I do get an apple email, always around 4am at night stating: your Apple Account is used to log in at iCloud via a webbrowser.
Could this be this app?
Definitevely not.
Weird, i have a strong LastPass password and 2FA.
I just changed my password again. Thanks for the quick reply.
I’m having an issue with my girlfriends new iPhone. I’ve been using smart presence for a month now. Prior to this new phone smart presence was perfectly working (i was testing with simple notifications ‘if person leaves’ and ‘if person arrives’). Now however it doesn’t. I checked all settings (private mac is off, same IP-adress as her old phone, this old phone is set to factory reset and already sold, so no conflicts possible). I already tried adding a new device and restarting smart presence. It just doesn’t show up as online or offline. Does anyone have some tips?
It is probably the ”Find my app” you have that installed?
I use this also to have a status of my printers if they are online or if they dropped offline. I currently use the guest type for this use case. Can we have an additional category for devices? it doesn’t/shouldn’t influence the status of the aggregated “people” presence logics.
Hi @Sharkys
I recently came across some strange behaviour when a person leaves and returns back again some minutes before the end of the absence detecion period:
- The returning person is immediately registered as present, what is ok and expected.
- But a view minutes later the absence event is triggered by former absence, what is annoying. - Strange thing is, that despite the absence trigger (When) the And card says that the person is present (not absent).
I built a test environment (When cards + Log, nothing else) but could not reproduce it although in “production” it happens fairly often. My guess is that this only happens within a certain time window…
I started to notice this with some very old version.
Went to the test version and it got worse: The rogue absence trigger came with a delay of approx 60 - 90 minutes.
Went to 0.9.5 and the rogue absence trigger comes approx right after the absence detection period.
Could you pls have a look at this?
Btw: I love that you changed the device type to “sensor” in the test version!
Well, not sure about that, as there are apps like NetScan exactly for this purpose, can you elaborate a little about that additional cathegory ? It wouldn’t be “Presense” sensing anymore, right…
Can you support this finding also by logs please ? Ideally after App restart (so it includes your config) and then later, when you observe this behaviour, including the device/phone name in the debug message…
NetScan is exactly what I was trying to achieve. Thank you for pointing me to it.
Shure. But I am currently travelling and it might take some weeks until I can do intensive testing again.
