What would be the simplest way to be alerted of an update to this page using home assistant?
It looks to have an RSS feed…
I’ve subscribed to it with my RSS feed reader.
I couldn’t find an RSS integration though.
I use Feedparser (HACS)
But where is the RSS feed for this site?
I use an RSS feed plugin for my browser, at it shows https://alerts.home-assistant.io/feed.xml. From the page source:
<link rel="alternate" type="application/rss+xml" title="RSS Feed for Home Assistant Alerts" href="/feed.xml" />
1 Like
would there be a possibility to create a kind of sensor if there is a new alert on https://alerts.home-assistant.io?
As the posts above yours stated:
It has an RSS feed (https://alerts.home-assistant.io/feed.xml) so you could use this to create a sensor:
Open the RSS feed in your web browser to see what to use as inclusions in the sensor.
1 Like
Tried this also. Sensor is working:
Attributes field is:
entries:
- link: 'https://alerts.home-assistant.io/#homematicip_cloud.markdown'
title: >-
HomematicIP (EQ-3) blocks public IP addresses, if access to the Cloud is
too frequent.
updated: 'Sun, Dec 20 12:00 PM'
content:
- type: text/html
language: null
base: 'https://alerts.home-assistant.io/feed.xml'
value: >-
<p>Since Dec 1, 2020, HomematicIP (EQ-3) has started to <strong>block
public IP addresses</strong> of Home Assistant installations, if they
access the Homematic IP Cloud <strong>too often</strong>. In this
case, the Homematic IP Cloud can only be reached from a cellular
network.<br />Further plans to completely block the non-partner apps
from the Homematic IP Cloud cannot be ruled out.</p>
<p>Official partners such as Mediola and Smartha are still
permitted.<br />The same issue has also been reported for other smart
home platforms, like ioBroker, which use different code to access the
Homematic IP Cloud.</p>
<p>The Homematic IP Cloud Integration is based on the cloud push
principle, by which status updates are transmitted from the cloud to
the local installation as an event, so this should not be the
problem.</p>
<p>Reducing calls to the cloud might help not to be blocked. The
following activities in Home Assistant make calls to the cloud (not
complete):</p>
<ul>
<li>Switch/dim light or power plug</li>
<li>Set target temperature or the active profile on a thermostat</li>
<li>Activate Eco/Vacation mode</li>
<li>Activate/deactivate alarm</li>
</ul>
<h2>Alternative Integration</h2>
<p>The <a
href="https://www.home-assistant.io/integrations/homematic/">Homematic
Integration</a>, which uses a local CCU or RaspberryMatic, is the
recommended alternative that doesn’t require the Homematic IP
Cloud.</p>
- link: 'https://alerts.home-assistant.io/#ziggo_mediabox_xl.markdown'
title: Ziggo Mediabox XL deprecation
updated: 'Tue, Nov 24 10:27 AM'
content:
- type: text/html
language: null
base: 'https://alerts.home-assistant.io/feed.xml'
value: >-
<p>Ziggo has been discouraging the use of the "thuisnetwerk"
feature of the Mediabox XL, they even explain <a
href="https://www.ziggo.nl/klantenservice/wifi/horizon-uit-het-thuisnetwerk-verwijderen#/">how
to undo this</a>.</p>
<p>It seems impossible to get the code running with new(er) mediaboxes
and therefore the integration will be removed from Home Assistant in
release 0.120.0.</p>
- link: 'https://alerts.home-assistant.io/#tplink.markdown'
title: TP-Link Remove Local API
updated: 'Wed, Nov 18 09:08 AM'
content:
- type: text/html
language: null
base: 'https://alerts.home-assistant.io/feed.xml'
value: >-
<h2>Summary</h2>
<p>TP-Link's latest firmware for Kasa Smart Home devices closes the
port (9999) previously used for local control, rendering Home
Assistant unable to communicate with these devices. Please see <a
href="https://twitter.com/TPLINKUK/status/1328687659133399043">this
tweet</a> for details from TP-Link, release notes for firmware are not
readily published by TP-Link. Please see <a
href="https://community.home-assistant.io/t/tp-link-hs110-smart-plug-disappears-after-latest-firmware-update/244229">this
discussion on our community forums</a> for more details.</p>
<h2>Update 2020/11/23</h2>
<p>TP-Link is offering Home Assistant users a custom version of the
latest firmware that will allow the local API to continue to work. You
will need to raise a support ticket with TP-Link and provide the MAC
address of your switch(es). Please see <a
href="https://www.home-assistant.io/blog/2020/11/23/tplink-local-access/">our
blog post</a> for more details.</p>
<p>We encourage all affected users to raise a ticket with TP-Link to
help them understand the size of their user base using Home
Assistant.</p>
- link: 'https://alerts.home-assistant.io/#loop_energy.markdown'
title: Loop Energy v1 shutting down
updated: 'Wed, Oct 21 06:25 PM'
content:
- type: text/html
language: null
base: 'https://alerts.home-assistant.io/feed.xml'
value: >-
<p>Loop Energy are <a
href="https://email.loop.homes/action-required-how-to-claim-your-free-loop-upgrade-1">shutting
down their old infrastructure</a>.</p>
<p>Existing users integrations will stop working on 2020-11-13.</p>
<p>The loop energy integration is not compatible with the replacement
infrastructure, and it does not look easy to make it so (no web access
to data, no public API, mobile app access only).</p>
- link: 'https://alerts.home-assistant.io/#icloud.markdown'
title: iCloud causes Apple ID sign-in notifications every 30 min
updated: 'Thu, Sep 10 12:00 PM'
content:
- type: text/html
language: null
base: 'https://alerts.home-assistant.io/feed.xml'
value: >-
<p>Since Oct 9, 2020 the iCloud integration prompts a sign-in
notification every 30 min. It is not compulsory to respond to the
notification, the integration is still working during this time.</p>
<p>A fix will be proposed to avoid this issue but we don't know when
yet.</p>
- link: 'https://alerts.home-assistant.io/#coinmarketcap.markdown'
title: Coinmarketcap public API deprecated
updated: 'Wed, Aug 19 04:56 AM'
content:
- type: text/html
language: null
base: 'https://alerts.home-assistant.io/feed.xml'
value: >-
<p>Since March 5th Coinmarketcap deprecated their legacy Public API in
favor of their new "Professional API".<br />This breaks the
current Coinmarketcap integration which still seems to rely on this
legacy API for it's data.<br />More details can be found <a
href="https://pro.coinmarketcap.com/migrate">here</a>.</p>
<p>Coinmarketcap moving towards the Professional API seems like it is
no longer Publicly available but they actually have a Basic tier for
their new API that allows for personal use and is actually suited for
a new Home Assistant integration (which currently does not exist
yet).</p>
- link: 'https://alerts.home-assistant.io/#tahoma.markdown'
title: Tahoma integration incompatible with firmware 2020.3.4-12
updated: 'Fri, Jul 03 12:00 PM'
content:
- type: text/html
language: null
base: 'https://alerts.home-assistant.io/feed.xml'
value: >-
<p>Updating your Somfy TaHoma bridge 2020.3.4-12 will cause the Tahoma
integration for Home Assistant to no longer work.</p>
<h2>Workaround</h2>
<p>Use the <a
href="https://www.home-assistant.io/integrations/somfy">Somfy</a>
integration which uses the official API. Unfortunately, not all the
devices are supported yet. If not all your devices are recognized via
the Somfy integration, have a look at the new Tahoma integration. </p>
<p>The Tahoma integration for Home Assistant is in the process of
being completely rewritten and modernized. An initial beta version has
been <a href="https://github.com/imicknl/ha-tahoma">released as a
custom integration</a> in order to gather feedback and bug reports.
After the testing period concludes the changes will be integrated back
into Home Assistant.</p>
- link: 'https://alerts.home-assistant.io/#dark_sky.markdown'
title: Dark Sky API closed for new users
updated: 'Tue, Mar 31 02:40 PM'
content:
- type: text/html
language: null
base: 'https://alerts.home-assistant.io/feed.xml'
value: >-
<p>Dark Sky has been <a
href="https://blog.darksky.net/dark-sky-has-a-new-home/">acquired by
Apple</a> and is no longer allowing new registrations for their API.
</p>
<p>New users will no longer be able to obtain an API key which is a
necessary requirement to configure the <a
href="https://www.home-assistant.io/integrations/weather.darksky/">Dark
Sky integration</a> in Home Assistant. The Home Assistant website
features <a
href="https://www.home-assistant.io/integrations/#weather">alternative
weather integrations</a>.</p>
<p>For existing users that have already obtained an API key, the Dark
Sky API will continue to function until the end of 2021.</p>
friendly_name: Engineering Feed
icon: 'mdi:rss'
templates:
icon_color: >-
if (state === 'on') return 'rgba(251,214,67,1)'; return
'rgba(71,116,157,1)';
icon_color: 'rgba(71,116,157,1)'
Now try find out how to show them… haha in Dashboard
You could also use restful integration and pull from https://alerts.home-assistant.io/alerts.json
1 Like
Looks nice, only thing is that the amount of subjects can be change. So maybe someone can create a script that will loop until the subjects are done.
In my example there are 8 links. When they add 1 or remove 1 then the amount will change.
That page does not appear to be up to date.
You’re absolutley right. Who can we report that to?
For non documentation website and forum issues I’ve just asked in the Home Assistant Discord / Other channel in the past. Seems to get noticed.
So today was the big test for my fancy dancy new alert automation. It failed miserably.
An alert for the security issue was posted Jan 14th. Yesterday that alert was updated, but the updated field in the RSS feed was not.
I see on github, that field looks to actually be “created”, hence why it was not updated.
RSS feed sensor config
- platform: feedparser
name: Home Assistant Alerts2
feed_url: https://alerts.home-assistant.io/feed.xml
date_format: '%Y-%m-%d'
inclusions:
- title
- updated
- content
- link
exclusions:
- language
Automation trigger, which I assumed would trigger anytime there was an alert updated on todays date.
- platform: template
value_template: >
{% set alert = states.sensor.home_assistant_alerts2.attributes.entries[0]['updated'] %}
{{ alert == states('sensor.date') }}
Think this is worth posting an issue? I hate to bother the core team for something silly.
Edit. Just for the sake of completeness, here’s my notification and a lovelace markdown card which lists all the active alerts with links.
- service: persistent_notification.create
data:
title: New HASS Alert
message: "[{{ states.sensor.home_assistant_alerts2.attributes.entries[0]['title'] }}]({{ states.sensor.home_assistant_alerts2.attributes.entries[0]['link'] }})"
notification_id: hass_alert
type: markdown
title: Home Assistant Alerts
content: |
{%- for entry in states.sensor.home_assistant_alerts2.attributes['entries'] -%}
**[{{- entry.title }}]({{ entry.link }})**
Updated: {{ entry.updated }}
{{ '\n---\n' if not loop.last }}
{%- endfor -%}