Where you got that last card image from (blue one)? Looking great!
thanks, and yes, using the temp sensor too here.
would wish the /hardware/info would do as it advertises… in my instance it outputs a huuuuge page of all possible data, and the displayed output in the docs is from some time ago, pure and simple. If I need to find the USB port for the zwave stick I have to scroll a ridiculous amount of lines…
/misc/info isn’t allowed?
1 Like
this is it:
type: picture-elements
image: /local/homeassistant/homeassistant.png
style:
'#root>bar-card':
$: |
ha-card {
background: none;
box-shadow: none;
}
bar-card-name {
color: white;
font-size: 100%;
font-weight: normal;
margin: 4px;
}
bar-card-currentbar {
border-radius: 7pt;
}
bar-card-backgroundbar {
border-shadow: 2pt;
margin-top: -2pt;
margin-left: -2pt;
border-radius: 7pt;
border-style: solid;
background: rgba(255, 0, 0, 0.8);
}
bar-card-value {
font-size: 125%;
color: white;
font-weight: bold;
margin: 4px;
}
elements:
- type: state-label
entity: sensor.last_boot_phrase
prefix: 'Last boot: '
# title: text
style:
color: white
font-size: 90%
left: 65%
top: 25%
- type: custom:bar-card
# animation:
# state: 'on'
columns: 5
direction: up
width: 10px
height: 90px
positions:
icon: off
indicator: off
minmax: off
title: outside
value: outside
name: outside
style:
left: 50%
top: 68%
width: 100%
scale: 100%
entities:
- entity: sensor.processor_use
max: 100
min: 0
name: Cpu
severity:
- color: '#40bf40'
from: 0
to: 40
- color: '#ffde00'
from: 41
to: 80
- color: '#fd0000'
from: 81
to: 100
- entity: sensor.cpu_temperature
max: 100
min: 0
name: Temperature
decimal: 0
severity:
- color: '#40bf40'
from: 0
to: 40
- color: '#ffde00'
from: 41
to: 75
- color: '#fd0000'
from: 75
to: 100
- entity: sensor.memory_use
max: 4096
min: 0
name: Memory
decimal: 0
severity:
- color: '#40bf40'
from: 0
to: 1280
- color: '#ffde00'
from: 1280
to: 2500
- color: '#fd0000'
from: 2500
to: 4096
- entity: sensor.disk_use_home
max: 64
min: 0
name: Disk
decimal: 0
severity:
- color: '#40bf40'
from: 0
to: 25
- color: '#ffde00'
from: 25
to: 50
- color: '#fd0000'
from: 50
- entity: sensor.swap_use
max: 1024
min: 0
name: Swap
decimal: 0
severity:
- color: '#40bf40'
from: 0
to: 640
- color: '#ffde00'
from: 640
to: 768
- color: '#fd0000'
from: 768
haven’t checked it for a while, so maybe settings in the card-mode or bar card have changed meanwhile. This is still working as it should though 
2 Likes
Was sensor.hacs_updates supposed to be sensor.hacs? Looks like in the HACs documentation that’s the sensor name for updates.
Ah yea, I need to update that. It used to be sensor.hacs_updates but this was originally made a while ago. I believe it changed to sensor.hacs when v1.0 came out since a lot changed at that point.
I still have it as sensor.hacs_updates in my system since I just clicked and changed the entity ID. But I should update it to use the default name as most people will have that.
1 Like
Just to note: HA Core v2021.4 brings some enhancements for Supervisor:
The Supervisor is now also in the integrations dashboard, and provides entities for all kinds of things! These entities are disabled by default, so head over to the integration and see if there anything in there you could use. Thanks @raman325!
So this way you can now - out of the box - use entities for current version and available updates for addons including for Home Assistant OS.
sensor.home_assistant_operating_system_version
sensor.home_assistant_operating_system_newest_version
binary_sensor.home_assistant_operating_system_update_available
Downside: 3 single entities where @CentralCommand’s command line sensor definition only needs one entity with three attributes. For this reason I´ll not switch to the Supervisor integration provided version and update information. Never change a running system 
, might be of interest for people starting from scratch with update notifications though.
It is fantastic! 
However, in this way there are many more entities, while with a single sensor you have news on more addons for example (update available, current version, new version)
uhmmm, and you don’t know if an addon is working or not. 
Yea I’ve been looking into this. I had a long chat about this in #beta in discord during the beta to see if I could convert over to using those sensors for info on whether the update is available instead of hitting the supervisor API with curl.
Unfortunately its pretty tricky to just update the package to those because there’s really no easy way to find them. The sensors created by the integration don’t have a common pattern in their entity ID that would make them easily findable by for loop to quickly see if any addons have updates. It also doesn’t look like they have an attribute or anything that makes them easily identifiable. They do all come from the same integration but that info can’t be leveraged in a template currently.
However blueprints do have selectors around integrations so I’m revisiting that in light of this. But I really don’t want to make a blueprint that requires people make one per addon as that just seems like a lot of grunt work and then a lot of automations clogging their list. One in total would be ideal, trying to see if that’s possible.
Anyway I’m still looking into it (and if anyone has any good ideas please share!). For now though I’m going to leave the package as is.
3 Likes
Is there a service to call to start the updates (have/supervisor/hassio) from telegram?
For updating an addon you have this:
service: hassio.addon_update
data:
addon: <addon slug>
For updating core & supervisor there isn’t but you can make them like this:
shell_command:
update_core: 'curl -X POST "http://supervisor/core/update" -H "Authorization: Bearer $(printenv SUPERVISOR_TOKEN)" 2> /dev/null'
update_supervisor: 'curl -X POST "http://supervisor/supervisor/update" -H "Authorization: Bearer $(printenv SUPERVISOR_TOKEN)" 2> /dev/null'
Although for supervisor you could also just wait since it auto-updates.
1 Like
Thanks, Any other suggestion for HACS integrations?
Well the package at the top includes an alert which sends a notification sensor.hacs_updates has a value greater then 0. The notification just has the count of hacs packages requiring updates though.
If you want a notification as an update to a HACS component becomes available with the details of what HACS component needs an update you can do that but its a bit trickier. I did that in Node RED since I find that easier, the export of my flows for that is in the second post. You can do it in pure HA though with something like this:
automation:
trigger:
platform: state
entity_id: sensor.hacs_updates
action:
- choose:
- alias: Update count went up
conditions: "{{ trigger.to_state.state | number > trigger.from_state.state | number }}"
sequence:
- variables:
component: >-
{% set old_ids = trigger.from_state.attributes.repositories | map(attribute='name') %}
{{ trigger.to_state.attributes.repositories | rejectattr('name', 'in', old_ids) | first }}
- service: notify.me
data:
title: "HACS Update - {{ component.display_name }}"
message: "Newest version of {{component.name}} is {{component.available_version}}, installed version is {{component.installed_version}}"
data:
tag: "{{ component.name }}"
default:
- variables:
component: >-
{% set new_ids = trigger.to_state.attributes.repositories | map(attribute='name') %}
{{ trigger.from_state.attributes.repositories | rejectattr('name', 'in', new_ids) | first }}
- service: notify.me
data:
message: clear_notification
data:
tag: "{{ component.name }}"
Just an FYI I have not tested this code. My automation around this is in Node RED so I’m just trying to translate what I have to HA YAML. It’s kind of complicated so it may need some adjustment but hopefully you can see what’s going on and take it from there if it does.
Also if you don’t use the HA mobile app or HTML5 notifications then you can drop the clear_notification bit. That automatically clears the notification after you’ve done the update but those integrations are the only two that support removing notifications. If you use telegram or something for example then dismissing after update isn’t an option.
Thanks for this, actually i was using the solution that alexkrupin posted some post above, that basically notify for update of everything, but the thing i miss is to just avoid opening HA to let the updates start but i want to use a telegram command, you solved the problem with Core (Supervisor and Addons have autoupdates Activated) i just miss something for update HACS components where i still need to open HA, start the update of outdated component(s), restart core. sometime pretty boring
…and sometimes pretty important to e. g. read the change log/release notes. For me personally that’s a bit too much of automation.
Starting the update from telegram, at least for me does not mean that i’ll skip looking at the changelog/release note (infact direct link to these are in notification message) 
1 Like
This is what I do as well. My notifications about updates for a specific component always include the following:
- The new and old version numbers (to see if its patch, minor or major)
- A link to the changelog notes
- A link to open to the thing’s page in the HA UI (if necessary)
- An action which starts the update from the notification without needing to open HA UI (if possible, can’t do that with HACS sadly)
With core updates I took it even further. My notification also includes whether the config check has passed or failed and a link to the logs of that add-on. So I know whether its safe to click that update action or whether I have to go look at the logs to see what happened.
This way I can completely manage my updates without touching the HA UI but still be safe about it.
1 Like
Hello,
I installed the full package,
for starters I wanted just a simple line where icons show up if there are any updates, like this (currently is it showing a HA update)
However, I know there are also addon updates but they are not showing 
(I simply want an extra icon to show up if there is anything with an update for now, ill work from there to get more details )
this is my code in the ui-lovelace.yaml
- type: entity-filter
entities:
- entity: alert.ha_update_available
name: "HA"
show_state: false
- entity: alert.supervisor_update_available
name: "Supervisor"
show_state: false
- entity: alert.addon_update_available
name: "Addons"
show_state: false
- entity: alert.hacs_update_available
name: "HACS"
show_state: false
- entity: alert.audio_update_available
name: "Audio"
show_state: false
- entity: alert.cli_update_available
name: "CLI"
show_state: false
- entity: alert.dns_update_available
name: "DNS"
show_state: false
- entity: alert.multicast_update_available
name: "Multicast"
show_state: false
- entity: alert.observer_update_available
name: "Observer"
show_state: false
state_filter:
- "on"
card:
type: glance
title: Beschikbare updates
these are my entities, I think there is something fundamentaly wrong, because the addons update warning is showing “idle” , should that not show “on” ? or a number of the amount of updates available ?
Can anyone point me in the direction to where I probably am going wrong ??
Thank you,
Hans
Shell command seems to be missing the -o UserKnownHostsFile=/config/.ssh/known_hosts option.
1 Like
I have one strange behaviour when trying to adopt this for two hosts: while it´s working great for host #1, the command_line sensor for host #2 just gives “Unavailable” (and therefore the binary_sensor of host #2 is unavailable too).
I checked the whole SSH passwordless part - same for both hosts, works great.
I checked the command in Portainer first - same for both hosts, works great.
I checked the /config/.ssh/known_hosts file and it contains lines for both hosts.
No idea why it works in Portainer but the command_line sensor fails. Any idea @CentralCommand 
No idea what else to check
Update:
- I rebooted the faulty host #2
and now sensors are notAfter next HA restart againunavailableanymore. BUT instead it shows 0 updates (there are 4).unknown. - And ALL sensors don´t get updated.
scan_intervalis 5 minutes but last change has been only once when HA has been restarted last time. Those ssh command_line sensors are the first and only one behaving like that. Strange… what the?
Update 10 days later: seems to work now, somehow.
Thanks everyone for the great info! I made a package that takes all of the notifications and puts them into one persistent_notification. On GitHub: packages/update_notifications.yaml
8 Likes