ESPHome Panasonic Climate WiFi interface
Table of Contents
Getting the Panasonic Climate control off the cloud
A little while back I came across a custom esphome component for a esp32 or esp8266 based airconditioning/Climate Wifi interface. A great way to get your Panasonic Climate control off the Panasonic Comfort Cloud and into Home Assistant locally. The horrible Panasonic app and ever failing cloud service had been bothering me for a while now.
How does it work?
Panasonic Climate units are usually connected to Panasonics Comfort Cloud using either a DSNK-P11 or a CZ-TACG1 WiFi interface.
 CZ-TACG1 |
 DNSK-P11 |
If you have one of these interfaces installed, you are unfortunate enough to be using the Panasonic Cloud service which sucks! Repeatedly having to log-in to your app and not not being able to control your Climate unit due to Cloud service outages are common issues. If you do not have one of these interfaces installed, you are likely not able to control your Climate units by anything else then the standard remote control that comes with the unit.
The Solution:
There is a solution to both problems. By using a custom esphome module it is possible to connect your Panasonic Climate Unit to Home Assistant locally. Remote controlling your Climate unit will be instant and no longer cloud dependant. The only thing missing was a drop-in hardware replacement for the original Panasonic DNSK-P11 Wifi-interface so Paul and I started measuring and fiddling around until we came up with this design:
Paul really did a great job on this PCB!
Panasonic Climate Interface with optional CN-CNT cable (no p11 header)
Espthings Panasonic Climate Interface with DNSK-p11 header
Usually we design PCBs with through-hole technology, but since that would not fit within the small footprint of the original PCB’s we had to design this one with SMD components. We will NOT publish the PCB source files as these files tend to end-up in the hands of people who commercially exploit them.
Features:
- 100% drop in replacement for the original DNSK-P11 PCB and a perfect fit for the original enclosure!
- ESP32, so you can also use BLE for location tracking of your phones etc.
- Status LED
- Fits the original Panasonic connector, no soldering, wire cutting or splicing required!
- Option to connect to a CN-CNT connector using a custom cable.
- Micro-USB terminal for installing the firmware (USB chip for auto-programming)
- Pre-programmed with a default esphome configuration with Hotspot, captive portal and web server enabled, so you can upload your own config OTA!
- Option to print or order a great tiny 3D-printable enclosure that exposes the P11 port, CN-CNT wires and USB-port.
- Fully tested
You want one?
Sometimes we produce a small batch of these modules to help out other Panasonic Cloud ‘victims’.
UPDATE 29th September 2022: Sorry, we do NOT have any more modules available and for now we have no plans to run another batch.
We do however have 2 pcs of the older batch left, which are only usable as DNSK-P11 replacement. Price: EURO 19,00 excl. PP.
Panasonic DNSK-P11 replacement:
Option 1. The price will be EURO 25,00 for the version that replaces the original Panasonic DNSK-P11 wifi adapter. It has the custom header for the original Panasonic DNSK-P11 cable installed (soldered).
Panasonic CN-CNT version:
There are a few options if you need it to replace the original CZ-TACG1 or if you have no Panasonic Wifi module installed at all. Please first check if your Panasonic Climate control has the CN-CNT connector!
Option 5. Buy the module with the custom CN-CNT cable attached (soldered) and no DNSK-P11 header, so specifically for the CN-CNT connector. The price is then EURO 28,00 This option makes sense if you are replacing a CZ-TACG1 or if you have no Panasonic Wifi module installed and you are not comfortable soldering the wires yourself.
Enclosure:
The .stl is available [ here ] so you can print it yourself as well!
Shipping:
How to buy or reserve one:
If you would like to buy or reserve one or more espthings Wifi interfaces, please use the contact form and state:
- Amount/option(s).
- Full name
- Full postal address
- If located outside of the Netherlands, your (mobile) phone number as we are required to to enter that for shipping
- The exact preferred shipping method (check above!)
Please save your technical questions for the comments section of this post. Do not use the contact form for that please!
Instructions:
Hardware:
DNSK-P11 replacement:
Original DNSK-P11 enclosure
Our module inside 😉
Below a video on how to install the original CZ-TACG1 interface. The interface is different, but you’ll find clear instructions on how to open and close the unit. After taking off the enclosure, check your Climate unit for the DNSK-P11 enclosure.
Please subscribe to our YouTube channel and hit the bell to never miss a (esp)thing!
Take the DNSK-P11 pcb out of the enclosure carefully, remove the black connector from the PCB and install your espthings P11 interface. Connect the interface using the original DNSK-P11 cable. The connector-lip needs to go downwords in the notch of the PCB, the flat part of the connector up.
Please be careful as the pins are tiny. If you use your brain in stead of brute force, you’ll be ok. 🙂
CZ-TACG1 replacement:
You can eiher replace the original CZ-TACG1interface, or if you have no Wifi interface installed yet and your Panasonic unit has the 5-pin CN-CNT connector, you are good to install the espthings.io Wifi interface.
CN-CNT connector
Below a video on how to install the original CZ-TACG1 interface. The installation of the espthings interface with the cable (option 5), is pretty straight forward.
Please subscribe to our YouTube channel and hit the bell to never miss a (esp)thing!
Software
Each interface has been tested and is pre-flashed with esphome firmware, with the Hotspot, Captive Portal and webserver enabled, so you can install your own esphome configuration (or any other compatible firmware) using OTA (WiFi).
Just connect to the Panasonic Climate Hotspot WiFi network, use password qwe12345 and access the web-interface by entering the IP -address or hostname of the interface in your webbrowser.
In esphome, create your own new configuration, press install, select “manual download”, download and save the file and upload that file in the web-interface of the interface (refer to the screenshot above). Power cycle the interface and it will then appear as “online” in the esphome dashboard.
>> Only needed for the old version: If you need to flash using USB for some reason, do not forget to close the jumper when booting the ESP32.
Config:
Please mind that we supply all modules with a basic test configuration which is the same for every single module. If you use more then one module in the same network, you need to reconfigure your modules with a unique (host)name! (substitutions: devicename: XXXX) and unique entity names (substitutions: long_devicename: Climate living)
More on the basic usage of esphome in this video:
https://youtu.be/yMhC6Or0oTY?t=170
ESPHome secrets:
esphome_wifi_ssid: 'yourssid' esphome_wifi_password: 'yourpass' esphome_ap_password: 'yourpass' esphome_api_password: 'yourpass' esphome_ota_password: 'yourpass'
ESPHome config:
substitutions:
devicename: "pana-climate"
long_devicename: "ESPthings Panasonic Climate Interface"
pcb_version: "220722-1"
esphome:
name: "${devicename}"
name_add_mac_suffix: false ## if 'false' use different names/hostnames for each device!
comment: "${long_devicename} ${pcb_version}"
platform: ESP32
board: mhetesp32minikit
project:
name: "esphome.pana-climate"
version: "${pcb_version}"
external_components:
source: github://DomiStyle/esphome-panasonic-ac
components: [panasonic_ac]
wifi:
ssid: !secret esphome_wifi_ssid
password: !secret esphome_wifi_password
ap:
ssid: "${devicename} Hotspot"
password: qwe12345
captive_portal:
web_server:
port: 80
logger:
level: DEBUG
api:
# uncomment the line below if you wish to use an api-password
#password: !secret esphome_api_password
ota:
# uncomment the line below if you wish to use an ota-password
#password: !secret esphome_ota_password
uart:
tx_pin: GPIO17
rx_pin: GPIO16
id: ac_uart
baud_rate: 9600
parity: EVEN
# revisions below 220722-01 use GPIO12
status_led:
pin: GPIO13
# For revisions from 220722-01 and higer the optional temperature sensor is available.
# DS18B20 1-wire Temperature Sensor
#dallas:
# - pin: GPIO18
#sensor:
# - platform: dallas
# # Check the dallas sensor address in the log file
# # For more info: https://esphome.io/components/sensor/dallas.html
# address: 0x540000001524be28
# name: "$long_devicename Temperature"
# id: temp
switch:
- platform: restart
name: "$long_devicename Restart"
climate:
- platform: panasonic_ac
type: cnt # For CZ-TACG1 use type: cnt / For DNSK-P11 use type: wlan
name: "${long_devicename}"
vertical_swing_select:
name: "${long_devicename} Vertical Swing Mode"
outside_temperature:
name: "${long_devicename} Outside Temperature"
# If the ac does not report a current temperature (CZ-TACG1 only) uncomment
# the line below and point to the appropriate sensor
#current_temperature_sensor: temp
Home Assistant Lovelace yaml example:
type: vertical-stack cards: - type: thermostat entity: climate.panasonic_climate_xx - type: entities entities: - entity: select.panasonic_climate_xx_vertical_swing_mode - entity: sensor.panasonic_climate_xx_outside_temperature
End result 🙂
Hallo AceIndy,
We hebben er inderdaad nog maar 2. Als je even contact opneemt via het contactformulier, kunnen we de eventuele mogelijkheden bekijken.
No, It can’t, sorry.
I believe it will also work for CZ-TACG1. Dominik’s repo also supports it, the correct wiring to the AC connector needs to to arranged of course. Michel what’s the status on stock and new batches? 🙂
Not in yet. Shipping is slow.
I need this in my life!
Will you be making more of these in the future?
Yes, the second batch is just in. We will be making more, but only after a certain amount of reservations are in so waiting times could be up to 2-3 months.
Hi,
is it possible to send:receive commands via MQTT?
https://esphome.io/components/mqtt.html?highlight=mqtt
Werkt deze ook voor saunier duval/bulex ? deze hebben gelijkaardige wifi interface
I wouldn’t know as I am not familiar with that brand of climate control, sorry.
Sorry if this is a stupid question, but what if your Panasonic AC unit has both the DNSK-P11 Wifi Module installed AND the CN-CNT connector on the PCB ? I see this in the HZ35XKE and the NZ35VKE units I’m currently looking at. Heck they also have the CN-WLAN connector … I think I’d be looking for Option 5 (or possible Option 3 even if it doesn’t make so much sense :D). Is there a space BOTH for the DNSK-P11 and your ESPHome module inside of the above mentioned AC units ? Thanks :).
That works. If you have the original DNSK-P11 and the espthings interface, you can use them both. 🙂
We are not familiar with every single Panasonic AC unit, but I have not seen any unit so far, that did not have some space to put our 3D-printable enclosure.
Thank you for your reply, Michel. Therefore, in this case, what option would you reccomend 🙂 ?
I would choose option 5 and either buy or print the enclosure.
Perfect, thanks. Yes, I was of course looking to buy the enclosure as well :). Hope that helps support your project 😉
Thank you. Much appreciated!
I have a Panasonic TZ series: https://www.logicool-ac.com/wp-content/uploads/2020/03/CS-TZ-WKEW-Service-Manual.pdf
The Wifi is built in, and it has the reference ACXA73-28520 and connected to CN-WLAN.
I do see in the PDF it has a CN-CNT port. However I have no clue if this is compatible, and if I should remove the existing wifi module?
That looks like the DNSK-p11 module. If you also have the CN-CNT you have the option to connect it both ways (depending on the espthings module option you choose) and you may also leave the original module in and connect a espthings module at the same time.
This information is all at your own discretion, because I do not have any option to test it on your specific model.
Found input from a Z series, similar idea: https://github.com/DomiStyle/esphome-panasonic-ac/issues/32
So indeed seems to work both ways. I guess for a drop-in replacement/addon option 5 is the easiest, correct? Just plug it in and run ESPHome to install.
Forgot to check the readme: https://github.com/DomiStyle/esphome-panasonic-ac
So indeed, I’m confident it will work. If you can confirm that option 5 is the easiest I will follow up on email for an order 🙂 Thanks!
They are both easy 😉
I have 6 Panasonic Fancoil PAW-FC2A-K009IR. I removed the cover to inspect the connectors, and only found two 4 pin connectors which are referred to as CN-Module and also 5 pins without connector in the middle just referred to as CN14. any idea if this would work with it?
https://share.icloud.com/photos/0a5VxSaUdPrkd2FOtccFqczpA
https://share.icloud.com/photos/0fd28Vyq8aYYQH8Djh6TqzryQ
That doesn’t look like anything I have seen before.
One thing I see the module is 5V and this shows 12V on the module connector.
Like I said, it does not look like anything I have seen before. You could try asking here: https://github.com/DomiStyle/esphome-panasonic-ac/issues
Hi Michel,
just recieved my modules and heve one installed but it does not generate the correct hotspot (pana-climate Hotspot in stead of esp32-airc-xx) and teh above mentioned password does not work.
did you change the default config? and if so what is the new password?
on this page should be correct:
ssid: "${devicename} Hotspot" <== devicename = pana-climatepassword: qwe12345tnx that worked indeed.
now i need to deal with home assistant giving me head ache, it will only detect entities from the most recently added device… 🙁 so they work when added but once i add a 2nd and 3rd the first ones stop working.
ow well, somethign for tomorrow to figure out.
Hi, please check our post carefully as you need to give all devices a unique name. We send them all with a base config so you can OTA upload your own configuration file.
So:
substitutions:devicename: "pana-climate-01"
substitutions:devicename: "pana-climate-02"
What you can do best now is:
1. Delete all devices from Home Assistant and restart.
2. Create all devices in esphome, with their own respective unique name: (or substitution) in the config
3. do a manual install in esphome and download the .bin files for all devices
4. Connect to the IP-address of each device and upload the corresponding config.
5. Add your newly discovered devices to home assistant.
etc..
If you are not that savvy with esphome, check our previous video for basic instructions: https://youtu.be/yMhC6Or0oTY?t=172
It installed well for two devices. The wifi name and password mentioned in the text are incorrect, you can get them from the .yaml file as mentioned in the comment above.
Plugging in (version 5) was very very easy. I now have them running in HA.
– First add them using USB and install your variant of the software.
I now only need to figure out the swing modes, they are not in line with my panasonic module, but that is software I guess.
Hi, you are absolutely right. I did not see the old password in the post. The yaml is indeed correct. I have corrected the post.
For swing mode you need to use a separate entity. My lovelace yaml:
type: vertical-stackcards:
- type: thermostat
entity: climate.panasonic_climate_xx
- type: entities
entities:
- entity: select.panasonic_climate_xx_vertical_swing_mode
- entity: sensor.panasonic_climate_xx_outside_temperature
The post just to confirm the quality of the product and how it works.
Installed about 1 week ago and so far I have used 2 modules without any problems, very easy installation and setup.
Any command is received practically instantly and without any problems.
Great job!
Thanks Stefano, always nice to hear!
It’s all true, wonderfull project. Only mode it seems not to work in my setting is ‘fun-only’. In your?
That fully depends on your panasonic model. If it does not support fan-only on your remote, it won’t in esphome.
ok thanks. In my remote there’re another’s setting, like speed-fun, is it possible to add in esphome?
If not available in software yet, you need to apply for a feature request here: https://github.com/DomiStyle/esphome-panasonic-ac/issues
Hello! Is there easy conversion to wifi -> Modbus TCIP? Is the interface of panasonic regular RS232?
I am building my bms/scada system where i can use opc, modbus rtu/tcip or using convert 232 to 485.
The interface uses serial signalling at 5V (TTL Level). The software is an esphome application. So if you can write a custom component which includes the translation from modbus to the command set of the ac unit, and get that to work in esphome, or any other environment which supports the ESP32 controller, you can do it.
We will not support that application. We will just support the hardware side….
Hi Michel,
Thanks again for the quick service!
As you mentioned it works like a charm..
one tiny thing. When i’m viewing the logs in esphome it throws a warning.
[W][panasonic_ac.cz_tacg1:462]: Received unknown mild dry value
I’m not quit sure.
Could it be you have this config option enabled?
# mild_dry_switch:
# name: Mild Dry
Only enable options your unit actually supports.
Or maybe your unit supports it and you have it disabled 😉
You are right. it is the latter one.
enabled the option in the yaml and toggled it on/off in the ui.
Hi,
maybe I’m missing something here:
I have six Panasonic air conditioners with the DNSK-P11 WiFi module.
I already have the ESPthings modules and am exchanging them for the original ones.
I think I followed the instructions here exactly and assigned unique names to the individual modules in their ESPHome Config.
Unfortunately, I always see the same name for the entities in HomeAssistant:
ESPthing’s Panasonic Climate Interface
Shouldn’t they be different, as defined in the ESPHome Config?
The first device works perfectly, from the second there is of course a name conflict.
Unfortunately I can’t get any further, please give me a hint…
Many Thanks
Regards
Herbi
Two different Configs for example:
“kueche” works, “Wozi” not.
Please post your entire config of both modules
Use something like https://pastebin.com if you are not comfortable with using code tags.
The second, working config (the first installed):
(I will learn about the usage of pastebin… 😉
In order to help, I really need the full config, I can’t see what names you used for the Home Assistant entities like this.
1st and working Config:
substitutions:
devicename: “esp32-ac-kueche”
long_devicename: “AC Küche”
esphome:
name: “${devicename}”
name_add_mac_suffix: false ## use different names/hostnames for each device!
comment: ${long_devicename}
platform: ESP32
board: mhetesp32minikit
project:
name: esphome.pana-climate
version: “220528-1”
external_components:
source: github://DomiStyle/esphome-panasonic-ac
components: [panasonic_ac]
wifi:
ssid: !secret esphome_wifi_ssid
password: !secret esphome_wifi_password
ap:
ssid: “${devicename} Fallback Hotspot”
password: qwe12345
captive_portal:
web_server:
port: 80
logger:
level: DEBUG
api:
ota:
uart:
tx_pin: GPIO17
rx_pin: GPIO16
id: ac_uart
baud_rate: 9600
parity: EVEN
status_led:
pin: GPIO12
climate:
– platform: panasonic_ac
type: wlan # For CZ-TACG1 use type: cnt / For DNSK-P11 use type: wlan
name: “${long_devicename}”
vertical_swing_select:
name: “${long_devicename} Vertical Swing Mode”
horizontal_swing_select:
name: “${long_devicename} Horizontal Swing Mode”
nanoex_switch:
name: “${long_devicename} NanoeX Switch”
outside_temperature:
name: “${long_devicename} Outside Temperature”
2nd Config, not working:
substitutions:
devicename: “ac-wozi”
long_devicename: “AC Wohnzimmer”
esphome:
name: “${devicename}”
name_add_mac_suffix: false ## use different names/hostnames for each device!
comment: ${long_devicename}
platform: ESP32
board: mhetesp32minikit
project:
name: esphome.pana-climate
version: “220528-1”
external_components:
source: github://DomiStyle/esphome-panasonic-ac
components: [panasonic_ac]
wifi:
ssid: !secret esphome_wifi_ssid
password: !secret esphome_wifi_password
ap:
ssid: “${devicename} Fallback Hotspot”
password: qwe12345
captive_portal:
web_server:
port: 80
logger:
level: DEBUG
api:
ota:
uart:
tx_pin: GPIO17
rx_pin: GPIO16
id: ac_uart
baud_rate: 9600
parity: EVEN
status_led:
pin: GPIO12
climate:
– platform: panasonic_ac
type: wlan # For CZ-TACG1 use type: cnt / For DNSK-P11 use type: wlan
name: “${long_devicename}”
vertical_swing_select:
name: “${long_devicename} Vertical Swing Mode”
horizontal_swing_select:
name: “${long_devicename} Horizontal Swing Mode”
nanoex_switch:
name: “${long_devicename} NanoeX Switch”
outside_temperature:
name: “${long_devicename} Outside Temperature”
Did you actually install (program) these configs? What does the log in esphome say, from bootup on?
Pro-tip: Use the ‘code‘ button in the editor of this message-editor and paste your code between the tags. Makes it more readable.
I do not see any errors in your config. You might have tried the module before and your issues might now be within Home Assistant and not within esphome. Try removing both devices from HA, restart HA and then add them again, one by one.
If that does not work you need to tell us more about the exact issues, because it’s unclear what you are exactly experiencing.
I knew it must have been something ‘stupid’ like that as your configs where correct, but your hostname was not corresponding to that config. Great it works now. Enjoy!
I have a Panasonic CZ-TACG1. On the CN-CNT connector it has wires on pints 2, 3, 4, and 5. In the photo of your device (above) you have wires on pins 1, 3, 4, 5. What is the difference? Is this because the CZ-TACG1 uses a 12v power source and your device uses 5v?
I highly doubt yours is in fact a regular CZ-TACG1 interface as those have 5 wires, also providing 5v which our interface needs. https://github.com/DomiStyle/esphome-panasonic-ac/blob/master/README.CZTACG1.md
I’m not sure what you mean. Are you saying that my CZ-TACG1 doesn’t have a regular CZ-TACG1 interface? I’ve attached a photo showing red (power?) next to the black instead of at the opposite end.
I suspect the aircon provides both 5v and 12v, and my CZ-TACG1 uses the 12v, but your device can use the 5v. When I finish work today, I will test the voltage on the aircon to confirm that both voltage levels are present.
I think I misread. If your aircon has a regular CN-CNT interface, you should be good. There will be both 5v and 12v, of which we use the 5v.
Right, that makes sense. And yes, I was able to confirm that both 5v and 12v are present on my aircon, and that only the 12v line is wired on the CZ-TACG1’s cable/plug (red wire, pin 4).
So as long as I connect the ESP32 wifi interface module’s red wire to pin 1 instead of pin 4, everything else stays the same, and it’ll all work.
Thanks for setting my mind at ease!
Hi Michel,
I just received my first module, i flashed it with my firmware and it works perfectly.
Now i can control my ac with the original and with your module.I control the ac with GET and POST commands perfectly. You made my day, thank you !!. Now i have to figure out UDP.
Hi Filip,
Great to hear that your somewhat different approach works as desired!
Have fun with your cloudless solution 😉
Do you know if this is compatible with the CZ-CAPWFC1 I believe from this https://github.com/DomiStyle/esphome-panasonic-ac/issues/26 that it is a DNSK-P11 inside this module.
I would love to get a local version of this working.
I’m afraid there is no progress on that yet: https://github.com/DomiStyle/esphome-panasonic-ac/issues/63
Hi,
It says; Possibility to connect a DS18B20 . Can you register the room temperature with this and switch the device on/off in accordance with the temperature measured in the DS18B20 ? (So heat pump flaps closed?)
EDIT: Michel: I translated your question this time so other people will be able to read it as well. Please use English on an English website 😉
Well, yes that would be possible. You could use the automations within ESPHome, or just automate that from Home Assistant as you can expose this sensor to Home Assistant.
Hello,
ok i will order one. So i only have to order DS18B20 and option 4?
thx
Hi Nicolas,
Please read the instructions for ordering. You will have to get the DS18B20 elsewhere. We are not selling those.
Hi. I received my device last Friday, printed a case, uploaded new firmware, connected it to my wifi, powered off my aircon, and plugged the device in to the header for the CZ-TACG1 interface. Once power was restored to the aircon, the device appeared on my wifi, showed up in Home Assistant, and all seemed to be working perfectly.
Overall, I’m really quite pleased, so thankyou very much for your work on this. However, I have a couple of issues I’m hoping someone can advise me on.
Firstly, the current temperature (as displayed on the web interface) seems to fluctuate from about 21C to 29C and back again, around once per 10 minutes.
I note that the ESPhome yaml you provided has an entry for current_temperature_sensor commented out:
with a note to uncomment if the current temperature doesn’t show up. The current temperature IS showing up, so I don’t think I should uncomment. It’s just that the temp is wrong, and not even stable. Is there something wrong with my device or my aircon that the temperature if fluctuating like that? Or a change to the code I can implement to fix this? Debugging options to help diagnose?
The second issue is that there is no entity for current temperature. On the official CZ-TACG1 device connected to Home Assistant using the Comfort Cloud integration, the current temperature shows as an entity. I’m not sure if your board is providing feature-parity with the Panasonic alternative, and there’s something wrong, or if I have to setup a sensor myself, to get its value from the current_temperature attribute.
I’d be grateful for any help you can offer.
The temperature is read directly from the AC, so any incorrect measurements should come directly from the AC. We have noticed the current temperature measurement from the AC can be pretty bad when the AC is running.
This temperature is no separate entity, it’s displayed within the climate component (currently: XX)
The current_temperature_sensor: parameter can be used for an external temperature sensor, for example a sensor which is already available in Home Assistant, like a zigbee aqara temperature sensor, or something like that.
When configured, this sensor will overrule the internal sensor.
sensor:- platform: homeassistant
id: current_temperature
entity_id: sensor.temperature_living #home assistant entity here
attribute: current_temperature
then
current_temperature_sensor: current_temperatureMore on that here: https://github.com/DomiStyle/esphome-panasonic-ac
Thanks for your answer Michel. I think the problem is fixed, so just for closure, and to help anyone else with the same symptoms:
Last night, the ESPthings module stopped responding on the network. The aircon continued to work, but I couldn’t ping the module’s static IP. This morning, rather than disassemble the aircon to reset the module, I just turned the aircon off and on at the mains switch.
Since power cycling, everything is working again. And as a bonus, the “current temperature” had settled down and is now oscillating by a 1C margin around the set temperature. So the problem I had is now fixed!
The attached image shows a graph of the temp being reported by the aircon, with the wild fluctuations before the outage, then settling to normal afterwards.
I’m still a bit concerned that the ESP module stopped responding. This could just be my wifi network (I have a lot of devices and I might be pushing the limit of my mesh wifi system).
I would not worry too much about the module being at fault. We test every single one of them before shipping and this would be the first 😉
Just dropping a message to say that this seems to work wonderfull. Setting up 2 modules was little tricky, I had to add manual ip to the yaml files in order to get things working properly.
Thanks for letting us know!
You should not have to configure IP’s manually. You need to use unique devicenames as outlined in our example config.
Hi Michel, I recently received my unit and once installed, works nicely. (CZ-TACG1)
I just wanted to ask about the entities available in HA for automation purposes. According to the Domi package, “The climate entity and all sensors and switches are now automatically exposed to Home Assistant” in the latest version.
If someone could give me some help about, would be appreciated. It’s my first experience with HA and all this science and still know a very little ..
Thank you very much for your work!
Hi Alfons. All entities that are exposed are to be found in HA either via HA menu -> Developer tools -> states (then use the search option) or:
HA menu -> settings -> Devices & Services -> ESPHome -> devicename -> click “1 device”
At https://www.home-assistant.io/docs/automation/ you will find all information about making automations.
All right….I’ve been searching but the fact is that I cannot find any entities published for the device. Probably I must be doing something wrong…. Thanks in advance
In that case remove the device(s) from HA, restart HA and then add it manually again as esphome device. After that check again.
Hi
On My heating pump I Can set 3 temperatures hot water, floor heating and general heating.
Is this supported?
I don’t think so.
Hello Michel,
I’m trying to update the interface via OTA but it’s failed. The error message is: Update failed. Wrong magic byte.
Any idea what I’m doing wrong.
I build the fw with homeassistant and your config from above. Just changed the name and long device_name
Thx
Alexander
Clean the build files, then do a manual install and choose ‘modern’ format.
Still the same failure
Then I suggest flashing it via USB. It’s impossible for me to see where it goes wrong in your setup without providing detailed information.
I have flashed another module with the same binary and I can update it OTA without issues.
Ok, I was able to flash with ESPHome CLI. It works well. Great job!
Is there a posibility to deactivate the led?
Turn it into a binary light.
Hallo Michel, Ik heb de eerste module in werking. Mooi product!
Ik heb een aangepaste Esphome firmware erop gezet met mqtt ingeschakeld en de api uitgeschakeld. Ik krijg nu keurig de waarden van de AC unit in mqtt.
Wat ik alleen niet door hem / kan vinden is hoe commando’s naar de ac unit te sturen. Moet ik daarvoor zelf on_message topics configureren? Zo ja, zou je daarvan een voorbeeldje kunnen geven van instellen fansnelheid of zoiets? Of mij anders in de goede richting wijzen?
Alvast mijn dank.
Liever Engels de volgende keer, dan hebben andere mensen er ook nog iets aan 😉
Zelf gebruik ik gewoon de API in combinatie met HA, ik heb geen ervaring met MQTT in combinatie met dit project.
Hello,
i’ve received the module well. Was possible to connect to the ESPthngs Panasonic interface. After that, i was possible to choose my home network, fill in my password. But now he’s blinking green for a while. Can’t find him in Home Assistant app.
Can i do a factory reset?
thx
Is the module connected successfully to your (wifi) network and when you enter the IP-address of the module in your browser, do you see the esphome webinterface?
If we look in the browser, no esphome webinterface. I guess we used a wrong password.
If it does not successfully connect to wifi within 30 seconds, it will create an access point and you should be able to reconnect to that and set wifi again.
If not, you can flash the firmware to the device as outlined in the video. This does require some basic esphome knowledge.
Hi where to order this panasonic esp32 module for replace the CZ-TACG1 I use.
Please read the instructions on this page. Thank you.
Hi, this is just great stuff!
Have it up and running now and managed to make the indoor tempate sensor 🙂
2 questions:
-I cant see the NanoeX entity, is this setup as standard, or do i need to edit ESPconfig?
-How do i make the config file with ESPhome? Do i need some sort of editor?
Best regards Ed
1. Add the appropriate section to your esphome config as outlined here: https://github.com/DomiStyle/esphome-panasonic-ac/blob/master/ac.yaml.example
2. You need to take a look at our video:https://youtu.be/yMhC6Or0oTY?t=172 or/and checkout http://www.esphome.io
Hi there,
I am trying to compile the source code in ESPHome version 2022.3.1, which is installed in Home Assistant ver. 2022.9.6, Supervisor 2022.09.1 and Frontend 20220907.2 – latest.
I got board pcb_version: “220722-1”.
I used this source code. As a result, the compilation failed.
I wonder If I simply overlooked or ignored something. Thank you.
Michael
Hi Michael,
I just compiled your exact code without issues. I presume you are using the esphome SECRETS correctly?
I have no further clue as to where your compilation issues are cause by.
In secrets I have defined (it also normally complaining when there is no coresponding record) these records:
wifi_ssid:
wifi_password:
esphome_api_password:
esphome_ota_password:
I used option: Install/Manual Download/Modern Format
I’m sorry, but I have no clue as to what is your specific issue when compiling.
my compile of your file:Paste.ee – View paste bF3Jl
Hi Michel,
thank you for your reply and test. For others who might be in a similar situation, I uninstall ESPHome addon from my Home Assistant, install it again and I was able to compile code without any further changes. OTA uploaded firmware successfully.
There is one thing I am not sure why is happening, see the log. I could see quite a bit of [W] Warnings :
[19:39:53][W][panasonic_ac.cz_tacg1:259]: Dropping invalid packet (length)
[19:39:58][W][panasonic_ac.cz_tacg1:259]: Dropping invalid packet (length)
[19:40:03][W][panasonic_ac.cz_tacg1:259]: Dropping invalid packet (length)
[19:40:08][W][panasonic_ac.cz_tacg1:259]: Dropping invalid packet (length)
[19:40:13][W][panasonic_ac.cz_tacg1:259]: Dropping invalid packet (length)
[19:40:18][W][panasonic_ac.cz_tacg1:259]: Dropping invalid packet (length)
Should I be concerned? Thank you.
Hi Michel, just wanted to say a huge thank you for this project – I’ve had my CZ-TACG1 replacements for a few weeks now and after some fiddling around (my first time using ESPHome) they’ve been working flawlessly!
Thanks, that’s great to hear!