Pool controller Jandy IQPUMP01 support.

[aruiz760]

Hello, I hope I'm putting this in the correct location. The Jandy IQPUMP01 shows up in the Iaqualink app but not on the integration. Here is a log output:

_Logger: homeassistant.components.iaqualink
Source: components/iaqualink/init.py:98
Integration: Jandy iAqualink (documentation, issues)
First occurred: 12:28:20 AM (8 occurrences)
Last logged: 1:28:00 PM

No systems detected or supported_

Would appreciate any help. Thanks.

[Joacbe]

IQPUMP seems a bit special and is not supported out of the box by the module apparently (at least I was taking a look at the Home Assistant integration).

I don't have the skills to modify anything of the existing but I've been able to identify the various API URLs to be called to perform the basic operations and validate them all on my pupm.

I'll be more than happy to share if anybody has the skills and is willing to add the IQPUMP01 support.

[aruiz760]

Thanks.

[robertw]

IQPUMP seems a bit special and is not supported out of the box by the module apparently (at least I was taking a look at the Home Assistant integration).

I don't have the skills to modify anything of the existing but I've been able to identify the various API URLs to be called to perform the basic operations and validate them all on my pupm.

I'll be more than happy to share if anybody has the skills and is willing to add the IQPUMP01 support.

If you have the api calls and willing to share that would be a big help thnak you

[Joacbe]

I can share my Postman project where all the details are aggregated.
ZodiacIQPump.postman_collection.json

I have 8 variables defined:

Below variables values are coming from your Jandy/iAqualink account:

• JandyUserLogin
• JandyUserPassword
• APIKey = EOOEMOW4YR6QNB07 (apparently it never changes)
• PumpSerial = the serial number without the dashes signs
  
  Note: the serial number may also be retrieved using the query named "Get Devices" as the "serial_number" attribute in the returned json.

And identified 10 different API calls

Those are allowing to perform all the most important operations over the pump:

• The Auth & GetToken query allows connecting and getting the required values for defining the following variables:

• IDToken = IdToken

• AccessToken = AccessToken

• AuthToken = authentication_token

• UserID = id

• Get Devices allows getting all the iAqualink devices existing in association to your account. In my case, I only have the pump, device of type i2d

• 0 - Get Device All Data

Dealing with pump override/forced activation start / stop

• 1 - Device Write Mode - Set custom time
• 2 - Device Write - Custom Speed
• 3 - Device Write - Custom Operations time
• 4a - Device Stop pump

Setting back pump in scheduled operating mode

• 4b - Device Start pump - Resume Schedule

Dealing with pump schedules: reading/writing

• 5 - Device Read Schedules
• 6 - Device Write Schedules

Last but not least, this is how to interprete the values returned when dealing with the schedules:

• Returned data on a single row: Y070018001500YYYYYYYDefault Schedule
  = Y : is schedule enabled? Y / N
  = 0700 : start time (always 4 digits)
  = 1800 : stop time (always 4 digits)
  = 1500 : RPM during the schedule (always 4 digits, filled in with 0 if less than 1000)
  = YYYYYYY : week days the schedule is enabled. Could be N as well if disabled. Note: starting with Sunday!!
  = Default Schedule: name of the schedule

Notes, schedules are all separated by a | and stored on a single line

[robertw]

Many thanks i am not a great coder but will try to make it work with home Assistant.......