Direct connect to Jandy JXI heater?

[romank95]

Hi there, looking to take control of a Jandy JXI heater directly over RS485 without any kind of control panel. Is this a supported configuration?

Thanks!

[tagyoureit]

We support some Pentair models, but no one has decoded the JXI heaters yet. It looks like there might be some slight advantages to using >Rev N (see TFP), but in general setting up the fireman's switch to turn the heater on/off gets you all the functionality you need.

[chevyzr1]

Hi there, looking to take control of a Jandy JXI heater directly over RS485 without any kind of control panel. Is this a supported configuration?

Thanks!
@tagyoureit
+1 for this exact setup. It seems there could be benefit of using the RS485 communication to get the additional data points the heater displays such as temperature, flow, and fault status. Is there any chance this could be a feature added in the future? I tried connecting it but I just get packets sent and received but all show up as "unsuccessful" comms readout.

[hubuser01]

I am now getting responses back from the heater, but they are null's (0). But this might be due to the fact that the pump is not set up yet and there is no water flow through the heater. It may be another week or two before we can get that going. We will report back when the pump is running. Just did not want to leave you hanging. Again.. Thank You!

[hubuser01]

The excitement of this project has put the pool opening a bit ahead of schedule... pump is running but again.. no luck
Here is a log entry
{"port":0,"id":4,"valid":true,"dir":"out","proto":"jandy","pkt":[[],[], [16,2,104,12], [0],[134,16,3]],"ts":"2026-05-14T15:35:59.624-0400"}
The checksum is 134. should it be 116? 104+12+0 = 116
[DLE] 16 [STX] 2 [DEST] 104 [CMD] 12 [DATA...] 0 [CHECKSUM] (dest+cmd+data & 255) [DLE] 16 [ETX] 3
looks like you might be including DLE and STX for the checksum.
I found this somewhere: "CHECKSUM: Single byte checksum (sum of DEST through last DATA byte, masked to 8 bits)"
Just can not thank you enough!

[tagyoureit]

Nice find... this works differently than the Aqualink protocol which includes the [16,2] header. Pull and try again.

[hubuser01]

The checksum looks good. but still no luck. My heater is the Jandy JXi260N. I am wondering if the 68 address is for the JXi400 and the JXi260 is different. The power interface boards for the different models are the same part number. Did a lot of testing today. Turns out the null I was receiving may not be coming from the rs485 bus. I bridged a pc with hterm and an rs485 adapter on the bus and was not seeing the "null" coming from the bus and never saw anything coming from the heater. I am seeing the 16,2,104,12,0,116,16,3 coming from njsPC. Working on a python script to scan the addresses to see if we can get some sort of response from the heater.
Not sure where to go from here.
By any chance, have I thanked you yet?

[hubuser01]

Heater was in remote tsat mode
Tried a python script that sent commands to every address from 0 to 247
Commands sent (decimal):
16,2,address,12,0,checksum,16,3
16,2,address,0,0,checksum,16,3
16,2,address,37,0,checksum,16,3
ran using both checksums 0-4 and 2-4
reran these after swapping D+ and D- wires

• I was seeing a "null" (0) being received after every command after the wire swap.
• This null was not being picked up from another rs485 device on the bus. Not sure where it came from.

tried 9600,n,8,1 and also 9600,n,7,1
Not a single response back from the heater :-(

Jandy JXI260N firmware
pi rev JXi: 6.03
UI FW rev: 1.8

I really wanted to use the rs485 to get the temp so I did not have to use the fireman method with an additional temp sensor. There is also an SAF (Spouse Approval Factor) that has to be met.

[chevyzr1]

The timing of this update is a bit amusing as I was impatient and decided to give Claude a try and intgrate rs 485 comms with Jandi JXI400 myself. I was successful after several (about a week) of failed attempts. I’m sure your version is much better but I will share mine for giggles. I ended up adding a separate RS485 adapter to my pi as my pentair pump communicates on my primary port and since the Jandy uses a different message structure I was seeing a lot of collisions with them both on the same adapter. I will give yours a try and see if there’s any difference. One thing that I found and what took so much time was getting the flame widget to work with the heater on RS485 mode. Also getting the address dropdown widget under heaters took some time. See here:https://github.com/chevyzr1/nodejs-poolController-jxi/tree/feature/jxi-heater

…

On May 9, 2026, at 6:00 PM, tagyoureit ***@***.***> wrote: Thx. Pull njsPC/dP again. The UI was missing the configurable elements including the address. — Reply to this email directly, view it on GitHub <#1128 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BH52N4D6CRHI6OLZIIAN3ID4Z6TA3AVCNFSM6AAAAACYC2U75SVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMOBWGUZTENY>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.

[hubuser01]

Since you have this working, would it be possible to get some additional information?
What model heater do you have? you already answered this: JXi400
What rs485 adapter are you using?
What is your pin out from the heater to the rs485 adapter?
pin 4 Green - not connected
pin 3 Yellow - Data-
pin2 Black - Data+
pin 1 Red - not connected
Are you connecting pin 4 green to ground on your adapter? ( I have not tried this yet, will try soon)
What exactly are you sending out to the heater? (decimal) 16 2 104 12 0 116 16 3
What serial setting are you using? 9600,n,8,1?
Heater Version? Shows briefly upon power up.
Thanks

[chevyzr1]

After reviewing the updates VS the my config, I wanted to share what I found while getting a Jandy JXi400 working via RS485 on a Nixie board. I've been running it successfully for several weeks and there are a few protocol details that differ from the upstream jxi implementation: 1. Heater broadcasts 0x25 autonomously after every command The JXi sends a 0x25 temp response on its own after every command — no explicit query is needed. My working implementation just listens for inbound 0x25 frames passively. Sending a separate 0x25 query creates a second redundant frame and can cause parser collisions if both arrive close together. 2. Temp byte index: payload[6], not payload[5] The 0x25 response payload (excluding the action byte) is 6 bytes: [0]=0x33, [1]=counter, [2]=0x04, [3]=0xF7, [4]=0xF5, [5]=temp°F+20. With the action byte counted as part of the payload, the temp is at payload[6] (i.e., payload[5] in a 0-indexed slice that excludes the action byte — depends on how your parser counts it). The upstream code was reading one byte too early, giving garbage temp readings. 3. Heat command needs mode arg byte Command 0x0C must include an arg byte: [0xE9] for pool mode, [0xEE] for spa mode. Without it, the heater doesn't respond correctly. 4. Status bitmask for burner-on: 0x08 The 0x0D status frame uses bit 0x08 = burner ON, 0x10 = burner OFF (matches public Jandy protocol docs). Pending live-fire verification on my end when I de-winterize. I've implemented this as type jandyrs485 on my fork (chevyzr1/nodejs-poolController-jxi, branch feature/jxi-heater). Happy to share more detail or coordinate merging the corrections back into the upstream jxi type.

…

On May 9, 2026, at 6:49 PM, Roy L ***@***.***> wrote: The timing of this update is a bit amusing as I was impatient and decided to give Claude a try and intgrate rs 485 comms with Jandi JXI400 myself. I was successful after several (about a week) of failed attempts. I’m sure your version is much better but I will share mine for giggles. I ended up adding a separate RS485 adapter to my pi as my pentair pump communicates on my primary port and since the Jandy uses a different message structure I was seeing a lot of collisions with them both on the same adapter. I will give yours a try and see if there’s any difference. One thing that I found and what took so much time was getting the flame widget to work with the heater on RS485 mode. Also getting the address dropdown widget under heaters took some time. See here:https://github.com/chevyzr1/nodejs-poolController-jxi/tree/feature/jxi-heater > On May 9, 2026, at 6:00 PM, tagyoureit ***@***.***> wrote: > > > Thx. Pull njsPC/dP again. The UI was missing the configurable elements including the address. > > — > Reply to this email directly, view it on GitHub <#1128 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BH52N4D6CRHI6OLZIIAN3ID4Z6TA3AVCNFSM6AAAAACYC2U75SVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMOBWGUZTENY>. > Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > You are receiving this because you commented. >

[tagyoureit]

Most of these I had correct. Updated a couple small items like the bitmask. Check out my version. I couldn't see your repo because it's private but happy to include any other changes that need to be made.

[hubuser01]

number 3 - would we need to send (hex) 10 02 68 0c e9 [checksum] 10 03
would the checksum be (10+02+68+0c+e9) & ff -or- (68+0c+e9) & ff

[tagyoureit]

Yup, I did include a fix for that last week.

[hubuser01]

sorry, that was intended for chevyzr1. Figured if they had it working, they could confirm a few things. I'm finding a lot of conflicting information on this heater. My power interface board is showing red on the D4 led which indicates a problem on the board. Everything is working fine on the heater so it might be the aqualink interface that is complaining. Might have screwed it up messing with it. I have a power interface board on order. Should be getting it Wednesday. Hopefully ill have time to mess with it by the end of the week.

[hubuser01]

It finally stopped raining, got time to replace the power interface board and can now send/receive data to/from the heater.

The replacement board version:
Jandy JXI260N
PI Rev JXi: 7.05
UI FW rev: 1.8

The wiring looks like this:

1. RED: Not Connected (and do even think about connecting this! find another power source for your raspberry pi!)
2. BLK: RS-485 Data+
3. YEL: RS-485 Data-
4. GRN: Not Connected
   Using cat 5 white/blue pair and is about 25' (for now) and not using any terminating resisters,
   EDIT: Permanent wire in place ~115' not using terminating resisters and it is working like a champ

Heater set to Remote - T-Stat

Serial port is set up for 9600,n,8,1

Confirmed the checksum should include DLE and STX (sorry @tagyoureit - Could you "unfix" your fix)
sum = a[0] + a[1] + a[2] + a[3] + a[4]
checksum = sum & 255

Send out decimal characters: 16 2 104 37 0 159 16 3
Receives decimal characters: 16 2 0 37 0 0 9 0 0 0 89 153 16 3 (yep.. the pool is 69F)

@tagyoureit now that I am at this point, let me know if there is anything I can do to help out. And yet again.... Thank You!

[d5coupe]

Jandy JXi (device 104) never replies on a shared Pentair RS-485 bus — all polls abort 3/3, all other equipment fine (njsPC 9.1.0, Nixie)

Summary

On a Nixie (virtual/standalone) controller, njsPC 9.1.0 polls a newly added Jandy JXi heater but never gets a reply — every poll aborts after 3 attempts. Meanwhile every other device on the same RS-485 bus (Pentair IntelliFlo VSF pump + IntelliChlor IC40) communicates normally, and the bus failure rate sits at ~0.07–0.09%. I have matched the wiring + heater-mode combination reported as working in earlier discussions and still get nothing back from the heater. Looking for guidance on whether this is a config/address/mode issue or something in the 9.1 JXi decoder.

Environment

• njsPC: 9.1.0 — ghcr.io/tagyoureit/njspc:latest (confirmed package.json version 9.1.0)
• dashPanel: ghcr.io/rstrouse/njspc-dash:latest
• Host: Docker on Synology NAS (Container Manager project)
• Controller type: Nixie — Single Body
• RS-485 transport: Elfin EW11 (WiFi↔RS-485) over network — POOL_NET_CONNECT to 192.168.1.74:8899, 9600 8N1
• Primary Port stats (healthy): ~69,000 successful reads, 61 failed, 58 collisions, failureRate 0.09%

Equipment on the shared bus

Device | Address | Protocol | Status -- | -- | -- | -- IntelliFlo VSF pump | 96 | Pentair | Working (occasional normal retry) IntelliChlor IC40 | 80 | Pentair | Working Jandy JXi heater | 1 (→ device 104) | Jandy | Never replies

JXi control board: R-Kit R0988700, board H0774700_REVC.

dashPanel heater config

• Type: Jandy JXi
• Body: Pool
• Address: 1
• Cooldown Delay: 5 min
• Start/Stop Temp Delta: 1 °F / 1 °F
• Connection: Primary Port (same EW11 bus as pump + IC40)

The failure

njsPC polls the heater on a steady cycle and aborts every time:

error: Communication error with JXi heater: Message aborted after 3 attempt(s): 16,2,104,12,0,116,16,3

Decoding that frame: 0x10 0x02 | 104 (0x68 device) | 12 (0x0C command) | 0x00 | 0x74 (checksum) | 0x10 0x03. So njsPC is addressing device 104, command 12, which matches the documented JXi addressing/command. The heater simply never responds — 3/3 aborts, every cycle, indefinitely.

Critically, during these heater aborts the pump and IC40 continue to respond normally (their only failures correlate with me cycling the shared breaker while wiring). So this is isolated to the heater, not a bus-wide problem.

What I have already tried

Heater Remote mode:

• Tried Remote RS485 — aborts.
• Tried Remote T-STAT — aborts. T-STAT confirmed displayed on the panel and persists across a heater power cycle.

Wiring (heater RS-485 red terminal bar, R B Y G):

• Tried Yellow/Green as the data pair (per JXi manual wiring diagram).
• Tried the two middle terminals — Black = Data+, Yellow = Data−, with Red and Green left unconnected (per a prior discussion where this combination was reported working).
• Confirmed the heater data pair is electrically continuous with the same D+/D− the working pump/IC40 ride on.

Polarity: swapped the data pair both ways in each wiring configuration.

Other: address set to 1 (→ device 104); multiple heater + container power cycles.

Result: device 104 never replies in any combination of mode/wiring/polarity. All other bus equipment communicates throughout.

Questions

1. For a JXi on a Nixie controller, is device 104 / command 12 the expected address+poll, or should the dashPanel address map differently?
2. Does the 9.1 JXi support expect the heater in Remote RS485 or Remote T-STAT mode? (A prior working report used T-STAT + Black/Yellow; I have replicated that exactly without success.)
3. Is a JXi expected to work on a shared bus with Pentair equipment, or does the Jandy device need its own RS-485 port?
4. Given the heater is mute, would you expect to see any inbound bytes from device 104 in a capture, or does this pattern indicate the heater isn't decoding njsPC's poll at all?

[hubuser01]

Decoding that frame: 0x10 0x02 | 104 (0x68 device) | 12 (0x0C command) | 0x00 | 0x74 (checksum) | 0x10 0x03. So njsPC is addressing device 104, command 12, which matches the documented JXi addressing/command. The heater simply never responds — 3/3 aborts, every cycle, indefinitely.

The JXi heater will not respond because the checksum is off.
The checksum should be 134(0x86) and is off by 18(0x12) which is the first part of the frame 0x10 0x02.

This is my fault. tagyoureit created an offset to the JXi protocol checksum based on something I told them on the 9.1.0 version.

This is what I did to try to remove the checksum offset:
line 266 of /home/[username]/nodejs-poolController/controller/comms/messages/Messages.ts
original line:
let start = this.protocol === Protocol.Jandy ? 2 : 0;
changed to:
let start = this.protocol === Protocol.Jandy ? 0 : 0;

This is probably not a proper fix but this is what I tried.
Not sure if this would work in a docker environment.

Hoping version 9.1.1 will remove this offset.

I do not think tagyoureit has this pool heater to test his code and have not seen a confirmed case where this is completely working yet.

What version JXi Heater do you have? Mine shows up briefly when you first apply power. You have an option Remote RS485 that my heater does not have. Mine is set for Remote T-Stat.

What ever you do...DO NOT connect the Red wire to anything! I tried to use this voltage to power a raspberry pi and ended up having to order another board. The board worked fine in all aspect except for the RS485.

Question 1: My heater address is 104 and responds to command 12 (when the checksum is correct). I do not see a way to change the address on the heater itself.
Question 2: Unsure about the Remote RS485 as my heater does not have that option. Mine works with Remote T-Stat. My wiring is working as stated above. Put in a permanent wire yesterday that is about 200' long and is working flawlessly.
Question 3: RS485 supports many devices and njspc is using both protocols on the same bus. You may need terminating resisters, but do not worry about this until the checksum gets corrected.
Question 4: JXi is using the RS485 in a "modbus" type mode. The heater should not communicate on the bus unless it gets a valid packet from a device with the address of 0(controller/njsPC).

Hope this helps
BTW, compliments on your write up. Detailed, organized and it looks pretty.
Wish there was a way to give tagyoureit more time to work on this. Their work is very much appreciated.

[d5coupe]

Thanks for the reply! I am using a Jandy JXIQ 400 with versaflow.

[hubuser01]

Are you able to get the version number off of the display when you apply power to the heater?

[hubuser01]

With the applied checksum work around on the prior post, njsPC is not showing pool temperature. njsPC log is showing: "The body temperature for Pool cannot be determined." not sure if you want logs posted here. Let me know if you want them.

This is a confirmed way to get the water temperature from the heater
-->[16, 2, 104, 37, 0, 159, 16, 3]
<--[16, 2, 0, 37, 0, 0, 16, 0, 0, 0, 0, 86, 157, 16, 3]
37[0, 0, 16, 0, 0, 0, 0, 86]Water Temp = 66
86 - 20 = water temp 66

I also read somewhere that a 16 in the data portion of the packet requires a [null] 0 right after and that null needs to be removed from the data. So there might be an extra 0 in the data for every 16 seen.
Assuming so it does not get confused with the [DLE] 16 [STX] 2 start of frame or [DLE] 16 [ETX] 3 end of frame.
I've seen a 9 returned instead of 16: [16,2,0,37],[0,0,9,0,0,0,89],[153,16,3] - One less 0
Not sure what the 9 or 16 means
EDIT: Data[0] - GV On Time in hours
EDIT: Data[1] - Assuming and not proved - GV On Time in hours byte 2
EDIT: Data[2] - Number of Cycles byte 1
EDIT: Data[3] - Number of Cycles byte 2
EDIT: Data[4] - ?
EDIT: Data[5] - ?
EDIT: Data[6] - Temperature + 20
njsPC 9.1.0 does not turn on the pool or spa and the temperature is not reporting.

Scanned commands 0 - 255 data 0 - only got responses from 0, 12 and 37
Scanned commands 0 data 0-255 - all had same response
Scanned commands 37 data 0-255 - all had same response
Hoping to scan the 12 commands to see what else can be found. Hoping to find a way to read the display, create set points, read flow sensor, read errors, etc...

[hubuser01]

1|njsPC | [02/06/2026, 17:05:35] info: {"port":0,"id":81,"valid":true,"dir":"out","proto":"jandy","pkt":[[],[], [16,2,104,12], [0],[134,16,3]],"ts":"2026-06-02T17:05:35.903-0400"}
1|njsPC | [02/06/2026, 17:05:35] verbose: Wrote packet [Port 0 id: 81] [16,2,104,12,0,134,16,3].Retries remaining: 2
1|njsPC | [02/06/2026, 17:05:35] silly: Message in 82 is a response for message out 81
1|njsPC | [02/06/2026, 17:05:35] info: {"port":0,"id":82,"valid":true,"dir":"in","proto":"jandy","for":[81],"pkt":[[],[],[16,2,0,13],[16,0,0,0],[47,16,3]],"ts": "2026-06-02T17:05:35.936-0400"}

command [16,2,104,12], [0],[134,16,3] does not appear to be a valid command.
the heater will do nothing and it will return -->[16, 2, 104, 12, 0, 134, 16, 3] <--[16, 2, 0, 13, 0, 0, 0, 31, 16, 3] | 13[0, 0, 0]

-->[16, 2, 104, 12, 0, 134, 16, 3] <--[16, 2, 0, 13, 16, 0, 0, 0, 47, 16, 3] | 13[16, 0, 0]Error
This will happen if there is a non complete or corrupt command sent on the rs485 bus prior to issuing a command. the heater seems to store that data for a long time causing the new command to be appended to any buffered data giving you the 13[16,0,0,0] response. This happens with any command, not just 12 commands. This issue may be from a prior command sent.
This is also that 16 data scenario were the null (0) after the 16 needs to be removed and should not be part of the data.

The outcome of the scan: 16,2,104,12,x,[checksum],16,3

<title></title>
<meta name="generator" content="LibreOffice 26.2.3.2 (Windows)"/>
<style type="text/css">
	body,div,table,thead,tbody,tfoot,tr,th,td,p { font-family:"Liberation Sans"; font-size:x-small }
	a.comment-indicator:hover + comment { background:#ffd; position:absolute; display:block; border:1px solid black; padding:0.5em;  } 
	a.comment-indicator { background:red; display:inline-block; border:1px solid black; width:0.5em; height:0.5em;  } 
	comment { display:none;  } 
</style>

pool on		spa on		pool on		spa on
decimal	hex	decimal	hex	decimal	hex	decimal	hex
9	9	10	A	13	D	14	E
25	19	26	1A	29	1D	30	1E
41	29	42	2A	45	2D	46	2E
57	39	58	3A	61	3D	62	3E
73	49	74	4A	77	4D	78	4E
89	59	90	5A	93	5D	94	5E
105	69	106	6A	109	6D	110	6E
121	79	122	7A	125	7D	126	7E
137	89	138	8A	141	8D	142	8E
153	99	154	9A	157	9D	158	9E
169	A9	170	AA	173	AD	174	AE
185	B9	186	BA	189	BD	190	BE
201	C9	202	CA	205	CD	206	CE
217	D9	218	DA	221	DD	222	DE
233	E9	234	EA	237	ED	238	EE
249	F9	250	FA	253	FD	254	FE

With this scan outcome, it looks like the heater is only using the 4 least significant bits which tells me there can only be 16 values.

This is what you get when you turn on the pool or spa
-->[16, 2, 104, 12, 233, 111, 16, 3]
<--[16, 2, 0, 13, 8, 0, 0, 39, 16, 3]
13[8, 0, 0]Status

8 appears to be an OK or ACK
16 appears to be an ERROR or FAIL

If a response of 8 is given that does not mean that the heater is on. We disconnected the water flow sensor which shuts off the heater. Then issues a Pool On command 12[233], heater responded with 12[8,0,0] but it does not turn on.

If the heater is set to offline mode from the heater panel and then issues a Pool On command 12[233], it will return 13[16,0,0] and the heater will not turn on.

Still digging to find a way to get the status of the heater, errors, etc....

[hubuser01]

Not really finding anything else. The only other thing not mentioned yet is to turn off the heater/spa. To do that, just do not send any commands for a little over 20 seconds. I have written "heater controller" python script that will put this heater into Home Assistant. Wife is pretty happy. Hopefully there is enough info here to help you implement this heater. If not, let me know what else you need.

[chevyzr1]

Hubuser01 apologies for the delayed response as I just found this thread in my junk folder.My heater has been working without issue for the last month via the rs485 interface. I also just added a heater interlock function widget in the UI for my heater bypass valves. I'm not able to tell clearly from this thread where you landed so please let me know how I can help get this running for you. I'm happy to provide logs, fw version, etc. whatever you need!Sent from my iPhoneOn May 18, 2026, at 3:03 PM, hubuser01 ***@***.***> wrote: sorry, that was intended for chevyzr1. Figured if they had it working, they could confirm a few things. I'm finding a lot of conflicting information on this heater. My power interface board is showing red on the D4 led which indicates a problem on the board. Everything is working fine on the heater so it might be the aqualink interface that is complaining. Might have screwed it up messing with it. I have a power interface board on order. Should be getting it Wednesday. Hopefully ill have time to mess with it by the end of the week. —Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you commented.Message ID: ***@***.***>

[hubuser01]

@chevyzr1 Some things you said about your JXi heater seems to act differently than my JXi heater. What is your exact model number? I'm wondering if your heater is a JXiQ. Mine is a Jandy JXI260N. What version number(s)? My version numbers show up briefly upon power up as PI Rev JXi: 7.05 UI FW rev: 1.8
I ended up writing a heater controller in python. Mqtt was included for Home Assistant integration. Now we can schedule turn on/off times and see pretty charts. Wife is super happy that she does not have to wake up at 4am to turn on the heater anymore. It has been running issue free for about three weeks now. Wife Approval Factor points gained: 46

[chevyzr1]

The wife approval factor is what makes it all worth it! That and it gives us an excuse to tinker 😆😉I have a JXi400 without the N. It's not the latest model as my menu does not have a dedicated "RS485" option, I only have "remote t-stat" which serves as both the RS485 comms or the remote fireman's switch depending on which is being used. Once I was able to get the serial communication operational it now displays a message "RS485 control" on the heater ui.I'm currently traveling for work until tomorrow afternoon. I will get the information you requested. I'm also happy to share logs if that's helpful. I'm currently using the pool controller dashboard from the repo with some custom add ons I've integrated as mentioned previously. It's been working flawlessly and my wife can operate it via my Home Assistant instance I setup for her (didn't want her operating the controls from the dashboard as there's too many thing to mess with). It's nice having the additional integration the RS485  offers with an additional temp reporting from the heater, along with the burner status that lets me know when the heater has actually fired. Sent from my iPhoneOn Jun 23, 2026, at 4:06 PM, hubuser01 ***@***.***> wrote: @chevyzr1 Some things you said about your JXi heater seems to act differently than my JXi heater. What is your exact model number? I'm wondering if your heater is a JXiQ. Mine is a Jandy JXI260N. What version number(s)? My version numbers show up briefly upon power up as PI Rev JXi: 7.05 UI FW rev: 1.8 I ended up writing a heater controller in python. Mqtt was included for Home Assistant integration. Now we can schedule turn on/off times and see pretty charts. Wife is super happy that she does not have to wake up at 4am to turn on the heater anymore. It has been running issue free for about three weeks now. Wife Approval Factor points gained: 46 —Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[hubuser01]

My heater was bought in 2018. The power interface board was just replaced with a board with newer firmware. From 6.03 to 7.05. I may have killed my original board trying to power the raspberry pi with it. Never got the rs485 to work on that board. The remote options are: remote tstat, standalone, hi-lo-com and when there is data on the rs485 bus a forth rs485 option shows up. This does not send out autonomous 0x25 responses like yours does. It has to be requested by the 0x25 command. Maybe there is a command that can set this on or off. The set points seem to be ignored if using rs485 to control the heater. The only way to tell if the burner is on is to watch for GV on Time or the temperature increment. GV on Time could take an hour and the temperature increase could be from warmer outside temperature so not always a true indication. A cycle count increase does not necessarily mean that the burner is on due to no water flow, high limit, ignition faults, etc. Switching from pool to spa will increment the cycle count even though the burner stays on when switching. I was going through the Aqualink code and there is some info in it. Just have not had the time to test any of it. I really want true burning indication, error info and display messages. I may hit you up for logs, but not real sure what to ask for at this time. This is the time where we have to be real careful not to break the controls in Home Assistant. Wife Approval Factor could easily go to -100 with one bad automation.

[d5coupe]

Hey guys, glad this discussion is continuing. I cannot get the connection to NJSPC to work. I have a JXIQ400:
PI FW REV: 1.33
UI FW REV: 1.19
It has both TSTAT and RS485 options in the menu. Wiring is correct. Any ideas how to resolve the connection issue? Thanks!

[hubuser01]

Your heater has an Address option in the service mode menu. What is it currently set at and what are the other options? This may be changing the rs485 address of the heater. Or maybe the address for the JXiQ might be completely different than the JXi. See if this command returns anything: 16 2 104 0 0 122 16 3
you can try other addresses. We have been assuming yours is 104.
The 122 is the checksum value, it must equal to the sum of the first 5 decimals. so 16+2+104+0+0=122.
So to try other addresses:
address 103 = 16 2 103 0 0 121 16 3
address 105 = 16 2 105 0 0 123 16 3
If the checksum becomes greater than or equal to 256 then subtract 256 from the result.
address 238 = 16 02 238 0 0 0 16 3
address 239 = 16 02 239 0 0 1 16 3
From what I can tell the addresses could be anything from 1 to 247
This could be a pain to find.
Just maybe if we are nice enough, tagyoureit could maybe add or create some sort of discovery code. wink wink

[hubuser01]

Did a git pull but it shows Already up to date.

[hubuser01]

not the master.. found the branch: WS-ICv1-ICv3-Refactor
Found 5 errors in 5 files.
Errors Files
1 test/integration/suites/circuits.test.ts:1
1 test/integration/suites/config-writes.test.ts:1
1 test/integration/suites/lights-groups.test.ts:1
1 test/integration/suites/system-options.test.ts:1
1 test/integration/vitest.config.ts:1
all error say: Cannot find module 'vitest' or its corresponding type declarations.

nodejs-poolcontroller will not start

[tagyoureit]

Ah, pushed to the wrong branch. It's back on master now. But for the errors above you just need to npm i to install the vitest dependency.

[hubuser01]

The above errors were due to a corrupt SD card. npm i was not installing dependencies. New card installed and loaded. Running on master version 10 now.

[hubuser01]

Added heater, started heater, stopped heater, removed heater.
-No pool temp reported
Looks like you are sending 12 0 but this does not respond with pool temp. The command to get that info is 37 0
-Heater does not start
Does not even look like a pool start command was issued. maybe due to "The body temperature for Pool cannot be determined. Heater status for this body cannot be calculated."

Here are the logs:

[29/06/2026, 15:11:02] info: Serial port: /dev/ttyUSB0 request to open successful 9600b 8-none-1
[29/06/2026, 15:11:11] info: [15:11:11] 192.168.1.45 PUT /config/heater {"id":-1,"name":"Heater 1","type":8,"body":0,"address":104,"cooldownDelay":0,"startTempDelta":1,"stopTempDelta":1,"connectionId":null,"deviceBinding":null}
[29/06/2026, 15:11:11] info: Adding a new heater with id 256
[29/06/2026, 15:11:11] info: A Heater was not found for id #256 creating Heater
[29/06/2026, 15:11:11] info: {"port":0,"id":87,"valid":true,"dir":"out","proto":"jandy","pkt":[[],[], [16,2,104,12], [0],[134,16,3]],"ts":"2026-06-29T15:11:11.896-0400"}
[29/06/2026, 15:11:11] verbose: Wrote packet [Port 0 id: 87] [16,2,104,12,0,134,16,3].Retries remaining: 2
[29/06/2026, 15:11:11] silly: Message in 88 is a response for message out 87
[29/06/2026, 15:11:11] info: {"port":0,"id":88,"valid":true,"dir":"in","proto":"jandy","for":[87],"pkt":[[],[],[16,2,0,13],[16,0,0],[47,16,3]],"ts": "2026-06-29T15:11:11.931-0400"}
[29/06/2026, 15:11:14] info: [15:11:14] 192.168.1.45 GET /config/all
[29/06/2026, 15:11:14] info: [15:11:14] 192.168.1.45 GET /state/appVersion
[29/06/2026, 15:11:14] info: [15:11:14] 192.168.1.45 GET /app/config/log
[29/06/2026, 15:11:14] info: [15:11:14] 192.168.1.45 GET /app/config/options/backup
Updating config file
[29/06/2026, 15:11:19] info: Reloading app config: config.json
Updating config file
[29/06/2026, 15:11:19] info: Reloading app config: config.json
[29/06/2026, 15:11:21] warn: Inactivity timeout for 0 serial port /dev/ttyUSB0 after 10 seconds
[29/06/2026, 15:11:21] info: Serial Port 0 - /dev/ttyUSB0 has been closed.
[29/06/2026, 15:11:21] info: Successfully closed portId 0 for serial port /dev/ttyUSB0
[29/06/2026, 15:11:21] info: Serial port: /dev/ttyUSB0 request to open successful 9600b 8-none-1
[29/06/2026, 15:11:22] info: [15:11:22] 192.168.1.45 PUT /state/circuit/setState {"id":6,"state":true}
[29/06/2026, 15:11:22] verbose: Turning on a body circuit Pool
[29/06/2026, 15:11:22] info: NCP: Setting Circuit Pool to true
[29/06/2026, 15:11:22] warn: The body temperature for Pool cannot be determined. Heater status for this body cannot be calculated.
[29/06/2026, 15:11:25] warn: The body temperature for Pool cannot be determined. Heater status for this body cannot be calculated.
[29/06/2026, 15:11:25] info: [15:11:25] 192.168.1.45 PUT /state/circuit/setState {"id":6,"state":false}
[29/06/2026, 15:11:25] verbose: Turning off a body circuit Pool
[29/06/2026, 15:11:25] info: NCP: Setting Circuit Pool to false
[29/06/2026, 15:11:26] info: {"port":0,"id":89,"valid":true,"dir":"out","proto":"jandy","pkt":[[],[], [16,2,104,12], [0],[134,16,3]],"ts":"2026-06-29T15:11:26.935-0400"}
[29/06/2026, 15:11:26] verbose: Wrote packet [Port 0 id: 89] [16,2,104,12,0,134,16,3].Retries remaining: 2
[29/06/2026, 15:11:26] silly: Message in 90 is a response for message out 89
[29/06/2026, 15:11:26] info: {"port":0,"id":90,"valid":true,"dir":"in","proto":"jandy","for":[89],"pkt":[[],[],[16,2,0,13],[0,0,0],[31,16,3]],"ts": "2026-06-29T15:11:26.968-0400"}
[29/06/2026, 15:11:36] warn: Inactivity timeout for 0 serial port /dev/ttyUSB0 after 10 seconds
[29/06/2026, 15:11:36] info: Serial Port 0 - /dev/ttyUSB0 has been closed.
[29/06/2026, 15:11:36] info: Successfully closed portId 0 for serial port /dev/ttyUSB0
[29/06/2026, 15:11:36] info: Serial port: /dev/ttyUSB0 request to open successful 9600b 8-none-1
[29/06/2026, 15:11:41] info: {"port":0,"id":91,"valid":true,"dir":"out","proto":"jandy","pkt":[[],[], [16,2,104,12], [0],[134,16,3]],"ts":"2026-06-29T15:11:41.970-0400"}
[29/06/2026, 15:11:41] verbose: Wrote packet [Port 0 id: 91] [16,2,104,12,0,134,16,3].Retries remaining: 2
[29/06/2026, 15:11:42] silly: Message in 92 is a response for message out 91
[29/06/2026, 15:11:42] info: {"port":0,"id":92,"valid":true,"dir":"in","proto":"jandy","for":[91],"pkt":[[],[],[16,2,0,13],[0,0,0],[31,16,3]],"ts": "2026-06-29T15:11:42.013-0400"}
[29/06/2026, 15:11:52] warn: Inactivity timeout for 0 serial port /dev/ttyUSB0 after 10 seconds
[29/06/2026, 15:11:52] info: Serial Port 0 - /dev/ttyUSB0 has been closed.
[29/06/2026, 15:11:52] info: Successfully closed portId 0 for serial port /dev/ttyUSB0
[29/06/2026, 15:11:52] info: Serial port: /dev/ttyUSB0 request to open successful 9600b 8-none-1
[29/06/2026, 15:11:54] info: [15:11:54] 192.168.1.45 GET /config/all
[29/06/2026, 15:11:54] info: [15:11:54] 192.168.1.45 GET /config/options/general
[29/06/2026, 15:11:54] info: [15:11:54] 192.168.1.45 GET /config/options/alerts
[29/06/2026, 15:11:54] info: [15:11:54] 192.168.1.45 GET /config/options/rs485
[29/06/2026, 15:11:54] info: [15:11:54] 192.168.1.45 GET /config/options/security
[29/06/2026, 15:11:57] info: {"port":0,"id":93,"valid":true,"dir":"out","proto":"jandy","pkt":[[],[], [16,2,104,12], [0],[134,16,3]],"ts":"2026-06-29T15:11:57.018-0400"}
[29/06/2026, 15:11:57] verbose: Wrote packet [Port 0 id: 93] [16,2,104,12,0,134,16,3].Retries remaining: 2
[29/06/2026, 15:11:57] silly: Message in 94 is a response for message out 93
[29/06/2026, 15:11:57] info: {"port":0,"id":94,"valid":true,"dir":"in","proto":"jandy","for":[93],"pkt":[[],[],[16,2,0,13],[0,0,0],[31,16,3]],"ts": "2026-06-29T15:11:57.043-0400"}
[29/06/2026, 15:11:57] info: [15:11:57] 192.168.1.45 GET /config/options/heaters
[29/06/2026, 15:12:00] info: [15:12:00] 192.168.1.45 DELETE /config/heater {"id":256,"name":"Heater 1","type":8,"body":0,"address":104,"cooldownDelay":0,"startTempDelta":1,"stopTempDelta":1,"connectionId":null,"deviceBinding":null}
[29/06/2026, 15:12:00] info: {"port":0,"id":95,"valid":true,"dir":"out","proto":"jandy","pkt":[[],[], [16,2,104,12], [0],[134,16,3]],"ts":"2026-06-29T15:12:00.302-0400"}
[29/06/2026, 15:12:00] verbose: Wrote packet [Port 0 id: 95] [16,2,104,12,0,134,16,3].Retries remaining: 2
[29/06/2026, 15:12:00] silly: Message in 96 is a response for message out 95
[29/06/2026, 15:12:00] info: {"port":0,"id":96,"valid":true,"dir":"in","proto":"jandy","for":[95],"pkt":[[],[],[16,2,0,13],[0,0,0],[31,16,3]],"ts": "2026-06-29T15:12:00.338-0400"}
[29/06/2026, 15:12:00] info: Closing JXi Heater Heater 1
[29/06/2026, 15:12:10] warn: Inactivity timeout for 0 serial port /dev/ttyUSB0 after 10 seconds
[29/06/2026, 15:12:10] info: Serial Port 0 - /dev/ttyUSB0 has been closed.
[29/06/2026, 15:12:10] info: Successfully closed portId 0 for serial port /dev/ttyUSB0

[hubuser01]

I am not sure how to change the Heat Mode. When Heat Mode it is clicked, a popup for the set point comes up and have not seen a way to turn it on. Clicking the Pool Icon or the Feature Pool Button will turn them green, but it does not change the Heat Mode to on. I have never seen a query in the logs for requesting Pool Temp. (Again, Thank you!) I am beginning to wonder if you ever have time to enjoy your pool since starting this project.

[tagyoureit]

Nixie needs to be fed temperatures from an external source, like REM (see REM wiki).

The heat modes are only relevant for the currently installed heaters. In the screenshot, you have no heaters installed so no heat modes will appear.

And I currently don't own a pool 😢 ... but I do get to enjoy the one in my complex. 😄

[hubuser01]

oh, there is no way to use the built in thermal sensor on this heater? ("consider this an official feature request") I do have a plethora amount and types of thermal sensors lying around. You just never know when you need to know the attic temp and humidity levels.
There is the Jandy heater, but it does not show up in the Pool Heat Settings popup.

If I add heater type JXi or LXi, a heater will not show up. Tried adding Gas Heater and that showed up in the list.

[tagyoureit]

The heat modes not showing is a real bug. Pull the latest.

You can use the API to set temps in the interim, but ultimately Nixie needs temps fed into them so it knows when to tell the heater to heat.

curl -X PUT http://localhost:4200/state/temps \
  -H "Content-Type: application/json" \
  -d '{"air": 65, "waterSensor1": 64}'

Once you get the heater up and running, we can definitely look at using the heater reported temp as the input water temp.

[hubuser01]

I did not do extensive testing, but did a quick and dirty test...
turned the pool green
start temp delta set at 1
stop temp delta set at 1
set point 70
heat mode heater
set pool temp 71 - heater did not start
set pool temp 70 - heater did not start
set pool temp 69 - heater started
set pool temp 70 - continue heating
set pool temp 71 - heater stopped

I think you got it! Can we call it?.... The JXi260n officially supported! WooHoo!!!!
Jandy JXI260N
pi rev JXi: 7.05
UI FW rev: 1.8

Let me know if you want any other test run. We have people coming over most of this week end so we might not be able to test until after the party is over.

Not sure why nobody want to come over and swim...

Cant wait to see the gas bill.

Sorry, couldn't resist
And before I forget...Thank You!