After configuring a Fritz Box as IP Client on a main modem/router I have problems with these addOns.
In the Samba registry I find this:
*****
idmap range not specified for domain '*'
idmap range not specified for domain '*'
idmap range not specified for domain '*'
idmap range not specified for domain '*'
idmap range not specified for domain '*'
idmap range not specified for domain '*'
idmap range not specified for domain '*'
idmap range not specified for domain '*'
process_local_master_announce: Server ECHOLIFE_WAP at IP 192.168.1.254 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election.
*****
Samba name server HOMEASSISTANT has stopped being a local master browser for workgroup WORKGROUP on subnet 192.168.1.69
*****
*****
Samba name server HOMEASSISTANT is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.69
*****
idmap range not specified for domain '*'
idmap range not specified for domain '*'
idmap range not specified for domain '*'
process_local_master_announce: Server ECHOLIFE_WAP at IP 192.168.1.254 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election.
*****
Samba name server HOMEASSISTANT has stopped being a local master browser for workgroup WORKGROUP on subnet 192.168.1.69
*****
*****
Samba name server HOMEASSISTANT is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.69
*****
process_local_master_announce: Server ECHOLIFE_WAP at IP 192.168.1.254 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election.
*****
Samba name server HOMEASSISTANT has stopped being a local master browser for workgroup WORKGROUP on subnet 192.168.1.69
*****
*****
Samba name server HOMEASSISTANT is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.69
*****
process_local_master_announce: Server ECHOLIFE_WAP at IP 192.168.1.254 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election.
*****
Samba name server HOMEASSISTANT has stopped being a local master browser for workgroup WORKGROUP on subnet 192.168.1.69
*****
*****
Samba name server HOMEASSISTANT is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.69
*****
process_local_master_announce: Server ECHOLIFE_WAP at IP 192.168.1.254 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election.
*****
Samba name server HOMEASSISTANT has stopped being a local master browser for workgroup WORKGROUP on subnet 192.168.1.69
*****
*****
Samba name server HOMEASSISTANT is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.69
*****
process_local_master_announce: Server ECHOLIFE_WAP at IP 192.168.1.254 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election.
*****
Samba name server HOMEASSISTANT has stopped being a local master browser for workgroup WORKGROUP on subnet 192.168.1.69
*****
*****
Samba name server HOMEASSISTANT is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.69
*****
process_local_master_announce: Server ECHOLIFE_WAP at IP 192.168.1.254 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election.
*****
Samba name server HOMEASSISTANT has stopped being a local master browser for workgroup WORKGROUP on subnet 192.168.1.69
*****
*****
Samba name server HOMEASSISTANT is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.69
*****
process_local_master_announce: Server ECHOLIFE_WAP at IP 192.168.1.254 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election.
*****
Samba name server HOMEASSISTANT has stopped being a local master browser for workgroup WORKGROUP on subnet 192.168.1.69
*****
*****
Samba name server HOMEASSISTANT is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.69
*****
The Google Backup registry:
02-03 16:26:42 INFO Syncing Backups
02-03 16:28:03 ERROR Unable to connect to www.googleapis.com
02-03 16:28:03 INFO I'll try again in 21 minutes, 20 seconds
02-03 16:49:23 INFO Syncing Backups
02-03 16:50:34 ERROR Unable to connect to www.googleapis.com
02-03 16:50:34 INFO I'll try again in 42 minutes, 40 seconds
02-03 17:21:01 WARNING Timed out communicating with token2.habackup.io, trying alternate server(s)...
02-03 17:21:12 WARNING Timed out communicating with token1.habackup.io, trying alternate server(s)...
02-03 17:21:23 WARNING Timed out communicating with habackup.io, trying alternate server(s)...
02-03 17:21:23 ERROR Unable to refresh credentials with Google Drive
02-03 17:21:23 ERROR Couldn't refresh Google Drive credentials because: Timed out communicating with habackup.io
02-03 17:21:23 INFO I'll try again in 1 hours, 25 minutes, 20 seconds