Docker + Multi Instance + Phrase Broker
Closed this issue · 3 comments
I am having issues trying to get a multi Kodi setup working from a single server setup using phrase broker. I'm sure I'm missing something or it's just beyond my paygrade:
My Setup:
Docker Desktop running on Windows 10 - Single Instance (Option B3) - I'm building with the use of a config file. This is the first concern, when it builds docker prompts a desktop warning about using an external file.
I am using separate IFTT applets for each instance, the triggers are the same for each one
However for the action on each applet, in the body I have inserted the id of the kodi instance to match
Regardless, the commands always get sent to the same Kodi box (which happens to be the first one in the config file. Also noting complex commands don't seem to work. If I disable all applets except for one, and remove the id in the body, then everything works fine just firing to a single box.
So, I'm officially stumped ... I've attached some output screens as well.
am using separate IFTT applets for each instance, the triggers are the same for each one
thats the issue right there. the trigger phrases need to be different. We need the information, which kodi instance you want to target within the trigger. i.e living room kodi $
complex commands don't seem to work
According to the log-snippets you seem to encode the target-kodi at the end of a phrase. i.e. in the lounge or in the family.
but your IFTTT-Trigger does not reflect that. Thats why most command wont work, since the broker get thrown off by those words.
You could try to mix the recommend approch with your approach, if it feels more natural to you. But I am not sure if it will work well. Meaning you could make your trigger phrase like this: kodi $ in the lounge and kodi $ in the family
IFTTT should then only pass on the desired $-payload together with the kodi-ID. Then the broker should be happy.
docker prompts a desktop warning about using an external file
thats to be expected on windows, if you use the external file approach.
Appreciate the quick response, I'll make some changes tonight and feedback how I go.
timeout -> closed. Please open a new issue, if you still have problems.