hey, tried now with nabucasa urlās, but its the same ā¦
on first reboot , i have 5 errors for my 5 sensors, i think its already requesting info, while my system is not yet ready ā¦ on next scan_interval its succeeds
i should find a way to have some startup delay for those sensorsā¦
silvrr
March 6, 2020, 11:45am
15
Yup, this is a known issue and is documented in the write up.
i noticed today a new HassOs update 3.12 in the supervisor tba
is this also possible to notify with a sensor?
silvrr
March 7, 2020, 3:36pm
18
https://version.home-assistant.io/stable.json
That will fine you the most current available for your platform.
I would explore the Hassio API. I think I have seen both the supervisor and HassOS versions reported.
cool, seen you already created this one
I see way to many people asking about what the latest hassio version is or when it will be available. Hassio versions are generally available within 1 day after the main branch release. This is due to having to make the hassio build which just takes time.
To find out when a new version is available for your specific Hass.io build, create the following sensor.
#https://www.home-assistant.io/components/sensor.rest/
sensor:
- platform: rest
resource: https://s3.amazonaws.com/hassio-versiā¦
allthough you still need to know the current version installed ā¦
Vasco
March 7, 2020, 8:23pm
21
Maybe we can look at something that does a pull from command. When you do ha supervisor info in ssh, you get installed addons, version installed and version available.
Get that data from there, make it as some kind of sensor and trigger based on that
r3mcos3
(R3mcos3)
March 8, 2020, 8:40am
22
do i create llt for every addon that i want a sensor for??ā
silvrr
March 8, 2020, 1:33pm
23
No a single one will work for all of them.
1 Like
yes, that āha supervisor infoā command is indeed better
then its indeed possible to have 1 rest sensor, for all available addons, ha version, hassos version ā¦
edit: seems is doesnt give the HassOs version
r3mcos3
(R3mcos3)
March 25, 2020, 1:17pm
25
For me the notifications donāt work Iāve no clue on where it goes wrong, I see there is an update but i didnāt get a message
silvrr
March 25, 2020, 3:49pm
26
If you donāt give any info on how you set up your sensor and automation, I (nor anyone else) can help you troubleshoot.
did the sensor show up in your states dev tool? Are the attributes included?
r3mcos3
(R3mcos3)
March 25, 2020, 5:01pm
27
I have everything setup as described,
sensor & switch are in dev tools.
but i have already updated that addon. so you donāt see an update now.
silvrr
March 25, 2020, 6:38pm
28
What is the state of the automation? Did you include initial_state: false
in the automation setup?
for some reason, my rest sensors for my add-ons dont have the ālast_versionā attribute anymore?
i only see āversionā in the states ā¦ someone else got this too ?
EDIT : ok, seems the attribute is changed, its now : version_latest
silvrr
March 30, 2020, 11:41am
30
I think the latest supervisor update may be at the root of this change. Thanks for digging into it, I hadnāt had the chance yet.
Vasco
March 30, 2020, 2:20pm
31
I think @CentralCommand has a very complete one
dorremez
(Dor Remez-Guy)
April 13, 2020, 8:29pm
32
silvrr:
platform: rest resource: http://192.168.1.2:8123/api/hassio/addons/a0d7b954_adguard/info name: adguard value_template: ā{{ value_json.data.state }}ā scan_interval: 60 headers: Authorization: !secret llt Content-Type: application/json json_attributes_path: ā$.dataā json_attributes: - version - version_latest
Iām getting this errorā¦ Why?
Log Details (WARNING)
Logger: homeassistant.components.rest.sensor
Source: components/rest/sensor.py:249
Integration: rest (documentation , issues )
First occurred: 11:28:10 PM (1 occurrences)
Last logged: 11:28:10 PM
Empty reply found when expecting JSON data
silvrr
April 13, 2020, 8:48pm
33
Can you share your config?
I looks like the sensor is making the call but its getting nothing in return.