-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CZ-TAW1 crashed after the original firmware update #29
Comments
Addition: |
I'm using firmware from the link: I've the same problems like @omenukas |
I tried the procedure to access ssh ( to gather any logs) : panasonic_heat_pump/commands/OSCommand umount /overlay and after rebooting your software stops working, only helps me flash the device again . |
hello, were you able to configure homeassistant ? you can help me ? @donpablos @omenukas |
@omenukas |
I solved the problem by buying this module: |
@dimaregabriele |
I first tried with the version downloaded in Aug 2023 (v1.0.166 I guess Jan 12 2021 /usr/bin/GoHeishaMon_MIPSUP) without success so I SSH the module and ran manually GoHeishaMon_MIPSUP :
I found this post #27 (comment) and tried again but GoHeishaMon (version 1.1.191 ) crashes randomly I wrote a short script to run GHM and check when it crashes.
Latest version GoHeishaMon (version 1.0.192 ) also crashes randomly I have no idea where to look to avoid these crashes. |
The CZ-TAW1 module was connected to the Aquarea Smart Cloud and stopped working sometime in the fall/winter. The "Status" indicator started flashing red. After rebooting the module it works for a while and then breaks again.
I decided to try sending the heat pump data to the Mqtt server.
I performed a firmware rewrite using the following link:
https://www.mediafire.com/file/c2ac2ls56fhzxbz/GoHeishaMon1.1.191z166.zip/file
Everything started working and I was already happy, but only half an hour. And then the data to mqtt stopped going. After rebooting the module, it's the same again - it works for a while and then stops again. The situation is the same as with the original firmware.
Do you have any ideas on how to solve this problem?
The text was updated successfully, but these errors were encountered: