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

Failed to call service climate/set_temperature. [Error/Timeout] occurred while communicating with the OJ Microline API. #139

Open
gessl opened this issue Feb 15, 2024 · 5 comments
Labels
bugfix Inconsistencies or issues which will cause a problem for users or implementers. no-stale This issue or PR is exempted from the stable bot.

Comments

@gessl
Copy link

gessl commented Feb 15, 2024

I on occasion get the following two error messages:

Failed to call service climate/set_temperature. Error occurred while communicating with the OJ Microline API.

and

Failed to call service climate/set_temperature. Timeout occurred while communicating with the OJ Microline API.

Steps to produce is simply to change the set temperature or issue other commands via the card on the dashboard. It's unclear to me when precisely it happens, but it happens fairly regularly for me (I'll try to narrow this down.)

@robbinjanssen robbinjanssen added the bugfix Inconsistencies or issues which will cause a problem for users or implementers. label Feb 15, 2024
@robbinjanssen
Copy link
Owner

@gessl maybe add a ping sensor to your thermostat, see if the wifi is stable?

@robbinjanssen
Copy link
Owner

I think this might be related to #140

@gessl
Copy link
Author

gessl commented Feb 15, 2024

Could well be related to #140. I added the ping sensor and ping to device is stable even when the device goes unavailable the one time I just saw it. I'll keep monitoring though.

Copy link

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Mar 16, 2024
@gessl
Copy link
Author

gessl commented Mar 16, 2024

Sounds good. I'll be testing!

@github-actions github-actions bot removed the stale There has not been activity on this issue or PR for quite some time. label Mar 17, 2024
@robbinjanssen robbinjanssen added the no-stale This issue or PR is exempted from the stable bot. label Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugfix Inconsistencies or issues which will cause a problem for users or implementers. no-stale This issue or PR is exempted from the stable bot.
Projects
None yet
Development

No branches or pull requests

2 participants