Skip to content
  • Home
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • 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

  • Default (No Skin)
  • No Skin
Collapse
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
    23
    1
    1.3k

  • 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"

Scheduled Pinned Locked Moved Error/Bug
27 Posts 9 Posters 6.4k Views 8 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • crunchipC crunchip

    @bielefelder81 mit welcher Adapter Version?
    sollte an sich mit v 1.1.1 behoben sein, ansonsten issue erstellen

    B Offline
    B Offline
    Bielefelder81
    wrote on last edited by
    #16

    @crunchip Also bei mir ist Yeelight auf 1.0.3, aber mir wird auch keine höhere verfügbare Version angezeigt.

    Thomas BraunT 1 Reply Last reply
    0
    • B Bielefelder81

      @crunchip Also bei mir ist Yeelight auf 1.0.3, aber mir wird auch keine höhere verfügbare Version angezeigt.

      Thomas BraunT Online
      Thomas BraunT Online
      Thomas Braun
      Most Active
      wrote on last edited by
      #17

      @bielefelder81

      Dann bist du (ganz vernünfitg) auf dem Stable-Zweig.

      yeelight-2
      github:	1.1.2
      latest:	1.1.2 for 22 days
      stable:	1.0.3 for 21 months
      

      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 1 Reply Last reply
      0
      • Thomas BraunT Thomas Braun

        @bielefelder81

        Dann bist du (ganz vernünfitg) auf dem Stable-Zweig.

        yeelight-2
        github:	1.1.2
        latest:	1.1.2 for 22 days
        stable:	1.0.3 for 21 months
        
        B Offline
        B Offline
        Bielefelder81
        wrote on last edited by
        #18

        @thomas-braun Ich habe es auch gerade auf "Beta" geändert und trotzdem kein Update

        Thomas BraunT 1 Reply Last reply
        0
        • B Bielefelder81

          @thomas-braun Ich habe es auch gerade auf "Beta" geändert und trotzdem kein Update

          Thomas BraunT Online
          Thomas BraunT Online
          Thomas Braun
          Most Active
          wrote on last edited by
          #19

          @bielefelder81

          iobroker update -i
          

          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 1 Reply Last reply
          0
          • Thomas BraunT Thomas Braun

            @bielefelder81

            iobroker update -i
            
            B Offline
            B Offline
            Bielefelder81
            wrote on last edited by
            #20

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

            Thomas BraunT 1 Reply Last reply
            0
            • 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
              wrote on last edited by 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 Replies Last reply
              0
              • Thomas BraunT Thomas Braun

                @bielefelder81

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

                B Offline
                B Offline
                Bielefelder81
                wrote on last edited by
                #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 Reply Last reply
                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
                  wrote on last edited by
                  #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 Reply Last reply
                  0
                  • Thomas BraunT Thomas Braun

                    @bielefelder81

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

                    B Offline
                    B Offline
                    Bielefelder81
                    wrote on last edited by
                    #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 Reply Last reply
                    0
                    • F Offline
                      F Offline
                      frankyboy73
                      wrote on last edited by
                      #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 Reply Last reply
                      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 Away
                        crunchipC Away
                        crunchip
                        Forum Testing Most Active
                        wrote on last edited by
                        #26

                        @frankyboy73 ist bekannt und issue gibt es bereits

                        umgestiegen von Proxmox auf Unraid

                        F 1 Reply Last reply
                        0
                        • crunchipC crunchip

                          @frankyboy73 ist bekannt und issue gibt es bereits

                          F Offline
                          F Offline
                          frankyboy73
                          wrote on last edited by
                          #27

                          @crunchip Ok,danke.

                          Schöne Grüße Frank

                          1 Reply Last reply
                          0
                          Reply
                          • Reply as topic
                          Log in to reply
                          • Oldest to Newest
                          • Newest to Oldest
                          • Most Votes


                          Support us

                          ioBroker
                          Community Adapters
                          Donate

                          831

                          Online

                          32.5k

                          Users

                          81.7k

                          Topics

                          1.3m

                          Posts
                          Community
                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                          ioBroker Community 2014-2025
                          logo
                          • Login

                          • Don't have an account? Register

                          • Login or register to search.
                          • First post
                            Last post
                          0
                          • Home
                          • Recent
                          • Tags
                          • Unread 0
                          • Categories
                          • Unreplied
                          • Popular
                          • GitHub
                          • Docu
                          • Hilfe