Cool that you got it. Yeah, maybe it was that you need to nuke the image and not the container. Not sure. I know it’s a bit obtuse to understand when you’re following someone else’s instructions and then have new instructions out of order.

Your browser is being fed ws://dash_host:dash_port , which is derived from the Dash_url when it loads. so when you connect from http://100.6.200.xx externally, the HTTP side renders fine, but then it goes to hit that ws:// url, but it’s getting 192.168.2.xx, which obviously doesnt work externally.

That’s going to take a deeper code change to make the ws:// match the situation, eg, not be “hard coded” against dash_url.

That is essentially correct - the ws:// url is what gets the streaming updates so you won’t see any updates, but you also get blank values at page load because the widgets attempt to connect back to AppDaemon to grab their initial state.