Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. js-controller 3.0/3.1 jetzt im Latest!

    NEWS

    • 15. 05. Wartungsarbeiten am ioBroker Forum

    • Monatsrückblick - April 2025

    • Minor js-controller 7.0.7 Update in latest repo

    js-controller 3.0/3.1 jetzt im Latest!

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

      @LJSven Der kommt eher vom iot Adapter der neuesten version. Bzw bitte nochmal updaten auf Latest ... da haben wir mal versuche die nötigen Linux Pakete mit zu installieren

      L 1 Reply Last reply Reply Quote 0
      • apollon77
        apollon77 @LJSven last edited by

        @LJSven Dann lada Admin mal neu 🙂 Vllt hat der einfach nur ein State Update nicht bekommen

        1 Reply Last reply Reply Quote 0
        • L
          LJSven @apollon77 last edited by

          @apollon77 Der iot-Adapter ist auf 1.4.6 - beim Raspberry sind die Fehler auch weg (waren auch da) / beim Tinkerboard sind sie noch da.

          apollon77 1 Reply Last reply Reply Quote 0
          • M
            muckel @apollon77 last edited by muckel

            @apollon77 sagte in js-controller 3.0 jetzt im Latest!:

            Ja ist simple. die "dependencies" im io.-package sind bullshit. Da wurde früher einiges nicht sauber geprüft - jetzt wirds 😞 Adapter Dev muss fixen

            Da ich kein Entwickler bin: wo gehören die eigentlich hin?

            apollon77 1 Reply Last reply Reply Quote 0
            • lobomau
              lobomau last edited by lobomau

              Bei mir lief Update von 2.x auf 3.0.14 ohne Probleme.
              Nur der worx-Adapter will grad nicht. Aber liegt es an dem Update?

              worx.0	2020-04-21 16:28:00.933	error	at processTicksAndRejections (internal/process/task_queues.js:84:21)
              worx.0	2020-04-21 16:28:00.933	error	at endReadableNT (_stream_readable.js:1187:12)
              worx.0	2020-04-21 16:28:00.933	error	at IncomingMessage.emit (events.js:322:22)
              worx.0	2020-04-21 16:28:00.933	error	at Object.onceWrapper (events.js:416:28)
              worx.0	2020-04-21 16:28:00.933	error	at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/request/request.js:1083:12)
              worx.0	2020-04-21 16:28:00.933	error	at Request.emit (events.js:310:20)
              worx.0	2020-04-21 16:28:00.933	error	at Request.<anonymous> (/opt/iobroker/node_modules/request/request.js:1161:10)
              worx.0	2020-04-21 16:28:00.933	error	at Request.emit (events.js:310:20)
              worx.0	2020-04-21 16:28:00.933	error	at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
              worx.0	2020-04-21 16:28:00.933	error	at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise/node_modules/request-promise-core/lib/plumbing.js:46:31)
              worx.0	2020-04-21 16:28:00.933	error	at Request.plumbing.callback (/opt/iobroker/node_modules/request-promise/node_modules/request-promise-core/lib/plumbing.js:104:33)
              worx.0	2020-04-21 16:28:00.933	error	at new StatusCodeError (/opt/iobroker/node_modules/request-promise/node_modules/request-promise-core/lib/errors.js:32:15)
              worx.0	2020-04-21 16:28:00.933	error	(18114) StatusCodeError: 422 - {"message":"Missing coordinates","code":"422.005"}
              worx.0	2020-04-21 16:28:00.932	error	(18114) uncaught exception: 422 - {"message":"Missing coordinates","code":"422.005"}
              
              B apollon77 2 Replies Last reply Reply Quote 0
              • B
                bkiss @lobomau last edited by

                @lobomau
                Der Worx Adapter (Version 1.0.0) läuft bei mir nach dem Update ohne Probleme

                1 Reply Last reply Reply Quote 0
                • apollon77
                  apollon77 @LJSven last edited by

                  @LJSven SInd aber am Ende nicht so wichtig weil nur ein kleines Feature von iot dann nicht tut.

                  L 1 Reply Last reply Reply Quote 0
                  • apollon77
                    apollon77 @muckel last edited by

                    @muckel In dem Fall done ... siehe https://forum.iobroker.net/post/416368

                    1 Reply Last reply Reply Quote 0
                    • apollon77
                      apollon77 @lobomau last edited by

                      @lobomau eher nicht. Mach mal Issue beim Adapter auf

                      1 Reply Last reply Reply Quote 0
                      • L
                        LJSven @apollon77 last edited by

                        @apollon77 sagte in js-controller 3.0 jetzt im Latest!:

                        @LJSven SInd aber am Ende nicht so wichtig weil nur ein kleines Feature von iot dann nicht tut.

                        Glaube ich dir - aber wenn ich eins nicht mag, sind das Fehler- & Warnmeldungen 😉 PS. Die Meldung (pixman-1) kommt jetzt aber bei jedem Adapter Update - nicht nur bei iot.

                        apollon77 1 Reply Last reply Reply Quote 0
                        • apollon77
                          apollon77 @LJSven last edited by apollon77

                          @LJSven Ja ich weiss. Das liegt an npm weil der immer alles prüft

                          Kannst höchsten nochmal manuell ein

                          sudo apt install libcairo2-dev libpango1.0-dev libjpeg-dev libgif-dev librsvg2-dev

                          versuchen und schauen ob es danach weg ist

                          L 1 Reply Last reply Reply Quote 0
                          • L
                            LJSven @apollon77 last edited by

                            @apollon77 sagte in js-controller 3.0 jetzt im Latest!:

                            sudo apt install libcairo2-dev libpango1.0-dev libjpeg-dev libgif-dev librsvg2-dev

                            Habe es mal ausgeführt - lief durch - werde beobachten, ob es jetzt weg ist.

                            1 Reply Last reply Reply Quote 0
                            • P
                              peer69 Forum Testing last edited by

                              Kann man die Meldungen zum invalid object type deaktivieren? Ich hab es den devs gemeldet, hätte jetzt aber gern wieder ein sauberes logfile.

                              deconz.0	2020-04-21 16:44:54.251	warn	(25582) This value will not be set in future versions. Please report this to the developer.
                              deconz.0	2020-04-21 16:44:54.251	warn	(25582) State value to set is invalid for deconz.0.Groups.1.bri: The state is missing the required property val!
                              deconz.0	2020-04-21 16:44:53.241	warn	(25582) This value will not be set in future versions. Please report this to the developer.
                              deconz.0	2020-04-21 16:44:53.240	warn	(25582) State value to set is invalid for deconz.0.Groups.1.on: The state is missing the required property val!
                              deconz.0	2020-04-21 16:44:38.212	warn	(25582) This value will not be set in future versions. Please report this to the developer.
                              deconz.0	2020-04-21 16:44:38.212	warn	(25582) State value to set is invalid for deconz.0.Groups.1.on: The state is missing the required property val!
                              netatmo.0	2020-04-21 16:44:10.582	warn	(27317) This object will not be created in future versions. Please report this to the developer.
                              netatmo.0	2020-04-21 16:44:10.579	warn	(27317) Object netatmo.0.My-Home.Events.5e9f06b99asdfasdfasddfasdfabb09.time is invalid: obj.common.type has an invalid value (date) but has to be one of number, string, boolean, array, object, mixed, file,
                              deconz.0	2020-04-21 16:44:08.259	warn	(25582) This value will not be set in future versions. Please report this to the developer.
                              deconz.0	2020-04-21 16:44:08.258	warn	(25582) State value to set is invalid for deconz.0.Groups.1.bri: The state is missing the required property val!
                              netatmo.0	2020-04-21 16:43:59.394	warn	(27317) This object will not be created in future versions. Please report this to the developer.
                              netatmo.0	2020-04-21 16:43:59.393	warn	(27317) Object netatmo.0.My-Home.Events.5e9fasdffdsafasd3fb06d.time is invalid: obj.common.type has an invalid value (date) but has to be one of number, string, boolean, array, object, mixed, file,
                              netatmo.0	2020-04-21 16:43:19.367	warn	(27317) This object will not be created in future versions. Please report this to the developer.
                              netatmo.0	2020-04-21 16:43:19.366	warn	(27317) Object netatmo.0.My-Home.Events.231067c231219694e4f1389.time is invalid: obj.common.type has an invalid value (date) but has to be one of number, string, boolean, array, object, mixed, file,
                              deconz.0	2020-04-21 16:42:49.430	warn	(25582) This value will not be set in future versions. Please report this to the developer.
                              deconz.0	2020-04-21 16:42:49.429	warn	(25582) State value to set is invalid for deconz.0.Groups.1.bri: The state is missing the required property val!
                              deconz.0	2020-04-21 16:42:38.297	warn	(25582) This value will not be set in future versions. Please report this to the developer.
                              deconz.0	2020-04-21 16:42:38.296	warn	(25582) State value to set is invalid for deconz.0.Groups.1.bri: The state is missing the required property val!
                              deconz.0	2020-04-21 16:42:37.298	warn	(25582) This value will not be set in future versions. Please report this to the developer.
                              deconz.0	2020-04-21 16:42:37.297	warn	(25582) State value to set is invalid for deconz.0.Groups.1.on: The state is missing the required property val!
                              
                              harrym apollon77 2 Replies Last reply Reply Quote 0
                              • harrym
                                harrym @peer69 last edited by

                                @peer69 stell den loglevel auf error

                                1 Reply Last reply Reply Quote 0
                                • apollon77
                                  apollon77 @peer69 last edited by

                                  @peer69 Und Issues bei den Adaptern anlegen nicht vergessen bevor Du auf "Ignore" schaltest

                                  1 Reply Last reply Reply Quote 0
                                  • D
                                    dtp last edited by dtp

                                    Hab gerade das Update auf den js-controller 3.0.14 und admin 4.0.9 für mein Docker-Image V4 auf der Synology DiskStation gemacht. Lief alles problemlos durch. Auch alle meine Adapter starteten ohne Fehlermeldungen.

                                    1 Reply Last reply Reply Quote 1
                                    • ostseereiter
                                      ostseereiter last edited by ostseereiter

                                      Das Update des js-controller 3.0.14 und admin 4.0.9 lief durch. Im Moment keine Auffälligkeiten.

                                      1 Reply Last reply Reply Quote 0
                                      • wendy2702
                                        wendy2702 last edited by wendy2702

                                        Update von 3.0.13 nach 3.0.14.

                                        @apollon77 : Sayit upload hatte ich vorher gemacht. Jetzt kommt das:

                                        
                                        2020-04-21 20:58:15.785  - warn: readFile will not read this file (tts.userfiles/scifi.mp3) in future versions: sayit.1 is not an object of type "meta"
                                        2020-04-21 20:58:15.809  - warn: readFile will not read this file (tts.userfiles/scifi.mp3) in future versions: sayit.1 is not an object of type "meta"
                                        2020-04-21 20:58:15.812  - warn: readFile will not read this file (tts.userfiles/gong.mp3) in future versions: sayit.1 is not an object of type "meta"
                                        2020-04-21 20:58:15.813  - warn: readFile will not read this file (tts.userfiles/gong.mp3) in future versions: sayit.1 is not an object of type "meta"
                                        
                                        

                                        Und das hier beim Yamaha Adapter: (Sorry falls es schon erwähnt wurde)

                                        
                                        2020-04-21 20:59:08.020  - warn: yamaha.0 (32612) Object yamaha.0.Commands.volumeUp is invalid: obj.common.type has an invalid value (integer) but has to be one of number, string, boolean, array, object, mixed, file, json
                                        2020-04-21 20:59:08.020  - warn: yamaha.0 (32612) This object will not be created in future versions. Please report this to the developer.
                                        2020-04-21 20:59:08.022  - warn: yamaha.0 (32612) Object yamaha.0.Commands.volumeDown is invalid: obj.common.type has an invalid value (integer) but has to be one of number, string, boolean, array, object, mixed, file, json
                                        2020-04-21 20:59:08.022  - warn: yamaha.0 (32612) This object will not be created in future versions. Please report this to the developer.
                                        2020-04-21 20:59:08.023  - warn: yamaha.0 (32612) Object yamaha.0.Commands.adjustVolume is invalid: obj.common.type has an invalid value (integer) but has to be one of number, string, boolean, array, object, mixed, file, json
                                        2020-04-21 20:59:08.024  - warn: yamaha.0 (32612) This object will not be created in future versions. Please report this to the developer.
                                        2020-04-21 20:59:08.027  - warn: yamaha.0 (32612) Object yamaha.0.volume is invalid: obj.common.type has an invalid value (integer) but has to be one of number, string, boolean, array, object, mixed, file, json
                                        2020-04-21 20:59:08.027  - warn: yamaha.0 (32612) This object will not be created in future versions. Please report this to the developer.
                                        
                                        

                                        Issue für Yamaha: https://github.com/iobroker-community-adapters/ioBroker.yamaha-community/issues/14

                                        wendy2702 created this issue in iobroker-community-adapters/ioBroker.yamaha-community

                                        closed Warnings with JS-Controller 3.0.14 #14

                                        apollon77 1 Reply Last reply Reply Quote 1
                                        • JB_Sullivan
                                          JB_Sullivan last edited by JB_Sullivan

                                          Nach dem Update auf 3.0.14 und Admin 4.0.9 habe ich jetzt einen bunten Strauß an Warn und Fehlermeldungen von verschiedenen Adaptern (vorher NULL Fehlermeldungen)

                                          tr-064.0	2020-04-21 21:35:37.299	error	(10884) Password error: Please re-enter the password in Admin. Stopping
                                          
                                          
                                          fritzbox.0	2020-04-21 21:35:41.038	warn	(6452) restartConnection: 10.IP.IP.
                                          fritzbox.0	2020-04-21 21:35:41.035	info	(6452) adapter connected to fritzbox: 10.IP.IP.
                                          
                                          innogy-smarthome.0	2020-04-21 21:37:02.227	debug	(8720) SOCKET CONNECTION TO THE INNOGY API WAS CLOSED
                                          innogy-smarthome.0	2020-04-21 21:37:02.202	info	(8720) Terminated (NO_ERROR): Without reason
                                          innogy-smarthome.0	2020-04-21 21:37:02.200	info	(8720) terminating
                                          innogy-smarthome.0	2020-04-21 21:37:02.192	debug	(8720) SOCKET CONNECTION TO THE INNOGY API WAS CLOSED
                                          innogy-smarthome.0	2020-04-21 21:37:02.188	error	at TLSWrap.onStreamRead (internal/stream_base_commons.js:111:27)
                                          innogy-smarthome.0	2020-04-21 21:37:02.188	error	(8720) Error: read ECONNRESET
                                          innogy-smarthome.0	2020-04-21 21:37:02.188	error	(8720) uncaught exception: read ECONNRESET
                                          
                                          

                                          Irgendwie hat man das Gefühl, das alles was mit FritzBox zu tun hat gerade kollabiert.

                                          tr-064.0	2020-04-21 21:49:03.583	warn	at process.topLevelDomainCallback (domain.js:126:23)
                                          tr-064.0	2020-04-21 21:49:03.583	warn	at processImmediate (timers.js:658:5)
                                          tr-064.0	2020-04-21 21:49:03.583	warn	at tryOnImmediate (timers.js:676:5)
                                          tr-064.0	2020-04-21 21:49:03.583	warn	at runCallback (timers.js:705:18)
                                          tr-064.0	2020-04-21 21:49:03.583	warn	at Immediate.setImmediate (C:\iobroker\GLT\node_modules\iobroker.js-controller\lib\states\statesInRedis.js:234:41)
                                          tr-064.0	2020-04-21 21:49:03.583	warn	at change (C:\iobroker\GLT\node_modules\iobroker.js-controller\lib\adapter.js:5228:34)
                                          tr-064.0	2020-04-21 21:49:03.583	warn	at Adapter.EventEmitter.emit (domain.js:448:20)
                                          tr-064.0	2020-04-21 21:49:03.583	warn	at Adapter.emit (events.js:198:13)
                                          tr-064.0	2020-04-21 21:49:03.583	warn	at Adapter.adapter.on.obj (C:\iobroker\GLT\node_modules\iobroker.tr-064\main.js:92:41)
                                          tr-064.0	2020-04-21 21:49:03.583	warn	at onMessage (C:\iobroker\GLT\node_modules\iobroker.tr-064\main.js:255:25)
                                          tr-064.0	2020-04-21 21:49:03.583	warn	(3316) TypeError: Cannot read property 'forEachHostEntry' of undefined
                                          tr-064.0	2020-04-21 21:49:03.561	warn	(3316) States system pmessage io.messagebox.system.adapter.tr-064.0 {"command":"discovery","message":{"onlyActive":true,"reread":false},"from":"system.adapter.admin.0","callback":{"message":{"onlyAct
                                          tr-064.0	2020-04-21 21:48:58.819	error	(3316) Password error: Please re-enter the password in Admin. Stopping
                                          tr-064.0	2020-04-21 21:48:58.798	info	(3316) starting. Version 4.0.0 in C:/iobroker/GLT/node_modules/iobroker.tr-064, node: v10.17.0, js-controller: 3.0.14
                                          host.GLT	2020-04-21 21:48:56.999	info	instance system.adapter.tr-064.0 started with pid 3316
                                          host.GLT	2020-04-21 21:48:56.978	info	"system.adapter.tr-064.0" enabled
                                          
                                          wendy2702 apollon77 2 Replies Last reply Reply Quote 0
                                          • F
                                            Flugschüler last edited by wendy2702

                                            Hallo!
                                            bin noch neu hier im Forum
                                            bei mir kommt immer das und dann startet mein js adapter neu.
                                            Kann mir vieleicht irgend wer helfen?

                                            
                                            host.raspberrypi	2020-04-21 20:49:09.462	error	Caught by controller[1]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1107:14)
                                            host.raspberrypi	2020-04-21 20:49:09.462	error	Caught by controller[1]: Error: connect EHOSTUNREACH 192.168.1.140:22
                                            host.raspberrypi	2020-04-21 20:49:09.461	error	Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejecte
                                            
                                            
                                            wendy2702 apollon77 2 Replies 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

                                            917
                                            Online

                                            31.6k
                                            Users

                                            79.4k
                                            Topics

                                            1.3m
                                            Posts

                                            js-controller
                                            127
                                            1340
                                            350071
                                            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