Nice work!

[betatester88]

Just tested GEOGDO image and it worked for me using MQTT. I kept the same config file, although the new image config example have this.
garage_doors:

• geofence:
  type: polygon
  settings:

My current config (note: polygon_geofence) but it worked.
garage_doors:

• #main garage example
  polygon_geofence:
  open:
  - lat: 35.44322366057661
  lng: -67.56654445682832

Thanks again for your hard work.

A side note: After more tests, it seems geogdo assumed the door is opened when first boot. Trigger an update of the door status by open it via other method will sync correctly with geodgo.
While driving into geofence AND open is opened. Start geogdo container.

11/12/2023 20:53:05 [WARNING] Action and state mismatch: garage state is not valid for executing requested action; current state: opened; requested action: open

[brchri]

Interesting that your old config worked, it shouldn't be parsing that correctly. Interesting. (apologies for the changes btw, trying to make it cleaner and defining the type in the name seemed clunky)

As far as assuming opened, you said your MQTT broker doesn't retain, correct? So it's just a matter of it assuming the incorrect default? I can look at that, I don't know that I explicitly set a default assumption if it was empty so that's interesting. I'll let you know what I find.

[betatester88]

Correction, you going to hate me for this. I did change the config file to the updated format. I was looking at the text file I copied yesterday when I posted my first comment. My apologies, got confused with the one copied and the one actually on the config. I'll post if I discover anything worthwhile. Thank you!

[brchri]

Correction, you going to hate me for this.

Haha, np

I was thinking testing this as a way to contribute if/where I can.

Yeah you're providing great feedback, really appreciate it. 😄

In other words, it will always fail regardless it is attempting to close/open the door when status is null.

This is correct, if you defined a required_start_state but one isn't available on app start, it will always fail until a state is published. Could add a default_start_state or something to use if there isn't a state available on app start?

[betatester88]

I think this is only an isolated issue to me or anyone is using Adafruit. I have incorporated Arduino to trigger a 'GET' for the door status which cause a "change" with the last known value (aka re-publish) at first boot or at any MQTT reconnect. In practice, it will sync correctly. The only time it fails is when geogdo just rebooted and I happen to drive into the geofence before the 'GET' happens.

BTW, the day I test this new image was the same day my Tesla gotten the new update. It worked in the morning but failed in the afternoon. Luckily, I found the workaround with the teslamat-fork. Was thinking to ping you as fyi...but thinking that was a different project. I also realized you have that info in the following day :). I probably will ping you if I didn't see that.

From: Adafruit
Among other factors, our scale, Adafruit IO's mix of MQTT & HTTP APIs, the speed at which we’re taking in new data, and the fact that we’re already storing almost every message that is sent mean that a “simple” feature like retain becomes difficult to support without making MQTT service performance worse for everyone.

Since we don’t actually store data in the broker but at a lower level and can’t support PUBLISH retain directly, we’re proposing a different solution for the retaining problem: the /get topic modifier.

[brchri]

Nice, sounds like a good workaround. And yeah appreciate the heads up about the teslamate fork. In case you didn't see it, it looks like the author did publish a fix on the original project, but also said he's retiring and transferred the project to an org with a group of maintainers to continue the project without him going forward. I went back to the original project instead of the fork and it does appear to be working, and hopefully will now get more regular updates going forward.

[betatester88]

Thanks, I didn't see that. Let me switch back. :)