J335 (Unencrypted)

[srleach]

Sorry, I moved the code from the PR into the main branch and wanted to ensure we don't lose track @BlackAngel2109

I've been stubbing out the message sending and I'm at a position of probably 80% comfort with the functionality on an encrypted spa now.

I'd really like to see an extended capture on yours. The updated file you attached last week still only had 100 lines - so I wonder if you need to tweak this then leave it running for a bit?

I suspect that we'll need to send a config message to get it to start emitting what we want, which is fine if required but it'd be handy to know, and to have some data to work from my end.

I think, based on what I've done with mine, once we've got yours working, getting an encrypted or unencrypted spa to work with the code should be as simple as a config file, even if the message format or structure changes somewhat between specific tubs.

[BlackAngel2109]

Tried giving it another go just now. As like the last time I'm at work but I gave it a go remotely...

Getting error when I try from the logs -

Lines
100
Actions

Warning: Config file not found. Using some defaults

INFO:spa2mqtt.spas.base.communicator.communicator:Instantiated default communicator with target 192.168.100.47:4257

Traceback (most recent call last):

File "/app/spa2mqtt/main.py", line 44, in

asyncio.run(main())

File "/usr/local/lib/python3.11/asyncio/runners.py", line 190, in run

return runner.run(main)

       ^^^^^^^^^^^^^^^^

File "/usr/local/lib/python3.11/asyncio/runners.py", line 118, in run

return self._loop.run_until_complete(task)

       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/local/lib/python3.11/asyncio/base_events.py", line 654, in run_until_complete

return future.result()

       ^^^^^^^^^^^^^^^

File "/app/spa2mqtt/main.py", line 38, in main

mqtt.attach_spa(spa)

^^^^^^^^^^^^^^^

AttributeError: 'NoneType' object has no attribute 'attach_spa'

Warning: Config file not found. Using some defaults

[BlackAngel2109]

If I change - VARIANT_DEFINITION=jacuzzi_j235_encrypted I don't get the errors but I don't get any communications.

Warning: Config file not found. Using some defaults

INFO:spa2mqtt.spas.base.communicator.communicator:Instantiated default communicator with target 192.168.100.47:4257

INFO:spa2mqtt.spas.base.communicator.communicator:Attaching update handler.

INFO:spa2mqtt.spas.base.communicator.communicator:Connected to spa.

[srleach]

When you update to use the jacuzzi_j235_encrypted - I believe you actually are getting comms but you're not getting any known messages so it's just sitting silent.

Have you updated the code? It's quite likely I broke something in the debug paths I set up for your comms variant while tweaking the message sending for mine. I'll see if I can resolve.

[srleach]

Yep I can replicate this - bear with me a little bit, will try and get it sorted before I hit the sack.

[srleach]

Should be working again. Thanks for helping with your hardware!

You'll have to pull on branch main and re-build the portainer deploy from main

[BlackAngel2109]

Ok, got another file with hopefully a few more lines.... Let me know if you need more.
_spa2mqtt_logs.txt

[BlackAngel2109]

Just wondering if there's been any progress for the unencrypted J345 (my tub)?

[srleach]

Hey @BlackAngel2109 - Sorry for the quiet here. Life got in the way - kids and all that. The coming of winter here got me re-enthusiastic about trying to solve this, so I rewrote things a little more robustly, and found a few mistakes I'd made before. I think I owe it to you to try and get yours working here, too. I'll open a change to aim to support your tub based on the previous data you shared late last year.

[srleach]

Sorry again for the long silence on this @BlackAngel2109, and thanks for your patience and for all the logs.

There is now support for your tub. I rewrote the bridge this autumn, and v2.1.0 adds a definition for the unencrypted J345 through the ProLink module, built from the logs you posted here and on #11 and checked against pyjacuzzi.

I don't have a tub like yours, so none of it has been run against the real thing. It starts receive-only and sends nothing until you switch transmit on.

Setup guide, including Portainer on Home Assistant OS (environment variables only, no volume mounts this time): https://srleach.github.io/spa2mqtt/tubs/jacuzzi-j345/

The short version is the published image ghcr.io/srleach/spa2mqtt:latest with:

SPA_DEFINITION=jacuzzi_j345
SPA_IP=<your ProLink's address>
SPA_PORT=4257
MQTT_BROKER=<your broker>

What it should do:

• Read: water and target temperature, both pight colour and brightness.
• Control, once you enable transmit: pump 1 and 2, the nine light colours, brightness, and set temperature (80–104
  °F). These are only the commands your pyjacuzzi log shows working.

If you get a chance to try it, these would help most:

1. Does the water temperature in Home Assistant match the topside?
2. Does "Heater Active" match the heater indicator? That one is a guess from the data.
3. Do your pumps have a low speed, and is there a pump 3 or a blower?
4. Is your topside ever set to Celsius? Setting the temperature is blocked in that mode for now.

The guide has a "Send captures back" section if you can grab a log while pressing things at the topside. I called it a J345 because that's what you said most recently; shout if it's actually a J335.