Replies: 26 comments
-
|
I'm having the same issues. Once the car starts driving Teslamate starts receiving messages it chokes on. I haven't installed the MQTT part either and have Teslamate running in docker. @adriankumpf Can you tell me what info you still need? Relevant entries from the logs Environment
|
Beta Was this translation helpful? Give feedback.
-
|
Never mind... I forgot to set DISABLE_MQTT in the env variables. @rybber78 did you perhaps forget as well? |
Beta Was this translation helpful? Give feedback.
-
|
Yup, can confirm DISABLE_MQTT=true setting fixes it. Please close. |
Beta Was this translation helpful? Give feedback.
-
|
Where did you enter this variable? |
Beta Was this translation helpful? Give feedback.
-
|
When starting the docker container, it's set as an environment variable with the -e switch. |
Beta Was this translation helpful? Give feedback.
-
Super! it finally works. Thank you |
Beta Was this translation helpful? Give feedback.
-
|
Hello,
I've tried the workaround Do you have some other ideas to fix the problem? Thank you very much. |
Beta Was this translation helpful? Give feedback.
-
|
You'll need to include a few more environment variables than just MQTT_DISABLE such as DATABASE_USER, DATABASE_PASS, etc. As seen at https://docs.teslamate.org/docs/configuration/environment_variables/. I just shortened my example down to the one variable for brevity. Each one will require its own -e switch.
docker run -e MQTT_DISABLE=true -e DATABASE_USER=the_user -e DATABASE_PASS=mypassword -e DATABASE_HOST=dbserver.org -e DATABASE_PORT=5432 -e DATABASE_NAME=mydb teslamate/teslamate:latest
There are a
If you're using the Docker compose method seen here https://docs.teslamate.org/docs/installation/docker then you'll want to add MQTT_DISABLE=true under the environment list, while removing MQTT_HOST=mosquitto.
…-------- Original Message --------
From: Strobi-Boy <[email protected]>
Sent: November 21, 2020 9:56:14 a.m. MST
To: adriankumpf/teslamate <[email protected]>
Cc: Brendan Ward <[email protected]>, Comment <[email protected]>
Subject: Re: [adriankumpf/teslamate] TeslaMate divides every drive into little parts (#1063)
Hello,
since the last Update (1.20 -> 1.20.1), I have the same problem with the devided drives.
TeslaMate version: 1.20.1
Type of installation: Docker
OS TeslaMate is installed on: RaspBerry Stretch
User OS & Browser: Windows / Firefox
I've tried the workaround
**docker run -e DISABLE_MQTT=true teslamate/teslamate:latest"**
but it didn't work with my system.
Do you have some other ideas to fix the problem?
Thank you very much.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#1063 (comment)
--
Sent from my Android device
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the fast response.
What is going wrong with my TeslaMate? Thanks for your advice. |
Beta Was this translation helpful? Give feedback.
-
|
I'm experiencing the exact same problem as Strobi-Boy with My guess is the steps should be:
But I am too new at Docker to figure out what I am doing wrong. (I'm still learning about Docker but I haven't come across the right ways to do this!) |
Beta Was this translation helpful? Give feedback.
-
|
You don't need to stop docker. Do a "docker-compose up" again after changing the file. It will update the configuration and restart any containers it needs to. |
Beta Was this translation helpful? Give feedback.
-
|
Hello, ...and restartet the Docker - but the problem with the splitted drives is already there: Do you have any more tips to solve the problem? |
Beta Was this translation helpful? Give feedback.
-
|
Do anyone has any idea, how to fix the problem? |
Beta Was this translation helpful? Give feedback.
-
|
You'll need to add some logs from your container as well as the entire compose file and your currently running docker containers (docker ps) . There's not enough information right now to help. If I had to guess one of the components is not running properly after you tried to install it twice. |
Beta Was this translation helpful? Give feedback.
-
|
Hello, This is the compose file: services: teslamate: database: grafana: mosquitto: volumes: teslamate-db: teslamate-grafana-data: mosquitto-conf: mosquitto-data: This are the runnig docker containers: pi@RaspBerryPi:~ $ docker ps |
Beta Was this translation helpful? Give feedback.
-
|
docker-comopose logs Oder |
Beta Was this translation helpful? Give feedback.
-
|
Here we go: $ docker-compose logs $ docker-compose logs -f $ docker-compose logs teslamate $ docker-compose up -d ERROR: for pi_teslamate_1 Cannot start service teslamate: driver failed programming external connectivity on endpoint pi_teslamate_1 (b96220ed3dd4368e93b52139e65a3144e0672414742b1922d10b2e0174f126d5): BiStarting pi_grafana_1 ... error ERROR: for pi_grafana_1 Cannot start service grafana: driver failed programming external connectivity on endpoint pi_grafana_1 (447f47e6bd3183c5f3589d08f686155fc05b3690fdd27435d3bfe774f3899f92): Bind for 0.0.0.0:3000 failed: port is already allocated ERROR: for pi_mosquitto_1 Cannot start service mosquitto: driver failed programming external connectivity on endpoint pi_mosquitto_1 (58423f4d4025742c9450ee87337984236f02b4dec7d4b2c17ecc694eb5f19a35): Error starting userland proxy: listen tcp 0.0.0.0:1883: bind: address already in use ERROR: for grafana Cannot start service grafana: driver failed programming external connectivity on endpoint pi_grafana_1 (447f47e6bd3183c5f3589d08f686155fc05b3690fdd27435d3bfe774f3899f92): Bind for 0.0.0.0:3000 failed: port is already allocated ERROR: for mosquitto Cannot start service mosquitto: driver failed programming external connectivity on endpoint pi_mosquitto_1 (58423f4d4025742c9450ee87337984236f02b4dec7d4b2c17ecc694eb5f19a35): Error starting userland proxy: listen tcp 0.0.0.0:1883: bind: address already in use ERROR: for teslamate Cannot start service teslamate: driver failed programming external connectivity on endpoint pi_teslamate_1 (b96220ed3dd4368e93b52139e65a3144e0672414742b1922d10b2e0174f126d5): Bind for 0.0.0.0:4000 failed: port is already allocated |
Beta Was this translation helpful? Give feedback.
-
|
No idea why drives are splitted? |
Beta Was this translation helpful? Give feedback.
-
|
If there is no possibility to fix the problem, is it possible save the TeslaMate Data and to remove the TeslaMate / Docker installation completely? |
Beta Was this translation helpful? Give feedback.
-
|
Hello,
The following logs are attached: |
Beta Was this translation helpful? Give feedback.
-
pi@raspberrypi:~ $ docker ps
|
Beta Was this translation helpful? Give feedback.
-
|
I've tried a little bit and changed the mosquitto port from 1883 to 1882 and now it seems, that it work - but not 100% correct: The old data ist gone - but the drives will be displayed correct - but without informations about the consumption: Some informations in the drive details are also missing: |
Beta Was this translation helpful? Give feedback.
-
|
@Strobi-Boy your fist issue was caused by you accidentally installing teslamate twice. The remnants of the fist installation were reserving ports which caused the second installation to fail to start properly. Your second issue seems to be caused by something holding on to the default port of mosquitto, Did you completely wipe your raspberry pi or are there still some docker images running from the previous installs? You then changed the port mapping of your MQTT container, so any connection made to 1883 from the outside is going to go to 1882. This is fine as long as you instruct the MQTT process inside the container to also bind to 1882 which I don't see you doing. Resulting in any data sent by Teslamate to mosquitto:1883 to end up in a black hole. I'm actually surprised it's not causing a fatal error in Teslamate. |
Beta Was this translation helpful? Give feedback.
-
|
In the meantime I've tried several new installations (both with stretch and buster).
Every time I first install TeslaMate and then OpenWB (to control the wallbox), TeslaMate splits the trips into small parts. How can I change the default-port of 1883 to another port (including MQTT process), so that Teslamate can work as it shoud? |
Beta Was this translation helpful? Give feedback.
-
Are you sure any traces of the old installations you tried are gone?
|
Beta Was this translation helpful? Give feedback.
-
Yes - I installed a new and fresh Buster / Stretch (FULL) with the few steps I wrote. I changed the port so 1883:1833 and started Teslamate again:
It will show this: To install OpenWB I only ran the following commands: |
Beta Was this translation helpful? Give feedback.
-
Describe the bug
Every one of my drives are divided into small parts and counted as individual drives
Expected behavior
Should be listed as one drive.
How to reproduce it (as minimally and precisely as possible):
Go driving
(I'm running on docker and did not bother installing the MQTT part...)
Relevant entries from the logs
14:22:17.846 [error] Task #PID<0.5210.0> started from #PID<0.5199.0> terminating
** (stop) exited in: GenServer.call(TeslaMate.Mqtt.Publisher, {:publish, "teslamate/cars/1/update_available", "false", [retain: true, qos: 1]}, 10000)
nction: &:erlang.apply/2
Screenshots
Data
Environment
Beta Was this translation helpful? Give feedback.
All reactions