[APP][Pro] ClimateControl - Upgrade your HVAC experience

It would be great if the app could work for Panasonic air conditioners :folded_hands: :slight_smile: @tammert

Agreed, I’m just waiting on some information from ProtoART and then I can add Panasonic airconditioners too!

LG is available on the testing branch: ClimateControl | Homey

Thank you for developing the LG version.

While testing the LG test version, I noticed two issues related to the vane settings:

  • In Vane mode, the Auto option is missing.

  • In Wide Vane mode, an Auto option is available, but it does not function correctly. When Auto is enabled in Wide Vane mode, it is not applied or passed through to ClimateControl.

Additionally, would it be possible to also add the three options highlighted in the image below:

  • Auto Dry

  • Purifier

  • Energy Saving

I hope this feedback helps improve the LG integration. Thanks in advance!

@tammert any news from ProtoArt regrading implementation of panasonic?

@tammert

I recently had to temporarily cut the power to our house. After powering everything back on, 2 out of the 5 units no longer update their inside temperature.

In Home Assistant, the temperatures are updated correctly, so it seems to be related to the Homey implementation. I also don’t see any repair functionality to freshly retrieve all values from the units.

Is this something you could look into?

I have been investigating the issue a bit more and apparently I didn’t assign static IPs to the control units and for the two of them that are in error at the moment, the IP had changed. An easy solution would be that in the settings of a unit, you can edit the IP address? :slight_smile:

Not yet, I first need to finish LG stuff too but I’ve been pressed for time…

So I’ve programmed an ā€œauto-repairā€ functionality based on the mDNS values retrieved from the CC modules. These should normally ensure that even if an IP changes, the device is updated with the new IP (based on the static ā€œidā€ found in the mDNS record): see net.protoart.clima/lib/baseDevice.ts at main Ā· tammert/net.protoart.clima Ā· GitHub. Homey doesn’t prefer/allow IP-via-settings outside of the discovery mechanism, so while your suggestion makes sense from your perspective, the answer is ā€œthat’s not how it worksā€ :slight_smile:

Are the devices ā€œbrokenā€, or is it just a few values? Otherwise, try if you can find them as new devices (and delete the old ones).

They were broken. I just removed them and added them as new devices. :slight_smile:

Hi, thanks again for working on the LG version.

I’m still testing it and was wondering if there are plans to make the LG version a final release, and if my previously mentioned points could possibly be included.

Thank you for the reminder and the patience! I’ve pushed v0.9.0 to testing now, which addresses pretty much everything you asked for: except for the ā€œvane mode: autoā€, because it’s not available in the ClimateControl :frowning:

I’ve also added the Silent Mode toggle for MHI.

HOWEVER: I own MEs which do not support any toggles, so I have no way to verify whether the toggles actually work and/or are even shown. But hey, the code compiles, right?!

Please let me know if you see the toggles, and preferably if they work :sweat_smile:

Hi, thanks for the update!

After the update was installed automatically, ClimateControl went offline in Homey. I tried adding the device again as a new device in Homey, but it can no longer be found.

Could you check what might be causing this, or possibly make the previous version available again? Thanks!

Restarting the Homey app, Homey itself, and the ClimateControl didn’t solve the issue

Can you send me a diagnostics report via the Honey ClimateControl App settings? Hopefully I’ll be able to see whats going on then

a5d10c0b-337c-4cd3-90fb-b6ea29e46550

diagnostics report code

Thanks, I see the error! If you’re in a rush, you can remove the broken device and then re-add it to fix, but if you can wait I’ll try to fix it this morning. The issue is the removed wide_vane, it’s crashing the device on init

Thanks! I honestly can’t do without your app anymore, even though it’s still in the testing phase. It’s more reliable than the other two Homey apps that run via the ThinQ platform.

I’d rather wait for the fix. I already have quite a few flows connected to it, and I’d have to rebuild everything if I removed and re-added the device.

v0.9.1 is live on testing! I swapped the capability removal/adding logic around, I hope it fixes the issue. If it does, let me know. Otherwise, just send me another Diagnostics Report and I’ll take an additional look :slight_smile:

The CC is back online after the update, fortunately. I’ll test the new features in the Homey app over the next few days. :+1: