Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Tuya Presence Zy-m100-s mit dem Zigbee-Adapter einbinden

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    Tuya Presence Zy-m100-s mit dem Zigbee-Adapter einbinden

    This topic has been deleted. Only users with topic management privileges can see it.
    • ingranu
      ingranu @mickym last edited by

      @mickym Zigbee Adapter komplett gelöscht. Ich habe ein ConbeeII Stick

      mickym 1 Reply Last reply Reply Quote 0
      • ingranu
        ingranu @Guest last edited by

        @dp20eic ```
        igbee2MQTT:info 2023-06-27 14:15:59: Logging to console and directory: '/opt/zigbee2mqtt/data/log/2023-06-27.14-15-59' filename: log.txt
        Zigbee2MQTT:info 2023-06-27 14:15:59: Starting Zigbee2MQTT version 1.31.2 (commit #21f5125)
        Zigbee2MQTT:info 2023-06-27 14:15:59: Starting zigbee-herdsman (0.14.117)
        Zigbee2MQTT:info 2023-06-27 14:16:00: zigbee-herdsman started (resumed)
        Zigbee2MQTT:info 2023-06-27 14:16:00: Coordinator firmware version: '{"meta":{"maintrel":0,"majorrel":38,"minorrel":120,"product":0,"revision":"0x26780700","transportrev":0},"type":"ConBee2/RaspBee2"}'
        Zigbee2MQTT:info 2023-06-27 14:16:00: Currently 0 devices are joined:
        Zigbee2MQTT:warn 2023-06-27 14:16:00: permit_join set to true in configuration.yaml.
        Zigbee2MQTT:warn 2023-06-27 14:16:00: Allowing new devices to join.
        Zigbee2MQTT:warn 2023-06-27 14:16:00: Set permit_join to false once you joined all devices.
        Zigbee2MQTT:info 2023-06-27 14:16:00: Zigbee: allowing new devices to join.
        Zigbee2MQTT:info 2023-06-27 14:16:00: Connecting to MQTT server at mqtt://localhost
        Zigbee2MQTT:error 2023-06-27 14:16:00: MQTT error: connect ECONNREFUSED 127.0.0.1:1883
        Zigbee2MQTT:error 2023-06-27 14:16:00: MQTT failed to connect, exiting...
        Zigbee2MQTT:info 2023-06-27 14:16:00: Stopping zigbee-herdsman...
        Zigbee2MQTT:info 2023-06-27 14:16:00: Stopped zigbee-herdsman

        ? mickym 3 Replies Last reply Reply Quote 0
        • mickym
          mickym Most Active @ingranu last edited by

          @ingranu sagte in Tuya Presence Zy-m100-s mit dem Zigbee-Adapter einbinden:

          @mickym Zigbee Adapter komplett gelöscht. Ich habe ein ConbeeII Stick

          Ok den habe ich auch - dann sollte es gehen . Neu starten und mit systemctl status zigbee2mqtt prüfen - das muss laufen bevor was anderes nicht geht.

          1 Reply Last reply Reply Quote 0
          • ?
            A Former User @ingranu last edited by A Former User

            @ingranu sagte in Tuya Presence Zy-m100-s mit dem Zigbee-Adapter einbinden:

            @dp20eic ```
            igbee2MQTT:info 2023-06-27 14:15:59: Logging to console and directory: '/opt/zigbee2mqtt/data/log/2023-06-27.14-15-59' filename: log.txt
            Zigbee2MQTT:info 2023-06-27 14:15:59: Starting Zigbee2MQTT version 1.31.2 (commit #21f5125)
            Zigbee2MQTT:info 2023-06-27 14:15:59: Starting zigbee-herdsman (0.14.117)
            Zigbee2MQTT:info 2023-06-27 14:16:00: zigbee-herdsman started (resumed)
            Zigbee2MQTT:info 2023-06-27 14:16:00: Coordinator firmware version: '{"meta":{"maintrel":0,"majorrel":38,"minorrel":120,"product":0,"revision":"0x26780700","transportrev":0},"type":"ConBee2/RaspBee2"}'
            Zigbee2MQTT:info 2023-06-27 14:16:00: Currently 0 devices are joined:
            Zigbee2MQTT:warn 2023-06-27 14:16:00: permit_join set to true in configuration.yaml.
            Zigbee2MQTT:warn 2023-06-27 14:16:00: Allowing new devices to join.
            Zigbee2MQTT:warn 2023-06-27 14:16:00: Set permit_join to false once you joined all devices.
            Zigbee2MQTT:info 2023-06-27 14:16:00: Zigbee: allowing new devices to join.
            Zigbee2MQTT:info 2023-06-27 14:16:00: Connecting to MQTT server at mqtt://localhost
            Zigbee2MQTT:error 2023-06-27 14:16:00: MQTT error: connect ECONNREFUSED 127.0.0.1:1883
            Zigbee2MQTT:error 2023-06-27 14:16:00: MQTT failed to connect, exiting...
            Zigbee2MQTT:info 2023-06-27 14:16:00: Stopping zigbee-herdsman...
            Zigbee2MQTT:info 2023-06-27 14:16:00: Stopped zigbee-herdsman

            Moin,

            fast richtig 🙂

            die Code-Tags gehören immer in eine neue Zeile, dann der Text der gezeigt werden soll, dann neue Zeile und abschließend Code-Tag

            Wenn Du das Menü von oben nimmst, dann einfach enter, dann Code-Tag anklicken und den Text zwischen die drei ``` Zeichen setzen.

            VG
            Bernd

            1 Reply Last reply Reply Quote 0
            • mickym
              mickym Most Active @ingranu last edited by

              @ingranu sagte in Tuya Presence Zy-m100-s mit dem Zigbee-Adapter einbinden:

              MQTT error: connect ECONNREFUSED 127.0.0.1:1883

              Entscheide Dich erst mal ob Du mit dem zigbee2mqtt Adapter als Broker verwenden willst, dann brauchst Du den mqtt Adapter nicht.

              ingranu 1 Reply Last reply Reply Quote 0
              • ingranu
                ingranu @mickym last edited by

                @mickym Ich habe alle Adapter deinstalliert und nur die Installation auf Linux gemacht vom Zigbe2mqtt gemacht.

                1 Reply Last reply Reply Quote 0
                • ?
                  A Former User @Guest last edited by A Former User

                  @dp20eic sagte in Tuya Presence Zy-m100-s mit dem Zigbee-Adapter einbinden:

                  @dp20eic Also die config sieht so aus:

                  Moin,

                  ich denke, dass da ein Fehler in der config ist.

                  Meine:

                  [sudo] password for dp20eic: 
                  homeassistant: false
                  permit_join: false
                  mqtt:
                    base_topic: zigbee2mqtt
                    server: mqtt://ds716plus.fritz.box:1883          <--- Port sehe ich bei Dir nicht
                  serial:
                    port: /dev/ttyACM3
                    adapter: auto
                  frontend:
                    port: 8080
                  advanced:
                    homeassistant_legacy_entity_attributes: false
                    legacy_api: false
                    legacy_availability_payload: false
                  device_options:
                    legacy: false
                  

                  VG
                  Bernd

                  P.S.: Nop, mein Fehler, Du setzt auf minimal, also ohne MQTT, dann muss da auch kein Port rein. Musste mich auch gerade erst einmal wieder einlesen 🙂

                  ingranu 1 Reply Last reply Reply Quote 0
                  • ingranu
                    ingranu @Guest last edited by ingranu

                    @dp20eic Habe die Config jetzt angepasst und meine IP eingetragen sowie der Port:

                    homeassistant: false
                    permit_join: true 
                    mqtt:
                    base_topic: zigbee2mqtt
                    server: mqtt://192.168.3.7:1883
                    serial:
                    port: /dev/ttyACM0
                    adapter: auto
                    frontend:
                    port: 8080
                    advanced:
                    homeassistant_legacy_entity_attributes: false
                    legacy_api: false
                    legacy_availability_payload: false
                    device_options:
                    legacy: false
                    
                    Zigbee2MQTT:info  2023-06-27 14:36:21: Logging to console and directory: '/opt/zigbee2mqtt/data/log/2023-06-27.14-36-21' filename: log.txt
                    Zigbee2MQTT:info  2023-06-27 14:36:21: Starting Zigbee2MQTT version 1.31.2 (commit #21f5125)
                    Zigbee2MQTT:info  2023-06-27 14:36:21: Starting zigbee-herdsman (0.14.117)
                    Zigbee2MQTT:info  2023-06-27 14:36:22: zigbee-herdsman started (resumed)
                    Zigbee2MQTT:info  2023-06-27 14:36:22: Coordinator firmware version: '{"meta":{"maintrel":0,"majorrel":38,"minorrel":120,"product":0,"revision":"0x26780700","transportrev":0},"type":"ConBee2/RaspBee2"}'
                    Zigbee2MQTT:info  2023-06-27 14:36:22: Currently 0 devices are joined:
                    Zigbee2MQTT:warn  2023-06-27 14:36:22: `permit_join` set to  `true` in configuration.yaml.
                    Zigbee2MQTT:warn  2023-06-27 14:36:22: Allowing new devices to join.
                    Zigbee2MQTT:warn  2023-06-27 14:36:22: Set `permit_join` to `false` once you joined all devices.
                    Zigbee2MQTT:info  2023-06-27 14:36:22: Zigbee: allowing new devices to join.
                    Zigbee2MQTT:info  2023-06-27 14:36:22: Connecting to MQTT server at mqtt://192.168.3.7:1883
                    Zigbee2MQTT:error 2023-06-27 14:36:22: MQTT error: connect ECONNREFUSED 192.168.3.7:1883
                    Zigbee2MQTT:error 2023-06-27 14:36:22: MQTT failed to connect, exiting...
                    Zigbee2MQTT:info  2023-06-27 14:36:22: Stopping zigbee-herdsman...
                    Zigbee2MQTT:info  2023-06-27 14:36:23: Stopped zigbee-herdsman
                    

                    iobroker komplett gestopt. Jedoch gehts trotzdem nicht

                    ? mickym 2 Replies Last reply Reply Quote 0
                    • ?
                      A Former User @ingranu last edited by

                      @ingranu sagte in Tuya Presence Zy-m100-s mit dem Zigbee-Adapter einbinden:

                      Habe die Config jetzt angepasst und meine IP eingetragen sowie der Port:

                      Moin,

                      hatte gerade ergänzt, dass ich da ein Fehler gemacht habe, da Du erst einmal ohne MQTT Server arbeiten willst, dann muss da auch kein Port rein und localhost ist auch ok.

                      Sorry für die Verwirrung, ist schon einige Zeit her 😉

                      VG
                      Bernd

                      ingranu 1 Reply Last reply Reply Quote 0
                      • ingranu
                        ingranu @Guest last edited by

                        @dp20eic Kein Ding 🙂 Hab beides versucht, gleiche Ergebniss

                        1 Reply Last reply Reply Quote 0
                        • mickym
                          mickym Most Active @ingranu last edited by

                          @ingranu Du brauchst eine Broker - also entweder den zigbee2mqtt Adapter oder den mqtt Adapter als Broker - eines von beiden muss als Ziel dienen.

                          Was hast Du denn sonst noch für Adapter laufen?

                          9ffb7575-fae2-461e-95bb-9b1f715c3e39-image.png

                          also

                          sudo netstat -tulpen
                          

                          und schauen, was für Prozesse laufen.

                          ingranu 1 Reply Last reply Reply Quote 0
                          • ingranu
                            ingranu @mickym last edited by

                            @mickym Ich habe den zigbe25mqtt am laufe, status sieht so aus:
                            z2PNG.PNG

                            Ausgabe:

                            root@iobroke-vm:/opt/zigbee2mqtt# sudo netstat -tulpen
                            Active Internet connections (only servers)
                            Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name    
                            tcp        0      0 0.0.0.0:9000            0.0.0.0:*               LISTEN      1001       28713      691/iobroker.js-con 
                            tcp        0      0 0.0.0.0:9001            0.0.0.0:*               LISTEN      1001       27572      691/iobroker.js-con 
                            tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      0          16778      1/init              
                            tcp        0      0 192.168.3.7:2001        0.0.0.0:*               LISTEN      1001       29567      1772/io.hm-rpc.0    
                            tcp        0      0 192.168.3.7:8081        0.0.0.0:*               LISTEN      1001       28970      1110/io.admin.0     
                            tcp        0      0 192.168.3.7:8082        0.0.0.0:*               LISTEN      1001       35943      3525/io.web.0       
                            tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      101        22085      663/systemd-resolve 
                            tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          25848      756/sshd: /usr/sbin 
                            tcp        0      0 192.168.3.7:8087        0.0.0.0:*               LISTEN      1001       35753      3464/io.simple-api. 
                            tcp        0      0 192.168.3.7:2010        0.0.0.0:*               LISTEN      1001       30468      2019/io.hm-rpc.1    
                            tcp        0      0 192.168.3.7:8701        0.0.0.0:*               LISTEN      1001       30890      2079/io.hm-rpc.2    
                            tcp6       0      0 :::111                  :::*                    LISTEN      0          16782      1/init              
                            tcp6       0      0 :::22                   :::*                    LISTEN      0          25859      756/sshd: /usr/sbin 
                            udp        0      0 0.0.0.0:5683            0.0.0.0:*                           1001       30933      2113/io.shelly.0    
                            udp        0      0 127.0.0.53:53           0.0.0.0:*                           101        22084      663/systemd-resolve 
                            udp        0      0 0.0.0.0:67              0.0.0.0:*                           1001       29814      1298/io.radar2.0    
                            udp        0      0 192.168.3.7:68          0.0.0.0:*                           100        22058      661/systemd-network 
                            udp        0      0 0.0.0.0:111             0.0.0.0:*                           0          16779      1/init              
                            udp6       0      0 :::111                  :::*                                0          16785      1/init              
                            
                            mickym 1 Reply Last reply Reply Quote 0
                            • mickym
                              mickym Most Active @ingranu last edited by mickym

                              @ingranu Da Du keinen eigen Mqtt Broker hast - musst Du Dummy mqtt-Broker erstellen anhaken. Was Dir lieber ist. Und lass mal Websocket weg (wenn das geht) - keine Ahnung was Du da noch für Möglichkeiten hast. Und dann wieder prüfen, ob was auf 1883 hört. Im Moment siehst Du das nichts auf 1883 hört, deswegen kann sich Dein zigbee2mqtt Dienst nicht verbinden.

                              ingranu 1 Reply Last reply Reply Quote 0
                              • ingranu
                                ingranu @mickym last edited by ingranu

                                @mickym stimmt das so ?

                                Z2m.PNG

                                Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name    
                                tcp        0      0 0.0.0.0:9000            0.0.0.0:*               LISTEN      1001       28713      691/iobroker.js-con 
                                tcp        0      0 0.0.0.0:9001            0.0.0.0:*               LISTEN      1001       27572      691/iobroker.js-con 
                                tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      0          16778      1/init              
                                tcp        0      0 192.168.3.7:2001        0.0.0.0:*               LISTEN      1001       29567      1772/io.hm-rpc.0    
                                tcp        0      0 192.168.3.7:8081        0.0.0.0:*               LISTEN      1001       28970      1110/io.admin.0     
                                tcp        0      0 192.168.3.7:8082        0.0.0.0:*               LISTEN      1001       35943      3525/io.web.0       
                                tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      101        22085      663/systemd-resolve 
                                tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          25848      756/sshd: /usr/sbin 
                                tcp        0      0 192.168.3.7:8087        0.0.0.0:*               LISTEN      1001       35753      3464/io.simple-api. 
                                tcp        0      0 192.168.3.7:2010        0.0.0.0:*               LISTEN      1001       30468      2019/io.hm-rpc.1    
                                tcp        0      0 192.168.3.7:1883        0.0.0.0:*               LISTEN      1001       42944      3948/io.zigbee2mqtt 
                                tcp        0      0 192.168.3.7:8701        0.0.0.0:*               LISTEN      1001       30890      2079/io.hm-rpc.2    
                                tcp6       0      0 :::111                  :::*                    LISTEN      0          16782      1/init              
                                tcp6       0      0 :::22                   :::*                    LISTEN      0          25859      756/sshd: /usr/sbin 
                                udp        0      0 0.0.0.0:5683            0.0.0.0:*                           1001       30933      2113/io.shelly.0    
                                udp        0      0 127.0.0.53:53           0.0.0.0:*                           101        22084      663/systemd-resolve 
                                udp        0      0 0.0.0.0:67              0.0.0.0:*                           1001       29814      1298/io.radar2.0    
                                udp        0      0 192.168.3.7:68          0.0.0.0:*                           100        22058      661/systemd-network 
                                udp        0      0 0.0.0.0:111             0.0.0.0:*                           0          16779      1/init              
                                udp6       0      0 :::111                  :::*                                0          16785      1/init   
                                
                                mickym T 2 Replies Last reply Reply Quote 0
                                • mickym
                                  mickym Most Active @ingranu last edited by mickym

                                  @ingranu Ja jetzt schaut das besser aus.
                                  227ed11e-8594-4353-a009-60884bc13ae1-image.png
                                  Nun mit

                                  sudo systemctl restart zigbee2mqtt
                                  

                                  und mit

                                  systemctl status zigbee2mqtt
                                  

                                  kontrollieren

                                  ingranu 1 Reply Last reply Reply Quote 0
                                  • ingranu
                                    ingranu @mickym last edited by ingranu

                                    @mickym said in Tuya Presence Zy-m100-s mit dem Zigbee-Adapter einbinden:

                                    sudo systemctl restart zigbee2mqtt

                                    Erhalte ich diese Meldungen:

                                    zigbee2mqtt.service - zigbee2mqtt
                                         Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; enabled; vendor preset: enabled)
                                         Active: activating (auto-restart) (Result: exit-code) since Tue 2023-06-27 15:07:19 CEST; 6s ago
                                        Process: 3857 ExecStart=/usr/bin/npm start (code=exited, status=1/FAILURE)
                                       Main PID: 3857 (code=exited, status=1/FAILURE)
                                    

                                    Scheint zu laufen:

                                    zigbee2mqtt.service - zigbee2mqtt
                                         Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; enabled; vendor preset: enabled)
                                         Active: active (running) since Tue 2023-06-27 15:09:04 CEST; 244ms ago
                                       Main PID: 4395 (npm)
                                          Tasks: 7 (limit: 9311)
                                         Memory: 30.1M
                                         CGroup: /system.slice/zigbee2mqtt.service
                                                 └─4395 npm
                                    
                                    Jun 27 15:09:04 iobroke-vm systemd[1]: Started zigbee2mqtt.
                                    root@iobroke-vm:/opt/zigbee2mqtt# 
                                    
                                    mickym ? 2 Replies Last reply Reply Quote 0
                                    • mickym
                                      mickym Most Active @ingranu last edited by mickym

                                      Na dann ist doch gut.

                                      ingranu 1 Reply Last reply Reply Quote 0
                                      • ingranu
                                        ingranu @mickym last edited by ingranu

                                        @mickym Bricht dann aber wieder ab:

                                        zigbee2mqtt.service - zigbee2mqtt
                                             Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; enabled; vendor preset: enabled)
                                             Active: activating (auto-restart) (Result: exit-code) since Tue 2023-06-27 15:11:28 CEST; 607ms ago
                                            Process: 1298 ExecStart=/usr/bin/npm start (code=exited, status=1/FAILURE)
                                           Main PID: 1298 (code=exited, status=1/FAILURE)
                                        

                                        Sieht bei mir so aus:

                                        [Unit]
                                        Description=zigbee2mqtt
                                        After=network.target
                                        
                                        [Service]
                                        Environment=NODE_ENV=production
                                        ExecStart=/usr/bin/npm start
                                        WorkingDirectory=/opt/zigbee2mqtt
                                        StandardOutput=inherit
                                        # Or use StandardOutput=null if you don't want Zigbee2MQTT messages filling syslog, for more options 
                                        # see systemd.exec(5)
                                        StandardError=inherit
                                        Restart=always
                                        RestartSec=10s
                                        User=root
                                        [Install]
                                        WantedBy=multi-user.target
                                        
                                        mickym 1 Reply Last reply Reply Quote 0
                                        • ?
                                          A Former User @ingranu last edited by A Former User

                                          @ingranu sagte in Tuya Presence Zy-m100-s mit dem Zigbee-Adapter einbinden:

                                          Active: active (running) since Tue 2023-06-27 15:09:04 CEST; 244ms ago

                                          Moin,

                                          schau mal öfter,

                                           Active: active (running) since Tue 2023-06-27 15:09:04 CEST; 244ms ago   <--- 
                                          

                                          So, oder so ähnlich sollte das aussehen, wenn es läuft, außer, dass Du noch nichts angelernt hast.

                                          $ systemctl status zigbee2mqtt.service
                                          ● zigbee2mqtt.service - zigbee2mqtt
                                               Loaded: loaded (/usr/lib/systemd/system/zigbee2mqtt.service; enabled; preset: disabled)
                                               Active: active (running) since Thu 2023-06-22 13:51:31 CEST; 5 days ago
                                             Main PID: 70 (node)
                                                Tasks: 11 (limit: 38344)
                                               Memory: 90.8M
                                                  CPU: 16.016s
                                               CGroup: /system.slice/zigbee2mqtt.service
                                                       └─70 node index.js
                                          
                                          Jun 27 12:12:41 arch-iob node[70]: Zigbee2MQTT:info  2023-06-27 12:12:41: MQTT publish: topic 'zigbee2mqtt/BWM', payload '{"battery":74,"illuminance_above_threshold":false,"linkquality":97,"occupancy":true,"update":{"installed_version>
                                          Jun 27 12:15:41 arch-iob node[70]: Zigbee2MQTT:info  2023-06-27 12:15:41: MQTT publish: topic 'zigbee2mqtt/BWM', payload '{"battery":74,"illuminance_above_threshold":false,"linkquality":97,"occupancy":false,"update":{"installed_versio>
                                          Jun 27 12:25:30 arch-iob node[70]: Zigbee2MQTT:info  2023-06-27 12:25:30: MQTT publish: topic 'zigbee2mqtt/0x00158d000404fcfa', payload '{"battery":100,"device_temperature":31,"linkquality":162,"power_outage_count":63,"voltage":3045}'
                                          Jun 27 12:50:26 arch-iob node[70]: Zigbee2MQTT:info  2023-06-27 12:50:26: MQTT publish: topic 'zigbee2mqtt/0x00158d000404db9f', payload '{"battery":100,"device_temperature":35,"linkquality":170,"power_outage_count":164,"voltage":3015}'
                                          Jun 27 13:12:42 arch-iob node[70]: Zigbee2MQTT:info  2023-06-27 13:12:42: MQTT publish: topic 'zigbee2mqtt/BWM/availability', payload '{"state":"offline"}'
                                          Jun 27 13:15:42 arch-iob node[70]: Zigbee2MQTT:info  2023-06-27 13:15:42: MQTT publish: topic 'zigbee2mqtt/0x00158d000404fcfa', payload '{"battery":100,"device_temperature":31,"linkquality":162,"power_outage_count":63,"voltage":3045}'
                                          Jun 27 13:40:36 arch-iob node[70]: Zigbee2MQTT:info  2023-06-27 13:40:36: MQTT publish: topic 'zigbee2mqtt/0x00158d000404db9f', payload '{"battery":100,"device_temperature":35,"linkquality":168,"power_outage_count":164,"voltage":3015}'
                                          Jun 27 14:05:54 arch-iob node[70]: Zigbee2MQTT:info  2023-06-27 14:05:54: MQTT publish: topic 'zigbee2mqtt/0x00158d000404fcfa', payload '{"battery":100,"device_temperature":30,"linkquality":162,"power_outage_count":63,"voltage":3045}'
                                          Jun 27 14:30:45 arch-iob node[70]: Zigbee2MQTT:info  2023-06-27 14:30:45: MQTT publish: topic 'zigbee2mqtt/0x00158d000404db9f', payload '{"battery":100,"device_temperature":35,"linkquality":168,"power_outage_count":164,"voltage":3015}'
                                          Jun 27 14:56:06 arch-iob node[70]: Zigbee2MQTT:info  2023-06-27 14:56:06: MQTT publish: topic 'zigbee2mqtt/0x00158d000404fcfa', payload '{"battery":100,"device
                                          

                                          Mach mal

                                          watch systemctl status zigbee2mqtt.service
                                          

                                          VG
                                          Bernd

                                          P.S.: und mal schauen was im journal steht

                                          journalctl -u node
                                          
                                          1 Reply Last reply Reply Quote 0
                                          • mickym
                                            mickym Most Active @ingranu last edited by

                                            Startet eigentlich Dein zigbee2mqtt Adapter richtig?

                                            ingranu 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            637
                                            Online

                                            31.9k
                                            Users

                                            80.2k
                                            Topics

                                            1.3m
                                            Posts

                                            8
                                            76
                                            5219
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo