Thanksgiving lighting took a holiday

[CatmanV2]

@therealdb It is indeed so designed, but that's not what I am seeing in terms of behaviour. Of course I may have misconfigured it on my phone so I am happy to be corrected!

(but I'll probably bug you for help)

But not right now

C

[gwp1]

@CatmanV2 I concur with @therealdb here, I've been using the OwnTracks on iOS via the Hubitat app integrations and it works well. I also use, as a secondary, a Home Assistant integration called iCloud3 which mitigates the 2FA issues you found with iPhone Locator. I've seen no noticeable battery issues (once I had iC3 configured correctly.)

@toggledbits got me into OwnTracks when he had his Logo trial up and running.

[CatmanV2]

Well I fully expect to be wrong I know that Geolocation is one of the use cases that Apple permit (or at least tolerate) in their process (and it's documented in the Owntracks literature as well as being the workaround for our devs.

I strongly suspect I fubarred the config somewhere (possibly as basic as not allowing full location services, for example). I had a crack this morning and I have the phone claiming it's connected, and reactor claiming it's connected (yay)

I need to get the entity installed but that's another day

C

[CatmanV2]

Trying to follow the posting guidelines.....

  - id: mqqt
    enabled: true
    implementation: MQTTController
    name: Mosquito
    config:
      source: "mqtt://192.168.70.249:8883/"
      username: xxxxx 
      password: xxxxx
      entities:
        catman_iphone:
          name: "Catman Phone"
          topic: FFCEB043-B975-490E-B051-198473F6A504
          uses_template: owntracks_in_region

Claims to be valid YAML in https://yamlchecker.com/

But when I add the last 4 lines to my reactor.yaml msr will not start:

Reactor log stops:

[latest-22274]2022-10-08T17:32:39.316Z <Engine:NOTICE> [Engine]Engine#1 has shut down.
[latest-22274]2022-10-08T17:32:39.316Z <app:NOTICE> Closing Structure...
[latest-22274]2022-10-08T17:32:39.317Z <Structure:INFO> Structure#1 Stopping controllers...
[latest-22274]2022-10-08T17:32:39.317Z <VeraController:NOTICE> VeraController#vera stopping
[latest-22274]2022-10-08T17:32:39.321Z <VeraController:ERR> Controller VeraController#vera is off-line!
[latest-22274]2022-10-08T17:32:39.366Z <MQTTController:NOTICE> MQTTController#mqqt stopping, sending LWT
[latest-22274]2022-10-08T17:32:39.366Z <DynamicGroupController:NOTICE> DynamicGroupController#groups stopping
[latest-22274]2022-10-08T17:32:39.369Z <DynamicGroupController:ERR> Controller DynamicGroupController#groups is off-line!
[latest-22274]2022-10-08T17:32:39.369Z <SystemController:NOTICE> SystemController#reactor_system stopping
[latest-22274]2022-10-08T17:32:39.371Z <SystemController:ERR> Controller SystemController#reactor_system is off-line!
[latest-22274]2022-10-08T17:32:39.372Z <Structure:INFO> Structure#1 Final data sync...
[latest-22274]2022-10-08T17:32:39.379Z <Structure:NOTICE> Structure Structure#1 stopped
[latest-22274]2022-10-08T17:32:39.379Z <app:NOTICE> Stopping timers...
[latest-22274]2022-10-08T17:32:39.380Z <app:NOTICE> Shutdown complete, process ID 27723

As soon as I replace the original version of reactor.yaml

  - id: mqqt
    enabled: true
    implementation: MQTTController
    name: Mosquito
    config:
      source: "mqtt://192.168.70.249:8883/"
      username: xxxx 
      password: xxxx

Everything springs to life.

I can't see an error in my syntax. Do I need to have the region in there (although I've tried both with and without)

It's going to be something obvious / stupid but hopefully I'm learning at least a little

TIA

C

[therealdb]

@catmanv2 the logs are not complaining, so maybe the error was written before.

values are escaped with " in the docs, give it a try (ie: "catman_iphone" and topic: "FFCEB043-B975-490E-B051-198473F6A504")

[CatmanV2]

Thanks

Tried

  entities:
        catman_iphone:
          name: "Catman Phone"
          topic: "FFCEB043-B975-490E-B051-198473F6A504"
          uses_template: owntracks_in_region
          regionName: Home

and

  entities:
        "catman_iphone":
          name: "Catman Phone"
          topic: "FFCEB043-B975-490E-B051-198473F6A504"
          uses_template: owntracks_in_region
          regionName: Home

With no discernible difference

C

[toggledbits]

@catmanv2 Topics for me are not UUIDs, but rather the content of the Device ID field in the Identification section of the configuration. This is a value you set, not a value determined by OwnTracks. That's Android. I no longer have an Apple device I can use for this.

        owntracks_patrick_home_template:
          name: "Patrick Home Template"
          uses_template: owntracks_in_region
          topic: phrs21
          regionName: Home

[MikeReadington]

Thanks for all of the input.

For whatever reason I am having the same spotty relationship with OwnTracks that @CatmanV2 has. One minute I think it's solved, the next minute it's missed a trigger.

With the success others have had, including @gwp1 with the same method of deployment, I must have something wrong. I'll keep working on it as time permits.

Thanks again

[CatmanV2]

@mikereadington iPhone or Android?

C

[MikeReadington]

@catmanv2 iPhone. I just returned home and it got a location trigger, but it was far from an instant trigger. The phone was in sleep for at least 30 minutes before I crossed the perimeter, and I would say the delay was in the area of 45 seconds.

[CatmanV2]

45 seconds I can live with, personally but might not be right for your use case. (My fence is about 5km out)

The thing I'm struggling with right now is testing it. I think I need to cross the fence. Logically I make the region much smaller for testing purposes but other issues at work today.

C

[gwp1]

@catmanv2 testing OwnTracks can be accomplished by changing from substantial to move in the app and then, well, moving.

[CatmanV2]

@gwp1 said in iPhone location or alternative.:

@catmanv2 testing OwnTracks can be accomplished by changing from substantial to move in the app and then, well, moving.

Thanks, I can see the data arriving from Owntracks in Mosquitto (if you hit publish, for example) but what I can't do is get the MQQT entity to have anything but 'null' as its primary value. I can see MQQT is publishing to reactor as well, so confidence is reasonably high....

My "logic" is that MSR is looking for the 'Enter' or 'Leave' payload which you only get when you transition into / out of a region.

I was expecting to go somewhere today but the optician was ill and I've been tied up on calls and meetings all day so not had a chance to set a small region and wander up the road.

Of course my logic could be utterly wrong, but wanted to test it before asking for more help.

Because then I can save what little credibility I have and use it asking for help as to why the second phone (Mrs C's) doesn't have primary value. I found an error in the logs though which I'll dig at later

Cheers

C

[MikeReadington]

@catmanv2 Yeah, my use case is a little more particular. I don't have an issue with never getting notification changes, they are just more delayed than I would like. I think once you get MQTT and MSR talking a 5km is going be more than relievable enough.

I had iPhone locator poll/force location refresh when I came in my driveway and triggered the magnetic sensor. I needed the location to be accurate and updated by the time I reached either my house or my building on property. The driveway is about 300m long as the crow flies for region radius purposes, and traversal to either location is much less than 45 seconds.

For what it is worth, I do see instant (and I mean instant instant) location changes like @therealdb and @gwp1 reported when the app is open or recently accessed. The delay seems to come from the app being backgrounded and the phone idle for a long period.

@gwp1 with HASS iCloud3, can you remote request a location refresh of the phone? Meaning, could I have polling suspended until I ask for an update? I think I could get exactly what I am looking for with a combination of the two and some MSR logic.

[CatmanV2]

@mikereadington said in iPhone location or alternative.:

I had iPhone locator poll/force location refresh when I came in my driveway and triggered the magnetic sensor. I needed the location to be accurate and updated by the time I reached either my house or my building on property. The driveway is about 300m long as the crow flies for region radius purposes, and traversal to either location is much less than 45 seconds.

Given my thermostat has a 5 minute update. 45 seconds is just dandy.

The lights and so on are never going to be an issue.

C

[therealdb]

@mikereadington not an issue for me and my wife. Both set to significant, and I rarely open the app and I can say my wife is never opening it.

I’ll soon add beacons to my cars/motorcycle because home assistant has btle relay and I’ll go with esphome. It’s capable of moving btle messages to the central location and update corresponding device. Maybe it’s achievable for you too. My use case is to open/close my car gate automatically, but my driveway is short and I can place the gateway inside the house.

[MikeReadington]

@therealdb wow, that is what I was just looking at beacons. Looks promising if they are reliable.

I don't have gates, but I would not mind a few automated defensive turrets.

[gwp1]

@mikereadington I tried beacons; was not successful.

[tamorgen]

The issue with IPhoneLocator happened to me a few months ago. @amg0 was away on vacation, and did comment that Apple may have changed the API, and it wasn’t well documented. A few days later, it started working again.

The geofencing issues in Vera, along with Ezlo’s lack of geofencing, pushed me over the edge with Vera/Ezlo. I moved over to Home Assistant a few weeks ago, along with MSR, and overall it’s been much more stable. I’m also just using Home Assistant’s built in geofencing, and it’s working well.

I still have Vera running, as I’m not 100% migrated, but I’m close.

[therealdb]

Not sure if @gwp1 was trying the new support in HASS, but I'm leaning a link anyway https://www.home-assistant.io/integrations/ibeacon