| 26 Apr 2024 |
 @hexa:lossy.network | like this? | 21:00:22 |
| @hexa:lossy.network | 
Download image.png | 21:00:24 |
 Geoffrey Frogeye | Exactly :) | 21:01:52 |
| Geoffrey Frogeye | The problem is not so much hass complaining, but mostly that when I flip a switch it can take up to a minute for the corresponding event to trigger 😅 | 21:03:48 |
| Geoffrey Frogeye | In reply to @k900:0upti.me
So yeah, oauth2_proxy does not work with the mobile app This worked for me: https://github.com/home-assistant/android/issues/1438#issuecomment-1244106690 :) | 21:04:52 |
 K900 | Meh, I just ended up running LDAP auth | 21:05:45 |
| K900 | It's silly but it is what it is | 21:05:55 |
| @hexa:lossy.network | interesting | 21:09:29 |
| @hexa:lossy.network | I have never debugged this tbh | 21:09:35 |
| Geoffrey Frogeye | I have a workaround! If I change the "CoIoT peer" in the device config to use a different port (say 5684), and then I redirect that port to hass on the correct port using rinetd (see command below) then it works.
nix run nixpkgs#rinetd -- --foreground --conf-file <(echo '0.0.0.0 5684/udp 127.0.0.1 5683/udp')
| 21:40:08 |
| Geoffrey Frogeye | * I have a workaround! If I change the "CoIoT peer" in the device config to use a different port (say 5684), and then I redirect that port to hass on the correct port using rinetd (see command below) then it works.
nix run 'nixpkgs#rinetd' -- --foreground --conf-file <(echo '0.0.0.0 5684/udp 127.0.0.1 5683/udp')
| 21:40:19 |
| Geoffrey Frogeye | Why it was working under Docker was probably due to the port redirection done via docker-proxy. So it probably is an upstream bug, although now I'm wondering if all supported way of installing hass uses some kind of container, which would explain why they never caught the issue. I hope it's something that can be fixed in a Python library somewhere... | 21:43:24 |
|  Qyriad changed their display name from Qyriad to Qyriad (she/they). | 23:47:44 |
| Qyriad changed their display name from Qyriad (she/they) to Qyriad. | 23:47:57 |
| 27 Apr 2024 |
| Qyriad changed their display name from Qyriad to Qyriad . | 00:01:06 |
| Qyriad changed their display name from Qyriad to Qyriad. | 00:09:42 |
 presto8 | I had those push update failures too; I found a guide on Shelly's forum I think that said to use unicast messages instead of multicast. From the device's Shelly UI web interface, click Internet & Security, then Enable CoIOT should already be checked and put the Home Assistant IP address and port in there. Once I did this, all of my push update issues went away. | 00:22:38 |
 raboof | Are you using CoIoT for sending commands to the devices as well? I am too, but it gets complicated when he device is temporarily offline - I've been wondering whether I should switch to MQTT instead | 06:30:41 |
| Geoffrey Frogeye | In reply to @presto8:matrix.org
I had those push update failures too; I found a guide on Shelly's forum I think that said to use unicast messages instead of multicast. From the device's Shelly UI web interface, click Internet & Security, then Enable CoIOT should already be checked and put the Home Assistant IP address and port in there. Once I did this, all of my push update issues went away. I am already using unicast. Can I ask which way you're running Home Assistant? | 06:41:49 |
| Geoffrey Frogeye | In reply to @raboof:matrix.org
Are you using CoIoT for sending commands to the devices as well? I am too, but it gets complicated when he device is temporarily offline - I've been wondering whether I should switch to MQTT instead I'm not sure, this is abstracted by the aioshelly library. MQTT sounds like a good fallback plan if all else fails. | 06:44:37 |
| Geoffrey Frogeye | * Yes, ans I am using unicast already. Can I ask which way you're running Home Assistant? | 06:47:29 |
| Geoffrey Frogeye | In reply to @geoffrey:frogeye.fr
I have a workaround! If I change the "CoIoT peer" in the device config to use a different port (say 5684), and then I redirect that port to hass on the correct port using rinetd (see command below) then it works.
nix run 'nixpkgs#rinetd' -- --foreground --conf-file <(echo '0.0.0.0 5684/udp 127.0.0.1 5683/udp')
I tried to apply a variation of it: keep/reset the CoIoT peer port of the devices to 5683, switch rinetd ports (i.e. it listens to 5683 and forwards to 5684) and patch aioshelly to listen on 5684 instead... and despite now sharing the same configuration and having been rebooted only the device I did the test on works... I am properly puzzled. | 06:53:02 |
| Geoffrey Frogeye | * I tried to apply a variation of it (so I wouldn't have to change tens of devices configurations): keep/reset the CoIoT peer port of the devices to 5683, switch rinetd ports (i.e. it listens to 5683 and forwards to 5684) and patch aioshelly to listen on 5684 instead... and despite now sharing the same configuration and having been rebooted only the device I did the test on works... I am properly puzzled. | 06:53:53 |
| Geoffrey Frogeye | * I tried to apply a variation of it (so I wouldn't have to change tens of devices configurations): keep/reset the CoIoT peer port of the devices to 5683, switch rinetd ports (i.e. it listens to 5683 and forwards to 5684) and patch aioshelly to listen on 5684 instead... and despite now sharing the same configuration and having been rebooted only the device I tried the first workaround on works... I am properly puzzled. | 06:54:57 |
| Geoffrey Frogeye | In the end I changed every Shelly's CoIoT peer port to 5684... rebooted, and then back to 5683, rebooted, and now everything works fine without any port redirection shenanigans 🙃. I guess that maybe it was an issue with the devices caching something, although I also realized that some of those actually never stopped working. Oh well. Thanks for the suggestions all, I'll stay around to see if I can help some time :) | 10:09:57 |
| Geoffrey Frogeye | * In the end I changed every Shelly's CoIoT peer port to 5684... rebooted, and then back to 5683, rebooted, and now everything works fine without any port redirection shenanigans 🙃. I guess that maybe it was an issue with the devices caching something, although I also realized that I had more devices that actually never stopped working. Oh well. Thanks for the suggestions all, I'll stay around to see if I can help some time :) | 10:10:41 |
|  matthias.sh joined the room. | 15:37:11 |
 ibizaman | hello 👋 I couldn't find anything online so I came over here. Is there a way to add/configure integrations through the yaml file?
I'm thinking specifically about the wyoming integrations. | 18:12:49 |
| ibizaman | * hello 👋 I couldn't find anything online so I came over here. Is there a way to add/configure integrations through the yaml file?
I'm thinking specifically about the wyoming integrations. The idea would be to not need to fiddle with the UI. | 18:12:59 |
| ibizaman | did a grep in my own HA folder and found integrations live in .storage/core.config_entries | 18:14:56 |
