- Naming schema
- Adding new devices
The default names generated by Home Assistant are unsustainable in the long term and hard to work with. This is how I tediously work around them
$placementis optional and used when needed. examples:
If there are more than one type of sensor in a location, they are named in one of the following ways:
And then they get all grouped or templated together into a single
it is often the group/template that it makes sense to show on dashboard and build automations with.
A (non-exhaustive) list of diferent
radar: mmWave presence detection
motion: PIR sensors, motion detectors and "moving target" on mmWave sesors
door: a magnetic/hall/reed/window sensor affixed to a door.
window: same, but affixed to a window
tamper: tamper detection, commonly found on various Z-Wave sensors
|Default name||Naming standard|
Additionally I create derivative sensors:
They are good for spotting devices that are wrongly configured to send too many reports.
First we need to get the device to join the Zigbee network. These devices are not very standardized in how they join a network, and are very picky about distance from the controller. Sometimes there are instructions in Zigbee2mqtt's Device page but not always. Aside from the devices manual, it's a good place to start looking.
Once the device has joined, rename it from the default
0x.. name. The
friendly_name and id are stored in the
file (using config as storage..). Since i manage this with ansible, i
add something like this to the inventory variable
ansible will template it into
'0x70ac08fffeb4cd10': friendly_name: light_livingroom_plants
Protip: the web ui has a "Update Home Assistant entity ID" toggle, which defaults to
Now the device is in Home Assistant, with a mostly-correct name, but
entity_ids are wrong and need to be redefined in Home Assistant.
|default name||naming standard|
Zigbee devices dont expose a lot of entities.