Domoticz

Thanks! I’m glad you like my work! Thanks for the suggestions, they are welcome additions and I will work on them!

Hi MrHobbes74,
Thanks for the great work!
I look forward to setting it up... but will need to upgrade my Raspbian & Domoticz to the latest versions before though...
We were several people from a Tesla french forum to discuss about it but we did not have much time to make it a reality!
Now I guess we are numerous to have much more time for this kind of things...
Nice job anyway

cr1cr1 wrote: ↑Saturday 28 March 2020 13:16 Hi MrHobbes74,
Thanks for the great work!
I look forward to setting it up... but will need to upgrade my Raspbian & Domoticz to the latest versions before though...
We were several people from a Tesla french forum to discuss about it but we did not have much time to make it a reality!
Now I guess we are numerous to have much more time for this kind of things...
Nice job anyway

Thanks! It was two months of well spent work Well yes, since we are all at home these days, now is the perfect time to upgrade your RPi!

BTW, I wrote a post with all the steps I went through when I upgraded my Domoticz system.
It is hre :
https://www.domoticz.com/forum/viewtopi ... 76#p231476

Hello,
Your plug-in is a very good initiative!
Is it possible to change details without waiting for a new update?
For example :
The location distance. My car is in my garage and from time to time it is noted "not at home" ...
Change alert messages to personalize them (I'm French -;))
Access the odometer, to calculate the average speed?
Thank you for your work.

marcus54 wrote: ↑Monday 06 April 2020 17:39 Hello,
Your plug-in is a very good initiative!
Is it possible to change details without waiting for a new update?
For example :
The location distance. My car is in my garage and from time to time it is noted "not at home" ...
Change alert messages to personalize them (I'm French -;))
Access the odometer, to calculate the average speed?
Thank you for your work.

Hi! Glad you like the Tesla hardware! It’s not a plug-in, but part of the native domoticz application. Right now the hardware does not support a custom command yet, so you can’t extend it yourself.

The location problem you can solve by changing the location in Domoticz settings to the location in your garage (e.g. what the Tesla indicates in the logging).
Its not possible to change alert messages yet...parts are hard coded and parts are coming from the Tesla itself.
Regarding the ODO meter, I’m currently extending the hardware to add the car’s total distance driven, and to set the charge limit. Average speed is not a feature I would pursue...that requires minute by minute update while driving and cost a lot of battery. And it will not allow the car to sleep at all.

MrHobbes74 wrote: ↑Monday 06 April 2020 19:43 The location problem you can solve by changing the location in Domoticz settings to the location in your garage (e.g. what the Tesla indicates in the logging).

Perhaps you could consider that if the Tesla is less than xx (xx= 100?) meters away from the Domoticz location, it is home ???

Thank you for your reply.

I really like the new Tesla hardware extension! Thanks for that!
One feature I would like to see is some kind of track administration. Don't need it for my taxes but would like to have some insights on the tracks with data like starting point, end point, starting time, end time (duration), km's, energy used.
Keep up the good work!

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 Mr Hobbes

Great work on the Tesla Hardware module. Any idea when you'll have time to code the "setting of the charge limit" ?

We have solar panels and when the Powerwalls have been filled I'd like to set the charge limit on the car (currently not possible) and start the car charging (possible now).

Or some workaround to do that at the moment would be great too.

Well done and thanks again for your hard work !!!

dp

maloesa wrote: ↑Tuesday 07 April 2020 11:35 I really like the new Tesla hardware extension! Thanks for that!
One feature I would like to see is some kind of track administration. Don't need it for my taxes but would like to have some insights on the tracks with data like starting point, end point, starting time, end time (duration), km's, energy used.
Keep up the good work!

For just logging, there are already many solutions, like TeslaFi or TeslaScope. These give great insight in charging, driving tracks, speeds, consumption, battery etc. It would be lots of work trying to rebuild that.

nigels0 wrote: ↑Friday 10 April 2020 2:02 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!

dpdpkpcom wrote: ↑Friday 10 April 2020 15:40 Hi Mr Hobbes

Great work on the Tesla Hardware module. Any idea when you'll have time to code the "setting of the charge limit" ?

We have solar panels and when the Powerwalls have been filled I'd like to set the charge limit on the car (currently not possible) and start the car charging (possible now).

Or some workaround to do that at the moment would be great too.

Well done and thanks again for your hard work !!!

dp

Hi! Thanks!
I’m currently working on the option to set a charge limit.
Can’t tell when it’s finished, it’s not that straightforward with the available device templates that are available in domoticz.
Hopefully there will be an update soon!

Bikey wrote: ↑Friday 10 April 2020 16:05

maloesa wrote: ↑Tuesday 07 April 2020 11:35 I really like the new Tesla hardware extension! Thanks for that!
One feature I would like to see is some kind of track administration. Don't need it for my taxes but would like to have some insights on the tracks with data like starting point, end point, starting time, end time (duration), km's, energy used.
Keep up the good work!

For just logging, there are already many solutions, like TeslaFi or TeslaScope. These give great insight in charging, driving tracks, speeds, consumption, battery etc. It would be lots of work trying to rebuild that.

I agree, this goes beyond the scope of this module in domoticz context. There are probably wonderful other apps available for this!

oliviers wrote: ↑Monday 06 April 2020 20:36

MrHobbes74 wrote: ↑Monday 06 April 2020 19:43 The location problem you can solve by changing the location in Domoticz settings to the location in your garage (e.g. what the Tesla indicates in the logging).

Perhaps you could consider that if the Tesla is less than xx (xx= 100?) meters away from the Domoticz location, it is home ???

I did that. Not sure if it’s 100 meters but it’s a range around the domoticz location.
But still the easiest is to park the car home, get the location from the logging, and set that as home location in Domoticz. It solves all problems

MrHobbes74 wrote: ↑Sunday 12 April 2020 15:59 I did that. Not sure if it’s 100 meters but it’s a range around the domoticz location.
But still the easiest is to park the car home, get the location from the logging, and set that as home location in Domoticz. It solves all problems

OK, thanks. I will do that.

MrHobbes74 wrote: ↑Sunday 12 April 2020 15:52

dpdpkpcom wrote: ↑Friday 10 April 2020 15:40 Hi Mr Hobbes

Great work on the Tesla Hardware module. Any idea when you'll have time to code the "setting of the charge limit" ?

We have solar panels and when the Powerwalls have been filled I'd like to set the charge limit on the car (currently not possible) and start the car charging (possible now).

Or some workaround to do that at the moment would be great too.

Well done and thanks again for your hard work !!!

dp

Hi! Thanks!
I’m currently working on the option to set a charge limit.
Can’t tell when it’s finished, it’s not that straightforward with the available device templates that are available in domoticz.
Hopefully there will be an update soon!

By the way: a workaround could be that you charge only a max amount of time. You can set a fixed charge limit in the Tesla app, and if you can figure out the charge rate from your batteries, and when the power walls are full, charge for a fixed set of hours (via a dzVents script), or until the fixed charge limit is reached.

MrHobbes74 wrote: ↑Sunday 12 April 2020 18:12

MrHobbes74 wrote: ↑Sunday 12 April 2020 15:52

dpdpkpcom wrote: ↑Friday 10 April 2020 15:40 Hi Mr Hobbes

Great work on the Tesla Hardware module. Any idea when you'll have time to code the "setting of the charge limit" ?

We have solar panels and when the Powerwalls have been filled I'd like to set the charge limit on the car (currently not possible) and start the car charging (possible now).

Or some workaround to do that at the moment would be great too.

Well done and thanks again for your hard work !!!

dp

Hi! Thanks!
I’m currently working on the option to set a charge limit.
Can’t tell when it’s finished, it’s not that straightforward with the available device templates that are available in domoticz.
Hopefully there will be an update soon!

By the way: a workaround could be that you charge only a max amount of time. You can set a fixed charge limit in the Tesla app, and if you can figure out the charge rate from your batteries, and when the power walls are full, charge for a fixed set of hours (via a dzVents script), or until the fixed charge limit is reached.

To figure out what I really need to make, I have some questions about what you want to do with the charge limit. I could only understand you want to set it to 100% (to make fully use of the sun when your powerwalls are full). Is that correct? Or do you want to choose between a range of 50-100%? Usually the charge limit is set to 90% (default value). If you want to charge less, you can write a script to stop charging when your desired percentage is reached. Only if you want to charge more, you would need to be able to set it to max.

Can you explain your use cases if it deviates from this?

Hello, I have a question:
The vehicle is home, I have set the "Active Interval" to 5 minutes: 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)