Issue with Jandy VSP Pump, and Heat Pump

[mal7887]

Hello,

Awesome project, really appreciate all the hard work. I have a few questions about my setup that I can't seem to figure out.

1. Pump doesn't show RPM and Watts
I have a Jandy VSP pump. The pump ID shows as 0xe0, I have entered that into the config for button one, but it still does not show. In the logs I do see both watts and speed.

my config:
button_01_label=Filter Pump
button_01_pumpID=0xe0
button_01_pumpIndex=1
button_01_pumpType=JANDY ePUMP

2. Can't turn Heat pump On/off
I can't control my Jandy Heat Pump though AqualinkD.
In my IAqualink App I have 3 Heat toggles: Spa Heater, Pool Heater, Heat Pump. The heat/cooling will only run if I manually toggle the Heat Pump switch on the official iAqualink app. It does not correspond to one of the AUX switches. I can also toggle the Heat Pump with a One Touch button.

My Config:
read_RS485_swg = yes
read_RS485_ePump = yes
#read_RS485_vsfPump = yes
read_RS485_JXi = yes
#read_RS485_LX = yes
#read_RS485_Chem = yes
#read_RS485_iAqualink = yes

If it's OFF I see a status message: Info: AllButton: RS Message :- 'Heat Pump OFF'
If it's ON I see a status message: Info: AllButton: RS Message :- 'Heat Pump ON'

Not sure if I have something newer or not or if I am doing something wrong.

3. Can't access One Touch options in AqualinkD

As a workaround to controlling the heat pump switch, I thought I would instead setup a One Touch virtual button in AqualinkD that just turns on the heat pump, however I can't get that to work. The One touch works fine in the offical app (it turns the heat pump toggle on off).

My config:
virtual_button_01_label = Heat Pump
virtual_button_01_onetouchID = 5

Log:
Feb 23 11:47:09 Info: Panl&Prog: Device request type 'OnOff' for deviceindex 15 '5 Heat Pump' of value 0 from 'WebSocket'
Feb 23 11:47:09 Info: Panl&Prog: received 'OFF' for 'Aux_V4', turning 'OFF'
Feb 23 11:47:09 Info: Panl&Prog: Set state for Virtual Button Aux_V4 code=0x00 iAqualink2 enabled=No
Feb 23 11:47:09 Error: Panl&Prog: Can only use Aqualink Touch protocol for Virtual Buttons

The pump would just be a nice to have, but not having the Heat Pump switch is a real PITA.

Any help would be greatly appreciated, will provide any useful info you need.

[sfeakes]

Can you post your aqualinkd.conf file and the output of serial_logger.? With those I can take a deeper look, but a preliminary assessment is below.

For VSP and Virtual Buttons you have to enable extended_device_id in aqualinkd.conf, (preferable to a Aqualink Touch ID). It looks from the problems you are having this is not enabled.

It also like like you have a panel rev Y or greater from your images. Jandy changed how the pump ID's work on that rev#, I had coded for it for someone else, and AqualinkD worked for them. But without that board myself, it's hard to fully test. So I may need to do some more work on that and get some logs from you. But let's see where things are after you posted the above files.

I've never seen a heat-pump that's not physically connected to an AUX circuit. But if yours is infact not connected to an AUX circuit, then virtual button is the only option, and we need to fix the above to get those to work. Out of interest if your heat pump simply enabled from a JVA?, then I could see only needed a virtual button.

Back to the pump VSP info, what will also help with rev Y is configuring the pump name in AqualinkD, button_01_pumpName=My Pump Name since they don't use PumpType and PumpIndex in rev Y anymore. BUT, I can also see this causing a problem in your setup since it "looks" like you have AUX1 label as "Filter Pump" and the pump itself is also called "Filter Pump", that may create a problem when reading information from the panel text menus. So you may want to rename the pump once you have the config sorted.

[mal7887]

I believe I have the extended_device_id set properly to a One Touch. I also tried setting it to a Aqualink Touch (0x30, 0x31, 0x32 & 0x33) and if it is set to this, the system becomes unresponsive.

Here are the requested files:

aqualinkd_config.txt

aqualinkd Log.log

On the heat pump I am 100% certain it is not controlled by a relay, only a RS485 wire. The only way I can get the heat pump to run is if I enable the bottom toggle in the App.

[mal7887]

I am running version B0316823 REV Yg.

On the pump naming. The pump is wired through relay 1. I don't see where I can change the name of that relay, but I do see where I can change it in the newer VS Pump Setup menu. Should I change it there?

[mal7887]

Also not sure if relevant on the heat pump, I occasionally see the message about the heat pump.:

Feb 23 13:06:48 Warning: RS Serial: Read Jandy packet BAD PACKET To 0x00 of type LXi status | HEX: 0x10|0x02|0x00|0x0d|0x40|0x00|0x00|0x5f|0x10|0x10|0x02|0x50|0x11|0x1e|0x91|0x10|0x03|
Feb 23 13:09:57 Warning: RS Serial: Serial read bad Jandy checksum, ignoring
Feb 23 13:09:57 Warning: RS Serial: Read Jandy packet BAD PACKET To 0x00 of type LXi status | HEX: 0x10|0x02|0x00|0x0d|0x40|0x00|0x00|0x5f|0x10|0x02|0x50|0x11|0x1e|0x91|0x10|0x03|
Feb 23 13:12:34 Warning: RS Serial: Serial read bad Jandy checksum, ignoring
Feb 23 13:12:34 Warning: RS Serial: Read Jandy packet BAD PACKET To 0x00 of type LXi status | HEX: 0x10|0x02|0x00|0x0d|0x40|0x00|0x00|0x5f|0x10|0x02|0x50|0x11|0x1e|0x91|0x10|0x03|

[sfeakes]

checksum errors are due to bad RS 485 wiring (or termination). a few here and their are not usually a problem, but if you are seeing that a lot, I'd check the wiring.

[mal7887]

It is very infrequent. Noted, thanks.

[sfeakes]

First try adding button_01_pumpName=Filter Pump to aqualinkd.conf. If it creates some confusion, then change the name of the pump (not the button) in the app, and change aqualinkd.conf accordingly.

What was the output of serial_logger? That will tell you what ID's you can use and what the pump ID is. The unresponsive could be due to an ID conflict.

Looking over your config, you should make some other changes as well.
#rssa_device_id=0x48. -> Enable this by removing the #
enable_iaqualink=yes -> Disable this by adding a #. You can ONLY use this setting if you don't have a iAqualink connected. (My mistake bad documentation, I'll fix that). This also may be why you system because unresponsive using a 0x3? ID, since both AqualinkD and iAqualink were trying to use the extended Aqualink Touch protocol, and only one device is supported.
To be clear, 4 devices are supported on the Aqualink Touch protocol, but only 1 of those 4 can use the Aqualink Touch Extended protocol. (And that's iAqualink in your case). That setting enables the extended protocol.
#read_RS485_iAqualink = yes -> Enable this by removing the #. Since iAqualink is using the extended protocol, AqualinkD can still read that information (It just can't write).

[mal7887]

Here is the serial Output:

aqualinkd_Serial.log

Feb 23 13:48:46 Notice: Serial Log:ID 0xa3 is in use <-- iAqualink 2.0
Feb 23 13:48:46 Notice: Serial Log:ID 0x0a is not used <-- can use for Aqualinkd
Feb 23 13:48:46 Notice: Serial Log:ID 0x70 is in use <-- Heat Pump
Feb 23 13:48:46 Notice: Serial Log:ID 0x60 is not used <-- can use for Aqualinkd (PDA mode only)
Feb 23 13:48:46 Notice: Serial Log:ID 0x40 is not used <-- can use for Aqualinkd (Extended Device ID)
Feb 23 13:48:46 Notice: Serial Log:ID 0x48 is not used <-- can use for Aqualinkd (RSSA ID)
Feb 23 13:48:46 Notice: Serial Log:ID 0x33 is in use <-- Aqualink (iAqualink / Touch)
Feb 23 13:48:46 Notice: Serial Log:ID 0x42 is not used <-- can use for Aqualinkd (Extended Device ID)
Feb 23 13:48:46 Notice: Serial Log:ID 0x43 is not used <-- can use for Aqualinkd (Extended Device ID)
Feb 23 13:48:46 Notice: Serial Log:ID 0xe0 is in use <-- Unknown Device THIS IS THE FILTER PUMP
Feb 23 13:48:46 Notice: Serial Log:ID 0x30 is not used <-- can use for Aqualinkd (Prefered Extended Device ID)
Feb 23 13:48:46 Notice: Serial Log:ID 0x31 is not used <-- can use for Aqualinkd (Prefered Extended Device ID)
Feb 23 13:48:46 Notice: Serial Log:ID 0x32 is not used <-- can use for Aqualinkd (Prefered Extended Device ID)
Feb 23 13:48:46 Notice: Serial Log:ID 0x50 is in use <-- Salt Water Generator (Aquarite mode)
Feb 23 13:48:46 Notice: Serial Log:ID 0x08 is not used <-- can use for Aqualinkd
Feb 23 13:48:46 Notice: Serial Log:ID 0x09 is not used <-- can use for Aqualinkd
Feb 23 13:48:46 Notice: Serial Log:ID 0x0b is not used <-- can use for Aqualinkd
Feb 23 13:48:46 Notice: Serial Log:ID 0x41 is not used <-- can use for Aqualinkd (Extended Device ID)

I made all the changes you mentioned above and set extended_device_id= to 0x30 that combined with the other changes did not cause everything to freeze up like before! :-)

button_01_label=Filter Pump
button_01_pumpID=0xe0
button_01_pumpIndex=1
button_01_pumpType=JANDY ePUMP
button_01_pumpName=Filter Pump

Now also have Pump info! :-D

Now with the Heat Pump Toggle...

In the config I have:

virtual_button_01_label = Heat Pump
virtual_button_01_onetouchID = 5

If I toggle this, It is not toggling the One Touch 5 (which is just the heat pump), but it IS toggling the heat pump switch.

I just noticed they are the same name (one touch 5 is "Heat Pump" and the Heat pump toggle is also "Heat Pump"). Could that be why?

[sfeakes]

Glad is seems to be mainly working now.

Since iAqualink is using the extended Touch Protocol (and not AqualinkD), AqualinkD has to search the menu's for the device. So if two devices have the same name, it will just pick the first it comes across. if AqualinkD could use the extended touch protocol, then it can access the OneTouch by the ID and not have this issue.

So renaming one of them should help

[mal7887]

Confirming renaming worked. Being able to control the Heat Pump now is awesome, it's been such a pain not being able to.

I am all set now, everything works!

Thanks again for brining this outdated pool tech to the 21st centry.

[mal7887]

Thought i would share one more observation. I have an rs4 combo panel, with 4 relays in use and 4 jvas in use. My spa Light was wired to the 4th relay, which in the rs4 is the solar circuit. .

If I set my config file to a rs4 combo. I was not able to control my waterfall JVA in aqualinkd. It seems there arent enough buttons avaliable in the rs4 config. I was able to resolve this by manually setting my panel type to a rs6 in the config and mapping the buttons correctly.

Another issue I encountered was controlling lights on the solar circuit. I was able to turn the spa lights on/off, but could not get aqualinkd to set the color of the light. The jandy app was able to control and set the light fine when it was on the solar circuit. I was able to resolve this by swapping my spa blower to the solar circuit relay and my spa Light to aux2.

[mal7887]

Just wanted to report that my previous statement was incorrect. When my builder setup my two additional JVAS. They assigned one to AUX3. This did not have anything to do with RS Panel size in config. I changed my JVAs to V1 and V2 and created virtual outlets now and can control no problem.