Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Probleme mit Updates

    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

    Probleme mit Updates

    This topic has been deleted. Only users with topic management privileges can see it.
    • Thomas Braun
      Thomas Braun Most Active @Steinmetz_4 last edited by

      @steinmetz_4

      iobroker upgrade admin --debug
      S 1 Reply Last reply Reply Quote 0
      • S
        Steinmetz_4 @mickym last edited by

        @mickym sagte in Probleme mit Updates:

        @steinmetz_4 Ich hab Dir mein Vorgehen noch verlinkt. Mach halt ein Backup deines systems vorher.

        pi@iobroker-pi:~ $ iob stop
pi@iobroker-pi:~ $ cd /opt/iobroker
pi@iobroker-pi:/opt/iobroker $ sudo rm -rf node_modules
pi@iobroker-pi:/opt/iobroker $ sudo rm package-lock.json
pi@iobroker-pi:/opt/iobroker $ npm cache clean --force
npm WARN using --force Recommended protections disabled.
pi@iobroker-pi:/opt/iobroker $ npm install
npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated multer@1.4.4: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibility with Node.js 0.10.
npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies.
npm WARN deprecated w3c-hr-time@1.0.2: Use your platform's native performance.now() and performance.timeOrigin.
npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated circular-json@0.5.9: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated crypto@1.0.1: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in.
npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated xmldom@0.1.31: Deprecated due to CVE-2021-21366 resolved in 0.5.0
npm WARN deprecated @types/keyv@4.2.0: This is a stub types definition. keyv provides its own type definitions, so you do not need this installed.
npm WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained.
npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated axios@0.27.0: Formdata complete broken, incorrect build size
npm WARN deprecated xmldom@0.1.16: Deprecated due to CVE-2021-21366 resolved in 0.5.0

added 2246 packages in 6m

194 packages are looking for funding
  run `npm fund` for details
pi@iobroker-pi:/opt/iobroker $ npm list
iobroker.inst@3.0.0 /opt/iobroker
├── @types/caseless@0.12.2 extraneous
├── @types/request@2.48.8 extraneous
├── @types/tough-cookie@4.0.2 extraneous
├── coffeescript@1.12.7 extraneous
├── iobroker.admin@6.2.23
├── iobroker.alexa2@3.19.9
├── iobroker.backitup@2.4.12
├── iobroker.chromecast@2.3.1
├── iobroker.cloud@4.2.2
├── iobroker.coronavirus-statistics@0.8.7
├── iobroker.daswetter@3.1.3
├── iobroker.discovery@3.1.0
├── iobroker.ds18b20@1.6.0
├── iobroker.dwd@2.8.3
├── iobroker.epson_ecotank_et_2750@0.0.12
├── iobroker.feiertage@1.1.0
├── iobroker.flot@1.11.0
├── iobroker.fritzdect@2.2.3
├── iobroker.history@2.2.0
├── iobroker.homeconnect@1.1.0
├── iobroker.hs100@2.1.2
├── iobroker.ical@1.13.1
├── iobroker.icons-addictive-flavour-png@0.1.0
├── iobroker.icons-material-png@0.1.0
├── iobroker.icons-material-svg@0.1.0
├── iobroker.icons-mfd-png@1.1.0
├── iobroker.icons-mfd-svg@1.1.0
├── iobroker.icons-open-icon-library-png@0.1.2
├── iobroker.icons-ultimate-png@1.0.1
├── iobroker.influxdb@3.1.8
├── iobroker.info@1.9.19
├── iobroker.iot@1.11.9
├── iobroker.jarvis@3.0.15
├── iobroker.javascript@6.0.3
├── iobroker.js-controller@4.0.23
├── iobroker.knx@2.0.13
├── iobroker.lgtv@1.1.10
├── iobroker.meross@1.14.0
├── iobroker.mihome-vacuum@3.4.2
├── iobroker.net-tools@0.2.0
├── iobroker.node-red@3.3.1
├── iobroker.ping@1.5.3
├── iobroker.pollenflug@1.0.6
├── iobroker.rpi2@1.3.2
├── iobroker.scenes@2.3.9
├── iobroker.shelly@6.0.0
├── iobroker.simple-api@2.7.0
├── iobroker.sonnen@1.11.0
├── iobroker.sonoff@2.5.1
├── iobroker.sourceanalytix@0.4.12-1
├── iobroker.sql@2.1.8
├── iobroker.tankerkoenig@2.1.1
├── iobroker.telegram@1.14.1
├── iobroker.tr-064@4.2.16
├── iobroker.trashschedule@2.0.3
├── iobroker.vis-google-fonts@1.0.3
├── iobroker.vis-hqwidgets@1.3.0
├── iobroker.vis-icontwo@0.89.0
├── iobroker.vis-inventwo@3.3.3
├── iobroker.vis-jqui-mfd@1.0.12
├── iobroker.vis-justgage@1.0.2
├── iobroker.vis-materialdesign@0.5.9
├── iobroker.vis-plumb@1.0.2
├── iobroker.vis-timeandweather@1.2.2
├── iobroker.vis@1.4.15
├── iobroker.weatherunderground@3.4.2
├── iobroker.web@4.3.0
├── iobroker.whatsapp-cmb@0.2.2
├── iobroker.worx@1.7.0
├── iobroker.zwave2@3.0.3
├── node-inspect@2.0.0 extraneous
├── suncalc2@1.8.1 extraneous
├── typescript@4.7.4 extraneous
├── virtual-tsc@0.6.2 extraneous
└── wake_on_lan@1.0.0 extraneous

pi@iobroker-pi:/opt/iobroker $

        Hab ich gemacht. 'Soll ich npm prune auch machen?

        mikeal created this issue in request/request

        open Request’s Past, Present and Future #3142

        mikeal created this issue in request/request

        open Request’s Past, Present and Future #3142

        mikeal created this issue in request/request

        open Request’s Past, Present and Future #3142

        Qix- created this issue in visionmedia/debug

        closed ReDos Vulnerability Regression Visibility Notice #797

        mickym Homoran 2 Replies Last reply Reply Quote 0
        • mickym
          mickym Most Active @Steinmetz_4 last edited by

          @steinmetz_4 sagte in Probleme mit Updates:

          'Soll ich npm prune auch machen?

          Ja

          1 Reply Last reply Reply Quote 0
          • Homoran
            Homoran Global Moderator Administrators @Steinmetz_4 last edited by

            @steinmetz_4 mixst du gerade beide Anleitungen?
            die verfolgen unterschiedliche Ansätze!
            entweder - oder! nicht beides!

            S 1 Reply Last reply Reply Quote 0
            • S
              Steinmetz_4 @Thomas Braun last edited by

              @thomas-braun

              pi@iobroker-pi:~ $ iobroker upgrade jarvis --debug
Server Configured backup period 120 is larger than the supported maximum of 35791 minutes. Defaulting to 120 minutes.
Server Configured backup period 120 is larger than the supported maximum of 35791 minutes. Defaulting to 120 minutes.
Would you like to upgrade jarvis from @3.0.14 to @3.0.15 now? [(y)es, (n)o]: y
Update jarvis from @3.0.14 to @3.0.15
NPM version: 8.19.2
Installing iobroker.jarvis@3.0.15... (System call)
npm WARN deprecated multer@1.4.4: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibility with Node.js 0.10.
npm WARN deprecated axios@0.27.0: Formdata complete broken, incorrect build size

added 56 packages, removed 16 packages, and changed 74 packages in 22s

188 packages are looking for funding
  run `npm fund` for details
upload [153] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/apple-touch-icon-120x120.png apple-touch-icon-120x120.png image/png
upload [150] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/apple-touch-icon-iphone-retina.png.png apple-touch-icon-iphone-retina.png.png image/png
upload [100] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/icons/favicon.ico icons/favicon.ico image/vnd.microsoft.icon
upload [90] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/icons/ios/AppIcon-20~ipad.png icons/ios/AppIcon-20~ipad.png image/png
upload [80] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/icons/ios/AppIcon-60@2x~car.png icons/ios/AppIcon-60@2x~car.png image/png
upload [70] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/icons/web/favicon.ico icons/web/favicon.ico image/vnd.microsoft.icon
upload [60] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/img/moon_12.436b3798.png img/moon_12.436b3798.png image/png
upload [50] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/img/moon_21.f3b5ba0a.png img/moon_21.f3b5ba0a.png image/png
upload [40] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/img/moon_4.61c6ba58.png img/moon_4.61c6ba58.png image/png
upload [30] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/img/weather_set5_13.a630a54d.png img/weather_set5_13.a630a54d.png image/png
upload [20] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/img/weather_set5_5.5334b7ac.png img/weather_set5_5.5334b7ac.png image/png
upload [19] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/img/weather_set5_6.1435f645.png img/weather_set5_6.1435f645.png image/png
upload [18] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/img/weather_set5_7.439d10db.png img/weather_set5_7.439d10db.png image/png
upload [17] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/img/weather_set5_8.9011b110.png img/weather_set5_8.9011b110.png image/png
upload [16] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/img/weather_set5_9.9dc0f52e.png img/weather_set5_9.9dc0f52e.png image/png
upload [15] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/index.html index.html text/html
upload [14] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/js/1.e516e81e.js js/1.e516e81e.js application/javascript
upload [13] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/js/10.de09a5cd.js js/10.de09a5cd.js application/javascript
upload [12] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/js/11.b003d093.js js/11.b003d093.js application/javascript
upload [11] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/js/3.4a8ae51d.js js/3.4a8ae51d.js application/javascript
upload [10] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/js/4.9a563abe.js js/4.9a563abe.js application/javascript
upload [9] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/js/5.9ba66b59.js js/5.9ba66b59.js application/javascript
upload [8] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/js/6.020de47f.js js/6.020de47f.js application/javascript
upload [7] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/js/7.89eaea6c.js js/7.89eaea6c.js application/javascript
upload [6] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/js/8.cb657ea9.js js/8.cb657ea9.js application/javascript
upload [5] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/js/9.e9a6eb5e.js js/9.e9a6eb5e.js application/javascript
upload [4] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/js/app.5d534061.js js/app.5d534061.js application/javascript
upload [3] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/js/app.hash.json js/app.hash.json application/json
upload [2] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/js/app.licences.json js/app.licences.json application/json
upload [1] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/js/vendor.3ed67ef3.js js/vendor.3ed67ef3.js application/javascript
upload [0] jarvis /opt/iobroker/node_modules/iobroker.jarvis/www/socket.io-2.3.1.slim.js socket.io-2.3.1.slim.js application/javascript
upload [15] jarvis.admin /opt/iobroker/node_modules/iobroker.jarvis/admin/admin.css admin.css text/css
upload [14] jarvis.admin /opt/iobroker/node_modules/iobroker.jarvis/admin/admin.js admin.js application/javascript
upload [13] jarvis.admin /opt/iobroker/node_modules/iobroker.jarvis/admin/i18n/de/translations.json i18n/de/translations.json application/json
upload [12] jarvis.admin /opt/iobroker/node_modules/iobroker.jarvis/admin/i18n/en/translations.json i18n/en/translations.json application/json
upload [11] jarvis.admin /opt/iobroker/node_modules/iobroker.jarvis/admin/i18n/es/translations.json i18n/es/translations.json application/json
upload [10] jarvis.admin /opt/iobroker/node_modules/iobroker.jarvis/admin/i18n/fr/translations.json i18n/fr/translations.json application/json
upload [9] jarvis.admin /opt/iobroker/node_modules/iobroker.jarvis/admin/i18n/it/translations.json i18n/it/translations.json application/json
upload [8] jarvis.admin /opt/iobroker/node_modules/iobroker.jarvis/admin/i18n/nl/translations.json i18n/nl/translations.json application/json
upload [7] jarvis.admin /opt/iobroker/node_modules/iobroker.jarvis/admin/i18n/pl/translations.json i18n/pl/translations.json application/json
upload [6] jarvis.admin /opt/iobroker/node_modules/iobroker.jarvis/admin/i18n/pt/translations.json i18n/pt/translations.json application/json
upload [5] jarvis.admin /opt/iobroker/node_modules/iobroker.jarvis/admin/i18n/ru/translations.json i18n/ru/translations.json application/json
upload [4] jarvis.admin /opt/iobroker/node_modules/iobroker.jarvis/admin/i18n/zh-cn/translations.json i18n/zh-cn/translations.json application/json
upload [3] jarvis.admin /opt/iobroker/node_modules/iobroker.jarvis/admin/index_m.html index_m.html text/html
upload [2] jarvis.admin /opt/iobroker/node_modules/iobroker.jarvis/admin/jarvis.png jarvis.png image/png
upload [1] jarvis.admin /opt/iobroker/node_modules/iobroker.jarvis/admin/words.js words.js application/javascript
upload [0] jarvis.admin /opt/iobroker/node_modules/iobroker.jarvis/admin/zefau.jpg zefau.jpg image/jpeg
              Homoran 1 Reply Last reply Reply Quote 0
              • Homoran
                Homoran Global Moderator Administrators @Steinmetz_4 last edited by

                @steinmetz_4 da ist kein error25

                und ACHTUNG!!

                @homoran sagte in Probleme mit Updates:

                @steinmetz_4 mixst du gerade beide Anleitungen?
                die verfolgen unterschiedliche Ansätze!
                entweder - oder! nicht beides!

                1 Reply Last reply Reply Quote 0
                • S
                  Steinmetz_4 @Homoran last edited by

                  @homoran sagte in Probleme mit Updates:

                  @steinmetz_4 mixst du gerade beide Anleitungen?
                  die verfolgen unterschiedliche Ansätze!
                  entweder - oder! nicht beides!

                  Nein! Ich mische nichts durcheinander.

                  Thomas Braun 1 Reply Last reply Reply Quote 0
                  • Thomas Braun
                    Thomas Braun Most Active @Steinmetz_4 last edited by Thomas Braun

                    @steinmetz_4

                    Von

                    sudo rm -rf node_modules

                    war aber nicht die Rede. Jedenfalls nicht von mir.

                    Homoran 1 Reply Last reply Reply Quote 0
                    • Homoran
                      Homoran Global Moderator Administrators @Thomas Braun last edited by

                      @thomas-braun sagte in Probleme mit Updates:

                      war aber nicht die Rede.

                      das war der alternative Vorschlag von @mickym, den @Steinmetz_4 leider hier untergemischt hat

                      S 1 Reply Last reply Reply Quote 0
                      • S
                        Steinmetz_4 @Homoran last edited by

                        @homoran sagte in Probleme mit Updates:

                        @thomas-braun sagte in Probleme mit Updates:

                        war aber nicht die Rede.

                        das war der alternative Vorschlag von @mickym, den @Steinmetz_4 leider hier untergemischt hat

                        Ja, ich kann mich düster erinnern, dass das ganze begann mit einem Update von Nodered. Darum habe ich den Vorschlag von Mickym ausprobiert.
                        Ich habe nun den Worx Adapter über die Adminoberfläche upgedatet und es hat funktioniert.

                        Ich Danke euch für eure Hilfe!!! Ohne eure Tips, wäre das nie wieder was geworden.
                        Tolles Forum, tolle Leute...

                        Mfg
                        Tom

                        Homoran 1 Reply Last reply Reply Quote 0
                        • Homoran
                          Homoran Global Moderator Administrators @Steinmetz_4 last edited by

                          @steinmetz_4 aber du hast jetzt immer noch diese mir absolut unbekannte Meldung zu dem Updateintervall drin, und wahrscheinlich jetzt einen ziemlich undefinierten Zustand durch die Vermengung der beiden Anleitungen.

                          S 1 Reply Last reply Reply Quote 0
                          • S
                            Steinmetz_4 @Homoran last edited by Steinmetz_4

                            @homoran

                            Ich habe glaube ich nichts vermengt.
                            Ich habe wie Thomas schrieb, nur einen Adapter mit --debug upgegraded.

                            Was kann ich tun, um sicher zu gehen dass alles wieder passt?

                            pi@iobroker-pi:/opt/iobroker $  which nodejs node npm && nodejs -v && node -v && npm -v && apt policy nodejs
/usr/bin/nodejs
/usr/bin/node
/usr/bin/npm
v16.17.1
v16.17.1
8.19.2
nodejs:
  Installed: 16.17.1-deb-1nodesource1
  Candidate: 16.18.0-deb-1nodesource1
  Version table:
     16.18.0-deb-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x bullseye/main arm64 Packages
 *** 16.17.1-deb-1nodesource1 100
        100 /var/lib/dpkg/status
     12.22.12~dfsg-1~deb11u1 500
        500 http://security.debian.org/debian-security bullseye-security/main arm64 Packages
     12.22.5~dfsg-2~11u1 500
        500 http://deb.debian.org/debian bullseye/main arm64 Packages
pi@iobroker-pi:/opt/iobroker $

                            Ist das in Zeile 9 und 10 so in ordnung?

                            Thomas Braun 1 Reply Last reply Reply Quote 0
                            • mickym
                              mickym Most Active last edited by mickym

                              @homoran sagte in Probleme mit Updates:

                              @steinmetz_4 aber du hast jetzt immer noch diese mir absolut unbekannte Meldung zu dem Updateintervall drin, und wahrscheinlich jetzt einen ziemlich undefinierten Zustand durch die Vermengung der beiden Anleitungen.

                              Ich seh da auch kein Problem. Da das komplette node_modules neu aufgebaut wurde, sollten eigentlich sowieso die aktuellsten Version drin sein und ist auch kein Mischmasch - da ja gar nichts altes mehr vorhanden war.

                              1 Reply Last reply Reply Quote 0
                              • Thomas Braun
                                Thomas Braun Most Active @Steinmetz_4 last edited by Thomas Braun

                                @steinmetz_4

                                Nein. Updates sind dazu da installiert zu werden.

                                iob stop
sudo apt update
sudo apt full-upgrade
sudo reboot

                                Und lass künftig die Finger von manuellen Updates von npm.

                                S 1 Reply Last reply Reply Quote 0
                                • S
                                  Steinmetz_4 @Thomas Braun last edited by

                                  @thomas-braun

                                  Wird umgehend erledigt...

                                  Mir ist noch das aufgefallen, könnte da ein Fehler sein?

                                  pi@iobroker-pi:~ $ npm list
/home/pi
├── @iobroker/adapter-core@2.6.0 extraneous
├── @types/iobroker@4.0.2 extraneous
├── @types/node@17.0.26 extraneous
└── iobroker.simple-api@2.6.5 extraneous
                                  Thomas Braun 1 Reply Last reply Reply Quote 0
                                  • Thomas Braun
                                    Thomas Braun Most Active @Steinmetz_4 last edited by Thomas Braun

                                    @steinmetz_4 sagte in Probleme mit Updates:

                                    könnte da ein Fehler sein?

                                    Ja, im /home/pi hat das nix zu suchen. Da haste mal direkt irgendwas per npm installiert und 'daneben geworfen'.

                                    S 1 Reply Last reply Reply Quote 0
                                    • S
                                      Steinmetz_4 @Thomas Braun last edited by

                                      @thomas-braun

                                      kann ich das los werden, oder soll ich es ignorieren?

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

                                        @steinmetz_4 sagte in Probleme mit Updates:

                                        @thomas-braun

                                        kann ich das los werden, oder soll ich es ignorieren?

                                        lösch halt das node_modules Verzeichnis im home Verzeichnis des pi - und gut ist.

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

                                          @mickym 👍

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

                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          872
                                          Online

                                          31.9k
                                          Users

                                          80.1k
                                          Topics

                                          1.3m
                                          Posts

                                          5
                                          29
                                          1182
                                          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