Comments (10)
Do you mean to the Device's description?
Device name you can specify in the configuration (Sunsynk/Deye/My inverter etc). Today it always adds the serial nubmber to that description
Why would you want to hide it?
from sunsynk.
mainly because I already had them configured like this without the name of the device in front, anyway it doesn't matter anymore I have modified the name showed so I will not suffer any more changes in future updates.
The thing about adding the name and the serial number in the entity_id of the sensors only started to happen in the last update
Now:
sensor.sunsynk_inverter_2112086414_pv1_power
Before:
sensor.pv1_power
from sunsynk.
Only noticed this today for the first time
It seems to be a change in the way HA assigns friendly_name: https://www.home-assistant.io/integrations/mqtt/#naming-of-mqtt-entities
The entity is a member of a device and entity.name is not None: friendly_name = f"{device.name} {entity.name}"
The device.name today is f"{MANUFACTURER} Inverter {SERIAL}"
. That should probably change to either just MANUFACTURER
, or introduce a new NAME
in settings.
Related to this is the entity_name, the entity.name should NOT include the SENSOR_PREFIX
(as is the case today). Sensor prefix was meant for the entity_id, which seem to be the entity_object_id - so need to introduce entity.object_id = f"SENSOR_PREFIX {sensor.name}"
Comments welcome
from sunsynk.
Now I have everything configured again with the new entity ID, when I have a while I'll try adding a prefix to see if it replaces all that or simply adds it, I'll comment when I try it, thanks for your answer, you have a prefix ? With what id do your sensors appear?
from sunsynk.
he device.name today is
f"{MANUFACTURER} Inverter {SERIAL}"
. That should probably change to either justMANUFACTURER
, or introduce a newNAME
in settings.
Sounds good. It should be an option in settings for each inverter. I.e I used to have INV1 PV1 Power, INV2 PV1 Power etc. Now it is 'Deye Inverter 734243290 PV1 Power'
I would like to be able to enter NAME: INV1, NAME: INV2... settings for each inverter
Or someone else might want to enter NAME: Sunsynk Inverter L1, NAME: Sunsynk Inverter L2, NAME: Sunsynk Inverter L3
from sunsynk.
Today we have ha_prefix
per inverter and manufacturer
as global setting. Can we work with these 2 only, or would you want a different name&ha_prefix per inverter. One for the entity object IDs and one for the pretty display
my preference is to have only the ha_prefix
from sunsynk.
It would be great if it could be customized to that level, manufacturer + num. serial is too long. I would prefer that adding the prefix overrides the global configuration and does not add a manufacturer.
Thanks for your attention!
from sunsynk.
Today we have
ha_prefix
per inverter andmanufacturer
as global setting. Can we work with these 2 only, or would you want a different name&ha_prefix per inverter. One for the entity object IDs and one for the pretty displaymy preference is to have only the ha_prefix
You're right I forgot about the ha_prefix
For me just having ha_prefix & sensor_definition would work. The friendly name is important to some because voice assistants etc use it. It would be a pain if Home Assistant kept setting it back to some long string like it is now.
from sunsynk.
In any case, from your comment I understand that the id of the entity does not depend on your complement, but on the global configuration of Home assistant. I attached a screenshot so that it is completely clear what id I mean. If so, we can consider this petition closed and, as always, thanks for your work Kellerza, you have more and more followers in Spain!.
from sunsynk.
Using just ha_prefix
(per inverter) and manufacturer
(global), I get the following
here you see the entity_id = sensor.ss_battery_current
and the name = SS Battery power
(without an override)
The only downside I see here is the SS
as the name of the device (first picture). But since that forms the prefix to all the sensor's friendly_names there is no way to really improve this
from sunsynk.
Related Issues (20)
- Prog{x} Time select list HOT 5
- I have just updated sunsynk add on, and am now getting 2 or 3 decimal places for all values. HOT 5
- Unable to successfully connect to Sunsynk inverter HOT 3
- Custom Sensors seems not to work HOT 7
- "PV3 Sensor" definition for Sunsynk 16Kw single phase inverter HOT 4
- Python Error HOT 2
- Batterie und RS485 Adapter an der Deye Schnittstelle ? Möglich? HOT 1
- Parallel support HOT 1
- 3 phase Grid Trickle Feed HOT 5
- Integration hangs regularly on reading/writing data HOT 18
- Use_timer: Unknown register value 1 HOT 9
- CRC validation failed: Sofar HYD-5000-EP HOT 7
- Slider scaling HOT 4
- Version b381a73 WARNING use_timer: Unknown register value 255 The Problem HOT 6
- Addon reading incorrect data after connection is lost HOT 6
- Possibility of use in sofar 5 ktlm g3? HOT 1
- Issue with the SOC figure since HA upgraded HOT 20
- grid_connected always OFF: Deye 3-phase HOT 3
- RWSensor System Zero Export power MinMax Value HOT 8
- USR-W630 IncompleteReadError HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from sunsynk.