NEWS
Test Adapter fb-checkpresence v1.1.x
-
@afuerhoff said in Test Adapter fb-checkpresence v1.1.x:
Hallo,
ich habe die Version 1.1.2 auf Github zum Testen veröffentlicht. Die Änderungen sind im ersten Beitrag beschrieben. Bitte gebt Rückmeldung, ob alles funktioniert.
habe jetzt folgende Eintragungen im Log:
2021-01-14 07:32:33.719 - info: fb-checkpresence.0 (5072) New interface found: fritz-box.LANBridge 2021-01-14 07:32:33.720 - warn: fb-checkpresence.0 (5072) createMeshObjects: {} 2021-01-14 07:32:33.720 - info: fb-checkpresence.0 (5072) New interface found: fritz-box.LAN:1 2021-01-14 07:32:33.720 - warn: fb-checkpresence.0 (5072) createMeshObjects: {} 2021-01-14 07:32:33.721 - info: fb-checkpresence.0 (5072) New interface found: fritz-box.LAN:2 2021-01-14 07:32:33.721 - warn: fb-checkpresence.0 (5072) createMeshObjects: {} 2021-01-14 07:32:33.721 - info: fb-checkpresence.0 (5072) New interface found: fritz-box.LAN:3 2021-01-14 07:32:33.722 - warn: fb-checkpresence.0 (5072) createMeshObjects: {} 2021-01-14 07:32:33.722 - info: fb-checkpresence.0 (5072) New interface found: fritz-box.LAN:4 2021-01-14 07:32:33.722 - warn: fb-checkpresence.0 (5072) createMeshObjects: {} 2021-01-14 07:32:33.722 - info: fb-checkpresence.0 (5072) New interface found: fritz-box.WAN:1 2021-01-14 07:32:33.723 - warn: fb-checkpresence.0 (5072) createMeshObjects: {} 2021-01-14 07:32:33.723 - info: fb-checkpresence.0 (5072) New interface found: fritz-box.GUEST:5G:0 2021-01-14 07:32:33.723 - warn: fb-checkpresence.0 (5072) createMeshObjects: {} 2021-01-14 07:32:33.723 - info: fb-checkpresence.0 (5072) New interface found: fritz-box.GUEST:2G:0 2021-01-14 07:32:33.724 - warn: fb-checkpresence.0 (5072) createMeshObjects: {} 2021-01-14 07:32:33.724 - info: fb-checkpresence.0 (5072) New interface found: fritz-box.AP:5G:0 2021-01-14 07:32:33.724 - warn: fb-checkpresence.0 (5072) createMeshObjects: {} 2021-01-14 07:32:33.725 - info: fb-checkpresence.0 (5072) New interface found: fritz-box.AP:2G:0 2021-01-14 07:32:33.725 - warn: fb-checkpresence.0 (5072) createMeshObjects: {} 2021-01-14 07:43:11.613 - info: fb-checkpresence.0 (5072) New interface found: fritz-box.LANBridge 2021-01-14 07:43:11.614 - warn: fb-checkpresence.0 (5072) createMeshObjects: {} 2021-01-14 07:43:11.615 - info: fb-checkpresence.0 (5072) New interface found: fritz-box.LAN:1 2021-01-14 07:43:11.615 - warn: fb-checkpresence.0 (5072) createMeshObjects: {} 2021-01-14 07:43:11.616 - info: fb-checkpresence.0 (5072) New interface found: fritz-box.LAN:2 2021-01-14 07:43:11.616 - warn: fb-checkpresence.0 (5072) createMeshObjects: {} 2021-01-14 07:43:11.616 - info: fb-checkpresence.0 (5072) New interface found: fritz-box.LAN:3 2021-01-14 07:43:11.617 - warn: fb-checkpresence.0 (5072) createMeshObjects: {} 2021-01-14 07:43:11.617 - info: fb-checkpresence.0 (5072) New interface found: fritz-box.LAN:4 2021-01-14 07:43:11.618 - warn: fb-checkpresence.0 (5072) createMeshObjects: {} 2021-01-14 07:43:11.618 - info: fb-checkpresence.0 (5072) New interface found: fritz-box.WAN:1 2021-01-14 07:43:11.618 - warn: fb-checkpresence.0 (5072) createMeshObjects: {} 2021-01-14 07:43:11.618 - info: fb-checkpresence.0 (5072) New interface found: fritz-box.GUEST:5G:0 2021-01-14 07:43:11.619 - warn: fb-checkpresence.0 (5072) createMeshObjects: {} 2021-01-14 07:43:11.619 - info: fb-checkpresence.0 (5072) New interface found: fritz-box.GUEST:2G:0 2021-01-14 07:43:11.619 - warn: fb-checkpresence.0 (5072) createMeshObjects: {} 2021-01-14 07:43:11.620 - info: fb-checkpresence.0 (5072) New interface found: fritz-box.AP:5G:0 2021-01-14 07:43:11.620 - warn: fb-checkpresence.0 (5072) createMeshObjects: {} 2021-01-14 07:43:11.620 - info: fb-checkpresence.0 (5072) New interface found: fritz-box.AP:2G:0 2021-01-14 07:43:11.620 - warn: fb-checkpresence.0 (5072) createMeshObjects: {}alle 11 Minuten
bis denne
@fenriswolf said in Test Adapter fb-checkpresence v1.1.x:
habe jetzt folgende Eintragungen im Log
Da hat sich ein Fehler eingeschlichen. Korrigiere ich.
-
Kann ich bestätigen.
Es werden auch keine Devices angelegt.
Wobei ich die Beta vom JS controller Installiert: 3.2.6-0 habe.
Dadurch kommen auch massenweise diese Warn:fb-checkpresence.0 2021-01-14 10:35:15.977 warn (5232) State "fb-checkpresence.0.fb-devices.fritz-box.AP:2G:0.link" has no existing object, this might lead to an error in future versions fb-checkpresence.0 2021-01-14 10:35:15.976 warn (5232) State "fb-checkpresence.0.fb-devices.fritz-box.AP:2G:0.cur_data_rate_tx" has no existing object, this might lead to an error in future versions fb-checkpresence.0 2021-01-14 10:35:15.976 warn (5232) State "fb-checkpresence.0.fb-devices.fritz-box.AP:2G:0.cur_data_rate_rx" has no existing object, this might lead to an error in future versions
Ich habe ein Update hochgeladen. Bitte neu testen. Am Besten einmal die Objekte unter fb-devices löschen. Die sind falsch angelegt worden.
Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
-
Ich habe ein Update hochgeladen. Bitte neu testen. Am Besten einmal die Objekte unter fb-devices löschen. Die sind falsch angelegt worden.
@afuerhoff said in Test Adapter fb-checkpresence v1.1.x:
Ich habe ein Update hochgeladen. Bitte neu testen. Am Besten einmal die Objekte unter fb-devices löschen. Die sind falsch angelegt worden.
Schaut wieder gut aus. Bis auf die Warn wegen Beta JS Controller.
Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
Immer Daten sichern! -
@afuerhoff said in Test Adapter fb-checkpresence v1.1.x:
Ich habe ein Update hochgeladen. Bitte neu testen. Am Besten einmal die Objekte unter fb-devices löschen. Die sind falsch angelegt worden.
Schaut wieder gut aus. Bis auf die Warn wegen Beta JS Controller.
-
@sigi234
Welche Warnungen meinst du ? Die vom Post oben?
Hast Du die Objekte einmal gelöscht?@afuerhoff said in Test Adapter fb-checkpresence v1.1.x:
Hast Du die Objekte einmal gelöscht?
Ja
Log:
2021-01-14 21:51:08.500 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.CCU3.LAN.name" has no existing object, this might lead to an error in future versions 2021-01-14 21:51:08.501 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.CCU3.LAN.link" has no existing object, this might lead to an error in future versions 2021-01-14 21:51:08.501 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.CCU3.LAN.rx_rcpi" has no existing object, this might lead to an error in future versions 2021-01-14 21:51:08.501 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.CCU3.LAN.cur_data_rate_rx" has no existing object, this might lead to an error in future versions 2021-01-14 21:51:08.501 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.CCU3.LAN.cur_data_rate_tx" has no existing object, this might lead to an error in future versions 2021-01-14 21:51:08.501 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.CCU3.LAN.type" has no existing object, this might lead to an error in future versions 2021-01-14 21:51:08.502 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.Dot-Bad.WLAN.name" has no existing object, this might lead to an error in future versions 2021-01-14 21:51:08.502 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.Dot-Bad.WLAN.link" has no existing object, this might lead to an error in future versions 2021-01-14 21:51:08.502 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.Dot-Bad.WLAN.rx_rcpi" has no existing object, this might lead to an error in future versions 2021-01-14 21:51:08.502 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.Dot-Bad.WLAN.cur_data_rate_rx" has no existing object, this might lead to an error in future versions 2021-01-14 21:51:08.502 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.Dot-Bad.WLAN.cur_data_rate_tx" has no existing object, this might lead to an error in future versions 2021-01-14 21:51:08.502 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.Dot-Bad.WLAN.type" has no existing object, this might lead to an error in future versions 2021-01-14 21:51:08.503 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.Dot-Buero.WLAN.name" has no existing object, this might lead to an error in future versions 2021-01-14 21:51:08.503 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.Dot-Buero.WLAN.link" has no existing object, this might lead to an error in future versionsBitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
Immer Daten sichern! -
@afuerhoff said in Test Adapter fb-checkpresence v1.1.x:
Hast Du die Objekte einmal gelöscht?
Ja
Log:
2021-01-14 21:51:08.500 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.CCU3.LAN.name" has no existing object, this might lead to an error in future versions 2021-01-14 21:51:08.501 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.CCU3.LAN.link" has no existing object, this might lead to an error in future versions 2021-01-14 21:51:08.501 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.CCU3.LAN.rx_rcpi" has no existing object, this might lead to an error in future versions 2021-01-14 21:51:08.501 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.CCU3.LAN.cur_data_rate_rx" has no existing object, this might lead to an error in future versions 2021-01-14 21:51:08.501 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.CCU3.LAN.cur_data_rate_tx" has no existing object, this might lead to an error in future versions 2021-01-14 21:51:08.501 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.CCU3.LAN.type" has no existing object, this might lead to an error in future versions 2021-01-14 21:51:08.502 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.Dot-Bad.WLAN.name" has no existing object, this might lead to an error in future versions 2021-01-14 21:51:08.502 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.Dot-Bad.WLAN.link" has no existing object, this might lead to an error in future versions 2021-01-14 21:51:08.502 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.Dot-Bad.WLAN.rx_rcpi" has no existing object, this might lead to an error in future versions 2021-01-14 21:51:08.502 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.Dot-Bad.WLAN.cur_data_rate_rx" has no existing object, this might lead to an error in future versions 2021-01-14 21:51:08.502 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.Dot-Bad.WLAN.cur_data_rate_tx" has no existing object, this might lead to an error in future versions 2021-01-14 21:51:08.502 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.Dot-Bad.WLAN.type" has no existing object, this might lead to an error in future versions 2021-01-14 21:51:08.503 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.Dot-Buero.WLAN.name" has no existing object, this might lead to an error in future versions 2021-01-14 21:51:08.503 - warn: fb-checkpresence.0 (13616) State "fb-checkpresence.0.fb-devices.Dot-Buero.WLAN.link" has no existing object, this might lead to an error in future versions -
Kannst Du mal ein Bild der entsprechenden Objekte posten. CCU3 sollte z.B. als Device angelegt sein.
@afuerhoff said in Test Adapter fb-checkpresence v1.1.x:
Kannst Du mal ein Bild der entsprechenden Objekte posten. CCU3 sollte z.B. als Device angelegt sein.
RAW Lan Name:
{ "from": "system.adapter.fb-checkpresence.0", "user": "system.user.admin", "ts": 1610657469997, "common": { "name": "fb-devices.CCU3.LAN.name", "desc": "name of the interface", "role": "value", "type": "string", "def": "", "read": true, "write": false }, "native": {}, "acl": { "object": 1636, "owner": "system.user.admin", "ownerGroup": "system.group.administrator", "state": 1636 }, "_id": "fb-checkpresence.0.fb-devices.CCU3.LAN.name", "type": "state" }Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
Immer Daten sichern! -
@afuerhoff said in Test Adapter fb-checkpresence v1.1.x:
Kannst Du mal ein Bild der entsprechenden Objekte posten. CCU3 sollte z.B. als Device angelegt sein.
RAW Lan Name:
{ "from": "system.adapter.fb-checkpresence.0", "user": "system.user.admin", "ts": 1610657469997, "common": { "name": "fb-devices.CCU3.LAN.name", "desc": "name of the interface", "role": "value", "type": "string", "def": "", "read": true, "write": false }, "native": {}, "acl": { "object": 1636, "owner": "system.user.admin", "ownerGroup": "system.group.administrator", "state": 1636 }, "_id": "fb-checkpresence.0.fb-devices.CCU3.LAN.name", "type": "state" } -
Ich habe ein Update hochgeladen. Bitte neu testen. Am Besten einmal die Objekte unter fb-devices löschen. Die sind falsch angelegt worden.
@afuerhoff said in Test Adapter fb-checkpresence v1.1.x:
Ich habe ein Update hochgeladen. Bitte neu testen. Am Besten einmal die Objekte unter fb-devices löschen. Die sind falsch angelegt worden.
Werde ich morgen im Laufe des Tages testen und berichten.
-
@sigi234
Da verstehe ich die Meldung vom JS-Controller nicht. Ist doch als Objekt angelegt.@afuerhoff said in Test Adapter fb-checkpresence v1.1.x:
@sigi234
Da verstehe ich die Meldung vom JS-Controller nicht. Ist doch als Objekt angelegt.Ja, ist bei andere Adapter auch so.
Neueste Meldung:
fb-checkpresence.0 2021-01-14 22:42:56.416 error (8292) soapAction xml2js GetInfo status=500 errNo=4 401 Invalid ActionBitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
Immer Daten sichern! -
@afuerhoff said in Test Adapter fb-checkpresence v1.1.x:
@sigi234
Da verstehe ich die Meldung vom JS-Controller nicht. Ist doch als Objekt angelegt.Ja, ist bei andere Adapter auch so.
Neueste Meldung:
fb-checkpresence.0 2021-01-14 22:42:56.416 error (8292) soapAction xml2js GetInfo status=500 errNo=4 401 Invalid Action -
@sigi234
Kannst Du mal das Log vom Start an posten. Da kommen die Meldungen was alles unterstützt wird.@afuerhoff said in Test Adapter fb-checkpresence v1.1.x:
@sigi234
Kannst Du mal das Log vom Start an posten. Da kommen die Meldungen was alles unterstützt wird.fb-checkpresence.0 2021-01-14 23:06:34.085 debug (9028) loopFamily ends after 5,187158400 s fb-checkpresence.0 2021-01-14 23:06:33.426 debug (9028) Handy-xxx: No history item before this day is available fb-checkpresence.0 2021-01-14 23:06:33.426 debug (9028) history Handy-xxx cntHistory: 15421 fb-checkpresence.0 2021-01-14 23:06:33.230 debug (9028) sendTo "getHistory" to system.adapter.history.0 from system.adapter.fb-checkpresence.0 fb-checkpresence.0 2021-01-14 23:06:33.230 debug (9028) history cntActualDay: 15422 fb-checkpresence.0 2021-01-14 23:06:33.059 debug (9028) sendTo "getHistory" to system.adapter.history.0 from system.adapter.fb-checkpresence.0 fb-checkpresence.0 2021-01-14 23:06:32.102 debug (9028) Handy-Ilse: No history item before this day is available fb-checkpresence.0 2021-01-14 23:06:32.102 debug (9028) history Handy-xxxx cntHistory: 15424 fb-checkpresence.0 2021-01-14 23:06:31.869 debug (9028) sendTo "getHistory" to system.adapter.history.0 from system.adapter.fb-checkpresence.0 fb-checkpresence.0 2021-01-14 23:06:31.869 debug (9028) history cntActualDay: 15425 fb-checkpresence.0 2021-01-14 23:06:31.622 debug (9028) sendTo "getHistory" to system.adapter.history.0 from system.adapter.fb-checkpresence.0 fb-checkpresence.0 2021-01-14 23:06:30.784 debug (9028) Handy-xxxxxx: No history item before this day is available fb-checkpresence.0 2021-01-14 23:06:30.783 debug (9028) history Handy-xxxxxx cntHistory: 15422 fb-checkpresence.0 2021-01-14 23:06:30.410 debug (9028) sendTo "getHistory" to system.adapter.history.0 from system.adapter.fb-checkpresence.0 fb-checkpresence.0 2021-01-14 23:06:30.409 debug (9028) history cntActualDay: 15423 fb-checkpresence.0 2021-01-14 23:06:29.928 debug (9028) sendTo "getHistory" to system.adapter.history.0 from system.adapter.fb-checkpresence.0 fb-checkpresence.0 2021-01-14 23:06:29.904 debug (9028) getDeviceList: [{"Index":"1","IPAddress":"192.168.178.99","MACAddress":"xxxxxxxxxx","Active":"1","HostName":"CCU3","InterfaceType":"Ethernet","X_AVM-DE_Port":"1","X_AVM-DE_Speed":"1000", fb-checkpresence.0 2021-01-14 23:05:37.540 info (9028) createFbDeviceObjects finished successfully fb-checkpresence.0 2021-01-14 23:05:36.457 debug (9028) getDeviceList: [{"Index":"1","IPAddress":"192.168.178.99","MACAddress":"xxxxxxx","Active":"1","HostName":"CCU3","InterfaceType":"Ethernet","X_AVM-DE_Port":"1","X_AVM-DE_Speed":"1000", fb-checkpresence.0 2021-01-14 23:05:35.845 debug (9028) system.adapter.admin.0: logging true fb-checkpresence.0 2021-01-14 23:05:35.693 info (9028) createMemberObjects finished successfully fb-checkpresence.0 2021-01-14 23:05:35.688 debug (9028) sendTo "getEnabledDPs" to system.adapter.history.0 from system.adapter.fb-checkpresence.0 fb-checkpresence.0 2021-01-14 23:05:35.594 debug (9028) sendTo "getEnabledDPs" to system.adapter.history.0 from system.adapter.fb-checkpresence.0 fb-checkpresence.0 2021-01-14 23:05:35.461 debug (9028) sendTo "getEnabledDPs" to system.adapter.history.0 from system.adapter.fb-checkpresence.0 fb-checkpresence.0 2021-01-14 23:05:35.367 info (9028) createGlobalObjects finished successfully fb-checkpresence.0 2021-01-14 23:05:35.159 debug (9028) ssl-port {"status":200,"result":true,"resultData":{"$":{"xmlns:u":"urn:dslforum-org:service:DeviceInfo:1"},"NewSecurityPort":"49443"},"errNo":0,"errorMsg":""} fb-checkpresence.0 2021-01-14 23:05:35.152 info (9028) service LANConfigSecurity1-X_AVM-DE_GetCurrentUser is supported fb-checkpresence.0 2021-01-14 23:05:35.148 info (9028) service DeviceConfig1-Reboot is supported fb-checkpresence.0 2021-01-14 23:05:35.143 info (9028) service X_AVM-DE_HostFilter-GetWANAccessByIP is supported fb-checkpresence.0 2021-01-14 23:05:35.139 info (9028) service X_AVM-DE_HostFilter-DisallowWANAccessByIP is supported fb-checkpresence.0 2021-01-14 23:05:35.134 info (9028) service DeviceInfo1-GetInfo is supported fb-checkpresence.0 2021-01-14 23:05:35.129 info (9028) service WLANConfiguration3-GetSecurityKeys is supported fb-checkpresence.0 2021-01-14 23:05:35.124 info (9028) service WLANConfiguration3-GetInfo is supported fb-checkpresence.0 2021-01-14 23:05:35.117 info (9028) service WLANConfiguration3-SetEnable is supported fb-checkpresence.0 2021-01-14 23:05:35.112 info (9028) service WANPPPConnection1-GetInfo is supported fb-checkpresence.0 2021-01-14 23:05:35.106 info (9028) service DeviceInfo1-GetSecurityPort is supported fb-checkpresence.0 2021-01-14 23:05:35.101 info (9028) service Hosts1-X_AVM-DE_GetSpecificHostEntryByIP is supported fb-checkpresence.0 2021-01-14 23:05:35.096 info (9028) service Hosts1-GetSpecificHostEntry is supported fb-checkpresence.0 2021-01-14 23:05:35.091 info (9028) service Hosts1-X_AVM-DE_GetMeshListPath is supported fb-checkpresence.0 2021-01-14 23:05:35.084 info (9028) service Hosts1-X_AVM-DE_GetHostListPath is supported fb-checkpresence.0 2021-01-14 23:05:35.078 debug (9028) services loaded successfully{"root":{"$":{"xmlns":"urn:dslforum-org:device-1-0"},"specVersion":{"major":"1","minor":"0"},"systemVersion":{"HW":"220","Major":"148","Minor":"7","Patch":"20","Bui fb-checkpresence.0 2021-01-14 23:05:34.984 debug (9028) configuratuion mesh info: true fb-checkpresence.0 2021-01-14 23:05:34.983 debug (9028) configuration fb-devices true fb-checkpresence.0 2021-01-14 23:05:34.983 debug (9028) configuration familymembers: [{"familymember":"Handy-xxxxxxxx-Privat","macaddress":"xxxxxxxxxx","ipaddress":"192.168.178.47","useip":true,"usename":true,"comment":"","enabled":true},{"famil fb-checkpresence.0 2021-01-14 23:05:34.983 debug (9028) configuration dateformat: <dd.mm.yyyy HH:MM> fb-checkpresence.0 2021-01-14 23:05:34.983 debug (9028) configuration history: <history.0> fb-checkpresence.0 2021-01-14 23:05:34.983 debug (9028) configuration user: <iobroker> fb-checkpresence.0 2021-01-14 23:05:34.982 info (9028) start fb-checkpresence: ip-address: "192.168.178.1" - interval devices: 2 Min. - interval members: 60 s fb-checkpresence.0 2021-01-14 23:05:34.975 info (9028) starting. Version 1.1.2 in C:/Program Files/iobroker/Test/node_modules/iobroker.fb-checkpresence, node: v12.20.1, js-controller: 3.2.6-0 fb-checkpresence.0 2021-01-14 23:05:34.828 debug (9028) statesDB connected fb-checkpresence.0 2021-01-14 23:05:34.827 debug (9028) States connected to redis: 127.0.0.1:9000 fb-checkpresence.0 2021-01-14 23:05:34.820 debug (9028) States create User PubSub Client fb-checkpresence.0 2021-01-14 23:05:34.819 debug (9028) States create System PubSub Client fb-checkpresence.0 2021-01-14 23:05:34.814 debug (9028) Redis States: Use Redis connection: 127.0.0.1:9000 fb-checkpresence.0 2021-01-14 23:05:34.813 debug (9028) objectDB connected fb-checkpresence.0 2021-01-14 23:05:34.810 debug (9028) Objects connected to redis: 127.0.0.1:9013 fb-checkpresence.0 2021-01-14 23:05:34.794 debug (9028) Objects client initialize lua scripts fb-checkpresence.0 2021-01-14 23:05:34.793 debug (9028) Objects create User PubSub Client fb-checkpresence.0 2021-01-14 23:05:34.793 debug (9028) Objects create System PubSub Client fb-checkpresence.0 2021-01-14 23:05:34.792 debug (9028) Objects client ready ... initialize now fb-checkpresence.0 2021-01-14 23:05:34.775 debug (9028) Redis Objects: Use Redis connection: 127.0.0.1:9013 fb-checkpresence.0 2021-01-14 23:05:30.727 info (15940) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason fb-checkpresence.0 2021-01-14 23:05:30.727 info (15940) terminating fb-checkpresence.0 2021-01-14 23:05:30.726 info (15940) cleaned everything up ... fb-checkpresence.0 2021-01-14 23:05:30.726 info (15940) Got terminate signal TERMINATE_YOURSELF -
@afuerhoff said in Test Adapter fb-checkpresence v1.1.x:
@sigi234
Da verstehe ich die Meldung vom JS-Controller nicht. Ist doch als Objekt angelegt.Ja, ist bei andere Adapter auch so.
Neueste Meldung:
fb-checkpresence.0 2021-01-14 22:42:56.416 error (8292) soapAction xml2js GetInfo status=500 errNo=4 401 Invalid Action@sigi234 said in Test Adapter fb-checkpresence v1.1.x:
Neueste Meldung:
fb-checkpresence.0 2021-01-14 22:42:56.416 error (8292) soapAction xml2js GetInfo status=500 errNo=4 401 Invalid ActionKommt die Meldung regelmäßig? Es wäre hilfreich zu wissen welche anderen Meldungen davor oder danach kommen.
Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
-
@sigi234 said in Test Adapter fb-checkpresence v1.1.x:
Neueste Meldung:
fb-checkpresence.0 2021-01-14 22:42:56.416 error (8292) soapAction xml2js GetInfo status=500 errNo=4 401 Invalid ActionKommt die Meldung regelmäßig? Es wäre hilfreich zu wissen welche anderen Meldungen davor oder danach kommen.
@afuerhoff said in Test Adapter fb-checkpresence v1.1.x:
Kommt die Meldung regelmäßig?
Nein
Es wäre hilfreich zu wissen welche anderen Meldungen davor oder danach kommen.
fb-checkpresence.0 2021-01-14 23:22:13.034 info (15516) createFbDeviceObjects finished successfully fb-checkpresence.0 2021-01-14 23:22:10.412 info (15516) createMemberObjects finished successfully fb-checkpresence.0 2021-01-14 23:22:10.021 info (15516) createGlobalObjects finished successfully fb-checkpresence.0 2021-01-14 23:22:09.823 info (15516) service LANConfigSecurity1-X_AVM-DE_GetCurrentUser is supported fb-checkpresence.0 2021-01-14 23:22:09.819 info (15516) service DeviceConfig1-Reboot is supported fb-checkpresence.0 2021-01-14 23:22:09.814 info (15516) service X_AVM-DE_HostFilter-GetWANAccessByIP is supported fb-checkpresence.0 2021-01-14 23:22:09.809 info (15516) service X_AVM-DE_HostFilter-DisallowWANAccessByIP is supported fb-checkpresence.0 2021-01-14 23:22:09.805 info (15516) service DeviceInfo1-GetInfo is supported fb-checkpresence.0 2021-01-14 23:22:09.800 info (15516) service WLANConfiguration3-GetSecurityKeys is supported fb-checkpresence.0 2021-01-14 23:22:09.795 info (15516) service WLANConfiguration3-GetInfo is supported fb-checkpresence.0 2021-01-14 23:22:09.789 info (15516) service WLANConfiguration3-SetEnable is supported fb-checkpresence.0 2021-01-14 23:22:09.783 info (15516) service WANPPPConnection1-GetInfo is supported fb-checkpresence.0 2021-01-14 23:22:09.777 info (15516) service DeviceInfo1-GetSecurityPort is supported fb-checkpresence.0 2021-01-14 23:22:09.772 info (15516) service Hosts1-X_AVM-DE_GetSpecificHostEntryByIP is supported fb-checkpresence.0 2021-01-14 23:22:09.767 info (15516) service Hosts1-GetSpecificHostEntry is supported fb-checkpresence.0 2021-01-14 23:22:09.763 info (15516) service Hosts1-X_AVM-DE_GetMeshListPath is supported fb-checkpresence.0 2021-01-14 23:22:09.757 info (15516) service Hosts1-X_AVM-DE_GetHostListPath is supported fb-checkpresence.0 2021-01-14 23:22:09.677 info (15516) start fb-checkpresence: ip-address: "192.168.178.1" - interval devices: 2 Min. - interval members: 60 s fb-checkpresence.0 2021-01-14 23:22:09.671 info (15516) starting. Version 1.1.2 in C:/Program Files/iobroker/Test/node_modules/iobroker.fb-checkpresence, node: v12.20.1, js-controller: 3.2.6-0 host.Medion(Test) 2021-01-14 23:22:08.889 info instance system.adapter.fb-checkpresence.0 started with pid 15516 host.Medion(Test) 2021-01-14 23:22:06.454 info instance system.adapter.fb-checkpresence.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) host.Medion(Test) 2021-01-14 23:22:05.792 info stopInstance system.adapter.fb-checkpresence.0 send kill signal fb-checkpresence.0 2021-01-14 23:22:05.796 info (13144) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason fb-checkpresence.0 2021-01-14 23:22:05.796 info (13144) terminating fb-checkpresence.0 2021-01-14 23:22:05.795 info (13144) cleaned everything up ... fb-checkpresence.0 2021-01-14 23:22:05.792 info (13144) Got terminate signal TERMINATE_YOURSELFJetzt schaut es wieder normal aus. Denke es hat was mit den JS Controller zu tun.
Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
Immer Daten sichern! -
@afuerhoff said in Test Adapter fb-checkpresence v1.1.x:
Kommt die Meldung regelmäßig?
Nein
Es wäre hilfreich zu wissen welche anderen Meldungen davor oder danach kommen.
fb-checkpresence.0 2021-01-14 23:22:13.034 info (15516) createFbDeviceObjects finished successfully fb-checkpresence.0 2021-01-14 23:22:10.412 info (15516) createMemberObjects finished successfully fb-checkpresence.0 2021-01-14 23:22:10.021 info (15516) createGlobalObjects finished successfully fb-checkpresence.0 2021-01-14 23:22:09.823 info (15516) service LANConfigSecurity1-X_AVM-DE_GetCurrentUser is supported fb-checkpresence.0 2021-01-14 23:22:09.819 info (15516) service DeviceConfig1-Reboot is supported fb-checkpresence.0 2021-01-14 23:22:09.814 info (15516) service X_AVM-DE_HostFilter-GetWANAccessByIP is supported fb-checkpresence.0 2021-01-14 23:22:09.809 info (15516) service X_AVM-DE_HostFilter-DisallowWANAccessByIP is supported fb-checkpresence.0 2021-01-14 23:22:09.805 info (15516) service DeviceInfo1-GetInfo is supported fb-checkpresence.0 2021-01-14 23:22:09.800 info (15516) service WLANConfiguration3-GetSecurityKeys is supported fb-checkpresence.0 2021-01-14 23:22:09.795 info (15516) service WLANConfiguration3-GetInfo is supported fb-checkpresence.0 2021-01-14 23:22:09.789 info (15516) service WLANConfiguration3-SetEnable is supported fb-checkpresence.0 2021-01-14 23:22:09.783 info (15516) service WANPPPConnection1-GetInfo is supported fb-checkpresence.0 2021-01-14 23:22:09.777 info (15516) service DeviceInfo1-GetSecurityPort is supported fb-checkpresence.0 2021-01-14 23:22:09.772 info (15516) service Hosts1-X_AVM-DE_GetSpecificHostEntryByIP is supported fb-checkpresence.0 2021-01-14 23:22:09.767 info (15516) service Hosts1-GetSpecificHostEntry is supported fb-checkpresence.0 2021-01-14 23:22:09.763 info (15516) service Hosts1-X_AVM-DE_GetMeshListPath is supported fb-checkpresence.0 2021-01-14 23:22:09.757 info (15516) service Hosts1-X_AVM-DE_GetHostListPath is supported fb-checkpresence.0 2021-01-14 23:22:09.677 info (15516) start fb-checkpresence: ip-address: "192.168.178.1" - interval devices: 2 Min. - interval members: 60 s fb-checkpresence.0 2021-01-14 23:22:09.671 info (15516) starting. Version 1.1.2 in C:/Program Files/iobroker/Test/node_modules/iobroker.fb-checkpresence, node: v12.20.1, js-controller: 3.2.6-0 host.Medion(Test) 2021-01-14 23:22:08.889 info instance system.adapter.fb-checkpresence.0 started with pid 15516 host.Medion(Test) 2021-01-14 23:22:06.454 info instance system.adapter.fb-checkpresence.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) host.Medion(Test) 2021-01-14 23:22:05.792 info stopInstance system.adapter.fb-checkpresence.0 send kill signal fb-checkpresence.0 2021-01-14 23:22:05.796 info (13144) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason fb-checkpresence.0 2021-01-14 23:22:05.796 info (13144) terminating fb-checkpresence.0 2021-01-14 23:22:05.795 info (13144) cleaned everything up ... fb-checkpresence.0 2021-01-14 23:22:05.792 info (13144) Got terminate signal TERMINATE_YOURSELFJetzt schaut es wieder normal aus. Denke es hat was mit den JS Controller zu tun.
-
@sigi234
Bitte mal beobachten.
Hast Du schon mal den QR-Code vom Gäste Wlan testen können?@afuerhoff said in Test Adapter fb-checkpresence v1.1.x:
@sigi234
Bitte mal beobachten.
Hast Du schon mal den QR-Code vom Gäste Wlan testen können?Gerade dabei, warte kurz.
Keine Anzeige?
Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
Immer Daten sichern! -
@afuerhoff said in Test Adapter fb-checkpresence v1.1.x:
@sigi234
Bitte mal beobachten.
Hast Du schon mal den QR-Code vom Gäste Wlan testen können?Gerade dabei, warte kurz.
Keine Anzeige?
-
@sigi234
Hast Du mit dem Basic Bool SVG Widget gemacht?
Hatte ich auch etwas nach gesucht -
Ich habe ein Update hochgeladen. Bitte neu testen. Am Besten einmal die Objekte unter fb-devices löschen. Die sind falsch angelegt worden.
@afuerhoff said in Test Adapter fb-checkpresence v1.1.x:
Ich habe ein Update hochgeladen. Bitte neu testen. Am Besten einmal die Objekte unter fb-devices löschen. Die sind falsch angelegt worden.
Guten Morgen,
habe getestet und sieht gut aus.Frage: Gibt es die Möglichkeit auch ein "presentGuest" zu bekommen? Im Format wie "presentMembers". Könnte das dann im Blockly als Liste verwenden.
Press any key to continue or any other to quit
-
@afuerhoff said in Test Adapter fb-checkpresence v1.1.x:
Ich habe ein Update hochgeladen. Bitte neu testen. Am Besten einmal die Objekte unter fb-devices löschen. Die sind falsch angelegt worden.
Guten Morgen,
habe getestet und sieht gut aus.Frage: Gibt es die Möglichkeit auch ein "presentGuest" zu bekommen? Im Format wie "presentMembers". Könnte das dann im Blockly als Liste verwenden.
Support us
411
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge