DO NOT UPGRADE YOUR HALO TO FIRMWARE V2.4. It is no longer compatible.
Upon further investigation, it appears that the security measures in Halo firmware v2.4 have changed, effectively locking out the integration in its current state.
The mobile app now performs a challenge/response with their cloud server to authorize local Bluetooth connectivity. While implementing this is relatively simple, it would require contacting their cloud server for a challenge/response for every new session key acquired locally via Bluetooth.
Their stance on this HA integration is clear. Given the new requirement for an internet connection to establish local Bluetooth connectivity, I empathize with end users and pool technicians who have poor or no internet coverage and are now unable to connect locally via Bluetooth to the Halo device in front of them as a result of this change.
Until then, we can only hope for the promised public API like they have with the connect 10.
But for now, I’ve got no interest in playing cat and mouse.
It’s also ironic that this post number 404