Listening to the MQTT topic bares no result #2096

M-ax-G · 2021-10-25T00:44:14Z

M-ax-G
Oct 25, 2021

I installed teslamate successfully on a RaspberryPi 3B (as per instructions, script found on Git/docs).
All seems to work... and looks great too. :)

However, subscribing to mosquitto_sub -v -t teslamate/cars/# on the same machine the docker containers are running, does not produce a result. In the meantime I tried to subscribe with a host address: Examples:
# [2021-10-25 11:46] maxg@maxg-pc-mint ~ $ mosquitto_pub -h 192.168.1.62 -t teslamate/cars/test -m test
results in:
# [2021-10-25 11:46] maxg@rpi33 ~ $ mosquitto_sub -v -t teslamate/cars/# | xargs -d$'\n' -L1 sh -c 'date "+%D %T.%3N $0"'
10/25/21 11:47:12.895 teslamate/cars/test test

I subscribed to a non-existing topic on said broker and get an error (as expected); I published a message to the broker and get a proper response; telling me MQTT is working.

What am I missing (doing wrong)?
# [2021-10-25 10:41] maxg@rpi33 ~ $ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
4f63dc9a6a2f teslamate/grafana:latest "/run.sh" 21 hours ago Up 21 hours 0.0.0.0:3000->3000/tcp maxg_grafana_1
bec8a29398b8 eclipse-mosquitto:2 "/docker-entrypoint.…" 21 hours ago Up 21 hours 0.0.0.0:1883->1883/tcp maxg_mosquitto_1
5ff33783513d postgres:13 "docker-entrypoint.s…" 21 hours ago Up 21 hours 5432/tcp maxg_database_1
e73019c99660 teslamate/teslamate:latest "tini -- /bin/sh /en…" 21 hours ago Up 21 hours 0.0.0.0:4000->4000/tcp maxg_teslamate_1
I read all messages here returned when searching for 'mqtt', but did not find anything related to my question.

Answered by pmboothby

Oct 25, 2021

If there has been no activity with the car, perhaps that's why no messages. You can try running mosquitto_sub in one window and then stop/start teslamate in another.

docker-compose stop teslamate
docker-compose start teslamate

I believe that should elicit a few messages to Mosquitto (it does on my system).

View full answer

pmboothby · 2021-10-25T08:51:27Z

pmboothby
Oct 25, 2021

mosquitto_sub -v -t teslamate/cars/# should work. If mosquitto_sub is just doing nothing when you run it, then that means it's connected to the MQTT server (else you would get an error message and return to the command line). Is Teslamate successfully connected to the car? What do you get from docker-compose logs teslamate? If Teslmate has no connection to the car, or failed to connect to Mosquitto, then you should see something in the logs and mosquitto_sub won't print anything.

1 reply

M-ax-G Oct 25, 2021
Author

Thank you for your reply.

Yes, teslamate/grafana shows all the data one would expect in online/sleep mode.

The log seems a bit long to post here... well, it seems I can attach files. :)
20211025-1918_teslamate_log.txt

From what I can gather looking at the log:
The car is new, picked it upon Friday, and did not drive since I installed teslamate, other than today, where I drove; 10cm back and forth to check a tire. This was recorded in the log. Timestamps are based on UTC.

The mosquitto_sub was running during that wake-up, but sis not capture anything.

As I mentioned, I used the prescribed .yml file to install the lot (db, mosquitto, grafana and teslamate), and have not fiddled with anything, given I am new to docker.

The mosquitto log reads as follows (the 172. being from the docker, while 196.168.1.13 is my PC)
[2021-10-25 19:25] maxg@rpi33 ~ $ docker-compose logs mosquitto
Attaching to maxg_mosquitto_1
mosquitto_1 | 0: mosquitto version 2.0.12 starting
mosquitto_1 | 0: Config loaded from /mosquitto-no-auth.conf.
mosquitto_1 | 0: Opening ipv4 listen socket on port 1883.
mosquitto_1 | 0: Opening ipv6 listen socket on port 1883.
mosquitto_1 | 0: mosquitto version 2.0.12 running
mosquitto_1 | 0: New connection from 172.18.0.4:38956 on port 1883.
mosquitto_1 | 0: New client connected from 172.18.0.4:38956 as TESLAMATE_302E3734393 (p2, c1, k60).
mosquitto_1 | 0: New connection from 192.168.1.13:51150 on port 1883.
mosquitto_1 | 0: New client connected from 192.168.1.13:51150 as mosq-7EQaXA3aJb5WYKPkaB (p2, c1, k60).
mosquitto_1 | 0: Client mosq-7EQaXA3aJb5WYKPkaB disconnected.
mosquitto_1 | 0: New connection from 192.168.1.13:51178 on port 1883.
mosquitto_1 | 0: New client connected from 192.168.1.13:51178 as mosq-fQpWaEeopcNxHI9Ldw (p2, c1, k60).
mosquitto_1 | 0: Client mosq-fQpWaEeopcNxHI9Ldw disconnected.
mosquitto_1 | 0: New connection from 192.168.1.13:51204 on port 1883.
mosquitto_1 | 0: New client connected from 192.168.1.13:51204 as mosq-mSf5u8homE9Dx3WsJR (p2, c1, k60).
mosquitto_1 | 0: Client mosq-mSf5u8homE9Dx3WsJR disconnected.
mosquitto_1 | 0: New connection from 192.168.1.13:51888 on port 1883.
mosquitto_1 | 0: New client connected from 192.168.1.13:51888 as mosq-ZF30KhK7uXj3bCrN5V (p2, c1, k60).
mosquitto_1 | 0: Client mosq-ZF30KhK7uXj3bCrN5V disconnected.
mosquitto_1 | 0: New connection from 192.168.1.62:58058 on port 1883.
mosquitto_1 | 0: New client connected from 192.168.1.62:58058 as mosqsub|12350-rpi33 (p2, c1, k60).
mosquitto_1 | 0: Client mosqsub|12350-rpi33 closed its connection.
mosquitto_1 | 0: New connection from 172.18.0.1:57782 on port 1883.
mosquitto_1 | 0: New client connected from 172.18.0.1:57782 as mosqsub|12354-rpi33 (p2, c1, k60).
mosquitto_1 | 0: New connection from 192.168.1.13:51968 on port 1883.
mosquitto_1 | 0: New client connected from 192.168.1.13:51968 as mosq-BgabUuYV53daLbxSbD (p2, c1, k60).
mosquitto_1 | 0: Client mosq-BgabUuYV53daLbxSbD disconnected.
mosquitto_1 | 0: Client mosqsub|12354-rpi33 closed its connection.
mosquitto_1 | 0: New connection from 172.18.0.1:57796 on port 1883.
mosquitto_1 | 0: New client connected from 172.18.0.1:57796 as mosqsub|12369-rpi33 (p2, c1, k60).
mosquitto_1 | 0: New connection from 192.168.1.13:52010 on port 1883.
mosquitto_1 | 0: New client connected from 192.168.1.13:52010 as mosq-DnshaqlZcIqXAmdCr3 (p2, c1, k60).
mosquitto_1 | 0: Client mosq-DnshaqlZcIqXAmdCr3 disconnected.
mosquitto_1 | 0: Client mosqsub|12369-rpi33 closed its connection.
mosquitto_1 | 0: New connection from 172.18.0.1:57800 on port 1883.
mosquitto_1 | 0: New client connected from 172.18.0.1:57800 as mosqsub|12373-rpi33 (p2, c1, k60).
mosquitto_1 | 0: New connection from 192.168.1.13:52012 on port 1883.
mosquitto_1 | 0: New client connected from 192.168.1.13:52012 as mosq-SDUC4qbzm1tXcUn1IV (p2, c1, k60).
mosquitto_1 | 0: Client mosq-SDUC4qbzm1tXcUn1IV disconnected.
mosquitto_1 | 0: New connection from 192.168.1.13:52018 on port 1883.
mosquitto_1 | 0: New client connected from 192.168.1.13:52018 as mosq-vNJxIfzC2u6R5GJkfS (p2, c1, k60).
mosquitto_1 | 0: Client mosq-vNJxIfzC2u6R5GJkfS disconnected.
mosquitto_1 | 0: Client mosqsub|12373-rpi33 closed its connection.
mosquitto_1 | 0: New connection from 172.18.0.1:58360 on port 1883.
mosquitto_1 | 0: New client connected from 172.18.0.1:58360 as mosqsub|13417-rpi33 (p2, c1, k60).
mosquitto_1 | 0: Client mosqsub|13417-rpi33 closed its connection.
mosquitto_1 | 0: New connection from 172.18.0.1:58384 on port 1883.
mosquitto_1 | 0: New client connected from 172.18.0.1:58384 as mosqsub|13465-rpi33 (p2, c1, k60).
mosquitto_1 | 0: Client mosqsub|13465-rpi33 closed its connection.
mosquitto_1 | 0: New connection from 172.18.0.1:60792 on port 1883.
mosquitto_1 | 0: New client connected from 172.18.0.1:60792 as mosqsub|16685-rpi33 (p2, c1, k60).
mosquitto_1 | 0: Client mosqsub|16685-rpi33 closed its connection.
mosquitto_1 | 0: New connection from 172.18.0.1:32882 on port 1883.
mosquitto_1 | 0: New client connected from 172.18.0.1:32882 as mosqsub|16904-rpi33 (p2, c1, k60).
mosquitto_1 | 0: Client mosqsub|16904-rpi33 closed its connection.
mosquitto_1 | 0: New connection from 172.18.0.1:32888 on port 1883.
mosquitto_1 | 0: New client connected from 172.18.0.1:32888 as mosqsub|16907-rpi33 (p2, c1, k60).
mosquitto_1 | 0: Client mosqsub|16907-rpi33 closed its connection.
mosquitto_1 | 0: New connection from 172.18.0.1:32900 on port 1883.
mosquitto_1 | 0: New client connected from 172.18.0.1:32900 as mosqsub|16935-rpi33 (p2, c1, k60).
mosquitto_1 | 0: Client mosqsub|16935-rpi33 closed its connection.
mosquitto_1 | 0: New connection from 172.18.0.1:32904 on port 1883.
mosquitto_1 | 0: New client connected from 172.18.0.1:32904 as mosqsub|16937-rpi33 (p2, c1, k60).
mosquitto_1 | 0: New connection from 192.168.1.13:40840 on port 1883.
mosquitto_1 | 0: New client connected from 192.168.1.13:40840 as mosq-Itp7FSnCMjjPiaKj96 (p2, c1, k60).
mosquitto_1 | 0: Client mosq-Itp7FSnCMjjPiaKj96 disconnected.
mosquitto_1 | 0: Client mosqsub|16937-rpi33 closed its connection.

I am reading in the doc that there is an environment varibale that says:
DISABLE_MQTT | Disables the MQTT feature if true but I do not know how to check for it. Maybe it is set to true.

pmboothby · 2021-10-25T10:10:43Z

pmboothby
Oct 25, 2021

If there has been no activity with the car, perhaps that's why no messages. You can try running mosquitto_sub in one window and then stop/start teslamate in another.

docker-compose stop teslamate
docker-compose start teslamate

I believe that should elicit a few messages to Mosquitto (it does on my system).

2 replies

M-ax-G Oct 25, 2021
Author

Wow, I am learning docker here :)
The point is, I ran:
# [2021-10-25 20:47] maxg@rpi33 ~ $ docker-compose stop teslamate
Stopping maxg_teslamate_1 ... done
# [2021-10-25 20:47] maxg@rpi33 ~ $ docker-compose start teslamate
Starting teslamate ... done

and waited... 3 seconds, 5 seconds, maybe 7 seconds
and yes, there is was!! :)

[2021-10-25 20:47] maxg@rpi33 ~ $
mosquitto_sub -v -t teslamate/cars/# | xargs -d$'\n' -L1 sh -c 'date "+%D %T.%3N $0"'
10/25/21 20:47:56.977 teslamate/cars/1/model 3
10/25/21 20:47:56.993 teslamate/cars/1/version 2021.32.21
10/25/21 20:47:57.007 teslamate/cars/1/rated_battery_range_km 429.6
10/25/21 20:47:57.019 teslamate/cars/1/wheel_type StilettoRefresh19
10/25/21 20:47:57.031 teslamate/cars/1/est_battery_range_km 322.46
10/25/21 20:47:57.043 teslamate/cars/1/spoiler_type None
10/25/21 20:47:57.055 teslamate/cars/1/ideal_battery_range_km 429.6
10/25/21 20:47:57.067 teslamate/cars/1/geofence (null)
10/25/21 20:47:57.085 teslamate/cars/1/usable_battery_level 80
10/25/21 20:47:57.099 teslamate/cars/1/display_name HappyTwentyTwo
10/25/21 20:47:57.111 teslamate/cars/1/latitude -27.317339
10/25/21 20:47:57.123 teslamate/cars/1/outside_temp 24.5
10/25/21 20:47:57.135 teslamate/cars/1/healthy true
10/25/21 20:47:57.147 teslamate/cars/1/since 2021-10-25T03:12:11.052287Z
10/25/21 20:47:57.160 teslamate/cars/1/trim_badging 74D
10/25/21 20:47:57.171 teslamate/cars/1/battery_level 80
10/25/21 20:47:57.184 teslamate/cars/1/exterior_color MidnightSilver
10/25/21 20:47:57.200 teslamate/cars/1/longitude 152.370318
10/25/21 20:47:57.212 teslamate/cars/1/state asleep
10/25/21 20:47:57.224 teslamate/cars/1/inside_temp 25.8
10/25/21 20:47:57.237 teslamate/cars/1/odometer 187.37

Problem solved. This restart did it. Than you!

pmboothby Oct 25, 2021

No worries!

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Listening to the MQTT topic bares no result #2096

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 2 comments 3 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

Select a reply

Listening to the MQTT topic bares no result #2096

M-ax-G Oct 25, 2021

Replies: 2 comments · 3 replies

pmboothby Oct 25, 2021

M-ax-G Oct 25, 2021 Author

pmboothby Oct 25, 2021

M-ax-G Oct 25, 2021 Author

pmboothby Oct 25, 2021

M-ax-G
Oct 25, 2021

Replies: 2 comments 3 replies

pmboothby
Oct 25, 2021

M-ax-G Oct 25, 2021
Author

pmboothby
Oct 25, 2021

M-ax-G Oct 25, 2021
Author