sage wing Jun 7, 2024, 10:08 AM

#

What do you mean "variables"?

#

Nothing in https://github.com/Flodu31/HomeAssistant-PeugeotIntegration#configuration mentions a location

plush herald Jun 7, 2024, 10:13 AM

#

In the PSA Car Controller it pulls the car last location, i can see in the plugin where the car is right now, so it seems to have that information. I just need to create a connection between them

sage wing Jun 7, 2024, 10:15 AM

#

What do you mean plugin?

#

Do you mean the add-on?

#

If yes, whenever you respond, then you need to check if the API provides that location

#

    resource: http://IPofTheSoftware:5000/get_vehicleinfo/YourVIN?from_cache=1

#

If that doesn't show it then there's nothing you can do

plush herald Jun 7, 2024, 10:18 AM

#

The Add-On PSA Car Controller (plugin) provides on a map where the car is

sage wing Jun 7, 2024, 10:18 AM

#

That's not a plugin

#

There's no such thing as plugins

#

They're called add-ons

#

https://www.home-assistant.io/docs/glossary/

Home Assistant

Glossary

Home Assistant's Glossary.

#

Yes, the words you use matter 😉

plush herald Jun 7, 2024, 10:20 AM

#

Okay so now we've confirmed i'm taking about the add-on and not plugin, is there a way?

sage wing Jun 7, 2024, 10:20 AM

#

That PSA aside: #1248578514962219139 message

plush herald Jun 7, 2024, 10:21 AM

#

I need to find out how it descripes that geo-location and then i can (assumably) create a sensor for it?

sage wing Jun 7, 2024, 10:21 AM

#

Yes, though it's not going to be trivial

#

First you need to get the data

#

Then you'll have to create a dummy device_tracker and use the device_tracker.see service or create an MQTT device tracker and publish the location to MQTT

plush herald Jun 7, 2024, 10:23 AM

#

If i look back at the github i should be able to go into the PSA Car Controller and find the location call and what its assigned too?

sage wing Jun 7, 2024, 10:25 AM

#

#1248578514962219139 message

#

Click that 😉

#

plush herald Jun 7, 2024, 10:31 AM

#

I can see a last_position sensor in there

sage wing Jun 7, 2024, 10:31 AM

#

And does that have a lat and long, or a word, or...?

plush herald Jun 7, 2024, 10:32 AM

#

Co-ords 0,1,2 with what looks like lat/long

#

So yes

sage wing Jun 7, 2024, 10:32 AM

#

Then you'll have to create a dummy device_tracker and use the device_tracker.see service or create an MQTT device tracker and publish the location to MQTT

plush herald Jun 7, 2024, 10:32 AM

#

Okay i'll go look it up and see what i can do

sage wing Jun 7, 2024, 10:33 AM

#

  - service: device_tracker.see
    data:
      dev_id: "car_gps"
      gps_accuracy: "10"
      gps:
        - "{{ latitude template }}"
        - "{{ longitude template }}"

#

Having created car_gps in known_devices.yaml and restarted HA

#

car_gps:
  icon:
  mac:
  name: car gps
  picture:
  track: true

plush herald Jun 7, 2024, 10:38 AM

#

Won't it need to call the information from the url?

#

device_tracker:
name: corsa_e
resource: http://censored:5000/get_vehicleinfo/censor?from_cache=1

#

"last_position": {"type": "Feature", "geometry": {"coordinates": [-1.21465, 54.55443, 29.0], "type": "Point"}

sage wing Jun 7, 2024, 10:41 AM

#

Ok... you need a sensor with the lat and long

#

Then you need the service call above and a #templates-archived to pull the lat and long

#

There is no restful device trackerr

#

So, baby steps

#

First you need to get the data

#

Do that

plush herald Jun 7, 2024, 10:53 AM

#

Okay so if i stick this in the sensors.yaml

    name: corsa_e
    resource: http://censor:5000/get_vehicleinfo/censored?from_cache=1
    scan_interval: 60
    timeout: 30
    value_template: 'OK'
    json_attributes:
    -last_position
- platform: template
    sensors:
    corsa_e_latitude:
    friendly_name: "Latitude"
    value_template: '["last.position"]["geometry"]["coordinates"]["0"]'
    sensors:
        corsa_e_longitude:
        friendly_name: "Longitude"
        value_template: '["last.position"]["geometry"]["coordinates"]["1"]'```

#

That hopefully will get the data from the json

#

then i can use the corsa_e_latitude in place like this

    data:
      dev_id: "car_gps"
      gps_accuracy: "10"
      gps:
        - "corsa_e_latitude"
        - "corsa_e_longitude"```

#

Would that work?

sage wing Jun 7, 2024, 10:59 AM

#

No

#

First, you need actual templates in the service call

#

Second, you've mashed a template sensor and rest sensor together without understanding what's going on

plush herald Jun 7, 2024, 11:00 AM

#

sage wing Second, you've mashed a template sensor and rest sensor together without underst...

Completely agree i'm still learning how to do this

#

but i think i'm starting to understand how it work (a little)

sage wing Jun 7, 2024, 11:02 AM

#

  - platform: template
    sensors:
      corsa_e_latitude:
        friendly_name: "Corsa E Lat"
        value_template: '{{ states.sensor.corsa_e.attributes["last.position"]["geometry"]["coordinates"]["0"] }}'
      corsa_e_longitude:
        friendly_name: "Corsa A Long"
        value_template: '{{ states.sensor.corsa_e.attributes["last.position"]["geometry"]["coordinates"]["1"] }}'

#

(probably)

#

Then

  - service: device_tracker.see
    data:
      dev_id: "car_gps"
      gps_accuracy: "10"
      gps:
        - "{{ states('sensor.corsa_e_latitude') }}"
        - "{{ states('sensor.corsa_e_longitude') }}"

#

(probably)

#

#templates-archived can help you with templates if you get stuck

#

Remember that last piece is a service call that doesn't go in the sensor definition

plush herald Jun 7, 2024, 11:04 AM

#

Okay, great help me understand this... how does HA know where to find the last.position, do it just know that because its been called from else where in the yaml

sage wing Jun 7, 2024, 11:04 AM

#

You'll use that service in an automation that's called when the lat/long changes

sage wing Jun 7, 2024, 11:05 AM

#

plush herald Okay, great help me understand this... how does HA know where to find the last.p...

Hopefully it's in the JSON

#

You may have to add last.position to the JSON attributes

#

You can also massively improve what's in https://github.com/Flodu31/HomeAssistant-PeugeotIntegration#configuration by moving to https://www.home-assistant.io/integrations/rest

plush herald Jun 7, 2024, 11:24 AM

#

Just restarted HA after adding the sensor but its showing as status Unavaliable

sage wing Jun 7, 2024, 11:47 AM

#

Go back and do all the troubleshooting steps again

plush herald Jun 7, 2024, 12:15 PM

#

Got it pulling the information now, templates channel helped me. Thanks again for all the help

#

I'm trying to add - service: device_tracker.see data: dev_id: "car_gps" gps_accuracy: "10" gps: - "{{ states('sensor.corsa_e_latitude') }}" - "{{ states('sensor.corsa_e_longitude') }}" to a yaml file but its asking for a platform

sage wing Jun 7, 2024, 12:28 PM

#

Remember that last piece is a service call that doesn't go in the sensor definition
You'll use that service in an automation that's called when the lat/long changes

#

(from above)

#

Also see #1248578514962219139 message

plush herald Jun 7, 2024, 12:35 PM

#

I've created the known_devices.yaml, do i need to reference that in the configuration.yaml?

sage wing Jun 7, 2024, 12:36 PM

#

No

#

Just write that automation, triggered by the state change of those two sensors

plush herald Jun 7, 2024, 12:46 PM

#

I'm creating the automation now...
When corsa e lat or corsa e long changes state or any attributes as the 'When'
Then do ' Call a service 'Device Tracker: See'

#

Manually ran the automation and got this error must contain at least one of mac, dev_id

pale sphinxBOT Jun 7, 2024, 12:49 PM

#

Sadly we're not mind readers (any more anyway, not after the last time we tried). Please share the YAML and any errors so we can see what you've done.

plush herald Jun 7, 2024, 12:50 PM

#

description: ""
trigger:
  - platform: state
    entity_id:
      - binary_sensor.corsa_e_lat
      - binary_sensor.corsa_e_long
condition: []
action:
  - service: device_tracker.see
    data: {}
mode: single```

sage wing Jun 7, 2024, 12:51 PM

#

Ok...

#

Did you look at that before posting it?

plush herald Jun 7, 2024, 12:51 PM

#

Its my first time creating a automation (hell its my first time for a lot of things today)

sage wing Jun 7, 2024, 12:52 PM

#

Did you look at that before posting it?

#

Did you compare the service call to what I posted? Hell, to what you posted?

plush herald Jun 7, 2024, 12:53 PM

#

I used the visual builder when i did, maybe i should stick to the yaml file and i might have seen something

sage wing Jun 7, 2024, 12:53 PM

#

  - service: device_tracker.see
    data: {}

vs

  - service: device_tracker.see
    data:
      dev_id: "car_gps"
      gps_accuracy: "10"
      gps:
        - "{{ states('sensor.corsa_e_latitude') }}"
        - "{{ states('sensor.corsa_e_longitude') }}"

plush herald Jun 7, 2024, 12:55 PM

#

Okay, lets go back to me being an idoit here as I don't understand. I created the known_devices.yaml and put the - service: device_tracker.see data: dev_id: "car_gps" gps_accuracy: "10" gps: - "{{ states('sensor.corsa_e_latitude') }}" - "{{ states('sensor.corsa_e_longitude') }}" code into it

sage wing Jun 7, 2024, 12:55 PM

#

What?

#

Dude

#

Dude!

sage wing · 2024-06-07T10:08:55.578Z

Tinkerer, following on about the PSA Car | Home Assistant | Page 1

plush herald Jun 7, 2024, 12:56 PM

#

Having created car_gps in known_devices.yaml and restarted HA

sage wing Jun 7, 2024, 12:56 PM

#

car_gps:
  icon:
  mac:
  name: car gps
  picture:
  track: true

plush herald Jun 7, 2024, 12:56 PM

#

sage wing Having created `car_gps` in `known_devices.yaml` and restarted HA

This section

sage wing Jun 7, 2024, 12:56 PM

#

car_gps:
  icon:
  mac:
  name: car gps
  picture:
  track: true

plush herald Jun 7, 2024, 12:56 PM

#

Ah so you meant the top part in the known_devices not the bottom part

sage wing Jun 7, 2024, 12:56 PM

#

this3

#

Other way around

plush herald Jun 7, 2024, 12:57 PM

#

Ignore me i read the whole thing wrong!

#

Sorry absolute idoit here

sage wing Jun 7, 2024, 12:57 PM

#

's fine

#

Just ... start paying attention when the error appears

#

When that happens, look at what I wrote, and what you have

plush herald Jun 7, 2024, 12:59 PM

#

Okay so... i don't get this wrong and look even worse... i've gone into the automation (yaml editor) should i just copy and paste what you have or does it need the tigger part as well. Like this ```alias: Corsa E GPS Change
description: ""
trigger:

platform: state
entity_id:
- binary_sensor.corsa_e_lat
- binary_sensor.corsa_e_long
  condition: []
  action:
service: device_tracker.see
data:
dev_id: "car_gps"
gps_accuracy: "10"
gps:
- "{{ states('sensor.corsa_e_latitude') }}"
- "{{ states('sensor.corsa_e_longitude') }}"
mode: single```

sage wing Jun 7, 2024, 12:59 PM

#

Close

#

binary_sensor.corsa_e_lat is wrong

#

Those have to be sensor

#

binary_sensor.corsa_e_lat is on/off

#

The templates have to match the entity

plush herald Jun 7, 2024, 1:00 PM

#

and of course the gps coordinates would never be 1 or 0

#

description: ""
trigger:
  - platform: state
    entity_id:
      - sensor.corsa_e_lat
      - sensor.corsa_e_long
condition: []
action:
  - service: device_tracker.see
    data:
      dev_id: "car_gps"
      gps_accuracy: "10"
      gps:
        - "{{ states('sensor.corsa_e_latitude') }}"
        - "{{ states('sensor.corsa_e_longitude') }}"
mode: single```

sage wing Jun 7, 2024, 1:01 PM

#

Nope

#

sensor.corsa_e_lat vs sensor.corsa_e_latitude

#

(etc)

plush herald Jun 7, 2024, 1:06 PM

#

I can't see a way for it to accept vs in the yaml... just errors

sage wing Jun 7, 2024, 1:06 PM

#

Dude

#

sensor.corsa_e_lat

or

sensor.corsa_e_latitude

#

one's wrong

pale sphinxBOT Jun 7, 2024, 1:07 PM

#

Developer tools: states

Open your Home Assistant instance and show your state developer tools

sage wing Jun 7, 2024, 1:07 PM

#

Look there

plush herald Jun 7, 2024, 1:12 PM

#

Amusing i wasn't answering here from the same network as my home assistant panel, but i worked out where you wanted me to go!

#

Corsa E Lat
    -1.21465     friendly_name: Corsa E Lat
sensor.corsa_e_longitude
Corsa E Long
    54.55443     friendly_name: Corsa E Long```

#

Wiped out the _ in the copy and paste

#

description: ""
trigger:
  - platform: state
    entity_id:
      - sensor.corsa_e_latitude
      - sensor.corsa_e_longitude
condition: []
action:
  - service: device_tracker.see
    data:
      dev_id: car_gps
      gps_accuracy: "10"
      gps:
        - "{{ states('sensor.corsa_e_latitude') }}"
        - "{{ states('sensor.corsa_e_longitude') }}"
mode: single

#

I saw what i did wrong! I removed the binary. from the start of the entity_id and didn't think the none binary sensors had a wrong name

#

different name ( i need some sleep obviously!)

sage wing Jun 7, 2024, 1:16 PM

#

Now try that and see if it works

pale sphinxBOT Jun 7, 2024, 1:16 PM

#

To test an automation there's three stages you can follow. Testing the action, the condition and action, and the whole automation:

Use Configuration -> Automations to find the automation and then select Run in the three dots menu. If this fails your problem is in the action: section, and details should be found in your log file
Use Developer tools -> Services and call automation.trigger on the automation with skip_condition: false. If the first passes but this fails then the problem is in your condition: block
Use Developer tools -> States to find the trigger entity, click the name, then change the state (at the top) to something that'll trigger the automation before pushing Set State. If this fails then the problem is with your trigger: section, or the automation is turned off (you can check that in Automations, automations that are turned off will show Disabled)

You can also see this section in the docs about testing and automation traces.

plush herald Jun 7, 2024, 1:17 PM

#

Result:

params:
  domain: device_tracker
  service: see
  service_data:
    dev_id: car_gps
    gps_accuracy: '10'
    gps:
      - -1.21465
      - 54.55443
  target: {}
running_script: false```

#

ran no problem! Phew

sage wing Jun 7, 2024, 1:20 PM

#

Now look at States for device_tracker.car_gps

plush herald Jun 7, 2024, 1:21 PM

#

I've got it on the map! Discovered something the 1 and 0 should be the other way round as the car is the middle of the Indian Ocean according to the map 😛

#

Just off the coast of the Seychelles

#

Sorted. I really appreciate all your help Tinkerer

#

Sent donation your way

#

If i want to add an image of the car to the map, i assume i just edit the known_devices.yaml and add the location of the file to the picture: line?

sage wing Jun 7, 2024, 1:46 PM

#

As a URL path

plush herald Jun 7, 2024, 1:47 PM

#

i've created www folder and uploaded the file to there so it'll just be /www/corsa.jpg

sage wing Jun 7, 2024, 1:48 PM

#

No

pale sphinxBOT Jun 7, 2024, 1:48 PM

#

HTTP

Offers a web framework to serve files.

Quality scale

:house: Internal

IoT Class

Local Push

Integration type

system

Documentation

View the documentation

Source

View the source on GitHub

Issues

View known issues

plush herald Jun 7, 2024, 1:49 PM

#

Okay so i have to use the full url, thanks

sage wing Jun 7, 2024, 1:49 PM

#

No

plush herald Jun 7, 2024, 1:49 PM

#

I'm reading the wrong thing then... 5 minutes

sage wing Jun 7, 2024, 1:49 PM

#

/local/corsa.jpg

plush herald Jun 7, 2024, 2:01 PM

#

I'm assuming if i want too do this for the cupra its pretty similar (however it already has a device_tracker.cupra_born_tracker)

sage wing Jun 7, 2024, 2:01 PM

#

Yes

plush herald Jun 7, 2024, 2:22 PM

#

Cool one last thing, went i reboot HA it looses the car position. I manually run the automation and it comes back, anyway to make it run more frequently or on restart?

#Tinkerer, following on about the PSA Car

Dude!