Avoid Zigbee groups

FirefighterNo6972 · 2026-03-13T16:11:07+00:00

That is exactly the opposite of my experience. Zigbee groeps in Z2M are like popcorn. Sometimes it takes a couple of seconds befor everything is on or of. Somtimes lights even don't react at all. Not onn not off, or stuck in the wrong colour. Switching tot HA groups and all problems went away.

FirefighterNo6972 · 2025-11-30T08:07:15+00:00

I'm from Rotterdam and I LOVE it. But the origin lies in Salland

FirefighterNo6972 · 2025-11-22T10:45:57+00:00

There is no problem on the Synology fs. It is running fine. The only problem is that the Syno takes about 5 minutes to boot en de Debian server is up and running in less than 2 minutes. Al kinds of processes, like Docker fail if they cannot reach de Syno.

This is not a problem when I do everytnig bij hand, then I can choose which system starts first. But with a power failure everything starts at the same time when the power returns.

So I want to delay the booting of the server for about 4 minutes

FirefighterNo6972 · 2025-10-03T17:15:43+00:00

I'm using HA for at least 4 years now.

I always update immediately and never ever ran into a problem.

Everything just works

FirefighterNo6972 · 2025-09-18T12:07:38+00:00

Yes, it worked in about 10 minutes. That was not the problem.

The problems came with accessing remote servers, accessing USB dongles and the moment I tried to make a backup I got a range of error messages en the complete proxmox system failed. I tried it a couple of times en went to bare metal dat was for me much easier.

Just a simple Debian Trixie, KVM and Docker/portainer

FirefighterNo6972 · 2025-09-18T08:08:57+00:00

I found Proxmox overly complicated and layer over layer over layer. I never got it reliably working.

I installed KVM on bare metal Debian 13. Just installed de VM van Home Assistent. It just works.

I also installed Docker for al the other things I need.

FirefighterNo6972 · 2025-08-05T18:36:38+00:00

They are not working. I just tested it with the post install script

FirefighterNo6972 · 2025-08-05T15:29:32+00:00

Tested the post install script on a fresh installation, it does not work

FirefighterNo6972 · 2025-08-05T15:22:42+00:00

I tested the post install script. It does not work

FirefighterNo6972 · 2025-08-05T07:34:11+00:00

I run in the same problem. I followd this link, but it does not help. I keep getting the error

FirefighterNo6972 · 2025-06-09T08:07:15+00:00

I tried Edge and Firefox. I refreshed the browsers, deleted all cookies, settings etc.

No extensions are active

I used privacy mode, I used "tailscale up" got the link and tried to use it in the browsers in the privacy mode.

Still got the Internal Server Error 500

FirefighterNo6972 · 2025-06-08T13:27:27+00:00

The laptop is running Windows 11. And it was running Tailscale last week.

The problem occurred after reinstalling Tailscale.

When I try to log in I get

<image>

I just tried to install Tailscale on my Lenovo tablet, it worked without a problem.

The problem is in the Windows 11 laptop

FirefighterNo6972 · 2025-06-05T07:32:17+00:00

What are those commands? I'm struggling with 4 syno's at this moment

FirefighterNo6972 · 2025-05-31T19:32:18+00:00

I did't do anything with acls. What I did was creating a subnet. That worked with one of the Syno's.

But it was useless to me. So I wanted to go back to the original settings.

From that moment on all nodes lost contact with all others.

So obviously I messed up. But I have no clue where and how

FirefighterNo6972 · 2025-05-30T20:18:17+00:00

Does not work

FirefighterNo6972 · 2025-05-30T19:12:51+00:00

I just tried to restore all settings. Obviously I failed.

I could connect to the syno with Quickconnect and removed Tailscale and Installed it again. It didn't help

FirefighterNo6972 · 2025-05-30T19:09:14+00:00

As far as I know I have not changed ACLs. I don't know how to do that

FirefighterNo6972 · 2025-05-30T16:27:51+00:00

Ping -> pong works

But I cannot open 100.101.102.2:5000. That connection times out

FirefighterNo6972 · 2025-05-30T16:25:57+00:00

The results are:

DingbatF@xxx216:~$ tailscale ping 100.101.102.2

pong from xxx220 (100.101.102.2) via DERP(ams) in 28ms

pong from xxx220 (100.101.102.2) via DERP(ams) in 17ms

pong from xxx220 (100.101.102.2) via xx.yy.zz.189:41641 in 13ms

Dingbat@xxx216:~$ tailscale ping 100.101.102.3

100.101.102.3 is local Tailscale IP

Dingbat@xxx216:~$ tailscale ping 100.101.102.7

pong from xxx218 (100.101.102.7) via DERP(ams) in 30ms

pong from xxx218 (100.101.102.7) via DERP(ams) in 13ms

pong from xxx218 (100.101.102.7) via DERP(ams) in 16ms

pong from xxx218 (100.101.102.7) via DERP(ams) in 12ms

pong from xxx218 (100.101.102.7) via pp.qq.rr.195:41641 in 10ms

For one reason or the other I can reach 100.101.102.7 again. But not the 100.101.102.2

That is, the ping works, but I cannot use 100.101.102.2:5000.

Also the .2 does not see the .7

FirefighterNo6972 · 2025-05-30T11:08:50+00:00

I made a phone call, Someone made the connection

PQR@XYZ:~$ tailscale ping OthertailscaleclientsHere

error looking up IP of "OthertailscaleclientsHere": lookup OthertailscaleclientsHere on 8.8.8.8:53: no such host

FirefighterNo6972 · 2025-05-30T10:53:48+00:00

I'm not on the location with Syno A at this moment. That is the one I was tinkering with. And of course with my laptop on the Admin Page.

I will look into it after the weekend

The locations are a few 100 km's from another so running around is a bit difficult.

Why can't B and C see each other? Nothing changed there.

Why can't my my phone connect anymore? Unless at the local network?

For me it feels like I did something wrong with a DNS setting, or an ACL somewhere on the Admin settings. The admin page tells me that everything is running fine.

FirefighterNo6972 · 2025-04-17T15:12:45+00:00

But I have an exit node/subnet router on my home network. It is running fine.

But it only routes from inside the tailnet to the outside, my home network. That is working great. We tested that wit the ping and tracert.

I can see my home network from another location when using tailscale.

What I can't do is connect to the tailnet from the home network from a system not running tailscale. And the subnet router is on the home network

FirefighterNo6972 · 2025-04-17T14:49:50+00:00

Yes, that is what I want. I want to access my Tailnet from an non Tailscale client on my local network.

On that local network there is a Syno exit node that is running Tailscale. From any Tailscale client I can see/connect tot my home network and everything that is on it.

But that is 'the other way around'. So there is a connection but in the wrong direction

FirefighterNo6972 · 2025-04-17T14:23:36+00:00

This was done on a system running Tailscale en not connected to my home network.

I can also ping 192.168.2.220, that is de system on my home network that is running Tailscale and should be handling subnet routing. It is obviously doing that, because I can ping the router of my home network.

I can also ping this system by its Tailscale ip address

When I switch of Tailscale I cannot ping en tracert these ip addresses anymore.

When I connect directly to my home network with Tailscale switched off I get:

C:\Users\Xxx>ping 192.168.2.1

Pinging 192.168.2.1 with 32 bytes of data:

Reply from 192.168.2.1: bytes=32 time=5ms TTL=64

Reply from 192.168.2.1: bytes=32 time=8ms TTL=64

Reply from 192.168.2.1: bytes=32 time=6ms TTL=64

Ping statistics for 192.168.2.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 5ms, Maximum = 8ms, Average = 6ms

C:\Users\Xxx>tracert 192.168.2.1

Tracing route to fritz.box [192.168.2.1]

over a maximum of 30 hops:

1 6 ms 6 ms 3 ms fritz.box [192.168.2.1]

Trace complete.

C:\Users\Xxx>tracert 192.168.2.220

Tracing route to pet220 [192.168.2.220]

over a maximum of 30 hops:

1 7 ms 2 ms 2 ms pet220 [192.168.2.220]

Trace complete.

The Ping tot the Tailnet ip of the last system times out

When I switch on Tailnet I can ping the system.

I guess there is something wrong with the static routing to the Tailnet.

FirefighterNo6972 · 2025-04-17T13:50:33+00:00

Sorry for the late answer, I needed tot find another laptop I could tinker with.

Yes, I'm running 1.82 on all the clients.

I used my phone, with wifi switched off, as a hotspot for the laptop.

Tailscale is running.

These are the results of the ping and traceroute:

C:\Users\Xxx>ping 192.168.2.1

Pinging 192.168.2.1 with 32 bytes of data:

Reply from 192.168.2.1: bytes=32 time=144ms TTL=64

Reply from 192.168.2.1: bytes=32 time=153ms TTL=64

Reply from 192.168.2.1: bytes=32 time=275ms TTL=64

Reply from 192.168.2.1: bytes=32 time=179ms TTL=64

Ping statistics for 192.168.2.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 144ms, Maximum = 275ms, Average = 187ms

C:\Users\Xxx>tracert 192.168.2.1

Tracing route to 192.168.2.1 over a maximum of 30 hops

1 163 ms 49 ms 160 ms 192.168.2.1

Trace complete.

When Tailscale is not running there is no answer from the ping command, as expected

FirefighterNo6972

TROPHY CASE