I’m trying to run an app locally during development, and suspect that it’s failing to enumerate devices in my network because it’s failing to do UDP multicast.
It looks like the homey app run command runs the app with bridge networking. Is there a way to tell homey-cli to use host networking (besides trying to manually replicate the docker run command)?
Good idea. I tried that, but then the app still has issues resolving IPs, so perhaps it’s not the multicast. Just thought I’d try to reproduce with host networking locally to see if that helped.
Actually, now it works with -r so I guess the lack of. multicast was the issue. Would be nice if homey cli had the option to run with host networking for these use-cases.
Resolving the docker run command via docker inspect \ --format "$(curl -s https://gist.githubusercontent.com/efrecon/8ce9c75d518b6eb863f667442d7bc679/raw/run.tpl)" \ container name
did not work, probably because home-cli also sets up a web socket to the homey or things like that (?)