Closed gchrisak closed 10 months ago
This is a good idea. Maybe there is possibility to increase the timeout for entities or leave the timeout as customizable field in the config.
To be honest, I don't think that's a good idea. Displaying an "unavailable" is somehow more honest. We don't have the endpoints under control and errors and failures can occur at any time on the part of Toyota or us. If there is such a failure, we simply do not know at this point what the correct values are. The values displayed should also reflect this.
If this is a problem for you, you could create template sensors to intercept this and display continuous values.
With the new API version, however, the endpoints should be more stable and responsive, so that "unavailable" should no longer be displayed so often 😉
@CM000n are you sure it's stable? https://ss.codeone.pl/ss-2024-04-04-14-59-51-1712235591-uZdS2tkg.png
I have many issues with it and it's not internet problem since other cloud based sensors work fine. Is there a way to find out root cause why it goes to unavailable state?
Hello. Thanks alot for all your efforts! Would it be possible to display last collected value instead of unavailable on the sensors? With Toyota connected services being so unstable, every few minutes all sensors show as unavailable.