Test Adapter time-switch v2.0.x GitHub/Latest

[Wolfi]

@walli545
Das passiert sobald die Tastatur eingeblendet und auf das TS Tool trift.
Wenn ich die Tastatur verkleinern dann funktioniert es aber mit so einer kleinen Tastatur kann man nicht arbeiten.

Neue Version für alle?
Bitte die Version von https://github.com/walli545/ioBroker.time-switch/tarball/dev installieren

[liv-in-sky]

@walli545

• bei mir kann ich den current value von hand schalten
• aber das schedule funktioniert nicht - json datenpunkt stimmt - kein schalten

fehler habe ich sonst keinen mehr im log
habe alles gelöscht, neu installiert , upload gemacht - kein schalten - kein eintrag im log

[Iccube]

@walli545 ist bei mir genauso wie es @Wolfi beschrieben hat lande auch immer in der Hauptview bei Android geräten Tablet und Handy

[walli545]

@liv-in-sky hab noch Logging hinzugefügt, bitte nochmal updaten. Falls es nicht geht, kompletten Log schicken und Inhalt des Schedules (Logging Level von Adapter auf debug stellen). Bei mir schaltet es schon

@Wolfi @Iccube Kann mir einer von euch davon eine Bildschirmaufnahme machen? Ich kann das bei mir nicht reproduzieren.

[liv-in-sky]

@walli545

log - hätte um 17:11 schalten sollen

Spoiler

time-switch.0	2020-05-03 17:11:58.616	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
time-switch.0	2020-05-03 17:11:58.614	info	(32525) Finished message update-trigger
time-switch.0	2020-05-03 17:11:58.613	debug	(32525) Scheduling trigger at 17:14 on 1,2,3,4,5,6,0
time-switch.0	2020-05-03 17:11:58.613	debug	(32525) {"dataId":"time-switch.0.onoff.1.data","trigger":{"type":"TimeTrigger","hour":17,"minute":14,"weekdays":[1,2,3,4,5,6,0],"id":"1","action":{"type":"OnOffStateAction","name":"Off"}}}
time-switch.0	2020-05-03 17:11:58.613	info	(32525) Received update-trigger
time-switch.0	2020-05-03 17:11:48.309	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
time-switch.0	2020-05-03 17:11:48.302	info	(32525) Finished message add-trigger
time-switch.0	2020-05-03 17:11:48.301	debug	(32525) Scheduling trigger at 0:0 on 1,2,3,4,5,6,0
time-switch.0	2020-05-03 17:11:48.300	debug	(32525) Wants OnOffValueAction
time-switch.0	2020-05-03 17:11:48.300	debug	(32525) Wants TimeTrigger
time-switch.0	2020-05-03 17:11:48.300	debug	(32525) {"dataId":"time-switch.0.onoff.1.data","triggerType":"TimeTrigger","actionType":"OnOffValueAction","valueType":"boolean","stateIds":["controll-own.0.LEDLampe"]}
time-switch.0	2020-05-03 17:11:48.300	info	(32525) Received add-trigger
time-switch.0	2020-05-03 17:11:45.926	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
time-switch.0	2020-05-03 17:11:45.923	info	(32525) Finished message update-trigger
time-switch.0	2020-05-03 17:11:45.922	debug	(32525) Scheduling trigger at 17:13 on 1,2,3,4,5,6,0
time-switch.0	2020-05-03 17:11:45.921	debug	(32525) {"dataId":"time-switch.0.onoff.1.data","trigger":{"type":"TimeTrigger","hour":17,"minute":13,"weekdays":[1,2,3,4,5,6,0],"id":"0","action":{"type":"OnOffStateAction","name":"On"}}}
time-switch.0	2020-05-03 17:11:45.921	info	(32525) Received update-trigger
time-switch.0	2020-05-03 17:11:35.803	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
time-switch.0	2020-05-03 17:11:35.801	info	(32525) Finished message add-trigger
time-switch.0	2020-05-03 17:11:35.799	debug	(32525) Scheduling trigger at 0:0 on 1,2,3,4,5,6,0
time-switch.0	2020-05-03 17:11:35.799	debug	(32525) Wants OnOffValueAction
time-switch.0	2020-05-03 17:11:35.799	debug	(32525) Wants TimeTrigger
time-switch.0	2020-05-03 17:11:35.799	debug	(32525) {"dataId":"time-switch.0.onoff.1.data","triggerType":"TimeTrigger","actionType":"OnOffValueAction","valueType":"boolean","stateIds":["controll-own.0.LEDLampe"]}
time-switch.0	2020-05-03 17:11:35.798	info	(32525) Received add-trigger
time-switch.0	2020-05-03 17:11:34.759	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
time-switch.0	2020-05-03 17:11:34.758	debug	(32525) change from adapter itself for time-switch.0.onoff.1.enabled
time-switch.0	2020-05-03 17:11:34.756	info	(32525) Finished message enable-schedule
time-switch.0	2020-05-03 17:11:34.756	debug	(32525) {"dataId":"time-switch.0.onoff.1.data"}
time-switch.0	2020-05-03 17:11:34.756	info	(32525) Received enable-schedule
time-switch.0	2020-05-03 17:11:34.739	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
time-switch.0	2020-05-03 17:11:34.737	debug	(32525) change from adapter itself for time-switch.0.onoff.1.enabled
time-switch.0	2020-05-03 17:11:34.736	info	(32525) Finished message enable-schedule
time-switch.0	2020-05-03 17:11:34.735	debug	(32525) {"dataId":"time-switch.0.onoff.1.data"}
time-switch.0	2020-05-03 17:11:34.735	info	(32525) Received enable-schedule
time-switch.0	2020-05-03 17:11:26.490	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
time-switch.0	2020-05-03 17:11:26.489	debug	(32525) change from adapter itself for time-switch.0.onoff.1.enabled
time-switch.0	2020-05-03 17:11:26.487	info	(32525) Finished message disable-schedule
time-switch.0	2020-05-03 17:11:26.487	debug	(32525) {"dataId":"time-switch.0.onoff.1.data"}
time-switch.0	2020-05-03 17:11:26.487	info	(32525) Received disable-schedule
time-switch.0	2020-05-03 17:11:26.466	debug	(32525) change from adapter itself for time-switch.0.onoff.0.data
time-switch.0	2020-05-03 17:11:26.465	debug	(32525) change from adapter itself for time-switch.0.onoff.0.enabled
time-switch.0	2020-05-03 17:11:26.463	info	(32525) Finished message enable-schedule
time-switch.0	2020-05-03 17:11:26.462	debug	(32525) {"dataId":"time-switch.0.onoff.0.data"}
time-switch.0	2020-05-03 17:11:26.462	info	(32525) Received enable-schedule
time-switch.0	2020-05-03 17:11:20.279	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
time-switch.0	2020-05-03 17:11:20.279	debug	(32525) change from adapter itself for time-switch.0.onoff.1.enabled
time-switch.0	2020-05-03 17:11:20.277	info	(32525) Finished message disable-schedule
time-switch.0	2020-05-03 17:11:20.276	debug	(32525) {"dataId":"time-switch.0.onoff.1.data"}
time-switch.0	2020-05-03 17:11:20.276	info	(32525) Received disable-schedule
time-switch.0	2020-05-03 17:11:19.828	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
time-switch.0	2020-05-03 17:11:19.827	debug	(32525) change from adapter itself for time-switch.0.onoff.1.enabled
time-switch.0	2020-05-03 17:11:19.825	info	(32525) Finished message disable-schedule
time-switch.0	2020-05-03 17:11:19.824	debug	(32525) {"dataId":"time-switch.0.onoff.1.data"}
time-switch.0	2020-05-03 17:11:19.824	info	(32525) Received disable-schedule
time-switch.0	2020-05-03 17:11:19.770	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
time-switch.0	2020-05-03 17:11:19.768	info	(32525) Finished message change-switched-values
time-switch.0	2020-05-03 17:11:19.767	debug	(32525) {"dataId":"time-switch.0.onoff.1.data","valueType":"boolean","onValue":"true","offValue":"false"}
time-switch.0	2020-05-03 17:11:19.767	info	(32525) Received change-switched-values
time-switch.0	2020-05-03 17:11:17.897	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
time-switch.0	2020-05-03 17:11:17.896	debug	(32525) change from adapter itself for time-switch.0.onoff.1.enabled
time-switch.0	2020-05-03 17:11:17.894	info	(32525) Finished message disable-schedule
time-switch.0	2020-05-03 17:11:17.893	debug	(32525) {"dataId":"time-switch.0.onoff.1.data"}
time-switch.0	2020-05-03 17:11:17.893	info	(32525) Received disable-schedule
time-switch.0	2020-05-03 17:11:17.408	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
time-switch.0	2020-05-03 17:11:17.407	debug	(32525) change from adapter itself for time-switch.0.onoff.1.enabled
time-switch.0	2020-05-03 17:11:17.405	info	(32525) Finished message disable-schedule
time-switch.0	2020-05-03 17:11:17.404	debug	(32525) {"dataId":"time-switch.0.onoff.1.data"}
time-switch.0	2020-05-03 17:11:17.404	info	(32525) Received disable-schedule
time-switch.0	2020-05-03 17:11:17.390	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
time-switch.0	2020-05-03 17:11:17.388	info	(32525) Finished message change-switched-values
time-switch.0	2020-05-03 17:11:17.387	debug	(32525) {"dataId":"time-switch.0.onoff.1.data","valueType":"boolean","offValue":"false"}
time-switch.0	2020-05-03 17:11:17.387	info	(32525) Received change-switched-values
time-switch.0	2020-05-03 17:11:11.065	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
time-switch.0	2020-05-03 17:11:11.065	debug	(32525) change from adapter itself for time-switch.0.onoff.1.enabled
time-switch.0	2020-05-03 17:11:11.061	info	(32525) Finished message disable-schedule
time-switch.0	2020-05-03 17:11:11.060	debug	(32525) {"dataId":"time-switch.0.onoff.1.data"}
time-switch.0	2020-05-03 17:11:11.060	info	(32525) Received disable-schedule
time-switch.0	2020-05-03 17:11:00.006	debug	(32525) Executing trigger with id 1
time-switch.0	2020-05-03 17:10:15.052	debug	(32525) got state: [object Object]
time-switch.0	2020-05-03 17:10:15.051	debug	(32525) Scheduling trigger at 17:11 on 1,2,3,4,5,6,0
time-switch.0	2020-05-03 17:10:15.040	debug	(32525) Scheduling trigger at 17:9 on 1,2,3,4,5,6,0
time-switch.0	2020-05-03 17:10:15.035	debug	(32525) got state: [object Object]
time-switch.0	2020-05-03 17:10:15.015	debug	(32525) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
time-switch.0	2020-05-03 17:10:14.989	debug	(32525) Onoff state 1not found, creating
time-switch.0	2020-05-03 17:10:14.988	debug	(32525) Found state time-switch.0.onoff.0.data
time-switch.0	2020-05-03 17:10:14.967	debug	(32525) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
time-switch.0	2020-05-03 17:10:14.948	info	(32525) starting. Version 1.1.0 in /opt/iobroker/node_modules/iobroker.time-switch, node: v10.20.1, js-controller: 3.0.20
host.iobroker59	2020-05-03 17:10:13.777	info	instance system.adapter.time-switch.0 started with pid 32525
host.iobroker59	2020-05-03 17:10:11.274	info	instance system.adapter.time-switch.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
time-switch.0	2020-05-03 17:10:10.752	info	(27511) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
time-switch.0	2020-05-03 17:10:10.752	info	(27511) terminating
time-switch.0	2020-05-03 17:10:10.752	info	(27511) cleaned everything up...
time-switch.0	2020-05-03 17:10:10.751	info	(27511) Got terminate signal TERMINATE_YOURSELF
host.iobroker59	2020-05-03 17:10:10.749	info	stopInstance system.adapter.time-switch.0 send kill signal
host.iobroker59	2020-05-03 17:10:10.748	info	stopInstance system.adapter.time-switch.0 (force=false, process=true)
time-switch.0	2020-05-03 17:09:56.648	debug	(27511) change from adapter itself for time-switch.0.onoff.0.data
time-switch.0	2020-05-03 17:09:56.647	debug	(27511) change from adapter itself for time-switch.0.onoff.0.enabled
time-switch.0	2020-05-03 17:09:56.645	info	(27511) Finished message enable-schedule
time-switch.0	2020-05-03 17:09:56.645	debug	(27511) {"dataId":"time-switch.0.onoff.0.data"}
time-switch.0	2020-05-03 17:09:56.644	info	(27511) Received enable-schedule
host.iobroker59	2020-05-03 17:09:10.059	info	instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
host.iobroker59	2020-05-03 17:09:00.026	info	instance system.adapter.ical.0 started with pid 29171
time-switch.0	2020-05-03 17:09:00.007	debug	(27511) Executing trigger with id 0
time-switch.0	2020-05-03 17:08:22.938	debug	(27511) change from adapter itself for time-switch.0.onoff.0.data
time-switch.0	2020-05-03 17:08:22.934	info	(27511) Finished message update-trigger
time-switch.0	2020-05-03 17:08:22.931	debug	(27511) Scheduling trigger at 17:11 on 1,2,3,4,5,6,0
time-switch.0	2020-05-03 17:08:22.930	debug	(27511) {"dataId":"time-switch.0.onoff.0.data","trigger":{"type":"TimeTrigger","hour":17,"minute":11,"weekdays":[1,2,3,4,5,6,0],"id":"1","action":{"type":"OnOffStateAction","name":"Off"}}}
time-switch.0	2020-05-03 17:08:22.930	info	(27511) Received update-trigger

log - hätte um 17:16 schalten sollen

Spoiler

time-switch.0	2020-05-03 17:16:00.006	debug	(32525) Executing trigger with id 0
time-switch.0	2020-05-03 17:14:26.309	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
time-switch.0	2020-05-03 17:14:26.306	info	(32525) Finished message update-trigger
time-switch.0	2020-05-03 17:14:26.305	debug	(32525) Scheduling trigger at 17:17 on 1,2,3,4,5,6,0
time-switch.0	2020-05-03 17:14:26.304	debug	(32525) {"dataId":"time-switch.0.onoff.1.data","trigger":{"type":"TimeTrigger","hour":17,"minute":17,"weekdays":[1,2,3,4,5,6,0],"id":"1","action":{"type":"OnOffStateAction","name":"Off"}}}
time-switch.0	2020-05-03 17:14:26.304	info	(32525) Received update-trigger
time-switch.0	2020-05-03 17:14:21.306	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
time-switch.0	2020-05-03 17:14:21.304	info	(32525) Finished message update-trigger
time-switch.0	2020-05-03 17:14:21.303	debug	(32525) Scheduling trigger at 17:16 on 1,2,3,4,5,6,0
time-switch.0	2020-05-03 17:14:21.303	debug	(32525) {"dataId":"time-switch.0.onoff.1.data","trigger":{"type":"TimeTrigger","hour":17,"minute":16,"weekdays":[1,2,3,4,5,6,0],"id":"0","action":{"type":"OnOffStateAction","name":"On"}}}
time-switch.0	2020-05-03 17:14:21.303	info	(32525) Received update-trigger
time-switch.0	2020-05-03 17:14:00.005	debug	(32525) Executing trigger with id 1

current value bleibt um 17:16 auf false

[walli545]

@liv-in-sky bewegt sich nur der Schalter nicht oder ändert sich auch der Wert des States nicht? Nicht, dass ich am Falschen Ende suche

[liv-in-sky]

@walli545 datenpunkte ändern sich nicht

du kannst auch gerne noch warten, ob es einen anderen user gibt, der das selbe problem hat

[liv-in-sky]

@walli545 habe es auch mal mit number getestet - selbes verhalten

[walli545]

@liv-in-sky kann es sein, dass du das Widget nicht neu angelegt hast? Und dadurch nie den geschaltenen State konfiguriert hast?

[liv-in-sky]

@walli545

instanz stop, widgets wurden gelöscht , objecte gelöscht - instanz gelöscht - update adapter - instanz neu - im setting neu und danach neues widget

[Wolfi]

@walli545 @Iccube

Wollte zur Bildschirmaufnahme eine Testumgebung benutzen ( Projekt main ) und siehe da dort lande ich nicht mehr in der Hauptview nein da funktioniert es.
Jetzt muss ich rausfinden warum in meinem Projekt das passiert

[Wolfi]

@walli545 @Iccube
Das hat definitiv nicht mit deinem Adapter/witget zu tun passiert auch mit einem anderen Eingabe Widget aber warum? Das muss ich noch rausfinden.

Was löst die Einblendung der Tastatur in der View aus??

[walli545]

@liv-in-sky habs mir gerade nochmal angeschaut, glaube ich habs gefunden. Problem war, dass ich es nicht mit einer frischen Installation ausprobiert hatte Bitte testen, danke fürs ausprobieren immer

[liv-in-sky]

@walli545
kurze info:
JETZT WIRD GESCHALTEN - - teste morgen ausgiebiger weiter

[Iccube]

@walli545 habe den Adapter mal gelöscht und neu aufgespielt dann neuen Schaltplan erstellt jetzt kann ich den Namen nicht mehr ändern und keine Schaltzeiten einfügen folgender fehler im log

time-switch.0	2020-05-03 22:46:26.485	error	(13686) Could not handle message:
time-switch.0	2020-05-03 22:46:26.485	error	(13686) Error
time-switch.0	2020-05-03 22:46:26.484	error	(13686) No schedule found for state undefined
time-switch.0	2020-05-03 22:46:26.484	error	at new Promise (<anonymous>)
time-switch.0	2020-05-03 22:46:26.484	error	at /opt/iobroker/node_modules/iobroker.time-switch/build/main.js:8:71
time-switch.0	2020-05-03 22:46:26.484	error	at Generator.next (<anonymous>)
time-switch.0	2020-05-03 22:46:26.484	error	at TimeSwitch.<anonymous> (/opt/iobroker/node_modules/iobroker.time-switch/build/main.js:142:43)
time-switch.0	2020-05-03 22:46:26.484	error	at MessageService.handleMessage (/opt/iobroker/node_modules/iobroker.time-switch/build/services/MessageService.js:29:16)
time-switch.0	2020-05-03 22:46:26.484	error	at __awaiter (/opt/iobroker/node_modules/iobroker.time-switch/build/services/MessageService.js:4:12)
time-switch.0	2020-05-03 22:46:26.484	error	at new Promise (<anonymous>)
time-switch.0	2020-05-03 22:46:26.484	error	at /opt/iobroker/node_modules/iobroker.time-switch/build/services/MessageService.js:8:71
time-switch.0	2020-05-03 22:46:26.484	error	at Generator.next (<anonymous>)
time-switch.0	2020-05-03 22:46:26.484	error	at MessageService.<anonymous> (/opt/iobroker/node_modules/iobroker.time-switch/build/services/MessageService.js:40:23)
time-switch.0	2020-05-03 22:46:26.484	error	(13686) Error: No schedule found for state undefined
time-switch.0	2020-05-03 22:46:26.483	info	(13686) Received disable-schedule

[Iccube]

Habe iobroker mal neu gestartet jetzt funktioniert alles wie es soll

[liv-in-sky]

@walli545
habe nochmal getestet - bool, string, zahl, mehrere datenpunkte

funktioniert alles

wäre es möglich im json noch das enabled oder disabled wieder einzufügen (ich hoffe, du änderst nicht wieder die json-struktur )

habe meine tabelle angeglichen (ist mir sonst zu viel platzverbrauch in der vis) - reagiert direkt auf das ändern der datenpunkte (das schalten der dp ist über die tabelle nicht möglich)

[walli545]

@liv-in-sky sehr gut danke Zum Thema enabled: Nein, der wird nicht mehr ins json kommen, zum einen finde ich es in einem eigenen State praktischer, da man so einfach einen Schalter erstellen kann, mit dem man alle ausschaltet, etc. und dafür dann nicht für alle einzeln ins programmier-widget muss. Wenn ich enabled nun wieder in json einbaue, würde sich wie du gesagt hast das json Format wieder ändern und ich muss es an zwei Stellen pflegen, was ich eher unschön finde.

[liv-in-sky]

@walli545 sorry - alles gut - den datenpunkt habe ich völlig übersehen- den kann ich auch so einbauen

war voll im json-modus

[walli545]

@liv-in-sky kannst dein eigenes Widget ja dann auch hochladen, vielleicht findets jemand ja praktischer