| 24 Nov 2021 |
 Maniac of Madness | security.acme.acceptTerms = true;
security.acme.email = "my_name@example.com";
services.nginx = {
enable = true;
recommendedProxySettings = true;
virtualHosts."hass.example.com" = {
forceSSL = true;
enableACME = true;
extraConfig = ''
proxy_buffering off;
'';
locations."/" = {
proxyPass = "http://127.0.0.1:8123";
proxyWebsockets = true;
};
};
};
networking.firewall.allowedTCPPorts = [ 80 443 ];
| 12:53:54 |
| Maniac of Madness | But I'm getting the following error:
Nov 24 14:46:27 home acme-hass.example.com-start[10905]: [hass.example.com] acme: error: 400 :: urn:ietf:params:acme:error:connection :: Fetching http://hass.example.com/.well-known/acme-challenge/Cc5Lrk6p3SdDryHkOHhIUAXvWq9ccTebnnSNaBA2JqE: Timeout during connect (likely firewall problem) | 12:54:55 |
 Linux Hackerman | Is the machine on a residential internet connection? If so, are ports 80 and 443 forwarded to it on the router? | 12:55:51 |
| Maniac of Madness | In reply to @linus.heckemann:matrix.mayflower.de
Is the machine on a residential internet connection? If so, are ports 80 and 443 forwarded to it on the router? Yes, they are. I can see my instance, and it's using a temporary self-signed certificate. | 12:56:33 |
| Linux Hackerman | Can you see it from anywhere other than your home internet connection? | 12:57:07 |
| Maniac of Madness | Let me check with cell data. | 12:57:19 |
| Maniac of Madness | Oof, I guess that's one way to find out things. It timed out. | 12:59:00 |
| Linux Hackerman | Do you actually have public IP addresses from your ISP? If you're behind CGNAT for IPv4, and don't have IPv6, it won't work at all, for instance | 12:59:58 |
| Maniac of Madness | I found out about CGNAT just today. Indeed CGNAT is being applied by my ISP, with the IPv4 address redirecting me to some other client. The IPv6 address worked just fine, so I disabled the A record on my Dynamic DNS provider (freedns.afraid.org in this case) and only kept the AAAA record. | 13:02:43 |
| Maniac of Madness | There might be some security restrictions applied by my ISP, which I can't check at the time. That's where I'm leaning at. | 13:03:41 |
| Linux Hackerman | for IPv6, the firewall stuff on your router could work in several different ways as well | 13:04:46 |
| Linux Hackerman | if your hass machine has a public IPv6 address, you'll need to make sure it's stable, and configure the router to allow ports 80 and 443 to it | 13:06:21 |
| 26 Nov 2021 |
 Jeroen | How would i create the following HASS config with nix?
entity_id: >
{% if is_state("input_select.chromecast_radio", "Livingroom") %} media_player.ca_livingroom
{% elif is_state("input_select.chromecast_radio", "Hall") %} media_player.ca_hall
{% elif is_state("input_select.chromecast_radio", "Bedroom") %} media_player.bed_room
{% elif is_state("input_select.chromecast_radio", "Bathroom") %} media_player.ca_bathroom
{% elif is_state("input_select.chromecast_radio", "Everywhere") %} media_player.home_group
{% endif %}
| 07:55:32 |
| Jeroen | I am puzzled by the > | 07:55:47 |
| Jeroen | Basically means, how do I do folded block scalar notation in nix | 08:39:01 |
 etu | The > in yaml becomes a multi line string that can be written on several lines but when parsed it will be read as a single line | 08:46:27 |
| etu | While the | character for multi line strings keeps the newlines | 08:46:44 |
| etu | So I would say that you don't have to recreate the > and all of the newlines in that block, you can split it up however you like in nix and nix will create a single line string in yaml but that should be fine. | 08:47:31 |
| Jeroen | Cool, i'll give it a go | 08:48:03 |
| Jeroen | seems to work to just put everything on a single line | 09:10:49 |
 @hexa:lossy.network | Can someone with more node2nix experience try and update zigbee2mqtt? I'm stuck. | 22:13:26 |
| Jeroen | +1 for zwavejs2mqtt:) | 23:02:08 |
| @hexa:lossy.network | that's a whole different wireless protocol though | 23:12:46 |
| @hexa:lossy.network | its really annoying, discovery isn't compatible anymore, so my light bulbs stopped working a few releases ago | 23:43:20 |
| @hexa:lossy.network | do I need to resort to some silly container setup?! | 23:43:33 |
 CRTified | In reply to @hexa:lossy.network
do I need to resort to some silly container setup?! I sadly had to :( it feels bad | 23:49:15 |
| @hexa:lossy.network | meh | 23:50:40 |
| @hexa:lossy.network | also this just appeared on lobste.rs https://myme.no/posts/2021-11-25-nixos-home-assistant.html | 23:50:50 |
| @hexa:lossy.network | headless HassOS on nixos with libvirt | 23:51:05 |
| 27 Nov 2021 |
| Jeroen | In antwoord op @hexa:lossy.network
that's a whole different wireless protocol though I know, but its also nodejs and i too failed to create a package for it. | 00:34:22 |
