No, the Home Assistant project is not supporting that. You can use it though, but it relies on community support.
Ah, okay, thanks. It read as if it was already possible.
Let’s not make this another thread about that, it’s been discussed in multiple treads already, and everything is covered in the ADR https://github.com/home-assistant/architecture/blob/3a280053dbd12c80776ba271155a95c9ebb666b2/adr/0014-home-assistant-supervised.md
Let’s keep this thread about the post it self , and continue to enjoy the celebrations
Wow, this week is packed with awesome stuff I more tempted than ever to move from HA Container to HA Supervised…
Brilliant work everyone, thanks for all the efforts. Need to start digging into the system but I’m expecting there are events exposed to HA that can notify of issues encountered by SU or the watchdog?
Just can’t get over how sophisticated this system is becoming but still manages to be maintain a “yeah nothing to see here” facade!
Really great job!
I’m now really satisfied with myself that I decide to use a standalone hp elitedesk 800 just for all things HA. It is fast becoming the core of my whole system.
You can use the Spotify Connect add-on to turn your Home Assistant into a Spotify playing target.
It’s available in the Community add-on store.
There are no events but for now, you can do it like this:
sensor observer:
- platform: scrape
name: Supervisor observer
resource: http://homeassistant.local:4357
select: ".description"
This works now, but I can’t say for how long since it uses scraping and the layout of the website can will change in the future.
https://www.home-assistant.io/integrations/scrape/
i like the watchdog, but in my opinion its a workaround, a add-on shouldt crash
its like the deconz add-on, its reporting crashes around the same timestamp for several users , shouldnt happen
Are you willing to please elaborate on that? I am just about to switch from wifi to wired so I am super pumped about the network manager but will be considering the ip situation soon. I’ve gathered that al dhcp reservation is easier, but when would one need a static ip instead?
Nobody is going to disagree with that
In a perfect world, every piece of software out there would never get issues, but until we get there we have to do what we can
when you have routers from ISP providers, they are sometimes limited, without dhcp reservation options
i know, but if we enable watchdog, then we dont know that there is maybe an issue with the add-on
Depends on your situation a bit and personal preference really. I personally prefer static IP above the DHCP reservations, mainly because it works even when my DHCP doesn’t. For things like services on my network I really want them to be there, whatever the state of things.
As you can see above, someone else thinks we should warn people not to use it
Another case where static is needed is when your Home Assistant instance becomes the DHCP server itself, or is going to act as a DNS server (e.g., using AdGuard).
So it depends a bit + a bit of personal preference.
That is true, if you need/want that information don’t enable it
So there’s no exposed event we could use to log / notify of a watchdog reset?
well… I am using the Adguard add-on that you developed so I better stick with static ip.
Please don’t forget that many users want to use the supervisor in Home Assistant Supervised scenario e.g. on Ubuntu.
Features that inherently conflict with that usage should be somehow optional or (un)pluggable.
Losing even the community supported way of installing it would be a real shame.
Awesome stuff, guys! Dumb question: I am running Supervisor 244, but I dont see Network Manager or the Crash Reporting options. Is this because I am running a “supervised” instance? Thanks
No that’s not it, the diagnostics part will not show in unsupported systems, so that might be it.
As for the network manager, it requires that the network manager is accessable over DBUS.
Your supervisor logs should tell you more about it.
Such an amazing team, I love seeing open source software work!