OpenDTU PV Inverter missing about hass-victron

[sfstar]

Hello and thank you for opening this issue.
A few questions:

• The modbus id's 33 and 34 aren't being detected while 32 is?
• Are the inverters online and reporting values in the GX device UI at the time the integration is scanning for registers?
• Are you able to create a modbus integration configuration to read one of the values of the PV inverters with slave address 33 and 34? (This should confirm whether the pv inverter is actually exposed).

[CerboJoe]

Hi,Yes, one of the 3 micro inverter (hoymiles) is found and works in HA. In OpenDTU and victron all works great since a year. Every three micro Inverters deliver data every 3 seconds. (one second per inverter)Maybe it was exactly the time, where they go offline in the evening when I start the first try to integrate. But the Hm-300 is the smallest of the 3 (2xHm-1500+1 Hm-300) and should go offline as first..Also I tryed a thousand times to make a rescan in the Konfiguration. Than I try a rescan with writing rights. This is also negative but now are the dashboards ill because the sliders and buttons are not away when I go back to the read mode only. (saver). So I will try a full new integration on a sunny day.. Does the rescan works? Maybe that's the only point? Additional the temperature sensors are shown in % and it's zero 🙁And a Pylontech battery does not tell us the energy, which is in or out of the battery. Me and HA is very sorrow about.. The energy flow doesn't work when batteries always say 0.0 kWh. But this is a general issue from Pylontech batteries on victron systems. And I can't find a solution.. I make a lot of pictures.. I hope, it helps. I also can give you any information you need.. Your last point, I can't help.. I'm not so far yet.. 🙄My HA runs only since a few weeks and I'm very happy, I don't run away when I see the code and yammels and topics.. I alway thought, this means the candys on an ice-cream 🤔But it gets better... ( in real, it's different IDs than in my issue message) Greetings, Joe  -------- Ursprüngliche Nachricht --------Von: sfstar ***@***.***> Datum: 13.03.24 14:05 (GMT+01:00) An: sfstar/hass-victron ***@***.***> Cc: CerboJoe ***@***.***>, Author ***@***.***> Betreff: Re: [sfstar/hass-victron] OpenDTU PV Inverter missing (Issue #180) Hello and thank you for opening this issue. A few questions: The modbus id's 33 and 34 aren't being detected while 32 is? Are the inverters online and reporting values in the GX device UI at the time the integration is scanning for registers? Are you able to create a modbus integration configuration to read one of the values of the PV inverters with slave address 33 and 34? (This should confirm whether the pv inverter is actually exposed). —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[sfstar]

Hello @CerboJoe,

Could you perhaps install the latest main version by following these instructions:
#182 (comment)

After which please reconfigure the integration to rescan all available devices (when all inverters are online and reporting in the GX device).

[CerboJoe]

I'm sorry.It dosent change anything. even not, after a full reinstallation. The HM-300 is shown, the two HM-1500 are not.

[sfstar]

Thanks for checking.
Could you perhaps share the entries located under:
"settings -> services -> modbus/TCP -> available services" on your GX device?

[sfstar]

Also please add the following configuration to your configuration.yaml file to further troubleshoot whether the inverters values are actually retrievable from the gx device:

modbus:
  - name: victron
    type: tcp
    host: <ip of the gx device>
    port: 502
    retry_on_empty: true
    retries: 10
    close_comm_on_error: true
     sensors:
       - name: pv_inverter_l1_voltage
         unit_of_measurement: "V"
         slave: 33
         address: 1027
         device_class: voltage
         state_class: measurement
         data_type: uint16
         scale: 0.1
         precision: 2
         offset: 0

Take note to customize the <ip of the gx device> part to the ip of your GX device.

After adding the configuration please restart your home assistant instance and check whether an entity is created with the name pv_inverter_l1_voltage and it's state is being populated with the inverters voltage values that are also visible in the GX device.
Please report your findings so that this issue can be further troubleshooted.