Python Plugin: Volvo EV

[akamming]

Since every (post) function we try returns an error 500, it looks liket that someting is clearly wrong on the Volvo side, so I can report that to them.

To quote myself, It looks like Volvo has changed something at their side, because locking/unlocking the car seems to work now.

Tx, glad it works!

Unfortunately that is not the only thing Volvo changed: They also now enforce 2factor authentication. Fortunately i already built the support for that some time ago, but it more work to get the plugin up and running.

So if you get "unauthenticated" messages in the plugin logging: See the paragraph "2 Factor Authentication" in the docs (https://github.com/akamming/Domoticz_Vo ... rge_Plugin) on how to fix (basically running the authenticate.py script in the plugin directory and restart the plugin) to fix

[rensbr]

Since every (post) function we try returns an error 500, it looks liket that someting is clearly wrong on the Volvo side, so I can report that to them.

To quote myself, It looks like Volvo has changed something at their side, because locking/unlocking the car seems to work now.

Tx, glad it works!

Unfortunately that is not the only thing Volvo changed: They also now enforce 2factor authentication.

So if you get "unauthenticated" messages in the plugin logging: See the paragraph "2 Factor Authentication" in the docs (https://github.com/akamming/Domoticz_Vo ... rge_Plugin) on how to fix (basically running the authenticate.py script in the plugin directory and restart the plugin) to fix

I haven't expericied any problems, so far. But good to know that your plugin also supports 2FA now, great work!

[akamming]

I haven't expericied any problems, so far. But good to know that your plugin also supports 2FA now, great work!

Very likely that's because you are already on the latest version which support 2FA and already made the tokens persistent for a restart. But if domoticz is down for about 2 hours, you will need to re-authenticate and then you will now need to use the 2FA authorization script

[HvdW]

Since 09-10-2024 the plugin didn't update anymore.
Several times I reset the car,.... nothing
I just read the posts about 2FA and did the sequence.

Still,.... nothing
The logs:

Code: Select all

2024-10-15 11:00:59.692 Status: PluginSystem: Failed dynamic library load, install the latest libpython3.x library that is available for your platform.
2024-10-15 11:00:59.719 Status: PluginSystem: 'Volvo' Registration ignored, Plugins are not enabled.

[akamming]

Since 09-10-2024 the plugin didn't update anymore.
Several times I reset the car,.... nothing
I just read the posts about 2FA and did the sequence.

Still,.... nothing
The logs:

Code: Select all

2024-10-15 11:00:59.692 Status: PluginSystem: Failed dynamic library load, install the latest libpython3.x library that is available for your platform.
2024-10-15 11:00:59.719 Status: PluginSystem: 'Volvo' Registration ignored, Plugins are not enabled.

What is the next step?

Your error has nothing to do with 2FA.

it's in the line:

Code: Select all

2024-10-15 11:00:59.692 Status: PluginSystem: Failed dynamic library load, install the latest libpython3.x library that is available for your platform.

Domoticz doesn't load any plugins, due to the fact there is something wrong with the python library on your system...

i am not a system administrator, maybe someone else can give a clue on how to fix this... (or do a google search on this error message, it does give a lot of hits with people who have had this issue before)

[HvdW]

Problem solved:
Found this page.
Did:

Code: Select all

sudo apt-get install python3.11-dev

Why it did function normally befor the 9th of october?
No idea.

Hope this helps other in troubleshooting.

PS
Afrterwards everything gets clear.
I changed SD card for a new one, so python3.11-dev wasn't installed.
Positive:
I copied the old Domoticz directory to the new SD card as domoticz.bak directory to be able to copy domoticz.db to the newly install.
When installing Domoticz with

Code: Select all

sudo bash -c "$(curl -sSfL https://install.domoticz.com)"

to my surprise the 'Domoticz automated installer' found and used the former setup so all I had to do was nothing . Everything was back in place like before.
Everything, except python3.11-dev
Maybe the developers can add that one as well in the future like if imported plugins then install python3.11-dev

[HvdW]

The Volvo plugin offers new opportunities.
First of all it can be used to set a desired charging level.
Create a sensor , a slider to set a level from 0 to 100%
Compare the desired level with domoticz.devices('XC40-ChargeLevel').state and control when the battery charging should be stopped.

On the other hand it is nice to be able to see after how many hours and minutes the desired charging level will be reached an write this information in a Text sensor.

Code: Select all

  -------- AUTO OPLADEN  ----------------
 
        if domoticz.devices('Volvo-aangesloten').state ~= 'Disconnected' then
            carConnected = 'Connected'
        else
            carConnected = 'not Connected' 
        end
        
        if laadvermogen > 1000 then -- if charging is in progress
            laadvermogen = domoticz.devices('Laadpaal').actualWatt/1000
        else
            laadvermogen = 3600/1000  -- calculate using the max current of 16A (in my case)
        end
        -- x/1000  is Watt to kW
        
        local batteryCapacity = 79 -- kW
       
        -- laadtijd berekenen tot dynamisch
        local remainingTime = (batteryCapacity/100)*((domoticz.devices('XC40 battery charge set').levelVal - domoticz.devices('XC40-ChargeLevel').state))/laadvermogen
               
        uren, honderdsten = math.modf(remainingTime)
        minuten = honderdsten*60
        minuten = math.floor(minuten+0.5)
        
        domoticz.devices('Volvo').setIcon(107)
        domoticz.devices('Volvo').updateText('Charge level set     ' .. tostring(domoticz.devices('XC40 battery charge set').levelVal) ..'%'.. 
            '\n Charge level actual   ' .. tostring(domoticz.devices('XC40-ChargeLevel').nValue) ..'% '..
            '\n Plug connected    ' .. carConnected ..
            -- '\n Plug connected    ' .. chargingState ..
            '\n \n \n      Charging level     ' .. domoticz.devices('Charging Level').state ..
            '\n &emsp;&emsp;&emsp;&emsp; Charging state &nbsp;&emsp;&emsp;&emsp;' .. domoticz.devices('Volvo-Opladen').state ..'</font> '..
            '\n \n &emsp; Charging to '..tostring(domoticz.devices('XC40 battery charge set').levelVal)..'% : '.. tostring(uren) .. ' hours, ' .. tostring(minuten) .. ' minutes'..
            '\n &nbsp;')

[akamming]

The Volvo plugin offers new opportunities.
First of all it can be used to set a desired charging level.
Create a sensor , a slider to set a level from 0 to 100%
Compare the desired level with domoticz.devices('XC40-ChargeLevel').state and control when the battery charging should be stopped.

On the other hand it is nice to be able to see after how many hours and minutes the desired charging level will be reached an write this information in a Text sensor.

Code: Select all

  -------- AUTO OPLADEN  ----------------
 
        if domoticz.devices('Volvo-aangesloten').state ~= 'Disconnected' then
            carConnected = 'Connected'
        else
            carConnected = 'not Connected' 
        end
        
        if laadvermogen > 1000 then -- if charging is in progress
            laadvermogen = domoticz.devices('Laadpaal').actualWatt/1000
        else
            laadvermogen = 3600/1000  -- calculate using the max current of 16A (in my case)
        end
        -- x/1000  is Watt to kW
        
        local batteryCapacity = 79 -- kW
       
        -- laadtijd berekenen tot dynamisch
        local remainingTime = (batteryCapacity/100)*((domoticz.devices('XC40 battery charge set').levelVal - domoticz.devices('XC40-ChargeLevel').state))/laadvermogen
               
        uren, honderdsten = math.modf(remainingTime)
        minuten = honderdsten*60
        minuten = math.floor(minuten+0.5)
        
        domoticz.devices('Volvo').setIcon(107)
        domoticz.devices('Volvo').updateText('Charge level set     ' .. tostring(domoticz.devices('XC40 battery charge set').levelVal) ..'%'.. 
            '\n Charge level actual   ' .. tostring(domoticz.devices('XC40-ChargeLevel').nValue) ..'% '..
            '\n Plug connected    ' .. carConnected ..
            -- '\n Plug connected    ' .. chargingState ..
            '\n \n \n      Charging level     ' .. domoticz.devices('Charging Level').state ..
            '\n &emsp;&emsp;&emsp;&emsp; Charging state &nbsp;&emsp;&emsp;&emsp;' .. domoticz.devices('Volvo-Opladen').state ..'</font> '..
            '\n \n &emsp; Charging to '..tostring(domoticz.devices('XC40 battery charge set').levelVal)..'% : '.. tostring(uren) .. ' hours, ' .. tostring(minuten) .. ' minutes'..
            '\n &nbsp;')

The volvo plugin (unfortunately) does not offer support to set the target charging level (i it is wish for me to implement it, but unfortunately the functionality is not available in the Volvo API). I assume you are referring to a custom script someone made which controls the wallbox based on the SoC level which is reported by the plugin..

[HvdW]

Your assumption is correct.
I'm using the data received from the Volvo plugin about current charging level.
A slider switch in Domoticz sets the desired battery level.
SmartEVSE cuts off the charging when the reported charging level from the Volvo plugin matches the preset level from the slider.

Beforehand I used a relay like this one to switch mains to the charging box.
I have changed the charging box to be smart using a SmartEVSE device and now the charging can be started and charging current changed using MQTT.

[joostvanderlinde]

Since every (post) function we try returns an error 500, it looks liket that someting is clearly wrong on the Volvo side, so I can report that to them.

To quote myself, It looks like Volvo has changed something at their side, because locking/unlocking the car seems to work now.

Tx, glad it works!

Unfortunately that is not the only thing Volvo changed: They also now enforce 2factor authentication. Fortunately i already built the support for that some time ago, but it more work to get the plugin up and running.

So if you get "unauthenticated" messages in the plugin logging: See the paragraph "2 Factor Authentication" in the docs (https://github.com/akamming/Domoticz_Vo ... rge_Plugin) on how to fix (basically running the authenticate.py script in the plugin directory and restart the plugin) to fix

When I first saw the mention of 2FA in this thread my plugin was till working so i did not pay much attention to it.... Today I noticed the data of my my C40 devices were outdated and I noticed a 'client not authorized' in the log.
Solution was indeed pretty simple: Update the plugin and run the authorize.py script. As per https://github.com/akamming/Domoticz_Vo ... rge_Plugin

Nice!!!

[HvdW]

I just wrote some new text for my Volvo text sensor.

Code: Select all

        if domoticz.devices('Volvo-aangesloten').state ~= 'Disconnected' then
            carConnected = 'Connected'
        else
            carConnected = 'not Connected' 
        end
           if laadvermogen > 1000 then 
            laadvermogen = domoticz.devices('Laadpaal').actualWatt/1000
        else
            laadvermogen = 3600/1000  -- Watt to kWh
        end
        
        -- calculate range
        local batteryCapacity = 79 -- kW
        local certainRange = 25    -- kWh/100km
        local currentRange = math.floor((domoticz.devices('XC40-ChargeLevel').state * batteryCapacity)/certainRange)
        local expectedRange = math.floor((domoticz.devices('XC40 battery charge set').levelVal * batteryCapacity)/certainRange)
        
        
        -- laadtijd berekenen tot dynamisch
        local resttijd = (batteryCapacity/100)*((domoticz.devices('XC40 battery charge set').levelVal - domoticz.devices('XC40-ChargeLevel').state))/laadvermogen
        domoticz.log('Battery set - Battery state '..domoticz.devices('XC40 battery charge set').levelVal..' - '.. domoticz.devices('XC40-ChargeLevel').state.. 'Laadvermogen : '..laadvermogen,domoticz.LOG_DEBUG)
        -- resttijd = round(resttijd,2)
        uren, honderdsten = math.modf(resttijd)
        minuten = honderdsten*60
        minuten = math.floor(minuten+0.5)
        -- certain range based on 25 kWh/100km
        
        domoticz.devices('Volvo').setIcon(107)
        domoticz.devices('Volvo').updateText('Charge level set     ' .. tostring(domoticz.devices('XC40 battery charge set').levelVal) ..'%'.. 
            '\n Charge level actual   ' .. tostring(domoticz.devices('XC40-ChargeLevel').nValue) ..'% '..
            '\n Plug connected    ' .. carConnected ..
            -- '\n Plug connected    ' .. chargingState ..
            '\n \n \n      Expected range    ' .. expectedRange ..' km '..
            '\n      Current range     ' .. currentRange ..' km'..
            '\n \n   Charging to '..tostring(domoticz.devices('XC40 battery charge set').levelVal)..'% : '.. tostring(uren) .. ' hours, ' .. tostring(minuten) .. ' minutes'..
            '\n  ')
     

Up till now it displayed Charging state and Set charging state.

volvo.jpg (16.82 KiB) Viewed 697 times

It now displays Expected Range and Actual Range as well.
Range is calculated using an electricity consumption of 25 kWh/100 km which is based on the Spritmonitor consumption.
In summer our Volvo uses 23 kWh/100 km, in winter 25 kWh/100 km

[rensbr]

Updated the plugin today and runt the script, works like a charm with my EX30 now, thanks! @akamming

[HvdW]

On tweakers I saw this:

Code: Select all

 "data": [
        {
            "command": "LOCK_REDUCED_GUARD",
            "href": "/v2/vehicles/vin/commands/lock-reduced-guard"
        },
        {
            "command": "LOCK",
            "href": "/v2/vehicles/vin/commands/lock"
        },
        {
            "command": "UNLOCK",
            "href": "/v2/vehicles/vin/commands/unlock"
        },
        {
            "command": "HONK",
            "href": "/v2/vehicles/vin/commands/honk"
        },
        {
            "command": "HONK_AND_FLASH",
            "href": "/v2/vehicles/vin/commands/honk-flash"
        },
        {
            "command": "FLASH",
            "href": "/v2/vehicles/vin/commands/flash"
        },
        {
            "command": "CLIMATIZATION_START",
            "href": "/v2/vehicles/vin/commands/climatization-start"
        },
        {
            "command": "CLIMATIZATION_STOP",
            "href": "/v2/vehicles/vin/commands/climatization-stop"
        }
    ]
}

Flash & Honk

[FireWizard]

Hi @HvdW,

You can easily check, what commands are supported by your car, by querying the following endpoint:

https://api.volvocars.com/connected-veh ... >/commands

This will return an array of objects. Each element in the array will list the specific command and its endpoint.

For flash and honk it is:

https://api.volvocars.com/connected-veh ... honk-flash

Regards

[akamming]

On tweakers I saw this:

Code: Select all

 "data": [
        {
            "command": "LOCK_REDUCED_GUARD",
            "href": "/v2/vehicles/vin/commands/lock-reduced-guard"
        },
        {
            "command": "LOCK",
            "href": "/v2/vehicles/vin/commands/lock"
        },
        {
            "command": "UNLOCK",
            "href": "/v2/vehicles/vin/commands/unlock"
        },
        {
            "command": "HONK",
            "href": "/v2/vehicles/vin/commands/honk"
        },
        {
            "command": "HONK_AND_FLASH",
            "href": "/v2/vehicles/vin/commands/honk-flash"
        },
        {
            "command": "FLASH",
            "href": "/v2/vehicles/vin/commands/flash"
        },
        {
            "command": "CLIMATIZATION_START",
            "href": "/v2/vehicles/vin/commands/climatization-start"
        },
        {
            "command": "CLIMATIZATION_STOP",
            "href": "/v2/vehicles/vin/commands/climatization-stop"
        }
    ]
}

Flash & Honk

This was my own message on tweakers (and already implemented flash-honk). So if you update to latest version it should work. (although it does require OTA update 3.3.16 on several cars before it works)