-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
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
OASA telematics unknown travel time #23542
Comments
I’m using OASA API over 2 years and I want to mention that the service goes down several times a day. It seems that your issue is a connectivity problem. |
Hey, it has never worked for me from day 1 since it was introduced with the new HA version. |
@panosmz can you have a look at it? thank you!
|
Hey @sicutero. This was solved in #23381, I forgot to open an issue, apologies for that. Your first issue was due to oasa api downtime, as @smartHomeHub mentioned, it can happen sometime during the day. |
thank you ! |
Thank you for the update ! |
Yes, that's how it's supposed to be. The state returned is a utc timestamp, so you can choose the relative time representation on your frontend. See #22196 (comment). You can format this value to display like |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
Home Assistant release with the issue:
0.92.1
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io RPi3+
Component/platform:
https://www.home-assistant.io/components/oasa_telematics/
Description of problem:
The sensor will always show unknown as time of arrival.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information:
The text was updated successfully, but these errors were encountered: