Configured geofence 'Home' (id: 1) has a cost per unit set which will prevent TeslaMateAgile from working properly

[thunder2k]

Hi,
I'm seeing this error in the logs.

These are the relevant configs from the yaml file:
- TeslaMate__UpdateIntervalSeconds=300
- TeslaMate__GeofenceId=1
- TeslaMate__EnergyProvider=FixedPrice
- FixedPrice__TimeZone=Etc/UTC # IANA (tz database) time zone code, used for below times
- FixedPrice__Prices__0=23:16-08:16=0.0523 # Night
- FixedPrice__Prices__1=08:16-23:16=0.1818 # Day

This is my geo-fence config in teslamate:

I'm running teslmate 1.26.1.

Any help is appreciated.

Thanks!

[MattJeanes]

Hey, you need to unset the cost for the geofence in TeslaMate for TeslaMateAgile to work correctly, as per the warning

[thunder2k]

Hi,
thanks for clarifying this. The way I interpreted it was that the cost format was somehow wrong! Maybe you can add it explicitly, something like: "Make sure the cost for the geofence is empty in teslamate!"
Thanks for the prompt reply, the error is not gone! Out of curiosity, is this a recent change? I have had this configured for ages now and never noticed this kind of error and the calculations were being performed correctly!

[MattJeanes]

Yeah it's just a warning as if TeslaMate calculates your charge TeslaMateAgile will ignore it, so we warn users to turn off this feature. That's a good idea for updating the message I think you're right in that it's not clear enough. You need to set it to blank instead of zero, here's what mine looks like which works without warning:

[thunder2k]

Makes total sense! Happy I've helped with my feedback! Btw I made a typo before, I meant "The error is NOW gone!", so we're good! Thanks again and keep up the good work!

[MattJeanes]

Oh, that makes more sense haha! I've updated the warning which will go out whenever I release a new update (I won't do one just for that!):

Configured geofence '{geofence.Name}' (id: {geofence.Id}) should not have a cost set in TeslaMate as this may override TeslaMateAgile calculation

Hopefully that one is clearer, I'm open to feedback!