Another one - is the heating state actually read from the unit itself? Or is it derived data, i.e. when it’s in heat mode and the measured temperature is below target it assumes it’s actively heating? Because when I look at the temperature it definitely looks like the latter, i.e. derived data?
You can only choose heat/cool/etc, there is noe level adjustment other then the fan speed control, witch is recommended set to auto. Then the unit itself will control when it is actually working (heating or cooling) based on its own thermostat and adjust the fan speed as its internal system sees fit. If you want to control it based on an external thermometer i suggest using an automation to adjust the target temperature of the Panasonic up and down. It will take som testing to find the right levels.
The mode setting do not change based on the temperature. If heat mode is seleced it is in heat mode until that is changed, but the actual heating only happens when the measured temperature inside is below the set temperature. The unit do report this, adding “Idle” in front of Heat when it is not heating at the moment:
I have not tried to use this status myself, but I should be possible.
When it comes to the hvac_action state it’s not supplied from the API/device, so it’s just a guesstimate derived from the mode and temperatures.
Thanks, that’s what I’d assumed from looking at the data. Is the ‘Idle’ state that @christbj mentions above an actual report of when the unit is heating, or is this also assumed from the reported set/actual temperatures? If the former, can it be extracted as actual state data?
Apologies for all the questions, I’m finding that these units don’t actually target temperature very well because the temperature sensor is internal to the unit and so gets heavily corrupted by their own heat output. Am just trying to get a precise read on what’s going on. Thanks for a fantastic integration, it’s really helping me figure out what’s going on, and should also enable me to wrap an actual Home Assistant thermostat around it to get much better control than the units internal logic provides.
This shows the values from the Panasonic and the temperature from a sensor (MH-Z19) on the other side of the room, about 50cm above the floor. The Panasonic itself it mounted about 2m above the floor. At 16:30 the target temperature was set up to 27C, and down to 23 at 18:10. As you can see, the temp on the other side of the room also climbed, but naturally slower than the temp measured at the Panasonic itself. What I like is that they follow each other, although with a delay and a difference due to different levels above the floor.
The Graph also show when the Panasonic is actually heating, a detail I had not noticed before, it may be useful.
I believe that orange heating indicator is the derived data, i.e. just when measured is below target, not when it’s actually necessarily outputting heat.
Because you’ve set a high 27 target it pretty much stays on over that period at least, but what I find is that if you set a lower target it takes forever to get there because as soon as it starts outputting heat the internal sensor measures this, turns it off as its over target and constantly cycles - these are the oscillations you see I think. Because of this, even if it’s well below room temperature for hours, it’s still just cycling on and off approximately every ten minutes. Setting an hour long boost time like you have might be one way around it, but if there was an external temperature sensor available that would solve the problem immediately I think. If not though, I’ll probably have to set up a thermostat in Home Assistant itself to use an external sensor (like your MH-Z19) to control the unit.
1 Like
Hi! Very cool integration, thanks for that!
Where would I find the list of Fan mode property states for the climate entity? When I try “FAN_AUTO” or “FAN_MEDIUM” for example, it won’t react.
But for example, if I try “24” for temperature property, it reacts well.
Trying to do an automation based on a third party temperature sensor in the room.
Thanks!
Dear Jimmy,
Today morning the Panasonic Comfort Cloud integration stopped. I reinstalled it, and I am not able to sign in. The user Id and the password is correct, I check it in the comfort cloud app directly. The error message is what I receive during the sign in: “Unexpected error creating device.”
Could you please help me what could be wrong?
Thank you very much.
Same here. Although Panasonic app is working. I’m getting error: “Unexpected error connecting to the API.” when trying to reconnect to Comfot Cloud from Home Assistant. I’m guessing some kind of change in the API is causing this
The integration was smooth till today for me as well. Today the integration failed to connect. I can connect via Comfort Cloud app.
It seems the API might have changed something in the login process (I would guess). I would appreciate any help here.
1 Like
Same here.
Since this morning it is no longer working.
I tried downgrading, but that also doesn’t work.
It looks like Panasonic has changed something.
Same here too.
I am very happy to have local control of my two Panasonic devices, thanks to this project: ESPHome Panasonic Climate WiFi interface - espthings.io
The 2024.11 update of the integration fixed the problem.
Has anyone written a comfiguration for homekitbridge that exposes these air conditioners to homekit users?