Is there a way to permanently disable the “unsupported system” message? I acknowledge that HA devs would not support my system in case of issues coming up because of me running an extra docker container that’s for automation and doesn’t touch HA in any way, but can’t find a way to completely disable this warning from showing up. Clicking the ignore button seems to only hide it temporarily. It’s a personal annoyance to get excited for a red notification icon, thinking there’s an update for something, only to be presented with this message instead. Any assistance to do this would be greatly appreciated.
Yes it’s using supervised and HA is running in docker containers on Debian. After I added my other own custom docker container for a personal app I developed, that’s when the warning showed up and upon researching it, sounds like it’s because it wants no other containers running on the system. I’d rather not require a second server to hide a message, though. Does that mean there’s no way to hide the warning even though I’ve already acknowledged it a few times?
does your app interact with HA then?
Dockers can be pretty good separated, so only if you want them to interact, they would be aware of each other.
If so, then it would require to more clear on the unsupported part.
If not, more configuration on docker will resolve this thing
Nah it doesn’t care about HA at all. Listens on one port that’s unrelated to HA and is a simple API, nothing advanced. I just have it on the same system as HA because some separate automation on the network uses it (but not HA). Haven’t gone entirely in to determine how HA knows of another container is on the system (different subnets, other container has no mount points), but assumed (maybe incorrectly) the supervised software relayed information to the HA containers or something.
Context of the custom container. It’s just a python API. Here’s the dockerfile, followed by the command to run it.
But no notes about any override (or intent to do so.)
I strongly suspect youre living with the message if you decide to operate that way. Reading the docs I’m fairly certain a feature request to remove the message would be denied out of hand. It’s like the not activated message on a windows client that hasn’t installed an activation key. It’s not just for you its also for anyone else (dev has no clue who might be installed this way nor who would help them with installs) who might login to assist you with your install.
Will it cause a problem. Probably not - probably just an eyesore for you but I seriously doubt you’ll ever see it go away.
Yes, because of the requirements outlined by Nathan above. There is no way around this. Supervised is a terrible install method.
If you want to run your own software and know Docker (as you seem to) you should be using a Container install. You will lose access to managed add-ons but you can install Docker containers for most if not all of these instead. You just have to manage the updates instead of the supervisor doing it.
built your api as 3rd party addon for HA will get you out of the ‘unsupported’ corner as the supervisor can then manage it within the rules, but will not do anything with it.
Still, I’d be avoiding Supervised installs. The devs hate it. If this grey wedge gets small enough I wouldn’t be surprised if it gets dropped as an official installation method (no there are currently no plans to do this, and this is just my opinion).
Of the 4 options available, supervised is the best for my use case and has treated me well over the past 2-3 years. As mentioned in the thread, container loses some capabilities that I require (it was the first method I installed by), including the add ons feature. OS install limits greatly what I can do with the system at an OS level (I lock down devices heavily on the network and also have custom system level logging and such that the OS install would prevent me from doing, as I’ve tried to use it before), and the core install is basically just a less useful install method than container. Supervised is honestly the only option that meets all my personal requirements for HA to function and also give me my freedom to control the system the way I want.
That being said, I’ll look into the 3rd party add on method mentioned above, hopefully that gets me what I’m looking for.
Where can we suggest a “feature request” to turn off the “unsupported system” message? I would find it useful to have a checkbox that acknowledges that it is unsupported, that I know it is unsupported - and ignore the check (or at least the daily reporting of the check.)
I do a bunch of development and run unsupported as a basic rule. I think having the option to disable this message would be useful for people in this situation, and others who just prefer to run unsupported configurations.
I do know that there are many people running unsupported software who have mentioned the desire to turn this off. Being that this is open source software, I could just go in and hunt down the process and comment it out, but I think it would be a good showing to allow the permanent disabling of a status message that is a daily annoyance. (You can keep the check - but just offer disabling the message.)
There are many simple ways to implement this change, and no good reason for it to remain unimplemented.
Again, it is open source, and can be disabled - this is something that many people have been looking for… and honestly, telling a person asking how to disable it that they need to “move to a supported installation” isn’t technically true. You could tell them where in the code the process lives and what lines to comment out to disable it, or inform them of the process of recommending a “feature request” to have it considered for implementation. Again, this is open source, and your answer seemed very “closed.”
I’d suggest you search. There are at LEAST six I know that have been closed as dupe and that one will too. It’s already out there go search. (it’s a perennial ask)
Also it probably won’t happen see the discussion in the thread when you find it.
TL;DR That message isn’t for you it’s for support when someone sends logs for review.
The massage that pops up is the only thing I’m asking for, I said you can keep the check and forward that information if I were to send a log for review.
The message puts a “dot” for a notification, the same way an Update does, or a system message. I want to disable this message popping up… keep the check, keep the log… just want to shut off the notification that I’m running an unsupported system.
I searched the Feature request and saw one for this still open but had no votes, was buried and was kinda rude (to be honest) and didn’t give any constructive feedback… Again… if this is just for the support people, then the end-user doesn’t require a daily notification whenever they click “ignore” as a matter of fact… if the “ignore” button did its job… I wouldn’t be here.
Also, if this is indeed a perennial ask - why hasn’t it been implemented? The option to permanently shut off a notification with understanding of the consequence seems pretty innocuous.
Speaking as a support person (my entire 25 yr career)
I SUCKS when you spend hours on something that could have been surfaced in a UI or log and checked. If I remote in to help you and that’s not there then I burn six hours trying to fix something (exaggerating yes) that’s caused by you having an unsupported config I’m going to get quite… Pissed.
Thats why these are there and not able to be turned off. Again. Not for you. Same reason windows drops a watermark on the desktop in beta, pre-activation and prerelease.
Just being real here you have about a 0.01% chance of a developer EVER accepting this kind of FR.
I feel support pain on that… but I would rather there be a flag set that says under system properties that this is an unsupported configuration than a daily popup message that I have to “ignore” daily which then continues to pop up daily after being “ignored.” Again, this is an open source platform, Microsoft putting a Beta flag on something is one thing… that is a closed source platform… to force a daily unsupported system message on Open Source users seems a little unnecessary.
I do understand the support end, but if the system log included the “Unsupported status” of the system, there would be no issues with it for the user. If the first support question would be “is this a supported implementation?” flagging the end-user daily is less assistance then adding the status to the reporting method.
Over 30 years of total support here. I feel you, man. I don’t think the ask to disable the constant “reporting nag” is an issue… there is already an “Ignore” button on it… heck I would be happy with a compromise of “Ignore for 30 days” to actually keep the message from popping up for 30 days. But when I click “ignore” I’ll see it again tomorrow - even when I change nothing.
Let me control my installation. I don’t need support or your tyranny. If I want to run a new version of the OS that is my perogative. Not being able to hide this message is bloody ridiculous, this is not open source.
