Open PV-Joe opened 2 days ago
Meanwhile I helped myself and added these lines to make AC and DC temperature for the Deye Hybrid work again:
- name: "DC Temperature"
# disabled:
class: "temperature"
state_class: "measurement"
uom: "°C"
scale: 0.1
rule: 2
offset: 1000
registers: [0x021C]
icon: "mdi:thermometer"
range:
min: 0
max: 3000
- name: "AC Temperature"
# disabled:
class: "temperature"
state_class: "measurement"
uom: "°C"
scale: 0.1
rule: 2
offset: 1000
registers: [0x021D]
icon: 'mdi:thermometer'
range:
min: 0
max: 3000
You can delete the following sensor as this is the same as AC temperature:
- name: "Temperature"
class: "temperature"
state_class: "measurement"
uom: "°C"
scale: 0.1
rule: 2
offset: 1000
registers: [0x021D]
icon: "mdi:thermometer"
range:
min: 0
max: 3000
Yes I did change names of some of the sensors. Now i see that I should have stated that! Thanks for pointing it out! Anyway naming of the sensors is in my opinion totally personal thing so feel free to adjust them accordingly to suit your needs!
I have planned for the future to transfer this customization into the configuration from HA.
When comes to this particular change of names. If I remember correctly reading of the DC Temperature newer worked for me and was always 25°C co I decided to throw that one out!
And about the override, it works like this: Inverter with same serial number will always override the existing one. This way it works also in the version from Stephen and i kept it that way. Sorry about the inconvenience!
Thanks for your reply. Your integration works like a charm!
You are right. The DC Temperature seems to be stuck at 25 C but the AC temperature works:
Does anyone know the right DC temperature Modbus register value for the Deye Hybrid SG04LP3?
It is the right one, at least according to the modbus doc available. My guess is that the sensor (in terms of a hardware) is just not there. :)
I just begin to look into that "sensor naming" matter and that DC Temperature sensor stayed in fact in the definition file but i marked it with "disabled:". That means that the sensor entity won't be added automatically with configuring of the device, but you can then enable this entity in the HA and it will stay enabled. ;)
I did enable it by putting a “#” in front of “disable:”
Thats also an option. 😄 This feature works with HAs 'Disabled by integration' feature.
Sensor entity, which is then added into the HA looks like this:
And when you click on it you can enable it, by clicking on ENABLE:
But is true to say that I never actually tested if it works so... 😄
I presume this does not work with SUN-10K-SG01HP3-EU-AM2 ?
That's a high voltage inverter, serial no. starts with 23xxx, so presumably it's not protocol Version 5, but 4? Or another?
@PV-Joe I made the changes to the definition file in the: c6dfe87
Edit: But I have to say that (even it's not like those are end of the world problems) some of the sensor names are really inconsistent and when I was doing any changes I was trying to make them in compatibility with the HA Sunsynk addon from Kallerza which who named them very reasonably. But I also understand that it's annoying when you load things up and it's all messed up. 😄 Anyway for any newcomers there is new file with the updated naming scheme. 😉
Hi David,
Just testing your integration in my productive system.
My Configuration: DEYE Hybrid 8K SG04LP3 EU PYTES E-Box Battery
I installed your integration parallel to the Solarman integration 1.4.1 by Stephen and realized that it was overwritten.
Result: Many sensors have different names. That’s not a big problem and can be fixed manually.
I realized that the following sensor is missing: Solarman AC Temperature Could you please add it?
I‘m impressed by the speed of reloading the values. This integration is much faster.
Great work and many thanks!