Tesla hardware module

[MrHobbes74]

Hello, I have a question:
The vehicle is home, I have set the "Active Interval" to 5 minutes:
Capture39.JPG

But, despite that, it looks like the "Tesla hw" is still polling the car every minute, as I can see from the log:

2020-04-15 11:03:25.456 Status: Tesla: Executing command: Get Awake state
2020-04-15 11:04:26.385 Status: Tesla: Executing command: Get Awake state
2020-04-15 11:05:27.302 Status: Tesla: Executing command: Get Awake state
2020-04-15 11:06:29.604 Status: Tesla: Executing command: Get Awake state
2020-04-15 11:07:30.507 Status: Tesla: Executing command: Get Awake state
2020-04-15 11:08:31.433 Status: Tesla: Executing command: Get Awake state
2020-04-15 11:09:32.357 Status: Tesla: Executing command: Get Awake state

Is this normal ?
Best regards,
Oliviers
(I tried to reboot the RPI, that didn't change anything)

Hi! Yes, the awake check is always done every minute. This doesn’t drain battery, and is the only api call that works during sleep and doesn’t wake up the car. I will add this to the wiki.

[oliviers]

Hi! Yes, the awake check is always done every minute. This doesn’t drain battery, and is the only api call that works during sleep and doesn’t wake up the car. I will add this to the wiki.

Thanks for the clarification. No worry, thus !

[nigels0]

Hi,

Just got a model 3 and this was just what I was looking for!

I have one issue though; the car is being charged (via a mains cable, not a charger) and the car will not wake up to respond to status requests (I have the time set to 20 mins for when the car is away from home and not charging). This seems different to the wiki.

Secondly, could there be an option to reduce the amount of messages going into the log? It’s difficult to find other things as this is so wordy. Maybe a configurable option on the hardware definition?

Regards

Hi! Glad you appreciate the module! Regarding your problem: Is your car detected to be home when you are charging? The module can only detect that you are charging and keep the car awake when it’s already awake AND home. If the car is asleep, a charging cannot be detected (unless it wakes up). In case you charge while not at home, the update is still only every 20 minutes (if not asleep). Home detection is important here, so please check the log.

There is currently no setting to change the log. You know you can filter on other things when you want to look for other things? I use it a lot to diagnose a certain hardware, just filter on that hardware.

Good luck!

Yes, car is at home in the log, and charging, but still asleep.

WRT the logs, the status log is really too frequent. While I can filter, it makes it rather difficult to just glance at the status tab and see that all is well. I think the polling status message is not needed as it would throw an error if it wasn’t doing it - and that would justify filling up the logging.

[MrHobbes74]

Hi,

Just got a model 3 and this was just what I was looking for!

I have one issue though; the car is being charged (via a mains cable, not a charger) and the car will not wake up to respond to status requests (I have the time set to 20 mins for when the car is away from home and not charging). This seems different to the wiki.

Secondly, could there be an option to reduce the amount of messages going into the log? It’s difficult to find other things as this is so wordy. Maybe a configurable option on the hardware definition?

Regards

Hi! Glad you appreciate the module! Regarding your problem: Is your car detected to be home when you are charging? The module can only detect that you are charging and keep the car awake when it’s already awake AND home. If the car is asleep, a charging cannot be detected (unless it wakes up). In case you charge while not at home, the update is still only every 20 minutes (if not asleep). Home detection is important here, so please check the log.

There is currently no setting to change the log. You know you can filter on other things when you want to look for other things? I use it a lot to diagnose a certain hardware, just filter on that hardware.

Good luck!

Yes, car is at home in the log, and charging, but still asleep.

WRT the logs, the status log is really too frequent. While I can filter, it makes it rather difficult to just glance at the status tab and see that all is well. I think the polling status message is not needed as it would throw an error if it wasn’t doing it - and that would justify filling up the logging.

And what is your time set for update when charging?

[nigels0]

Default interval is 20 minutes.

[MrHobbes74]

Default interval is 20 minutes.

And active interval?

[nigels0]

Ah, 1 minute for that.

[MrHobbes74]

I guess if the car is already asleep before you start charging it via the cable, it may not wake up. In that case the hardware has no way to detect it. But once it has detected a charging session, it won’t let the car go to sleep if your active interval is 1 minute.

[Bikey]

What should be the effect of changing the "Active Interval" time? Because I saw so many messages I have set it to 2 minutes, but it looks like this has no effect. I still see messages requesting the awake state every minute, and sometimes even more frequent, and even more other "Get Charge State" messages in between:

Code: Select all

2020-04-26 13:00:33.091 Status: Tesla: Executing command: Get Awake state
2020-04-26 13:00:34.319 Tesla: Car is awake
2020-04-26 13:00:34.319 Status: Tesla: Executing command: Get Charge state
2020-04-26 13:00:35.871 (TeslaModel3) General/Percentage (TeslaModel3 Battery Level)
2020-04-26 13:01:34.870 Status: Tesla: Executing command: Get Awake state
2020-04-26 13:01:36.310 Tesla: Car is awake
2020-04-26 13:02:36.319 Status: Tesla: Executing command: Get Awake state
2020-04-26 13:02:37.737 Tesla: Car is awake
2020-04-26 13:02:38.738 Status: Tesla: Executing command: Get Awake state
2020-04-26 13:02:40.144 Tesla: Car is awake
2020-04-26 13:02:40.144 Status: Tesla: Executing command: Get Charge state
2020-04-26 13:02:41.831 (TeslaModel3) General/Percentage (TeslaModel3 Battery Level)
2020-04-26 13:03:40.823 Status: Tesla: Executing command: Get Awake state
2020-04-26 13:03:42.271 Tesla: Car is awake
2020-04-26 13:04:42.279 Status: Tesla: Executing command: Get Awake state
2020-04-26 13:04:43.713 Tesla: Car is awake
2020-04-26 13:04:44.714 Status: Tesla: Executing command: Get Awake state
2020-04-26 13:04:46.069 Tesla: Car is awake
2020-04-26 13:04:46.070 Status: Tesla: Executing command: Get Charge state
2020-04-26 13:04:47.797 (TeslaModel3) General/Percentage (TeslaModel3 Battery Level)
2020-04-26 13:05:46.807 Status: Tesla: Executing command: Get Awake state
2020-04-26 13:05:48.057 Tesla: Car is awake

And this is after setting the interval to 3 minutes (and filtering in the log for "Get Charge state"):

Code: Select all

2020-04-26 13:13:19.360 Status: Tesla: Executing command: Get Awake state
2020-04-26 13:13:21.623 Status: Tesla: Executing command: Get Awake state
2020-04-26 13:14:21.415 Status: Tesla: Executing command: Get Awake state
2020-04-26 13:15:22.687 Status: Tesla: Executing command: Get Awake state
2020-04-26 13:16:24.120 Status: Tesla: Executing command: Get Awake state
2020-04-26 13:16:26.545 Status: Tesla: Executing command: Get Awake state
2020-04-26 13:17:28.593 Status: Tesla: Executing command: Get Awake state
2020-04-26 13:18:29.898 Status: Tesla: Executing command: Get Awake state
2020-04-26 13:19:31.140 Status: Tesla: Executing command: Get Awake state
2020-04-26 13:19:33.396 Status: Tesla: Executing command: Get Awake state
2020-04-26 13:20:35.139 Status: Tesla: Executing command: Get Awake state

[oliviers]

Hi,
I have asked the same question, and the developper has answered. Pls check in the messages above.

[Bikey]

Oh, excuse me I see, the interval is set all commands except the "Get Awake state" as this doesn't wake up the car.
So not a big problem, although - even if this does not wake the car - I don't think it is good practice to poll an API (and use resources) if this is not needed.

[MrHobbes74]

The reason this is done is to detect a car wake up, so that events are logged when they should be logged (e.g to detect when you wake up the car to leave the house, or when charging starts when the car was asleep. This makes event changes accurate, while otherwise you have to wait max the default interval (Which can be a long time) before anything is detected. Other apps that monitor the cars status also use this specific api call every minute.

Also this way you can see when your car wakes up because of an external event (eg someone tries to open the door, or sentry is active). At those moments, the car wakes up and changes the status.

[MrHobbes74]

Hi,

Just got a model 3 and this was just what I was looking for!

I have one issue though; the car is being charged (via a mains cable, not a charger) and the car will not wake up to respond to status requests (I have the time set to 20 mins for when the car is away from home and not charging). This seems different to the wiki.

Secondly, could there be an option to reduce the amount of messages going into the log? It’s difficult to find other things as this is so wordy. Maybe a configurable option on the hardware definition?

Regards

Hi! Glad you appreciate the module! Regarding your problem: Is your car detected to be home when you are charging? The module can only detect that you are charging and keep the car awake when it’s already awake AND home. If the car is asleep, a charging cannot be detected (unless it wakes up). In case you charge while not at home, the update is still only every 20 minutes (if not asleep). Home detection is important here, so please check the log.

There is currently no setting to change the log. You know you can filter on other things when you want to look for other things? I use it a lot to diagnose a certain hardware, just filter on that hardware.

Good luck!

Yes, car is at home in the log, and charging, but still asleep.

WRT the logs, the status log is really too frequent. While I can filter, it makes it rather difficult to just glance at the status tab and see that all is well. I think the polling status message is not needed as it would throw an error if it wasn’t doing it - and that would justify filling up the logging.

In my next update I will remove the every minute awake state log, so you will only see logging when actually something happens

[Bikey]

That is a good compromise:-) Thanks for your great work!

[nigels0]

Hi! Glad you appreciate the module! Regarding your problem: Is your car detected to be home when you are charging? The module can only detect that you are charging and keep the car awake when it’s already awake AND home. If the car is asleep, a charging cannot be detected (unless it wakes up). In case you charge while not at home, the update is still only every 20 minutes (if not asleep). Home detection is important here, so please check the log.

There is currently no setting to change the log. You know you can filter on other things when you want to look for other things? I use it a lot to diagnose a certain hardware, just filter on that hardware.

Good luck!

Yes, car is at home in the log, and charging, but still asleep.

WRT the logs, the status log is really too frequent. While I can filter, it makes it rather difficult to just glance at the status tab and see that all is well. I think the polling status message is not needed as it would throw an error if it wasn’t doing it - and that would justify filling up the logging.

In my next update I will remove the every minute awake state log, so you will only see logging when actually something happens

Appreciated!

[MrHobbes74]

Hi all, a new version of the module is integrated [2012.2 beta build 12004].
- added odometer
- added switch to set the charge level to max (on) or default (off)
- added alert to warn you off open windows/trunks/doors/unlocked car
- removed excessive logging while nothing is being done except polling (for wakeup detection)

If you want all these nice features, make sure you update to [2012.2 beta build 12004 or higher]!

[Bikey]

Nice!
Would it in a next release also be possible to set the charge level at an specific % like in the Tesla App?

And what I really would like if I could set the Amperage for the charging so I can make my own load balancing solution (currently only switching on/off depending Solar power). Is that functionality available in the Tesla API?

[MrHobbes74]

Nice!
Would it in a next release also be possible to set the charge level at an specific % like in the Tesla App?

And what I really would like if I could set the Amperage for the charging so I can make my own load balancing solution (currently only switching on/off depending Solar power). Is that functionality available in the Tesla API?

Setting the specific % is not easy, I have struggled with this for a long time. The current widgets do not support this well. That’s why I came up with the switch to set to 100%. That way, you can write your own scripts around the battery device (in dzVents) to stop charging when your desired percentage is reached.

I think setting amperage is possible in the Api. I may have a look at it for a next release.

[Bikey]

Setting the specific % is not easy, I have struggled with this for a long time. The current widgets do not support this well.

Perhaps you can use a multi-level switch with predefined levels for e.g. 50,60,70,80,90,100% for this?

[MrHobbes74]

Setting the specific % is not easy, I have struggled with this for a long time. The current widgets do not support this well.

Perhaps you can use a multi-level switch with predefined levels for e.g. 50,60,70,80,90,100% for this?

I tried that. But what if you use the Tesla app to put it on 76%? That doesn’t fit these discrete steps. It’s not water tight and I don’t see the use case as you can solve everything with scripts, and that’s what domoticz is for. I assume you don’t want to do everything manually, so what’s the difference between a script that sets the desired limit, or a script that stops charging at the desired limit? Both achieve the same goal, and you can do the latter already.