Running latest docker 'dev' version.
I've set the entity naming convention of 'zwave_%nid_%o', but when I add a name and location (to be sent as part of the info), it renames the entities too?
I'd expect that the name and location appears in the dashboard and is sent when the option 'include node info', but the entities follow the naming convention set...
I've set the entity naming convention of 'zwave_%nid_%o', but when I add a name and location (to be sent as part of the info), it renames the entities too?
Yes but you need to rediscover all nodes or restart the application (by save settings again for example) in order to get all the entities updated
I do that, but that's the issue. When I rediscover them it adds the name and location to the entity name - I expect it shouldn't, as I've set a naming convention I want respected?
When I rediscover them it adds the name and location to the entity name
@billiaz ?
@Swiftnesses Currently this is how it works, which probably is not right.
The entity name on your example should be: zwave_<1-255>_
I will check what breaks on rediscovery! even though I did not have any issue to this!
Two questions
Thanks
Maybe would be useful to see the actual gateway settings?
also could be. I will test this on my nodes now!
Will perform a rediscover node and see if this happens, as I use different than standard naming setup
Tested:
In my latest dev (yesterday build) I do not face this on non CustomDevices
I'm not convinced this is fixed, either that or my expectations are not aligned with how it should work.

As you can see, the MQTT topic still includes the location:

As does the entity name:

The entities themselves look fine:

What I 'expect' is that the node topics, the entity name and entities all follow the naming convention, but the node location and name get included in the entity info (which I use for tracking). Note: ignore the fact they're blank on the below screenshot, they work fine (just a bad example!).

I can see you disabled the Use entity names instead of numericIDs
I will check code if there is something there, not respected.
@Swiftnesses I do not understand your second and third screenshots, where these come from, they are so well cropped i need more details.
Sorry @billiaz - 2nd screenshot is showing the mqtt topic, the 3rd shows the entity in Home Assistant.
I found where is happening. I will create a patch for this @robertsLando will need to review with me the solution.
Thank you :)
@Swiftnesses if you can compile the branch: fix-hass_ignoreLoc
it would be helpful to get your point of view
Done
Just reployed the dev docker and this looks fixed. Awesome work guys - thank you!