Greg White

I'm in, watching this thread with interest. My WT32-ETH01 board is still a month or so off delivery; but if you are impatient like me and want to get a...

I had this problem sometime back; [issue](https://github.com/nicholaswilde/helm-charts/issues/3). The problem is related to Charts that are build using the ‘Common’ library. You can resolve the issue by adding the following to...

Subscribing to this issue because I have the exact same problem as reported here regarding a locally hosted almond-server. This message appears in the almond-server logs when home-assistant tries to...

Hi @markusressel , @gcampax Here is a temporary workaround I am using until an official solution becomes available for connecting to almond-server on a remote host. I have two hosts...

Hi @gcampax thank you for your reply. First off thanks for pointing out the pitfalls and challenges that this workaround brings, anyone considering this solution would need to proceed with...

@markusressel Sorry to hear that the workaround isn't working for you. You just need to ensure that 'almond' and 'nginx' is attached to the host network. Indeed you followed the...

Not sure if this is of use to you, but since the original post I have migrated my setup from Docker to Kubernetes. In this setup I had to implement...

@markusressel Great to see you have got it working. I am not experiencing those websocket errors you refer to. The connection should automatically be upgrade if using the nginx config...

I'll take that back. Thought I'd do a refresh on almond and I am now seeing websocket related errors shortly after the device creation phase. ```logs Error on Home Assistant...

I fixed the websocket issue by: 1. removing base_url from configuration.yaml as per [Home-Assistant 0.110 breaking changes instructions](https://www.home-assistant.io/blog/2020/05/20/release-110/#breaking-changes) 2. set external_url & internal_url to HA's full FQDN i.e: *(because my...