Feature request -- multiserver

[skug67]

The README suggests that multiserver configurations might possibly be added in the future but then asks how useful it would be. FWIW, it would definitely be helpful for me.

In the meantime, thanks -- it's very helpful to me.

[db1996]

So you are talking multi server as in multiple homeassistant instances right?

Since that readme update, there are now already options for having a local URL and remote URL based on connected Wi-Fi. But I assume this is not what you want?

Multiple instances would be such a huge undertaking. The profile triggers for example would only work for 1 server, android would simply not allow me to open multiple websockets simultaneously and not kill it in the background. That would mean I could make options for this, but the websocket side of things would simply be restricted to 1 server. You could only use actions (service calls) basically.

[skug67]

I see your point. I'm mostly trying to integrate Tasker into some routines that I run from my car via AndroidAuto. And I change the server that appears on the screen in AA through the Android companion app -- I'm not trying to have realtime connection to two servers, it would be plenty to be able to toggle easily w/o re-entering all the details.

[db1996]

Okay, I see your intention. It's a cool idea for sure.

So here's a rough idea for what I have in mind for this, let me know what you think.

• In TaskerHA, manage multiple instances (least difficult to do lol)
• Make a context switcher in TaskerHa, this triggers which instance has a realtime connection (websocket)
  • this would change which websocket triggers are currently active
  • Instance would also have to be saved to which trigger, which means if you wanted to have the same websocket state trigger for both you'd need to make a profile for both.
• In a tasker action like a service call or get state, you can choose which instance to use always (independant of current context). Since I don't think it'd be very useful to have 1 action that runs on variable HA instances, since entity ids need to be the exact same for this to work.
• Make a tasker action that lets you switch context from tasker as well

Would this be a viable solution for you?

[skug67]

Would totally work. Thanks for being so amazingly responsive and open to suggestions.

[db1996]

Thanks for the kind words! appreciated

I am currently on vacation so I will be working on this probably next week or the week after, there's a couple things on the list now. I'll keep you posted on when the new release is live with this. Might take a bit of time but I'll definitely make it