Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Beta Test js-controller 3.2.x auf GitHub

    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

    Beta Test js-controller 3.2.x auf GitHub

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

      @apollon77 sagte in Beta Test js-controller 3.2.x auf GitHub:

      @ilovegym Butte auch Issue anlegen

      https://github.com/Apollon77/ioBroker.smartmeter/issues/179

      Ilovegym66 created this issue in Apollon77/ioBroker.smartmeter

      closed js-cotntroller 3.2.3 warnings #179

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

        @Rob_in Exakt, war gherade einkaufen und dann ne USV tauschen und jetzt sortiere ich alles und bereite update vor 🙂
        Noch eeeeeetwas Geduld

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

          So, liebe Freunde der gepflegten Controler Tests 🙂

          Github ist nun mit der 3.2.4 ausgestattet die alles bisher berichtete behandelt.

          • die "Not exists" Fehler in einigen Adaptern wenn diese nicht existente Objekte gelöscht haben sollten weg sein
          • Lets encrypt wurde nochmal ein bissl getuned (hat das schonmal jemand gecheckt? ;-))
          • der Adapter löschen File Fehler von @Homoran sollte auch weg sein

          Have fun

          Ingo

          Neuschwansteini Homoran UncleSam peterbaumert 4 Replies Last reply Reply Quote 0
          • Neuschwansteini
            Neuschwansteini @apollon77 last edited by

            @apollon77 Super, vielen vielen Dank fürs schnelle fixen, das Teil läuft hier jetzt produktiv und darf sich mal austoben.. 🙂

            Enigma, Mihome-Vacuum, etc.. keine Fehler mehr.

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

              @apollon77 sagte in Beta Test js-controller 3.2.x auf GitHub:

              der Adapter löschen File Fehler von @Homoran sollte auch weg sein

              Jepp!

              $ ./iobroker del hm-rpc
Delete adapter "hm-rpc"
host.ioBroker-rock64 Counted 3 meta of hm-rpc
host.ioBroker-rock64 Counted 1 adapter for hm-rpc
host.ioBroker-rock64 file hm-rpc.admin deleted
host.ioBroker-rock64 object hm-rpc.admin deleted
host.ioBroker-rock64 Deleting 4 object(s).
npm uninstall iobroker.hm-rpc --loglevel error --prefix "/opt/iobroker" (System call)
process exited with code 0

              Danke!

              1 Reply Last reply Reply Quote 1
              • J
                Jan1 last edited by

                Eine Warnung habe ich noch:

                alexa2.0	2021-01-09 18:37:33.810	warn	(2002421) State "alexa2.0.Echo-Devices.G070L80672670J9K.Player.muted" has no existing object, this might lead to an error in future versions
alexa2.0	2021-01-09 18:37:33.808	warn	(2002421) State "alexa2.0.Echo-Devices.G070L80672670J9K.Player.volume" has no existing object, this might lead to an error in future versions
                apollon77 Homoran 2 Replies Last reply Reply Quote 0
                • apollon77
                  apollon77 @Jan1 last edited by

                  @Jan1 —> Adapter issue anlegen (bzw das gibts schon)

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

                    @Jan1 sagte in Beta Test js-controller 3.2.x auf GitHub:

                    Eine Warnung habe ich noch:

                    so was hab ich reichlich:

                    hm-rpc.0	2021-01-09 18:48:51.753	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:35","VALUES"]
hm-rpc.0	2021-01-09 18:48:51.695	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:34","VALUES"]
hm-rpc.0	2021-01-09 18:48:51.630	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:33","VALUES"]
hm-rpc.0	2021-01-09 18:48:51.537	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:32","VALUES"]
hm-rpc.0	2021-01-09 18:48:51.467	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:31","VALUES"]
hm-rpc.0	2021-01-09 18:48:51.407	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:30","VALUES"]
hm-rpc.0	2021-01-09 18:48:51.340	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:29","VALUES"]
hm-rpc.0	2021-01-09 18:48:51.277	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:28","VALUES"]
hm-rpc.0	2021-01-09 18:48:51.218	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:27","VALUES"]
hm-rpc.0	2021-01-09 18:48:51.159	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:26","VALUES"]
hm-rpc.0	2021-01-09 18:48:51.101	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:25","VALUES"]
hm-rpc.0	2021-01-09 18:48:51.042	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:24","VALUES"]
hm-rpc.0	2021-01-09 18:48:50.982	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:23","VALUES"]
hm-rpc.0	2021-01-09 18:48:50.894	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:22","VALUES"]
hm-rpc.0	2021-01-09 18:48:50.824	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:21","VALUES"]
hm-rpc.0	2021-01-09 18:48:50.764	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:20","VALUES"]
hm-rpc.0	2021-01-09 18:48:50.704	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:19","VALUES"]
hm-rpc.0	2021-01-09 18:48:50.644	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:18","VALUES"]
hm-rpc.0	2021-01-09 18:48:50.586	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:17","VALUES"]
hm-rpc.0	2021-01-09 18:48:50.528	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:16","VALUES"]
hm-rpc.0	2021-01-09 18:48:50.469	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:15","VALUES"]
hm-rpc.0	2021-01-09 18:48:50.411	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:14","VALUES"]
hm-rpc.0	2021-01-09 18:48:50.300	warn	(10641) State "hm-rpc.0.LTK0124195.2.FREQUENCY" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:50.298	warn	(10641) State "hm-rpc.0.LTK0124195.2.VOLTAGE" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:50.296	warn	(10641) State "hm-rpc.0.LTK0124195.2.CURRENT" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:50.287	warn	(10641) State "hm-rpc.0.LTK0124195.2.POWER" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:50.286	warn	(10641) State "hm-rpc.0.LTK0124195.2.ENERGY_COUNTER" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:50.284	warn	(10641) State "hm-rpc.0.LTK0124195.2.BOOT" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:50.234	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:13","VALUES"]
hm-rpc.0	2021-01-09 18:48:49.813	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:12","VALUES"]
hm-rpc.0	2021-01-09 18:48:49.747	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:11","VALUES"]
hm-rpc.0	2021-01-09 18:48:49.689	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:10","VALUES"]
hm-rpc.0	2021-01-09 18:48:49.630	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:9","VALUES"]
hm-rpc.0	2021-01-09 18:48:49.571	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:8","VALUES"]
hm-rpc.0	2021-01-09 18:48:49.512	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:7","VALUES"]
hm-rpc.0	2021-01-09 18:48:49.453	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:6","VALUES"]
hm-rpc.0	2021-01-09 18:48:49.393	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:5","VALUES"]
hm-rpc.0	2021-01-09 18:48:49.333	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:4","VALUES"]
hm-rpc.0	2021-01-09 18:48:49.263	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:3","VALUES"]
hm-rpc.0	2021-01-09 18:48:49.203	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:2","VALUES"]
hm-rpc.0	2021-01-09 18:48:49.140	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:1","VALUES"]
hm-rpc.0	2021-01-09 18:48:49.072	warn	(10641) State "hm-rpc.0.NEQ0633493.1.STATE" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:49.070	warn	(10641) State "hm-rpc.0.NEQ0633493.1.LOWBAT" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:49.032	warn	(10641) State "hm-rpc.0.NEQ0633493.1.ERROR" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:48.133	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:0","VALUES"]
hm-rpc.0	2021-01-09 18:48:44.849	warn	(10641) State "hm-rpc.0.BidCoS-RF.50.PRESS_LONG" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:44.508	warn	(10641) State "hm-rpc.0.JEQ0140901.1.BRIGHTNESS" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:44.482	warn	(10641) State "hm-rpc.0.JEQ0140901.1.SUNSHINEDURATION" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:44.481	warn	(10641) State "hm-rpc.0.JEQ0140901.1.WIND_DIRECTION_RANGE" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:44.479	warn	(10641) State "hm-rpc.0.JEQ0140901.1.WIND_DIRECTION" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:44.478	warn	(10641) State "hm-rpc.0.JEQ0140901.1.WIND_SPEED" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:44.476	warn	(10641) State "hm-rpc.0.JEQ0140901.1.RAIN_COUNTER" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:44.475	warn	(10641) State "hm-rpc.0.JEQ0140901.1.RAINING" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:44.473	warn	(10641) State "hm-rpc.0.JEQ0140901.1.HUMIDITY" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:44.466	warn	(10641) State "hm-rpc.0.JEQ0140901.1.TEMPERATURE" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:43.685	warn	(10641) State "hm-rpc.0.LTK0129844.2.SET_TEMPERATURE" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:43.666	warn	(10641) State "hm-rpc.0.LTK0129844.2.ACTUAL_HUMIDITY" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:43.664	warn	(10641) State "hm-rpc.0.LTK0129844.2.ACTUAL_TEMPERATURE" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:43.646	warn	(10641) State "hm-rpc.0.NEQ0532734.5.LOWBAT" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:43.645	warn	(10641) State "hm-rpc.0.NEQ0532734.4.LOWBAT" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:43.643	warn	(10641) State "hm-rpc.0.NEQ0532734.3.LOWBAT" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:43.642	warn	(10641) State "hm-rpc.0.NEQ0532734.2.LOWBAT" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:43.640	warn	(10641) State "hm-rpc.0.NEQ0532734.1.LOWBAT" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:43.639	warn	(10641) State "hm-rpc.0.NEQ0532734.0.LOWBAT" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:43.637	warn	(10641) State "hm-rpc.0.NEQ0532734.4.TEMPERATURE" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:43.635	warn	(10641) State "hm-rpc.0.NEQ0532734.3.TEMPERATURE" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:43.633	warn	(10641) State "hm-rpc.0.NEQ0532734.2.TEMPERATURE" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 18:48:43.621	warn	(10641) State "hm-rpc.0.NEQ0532734.1.TEMPERATURE" has no existing object, this might lead to an error in future versions

                    Issue bei hm-rpc?

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

                      @apollon77
                      Dann ist ja schon alles in die Wege geleitet und der Rest verhält sich bei mir bis jetzt sehr unauffällig. Mal wieder top Arbeit 👍

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

                        @apollon77 sagte in Beta Test js-controller 3.2.x auf GitHub:

                        Lets encrypt wurde nochmal ein bissl getuned (hat das schonmal jemand gecheckt? ;-))

                        Wäre es sinnvoll hier im Forumin in alle LE Themen der letzten vier Monate einen Beitrag zu machen, dass das getestet werden könnte? Von den Kern-Leuten verwenden das wohl die wenigsten, da die meisten auf die Cloud setzen

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

                          @UncleSam super Idee. Mag jemand das mal übernehmen? Aber halt betonen das noch frühes stadium nichtsesshaftem jemand unwissentlich seien Live system schrottet.

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

                            @apollon77 ich mache das... Wenn ich die Themen finde...

                            Edit: Nachtrag: habe es in 5 Themen, die seit Mai erstellt wurden, erwähnt. Hoffen wir, dass sich jemand meldet.

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

                              @UncleSam @apollon77

                              Auch hier weiß ich nicht, ob es am controller liegt, aber ich bekomme keine Verbindung zur Homematic bei HmIP

                              2021-01-09 20:03:37.197 - info: host.ioBroker-rock64 instance system.adapter.hm-rpc.1 started with pid 10896
2021-01-09 20:03:40.061 - info: hm-rpc.1 (10896) starting. Version 1.14.24 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v12.20.1, js-controller: 3.2.4
2021-01-09 20:03:40.256 - info: hm-rpc.1 (10896) xmlrpc server is trying to listen on 192.168.138.168:2010
2021-01-09 20:03:40.258 - info: hm-rpc.1 (10896) xmlrpc client is trying to connect to 192.168.123.52:2010/ with ["http://192.168.138.168:2010","hm-rpc.1"]
2021-01-09 20:03:58.396 - warn: hm-rpc.0 (10658) State "hm-rpc.0.CENTRAL.PONG" has no existing object, this might lead to an error in future versions
:
:
:
hm-rpc.1	2021-01-09 20:05:51.215	error	(10896) init error: Error: connect ETIMEDOUT 192.168.123.52:2010

                              Einstellung ist identisch, wie bisher

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

                                @Homoran timeout ... wüsste nicht was das sein kann. Mal ccu restarted?

                                Homoran 1 Reply Last reply Reply Quote 0
                                • MalleRalle
                                  MalleRalle last edited by MalleRalle

                                  So, ich teste mal mit.
                                  Sieht alles schonmal ganz gut aus.
                                  Folgende Fehlermeldungen:

                                  
tankerkoenig.0	2021-01-09 20:55:00.231	warn	(382886) State "tankerkoenig.0.stations.8.e10.combined" has no existing object, this might lead to an error in future versions
hm-rpc.3	2021-01-09 20:54:55.061	warn	(382018) State "hm-rpc.3.CENTRAL.PONG" has no existing object, this might lead to an error in future versions

                                  EDIT ON
                                  Update auf hm-rpc@1.14.27 behebt den PONG Fehler
                                  THX @foxriver76
                                  EDIT OFF

                                  Feuersturm 1 Reply Last reply Reply Quote 0
                                  • SBorg
                                    SBorg Forum Testing Most Active last edited by

                                    Die 3.2.4 läuft bis jetzt sehr gut 😁

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

                                      @apollon77 sagte in Beta Test js-controller 3.2.x auf GitHub:

                                      @Homoran timeout ... wüsste nicht was das sein kann. Mal ccu restarted?

                                      Hier spinnt anscheinend gerade alles - 4 parallele Installationen.
                                      Die produktive aktualisiert noch, zwei andere haben Verbindung,
                                      rpc.0 mit rfd klappt aber auch nur rpc.1 mit HmIP nicht
                                      controller_3_2_4.png

                                      1 Reply Last reply Reply Quote 0
                                      • Issi
                                        Issi Developer last edited by Issi

                                        Hi, ich habe da glaube was gefunden wen man ein state erstellt mit einem def Wert wird er Orange dargestellt und die Quality zeigt [0x20] an hab es mit einem frisch installierten adapter und direkt in den ioBroker Objekten unter 0_userdata probiert beides dasselbe im log steht nichts drin
                                        Screenshot_12.png
                                        ist das jetzt ein feature oder ein bug 😕

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

                                          Ich habe gerade mal meinen ioBroker Container geclont und den js-controller 3.2.4 installiert.
                                          Beim update kamen folgende Meldungen:

                                          proxmox@ioBrokerBETA:/opt/iobroker$ npm install ioBroker/ioBroker.js-controller
[sudo] password for proxmox: 

> iobroker.js-controller@3.2.4 preinstall /opt/iobroker/node_modules/iobroker.js-controller
> node lib/preinstallCheck.js

NPM version: 6.14.6

> iobroker.js-controller@3.2.4 install /opt/iobroker/node_modules/iobroker.js-controller
> node iobroker.js setup first

object 0_userdata.0.example_state created
object _design/system updated

The following notifications happened during sync: 
- Ignoring Directory "iogo.admin" because officially not created as meta object. Please remove directory!
- Ignoring Directory "tr-064-community.admin" because officially not created as meta object. Please remove directory!

Renamed repository "default to "stable"
Renamed repository "latest to "beta"

> @root/acme@3.1.0 postinstall /opt/iobroker/node_modules/@root/acme
> node scripts/postinstall

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.1 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.7 (node_modules/osx-temperature-sensor):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

+ iobroker.js-controller@3.2.4
added 44 packages from 16 contributors, removed 53 packages, updated 40 packages and moved 1 package in 102.359s

35 packages are looking for funding
  run `npm fund` for details

                                          proxmox@ioBrokerBETA:/opt/iobroker$ nodejs -v
v12.18.3
proxmox@ioBrokerBETA:/opt/iobroker$ node -v
v12.18.3
proxmox@ioBrokerBETA:/opt/iobroker$ npm -v
6.14.6

                                          Bei socketio v 3.1.2 ( @apollon77 ) kommt folgende Warnung
                                          Edit Issue https://github.com/ioBroker/ioBroker.socketio/issues/40

                                          socketio.0	2021-01-09 22:33:47.854	warn	(3964) State "socketio.0.connected" has no existing object, this might lead to an error in future versions

                                          Ich habe den Pong Fehlter auch mit der 1.14.27
                                          HomeMatic RPC - 1.14.27 ( @foxriver76 )

                                          hm-rpc.0	2021-01-09 22:34:48.960	warn	(3530) State "hm-rpc.0.CENTRAL.0.PONG" has no existing object, this might lead to an error in future versions

                                          Ebenfalls kommen beim HmIPW-DRAP vom Adapter hm-rpc folgende Warnungen:
                                          Edit: Issue: https://github.com/ioBroker/ioBroker.hm-rpc/issues/298

                                          hm-rpc.0	2021-01-09 22:35:09.066	warn	(3530) State "hm-rpc.0.00179A4989A6AB.2.CURRENT" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 22:35:09.059	warn	(3530) State "hm-rpc.0.00179A4989A6AB.2.CURRENT_STATUS" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 22:35:09.055	warn	(3530) State "hm-rpc.0.00179A4989A6AB.2.VOLTAGE" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 22:35:09.054	warn	(3530) State "hm-rpc.0.00179A4989A6AB.2.VOLTAGE_STATUS" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 22:35:09.053	warn	(3530) State "hm-rpc.0.00179A4989A6AB.1.CURRENT" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 22:35:09.052	warn	(3530) State "hm-rpc.0.00179A4989A6AB.1.CURRENT_STATUS" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 22:35:09.051	warn	(3530) State "hm-rpc.0.00179A4989A6AB.1.VOLTAGE" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 22:35:09.050	warn	(3530) State "hm-rpc.0.00179A4989A6AB.1.VOLTAGE_STATUS" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 22:35:09.049	warn	(3530) State "hm-rpc.0.00179A4989A6AB.0.ERROR_CODE" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 22:35:09.048	warn	(3530) State "hm-rpc.0.00179A4989A6AB.0.ACTUAL_TEMPERATURE" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 22:35:09.046	warn	(3530) State "hm-rpc.0.00179A4989A6AB.0.ERROR_BUS_CONFIG_MISMATCH" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 22:35:09.045	warn	(3530) State "hm-rpc.0.00179A4989A6AB.0.ERROR_SHORT_CIRCUIT_DATA_LINE_BUS_1" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 22:35:09.044	warn	(3530) State "hm-rpc.0.00179A4989A6AB.0.ERROR_SHORT_CIRCUIT_DATA_LINE_BUS_2" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 22:35:09.043	warn	(3530) State "hm-rpc.0.00179A4989A6AB.0.ERROR_OVERHEAT" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 22:35:09.042	warn	(3530) State "hm-rpc.0.00179A4989A6AB.0.ERROR_POWER_SHORT_CIRCUIT_BUS_1" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 22:35:09.040	warn	(3530) State "hm-rpc.0.00179A4989A6AB.0.ERROR_POWER_SHORT_CIRCUIT_BUS_2" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 22:35:09.037	warn	(3530) State "hm-rpc.0.00179A4989A6AB.0.VOLTAGE" has no existing object, this might lead to an error in future versions
hm-rpc.0	2021-01-09 22:35:09.036	warn	(3530) State "hm-rpc.0.00179A4989A6AB.0.ERROR_UNDERVOLTAGE" has no existing object, this might lead to an error in future versions
                                          Feuer-sturm created this issue in ioBroker/ioBroker.socketio

                                          closed Warnung "has no existing object," beim Beta-Test von js-controller 3.2.x #40

                                          Feuer-sturm created this issue in ioBroker/ioBroker.hm-rpc

                                          closed Warnung "has no existing object," für HMIPw-DRAP beim Beta-Test von js-controller 3.2.x #298

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

                                            @Issi "feature" ... steht auch im changelog. Damit soll dargestellt werden da der wert nicht vom Gerät kam und auch nicht vom User oder einem Adapter gesetzt wurde.

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            854
                                            Online

                                            31.7k
                                            Users

                                            79.8k
                                            Topics

                                            1.3m
                                            Posts

                                            js-controller
                                            25
                                            287
                                            32850
                                            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