Hayward Aqualogic Pool Controller Automation with Home Assistant - cajuncoding/HomeAssistant GitHub Wiki

Awesome! It took some tinkering but everything is working great now!

Thanks for posting the screenshots and details in this thread...@stoehrmark's post from Jan. 2019 really helped!

I haven’t found any clear/consolidated instructions on proper setup of the USR-TCP232-304, but the critical details are all there between the HomeAssistnat thread above, the device manual, and in the notes from @swilson in github here...

The manual for the USR-TCP232-304 is located here...

The screenshot finally helped me understand that there is a TCP Server working mode that I had not fully gleaned from the online manual, and that then related fields for TCP Client get disabled while another critical field get enabled...

It needs to be set to TCP Server mode so that clients like HomeAssistant can connect to it using TCP; which the manual documents as the robust/reliable method of maintaining a connection with minimal risk of data packet loss (vs UDP).

After selecting the server mode then the Local Port Number field is visible and enabled but defaulted to 0 (zero)!

The manual states that a port Value of 0 (zero) means that it will use a random port number, so we need to set a specific port value here where I used 4328 (the reversed characters of 8324; the default port for TCP Client Mode):

So after assigning a specific port number in the Local Port Number with TCP Server working mode and then using the USR-TCP-Test software I was able to finally connect successfully, and validate the data streaming from the Hayward Pool Controller using my Windows PC as a TCP Client to test. The software runs on windows and allows testing of connectivity to help isolate any issues with either the device configuration or with with HomeAssistant configuration.

And of course then the HomeAssistant AquaLogic integration instructions made more sense as to what port it needed configured in the configuration.yaml so that HA can successfully connect as a client:

Once HomeAssistant is configured and running -- no errors in logs, etc. You can validate that a client has connected in the Web UI of the USR-TCP232-304 (see highlighted IP of connected client and data being transmitted):

Et Voila! My HA entities appeared and were finally reporting data. The sensors and switches both immediately started working for me...

Thanks for the excellent work @swilson, I def. owe you a beer / coffee for going the extra mile and adapting the shared knowledge of the Hayward protocols into a HomeAssistant integration!

And I hope these additional details will help the next person :slight_smile:

Now Geaux Code, CajunCoding!