starred/itsyhome-macos
1
0
Fork 0
mirror of https://github.com/nickustinov/itsyhome-macos.git synced 2026-04-26 04:15:56 +03:00
Code Issues 34 Projects Releases Packages Wiki Activity

[GH-ISSUE #69] On Mac every boot: "Failed to connect to Home Assistant: The Internet connection appears to be offline." #68

New issue
Closed
opened 2026-03-03 16:43:20 +03:00 by kerem · 8 comments
kerem commented 2026-03-03 16:43:20 +03:00
Owner
Copy link

Originally created by @moritz1000 on GitHub (Feb 22, 2026).
Original GitHub issue: https://github.com/nickustinov/itsyhome-macos/issues/69

Originally assigned to: @nickustinov on GitHub.

Itsyhome is set to launch at login.
On every Mac reboot I get this error:

Image

My problem with this error is that my internet connection and Home Assistant is for sure running/working.

After clicking Refresh in Itsyhome everything works as expected:

Image

The only reason I can think of is that Itsyhome is starting before my M4 Mac mini has connected to Wifi..?
But that would be also strange since the Mac connects to Wifi really fast.

Originally created by @moritz1000 on GitHub (Feb 22, 2026). Original GitHub issue: https://github.com/nickustinov/itsyhome-macos/issues/69 Originally assigned to: @nickustinov on GitHub. Itsyhome is set to launch at login. On every Mac reboot I get this error: <img width="302" height="264" alt="Image" src="https://github.com/user-attachments/assets/fb5b4e07-6084-414e-8b42-aea0b84cf29e" /> My problem with this error is that my internet connection and Home Assistant is _for sure_ running/working. After clicking Refresh in Itsyhome everything works as expected: <img width="324" height="190" alt="Image" src="https://github.com/user-attachments/assets/34ad1506-2fd2-4f3c-b862-e6b58784ca71" /> ___ The only reason I can think of is that Itsyhome is starting before my M4 Mac mini has connected to Wifi..? But that would be also strange since the Mac connects to Wifi really fast.
kerem closed this issue 2026-03-03 16:43:21 +03:00
kerem commented 2026-03-03 16:43:21 +03:00
Author
Owner
Copy link

@nickustinov commented on GitHub (Feb 22, 2026):

Thanks for reporting! Will fix this asap.

<!-- gh-comment-id:3940970071 --> @nickustinov commented on GitHub (Feb 22, 2026): Thanks for reporting! Will fix this asap.
kerem commented 2026-03-03 16:43:21 +03:00
Author
Owner
Copy link

@Cyb3rPhantom commented on GitHub (Feb 22, 2026):

I'm having a similar problem. Mine keeps telling me that the internet connection is offline but hitting Refresh doesn't fix it. My HA Is up and running, i can reach it as well as ping/curl to it with zero issues, but itsyhome will not connect to it. I've deleted the long live token and re-created it but still nothing. It was working fine when i first installed it a few days ago.

<!-- gh-comment-id:3941175406 --> @Cyb3rPhantom commented on GitHub (Feb 22, 2026): I'm having a similar problem. Mine keeps telling me that the internet connection is offline but hitting Refresh doesn't fix it. My HA Is up and running, i can reach it as well as ping/curl to it with zero issues, but itsyhome will not connect to it. I've deleted the long live token and re-created it but still nothing. It was working fine when i first installed it a few days ago.
kerem commented 2026-03-03 16:43:22 +03:00
Author
Owner
Copy link

@nickustinov commented on GitHub (Feb 22, 2026):

Thanks for the reports, both of you!

To make sure I fix the right thing, could you each grab some logs?

  1. Open Console.app
  2. In the search bar, set the filter to Process = Itsyhome (click the search field, choose "Process" from the dropdown, type Itsyhome) – this avoids noise from other system daemons
  3. Reproduce the issue (reboot, or try clicking Refresh)
  4. Look for any lines containing "Failed to connect" or "error" and paste them here

@moritz1000 – are you on Wi-Fi or wired ethernet? Wi-Fi tends to take a few extra seconds to authenticate after login, which could explain the timing.

@Cyb3rPhantom – since Refresh doesn't fix it either, does fully quitting Itsyhome (right-click the menu bar icon → Quit) and relaunching it help? That would tell me whether it's a startup race or something else.

The logs will show the exact error code and help me pin down whether these are the same bug or two separate issues.

<!-- gh-comment-id:3941358140 --> @nickustinov commented on GitHub (Feb 22, 2026): Thanks for the reports, both of you! To make sure I fix the right thing, could you each grab some logs? 1. Open **Console.app** 2. In the search bar, set the filter to **Process = Itsyhome** (click the search field, choose "Process" from the dropdown, type `Itsyhome`) – this avoids noise from other system daemons 3. Reproduce the issue (reboot, or try clicking Refresh) 4. Look for any lines containing "Failed to connect" or "error" and paste them here **@moritz1000** – are you on Wi-Fi or wired ethernet? Wi-Fi tends to take a few extra seconds to authenticate after login, which could explain the timing. **@Cyb3rPhantom** – since Refresh doesn't fix it either, does fully quitting Itsyhome (right-click the menu bar icon → Quit) and relaunching it help? That would tell me whether it's a startup race or something else. The logs will show the exact error code and help me pin down whether these are the same bug or two separate issues.
kerem commented 2026-03-03 16:43:22 +03:00
Author
Owner
Copy link

@Cyb3rPhantom commented on GitHub (Feb 22, 2026):

@nickustinov well oddly enough now it appears to be working fine. I'm not sure what the issue was but I started noticing it last night but figured I'd look more into today and this morning I saw this post. I did try quitting the app and even rebooting my computer last night and this morning but it still didn't force it to work. I stepped away after commenting and now as I was about to try to capture the logs everything is working again.

<!-- gh-comment-id:3941375430 --> @Cyb3rPhantom commented on GitHub (Feb 22, 2026): @nickustinov well oddly enough now it appears to be working fine. I'm not sure what the issue was but I started noticing it last night but figured I'd look more into today and this morning I saw this post. I did try quitting the app and even rebooting my computer last night and this morning but it still didn't force it to work. I stepped away after commenting and now as I was about to try to capture the logs everything is working again.
kerem commented 2026-03-03 16:43:22 +03:00
Author
Owner
Copy link

@moritz1000 commented on GitHub (Feb 22, 2026):

To make sure I fix the right thing, could you each grab some logs?

1. Open **Console.app**

2. In the search bar, set the filter to **Process = Itsyhome** (click the search field, choose "Process" from the dropdown, type `Itsyhome`) – this avoids noise from other system daemons

3. Reproduce the issue (reboot, or try clicking Refresh)

4. Look for any lines containing "Failed to connect" or "error" and paste them here

@moritz1000 – are you on Wi-Fi or wired ethernet? Wi-Fi tends to take a few extra seconds to authenticate after login, which could explain the timing.

Hey @nickustinov. As I wrote in my initial bug report I am on Wi-Fi.
I am not able to follow your steps to acquire logs since... well the issue happens immediately after logging in when Itsyhome launches at login. At this point of time Console.app is not open yet.

btw I don't get the error if I turn off the Itsyhome autolaunch setting and manually open the program after logging in.

<!-- gh-comment-id:3941488694 --> @moritz1000 commented on GitHub (Feb 22, 2026): > To make sure I fix the right thing, could you each grab some logs? > > 1. Open **Console.app** > > 2. In the search bar, set the filter to **Process = Itsyhome** (click the search field, choose "Process" from the dropdown, type `Itsyhome`) – this avoids noise from other system daemons > > 3. Reproduce the issue (reboot, or try clicking Refresh) > > 4. Look for any lines containing "Failed to connect" or "error" and paste them here > > > **[@moritz1000](https://github.com/moritz1000)** – are you on Wi-Fi or wired ethernet? Wi-Fi tends to take a few extra seconds to authenticate after login, which could explain the timing. Hey @nickustinov. As I wrote in my initial bug report I am on Wi-Fi. I am not able to follow your steps to acquire logs since... well the issue happens immediately after logging in when Itsyhome launches at login. At this point of time Console.app is not open yet. btw I don't get the error if I turn off the Itsyhome autolaunch setting and manually open the program after logging in.
kerem commented 2026-03-03 16:43:22 +03:00
Author
Owner
Copy link

@Cyb3rPhantom commented on GitHub (Feb 23, 2026):

Alright, so mine started having the same issue again and upon looking at the logs I was able to find the issue. It kept saying "unsatisfied (Local network prohibited), interface: en7, ipv4" anytime there was a connection attempt. I had to go into Settings, Privacy & Security and enable itsyhome under Local Network (which i thought was already done). Once that was checked and I tried connecting again it worked with no issues. Thank you!

<!-- gh-comment-id:3942062330 --> @Cyb3rPhantom commented on GitHub (Feb 23, 2026): Alright, so mine started having the same issue again and upon looking at the logs I was able to find the issue. It kept saying "unsatisfied (Local network prohibited), interface: en7, ipv4" anytime there was a connection attempt. I had to go into Settings, Privacy & Security and enable itsyhome under Local Network (which i thought was already done). Once that was checked and I tried connecting again it worked with no issues. Thank you!
kerem commented 2026-03-03 16:43:22 +03:00
Author
Owner
Copy link

@nickustinov commented on GitHub (Feb 24, 2026):

Please try build 235 from here https://testflight.apple.com/join/aMweYMF5

<!-- gh-comment-id:3953260219 --> @nickustinov commented on GitHub (Feb 24, 2026): Please try build 235 from here https://testflight.apple.com/join/aMweYMF5
kerem commented 2026-03-03 16:43:22 +03:00
Author
Owner
Copy link

@moritz1000 commented on GitHub (Feb 24, 2026):

Please try build 235 from here testflight.apple.com/join/aMweYMF5

Seems to work for me :).
I installed the update via testflight, restarted my Mac and no more pop-up after logging in.

<!-- gh-comment-id:3953559098 --> @moritz1000 commented on GitHub (Feb 24, 2026): > Please try build 235 from here [testflight.apple.com/join/aMweYMF5](https://testflight.apple.com/join/aMweYMF5) Seems to work for me :). I installed the update via testflight, restarted my Mac and no more pop-up after logging in.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
v1.3.1
1.1.0
v1.0.0
Labels
Clear labels   
bug

   
enhancement

   
pending release

   
pull-request

Mirrored from GitHub Pull Request

  
wip

   
wontfix
No labels
bug
enhancement
pending release
pull-request
wip
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/itsyhome-macos#68
No description provided.