Sebastian Plattner

we see now the following issue and I think its related to this. argocd-server pod uses serviceAccount: `argocd-server` while the Service Account accually has the name `prefix-argocd-server` here it is...

> Does this solve the same problem as described in https://bugs.racktables.org/view.php?id=665 ? I guess this could also solve the mentioned Problem

I guess I should move part of this into the neeo-sdk-toolkit?

I also added `ADAPTERPORT` as Env Variable, so I can set this when running multiple Docker Container with NEEO SDK Devices

ok, I just figured out, that I probably should use the neeo-sdk-toolkit to run multiple Devices in one Container. But the Problem with the wrong IP Address taken for the...

Sure, check https://github.com/splattner/neeo-driver-googlecast ``` FROM node:latest WORKDIR /app COPY package.json /app RUN npm install COPY . /app EXPOSE 6336 CMD ["npm","start"] ``` or by using the newer @neeo/cli ``` [...]...

> I see the use case for this, that makes sense. As you mentioned if we go this way it's more important to add this in the neeo-sdk-toolkit/cli since it...

I see the same behavior. Installed as a Addon and almost with all restarts, I have to reconfigure the Device. Normally I delete the Integration, restart HomeAssistant add the Intregration...

I see the following error ``` 2022-07-12 11:48:14 WARNING (MainThread) [homeassistant.components.deconz] Invalid key for deCONZ at core-deconz ``` so somehow, the key always becomes invalid

this seems not to be in https://github.com/cilium/cilium/releases/tag/v1.15.4 do I see somewhere when this will be released?