Help needed: "number-based entity" in HomeAssistant clarification about teslamateagile HOT 3 CLOSED

Hey, it looks like it's failing to call Home Assistant completely rather than failing to find any data

You should be able to use any numeric based entity, it does not have to be an input_number

Make sure you can call it using a tool like Postman locally to ensure you have the correct URL and authentication details

The call it makes is pretty much like this:

GET <home-assistant-url>/api/history/period/2024-05-07T04:00:00.353Z?end_time=2024-05-14T04:00:00.999Z&filter_entity_id=<your-entity-id>

With the 'Authorization' header set to 'Bearer '

You can use cURL to try it via this command:

curl --location '<home-assistant-url>/api/history/period/2024-05-07T04:00:00.353Z?end_time=2024-05-14T04%3A00%3A00.999Z&filter_entity_id=<your-entity-id>' --header 'Authorization: Bearer <your-token>'

from teslamateagile.

Thanks a lot for the tip, @MattJeanes!

There was indeed a typo in the configuration (a missing "s" in "https" for the URL). Shame on me for not double-checking before opening the issue. Sorry about that!
Once the typo has been fixed and cleaning up the homeassistant table (there were a few entries that contained "unavailable" instead of a float, which I need to make sure won't make it again into the system) everything has started working :)

Please feel free to close the issue and accept my apologies. Thanks again for your very useful product and for sharing it!

from teslamateagile.

Awesome, no problem - happy to help and see you got it working!

Top tip by the way for the unavailable problem because I had the same, you can set up an automation so that when the number sensor changes you can update an input_number with it's value. This ensures that the value is always available with it's last known value and never gets set to unavailable 🙂

from teslamateagile.