Dustin C. Hatch
ceeb61cdb0
ZwaveJS2Mqtt includes a very powerful web-based UI for configuring and controlling the Z-Wave network. This functionality is no longer available within Home Assistant itself, so being able to access the ZwaveJS2Mqtt UI is crucial to operating the network. I wanted to make the UI available at */zwave/*, which requires using *mod_rewrite* to conditionally proxy requests based on the `Connection` HTTP header, since the UI passes both HTTP and WebSocket requests to the same paths. *mod_rewrite* configuration is not inherited from the main server configuration to virtual hosts, so the `RewriteRule`/`RewriteCond` directives have to be specified within the `<VirtualHost>` block. This means that the Home Assistant proxy configuration has to be within its own virtual host, and the Zwavejs2Mqtt configuration has to be there as well.
7 lines
244 B
YAML
7 lines
244 B
YAML
homeassistant_image_name: '{{ homeassistant_default_image_name }}'
|
|
homeassistant_ssl_certificate: >-
|
|
{{ apache_ssl_certificate }}
|
|
homeassistant_ssl_certificate_key: >-
|
|
{{ apache_ssl_certificate_key }}
|
|
homeassistant_proxy_zwavejs2mqtt: true
|