πŸ³οΈβ€πŸŒˆπŸŽƒπŸ‡§πŸ‡·LuanaπŸ‡§πŸ‡·πŸŽƒπŸ³οΈβ€πŸŒˆ

@luana@wetdry.world
781 Followers
1.1K Following
3.4K Posts

β€’ She/Her β€’ 21 β€’ πŸ‡§πŸ‡·, talk πŸ‡§πŸ‡·πŸ‡¬πŸ‡§ β€’ Valve & FOSS fangirl β€’ Mermaid πŸ§œβ€β™€οΈ β€’ Otherkin β€’ πŸ³οΈβ€πŸŒˆ Lesbian ⚒ ‒





Loves #swimming, #cooking, #mermaids and #gaming. #OpenSource everything. #Linux user.

https://luana.dev.br/

Searchable!

Migrated from @luana

Pronounsshe/her
Websitehttps://luana.dev.br
GitHubhttps://github.com/LuNeder
Linux DistroNixOS
Migrated fromhttps://tech.lgbt/@luana
Joined fedi onOct 26, 2022
When I think of ai art prompts i think of this
Good on you Australia. Good on you. #politics
finished a new theme switcher for my website :3

no it's absolutely not necessary for it to be this fancy but i have fun designing things
null surgery: a followup

a follow-up to the blog post about the surgery i had. it focuses on the recovery and my experience with my new (lack of) equipment, along with some of the more complicated feelings.

Hundreds of thousands of Computers won't be able to upgrade to Windows 11, but that shouldn't make them eWaste.

Kudos to the @kde team for this amazing initiative!

https://endof10.org/

End of 10

@paco Thanks!!

I opened the 5353 port as suggested on that forum and it did made the pairing stop failing immediately, but then it just stuck loading forever and eventually timedout.

I checked (netstat -ln) which ports Home Assistant was listening on and I opened the following ports too: 21064 8123 40000 47831 34041 1900 35698 39446 42277 59682. This made it work!! Now sure which port made it work bc I didn't realy have the patience to try them one by one lol.

networking.firewall.allowedTCPPorts = [
# HomeKit Bridge
21063 21064 5353
# Other ports listed as being used by HA (netstat -ln), at least 1 of these also needed by the Bridge
8123 40000 47831 34041 1900 35698 39446 42277 59682
];
networking.firewall.allowedUDPPorts = [
# HomeKit Bridge
21063 21064 5353
# Other ports listed as being used by HA (netstat -ln), at least 1 of these also needed by the Bridge
8123 40000 47831 34041 1900 35698 39446 42277 59682
];

I leaved a comment in that post in case anyone else finds that and needs the ports.

#HomeAssistant

HomeKit Device integration/discovery requires mDNS service access through firewall

Hey! Thanks!! I’ve been having issues configuring the HomeKit Bridge integration and turns out port 5353 is also needed for that. I’ll add here, in case anyone else finds this when looking for ports to open, that adding 5353 (21063 was already open since that’s the only port bridge docs mention) did make bridge pairing stop failing immediately, but then it just stayed loading forever and eventually timed out. I checked all ports Home Assistant was listening on (netstat -ln) and opened all o...

Home Assistant Community
HomeKit Device integration/discovery requires mDNS service access through firewall

TLDR: For HomeKit Device discovery, open your firewall for mDNS service (UDP port 5353). This should be noted in the HomeKit Device documentation as a prerequisite. Ignore all the ranting below, unless you really want to see everything I tried before figuring this out. I just installed an Ecobee Premium thermostat, and as I have no iOS devices I can’t do the Apple Homekit pairing/unpairing to somehow trigger the automatic HA pairing. I have searched and read just about every post on here about...

Home Assistant Community
mfm alt: a neocat wagging its foxtail

​​​​​​
Apparently many #HomeAssistant integrations have hidden configs that can only be edited via yaml, which kinda sucks but no biggie, but there’s actually no way for you to edit the yaml of an existing integration. You need to delete the integration and then configure it entirely via yaml from scratch. That really sucks.
All my friends are there!! :3