cr3ative / homebridge-aqualisa Goto Github PK

I think MQTT is the key to this. I set up my own broker, fudged DNS so my shower thought it was aqualisa and I got a lot of traffic (> 1 message per second) from the shower. At this point nothing is flowing from my network to the cloud servers. I then tried and failed to turn the shower on with the app. What I think happens is the app makes a REST call to a cloud server, which then sends the instruction to turn on/off etc via the MQTT broker. This makes sense (to me) as it doesn't need to make an incoming call into the shower, the shower is just subscribed to some command topic and does what it is told to do.

My next plan is to figure out an MQTT SSL proxy so I can see whatever is sent back over MQTT from the cloud.

Oh my days. This Aqualisa shower was touted as being smart and it's as thick as s***. The app is next to hopeless and profiles have been removed from the controller. Sigh.

What do I want? I want to know when the shower is on or off, or the bath is on or off (the secondary valve) as then I can kick off magical events. I'd love to help test this with you and using HomeBridge and therefore into Home Assistant to make it actually useful.

THANKYOU!

I'm currently looking to add WiFi to a Aqualisa Quartz that I have laying around.
The unit is a Quartz (Divert?) unit, that uses the Black “Digital processor”
So far I have worked out the following schematics for the Main controller on the shower

A remote control to trigger Start/Stop (There is an error, R5 is 1K)

There are a couple of bits I'm looking for circuity for, the Divert function, How does the hand unit send the signal to be picked up by the "Divert Processor" and the other is Flow control, only on higher end hand units, such as hiqu, ilux,or infinia.

It would be nice to get the protocol figured out, so that we can make a better controller for home automation. I know its possible as this place makes a 3rd party controller