Custom object with custom attributes

[CoolS2 (Alex Reid)]

How do I make my own object with its own attributes?

For example, I made my arduino device, with a gps module, which calculates the location. And with the help of mobile internet to send data to HA.

HA has an api that allows me to save a value for the object with a POST request.

Eventually, I want to create my own object, a “car” that has a lng, lat, datetime property. To which to assign these values and display on the map. How can I do it?

[Troon]

It’s an “entity” you want, rather than an “object”.

If you’re using the API, here’s an example of an entity I create that has a bunch of attributes:

How can I populate Sensors from HTTP GET parameters

I’d assumed just a plain sensor via the API. As an example, here’s a bash script I run on my church’s Ubiquiti US-24-250W network switch to the public IP of my HA (via a Linode reverse proxy): #!/bin/sh while true do export HALLT="MY_LONG_LIVED_TOKEN" export TEMP="`swctrl env show | head -1 | cut -d: -f2 | sed 's/\ //'`" export FAN="`swctrl env show | grep "Fan-1" | tr -s ' ' | cut -d\ -f3`" export POE="`swctrl poe show | tr -s ' ' |grep "\ On\ " | cut -d\ -f2,10 | sed 's/\ /…

To display the entity on the map, you’d need to create a device_tracker:

Device tracker

…and an automation that triggers off any changes to the lat/long of your entity and updates the device tracker. An example of this:

Binary sensor template as device tracker (and attributes issues)

This is off-topic for your actual question, but hopefully helpful. To do the actual device_tracker job — in my case, for my car — I do the following: Entry in known_devices.yaml (docs): leaf: name: LEAF icon: mdi:car-electric track: true Automation to manually update the device_tracker entity with separately-available lat/long: - alias: LEAF - update device tracker description: Keep the device tracker aligned to the lat/long for zoning. id: UNIQUE_ID_HERE trigger: - platfo…

[CoolS2 (Alex Reid)]

Thank you for your reply. I have looked at quite a few different solutions, but some are already outdated and depreciated, for example, known_devices.yaml.

In the official documentation for device_tracker in the example the netgear platform.

# Example configuration.yaml entry for Netgear device
device_tracker:
  - platform: netgear
    host: IP_ADDRESS
    username: YOUR_USERNAME
    interval_seconds: 10
    consider_home: 180
    new_device_defaults:
      track_new_devices: true

But I don’t understand which platform I need to use for my case?

[Troon]

known_devices.yaml still works fine. It’s just not used by new integrations, but you’re not writing an integration.