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
do i create llt for every addon that i want a sensor for??â
No a single one will work for all of them.
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
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
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?
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.
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
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.
Iâm getting this error⌠Why? 
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
Can you share your config?
I looks like the sensor is making the call but its getting nothing in return.
Here it is⌠the !secret llt is the long result i got from creating a new LLT
Is this still working? I get âREST result could not be parsed as JSONâ in logs.
Yes, post your config, maybe I can help troubleshoot.
Found my error, typo 
Did you solve this problem? I have it too with my config:
resource: http://192.168.50.54:8123/api/hassio/addon/core_deconz/info
name: deconz
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
Logger: homeassistant.components.rest.sensor
Source: components/rest/sensor.py:249
Integration: rest (documentation, issues)
First occurred: 10:20:31 PM (6 occurrences)
Last logged: 10:25:39 PM
Empty reply found when expecting JSON data
Any ideas?I am having problems with thisâŚ
secret llt is a long lived token. To obtain a long lived token, go to your users profile page and scroll all the way to the bottom. Create a token and copy it in to your config. Once you close the window with the LLT you cannot view the token again so be sure to record it. My secret is formatted as follows: llt: "Bearer adfasdfadsfadsfasdfasdfasdfNiJ9.eyJpc3adfasdfasdfTZlZWQ0Nzsuperlongstring of numberslettersetc" Be sure to add the Bearer before the token and place the entire thing in quotes.
When I go to the bottom of the page an click create token, it asks for a name I name it Bearer, then I click ok. It produces a llt. I copy this to my secrets file looking like this.
âBearerjbf;qkbgfbrgbgbrbgbgbgbbgbergbgbrbgâ
Is this what I am supposed to do?
Also when creating the sensor the resource has an http address:8123, I am using Nabu Casa, what do I add.
Thanks for the help.
Add a space after bearer in the secret.
If you are are using nabu casa you should be able to use just the ip with http for this internal call. Just as shown in the example.