Hi @D-Autom8tion,
I think the BLU gateway doesn’t support active connections (which are required for this integration). So while the shelly gateway would probably allow HA to discover your chlorinator, it wouldn’t be able to connect to it.
There are some off-the-shelf esphome compatible modules that would be reasonably low fuss. Ready-Made Projects — ESPHome, for more info.
You have to manually add the github repo manually first
https://github.com/DanielNagy/astralpool_halo_chlorinator
But if you have a later Halo firmware after 2.3. Don’t bother. Theyve locked it out.
Yeah… I have 2.5… sigh…
For the first time, I’m glad I’ve got the ‘dumber’ Astral Viron EQ35 as it is still working fine with HA and this integration!
Hope you guys manage to work out a viable way to get the Halo working again!
Im about to sell my entire Astral stack over this issue and three colleagues too.
If anyone can identify a verified home assistant compatible integrated clorinator, doser, pump control and sensor group (or, etc.) Let me know please and we will start making the switch. Theres no point waiting for something that may never happen. Astral / Fluidra support is also really disappointing when it comes to the technology side of thier products. Wont ever go back.
Hi all, thanks for the great work on this over the last year or so. I have managed to get this working however, I am interested in knowing how I can turn on both heat and cleaning pump which are in the ‘other’ tab on the go app.
I only need to be able to turn on/off/auto, same as the chlorinator, but when i got this running couldn’t see them in the list of entities?
Totally agree with you on this … they have crap solutions really and their “apps” are incredibly basic.
can confirm tried today and i do have pump control but no sensors on HA.
I’ve managed to stay on 2.3 and have this HA integration working well - but yes, am concerned one day they’ll force me to update… Or there’ll be some features i need 
To require a cloud connection for a local BLE connection is stupid. But we’ll never know the reasons why they did it.
They’ve promised a public API(no date when), but I’m sure it will lack a lot of sensors the integration currently has.
As for alternatives @Mark.sydney, I believe the Hayward Aquarite Plus has options to make it internet connected. I discovered a HA integration for that some time back, cant really comment any further as I don’t own one.
To be honest, based on what I’ve seen from the available residential pool equipment available, there doesn’t seem to be any that I would class as real winners here. Their view on whats “smart” falls very short of ideal, and realistically it’s a case of “Here, we have a mobile app”. I mean, most smart home products fall into that category trying to tie you in to their own ecosystem. You need a separate app for each separate vendor (and sometimes product!)
I’ve personally started looking into the commercial pool offerings to see whats available. or Heck, maybe even go down the path of making my own pool system.
Unfortunately not as far as I can see. Forced upgrade to the broken version
Hi Daniel, thanks very much for your work on this. I realise you weren’t previously interested in updating the integration to work with the new bluetooth approach past V2.3. Is there any chance that you would reconsider? Yes it’s dumb that cloud polling is now required but for those of us that have no other way to integrate the Halo into HA, this is the difference between having integration or not at all 
Thanks for your words. Unfortunately as i mentioned before. I’m not going to implement the cloud auth. Not interested in playing the Cat and Mouse game. They blocked local BLE (stupid move in my opinion), they can easily block cloud auth as well as.
You only need to Look at what happened in the cloud garage door control, and the birth of RATGDO.
They have promised a public API, like they do for the Connect10… So Once that happens, i’ll update the Integatrion for that. Hopefully its sometime in the next 6 months.
I also would love to see this one day, fyi your solution works great on my v18.
I appreciate you do this only in your spare time so thank you for the development so far!!
Hi Daniel, I see that there is a new v2.6 firmware out. Has this made any difference in they was your integration can authenticate with the Halo.
Just tested - doesn’t look like it. The blind faith route isn’t going anywhere, perhaps we should contact Fluidra / Astral and just politely ask if they’re even working on this.
Hi Paul, thanks for the integration. Any further thoughts on implementing a control for the chlorine setting? Being able to adjust this seasonally, or turn it off when running the pump for other tasks (e.g. running a water feature all day) would be very useful for HA automations. I think the Viron / Viron EQ Chlorine setting values are always integer 0 - 8. Cheers
Hi @OBrother,
Glad you are getting some use out of the integration!
Yeah, it should be possible to set the ORP setpoint somehow (since you can do it from the app). I can see that there’s data coming out about the min and max ORP setpoints. While it isn’t likely to be hard, it probably isn’t trivial. Trivial is about all I’ve got time for at the moment unfortunately!
Anyone else out there with a splash of coding skills who wants to have a crack at this?
