Adapter legt keine Objekte in Objektliste an

[trave356]

Danke fürs Update des Adapters!
Bei mir funktioniert die Kommunikation mit der XS1, allerdings sind die Objektlisten unter Actuators und Sensors leer. Zugriff via getState funktioniert. Allerdings kommen entsprechende Warnings, dass die States keine Objekte haben.
node v18.18.1
npm 9.8.1
admin v6.10.1
(tritt mit 1.1.2 auf)

Log:

2023-10-13 17:59:14.095 - info: host.raspberrypi "system.adapter.xs1.0" enabled
2023-10-13 17:59:14.490 - info: host.raspberrypi instance system.adapter.xs1.0 started with pid 5423
2023-10-13 17:59:16.946 - debug: xs1.0 (5423) Redis Objects: Use Redis connection: 127.0.0.1:9001
2023-10-13 17:59:17.001 - debug: xs1.0 (5423) Objects client ready ... initialize now
2023-10-13 17:59:17.004 - debug: xs1.0 (5423) Objects create System PubSub Client
2023-10-13 17:59:17.006 - debug: xs1.0 (5423) Objects create User PubSub Client
2023-10-13 17:59:17.099 - debug: xs1.0 (5423) Objects client initialize lua scripts
2023-10-13 17:59:17.111 - debug: xs1.0 (5423) Objects connected to redis: 127.0.0.1:9001
2023-10-13 17:59:17.117 - silly: xs1.0 (5423) redis psubscribe cfg.o.system.user.*
2023-10-13 17:59:17.165 - silly: xs1.0 (5423) redis psubscribe cfg.o.enum.*
2023-10-13 17:59:17.168 - silly: xs1.0 (5423) objectDB connected
2023-10-13 17:59:17.172 - debug: xs1.0 (5423) Redis States: Use Redis connection: 127.0.0.1:9000
2023-10-13 17:59:17.197 - debug: xs1.0 (5423) States create System PubSub Client
2023-10-13 17:59:17.199 - debug: xs1.0 (5423) States create User PubSub Client
2023-10-13 17:59:17.246 - debug: xs1.0 (5423) States connected to redis: 127.0.0.1:9000
2023-10-13 17:59:17.248 - silly: xs1.0 (5423) statesDB connected
2023-10-13 17:59:17.586 - info: xs1.0 (5423) starting. Version 1.1.2 (non-npm: iobroker-community-adapters/ioBroker.xs1#1fd2d8d672628d7bd92786eadd02846ad3914ca9) in /opt/iobroker/node_modules/iobroker.xs1, node: v18.18.1, js-controller: 5.0.12
2023-10-13 17:59:17.656 - silly: xs1.0 (5423) States system redis pmessage system.adapter.xs1.0.logLevel/system.adapter.xs1.0.logLevel:{"val":"silly","ack":true,"ts":1697212757631,"q":0,"from":"system.adapter.xs1.0","lc":1697212476805}
2023-10-13 17:59:17.656 - info: javascript.0 (14759) State value to set for "javascript.0.Adapterüberwachung.Fehlerliste" has to be one of type "string", "number", "boolean" but received type "object"
2023-10-13 17:59:19.658 - info: xs1.0 (5423) xs1 initialization started...
2023-10-13 17:59:19.659 - info: xs1.0 (5423) xs1 starting main...
2023-10-13 17:59:19.660 - info: xs1.0 (5423) config XS1 Addresse: http://192.168.1.242:80
2023-10-13 17:59:19.664 - info: xs1.0 (5423) CopyList = {}
2023-10-13 17:59:20.150 - info: xs1.0 (5423) Finished state creation. Added totally 27 actuators or sensors
2023-10-13 17:59:34.647 - warn: xs1.0 (5423) State "xs1.0.Sensors.dummy" has no existing object, this might lead to an error in future versions
2023-10-13 17:59:34.650 - warn: xs1.0 (5423) State "xs1.0.Sensors.TP_Keller" has no existing object, this might lead to an error in future versions
2023-10-13 17:59:34.663 - warn: xs1.0 (5423) State "xs1.0.Sensors.dummy" has no existing object, this might lead to an error in future versions
2023-10-13 17:59:34.669 - warn: xs1.0 (5423) State "xs1.0.Sensors.TP_aussen" has no existing object, this might lead to an error in future versions
2023-10-13 17:59:34.671 - warn: xs1.0 (5423) State "xs1.0.Sensors.TP_Keller_m7" has no existing object, this might lead to an error in future versions
2023-10-13 17:59:34.675 - silly: xs1.0 (5423) States user redis pmessage xs1.0./xs1.0.Sensors.dummy:{"val":-0.3,"ack":true,"ts":1697212774666,"q":0,"from":"system.adapter.xs1.0","user":"system.user.admin","lc":1697212594786}
2023-10-13 17:59:34.679 - silly: xs1.0 (5423) States user redis pmessage xs1.0./xs1.0.Sensors.TP_Keller:{"val":15.1,"ack":true,"ts":1697212774666,"q":0,"from":"system.adapter.xs1.0","user":"system.user.admin","lc":1697212594778}
2023-10-13 17:59:34.683 - silly: xs1.0 (5423) States user redis pmessage xs1.0./xs1.0.Sensors.dummy:{"val":-0.3,"ack":true,"ts":1697212774669,"q":0,"from":"system.adapter.xs1.0","user":"system.user.admin","lc":1697212594786}
2023-10-13 17:59:34.684 - warn: xs1.0 (5423) State "xs1.0.Sensors.TP_diff" has no existing object, this might lead to an error in future versions
2023-10-13 17:59:34.690 - silly: xs1.0 (5423) States user redis pmessage xs1.0./xs1.0.Sensors.TP_aussen:{"val":16,"ack":true,"ts":1697212774685,"q":0,"from":"system.adapter.xs1.0","user":"system.user.admin","lc":1697212594792}
2023-10-13 17:59:34.692 - silly: xs1.0 (5423) States user redis pmessage xs1.0./xs1.0.Sensors.TP_Keller_m7:{"val":15.1,"ack":true,"ts":1697212774686,"q":0,"from":"system.adapter.xs1.0","user":"system.user.admin","lc":1697212774686}
2023-10-13 17:59:34.696 - silly: xs1.0 (5423) States user redis pmessage xs1.0./xs1.0.Sensors.TP_diff:{"val":-0.8,"ack":true,"ts":1697212774688,"q":0,"from":"system.adapter.xs1.0","user":"system.user.admin","lc":1697212594794}

[Trashman1981]

Ich habe ein ganz ähnliches Problem (kann die Aktoren nicht finden), allerdings bekomme ich ein etwas andere Fehlermeldung:

Das ist die Reaktion von Watchdog (1x jede Minute)
xs1.0 | 2023-10-17 21:08:56.724 | warn | State "xs1.0.Actuators.Watchdog" has no existing object, this might lead to an error in future versions

Das ist das Feedback vom Adapter im Log, wenn ich den XS1 über den Browser schalte:

xs1.0	2023-10-17 21:15:34.518	warn	State "xs1.0.Actuators.Schlafzimmer" has no existing object, this might lead to an error in future versions

Das kommt, wenn der Adapter aktiviert wird:

xs1.0	2023-10-17 21:06:56.669	info	Finished state creation. Added totally 12 actuators or sensors
xs1.0	2023-10-17 21:06:56.141	info	CopyList = {}
xs1.0	2023-10-17 21:06:56.136	info	config XS1 Addresse: http://192.168.188.50:80
xs1.0	2023-10-17 21:06:56.133	info	xs1 starting main...
xs1.0	2023-10-17 21:06:56.131	info	xs1 initialization started...
xs1.0	2023-10-17 21:06:55.333	info	starting. Version 1.1.2 in /opt/iobroker/node_modules/iobroker.xs1, node: v18.18.0, js-controller: 5.0.12

Über Hilfe bin ich natürlich immer sehr Dankbar :-)

Gruss, Trashman1981

[markTrier]

Gleiches Problem. Adapter 1.1.2 läuft, Actuators und Sensors bleiben leer.
Protokoll:

2023-10-23 20:14:06.567	warn	State "xs1.0.Sensors.WoZi_Ventil" has no existing object, this might lead to an error in future versions
xs1.0	2023-10-23 20:14:06.555	warn
xs1.0	2023-10-23 20:13:36.830	warn
xs1.0	2023-10-23 20:12:36.803	warn
xs1.0	2023-10-23 20:12:16.998	warn
xs1.0	2023-10-23 20:12:16.989	warn
xs1.0	2023-10-23 20:11:45.591	warn
xs1.0	2023-10-23 20:11:36.805	warn
xs1.0	2023-10-23 20:10:54.766	warn
xs1.0	2023-10-23 20:10:54.763	warn

[007Schneiderlein]

Habe leider auch das gleiche Problem wie trave356

Aber jetzt erstmal ein dickes Dankeschön für den Adapter und dessen Pflege 💪🙏

BG Stefan

[markTrier]

Schon jemand eine Lösung gefunden?

[trave356]

Anscheinend nicht, das Problem besteht zumindest bei mir weiter.
Bei
https://forum.iobroker.net/topic/3516/mein-erster-adapter-f%C3%BCr-ezcontrol-xs1/125?lang=de
scheint es eine Lösung zu geben, aber für mich leider nicht reproduzierbar.

[markTrier]

Vielleicht hilft u. g. Protokollauszug ja weiter, der sich so alle paar Minuten wiederholt. Es zeigt mir (Laie-Amateur), dass der Adapter läuft, die Objekte irgendwie von der ez-control an den iobroker "übergeben" werden, aber dann doch Fehler generieren, die dazu führen, dass die Objekte nicht da erscheinen, wo sie eigentlich sollen und ich folglich nicht damit arbeiten kann.

2023-11-20 22:31:43.852 - warn: xs1.0 (5251) State "xs1.0.Actuators.Watchdog" has no existing object, this might lead to an error in future versions -- 2023-11-20 22:32:16.787 - warn: xs1.0 (5251) State "xs1.0.Actuators.AZ_Heiz" has no existing object, this might lead to an error in future versions 2023-11-20 22:32:16.795 - warn: xs1.0 (5251) State "xs1.0.Sensors.AZ_Temp" has no existing object, this might lead to an error in future versions 2023-11-20 22:32:16.796 - warn: xs1.0 (5251) State "xs1.0.Sensors.AZ_Ventil" has no existing object, this might lead to an error in future versions 2023-11-20 22:32:43.855 - warn: xs1.0 (5251) State "xs1.0.Actuators.Watchdog" has no existing object, this might lead to an error in future versions 2023-11-20 22:33:43.856 - warn: xs1.0 (5251) State "xs1.0.Actuators.Watchdog" has no existing object, this might lead to an error in future versions 2023-11-20 22:34:43.857 - warn: xs1.0 (5251) State "xs1.0.Actuators.Watchdog" has no existing object, this might lead to an error in future versions 2023-11-20 22:35:23.592 - warn: xs1.0 (5251) State "xs1.0.Sensors.Bad_Fenster" has no existing object, this might lead to an error in future versions 2023-11-20 22:35:43.873 - warn: xs1.0 (5251) State "xs1.0.Actuators.Watchdog" has no existing object, this might lead to an error in future versions 2023-11-20 22:36:43.860 - warn: xs1.0 (5251) State "xs1.0.Actuators.Watchdog" has no existing object, this might lead to an error in future versions 2023-11-20 22:37:43.861 - warn: xs1.0 (5251) State "xs1.0.Actuators.Watchdog" has no existing object, this might lead to an error in future versions 2023-11-20 22:38:43.859 - warn: xs1.0 (5251) State "xs1.0.Actuators.Watchdog" has no existing object, this might lead to an error in future versions 2023-11-20 22:39:17.165 - warn: xs1.0 (5251) State "xs1.0.Sensors.WoZi_Ventil" has no existing object, this might lead to an error in future versions 2023-11-20 22:39:35.597 - warn: xs1.0 (5251) State "xs1.0.Sensors.Bad_Fenster" has no existing object, this might lead to an error in future versions 2023-11-20 22:39:43.884 - warn: xs1.0 (5251) State "xs1.0.Actuators.Watchdog" has no existing object, this might lead to an error in future versions 2023-11-20 22:40:43.862 - warn: xs1.0 (5251) State "xs1.0.Actuators.Watchdog" has no existing object, this might lead to an error in future versions 2023-11-20 22:41:13.440 - warn: xs1.0 (5251) State "xs1.0.Sensors.WoZi_Ventil" has no existing object, this might lead to an error in future versions 2023-11-20 22:41:43.877 - warn: xs1.0 (5251) State "xs1.0.Actuators.Watchdog" has no existing object, this might lead to an error in future versions 2023-11-20 22:42:43.869 - warn: xs1.0 (5251) State "xs1.0.Actuators.Watchdog" has no existing object, this might lead to an error in future versions 2023-11-20 22:43:12.303 - warn: xs1.0 (5251) State "xs1.0.Actuators.WoZi_Heiz" has no existing object, this might lead to an error in future versions 2023-11-20 22:43:12.314 - warn: xs1.0 (5251) State "xs1.0.Sensors.WoZi_Temp" has no existing object, this might lead to an error in future versions 2023-11-20 22:43:12.316 - warn: xs1.0 (5251) State "xs1.0.Sensors.WoZi_Ventil" has no existing object, this might lead to an error in future versions 2023-11-20 22:43:26.103 - warn: xs1.0 (5251) State "xs1.0.Sensors.Kueche_Temp" has no existing object, this might lead to an error in future versions 2023-11-20 22:43:26.110 - warn: xs1.0 (5251) State "xs1.0.Sensors.Kueche_Ventil" has no existing object, this might lead to an error in future versions 2023-11-20 22:43:43.860 - warn: xs1.0 (5251) State "xs1.0.Actuators.Watchdog" has no existing object, this might lead to an error in future versions 2023-11-20 22:43:48.217 - warn: xs1.0 (5251) State "xs1.0.Sensors.AZ_Ventil" has no existing object, this might lead to an error in future versions 2023-11-20 22:44:43.867 - warn: xs1.0 (5251) State "xs1.0.Actuators.Watchdog" has no existing object, this might lead to an error in future versions 2023-11-20 22:45:22.830 - warn: xs1.0 (5251) State "xs1.0.Sensors.Kueche_Ventil" has no existing object, this might lead to an error in future versions 2023-11-20 22:45:43.893 - warn: xs1.0 (5251) State "xs1.0.Actuators.Watchdog" has no existing object, this might lead to an error in future versions 2023-11-20 22:46:43.870 - warn: xs1.0 (5251) State "xs1.0.Actuators.Watchdog" has no existing object, this might lead to an error in future versions

[radebold]

Gibt es hier etwas Neues?

[mcm1957]

Mail from 3.1.2024 for reference

Hi Martin,

jepp genau diesen Fehler meine ich.
Beim starten des Adapters werden zwar die Object-Folder angelegt, jedoch die einzelnen Objekte nicht.
Wenn dann Daten kommen motzt das System, da die Objekte/States nicht vorhanden sind.

Manuell kann man die Objekte anlegen und es wird auch geupdatet, aber das ist recht aufwändig.
Ich habe versucht per jacascript das logfile auszulesen und mit createstate dann anzulegen, aber das macht er halt nicht im XS1 Objectfolder, sondern unter javascript oder userdata :-)


Danke Dir

Gruß
...