USR W610

[wymes]

Hi

I am experimenting with the above device . I know the actual com port is working by testing with a laptop through the device to a virtual com port over ether net . I can see no activity on the RS585 port when connected to the Solis inverter . The wiring is correct .and I can see approx 2.6v across the leads

I have tried a 485 to 232 adapter with no luck . I am awaiting an adapter to test as per the laptop test

Any clues on the config

THe unit is set up for tcp mmodbus rtu and the 485 port is enabled and the baud speed is correct

[alienatedsec]

Hi @wymes

Any screenshots of your configuration, and settings could be useful to oversee some of the challenges you are facing with this device.

[wymes]

Hi As requested From: alienatedsec ***@***.***> Sent: Sunday, July 9, 2023 12:46 PM To: wills106/homeassistant-solax-modbus ***@***.***> Cc: wymes ***@***.***>; Mention ***@***.***> Subject: Re: [wills106/homeassistant-solax-modbus] USR W610 (Discussion #461) Hi @wymes <https://github.com/wymes> Any screenshots of your configuration, and settings could be useful to oversee some of the challenges you are facing with this device. — Reply to this email directly, view it on GitHub <#461 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQWFLDVAXJ7IUAWKCIJE7MLXPKKWHANCNFSM6AAAAAA2DN4UNM> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AQWFLDX3FAYNUADUVGK3TYDXPKKWHA5CNFSM6AAAAAA2DN4UNOWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAMGL5Q.gif> Message ID: ***@***.*** ***@***.***> >

[alienatedsec]

Sorry @wymes there is nothing in your response. It looks like responding via email removes screenshots.

[wymes]

Hi

Just to add . I am assuming that the solis inverter is acting as a client to the w610 unit or is it a server to the w610 unit ?

REgards

Nigel

[alienatedsec]

@wymes If you are asking about Server / Client config for your W610, it will be in relation to your device. Server means that HA (or another Client) can query it, and the Client will be to connect to other Servers.

The inverter is a Slave on the Modbus network, which has nothing to do with Server / Client config.
However, your W610 wired to the inverter should be set as Server.

[wymes]

[alienatedsec]

@wymes I am not sure what is the 485 selector switch mode.

Apart from that, it looks like it uses an 8899 port. When configuring SolaX integration, did you use that port and IP 10.10.100.100?

Is that even the correct subnet on your network?

[wymes]

Hi

Apologies for splattering the discussions . What i have working is the w610 is connected via wifi to my router . It has an IP address from the router dhcp pool (192.168.0.x) . I use this address to connect the integration over port 8899

If I use the lan ports for the second device they have a 10.x.x.x address

From the entities i see you have the following
Battery Input Energy - charge
Battery Output Energy - Discharge

Battery Power one of the above

Would be great if battery Power was a -negative value for discharge and a positive value for charge . Then you can have a needle gauge cantered on zero which can then swing positive or negative

The solis cloud integration shows the value as neg or pos :-)

Ma\y thanks

Nigel

[alienatedsec]

@wymes create this template replace solislan with your name

sensor:
  - platform: template
    sensors:
      battery_power_display:
        friendly_name: "Battery Power Display"
        unit_of_measurement: "W"
        value_template: >
          {% if states('sensor.solislan_battery_input_energy')|float > 0 %}
            +{{ states('sensor.solislan_battery_input_energy') }}
          {% elif states('sensor.solislan_battery_output_energy')|float > 0 %}
            -{{ states('sensor.solislan_battery_output_energy') }}
          {% else %}
            0
          {% endif %}
        icon_template: >
          {% if states('sensor.solislan_battery_input_energy')|float > 0 %}
            mdi:battery-plus
          {% elif states('sensor.solislan_battery_output_energy')|float > 0 %}
            mdi:battery-minus
          {% else %}
            mdi:battery-unknown
          {% endif %}

[alienatedsec]

@wymes

Thanks for inspiring me to do the same as I wanted it for a while.

[wymes]

That worked a treat thanks

[wymes]

Hi

Tried station mode with data transfer as transparent and the integration burst into life :-)

If I were to buy a second device not sure how that would connect to the first so that the original data logger would work as well ?

Thanks

Nigel

[alienatedsec]

@wymes
It's hard to follow the conversation as you don't reply to the same thread but you make separate comments which create many threads in the same conversation.

When you purchase another device, you wire it to a data logger and you have to configure it as a client and provide the IP of the server to connect to (the one that is currently working with the integration)

[wymes]

hopefully final question

in the solis config I can see the following entity

SolisModbusSensorEntityDescription(
name = "Battery Power",
key = "battery_power",
native_unit_of_measurement = UnitOfPower.WATT,
device_class = SensorDeviceClass.POWER,
state_class = SensorStateClass.MEASUREMENT,
register = 33149,
register_type = REG_INPUT,
unit = REGISTER_S32,
entity_registry_enabled_default = False,
allowedtypes = HYBRID,
icon = "mdi:home",

But in the integration it is not showing . Everything else appears to be there . 143 entities found ?

Regards

Nigel

[wymes]

looking at the the HA config looks like it is disabled by the integration . I tried setting the value to null but that screwed up HA :-(
I will rebuild the server tomorrow with a fresh start

Regards

Nigel

[alienatedsec]

@wymes it's not enabled by default. You can enable it in entities when you filter disabled ones.