Z2M changing tcp address in config? Socket error SLZB-06

Configuration Zigbee
1

I am seeing the oddest behaviour that I suspect is something silly I’m doing. I am installing an SLZB-06 on an existing system that previously had a ZigStar coordinator. Everything is latest version as of this morning. I am using the Z2M config copied from the SLZB-06 web config page, which includes the actual ip address 192.168.1.16 (so I’m not using mDNS discovery). Z2M fails with a socket not found error, but it references 192.168.1.2. When I go back to the Z2M configuration.yaml sure enough the port: line has changed to tcp:192.168.1.2 etc. I have changed it back, rebooted HA, confirmed the change has held and then tried to again to start Z2M only for it again to be changed to 192.168.1.2! I feel like I am in Alice in Wonderland territory at this stage :slight_smile: Note it doesn’t seem to be picking up a backup copy of configuration.yaml, if I make a multiline change it only changes the ip address.

Any ideas? Is there any known circumstances in which Z2M would change the port: tcp address?

2

Figured it out - and yes I was indeed doing something silly (ish!). The created config from the SLZB-06 webpage is actually telling you exactly what to do, but I didn’t follow it exactly. It has a comment at the start saying it is best to edit the Z2M config directly in the YAML file rather than using the add-on configuration settings page. I was doing that, using the file editor add on to directly edit the config file. But then I looked again at the comment - it says to directly edit the yaml file by clicking the three dots menu from the add on configuration page. Ahhh! Surely that wouldn’t make any difference?! But it does! I don’t fully understand what is happening here, the file I get to via the 3 dots isn’t the same config file I am editing directly via file editor. It doesn’t have the full setup (a blank MQTT section for example). Anyways, it worked! And the new configurator fixes the problem I was having! So all good :slight_smile: