@lucky_esa Klar gerne, du meinst per TeamViewer nehme ich an ?

@lucky_esa Ich bekomme zwar Fehler, der Wert wird aber gesetzt.

lg-thinq.0
2025-09-30 10:30:00.361	info	undefined

lg-thinq.0
2025-09-30 10:30:00.361	error	AxiosError: Request failed with status code 400

lg-thinq.0
2025-09-30 10:30:00.361	error	Send failed

lg-thinq.0
2025-09-30 10:30:00.358	error	AxiosError: Request failed with status code 400

lg-thinq.0
2025-09-30 10:30:00.353	error	Send failed

@lucky_esa ich steure es über remote.basicCtrl dort die beiden Werte hotWaterTarget & opMode
Die Mikrowelle ist egal, die hatte ich nur mal eingefügt, weil es möglich war, aber nie genutzt.

@lucky_esa Habe dir eine Email geschickt, danke für deine Hilfe.

@lucky_esa Ja ich habe ein thinq1 Gerät, welches ich aber sowieso nicht nutze. Meinst du das macht Probleme ? Soll ich es mal löschen ?

Ich habe schon sämtliche Versionen versucht auch die neuste von Git. Ich bekomme immer folgenden Fehler kurz nach dem Login.

lg-thinq.0 2025-09-25 14:33:49.575	warn	Found no workID`s. Please restart adapter!

Wenn ich ein Gerät über die Remote Datenpunkte steuern Will ( Brauchwasserwärempumpe ) kommt folgender Fehler

2025-09-25 10:30:05.306 - error: lg-thinq.0 (533539) Send failed
2025-09-25 10:30:05.306 - error: lg-thinq.0 (533539) AxiosError: Request failed with status code 400
2025-09-25 10:30:05.312 - error: lg-thinq.0 (533539) Send failed
2025-09-25 10:30:05.312 - error: lg-thinq.0 (533539) AxiosError: Request failed with status code 400

Log nach Adapter Restart

lg-thinq.0
2025-09-25 14:41:27.826	warn	Found no workID`s. Please restart adapter!
lg-thinq.0
2025-09-25 14:41:27.566	info	MQTT connected to: t20/op/b95aa4d6cb8d2792fbe6b89fe636ab59e522bfb0ac6c376a212dd7b7b7f84e76/inbox
lg-thinq.0
2025-09-25 14:41:27.285	info	Start MQTT Connection
lg-thinq.0
2025-09-25 14:41:26.974	info	Create certification done
lg-thinq.0
2025-09-25 14:41:26.374	info	Found AWS CER
lg-thinq.0
2025-09-25 14:41:26.277	info	Found MQTT Host
lg-thinq.0
2025-09-25 14:41:25.821	info	Update raw datapoints for fa8118d4-5e16-11ee-a51c-020000000000
lg-thinq.0
2025-09-25 14:41:16.384	info	Create or update datapoints for fa8118d4-5e16-11ee-a51c-020000000000
lg-thinq.0
2025-09-25 14:41:16.265	info	Update raw datapoints for 387eeba3-80f1-1281-b196-4cbce99fb04c
lg-thinq.0
2025-09-25 14:41:09.859	info	Create or update datapoints for 387eeba3-80f1-1281-b196-4cbce99fb04c
lg-thinq.0
2025-09-25 14:41:09.750	info	Update raw datapoints for 25a63472-af7e-1a18-b11b-e0854d733a9c
lg-thinq.0
2025-09-25 14:41:03.128	info	Create or update datapoints for 25a63472-af7e-1a18-b11b-e0854d733a9c
lg-thinq.0
2025-09-25 14:41:03.127	info	Found: 3 devices
lg-thinq.0
2025-09-25 14:41:00.865	info	Login successful
lg-thinq.0
2025-09-25 14:40:59.631	info	starting. Version 1.1.2 (non-npm: TA2k/ioBroker.lg-thinq) in /opt/iobroker/node_modules/iobroker.lg-thinq, node: v22.20.0, js-controller: 7.0.7
lg-thinq.0
2025-09-25 14:40:55.384	info	terminating
lg-thinq.0
2025-09-25 14:40:54.882	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
lg-thinq.0
2025-09-25 14:40:54.882	info	terminating
lg-thinq.0
2025-09-25 14:40:54.881	info	Got terminate signal TERMINATE_YOURSELF

Hat jemand eine Idee woran das liegen könnte ? Ich habe den Adapter schon mehrfach gelöscht und neu erstellt, ältere Versionen versucht - alles leider ohne Erfolg.

@asgothian

Doch die kam auch hatte es nur nicht gesehen, habe nochmal im Log geschaut

2025-08-27 08:37:14.992 - info: zigbee.0 (669) No converter available for 'TS011F_plug_3' with key 'measurement_poll_intervall'
2025-08-27 08:37:14.992 - info: zigbee.0 (669) No converter available for 'TS011F_plug_3' with key 'state_action'

Soll ich es noch mit einer anderen Steckdose die ich schalten kann probieren ? Ich denke das Ergebnis wird das gleiche sein.

@asgothian

Habe die Punkte von dir versucht, leider auch ohne Erfolg.
Den send_payload Wert musste ich auf {"measurement_poll_intervall":20 } ändern anders kam eine Fehlermeldung.
Die Steckdose direkt über den Power state schalten kann ich nicht, da ansonsten der Server weg ist. Habe stattdessen wieder den Wert von power_outage_memory geändert.

zigbee.0
2025-08-27 08:29:32.897	warn	ELEVATED:I02 (a85e) value generated '227' from device 84ba20fffe6e78b8 for 'Measured electrical potential value'

zigbee.0
2025-08-27 08:29:32.897	warn	ELEVATED:I02 (a85e) value generated '0.166' from device 84ba20fffe6e78b8 for 'Instantaneous measured electrical current'

zigbee.0
2025-08-27 08:29:32.897	warn	ELEVATED:I02 (a85e) value generated '19' from device 84ba20fffe6e78b8 for 'Load power'

zigbee.0
2025-08-27 08:29:32.897	warn	ELEVATED:I01 (a85e) message received '{"power":19,"current":0.166,"voltage":227}' from device 84ba20fffe6e78b8 type 'TS011F_plug_3'

zigbee.0
2025-08-27 08:29:32.896	warn	ELEVATED:I02 (a85e) value generated '255' from device 84ba20fffe6e78b8 for 'Link quality'

zigbee.0
2025-08-27 08:29:32.896	warn	ELEVATED:I01 (a85e) message received '{"linkquality":255}' from device 84ba20fffe6e78b8 type 'TS011F_plug_3'

zigbee.0
2025-08-27 08:29:32.895	warn	ELEVATED:I01 (a85e) Zigbee Event of Type readResponse from device 0x84ba20fffe6e78b8, incoming event: {"type":"readResponse","data":{"rmsVoltage":227,"rmsCurrent":166,"activePower":19},"linkquality":255,"groupID":0,"cluster":"haElectricalMeasurement","meta":{"zclTransactionSequenceNumber":13,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

zigbee.0
2025-08-27 08:28:32.802	warn	ELEVATED:I02 (bda0) value generated '227' from device 84ba20fffe6e78b8 for 'Measured electrical potential value'

zigbee.0
2025-08-27 08:28:32.802	warn	ELEVATED:I02 (bda0) value generated '0.214' from device 84ba20fffe6e78b8 for 'Instantaneous measured electrical current'

zigbee.0
2025-08-27 08:28:32.802	warn	ELEVATED:I02 (bda0) value generated '23' from device 84ba20fffe6e78b8 for 'Load power'

zigbee.0
2025-08-27 08:28:32.802	warn	ELEVATED:I01 (bda0) message received '{"power":23,"current":0.214,"voltage":227}' from device 84ba20fffe6e78b8 type 'TS011F_plug_3'

zigbee.0
2025-08-27 08:28:32.802	warn	ELEVATED:I02 (bda0) value generated '255' from device 84ba20fffe6e78b8 for 'Link quality'

zigbee.0
2025-08-27 08:28:32.802	warn	ELEVATED:I01 (bda0) message received '{"linkquality":255}' from device 84ba20fffe6e78b8 type 'TS011F_plug_3'

zigbee.0
2025-08-27 08:28:32.800	warn	ELEVATED:I01 (bda0) Zigbee Event of Type readResponse from device 0x84ba20fffe6e78b8, incoming event: {"type":"readResponse","data":{"rmsVoltage":227,"rmsCurrent":214,"activePower":23},"linkquality":255,"groupID":0,"cluster":"haElectricalMeasurement","meta":{"zclTransactionSequenceNumber":3,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

zigbee.0
2025-08-27 08:27:48.220	warn	ELEVATED:I02 (0f7b) value generated '255' from device 84ba20fffe6e78b8 for 'Link quality'

zigbee.0
2025-08-27 08:27:48.220	warn	ELEVATED:I01 (0f7b) message received '{"linkquality":255}' from device 84ba20fffe6e78b8 type 'TS011F_plug_3'

zigbee.0
2025-08-27 08:27:48.219	warn	ELEVATED:I01 (0f7b) Zigbee Event of Type attributeReport from device 0x84ba20fffe6e78b8, incoming event: {"type":"attributeReport","data":{"moesStartUpOnOff":0},"linkquality":255,"groupID":0,"cluster":"genOnOff","meta":{"zclTransactionSequenceNumber":2,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1}

zigbee.0
2025-08-27 08:27:48.206	warn	ELEVATED:SUCCESS (0ee3) convert result {"state":{"power_outage_memory":"off"}} for device 0x84ba20fffe6e78b8

zigbee.0
2025-08-27 08:27:48.068	warn	ELEVATED:O04 (0ee3) convert power_outage_memory, "off", {} for device 0x84ba20fffe6e78b8 with Endpoint power_outage_memory

zigbee.0
2025-08-27 08:27:48.068	warn	ELEVATED:O04 (0ee3) convert power_outage_memory, "off", {} for device 0x84ba20fffe6e78b8 with Endpoint power_outage_memory

zigbee.0
2025-08-27 08:27:48.068	warn	ELEVATED:O04 (0ee3) convert power_outage_memory, "off", {} for device 0x84ba20fffe6e78b8 with Endpoint power_outage_memory

zigbee.0
2025-08-27 08:27:48.068	warn	ELEVATED:O03 (0ee3) Publishing to 0x84ba20fffe6e78b8 of model TS011F_plug_3 with power_outage_memory

zigbee.0
2025-08-27 08:27:48.068	warn	ELEVATED:O02 (0ee3) Change state 'power_outage_memory' at device 0x84ba20fffe6e78b8 type 'TS011F_plug_3'

zigbee.0
2025-08-27 08:27:48.067	warn	ELEVATED:O01 (0ee3) User state change of state zigbee.0.84ba20fffe6e78b8.power_outage_memory with value off (ack: false) from system.adapter.admin.0

Edit habe den Payload auch noch auf folgendes gesetzt, auch ohne Erfolg

{
  "measurement_poll_intervall": 20,
  "state_action": true
}

Habe nur diese Meldung gefunden

zigbee.0
2025-08-27 08:37:14.992	info	No converter available for 'TS011F_plug_3' with key 'state_action'

@asgothian

Tuya TS011F_plug_3 mit der Option measurement_poll_interval

@asgothian

Ja hatte den Wert von power_outage_memory hin und her gewechselt