-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
pkeller
Member
pkeller
Member
From the Teslamate Home page (4000)
----------------------------------------
Lucille
Model Y LR AWD
| Status | falling asleep for 2 min |
| Range (rated) | 181.1 mi |
| Range (est.) | 169.1 mi |
| State of Charge | 56% (57%) |
| Outside Temperature | 58.1 °F |
| Inside Temperature | 60.3 °F |
| Mileage | 4413 mi |
| Version | 2021.44.30.5 |
So the temps are getting recorded, but just not showing on the Overview graph? Let me delve deeper into the SQL for that query. I know it doesn't report if the data is too old, but that didn't seem to be the issue for you. Back soon.
pkeller
Member
Thanks for your effort(s).
As a foot note, The temps were showing correctly until about a week ago when I update the SW to 2021.44.30.5. About that time they disappeared along with any and all data (charge, temp, SW revision, mileage etc. I first noticed that he SW version was not shown but I have seen that before so I did not take particular notice. A couple of days ago I did a pull to make sure all was current. No help. Backed-up to 1.25.0 and most of the data reappeared. Not in the data base (there is a hole of about 6 days) but current data was there except for the temps.
Wonder if it is an API bug with the FSD beta branch. Can you poll the API and see if it is reporting it? You said the TeslaMate webpage was reporting temperatures?
I updated today from Buster to Bullseye on a PI 4.
I only had to manually delete /etc/systemd/system/dhcpcd.service.d/wait.conf to get dhcp running again.
You can see the discussion at Dhcpcd5 broken in bullseye.
I only had to manually delete /etc/systemd/system/dhcpcd.service.d/wait.conf to get dhcp running again.
You can see the discussion at Dhcpcd5 broken in bullseye.
pkeller
Member
Not exactly sure what you are wanting me to do. The Teslamate page is able to display the temps, current software version, status (sleep, online etc) and status of the windows (vent) accurately.
You gave me enough information in the bolded part, that is what I was after. I will leave it back in @init6 hands to see if they can dig through the SQL dashboards and provide more information. Might not hurt to open an issue on the GitHub repository too.
The first thing to note is that the Overview graph does not display the Temperature data all the time. It looks at the Position table and the Charges table to see when the last record that contains a temperature was recorded in either table. If that record is over 60 minutes ago it will display "No Data". From what I've read there is an assumption that the temp an hour ago is probably not a good indicator of what the temp is now. It's an arbitrary time value.
So you need to check the overview page within 1 hour of having charged or driven the car to be sure that it is updating properly. If you still see no data we can delve a bit further or as @cwanja has suggested, raise an issue on the GitHub page. No reason not to do both.
The rest of this posting is my best guess at how it works based on what I have observed. If someone knows more about how this all hangs together then feel free to correct me.
Why does the Teslamate Homepage show the temperature but the Overview doesn't? It's probably worth looking at how these elements work together.
Tesla sends a stream of data. Teslamate reads this stream and displays some of the data on the homepage and simultaneously records the data in the database. Grafana produced reports based on whatever data is in the database. (I'm a bit unsure of how this Teslamate Homepage is created but this is my best guess)
As I said earlier Grafana gets the data from the positions or charges tables. If the positions or charges tables are not updated then after an hour, the overview dashboard will disregard the data. I think this is what is happening here. I don't know the precise criteria for updating the positions table, but I can see that if I wake my car from a sleep I get 2 records when the car is woken, but nothing else is added while the car is just sitting there. That sort of makes sense as you'd soon fill up your database if you recorded every piece of data even if the car is not moving. You'd have a DB full of position records containing pretty much the same data. That could explain why the TM home pages displays temp, but it is not being recorded in the DB.
For example I woke my car at 13:57 and the car then fell asleep at 14:23. I only have two entries in the positions table for that period. One at 13:57 and one at 14:00. Nothing after that. I would therefore need to have looked at the Overview dashboard before 15:00 (60 minutes after my last record) to see any data, even though the car was still showing as awake until 14:23. To repeat, it's 60 minutes from the last record which is not necessarily the last time Teslamate recorded the car as being awake. (I suspect Teslamate has some form of timeout before it records the car as being asleep.)
Hope that helps.
So you need to check the overview page within 1 hour of having charged or driven the car to be sure that it is updating properly. If you still see no data we can delve a bit further or as @cwanja has suggested, raise an issue on the GitHub page. No reason not to do both.
The rest of this posting is my best guess at how it works based on what I have observed. If someone knows more about how this all hangs together then feel free to correct me.
Why does the Teslamate Homepage show the temperature but the Overview doesn't? It's probably worth looking at how these elements work together.
Tesla sends a stream of data. Teslamate reads this stream and displays some of the data on the homepage and simultaneously records the data in the database. Grafana produced reports based on whatever data is in the database. (I'm a bit unsure of how this Teslamate Homepage is created but this is my best guess)
As I said earlier Grafana gets the data from the positions or charges tables. If the positions or charges tables are not updated then after an hour, the overview dashboard will disregard the data. I think this is what is happening here. I don't know the precise criteria for updating the positions table, but I can see that if I wake my car from a sleep I get 2 records when the car is woken, but nothing else is added while the car is just sitting there. That sort of makes sense as you'd soon fill up your database if you recorded every piece of data even if the car is not moving. You'd have a DB full of position records containing pretty much the same data. That could explain why the TM home pages displays temp, but it is not being recorded in the DB.
For example I woke my car at 13:57 and the car then fell asleep at 14:23. I only have two entries in the positions table for that period. One at 13:57 and one at 14:00. Nothing after that. I would therefore need to have looked at the Overview dashboard before 15:00 (60 minutes after my last record) to see any data, even though the car was still showing as awake until 14:23. To repeat, it's 60 minutes from the last record which is not necessarily the last time Teslamate recorded the car as being awake. (I suspect Teslamate has some form of timeout before it records the car as being asleep.)
Hope that helps.
I did the same update, and I wish I saw your post earlier. Took me all night to get my pihole to work again (I'm not technical). Funny enough I was only able to get it going again thanks to that discussion. Bullseye installs connmand which used one of its ports.
Are you charging / have you charged since then? Just look at the data above.
Cardo
Active Member
For those struggling with the latest version of TeslaMate on a Raspberry Pi, this is also a good guide for upgrading from Buster to Bullseye. There’s a couple extra steps mentioned that aren’t covered in the TomsHardware guide.
blues.io
The Idiot-Proof Guide to Upgrading Raspberry Pi from Buster to Bullseye
Learn how to perform an in-place upgrade of your Raspberry Pi OS from Buster to Bullseye.
blues.io
Short charging session and the data is displayed. To me, the Overview dashboard seems to be working as intended @pkeller.
Similar threads
