Allow running multiple NetDaemon instances with separate Input_bools for apps

[FrankBakkerNl]

The problem

When running multiple NetDaemon host applications, witch different apps, connected to the same HA, the last one to start will remove the input_bools that were created by the other instance.

The proposed solution

We need to indicate which input_bool belongs to which host application. We could do that by prefixing and / or adding labels to the input_bools.. That would allow the host at startup to only delete the input_bool entities that belong to that host.

We can allow options to be set eg. AddNetDaemonStateManager(new StateManagerOption{...}) To allow the user to specify a prefix and or label for the generated entity. While at it we may also be able to allow for a naming convention to be specified, eg. ClassName, FullyQualifiedClassName

The alternatives

Additional context

[helto4real]

This one would be cool indeed.

[IPertinax]

Yeah having to roll all your apps into a single daemon is very limiting. Much prefer to register & manage apps on the individual level.

Would go further than Frank's suggestion and allow multiple app/dll registrations within the addon page.

Access to UI for config would also be nice, though using an entity for config is manageable and dashboardable.

[FrankBakkerNl]

How would you suggest it would work, having a single addon with multiple dlls? Afaik each addon is a single docker container.

What you want here ofcourse is possible if you deploy several docker containers manually (without using the addon)

[IPertinax]

Hey Frank,
I haven’t dug into the inner workings of HA but on the back of a napkin, the add-on would instantiate multiple containers (perhaps embedded, ideally not), or HA to instantiate multiple add-on instances.

It might require a little interaction with the HA team I suppose to extend the add-on containering but it would add value to the framework.

Alternatively, in a single container environment NetDeamon could launch a process for having the assembly identified through a /netdaemon6/assembly_processes.yaml &/ add-on UI.

Would want to be able to stop/start/kill each process individually and probably filter NetDeamon logs to process(es).

[FrankBakkerNl]

The NetDaemon add on is typically for the simple case to get you up to speed fast. With the requirements you describe you will eventually run into its limits and will have to look for other ways to host your NetDaemon containers.

I think what you want is definitely possible, just not using the addon but by spinning up your own docker containers. That would give you all the things you describe and the possibility to manage it any way you want. Possibly K8 will suit you better as a management platform. You could use OTEL for monitoring and logging of your NetDaemon containers using 'enterprise grade' tools. All of this is existing technology and I suspect it to be unlikely to get supported by HA addons.