Wiser 2 capability

Hi there all you smart people.

I am thinking about buying a Wiser Mk II to attach to my C-Bus. I want the app control and all that cool stuff. I am keen to hook up my Daikin air con too, but it is not RWG compatible and AirBase seems to have a Daikin app only.

Anyway, I was looking at the Coolmasternet AirCon bridge which will work with my Daikin. And I found this GitHub project where a guy has written code to execute commands to set cool/heat etc

My question is, can a Wiser 2 be programed to take a button press from the C-Bus thermo unit and then on that event send a piece of python code to the IP of the Coomasternet? the project is here https://github.com/koreth/pycoolmasternet for context.

If my question doens't make sense please let me know so i can explain myself better.

 

Wiser2 is obsolete, get a SHAC or NAC.

Wiser runs flash which is deprecated.

 

I added an Airbase to our 10yo HVAC last week.

Control is via the Daikin Airbase app, or Homekit via the diy homebridge-daikin-airbase.
Functionality depends on the HVAC system, we have the most basic on/off, heat/cool/fan, set temp.

The Airbase app has one on/off time setting per day, no distinction of the day of the week. The Homekit app allows a more complex schedule via Homekit automation rules that run on our Apple TV.

 

If it’s not obsolete then WHEN is it being migrated off flash to a web package that will be supported by browsers in 2021?

Clients are already getting warnings in chrome and the only answer we can give them is Clipsal is not giving any pro-active information and we can only presume that support will not be available for browsers.

Commercial clients DONT want app based access and how many commercial clients are running these units in HDMI which simply can’t be used remotely to the unit without creating a security and system integrity risk.

 

Circling back to an earlier post, homekit and homebridge-daikin-airbase has been working fine for me apart from one major issue.

When power is lost it takes a long time for the Airbase controller to appear on the LAN, not sure why, perhaps due to the fact it is not officially supported on my HVAC.
As a result Homekit drops the accessory and removes it from any automations, requiring manual intervention to recover automation rules.

This is not robust enough for real life use, so I have returned to controlling the Airbase schedule directly from Wiser via their HTTP API.
The Airbase control URL is longer than the Wiser GetHTTPData character limit, so I am using reverse proxy on the LAN to rewrite an abbreviated URL to the long form. A bit more to setup but a more robust result.

 

Have u jumped onto the GitHub for your plug-in and lodged is as a bug?

It’s unlikely that Homebridge is “dropping” the accessory, it’s more likely that there is a flaw in the plug-in.

If the accessory is in the config.json it isn’t going anywhere. It must be that the plug-in is choosing abandon polling for its devices.

Im not familiar with the Daikin unit so can’t assist more directly but reporting you bug will probably yield results if the plug-in hasn’t been abandoned by its author.

 

Good point, will do.

 

The homebridge-daikin-airbase author was very responsive and has implemented a change to maintain a persistent accessory profile, will be in the next release.

 

Excellent