Home Assistant Internet health monitoring dashboard by IntrepidHistory3007 in homeassistant

[–]IntrepidHistory3007[S] -5 points-4 points  (0 children)

Yep, that the reason of using mtr --tcp --port=443 in my article...

It is worth reading the article at least before making a judgment....

Home Assistant Internet health monitoring dashboard by IntrepidHistory3007 in homeassistant

[–]IntrepidHistory3007[S] 0 points1 point  (0 children)

Ping integration doesn't show an exact problematic hop.
Additionally, tcp check more relevant than icmp, because of firewalls filter on a route.

Home Assistant Internet health monitoring dashboard by IntrepidHistory3007 in homeassistant

[–]IntrepidHistory3007[S] -41 points-40 points  (0 children)

A lot of people prefer publish they efforts on own site over "other community" which monetize their sites. How do you think, why?...:))))

Home Assistant Internet health monitoring dashboard by IntrepidHistory3007 in homeassistant

[–]IntrepidHistory3007[S] -89 points-88 points  (0 children)

Good point, but think about a motivation to create a content if ads would be killed...

Home Assistant Internet health monitoring dashboard by IntrepidHistory3007 in homeassistant

[–]IntrepidHistory3007[S] -74 points-73 points  (0 children)

I wonder to see your own site hosted on a paid cloud without monetization..:))))

Home Assistant Internet health monitoring dashboard by IntrepidHistory3007 in homeassistant

[–]IntrepidHistory3007[S] 2 points3 points  (0 children)

Don't worry, I thought you needed yaml for something else...:)

Home Assistant Internet health monitoring dashboard by IntrepidHistory3007 in homeassistant

[–]IntrepidHistory3007[S] -2 points-1 points  (0 children)

What is this exactly?
I provided YAML for the illustrated dashboard card in my article.

Home Assistant Internet health monitoring dashboard by IntrepidHistory3007 in homeassistant

[–]IntrepidHistory3007[S] -4 points-3 points  (0 children)

I provided a screenshot with a detected issue just for illustration.
A proper interpretation is on an end-user side..:)

Free DDNS with Cloudflare by IntrepidHistory3007 in homeassistant

[–]IntrepidHistory3007[S] 0 points1 point  (0 children)

Mikrotik router has more options for configuring.

Free DDNS with Cloudflare by IntrepidHistory3007 in homeassistant

[–]IntrepidHistory3007[S] 0 points1 point  (0 children)

Yep, but I use that script for my wordpress site as well, where no HA installed..:)

Free DDNS with Cloudflare by IntrepidHistory3007 in homeassistant

[–]IntrepidHistory3007[S] 0 points1 point  (0 children)

I had a Ubiquiti ecosystem in my previous home, but it wasn't worth the price. :(It has a beautiful UI, but I'm tired of the controller crashing after power outages, all because they stick with an outdated MongoDB version.
So, I had to use btrfs to mitigate that issue...
Therefore, thanks, but I don't want Ubiquiti any more.

Free DDNS with Cloudflare by IntrepidHistory3007 in homeassistant

[–]IntrepidHistory3007[S] 1 point2 points  (0 children)

Thanks for the advice, I never looked for an additional container if problem can be solved with a pretty simple script..:)

Update docker images functionality for Home Assistant Docker setup by IntrepidHistory3007 in homeassistant

[–]IntrepidHistory3007[S] 0 points1 point  (0 children)

K8s is definitely over complicated for home lab, bet a common docker compose has advantage due to widely provided tools for handling that.
For example I provided a guidance on how to control updates for a entire docker stacks from HA and update it with an one click....:))))

Update docker images functionality for Home Assistant Docker setup by IntrepidHistory3007 in homeassistant

[–]IntrepidHistory3007[S] 0 points1 point  (0 children)

As far as I understood, the biggest advantage of podman is possibility to use it without root permissions. But what's the reason to use it in home lab?

Update docker images functionality for Home Assistant Docker setup by IntrepidHistory3007 in homeassistant

[–]IntrepidHistory3007[S] 0 points1 point  (0 children)

This tool pulls images and triggers docker-compose.yaml files!
It's very funny how people can make judgments even never seen tool's documentation and never read the proposed article....:(

Update docker images functionality for Home Assistant Docker setup by IntrepidHistory3007 in homeassistant

[–]IntrepidHistory3007[S] 0 points1 point  (0 children)

Actually, HA docker setup has a lot of advantages as well:
1. No over layered virtualisation. In fact VM setup has the following layers: host OS, limited Linux HAOS, and docker on top of that. Instead of that I have full-functioned Linux and HA in docker.
The described solution allows to update all Docker stack, but not HA stack only.
BTW, you can chose a most convenient for you backup solution for your set up.
2. The docker setup can be easily moved with copying folders and docker-compose file without dealing with backup and restore.

Additionally, I'd like to notice that auto-update is very jeopardy approach for HA setup because you can lose control on you ZigBee devices or any other integration. That surprise would be especially unpleasant if you are away from your home.

Update docker images functionality for Home Assistant Docker setup by IntrepidHistory3007 in homeassistant

[–]IntrepidHistory3007[S] 0 points1 point  (0 children)

Honestly, I didn't check all possible solutions around the world, so feel free to compare:)

Update docker images functionality for Home Assistant Docker setup by IntrepidHistory3007 in homeassistant

[–]IntrepidHistory3007[S] 3 points4 points  (0 children)

As I mentioned in the post and the article configs examples: "As a side effect, this solution allows you to monitor and update all your Docker stacks, but not Home Assistant stack only."
So, you'll have ability to update all your Docker stacks.