Doesn't open/close door and no error.

[betatester88]

I first tried polygon_geofence and that didn't work. I am now testing with circular _geofence to make it simple, no luck with that as well.

docker compose file:

version: "3.8"
services:
tesla-youq:
image: brchri/tesla-youq:latest
container_name: tesla-youq
environment:
- TZ=America/New_York # optional, sets timezone for container
- DEBUG=true
volumes:
- tesla-youq:/app/config # required, mounts folder containing config file(s) into container
restart: unless-stopped
volumes:
tesla-youq:

############
Get the SERIAL number.
docker run --rm -e MYQ_EMAIL=myemail@lol.com -e MYQ_PASS=myverylongQpassword brchri/tesla-youq:latest tesla-youq -d

2023/10/14 19:58:30 Acquiring MyQ session...
2023/10/14 19:58:30 Session acquired...
2023/10/14 19:58:30 Device Name: Garage Door
2023/10/14 19:58:30 Device State: open
2023/10/14 19:58:30 Device Type: virtualgaragedooropener
2023/10/14 19:58:30 Device Serial: CA07532F3A5H
2023/10/14 19:58:30 Device Name: Hub
2023/10/14 19:58:30 Device State:
2023/10/14 19:58:30 Device Type: hub
2023/10/14 19:58:30 Device Serial: GW15201C1A62
############

############

tesla-youq config.yml
global:
mqtt_host: 192.168.1.10
mqtt_port: 1883
mqtt_client_id: tesla-youq
mqtt_user: testuser
mqtt_pass: mymttpasswd
mqtt_use_tls: false
mqtt_skip_tls_verify: false
cooldown: 5
myq_email: myemail@lol.com
myq_pass: myverylongQpassword

garage_doors:
- circular_geofence: #lat/lng has been altered to mask the location
center:
lat: 40.630802
lng: -74.006189
close_distance: .012
open_distance: .02
myq_serial: CA07532F3A5H # Not the real serial number
cars:
- teslamate_car_id: 1 # id used for the vehicle in TeslaMate's MQTT broker

############

from TeslaMate/mosquitto, I can see it was connected.
1697313887: New connection from 172.20.0.1:39110 on port 1883.
1697313887: New client connected from 172.20.0.1:39110 as tesla-youq (p2, c1, k30, u'testuser').

tesla-youQ portainer output:
2023/10/14 16:20:59 Config loaded successfully
2023/10/14 16:20:59 Connected to MQTT broker
2023/10/14 16:20:59 Topics subscribed, listening for events...

Everything seems to be fine, but it doesn't appear it is triggering open/close on myQ. Are there any logs I can check to see if it was triggered? I tried DEBUG=true but the tesla-youQ output stay the same. Any help will be greatly appreciated.

[brchri]

It looks like the app isn't getting any pub/sub updates from the MQTT broker. With DEBUG=true, you'd see output anytime there was an update to one of the subscribed topics. If the app never gets any updates from MQTT, it never knows about the vehicle's location, so it never knows to try to operate the garage.

Try using a tool like MQTT Explorer to connect to your MQTT broker and make sure you're able to see data published to the teslamate topics for your car, especially latitude and longitude.

[betatester88]

Thank you for your reply. Yes, I did check and do see the data. Here is the screen shot.

[brchri]

You can use that same tool to update those mqtt values. Can you try doing so and check the youq output to see if it detects the update?

[betatester88]

I restarted the docker and then published 3 set of lat/lng using MQTT explorer to simulate coming from outside of the geofence to a spot where it should trigger the garage door. Unfortunately, no update on the output.

It doesn't look like it subscribed to any MQTT topic or a topic that doesn't exist.

Is there any way I can check if it subscribed to "teslamate/cars/1" - note, the is "s" in cars.

2023/10/15 22:05:09 Received interrupt signal, shutting down...
2023/10/15 22:05:11 Config loaded successfully
2023/10/15 22:05:11 Connected to MQTT broker
2023/10/15 22:05:11 Topics subscribed, listening for events...

[brchri]

That's hard coded in the app. This is definitely the issue, you're not getting updates from MQTT, but it's difficult to know why, all the MQTT logic happens in a package that's external to this repo. I'll get an image with some more verbose logging pushed that you can try to get some more info, but in the meantime, can you try ensuring that tesla-youq and the mqtt broker are on the same docker network, and setting the config's mqtt host to point to the docker container over that network directly? I had another user on a synology that couldn't get the mqtt broker connection to work through the host's IP for some reason and that fixed it for him, might be worth a try.

[betatester88]

Thanks for looking at this and here is bit more info. I have enabled the logging on the MQTT server. I am not seeing any subscribe request from the tesla-youQ. I also restarted the tesla-youQ just to make sure it get trigger to subscribe. Only see successful connection. Yes, both Teslamate and tesla-youq are on the same docker host.

[betatester88]

First, I would like to thank you for your time helping me out on this. I think I am making some progress. I don't know if this makes any sense. All these are new to me.
I compared my config to the example config file many times. Everything looks fine to me with some spacing differences.
The geofence block has 2 spaces at the front on my config. It does not line up with "global:" at the top of the config file.

After the changes made to the config file, now I am seeing the subscribe msg on the log.

I see it subscribe to "teslamate/cars/1/longitude" and "teslamate/cars/1/latitude" (in history)

One other question if you don't mind. Can I have only "open" in the settings without defining "close"? If possible, I would like not to auto close.

Thank you again for your help.

[brchri]

Oh interesting. Yes the spacing in the config.yml file is very important, particularly the leading spacing. That defines the dictionary that gets ingested into the config. If you didn't space properly, then it probably wasn't able to properly identify the garage configs and parameters. I'll add a check for that. Do you see updates in YouQ when you change things in the MQTT explorer now?

Regarding your question about having an option to not close, no I don't have this implemented but makes sense that it should be. Give me a day or two and I'll try and get that done so you can just have it open.

Finally, if you still need more verbose debugging, I've pushed a new docker tag you can use that should give quite a bit more info when DEBUG=true: brchri/tesla-youq:add-more-verbose-debug-logging

Hope this helps.

[betatester88]

Everything is working for me know. Thanks!
Yeah, I am a bit nervous about auto close :)

[brchri]

@betatester88 I've published a new docker image tag, allow-only-open-or-close-fences, which should allow you to omit open or close on any geofence type (obviously at least one must be defined). Feel free to give it a shot. I'll be doing some additional testing before publishing a proper release for it, but wanted to get you the initial changes if you wanted to check them out. Obvious disclaimers about changes still being tested and may be unstable apply.

[brchri]

Excellent, thanks for testing that. Things look good on my end too, so I'll probably merge it and publish a proper release for it later tonight.

[betatester88]

@brchri I saw you pushed out the latest image. I updated and using the same config.yml, but now getting this error. If I define the "close" then no error.

2023/10/16 19:27:50 error: no supported geofences defined for garage door &{ 0xc0000aa700 CA171F3A2G [0xc0000a6360] false }
myq_serial = CA171F3A2G Redacted

[brchri]

Did you make sure to do a pull after switching back to latest?

[betatester88]

Sorry, my bad. I just started with docker couple weeks ago and Portainer last week. I am a newbie on this.

Before:
image: brchri/tesla-youq:allow-only-open-or-close-fences
After:
image: brchri/tesla-youq:latest

I clicked "update the stack.

After selected the option to re-pull and redeploy that fixed the issue. I didn't recall I did this when I switched to "allow-only-open-or-close-fences" this morning. Maybe I am getting old, my RAM is not serving me well.

I also just realized that now it changed from v0.2.3 to v0.2.4.
org.opencontainers.image.version | v0.2.4

Thanks again!

[brchri]

No worries. The way docker works is when you start a container with a specific tag (such as latest), it first checks to see if you have that tag cached locally, and if so, it uses it, and if not, it pulls it from docker hub. Since you didn't have allow-only-open-or-close-fences, it pulled it, but when you swapped back to latest, it used the cached image you had from before. You have to specifically pull to update any cached image tags.

Glad you got it sorted.