Mein SLZB06 spinnt

Allgemein & News
22

Hast du die „Companion App“ drauf?
Und wenn ja findet die deinen Home Assistant?

23

Ja, ich habe die App auf dem iphone und ipad. Keine Verbindung möglich

24

Was steht den so im Proxmox → PVE->System->Systemlog ?

25

Status

running
HA-Status

keine
Knoten

pve
CPU-Auslastung

3.35% der 4 CPU(s)
Speicherverbrauch

21.57% (3.45 GiB von 16.00 GiB)
Host Arbeitsspeicherverbrauch

3.93 GiB
Bootdisk-Größe

182.00 GiB
IPs
192.178.168.32
fe80::d6f7:5d12:7622:5f11

26 
Nov 24 23:11:01 pve pvedaemon[1207]: <root@pam> starting task UPID:pve:000263A8:002F5A77:6924D7F5:qmrestore:105:root@pam:
Nov 24 23:11:43 pve pvedaemon[1207]: <root@pam> successful auth for user 'root@pam'
Nov 24 23:11:53 pve pvedaemon[1207]: <root@pam> end task UPID:pve:000263A8:002F5A77:6924D7F5:qmrestore:105:root@pam: OK
Nov 24 23:12:12 pve pvedaemon[1206]: <root@pam> starting task UPID:pve:0002651C:002F7641:6924D83C:imgdel:105@PBS:root@pam:
Nov 24 23:12:12 pve pvedaemon[1206]: <root@pam> end task UPID:pve:0002651C:002F7641:6924D83C:imgdel:105@PBS:root@pam: OK
Nov 24 23:12:17 pve pvedaemon[157003]: start VM 105: UPID:pve:0002654B:002F784B:6924D841:qmstart:105:root@pam:
Nov 24 23:12:17 pve pvedaemon[1205]: <root@pam> starting task UPID:pve:0002654B:002F784B:6924D841:qmstart:105:root@pam:
Nov 24 23:12:18 pve systemd[1]: Started 105.scope.
Nov 24 23:12:18 pve kernel: tap105i0: entered promiscuous mode
Nov 24 23:12:18 pve kernel: vmbr0: port 3(fwpr105p0) entered blocking state
Nov 24 23:12:18 pve kernel: vmbr0: port 3(fwpr105p0) entered disabled state
Nov 24 23:12:18 pve kernel: fwpr105p0: entered allmulticast mode
Nov 24 23:12:18 pve kernel: fwpr105p0: entered promiscuous mode
Nov 24 23:12:18 pve kernel: vmbr0: port 3(fwpr105p0) entered blocking state
Nov 24 23:12:18 pve kernel: vmbr0: port 3(fwpr105p0) entered forwarding state
Nov 24 23:12:19 pve kernel: fwbr105i0: port 1(fwln105i0) entered blocking state
Nov 24 23:12:19 pve kernel: fwbr105i0: port 1(fwln105i0) entered disabled state
Nov 24 23:12:19 pve kernel: fwln105i0: entered allmulticast mode
Nov 24 23:12:19 pve kernel: fwln105i0: entered promiscuous mode
Nov 24 23:12:19 pve kernel: fwbr105i0: port 1(fwln105i0) entered blocking state
Nov 24 23:12:19 pve kernel: fwbr105i0: port 1(fwln105i0) entered forwarding state
Nov 24 23:12:19 pve kernel: fwbr105i0: port 2(tap105i0) entered blocking state
Nov 24 23:12:19 pve kernel: fwbr105i0: port 2(tap105i0) entered disabled state
Nov 24 23:12:19 pve kernel: tap105i0: entered allmulticast mode
Nov 24 23:12:19 pve kernel: fwbr105i0: port 2(tap105i0) entered blocking state
Nov 24 23:12:19 pve kernel: fwbr105i0: port 2(tap105i0) entered forwarding state
Nov 24 23:12:19 pve pvedaemon[157003]: VM 105 started with PID 157016.
Nov 24 23:12:19 pve pvedaemon[1205]: <root@pam> end task UPID:pve:0002654B:002F784B:6924D841:qmstart:105:root@pam: OK
Nov 24 23:12:23 pve pvedaemon[1205]: VM 105 qga command failed - VM 105 qga command 'guest-ping' failed - got timeout
Nov 24 23:17:01 pve CRON[158499]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Nov 24 23:17:01 pve CRON[158501]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Nov 24 23:17:01 pve CRON[158499]: pam_unix(cron:session): session closed for user root
27

??? ist das aktuell

Der Rest schaut ok aus!

28 
Nov 24 23:17:01 pve CRON[158499]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Nov 24 23:17:01 pve CRON[158501]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Nov 24 23:17:01 pve CRON[158499]: pam_unix(cron:session): session closed for user root
Nov 25 00:00:07 pve systemd[1]: Starting dpkg-db-backup.service - Daily dpkg database backup service...
Nov 25 00:00:07 pve systemd[1]: dpkg-db-backup.service: Deactivated successfully.
Nov 25 00:00:07 pve systemd[1]: Finished dpkg-db-backup.service - Daily dpkg database backup service.
Nov 25 00:17:01 pve CRON[176783]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Nov 25 00:17:01 pve CRON[176785]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Nov 25 00:17:01 pve CRON[176783]: pam_unix(cron:session): session closed for user root
Nov 25 00:28:07 pve systemd[1]: Starting logrotate.service - Rotate log files...
Nov 25 00:28:07 pve systemd[1]: Reloading pveproxy.service - PVE API Proxy Server...
Nov 25 00:28:08 pve pveproxy[180249]: send HUP to 1216
Nov 25 00:28:08 pve pveproxy[1216]: received signal HUP
Nov 25 00:28:08 pve pveproxy[1216]: server closing
Nov 25 00:28:08 pve pveproxy[1216]: server shutdown (restart)
Nov 25 00:28:08 pve systemd[1]: Reloaded pveproxy.service - PVE API Proxy Server.
Nov 25 00:28:08 pve systemd[1]: Reloading spiceproxy.service - PVE SPICE Proxy Server...
Nov 25 00:28:09 pve spiceproxy[180253]: send HUP to 1225
Nov 25 00:28:09 pve spiceproxy[1225]: received signal HUP
Nov 25 00:28:09 pve spiceproxy[1225]: server closing
Nov 25 00:28:09 pve spiceproxy[1225]: server shutdown (restart)
Nov 25 00:28:09 pve systemd[1]: Reloaded spiceproxy.service - PVE SPICE Proxy Server.
Nov 25 00:28:09 pve pvefw-logger[705]: received terminate request (signal)
Nov 25 00:28:09 pve pvefw-logger[705]: stopping pvefw logger
Nov 25 00:28:09 pve systemd[1]: Stopping pvefw-logger.service - Proxmox VE firewall logger...
Nov 25 00:28:09 pve systemd[1]: pvefw-logger.service: Deactivated successfully.
Nov 25 00:28:09 pve systemd[1]: Stopped pvefw-logger.service - Proxmox VE firewall logger.
Nov 25 00:28:09 pve systemd[1]: pvefw-logger.service: Consumed 4.168s CPU time, 2.6M memory peak.
Nov 25 00:28:09 pve systemd[1]: Starting pvefw-logger.service - Proxmox VE firewall logger...
Nov 25 00:28:09 pve pvefw-logger[180266]: starting pvefw logger
Nov 25 00:28:09 pve systemd[1]: Started pvefw-logger.service - Proxmox VE firewall logger.
Nov 25 00:28:09 pve systemd[1]: logrotate.service: Deactivated successfully.
Nov 25 00:28:09 pve systemd[1]: Finished logrotate.service - Rotate log files.
Nov 25 00:28:09 pve spiceproxy[1225]: restarting server
Nov 25 00:28:09 pve spiceproxy[1225]: starting 1 worker(s)
Nov 25 00:28:09 pve spiceproxy[1225]: worker 180272 started
Nov 25 00:28:09 pve pveproxy[1216]: restarting server
Nov 25 00:28:09 pve pveproxy[1216]: starting 3 worker(s)
Nov 25 00:28:09 pve pveproxy[1216]: worker 180273 started
Nov 25 00:28:09 pve pveproxy[1216]: worker 180274 started
Nov 25 00:28:09 pve pveproxy[1216]: worker 180275 started
Nov 25 00:28:14 pve spiceproxy[1226]: worker exit
Nov 25 00:28:14 pve spiceproxy[1225]: worker 1226 finished
Nov 25 00:28:14 pve pveproxy[153269]: worker exit
Nov 25 00:28:14 pve pveproxy[154942]: worker exit
Nov 25 00:28:14 pve pveproxy[153064]: worker exit
Nov 25 00:28:14 pve pveproxy[1216]: worker 153269 finished
Nov 25 00:28:14 pve pveproxy[1216]: worker 154942 finished
Nov 25 00:28:14 pve pveproxy[1216]: worker 153064 finished
Nov 25 00:33:55 pve systemd[1]: Starting apt-daily.service - Daily apt download activities...
Nov 25 00:33:55 pve systemd[1]: apt-daily.service: Deactivated successfully.
Nov 25 00:33:55 pve systemd[1]: Finished apt-daily.service - Daily apt download activities.
Nov 25 01:17:01 pve CRON[195389]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Nov 25 01:17:01 pve CRON[195391]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Nov 25 01:17:01 pve CRON[195389]: pam_unix(cron:session): session closed for user root
Nov 25 01:39:39 pve kernel: perf: interrupt took too long (3210 > 3130), lowering kernel.perf_event_max_sample_rate to 62000
Nov 25 02:17:01 pve CRON[214073]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Nov 25 02:17:01 pve CRON[214075]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Nov 25 02:17:01 pve CRON[214073]: pam_unix(cron:session): session closed for user root
Nov 25 03:05:55 pve systemd[1]: Starting man-db.service - Daily man-db regeneration...
Nov 25 03:05:55 pve systemd[1]: man-db.service: Deactivated successfully.
Nov 25 03:05:55 pve systemd[1]: Finished man-db.service - Daily man-db regeneration.
Nov 25 03:10:01 pve CRON[230472]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Nov 25 03:10:01 pve CRON[230474]: (root) CMD (test -e /run/systemd/system || SERVICE_MODE=1 /sbin/e2scrub_all -A -r)
Nov 25 03:10:01 pve CRON[230472]: pam_unix(cron:session): session closed for user root
Nov 25 03:17:01 pve CRON[232661]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Nov 25 03:17:01 pve CRON[232663]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Nov 25 03:17:01 pve CRON[232661]: pam_unix(cron:session): session closed for user root
Nov 25 04:17:01 pve CRON[251328]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Nov 25 04:17:01 pve CRON[251330]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Nov 25 04:17:01 pve CRON[251328]: pam_unix(cron:session): session closed for user root
Nov 25 05:17:01 pve CRON[270047]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Nov 25 05:17:01 pve CRON[270049]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Nov 25 05:17:01 pve CRON[270047]: pam_unix(cron:session): session closed for user root
Nov 25 05:36:55 pve systemd[1]: Starting pve-daily-update.service - Daily PVE download activities...
Nov 25 05:36:56 pve pveupdate[276221]: <root@pam> starting task UPID:pve:00043713:0052AF8A:69253268:aptupdate::root@pam:
Nov 25 05:36:57 pve pveupdate[276243]: update new package list: /var/lib/pve-manager/pkgupdates
Nov 25 05:37:00 pve pveupdate[276221]: <root@pam> end task UPID:pve:00043713:0052AF8A:69253268:aptupdate::root@pam: OK
Nov 25 05:37:00 pve systemd[1]: pve-daily-update.service: Deactivated successfully.
Nov 25 05:37:00 pve systemd[1]: Finished pve-daily-update.service - Daily PVE download activities.
Nov 25 05:37:00 pve systemd[1]: pve-daily-update.service: Consumed 3.739s CPU time, 329.3M memory peak.
Nov 25 06:17:01 pve CRON[288339]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Nov 25 06:17:01 pve CRON[288341]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Nov 25 06:17:01 pve CRON[288339]: pam_unix(cron:session): session closed for user root
Nov 25 06:25:01 pve CRON[290764]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Nov 25 06:25:01 pve CRON[290766]: (root) CMD (test -x /usr/sbin/anacron || { cd / && run-parts --report /etc/cron.daily; })
Nov 25 06:25:01 pve CRON[290764]: pam_unix(cron:session): session closed for user root
Nov 25 06:33:07 pve systemd[1]: Starting apt-daily-upgrade.service - Daily apt upgrade and clean activities...
Nov 25 06:33:07 pve systemd[1]: apt-daily-upgrade.service: Deactivated successfully.
Nov 25 06:33:07 pve systemd[1]: Finished apt-daily-upgrade.service - Daily apt upgrade and clean activities.
Nov 25 07:17:01 pve CRON[306477]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Nov 25 07:17:01 pve CRON[306479]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Nov 25 07:17:01 pve CRON[306477]: pam_unix(cron:session): session closed for user root
Nov 25 08:17:01 pve CRON[324804]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Nov 25 08:17:01 pve CRON[324806]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Nov 25 08:17:01 pve CRON[324804]: pam_unix(cron:session): session closed for user root
Nov 25 09:17:01 pve CRON[342770]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Nov 25 09:17:01 pve CRON[342772]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Nov 25 09:17:01 pve CRON[342770]: pam_unix(cron:session): session closed for user root
Nov 25 10:17:01 pve CRON[361770]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Nov 25 10:17:01 pve CRON[361772]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Nov 25 10:17:01 pve CRON[361770]: pam_unix(cron:session): session closed for user root
Nov 25 11:17:01 pve CRON[380482]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Nov 25 11:17:01 pve CRON[380484]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Nov 25 11:17:01 pve CRON[380482]: pam_unix(cron:session): session closed for user root
Nov 25 12:17:01 pve CRON[398738]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Nov 25 12:17:01 pve CRON[398740]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Nov 25 12:17:01 pve CRON[398738]: pam_unix(cron:session): session closed for user root
Nov 25 13:12:12 pve pvedaemon[1207]: <root@pam> successful auth for user 'root@pam'
Nov 25 13:15:18 pve pvestatd[1178]: auth key pair too old, rotating..
Nov 25 13:17:01 pve CRON[417194]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Nov 25 13:17:01 pve CRON[417196]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Nov 25 13:17:01 pve CRON[417194]: pam_unix(cron:session): session closed for user root
Nov 25 13:19:04 pve pvedaemon[1207]: worker exit
Nov 25 13:19:04 pve pvedaemon[1204]: worker 1207 finished
Nov 25 13:19:04 pve pvedaemon[1204]: starting 1 worker(s)
Nov 25 13:19:04 pve pvedaemon[1204]: worker 417870 started
Nov 25 13:27:11 pve pvedaemon[1206]: <root@pam> successful auth for user 'root@pam'
Nov 25 13:42:11 pve pvedaemon[417870]: <root@pam> successful auth for user 'root@pam'
29

Das ist das was danach bis jetzt kam

30

Ok, schaut gut aus. Da sehe ich jetzt nichts Verdächtiges!

31

Okay, leider besteht das Problem weiterhin. Ich weiß mir echt keinen Rat mehr…

32

unter homeassistant.local:8123 kannst du dich ja noch anmelden?
und wenn du jetzt die alte IP Adresse wieder einstellst was passiert dann?

33

Wie meinst du das? Ich habe bei Netzwerkeinstellungen in HA die IP als feste IP drin. Ich bekomme keine verbindung über IP adresse

34

Das ist doch nicht mehr die „alte IP“ oder?

35

doch die 192.168.178.32

36

So wie sie in Proxmox drin ist

37

Hast du IPV6 aktiv ?

38

Nein

39

Unter der localen Anmeldung läuft auch gar nichts…ich kann auch nichts einrichten, da es immer fehl schlägt. Ich bin fast soweit mein Smart Home Einzustapfen und die guten alten Schalter zu nehmen…es funktioniert nichts mehr…Ich habe auch keine Lust darauf alles neu einrichten zu müssen…naja…ich gebe für heute erstmal auf…ich habe nun alles mögliche (wie ich meine) gemacht, aber es funktioniert genauso wenig wie vorher…

40

Ich hoffe immernoch das mir jemand von euch helfen kann. Ich bin für jede Hilfe dankbar. gerne auch über Team-Viewer.
VG Raoul

41

Ich bin gerade auf einem anderen Mini Pc am neueinrichten, doch leider lässt sich der SLZB-06 nicht einrichten
Fehler beim Speichern der Add-on Konfiguration, Missing option 'base_topic' in mqtt in Zigbee2mqtt (7ad98f9c_zigbee2mqtt). Got {'data_path': '/config/zigbee2mqtt', 'socat': {'enabled': False, 'master': 'pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777', 'slave': 'tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5', 'options': '-d -d', 'log': False}, 'mqtt': {}, 'serial': {'serial': {'port': 'tcp://192.168.178.93:6638', 'baudrate': 115200, 'adapter': 'zstack', 'disable_led': False}, 'advanced': {'transmit_power': 20}}
und so sieht die Konfiguration aus:

data_path: /config/zigbee2mqtt
socat:
  enabled: false
  master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
  slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
  options: "-d -d"
  log: false
mqtt: {}
serial:
  serial:
    port: tcp://192.168.178.93:6638
    baudrate: 115200
    adapter: zstack
    disable_led: false
  advanced:
    transmit_power: 20

für eure schnelle Holfe wäre ich sehr dankbar

VG Raoul