Vistapool Integration

Third party integrations
226

Before doing that I measured the power consumption of the HF5111S, it turned out to consume 35mA, which I assumed can easily be delivered by the Oxilife:

Photo 23.11.07, 14 57 31
Photo 23.11.07, 14 57 311920×1440 230 KB

So I’m powering the HF5111S from the Oxilife and it works flawlessly since weeks.

In Home Assistant I’m using the following configuration in configuration.yaml:

modbus:
  - name: Oxilife
    type: tcp
    host: 192.168.188.62
    port: 8899
    sensors:
      - name: Oxilife-ModBus-ph
        input_type: input
        unit_of_measurement: mol/l
        data_type: uint16
        slave: 1
        address: 258
        unique_id: Oxilife-ModBus-pH
        scale: .01
        offset: 0
      - name: Oxilife-ModBus-rx
        input_type: input
        unit_of_measurement: mV
        data_type: uint16
        slave: 1
        address: 259
        unique_id: Oxilife-ModBus-rx
        scale: 1
        offset: 0
      - name: Oxilife-ModBus-wt
        input_type: input
        unit_of_measurement: Celsius
        data_type: uint16
        slave: 1
        address: 262
        unique_id: Oxilife-ModBus-wt
        scale: .1
        offset: 0

And then I built some simple gauges to be able to monitor the main pool parameters from any mobile device in the house:

2023-11-18 09_30_55-Overview – Home Assistant - Iron
2023-11-18 09_30_55-Overview – Home Assistant - Iron499×641 19.6 KB

The YAML of the three gauges is as follows:

type: gauge
entity: sensor.oxilife_modbus_wt
needle: true
min: 0
max: 38
segments:
  - from: 26
    color: '#43a047'
  - from: 30
    color: '#ffa600'
  - from: 34
    color: '#db4437'
severity:
  green: 0
  yellow: 0
  red: 0
name: Wasser Temperatur
unit: °C

type: gauge
entity: sensor.oxilife_modbus_ph
needle: true
min: 6.8
max: 7.8
segments:
  - from: 6.8
    color: '#db4437'
  - from: 7
    color: '#ffa600'
  - from: 7.1
    color: '#43a047'
  - from: 7.5
    color: '#ffa600'
  - from: 7.6
    color: '#db4437'
name: pH-Wert
unit: ' '

type: gauge
entity: sensor.oxilife_modbus_rx
needle: true
min: 500
max: 900
segments:
  - from: 500
    color: '#db4437'
  - from: 550
    color: '#ffa600'
  - from: 600
    color: '#43a047'
  - from: 800
    color: '#ffa600'
  - from: 850
    color: '#db4437'
unit: ' mV'
severity:
  green: 0
  yellow: 0
  red: 0
name: Redox Wert

Simple and intuitive so every family member can easily interpret the values. :slight_smile:

227

Hi thank you . Could you write me a description of the HF settings. It was necessary to set something in HF.

228

Sure! Here we go, the settings in the web interface of the HF5111S:

System Settings

System_settings
System_settings635×919 23.7 KB

Serial Port Settings

Serial_Port_Settings
Serial_Port_Settings636×868 19.8 KB

Communication Settings

Communication_settings
Communication_settings636×847 21.3 KB

229

Thanks , I will try if I buy HF. Thanks

1 Like
230

Amazing Thonglor, and thank you for sharing!

Where did you buy the connector attached to modbus 3 port?

Best regards,
J

231

In Ebay you’ll find a lot of sellers for this device, it’s always between 32,-€ and 36,-€ incl. shipping.

232

IMG_0349

I mean this connector…

233

This is a standard 2.54mm 5-pin PCB female connector, e.g. like sold here:

(I didn’t buy it, I had it lying around at home)

234

Many thanks,

Have a great weekend!

1 Like
235

Hello… can you give me the repository to find in HACS, I have added a folder in components but I don’t get integration. Thank you

236

This is not in HACS, you need to set it up manually as described above

237

Correct… I have uploaded the folders and put them in components, restarted and when I go to add it does not appear in integrations… any ideas? Thank you

image

238

What I described in post 220 above is a manual set-up in configuration.yaml. There is nothing to download, and it is also not a custom_components. So, I can currently not follow what you’re describing. Just buy a serial server for Modbus, add the above mentioned entries to configuration.yaml and you’re good to go.

1 Like
239

I am looking for testers for my Dagen / Da-gen / Vistapool component:

It requires wifi/cloud connection. Let me know if it works and of any features missing, before I submit to HACS.

1 Like
240

Amazing, I’m totally into.

241

Should this work with my Vistapool.es login?

(already tried the da-gen app on my phone, but the login does not work there)

1 Like
242

I am not sure. My Da-gen device works on vistapool.es, but I don’t have any knowledge on how/why.

What device do you have?

243

“Sugar Valley Vistapool WIFI Module”

The “funny” part is: when I want to create a login on Da-gen app, it states the account already exists on my email address. So I assume Da-gen and Vistapool use the same back-end.

But I’m stuck, because now I can’t login on Da-gen app, which leads to not having a Da-gen account, which leads to not being able to use your component… :slight_smile:

UPDATE: I registered with an “+” behind my email address, and now everything works as it should. I could add my pool with the Node ID of my wifi module.

Can you give us an explanation of the entities we see?

Cl = rX? (because I see 0,0 there)
What’s the difference between FL1 and FL2?

1 Like
244

Same, I use it with vistapool.es and I have the same value for rX.
Anyway the component looks promising.

Good job.

245

I tried to use the same labels as in the Vistapool.es website and Dagen app interface, so it would self-explanatory, but maybe there is a difference based on localization or country?

For me in Denmark, the web says these values:
image

Unfortunately I misspelled the symbol and used CI instead of Cl (capital I vs lower case l). I will fix that in the next version.

FL1 and FL2 is the Flow 1 and Flow 2 sensor. I made this picture and hope it helps:

image
image932×927 64.3 KB

Please comment if another naming should be used?