Any option to change the CustomName?

[HectorDRR]

Hi;
Very interesting this project. A long time ago I was looking a way to include my own sensors in the display and finally I found this project and it works in a very easy way.
I use node-red in the Venus-GX to control my domotic installation so it has been very easy to make a flow to add the value of my Sanitary Hot Water to the display, but it appears under the 'My temperature Sensor' name.
I've tried to send, in the initialization JSON, a CustomName value with the name I want, ACS (SHW translated to Spain) but it didn't work.
I've removed the device form the VRM and initialised again, but no luck.
is supported to include CustomName in the initialise command?
This is the payload I send:
{"clientId":"TPlaca","connected":1,"CustomName":"ACS","version":"v1.0","services":{"t1":"temperature"}}

I've tried to change it in the service.yml, restart the service but the log says:

2025-02-14 14:56:52.753044500 INFO:device_service:Registering service temperature for client TPlaca at path com.victronenergy.temperature.mqtt_TPlaca_t1
2025-02-14 14:56:53.634943500 INFO:settingsdevice:Setting /Settings/MqttDevices/mqtt_TPlaca_t1/CustomName does not exist yet or must be adjusted
2025-02-14 14:56:54.303655500 INFO:settingsdevice:Setting /Settings/MqttDevices/mqtt_TPlaca_t1/TemperatureType does not exist yet or must be adjusted
2025-02-14 14:56:54.786350500 INFO:settingsdevice:Setting /Settings/Devices/mqtt_TPlaca_t1/ClassAndVrmInstance does not exist yet or must be adjusted
2025-02-14 14:56:55.217303500 WARNING:vedbus:USING OUTDATED REGISTRATION METHOD!
2025-02-14 14:56:55.222076500 WARNING:vedbus:Please set register=False, then call the register method after adding all mandatory paths. See https://github.com/victronenergy/venus/wiki/dbus-api
2025-02-14 14:56:55.252679500 INFO:vedbus:registered ourselves on D-Bus as com.victronenergy.temperature.mqtt_TPlaca_t1
2025-02-14 14:56:55.425332500 INFO:device_service:Registered Service com.victronenergy.temperature.mqtt_TPlaca_t1 under DeviceInstance 1
2025-02-14 14:56:55.446318500 INFO:device_manager:publish {'portalId': 'xxxxxx', 'deviceInstance': {'t1': 1}, 'topicPath': {'t1': {'N': 'N/xxxxxx/temperature/1', 'R': 'R/xxxxxx/temperature/1', 'W': 'W/xxxxxx/temperature/1'}}} to device/TPlaca/DBus, status is 0
2025-02-14 14:56:55.515215500 INFO:device_service:Setting changed, setting: CustomName, old: My Temperature Sensor, new: My Temperature Sensor
2025-02-14 15:03:06.477965500 INFO:device_proxy:Processing device proxy message from TPlaca: {'topicPath': 'W/xxxxxx/temperature/1', 'values': {'Temperature': 48}}
2025-02-14 15:03:06.484624500 INFO:device_proxy:1 proxy message(s) sent on behalf of TPlaca

Thanks so much for the software.

[freakent]

Hi,

It's not supported in the registration message as there are two existing ways to do this:

1. go into your Venus GX device console UI, choose Settings > Device List > [device name] > Device > Name and change the name here (this is what I do)

This is the equivalent page on my Ekrano for a Ruuvi tag.

2. Try publishing a message to W/xxxxxx/temperature/1/CustomName with "value: "[new name]"

I hoipe this helps.

[HectorDRR]

Thanks for the reply. I've not thinked about something such simple as you suggest.
I've do it the way you suggest and it works perfectly.
Thanks again :)