Congratulation to Robin for a job well done with the Network Map extension. I have it working flawlessly with the instructions provided.
I am new to HA and have no experience in javascript or python but it seems to me that one feature that is missing in the network map extension is the ability to rename devices in the map to meaningful names. I found an openhab forum article by Andreas Brett showing how to do this Openhab but am unable to translate this to my hassio Home Assistant instance.
It can be done elsewhere in the ha interface though.
I haven’t done this yet, but it looks as if you can rename devices from within Z2M’s config.
there is some info on this page.
https://www.zigbee2mqtt.io/configuration/configuration.html
@asyscom Sorry - I don’t know whether switching to dev will require pairing all devices again or not. It should be ok but…
Thanks for the pointer Kris,
I could see from the z2m log in the hassio\add-ons\zigbee2mqtt console that Z2M was loading a file configuration.yaml from the /share/zigbee2mqtt folder but couldn’t see this folder in my WinSCP view which made me wonder if this was a relative path. Not so, once I restarted the FTP add-on with protected mode off and reconnected with WinSCP I could see this folder and the configuration.yaml file. I then proceeded to make the edits as suggested in documention link you sent.
configuration.yaml:
devices: devices.yaml
homeassistant: true
mqtt:
base_topic: zigbee2mqtt
password: xxxxxxxx
server: mqtt://homeassistant
user: MQTTuser
permit_join: false
serial:
disable_led: true
port: /dev/ttyACM0
and created devices.yaml:
'0x00158d000233767a':
friendly_name: 'office_wireless_switch'
retain: true
'0x00158d0002f2a338':
friendly_name: 'office_motion_sensor'
retain: true
'0x00158d00030a51ab':
friendly_name: 'elec_blanket_pwr_plug'
retain: true
'0x00158d00032d38fc':
friendly_name: 'bed_lamps_plug'
retain: true
'0x00158d000396ada9':
friendly_name: 'wir_ceiling_light'
retain: true
'0x00158d0003cf65de':
friendly_name: 'office_ceiling_light'
retain: true
After restarting Z2M and regenerating the network map the friendly names were displayed:
.
Have you dev version of Z2M? Because in my map there is a bug, between coordinator and router (xioami plug)there is only a line and not 2, and all end point devices connect with router are not displayed as connect but online without lines
No, I am running the release version 1.4.0.
After adding more devices I too am seeing this behaviour.
What is “this”.
The behaviour mentioned by ASYSCOM. ie. Devices that are obviously connected because they are responding to commands but are showing as not connected in the network map.
It seems that the network mapping is not 100% correct. Obviously it seems to have improved, but I think that we have to accept it as imperfect at this stage.
I am currently running this component as per instructions above and it works flawlessly. I am considering moving to HACS, but does anyone know if this component is available in HACS or can run in parallel? When looking at the instructions, I see the specific remark in HACS that custom component needs to be deleted:
"Moving from custom_updater
If you have custom_updater installed you need to remove that (rename the directory or delete it completely). You will also need to remove the custom_updater entry from your configuration.yaml file.
HACS and custom_updater can not operate on the same installation."
I have HAC’s installed. Although I’ve not installed anything from it’s list of installable add-ons. Still reading on there usage.
However, Z2M mapper is not on the list. As of this writing.
So you have HACS and zigbee map running at the same time?
Yes, why wouldn’t you?
Yes.
And it’s working well.
However. I assume I’ll need to change that when this is ready.
hey,
i am interested in changing the friendly names rather than the original alpha-numeric names. But, when i attempted this in the past it messed up the pairing and i list control of them and had to re-flash my coordinator. i really don want to have to do this again.
did changing the friendly name using your method change the behaviour or anything of the devices/addon/network?
thanks
No. It seems as, under the hood Hass handles real name and friendly name seamlessly.
I see that Akriss has already replied. I comply with his assessment. No other change is evident.
I did notice however that you must now use the friendly name to remove the device using the method described in the documentation. MQTT topics and message structure | zigbee2mqtt.io
Thanks to both of you
