sfeakes / aquapured Goto Github PK

It would be great if we could set the options around what to do on launch of the software.

Currently it starts the system with a chlorinator value of 50%. It would be great if we could set the initial state on/off, and parameter values.

We had a power outage at about 1am and then the pump started running once power returned.

Hi! This project is awesome! Is exactly what I was searching for! Thanks!

A list of compatible hardware, even better a table with supported/unsupported functions would be great.

I am building a poll at the moment and the the feature of been able to communicate with the SWG is essential to decide what SWG I will purchase.

As I can see, all that support Jandy protocol are compatible, but how could I know that?

For instance, Zodiac EXO iQ compatible is compatible (use Jandy protocol)?
Is some SWG of the brand Astralpool compatible?
BTW, is there any compatible SWG which gives pH data? Or there is any pH meter device with jandy protocol?
Lots of thanks

If your were I, nowadays, what SWG will choose (compatible with this project).

My pool is only 40m3

Hi sfeakes,

Thought I would post here to keep our discussions about AquapureD separate from AqualinkD.

My RS485 converter showed up last night.
This is the one I got: https://www.amazon.com.au/gp/product/B0721BB8PQ/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1

Would you might giving a bit of direction about whats involved in introducing power on the RS485?
Will I need to supply power into the Tri Chlor or just the 2 data pins?

Im assuming just setting up rasbian on the pi?

I have a Pi model B (from memory) laying around not doing anything that I'll be using. Ill be running ethernet to the shed (backs onto house) and will be looking at integrating it with home assistant once its all up and running.

So just thinking about the PPM levels for salt. I had a water test done by the pool shop today and my salt level is really high, about 8000 ppm.

Previously Aquapure was showing readings of 4000, earlier today it dropped down to 2900 (not sure why)

The readings that come from the SWG, would they need to be calibrated to suit the levels of the chlorinator? Manual for my chlorinator states ideal Salt PPM Range: 4000 - 7000.

When the SWG is turned off or percentage is set to 0% the fullstatus value will remain at its current state, it doesn't update to 254 to indicate the unit is off.

Hi @sfeakes

My cell has ticked over the 6000hrs now and is currently showing a message on the SWG displaying 'check cell'.

I haven't seen anything in the docs in aquapured or aquarited that shows this message.

Is there something I can do log wise to see if this data can be read by aquapured? Ill will avoid reseting the hours to remove the error until I hear from you.

Thanks
Paul

Hi @sfeakes,

I have just updated to the latest release and noticed my switch in home assistant won't show off status. Always returns to on once switched. The actual pump turns on and off as expected.

Looking at the logs below, even when it receives SWG/set/0 it publishes /SWG 2 causing the switch state to not be accurate.

Debug:  MQTT: topic aquapure/SWG/set 0
Info:   Setting SWG percent to 0
Debug:  Serial read 11 bytes
Debug:  Jandy   Received AR PPM    | HEX: 0x10|0x02|0x00|0x16|0x1d|0x00|0x00|0x00|0x45|0x10|0x03|
Debug:  Received PPM 2900
Debug:  build_device_JSON 589 of 1024
Debug:  MQTT: Published id=41: aquapure/SWG/Percent 0
Debug:  MQTT: Published id=42: aquapure/SWG/Percent_f -17.78
Debug:  MQTT: Published id=43: aquapure/SWG/PPM 2900
Debug:  MQTT: Published id=44: aquapure/SWG/PPM_f 1593.33
Debug:  MQTT: Published id=45: aquapure/SWG/enabled 2
Debug:  MQTT: Published id=46: aquapure/SWG/fullstatus 0
Debug:  MQTT: Published id=47: aquapure/SWG/Boost 0
Debug:  MQTT: Published id=48: aquapure/SWG 2
Debug:  MQTT: Message publishing acknowledged (msg_id: 41)
Debug:  MQTT: topic aquapure/SWG/Percent 0
Debug:  MQTT: Didn't understand topic aquapure/SWG/Percent 0
Debug:  MQTT: Message publishing acknowledged (msg_id: 42)
Debug:  MQTT: received (msg_id: 42), looks like my own message, ignoring
Debug:  MQTT: Message publishing acknowledged (msg_id: 43)
Debug:  MQTT: received (msg_id: 43), looks like my own message, ignoring
Debug:  MQTT: Message publishing acknowledged (msg_id: 44)
Debug:  MQTT: received (msg_id: 44), looks like my own message, ignoring
Debug:  MQTT: Message publishing acknowledged (msg_id: 45)
Debug:  MQTT: received (msg_id: 45), looks like my own message, ignoring
Debug:  MQTT: Message publishing acknowledged (msg_id: 46)
Debug:  MQTT: received (msg_id: 46), looks like my own message, ignoring
Debug:  MQTT: Message publishing acknowledged (msg_id: 47)
Debug:  MQTT: received (msg_id: 47), looks like my own message, ignoring
Debug:  MQTT: Message publishing acknowledged (msg_id: 48)
Debug:  MQTT: received (msg_id: 48), looks like my own message, ignoring
Debug:  MQTT: topic aquapure/SWG/Percent/set 0.0
Info:   Setting SWG percent to 0
Debug:  build_device_JSON 589 of 1024
Debug:  MQTT: Published id=49: aquapure/SWG/Percent 0
Debug:  MQTT: Published id=50: aquapure/SWG/Percent_f -17.78
Debug:  MQTT: Published id=51: aquapure/SWG/PPM 2900
Debug:  MQTT: Published id=52: aquapure/SWG/PPM_f 1593.33
Debug:  MQTT: Published id=53: aquapure/SWG/enabled 2
Debug:  MQTT: Published id=54: aquapure/SWG/fullstatus 0
Debug:  MQTT: Published id=55: aquapure/SWG/Boost 0
Debug:  MQTT: Published id=56: aquapure/SWG 2
Debug:  MQTT: Message publishing acknowledged (msg_id: 49)
Debug:  MQTT: topic aquapure/SWG/Percent 0
Debug:  MQTT: Didn't understand topic aquapure/SWG/Percent 0
Debug:  MQTT: Message publishing acknowledged (msg_id: 50)
Debug:  MQTT: received (msg_id: 50), looks like my own message, ignoring
Debug:  MQTT: Message publishing acknowledged (msg_id: 51)
Debug:  MQTT: received (msg_id: 51), looks like my own message, ignoring
Debug:  MQTT: Message publishing acknowledged (msg_id: 52)
Debug:  MQTT: received (msg_id: 52), looks like my own message, ignoring
Debug:  MQTT: Message publishing acknowledged (msg_id: 53)
Debug:  MQTT: received (msg_id: 53), looks like my own message, ignoring
Debug:  MQTT: Message publishing acknowledged (msg_id: 54)
Debug:  MQTT: received (msg_id: 54), looks like my own message, ignoring
Debug:  MQTT: Message publishing acknowledged (msg_id: 55)
Debug:  MQTT: received (msg_id: 55), looks like my own message, ignoring
Debug:  MQTT: Message publishing acknowledged (msg_id: 56)
Debug:  MQTT: received (msg_id: 56), looks like my own message, ignoring
Debug:  Jandy   Sent     AR %%     | HEX: 0x00|0x10|0x02|0x50|0x11|0x00|0x73|0x10|0x03|0x00|
Debug:  Serial read 11 bytes
Debug:  Jandy   Received AR PPM    | HEX: 0x10|0x02|0x00|0x16|0x1d|0x00|0x00|0x00|0x45|0x10|0x03|
Debug:  Received PPM 2900
Debug:  Jandy   Sent     AR %%     | HEX: 0x00|0x10|0x02|0x50|0x11|0x00|0x73|0x10|0x03|0x00|
Debug:  Serial read 11 bytes
Debug:  Jandy   Received AR PPM    | HEX: 0x10|0x02|0x00|0x16|0x1d|0x00|0x00|0x00|0x45|0x10|0x03|
Debug:  Received PPM 2900
^CNotice: Stopping!

Hi @sfeakes

Just wanted to get an insight into your future plans for AquapureD.

Is this a project that you are going to continue working on?

I am happy to continue testing/helping where possible and am happy to buy you coffees to assist in the developement.

If you're not looking to continue with it thats all good just means I might have to look around for other projects similar to this one.

Hi @sfeakes - is there any chance you could look at why the Zodiac Tri protocol you added does not work?

I'm trying to get this working with a Zodiac Tri with pH in order to be able to read the pH. If I set the Controller to "JANDY REV L/M" and set SWG_DEVICE_ID = 0x50 in aquapured.conf, theneverything works as expected (log). When I set the Controller to "AQUALINK Tri" and SWG_DEVICE_ID = 0xB0 - I get this in the logs and the web server shows disconnected. Should this functionality work as I 'm assuming? I see there has been almost no discussion regarding this since @sfeakes posted that he had added the functionality to set the SWG id in the config.

I would like to run this code on a Linux system. I tried recompiling but it throws errors related to not being able to find Py Pins. Would it be difficult to add support for non-Rasberry Linux hardware?