Skip to content
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

Devices stopped responding after few days #12

Open
ishikht opened this issue Nov 3, 2021 · 9 comments
Open

Devices stopped responding after few days #12

ishikht opened this issue Nov 3, 2021 · 9 comments

Comments

@ishikht
Copy link

ishikht commented Nov 3, 2021

Hello guys,

I'm facing issue with my devices, devices are not able to execute local API commands on /api.cgi, and it's impossible to locate devices by UDP multicast. They are still accessible from the cloud API (mobile app and my.terneo website).
This was caused by running this integration in HA, as I'm not using anything else.
The problem occurs every 2-3 days, and not with all devices at the same time. I have 6 ax and 1 sx devices, since Monday 2 ax are off, rest are ok.

image

Probably the problem related to devices firmware.
But it's started to be impossible to use your integration as the only one way to reboot a device is to cut off power.
Please let me know if can help somehow from my side.
Thanks

@Foroxon
Copy link

Foroxon commented Nov 4, 2021

Have a very similar issue. Described here: #10

@pravdik
Copy link

pravdik commented Dec 5, 2021

I had the same issue with config from the example. Now everything is ok after removing any '' signs from the parameters.

@ishikht
Copy link
Author

ishikht commented Dec 6, 2021

I've made my own kind of HA integration, where I faced exactly the same issue. So, looks like it's a firmware issue.
At the moment I did make it work by using a mix of cloud API and local device commands. Once a device is unresponsive (actually device just returns an empty string) I just collect telemetry from the cloud API, same with device management, it works perfectly.

@Makave1i
Copy link
Owner

Makave1i commented Dec 8, 2021

@ishikht also can be controlled via mqtt, maybe this approach have a less problems

@ishikht
Copy link
Author

ishikht commented Dec 8, 2021

@Makave1i to be honest I tried, few times, but it doesn't work as expected. MQTT has a disadvantage, telemetry sent by a device doesn't contain powerOff state (local API and cloud API has that state ), and the device continues to send MQTT telemetry even if the device is off.
image
So, if you turn off the device in any other way than by MQTT, you will never know the device off. As result, in Home Assistant, it's impossible to set actual hvac mode and hvac action.

@Makave1i
Copy link
Owner

Makave1i commented Dec 8, 2021

good news from terneo support, this param will be in the next firmware version)

@ishikht
Copy link
Author

ishikht commented Dec 9, 2021

Sounds good, thanks for update

@avpavp2
Copy link

avpavp2 commented Jun 7, 2022

Any news or updates?

@denveronly
Copy link

Have similar issue
Have 3 Terneo Bx thermostats all three are seen in Homeassistant, on startup i have temps, but cnat change them it just doesnt affect anything
floor Temperatures at startup are grabbed and seen in integration and doesnt change

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants