-
Notifications
You must be signed in to change notification settings - Fork 19
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
Error: 'b' format requires -128 <= number <= 127 #208
Comments
So, I opened the Toshiba Android app and agreed to the new terms. It seems to have resolved the issue. Will update if it reappears. |
And updating again. The integration failed again. But after opening the official app and instantly returning to make changes in HA the setting changed. |
Same problem. Also reloading the integration solves the issue for some time, then it returns with no clear pattern. |
I've been okay a couple of days now. But still unsure what caused the initial issue. Will report back if it reappears. |
I put integration reload to happen every morning at 3:50AM, but this morning it has failed again. This same error coming from every function, does not matter if I try to set fan speed, temperature, operating mode or what. But again, reloading the integration fixed the issue... until next time. |
Now it's impossible to use, it has failed again... home assistant 2024.10.4, latest integration
|
The way to use this now is in automations by first reloading the integration and then doing what you need to do, this same every time you want to change something. Don't know if this is specific to just Toshiba Polar 35 with adapter version 2.4.00. |
I have the same problem. Home Assistant 2024.11.2, adapter version 2.4.00. We have a Toshiba multi split system with two indoor units: a Premium 13+ model and a floor model. I have used this Toshiba integration for almost a year, and the last couple of days it has become unusable. |
Here is the log entry I see: Logger: homeassistant.components.automation.turn_off_heat_pump_when_warm While executing automation automation.turn_off_heat_pump_when_warm |
Yes, this is becoming hurtful. Rebooting HA will fix it for sometime, but after half hour/hour or so - changing for example temperature becomes impossible and automations won't work due of:
|
same issue here as well... |
Same issue here... making a change in the Toshiba app on the phone helps for a while, or until sufficient commands have been sent from HA, then it breaks again. |
It just happened to me after accepting new terma in Toshiba mobile app. After that, i have reloaded the HA Toshiba integration plugin and started to work again correctly |
Does it work after a few hours? |
This works only for a limited time. Reloading the integration fixes this, but for a limited time again. |
Thanks @pjylkka, I raised #211 and I think you're right, that's a duplicate of this issue. I found that rolling back from HA 2024.11.2 to an earlier version fixed it, so I assume something has changed in 2024.11.2 that is incompatible with this integration. Someone mentioned on the other thread that there was a change in the Websocket implementation which had caused other plugins to break. |
I rolled back to: |
@wiblaa I'm now seeing the same issue. After opening the Toshiba app and clicking "Agree", the integration doesn't work for me either. |
Same issue, probably appeared already a couple days ago with some automation acting up but only noticed the same error message trying to set fan manually now: 'b' format requires -128 <= number <= 127. Have not updated core beyond 10.4. |
It seems to me a reinstall of the plugin helps. I've been good for several
days in between. But today I installed the latest ha update, and lost the
heater. It seems to work as expected after a reinstall from hacs.
…On Fri, 22 Nov 2024, 21:38 psoininen, ***@***.***> wrote:
Same issue, probably appeared already a couple days ago with some
automation acting up but only noticed the same error message trying to set
fan manually now: 'b' format requires -128 <= number <= 127. Have not
updated core beyond 10.4.
—
Reply to this email directly, view it on GitHub
<#208 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BAF5I5VZFKIXU67WIAOCPS32B6B3VAVCNFSM6AAAAABRASL3TWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJUGY2TCMJZGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Error seems to be present att about 3/4 of commands. Can't figure out if there are other circumstances causing it. Looking into using Google assistant instead until plugin is updated. Not ideal, but at least commands seem to get sent that way. |
I have same issue. Even when it works little while after restart this totally breaks my automation which does not work anymore due this. I'm running 2024.11.0 so it's not like it is only on never 2024.11 versions. I'm pretty sure all was working few weeks after upgrade and I only hit this recently so it is constantly an issue on my automation. |
Toshiba must be changing something. Integration has started to go 'unavailable' after a while now, need to test for that status as well instead of just catching the exceptions in the reloading health checks. Reloading the integration fixes that as well, until it breaks again. |
I also have this since some time. It comes and goes by random. |
This seems to be an issue with the toshiba-ac package where I’ve submitted an issue. I have a suspicion that this only happens when outside temperatures are below zero, does that seem right? |
We dropped below freezing a few days ago, so that tracks... |
This actually could be. One of mine is -5 and gives the error - other +6 and works. |
Seems to be the case for me also. Don't have the logs to verify, but the automation traces for yesterday and today are ok, and we've been above zero during that time. Nice catch @pbock ! |
I suspect that is correct. I was already wondering why my automations had been working correctly since Sunday. I still have occasional "state reload failed" messages, but nothing more serious. |
Having these issues as well. Not below zero at the moment. |
@h4de5 could you have a look at this issue please? Temperatures will be below zero next week and I suspect that my Toshiba automations will break then again. |
as you have already stated, this error is coming from the api package below. the integration here is just a shell for that. this is the same for most of the other issues here too - there is hardly anything i can change. |
same issue here as well with (toshiba v[2024.9.0] and latest HA. Opening Toshiba app and/or restarting HA solves the problem for a while, then it starts to give errors again shortly after that. |
Should be fixed in toshiba-ac v0.3.10 which has just been released! Any chance we could get this updated, @h4de5? |
fixed in #214 |
Hi!
Firstly, thank you for all the effort put into this!
Now, since a few days, don't know when for sure, I'm getting the following error message for any attempt setting of my device, haori.
Error: 'b' format requires -128 <= number <= 127
Is there anything I can do to resolve this? Reinstall is not helping.
The text was updated successfully, but these errors were encountered: