Open hyneksuchodol opened 1 year ago
I do confirm.
Solarman 1.4.3 was working fine with Deye SUN-6k-G03. No updates anymore after update to v1.5.0
With v1.5.0 I have noticed in the logs: 2023-09-06 10:29:25.170 WARNING (SyncWorker_7) [custom_components.solarman.solarman] Querying [3 - 112] failed, [0] retry attempts left 2023-09-06 10:29:25.171 WARNING (SyncWorker_7) [custom_components.solarman.solarman] Querying registers [3 - 112] failed, aborting. 2023-09-06 10:29:53.880 WARNING (SyncWorker_1) [custom_components.solarman.solarman] Querying [3 - 112] failed with exception [error: unpack requires a buffer of 220 bytes]
I use "deye_string.yaml" for Deye SUN-6k-G03 device Integration started to work again after downgrade to 1.4.3
Same here, using a Deye SUN800G3-EU-230 with this custom config:
requests:
- start: 0x0003
end: 0x0080
mb_functioncode: 0x03
parameters:
- group: solar
items:
- name: "PV1 Voltage"
class: "voltage"
state_class: "measurement"
uom: "V"
scale: 0.1
rule: 1
registers: [0x006D]
icon: 'mdi:solar-power'
- name: "PV2 Voltage"
class: "voltage"
state_class: "measurement"
uom: "V"
scale: 0.1
rule: 1
registers: [0x006F]
icon: 'mdi:solar-power'
- name: "PV1 Current"
class: "current"
uom: "A"
scale: 0.1
rule: 1
registers: [0x006E]
icon: 'mdi:solar-power'
- name: "PV2 Current"
class: "current"
state_class: "measurement"
uom: "A"
scale: 0.1
rule: 1
registers: [0x0070]
icon: 'mdi:solar-power'
- name: "Daily Production"
class: "energy"
state_class: "total"
uom: "kWh"
scale: 0.1
rule: 1
registers: [0x003C]
icon: 'mdi:solar-power'
- name: "Total Production"
class: "energy"
state_class: "total_increasing"
uom: "kWh"
scale: 0.1
rule: 3
registers: [0x003F,0x0040]
icon: 'mdi:solar-power'
validation:
min: 0.1
- group: Grid
items:
- name: "AC Voltage"
class: "voltage"
state_class: "measurement"
uom: "V"
scale: 0.1
rule: 1
registers: [0x0049]
icon: 'mdi:transmission-tower'
- name: "AC Output Frequency"
class: "frequency"
state_class: "measurement"
uom: "Hz"
scale: 0.01
rule: 1
registers: [0x004F]
icon: 'mdi:home-lightning-bolt'
- group: Inverter
items:
- name: "Running Status"
class: ""
state_class: ""
uom: ""
scale: 1
rule: 1
registers: [0x003B]
isstr: true
lookup:
- key: 0
value: "Stand-by"
- key: 1
value: "Self-check"
- key: 2
value: "Normal"
- key: 3
value: "Warning"
- key: 4
value: "Fault"
icon: 'mdi:home-lightning-bolt'
- name: "Total AC Output Power (Active)"
class: "power"
state_class: "measurement"
uom: "W"
scale: 0.1
rule: 3
registers: [0x0056, 0x0057]
icon: 'mdi:home-lightning-bolt'
- name: "Radiator Temperature"
class: "temperature"
uom: "°C"
state_class: "measurement"
scale: 0.01
rule: 1
offset: 1000
registers: [0x005a]
- name: "Inverter ID"
class: ""
state_class: ""
uom: ""
scale: 1
rule: 5
registers: [0x0003,0x0004,0x0005,0x0006,0x0007]
isstr: true
after upgrading the plugin (and restoring the custom config file)was no longer able to read out the value an generated lotś of errors like this:
home assistant solarman failed with exception [Illegal Data ValueError: The value contained in the request data field is not an allowable value
downgrading solved the problem
--- UPDATE ---
from https://github.com/StephanJoubert/home_assistant_solarman/pull/224 I can see that the converter should have been working with the provided _deye2mppt.yaml but in my case it also did not work
its a dupe of #367
the reading registers are: 0x0001~0x007B (123) and not 0x0080 (128)
same here to deye_4mppt.yaml
Same here... almost all parameters are in Unknown state
yes, I can confirm the same :-(
Yes, Same here … :-( …
Update to 1.51 do not solve the issue. To keep it functional I have to stay on 1.4.3
Is this issue being investigated, or it has been wrongly assumed to be fixed in 1.5.1 release?
Is this issue being investigated, or it has been wrongly assumed to be fixed in 1.5.1 release?
I'm not sure. I'm using fw 1.5.7 and it's working well: https://github.com/dasrecht/deye-firmware/tree/main/0_D0002_18 - I even don't know 1.4.3 or 1.5.1
Device disconnected after upgrade. Can't connect it back. Need to downgrade to version 1.4.3.. After install back old version every think looks good. I've seen multiple issues like this in several threads.