Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Error/Bug
  4. Log: has to be type "number" but received type "string"

NEWS

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    22
    1
    1.2k

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    9.2k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    14
    1
    2.5k

Log: has to be type "number" but received type "string"

Geplant Angeheftet Gesperrt Verschoben Error/Bug
27 Beiträge 9 Kommentatoren 6.3k Aufrufe 8 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • B Bielefelder81

    1a55e019-f4b8-4bc2-892e-c3a14d5ed4ee-image.png
    e9aeafff-7701-4b2f-9259-6d312f60ee70-image.png

    Thomas BraunT Online
    Thomas BraunT Online
    Thomas Braun
    Most Active
    schrieb am zuletzt editiert von Thomas Braun
    #21

    @bielefelder81

    Bitte die Rückmeldung aus der Konsole (in CodeTags eingebettet), keine Screenshots.

    Linux-Werkzeugkasten:
    https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
    NodeJS Fixer Skript:
    https://forum.iobroker.net/topic/68035/iob-node-fix-skript
    iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

    B 2 Antworten Letzte Antwort
    0
    • Thomas BraunT Thomas Braun

      @bielefelder81

      Bitte die Rückmeldung aus der Konsole (in CodeTags eingebettet), keine Screenshots.

      B Offline
      B Offline
      Bielefelder81
      schrieb am zuletzt editiert von
      #22

      Nach iobroker update -i wurden mir 6 Updates links bei Adapter angezeigt, aber auf der Adapterseite nichts...
      Musste wieder Strg+R drücken um den Cache zu leeren.

      Thomas BraunT 1 Antwort Letzte Antwort
      0
      • B Bielefelder81

        Nach iobroker update -i wurden mir 6 Updates links bei Adapter angezeigt, aber auf der Adapterseite nichts...
        Musste wieder Strg+R drücken um den Cache zu leeren.

        Thomas BraunT Online
        Thomas BraunT Online
        Thomas Braun
        Most Active
        schrieb am zuletzt editiert von
        #23

        @bielefelder81

        Deswegen halt die Konsole. Die lügt nicht.

        Linux-Werkzeugkasten:
        https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
        NodeJS Fixer Skript:
        https://forum.iobroker.net/topic/68035/iob-node-fix-skript
        iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

        1 Antwort Letzte Antwort
        0
        • Thomas BraunT Thomas Braun

          @bielefelder81

          Bitte die Rückmeldung aus der Konsole (in CodeTags eingebettet), keine Screenshots.

          B Offline
          B Offline
          Bielefelder81
          schrieb am zuletzt editiert von
          #24

          @thomas-braun
          So ging es

          Used repository: beta
          hash changed or no sources cached => force download of new sources
          update done
          Adapter    "admin"         : 5.1.25   , installed 5.1.23 [Updateable]
          Adapter    "alexa2"        : 3.9.3    , installed 3.9.3
          Adapter    "backitup"      : 2.1.17   , installed 2.1.13 [Updateable]
          Adapter    "deconz"        : 1.3.19   , installed 2.0.5
          Adapter    "discovery"     : 2.7.0    , installed 2.7.0
          Adapter    "fritzdect"     : 2.1.15   , installed 2.1.15
          Adapter    "ical"          : 1.11.3   , installed 1.11.2 [Updateable]
          Adapter    "info"          : 1.9.8    , installed 1.9.8
          Adapter    "iot"           : 1.8.22   , installed 1.8.22
          Adapter    "jarvis"        : 2.2.3    , installed 2.2.1 [Updateable]
          Adapter    "javascript"    : 5.2.8    , installed 5.2.8
          Controller "js-controller" : 3.3.15   , installed 3.3.15
          Adapter    "mihome-vacuum" : 3.2.2    , installed 3.2.2
          Adapter    "simple-api"    : 2.6.1    , installed 2.6.1
          Adapter    "socketio"      : 3.1.4    , installed 3.1.4
          Adapter    "sonoff"        : 2.4.5    , installed 2.4.5
          Adapter    "tankerkoenig"  : 2.1.1    , installed 2.1.1
          Adapter    "telegram"      : 1.10.0   , installed 1.10.0
          Adapter    "trashschedule" : 1.2.0    , installed 1.2.0
          Adapter    "web"           : 3.4.9    , installed 3.4.7 [Updateable]
          Adapter    "yeelight-2"    : 1.1.2    , installed 1.0.3 [Updateable]
          
          1 Antwort Letzte Antwort
          0
          • F Offline
            F Offline
            frankyboy73
            schrieb am zuletzt editiert von
            #25

            Hi, bei mir kommen diese Meldungen immer noch vom TR064. Der Tr064 ist auf Version 4.2.14. Node.js ist 14.18.2. js-Controller auf 3.3.21. NPM 6.14.15.
            Ich habe schon alle Datenpunkte bzw. den kompletten Ordner Callmonitor in den Objekten gelöscht, Adapter neu gestartet, leider keine Besserung

            
            
            tr-064.0
            2021-12-09 17:18:55.299	info	State value to set for "tr-064.0.callmonitor.lastCall.callee" has to be type "number" but received type "string"
            
            tr-064.0
            2021-12-09 17:04:41.564	info	State value to set for "tr-064.0.callmonitor.connect.caller" has to be type "number" but received type "string"
            
            tr-064.0
            2021-12-09 17:04:27.214	info	State value to set for "tr-064.0.callmonitor.outbound.caller" has to be type "number" but received type "string"
            
            tr-064.0
            2021-12-09 16:56:27.495	info	State value to set for "tr-064.0.callmonitor.lastCall.callee" has to be type "number" but received type "string"
            
            tr-064.0
            2021-12-09 16:30:51.606	info	State value to set for "tr-064.0.callmonitor.lastCall.callee" has to be type "number" but received type "string"
            
            tr-064.0
            2021-12-09 16:30:15.971	info	State value to set for "tr-064.0.callmonitor.inbound.callee" has to be type "number" but received type "string"
            
            tr-064.0
            2021-12-09 16:07:01.928	info	State value to set for "tr-064.0.callmonitor.lastCall.callee" has to be type "number" but received type "string"
            
            tr-064.0
            2021-12-09 16:06:38.472	info	State value to set for "tr-064.0.callmonitor.inbound.callee" has to be type "number" but received type "string"
            
            tr-064.0
            2021-12-09 15:35:06.805	info	State value to set for "tr-064.0.callmonitor.lastCall.callee" has to be type "number" but received type "string"
            
            tr-064.0
            2021-12-09 15:33:11.333	info	State value to set for "tr-064.0.callmonitor.connect.caller" has to be type "number" but received type "string"
            
            tr-064.0
            2021-12-09 15:32:58.315	info	State value to set for "tr-064.0.callmonitor.outbound.caller" has to be type "number" but received type "string"
            
            tr-064.0
            2021-12-09 15:22:46.638	info	State value to set for "tr-064.0.callmonitor.lastCall.callee" has to be type "number" but received type "string"
            
            tr-064.0
            2021-12-09 15:19:23.891	info	State value to set for "tr-064.0.callmonitor.inbound.callee" has to be type "number" but received type "string"
            
            tr-064.0
            2021-12-09 15:13:10.835	info	State value to set for "tr-064.0.callmonitor.connect.caller" has to be type "number" but received type "string"
            
            

            Schöne Grüße Frank

            crunchipC 1 Antwort Letzte Antwort
            0
            • F frankyboy73

              Hi, bei mir kommen diese Meldungen immer noch vom TR064. Der Tr064 ist auf Version 4.2.14. Node.js ist 14.18.2. js-Controller auf 3.3.21. NPM 6.14.15.
              Ich habe schon alle Datenpunkte bzw. den kompletten Ordner Callmonitor in den Objekten gelöscht, Adapter neu gestartet, leider keine Besserung

              
              
              tr-064.0
              2021-12-09 17:18:55.299	info	State value to set for "tr-064.0.callmonitor.lastCall.callee" has to be type "number" but received type "string"
              
              tr-064.0
              2021-12-09 17:04:41.564	info	State value to set for "tr-064.0.callmonitor.connect.caller" has to be type "number" but received type "string"
              
              tr-064.0
              2021-12-09 17:04:27.214	info	State value to set for "tr-064.0.callmonitor.outbound.caller" has to be type "number" but received type "string"
              
              tr-064.0
              2021-12-09 16:56:27.495	info	State value to set for "tr-064.0.callmonitor.lastCall.callee" has to be type "number" but received type "string"
              
              tr-064.0
              2021-12-09 16:30:51.606	info	State value to set for "tr-064.0.callmonitor.lastCall.callee" has to be type "number" but received type "string"
              
              tr-064.0
              2021-12-09 16:30:15.971	info	State value to set for "tr-064.0.callmonitor.inbound.callee" has to be type "number" but received type "string"
              
              tr-064.0
              2021-12-09 16:07:01.928	info	State value to set for "tr-064.0.callmonitor.lastCall.callee" has to be type "number" but received type "string"
              
              tr-064.0
              2021-12-09 16:06:38.472	info	State value to set for "tr-064.0.callmonitor.inbound.callee" has to be type "number" but received type "string"
              
              tr-064.0
              2021-12-09 15:35:06.805	info	State value to set for "tr-064.0.callmonitor.lastCall.callee" has to be type "number" but received type "string"
              
              tr-064.0
              2021-12-09 15:33:11.333	info	State value to set for "tr-064.0.callmonitor.connect.caller" has to be type "number" but received type "string"
              
              tr-064.0
              2021-12-09 15:32:58.315	info	State value to set for "tr-064.0.callmonitor.outbound.caller" has to be type "number" but received type "string"
              
              tr-064.0
              2021-12-09 15:22:46.638	info	State value to set for "tr-064.0.callmonitor.lastCall.callee" has to be type "number" but received type "string"
              
              tr-064.0
              2021-12-09 15:19:23.891	info	State value to set for "tr-064.0.callmonitor.inbound.callee" has to be type "number" but received type "string"
              
              tr-064.0
              2021-12-09 15:13:10.835	info	State value to set for "tr-064.0.callmonitor.connect.caller" has to be type "number" but received type "string"
              
              
              crunchipC Abwesend
              crunchipC Abwesend
              crunchip
              Forum Testing Most Active
              schrieb am zuletzt editiert von
              #26

              @frankyboy73 ist bekannt und issue gibt es bereits

              umgestiegen von Proxmox auf Unraid

              F 1 Antwort Letzte Antwort
              0
              • crunchipC crunchip

                @frankyboy73 ist bekannt und issue gibt es bereits

                F Offline
                F Offline
                frankyboy73
                schrieb am zuletzt editiert von
                #27

                @crunchip Ok,danke.

                Schöne Grüße Frank

                1 Antwort Letzte Antwort
                0
                Antworten
                • In einem neuen Thema antworten
                Anmelden zum Antworten
                • Älteste zuerst
                • Neuste zuerst
                • Meiste Stimmen


                Support us

                ioBroker
                Community Adapters
                Donate

                513

                Online

                32.5k

                Benutzer

                81.7k

                Themen

                1.3m

                Beiträge
                Community
                Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                ioBroker Community 2014-2025
                logo
                • Anmelden

                • Du hast noch kein Konto? Registrieren

                • Anmelden oder registrieren, um zu suchen
                • Erster Beitrag
                  Letzter Beitrag
                0
                • Home
                • Aktuell
                • Tags
                • Ungelesen 0
                • Kategorien
                • Unreplied
                • Beliebt
                • GitHub
                • Docu
                • Hilfe