fhempy: tuya (lokal)

[thburkhart]

Code Auswählen Erweitern

[code]define TUYA_JL35 f

setstate TUYA_JL35 E: 0.491 kWh cP: 56.0 W
setstate TUYA_JL35 2023-01-30 07:59:19 countdown_1 0.0
setstate TUYA_JL35 2023-02-23 17:56:57 cur_current 24.0
setstate TUYA_JL35 2023-02-23 17:57:02 cur_power 56.0
setstate TUYA_JL35 2023-02-23 17:56:17 cur_voltage 232.0
setstate TUYA_JL35 2023-01-30 07:59:19 dp_07 0
setstate TUYA_JL35 2023-02-23 17:56:52 energy 0.491
setstate TUYA_JL35 2023-02-23 12:27:45 online 1
setstate TUYA_JL35 2023-02-23 12:27:59 state on
setstate TUYA_JL35 2023-02-23 09:28:26 switch_1 on

[/code]
Hi Stefan,

so siehts bei meinem GL 1800X-Router aus. 56 Watt aktuell. Habe riesen Schreck gekriegt. In der App sind es plausible 5,6 Watt

im Übrigen muss man die Devices wohl zum Update anregen und zwar durch ein/ausschalten.

Also nur das faktor 10 Problem bei cur_power bleibt.

Viele Grüße

Thomas

[stefanru]

Ok,

das ist ja interessant, meine Steckdosen passen.
Scheint wohl auch Modell abhängig zu sein.
Dann muss wohl Dominik was zu sagen.

Gruß,
Stefan

[thburkhart]

Ich verwende Summen Power readings auch vom Smart Meter mit DB funktionen.
Ist jetzt vom Smart Meter aber ist hier auch anwendbar:
my $periodeStefanKW = $totalStefanKW - DbReadingsVal("logdbRep","stefan.stromzaehler:total_consumption",$startDateStefan,"no Value from DB");;

So kannst du den Wert zu einem Datum auslesen, hier startDateStefan und dann zu jetzt berechnen. Oder start date ist genau 30 Tage vor heute, usw.

hi Stefan, das war mir zu hoch

ist das in GPLOT?

da ich  ja nun energy habe und in die dblog schreibe, suche ich eine tabellarische und graphische Darstellung der Tabelle in der Form

Device   - Verbrauch Gesamt - Verbrauch 2023-01 - Verbrauch 2023-02  usw. usw
-------------------------------------------------------------------------------------------------

JL36        TUYA_JL36 energy       berechnet            berechnet
JL37
JL38
.
.
.

____________________________________________________________________________
Also wie in der App horizontal statt vertikal

geht das in GPLOT?

[stefanru]

Hi Thomas,

das war auch ohne Background von mir
Das ist eine Berechnung für meinen Stromzähler in einem User Reading:
my $periodeStefanKW = $totalStefanKW - DbReadingsVal("logdbRep","stefan.stromzaehler:total_consumption",$startDateStefan,"no Value from DB");;

Auf jeden fall mit deinem DBLOG_REP wie hier unter "Praxisbeispiele / Hinweise und Lösungsansätze für verschiedene Aufgaben" beschrieben bekommst du in FHEM Tabellen mit z.B. Monatsverbräuchen.
https://wiki.fhem.de/wiki/DbRep_-_Reporting_und_Management_von_DbLog-Datenbankinhalten

Ich glaube da geht auch was im GPLOT direkt, aber da habe ich gerade nichts das ich benutze.

Gruß,
Stefan

[dominik]

@Dominik,

super ! Vielen Dank!
in "energy" wird also ganz schlich aufsummiert und wir können den Monatsverbrauch mittels dblog/gplot selbst ermitteln und darstellen.
Muss ich gleich mal ausprobieren.
Als erstes muss ich energy mit dbloginclude in die Datenbank aufnehmen.

Wäre es für dich auch machbar analog zu SmartLife die Monate separat aufzunehmen:

energy   = Verbrauch von Start ab   "total"
energy_2302 Verbrauch 01.02.23 bis 28.02.23
energy_2303 Verbrauch 01.03.23 bis 31.03.23
energy_2304  usw.

dann hätte man das sofort im Überblick.

@all
oder wie macht ihr das?


Herzlicher Dank an Dominik für das suptertolle und stabile Modul

Viele Grüße

Thomas

define stat statistics DEVICENAME

Danach erhältst du im Device DEVICENAME stateEnergy Readings wo du Stunde, Tag, etc. Infos erhälst.

[dominik]

ich habe nun begonnen, energy zu testen:hier mein JL35

Code Auswählen Erweitern

[code]define TUYA_JL35 fhempy tuya wifvoilfrqeo6hvu 8877821724a16014ef14 192.168.9.93 f3ac3693f76b2a96 3.30
attr TUYA_JL35 DbLogExclude .*
attr TUYA_JL35 alias JL35 GL AXT1800
attr TUYA_JL35 dp_01 switch_1
attr TUYA_JL35 dp_02 countdown_1
attr TUYA_JL35 dp_03 add_ele
attr TUYA_JL35 dp_04 cur_current
attr TUYA_JL35 dp_05 cur_power
attr TUYA_JL35 dp_06 cur_voltage
attr TUYA_JL35 group Schalter (T)
attr TUYA_JL35 room -TUYA
attr TUYA_JL35 stateFormat E: energy kWh cP: cur_power W
attr TUYA_JL35 tuya_spec_functions [{'code': 'switch_1', 'dp_id': 1, 'type': 'Boolean', 'values': {}, 'desc': 'switch 1'}, {'code': 'countdown_1', 'dp_id': 2, 'type': 'Integer', 'values': {'min': 0, 'scale': 0, 'unit': '秒', 'max': 86400, 'step': 1}, 'desc': 'countdown 1'}]
attr TUYA_JL35 tuya_spec_status [{'code': 'switch_1', 'dp_id': 1, 'type': 'Boolean', 'values': {}}, {'code': 'countdown_1', 'dp_id': 2, 'type': 'Integer', 'values': {'min': 0, 'scale': 0, 'unit': '秒', 'max': 86400, 'step': 1}}, {'code': 'add_ele', 'dp_id': 3, 'type': 'Integer', 'values': {'min': 0, 'scale': 0, 'unit': '度', 'max': 500000, 'step': 100}}, {'code': 'cur_current', 'dp_id': 4, 'type': 'Integer', 'values': {'min': 0, 'scale': 0, 'unit': 'mA', 'max': 30000, 'step': 1}}, {'code': 'cur_power', 'dp_id': 5, 'type': 'Integer', 'values': {'min': 0, 'scale': 0, 'unit': 'W', 'max': 50000, 'step': 1}}, {'code': 'cur_voltage', 'dp_id': 6, 'type': 'Integer', 'values': {'min': 0, 'unit': 'V', 'scale': 0, 'max': 2500, 'step': 1}}]
#   DEF        tuya wifvoilfrqeo6hvu 8877821724a16014ef14 192.168.9.93 f3ac3693f76b2a96 3.3 ea8453wdazquzfl08l0e 8a4b27dd759d4c6a9456aa8155d2a0ea
#   DEVICEID   8877821724a16014ef14
#   FHEMPYTYPE tuya
#   FUUID      63b40e2e-f33f-fd5f-a6fc-66b5fe95602f2212
#   IODev      local_pybinding
#   NAME       TUYA_JL35
#   NR         1736
#   PYTHONTYPE tuya
#   STATE      E: 0.192 kWh cP: 56.0 W
#   TYPE       fhempy
#   eventCount 79
#   READINGS:
#     2023-01-30 07:59:19   countdown_1     0.0
#     2023-02-23 12:37:33   cur_current     23.0
#     2023-02-23 12:37:18   cur_power       56.0
#     2023-02-23 12:37:13   cur_voltage     233.4
#     2023-01-30 07:59:19   dp_07           0
#     2023-02-23 12:36:53   energy          0.192
#     2023-02-23 12:27:45   online          1
#     2023-02-23 12:27:59   state           on
#     2023-02-23 09:28:26   switch_1        on
#   args:
#     TUYA_JL35
#     fhempy
#     tuya
#     wifvoilfrqeo6hvu
#     8877821724a16014ef14
#     192.168.9.93
#     f3ac3693f76b2a96
#     3.3
#     ea8453wdazquzfl08l0e
#     8a4b27dd759d4c6a9456aa8155d2a0ea
#   argsh:
#
setstate TUYA_JL35 E: 0.192 kWh cP: 56.0 W
setstate TUYA_JL35 2023-01-30 07:59:19 countdown_1 0.0
setstate TUYA_JL35 2023-02-23 12:37:33 cur_current 23.0
setstate TUYA_JL35 2023-02-23 12:37:18 cur_power 56.0
setstate TUYA_JL35 2023-02-23 12:37:13 cur_voltage 233.4
setstate TUYA_JL35 2023-01-30 07:59:19 dp_07 0
setstate TUYA_JL35 2023-02-23 12:36:53 energy 0.192
setstate TUYA_JL35 2023-02-23 12:27:45 online 1
setstate TUYA_JL35 2023-02-23 12:27:59 state on
setstate TUYA_JL35 2023-02-23 09:28:26 switch_1 on

[/code]

cur_power ist um Faktor 10 zu hoch

JL04 ist ok

JL05,06,07

haben kein reading "energy"

@dominik , das müsstest du nachvollziehen können

Ist schade, dass tuya da bei manchen Werte falsche Specs liefert. Ich habe cur_power "korrigiert".

energy kommt erst wenn cur_power > 0. Vielleicht ist das noch nicht der Fall?

[dominik]

Zuerst einmal das List mit allen Readings vom Schlafzimmerventilator:

Code Auswählen Erweitern

Internals:
   CFGFN     
   DEF        tuya 6awobc9jfnlwvqtw bf75378cf6e13718e0rvcj 192.168.178.169 7ada5a7cbf4a78e8 3.3 asfg5sj9aurr9nib73fx fc553d7a6bfa4a569bc69ed2aa6924ed
   DEVICEID   bf75378cf6e13718e0rvcj
   FHEMPYTYPE tuya
   FUUID      63eab589-f33f-7706-2293-af83091afa968b90
   IODev      fhempy_local
   NAME       tuya_local_bf75378cf6e13718e0rvcj
   NR         69512
   PYTHONTYPE tuya
   STATE      on
   TYPE       fhempy
   eventCount 271
   READINGS:
     2023-02-13 23:11:22   active_time     1654518995
     2023-02-13 23:11:22   biz_type        18
     2023-02-13 23:11:22   category        fs
     2023-02-13 23:11:22   create_time     1627922506
     2023-02-23 17:45:43   dp_02           close
     2023-02-23 17:49:59   dp_101          8
     2023-02-23 17:36:06   dp_102          0
     2023-02-23 17:45:51   dp_105          close
     2023-02-23 17:36:09   dp_106          62
     2023-02-23 17:37:03   dp_13           0
     2023-02-23 17:46:24   dp_22           cancel
     2023-02-23 17:46:24   dp_23           0
     2023-02-13 23:11:22   icon            smart/icon/bay1579257011827QOvk/05cb05801c69fa7b6bdacda9c7f21196.png
     2023-02-13 23:11:22   id              bf75378cf6e13718e0rvcj
     2023-02-13 23:11:22   ip              88.153.83.160
     2023-02-13 23:11:22   lat             51.0583
     2023-02-13 23:11:22   local_key       7ada5a7cbf4a78e8
     2023-02-13 23:11:22   lon             6.1030
     2023-02-13 23:11:22   name            Schlafzimmerventilator
     2023-02-13 23:11:22   online          1
     2023-02-13 23:11:22   owner_id        23921647
     2023-02-13 23:11:22   product_id      6awobc9jfnlwvqtw
     2023-02-13 23:11:22   product_name    ARC Humidifier
     2023-02-23 17:32:59   state           on
     2023-02-13 23:11:22   sub             0
     2023-02-13 23:11:22   switch          on
     2023-02-23 17:39:22   switch_horizontal off
     2023-02-13 23:11:22   time_zone       +02:00
     2023-02-13 23:11:22   uid             eu1610479166063muAw8
     2023-02-13 23:11:22   update_time     1654518998
     2023-02-13 23:11:22   uuid            fd0c8a9f78a36684
   args:
     tuya_local_bf75378cf6e13718e0rvcj
     fhempy
     tuya
     6awobc9jfnlwvqtw
     bf75378cf6e13718e0rvcj
     192.168.178.169
     7ada5a7cbf4a78e8
     3.3
     asfg5sj9aurr9nib73fx
     fc553d7a6bfa4a569bc69ed2aa6924ed
   argsh:
Attributes:
   alias      Schlafzimmerventilator
   cmdIcon    on:general_an off:general_aus
   devStateIcon aus:ios-off:an an:ios-on-blue:aus off:ios-off:on on:ios-on-green:off
   dp_01      switch
   group      Geräte
   icon       Ventilator_fett
   room       Wohnung->Schlafzimmer,fhempy
   tuya_spec_functions [{'code': 'switch', 'dp_id': 1, 'type': 'Boolean', 'values': {}, 'desc': 'switch'}, {'code': 'fan_speed_percent', 'dp_id': 3, 'type': 'Integer', 'values': {'min': '1', 'max': '9', 'scale': '0', 'step': '1'}, 'desc': 'fan speed percent'}, {'code': 'switch_horizontal', 'dp_id': 5, 'type': 'Boolean', 'values': {}, 'desc': 'switch horizontal'}]
   tuya_spec_status [{'code': 'switch', 'dp_id': 1, 'type': 'Boolean', 'values': {}}, {'code': 'fan_speed_percent', 'dp_id': 3, 'type': 'Integer', 'values': {'min': '1', 'max': '9', 'scale': '0', 'step': '1'}}, {'code': 'switch_horizontal', 'dp_id': 5, 'type': 'Boolean', 'values': {}}]
   webCmd     : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : : :on:off

Zusätzlich auch ein Screenshot der Weboberfläche. Ist das mit dem Text "Switch" unterhalb des Set-Befehls richtig so?

Außerdem die gewünschte Tabelle. Hoffe es ist selbsterklärend. Was wie gesagt an Readings noch komplett fehlt ist die Angabe des "Fan-Speed" in 1er Stufen von 1-9, so wie es in den Attributen auch drin steht. Wäre natürlich ebenfalls als Funktion zu konzipieren.
Wurde früher über das Tuya-Cloud-Modul auch angezeigt und war einstellbar. Nur als Hinweis.

Hier nun der Hinweis wie du das selbst umsetzen kannst was in der Tabelle steht:

dp_02         Modus         Funktion und Info      sleep/fresh/strong/auto/close
anhand der Werte erkennt man, dass es ein Enum ist, also eine Aufzählung unterschiedlicher Strings

{'code': 'modus', 'dp_id': 2, 'type': 'Enum', 'values': '{"range":["sleep","fresh","strong", "auto", "close"]}', 'desc': 'modus'}
das fügst du in status und function ein, dann solltest du es setzen können und den aktuellen Wert im Reading modus sehen.

[thburkhart]

Ist schade, dass tuya da bei manchen Werte falsche Specs liefert. Ich habe cur_power "korrigiert".

energy kommt erst wenn cur_power > 0. Vielleicht ist das noch nicht der Fall?

ich habe es nun irgendwie hingekriegt, dass alle Stecker nun mal ein energy. Reading gekriegt haben. Bis auf eines:

Code Auswählen Erweitern

[code]define TUYA_SP04 fhempy tuya IGzCi97RpN2Lf9cu 045074212462ab24e988 192.168.9.34

attr TUYA_SP04 DbLogInclude energy,cur_power
attr TUYA_SP04 alias SP04 Spuelmaschine
attr TUYA_SP04 dp_01 switch_1
attr TUYA_SP04 dp_09 countdown_1
attr TUYA_SP04 dp_17 add_ele
attr TUYA_SP04 dp_18 cur_current
attr TUYA_SP04 dp_19 cur_power
attr TUYA_SP04 dp_20 cur_voltage
attr TUYA_SP04 event-min-interval .*:300
attr TUYA_SP04 group Schalter (T),Schalter Strommessung
attr TUYA_SP04 room -TUYA
attr TUYA_SP04 stateFormat E: energy kWh cP: cur_power W cV: cur_voltage V
attr TUYA_SP04 tuya_spec_functions [{'code': 'switch_1', 'dp_id': 1, 'type': 'Boolean', 'values': {}, 'desc': 'switch 1'}, {'code': 'countdown_1', 'dp_id': 9, 'type': 'Integer', 'values': {'unit': 's', 'min': 0, 'max': 86400, 'scale': 0, 'step': 1}, 'desc': 'countdown 1'}]
attr TUYA_SP04 tuya_spec_status [{'code': 'switch_1', 'dp_id': 1, 'type': 'Boolean', 'values': {}}, {'code': 'countdown_1', 'dp_id': 9, 'type': 'Integer', 'values': {'unit': 's', 'min': 0, 'max': 86400, 'scale': 0, 'step': 1}}, {'code': 'add_ele', 'dp_id': 17, 'type': 'Integer', 'values': {'unit': '', 'min': 0, 'max': 50000, 'scale': 3, 'step': 100}}, {'code': 'cur_current', 'dp_id': 18, 'type': 'Integer', 'values': {'unit': 'mA', 'min': 0, 'max': 30000, 'scale': 0, 'step': 1}}, {'code': 'cur_power', 'dp_id': 19, 'type': 'Integer', 'values': {'unit': 'W', 'min': 0, 'max': 50000, 'scale': 1, 'step': 1}}, {'code': 'cur_voltage', 'dp_id': 20, 'type': 'Integer', 'values': {'unit': 'V', 'min': 0, 'max': 5000, 'scale': 1, 'step': 1}}]
#   DEF        tuya IGzCi97RpN2Lf9cu 045074212462ab24e988 192.168.9.34 6e637c2cfed441d8 3.3 ea8453wdazquzfl08l0e 8a4b27dd759d4c6a9456aa8155d2a0ea
#   DEVICEID   045074212462ab24e988
#   FHEMPYTYPE tuya
#   FUUID      639f5053-f33f-fd5f-fbb4-5bcbd31a3c49c916
#   IODev      local_pybinding
#   NAME       TUYA_SP04
#   NR         1772
#   PYTHONTYPE tuya
#   STATE      E: energy kWh cP: cur_power W cV: cur_voltage V
#   TYPE       fhempy
#   eventCount 2
#   READINGS:
#     2023-02-24 09:58:14   online          1
#     2023-02-24 09:58:14   state           ready
#   args:
#     TUYA_SP04
#     fhempy
#     tuya
#     IGzCi97RpN2Lf9cu
#     045074212462ab24e988
#     192.168.9.34
#     6e637c2cfed441d8
#     3.3
#     ea8453wdazquzfl08l0e
#     8a4b27dd759d4c6a9456aa8155d2a0ea
#   argsh:
#
setstate TUYA_SP04 E: energy kWh cP: cur_power W cV: cur_voltage V
setstate TUYA_SP04 2023-02-24 09:58:14 online 1
setstate TUYA_SP04 2023-02-24 09:58:14 state ready

[/code]

Das ist die Spülmaschine. Über App kann ich sie schalten; nicht aber über FHEM. Liedfert keine readings

Wie bei alle anderen SP-Steckdosen wird kein Event erzeugt und somit nichts in die DB geschrieben.

Woran könnte das liegen ?

[dominik]

Ist die IP weiterhin korrekt oder hat die Steckdose vllt eine andere bekommen?

[thburkhart]

Ist die IP weiterhin korrekt oder hat die Steckdose vllt eine andere bekommen?

ja die IP stimmt und die MAC

[thburkhart]

hmm

allerdings sehe ich eben fhempy log:

Code Auswählen Erweitern

2023-02-24 13:18:50,125 - WARNING  - asyncio: socket.send() raised exception.
2023-02-24 13:18:55,138 - WARNING  - asyncio: socket.send() raised exception.
2023-02-24 13:18:57,739 - WARNING  - asyncio: socket.send() raised exception.
2023-02-24 13:19:00,153 - WARNING  - asyncio: socket.send() raised exception.
2023-02-24 13:19:05,165 - WARNING  - asyncio: socket.send() raised exception.
2023-02-24 13:19:07,753 - WARNING  - asyncio: socket.send() raised exception.
2023-02-24 13:19:10,176 - WARNING  - asyncio: socket.send() raised exception.
2023-02-24 13:19:15,189 - WARNING  - asyncio: socket.send() raised exception.
2023-02-24 13:19:17,765 - WARNING  - asyncio: socket.send() raised exception.
2023-02-24 13:19:20,201 - WARNING  - asyncio: socket.send() raised exception.
2023-02-24 13:19:25,215 - WARNING  - asyncio: socket.send() raised exception.
2023-02-24 13:19:27,778 - WARNING  - asyncio: socket.send() raised exception.
2023-02-24 13:19:30,226 - WARNING  - asyncio: socket.send() raised exception.
2023-02-24 13:19:35,239 - WARNING  - asyncio: socket.send() raised exception.
2023-02-24 13:19:37,789 - WARNING  - asyncio: socket.send() raised exception.
2023-02-24 13:19:40,256 - WARNING  - asyncio: socket.send() raised exception.
2023-02-24 13:19:45,281 - WARNING  - asyncio: socket.send() raised exception.
2023-02-24 13:19:47,802 - WARNING  - asyncio: socket.send() raised exception.
2023-02-24 13:19:48,381 - WARNING  - asyncio: socket.send() raised exception.

und das seit Mitternacht
und nach fhme shutdown restart:

Code Auswählen Erweitern

2023-02-24 13:22:47,059 - INFO     - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.606...
2023-02-24 13:22:47,063 - INFO     - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-02-24 13:22:47,103 - INFO     - websockets.server: server listening on 0.0.0.0:15733
2023-02-24 13:22:54,984 - INFO     - websockets.server: connection open
2023-02-24 13:22:54,985 - INFO     - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2023-02-24 13:23:13,088 - ERROR    - TUYA_STF3: Failed create_device
Traceback (most recent call last):
  File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 547, in create_device
    await self._create_cloudmapping_dev()
  File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 442, in _create_cloudmapping_dev
    await self.retrieve_tuya_specs()
  File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 417, in retrieve_tuya_specs
    spec = await self.get_tuya_dev_specification()
  File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 371, in get_tuya_dev_specification
    return resp["result"]
KeyError: 'result'
TUYA_STF3 ist ein Flächenschalter, der noch in der Schublade liegt

und die Fhem.log:

Code Auswählen Erweitern

023.02.24 13:22:20 2: DbLog dblog_THB - Wait for last database cycle due to shutdown ...
2023.02.24 13:22:20 1: Server shutdown delayed due to dblog_THB,alexa for max 10 sec
2023.02.24 13:22:20 2: DbLog dblog_THB - Last database write cycle done
2023.02.24 13:22:22 3: alexa: read: end of file reached while sysread
2023.02.24 13:22:22 3: alexa: stopped
2023.02.24 13:22:22 0: Server shutdown
2023.02.24 13:22:22 2: DbLog dblog_THB - stopping SubProcess PID >5643< ...
2023.02.24 13:22:22 2: DbLog dblog_THB - SubProcess PID >5643< stopped
2023.02.24 13:22:23 1: Including fhem.cfg
2023.02.24 13:22:24 2: DbLog dblog_THB - Subprocess >7578< initialized ... ready for non-blocking operation
2023.02.24 13:22:25 3: telnetPort: port 7072 opened
2023.02.24 13:22:25 3: WEB: port 8083 opened
2023.02.24 13:22:25 3: WEBphone: port 8084 opened
2023.02.24 13:22:25 3: WEBtablet: port 8085 opened
2023.02.24 13:22:25 3: TelegramBot_Define TelegramBotTHB: called
2023.02.24 13:22:26 3: BindingsIo v1.0.1
2023.02.24 13:22:26 3: fhempyServer v1.0.0
2023.02.24 13:22:26 3: fhempy v1.0.0 (tuya_cloud: TUYA)
2023.02.24 13:22:26 3: fhempy v1.0.0 (tuya: tuya_system)
2023.02.24 13:22:26 3: Opening CUL_0 device /dev/ttyACM0
2023.02.24 13:22:26 3: Setting CUL_0 serial parameters to 9600,8,N,1
2023.02.24 13:22:26 3: CUL_0: Possible commands: BbCFiAZNkGMKUYRTVWXefmLltux
2023.02.24 13:22:26 3: CUL_0 device opened
2023.02.24 13:22:26 2: Switched CUL_0 rfmode to MAX
2023.02.24 13:22:26 3: Opening JLLaCR device /dev/ttyUSB0
2023.02.24 13:22:26 3: Setting JLLaCR serial parameters to 57600,8,N,1
2023.02.24 13:22:27 3: JLLaCR device opened
2023.02.24 13:22:27 1: PERL WARNING: Use of uninitialized value in numeric ge (>=) at ./FHEM/12_OilFox.pm line 387, <$fh> line 570.
2023.02.24 13:22:27 2: LOGIN TOKEN MISSING OR EXPIRED
2023.02.24 13:22:27 3: myOilFox - email set to bkt@gmx.net
2023.02.24 13:22:27 3: myOilFox - set interval: 36000
2023.02.24 13:22:27 3: myOilFox - password set to thbbkt25
2023.02.24 13:22:27 3: powerfox: Defined with URL https://bkt%40gmx.net:thbbkt25@backend.powerfox.energy/api/2.0/my/246f283cfeac/current and interval 60 featurelevel 6.2
2023.02.24 13:22:43 2: eventTypes: loaded 16487 lines from ./log/eventTypes.txt
2023.02.24 13:22:43 3: TX29_00: I/O device is JLLaCR
2023.02.24 13:22:43 3: TX29DTH_01: I/O device is JLLaCR
2023.02.24 13:22:43 3: TX29DTH_02: I/O device is JLLaCR
2023.02.24 13:22:43 3: TX29DTH_03: I/O device is JLLaCR
2023.02.24 13:22:43 3: TX29DTH_04: I/O device is JLLaCR
2023.02.24 13:22:43 3: TX29DTH_05: I/O device is JLLaCR
2023.02.24 13:22:43 3: TX29DTH_06: I/O device is JLLaCR
2023.02.24 13:22:43 3: TX29DTH_07: I/O device is JLLaCR
2023.02.24 13:22:43 3: TX29DTH_08: I/O device is JLLaCR
2023.02.24 13:22:43 3: TX29DTH_09: I/O device is JLLaCR
2023.02.24 13:22:43 3: TX29DTH_10: I/O device is JLLaCR
2023.02.24 13:22:43 3: TX29DTH_11: I/O device is JLLaCR
2023.02.24 13:22:43 3: TX29DTH_12: I/O device is JLLaCR
2023.02.24 13:22:43 3: TX25IT_13: I/O device is JLLaCR
2023.02.24 13:22:43 3: TX29DTH_14: I/O device is JLLaCR
2023.02.24 13:22:43 3: TX29DTH_15: I/O device is JLLaCR
2023.02.24 13:22:43 3: TX29DTH_16: I/O device is JLLaCR
2023.02.24 13:22:43 3: TX29DTH_17: I/O device is JLLaCR
2023.02.24 13:22:43 3: TX29DTH_18: I/O device is JLLaCR
2023.02.24 13:22:43 3: TX29DTH_19: I/O device is JLLaCR
2023.02.24 13:22:43 3: TX29DTH_20: I/O device is JLLaCR
2023.02.24 13:22:43 3: TX29DTH_21: I/O device is JLLaCR
2023.02.24 13:22:43 3: TX29DTH_22: I/O device is JLLaCR
2023.02.24 13:22:43 3: HUEDevice2: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice4: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice5: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice6: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice7: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice8: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice10: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice17: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice18: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice19: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice20: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice22: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice23: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice24: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice25: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice27: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice28: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice29: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice30: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice31: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice32: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice33: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice38: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice39: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice40: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice41: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup0: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup1: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup2: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup3: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup4: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup5: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup6: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup7: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup8: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup9: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup10: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup11: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup12: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup13: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup14: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup15: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup16: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup17: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup18: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup19: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup20: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup21: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup22: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup23: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup24: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup25: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup26: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup27: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup28: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup29: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup30: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice44: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEGroup31: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUESensor6: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUESensor8: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUESensor10: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUESensor13: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUESensor24: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUESensor27: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUESensor34: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUESensor37: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUESensor45: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice45: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice46: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice47: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice48: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice49: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice50: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice51: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUESensor91: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUESensor110: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUESensor1: I/O device is hueBridge1
2023.02.24 13:22:43 3: HUEDevice52: I/O device is hueBridge1
2023.02.24 13:22:43 1: MaxTemp: WT
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_BULB01)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_BULB02)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya_cloud: TUYA_BULB03)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Camera1)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Camera2)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Camera3)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Camera4)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Camera5)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Camera6)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_DIY1)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_DIY3)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_DIY4)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_EMYLO1)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_EMYLO2)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_EMYLOD2)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_EMYLO3)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_EMYLO4)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL02)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL03)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL04)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL05)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL06)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL07)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL08)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL09)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL10Z)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL11Z)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL12Z)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL13)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL14)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL15)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL16)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL17)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL18)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya_cloud: TUYA_JL19)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL20)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL21)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL22)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL23)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL24)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya_cloud: TUYA_JL25)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL26)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL27)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL28)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL29)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL30)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL31)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL32)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL33)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL34)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL35)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_JL36)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_PS1)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_PS2)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_PS3)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_PS4)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_PS5)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_PS7)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_SCHF1)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_SCHF2)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_SCHF3)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya_cloud: TUYA_SCHFF4)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_SP01)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_SP02)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_SP03)
2023.02.24 13:22:44 3: fhempy v1.0.0 (tuya: TUYA_SP04)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya: TUYA_SP05)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya: TUYA_SP06)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya: TUYA_SP07)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya: TUYA_SP08)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya: TUYA_SP09)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya: TUYA_SP10)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya: TUYA_SP11)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya: TUYA_SP12)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya: TUYA_SP13)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya: TUYA_SP14)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya: TUYA_SP15)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya: TUYA_SP16)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya_cloud: TUYAC_PIR01)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya_cloud: TUYAC_PIR02)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya_cloud: TUYAC_PIR03)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorT01)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorT02)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorT03)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorT04)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorT05)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorW01)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorW02)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorW03)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorW04)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Sir01)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Sir02)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Sir03)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Relais01)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorSmoke01)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya: TUYA_STF1)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya: TUYA_STF2)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya: TUYA_STF3)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya: TUYA_MMG)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp01)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp02)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp03)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp04)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp05)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp06)
2023.02.24 13:22:45 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp07)
2023.02.24 13:22:45 1: PERL WARNING: Useless use of anonymous hash ({}) in void context at (eval 120) line 1, <$fh> line 6407.
2023.02.24 13:22:45 3: SST (SamsungSmartThingsConnector): define - CONNECTOR defined as SamsungSmartThingsConnector
2023.02.24 13:22:45 1: Including ./log/fhem.save
2023.02.24 13:22:45 1: Messages collected while initializing FHEM:SecurityCheck:
  WEB is not password protected
  WEBtablet is not password protected
  telnetPort is not password protected
  WEBphone is not password protected

Protect this FHEM installation by defining an allowed device with define allowed allowed
You can disable this message with attr global motd none

2023.02.24 13:22:46 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2023.02.24 13:22:46 3: alexa: starting
2023.02.24 13:22:46 3: alexa: using logfile: ./log/alexa-2023-02-24.log
2023.02.24 13:22:46 2: hueBridge1: autocreate: created 0/0/0 devices (ignored 0/2/26)
2023.02.24 13:22:47 3: n_global_INITIALIZED return value: Unknown command <set, try help.
2023.02.24 13:22:48 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2023.02.24 13:22:48 0: Featurelevel: 6.2
2023.02.24 13:22:48 0: Server started with 521 defined entities (fhem.pl:27110/2023-01-23 perl:5.032001 os:linux user:fhem pid:7577)
2023.02.24 13:22:48 3: DbLog dblog_THB - DB connection parameters are initialized in the SubProcess
2023.02.24 13:22:48 1: PERL WARNING: devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
2023.02.24 13:22:48 1: PERL WARNING: ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1304.
2023.02.24 13:22:50 3: DbLog dblog_THB - DB connection parameters are stored in SubProcess
2023.02.24 13:22:51 3: alexa: read: end of file reached while sysread
2023.02.24 13:22:51 3: alexa: stopped
2023.02.24 13:22:51 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2023.02.24 13:22:51 3: alexa: starting
2023.02.24 13:22:51 3: alexa: using logfile: ./log/alexa-2023-02-24.log
2023.02.24 13:22:52 2: AttrTemplates: got 258 entries
2023.02.24 13:22:55 1: PERL WARNING: Use of uninitialized value in string eq at ./FHEM/10_BindingsIo.pm line 548.
2023.02.24 13:22:57 2: {"token_type":"Bearer","access_token":"eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzUxMiJ9.eyJzdWIiOiJiNmU5ZDg5Ni1kMzMwLTRiMWYtODVhNS0wYjk4NGQyZWJiMDQiLCJhdWQiOiJVU0VSIiwic2NvcGUiOiJDVVNUT01FUl9BUEkiLCJpc3MiOiJvaWxmb3guaW8iLCJleHAiOjE2NzcyNDIyNzUsImp0aSI6IjQ2NTMzNTk5LWMzMDgtNGY4MC05OGFhLWViZTYzNDQ4ZWQ1MSIsImVtYWlsIjoiYmt0QGdteC5uZXQifQ.-s-Hu0X_CkGOjrbxpO6s4xaXgxp7s-nHlwiKO6fQEokbqTwEZIJLAlYP0ZziXcYYxgDiM1-7d_-QR7CsLiuzVg","refresh_token":"eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzUxMiJ9.eyJzY29wZSI6IkNVU1RPTUVSX0FQSSIsImlzcyI6Im9pbGZveC5pbyIsImV4cCI6MTY3ODUzNzM3NSwianRpIjoiYzQxY2QzYjctZTE0MC00ODgyLTkzMDctZDdhNGZkZmVkMjUwIn0.1bMZjohmAUV0bTKtCEHzRbGy5YJc4Gh3Avh2fawl0zvS5lWKDBg3Z2Xi4fhlEuo_AIClEBcc9pAOm-fC22virA"}
2023.02.24 13:23:03 2: hueBridge1: http request failed: read from https://192.168.9.179:443 timed out
2023.02.24 13:23:17 2: hueBridge1: EventStream: event for unknown device received, trying to refresh resouces
2023.02.24 13:23:18 2: hueBridge1: autocreate: created 0/0/0 devices (ignored 0/2/26)
2023.02.24 13:23:19 3: DbLog dblog_THB - SubProcess connected to fhem


[dominik]

Was sagt freezemon zu der Zeit?

[thburkhart]

Was sagt freezemon zu der Zeit?

nichts besonderes
inzwischen tauchen immer mehr JJs in der Datenbank auf:

Code Auswählen Erweitern

TUYA_JL03 2729 cur_current 2023-02-23 16:15:11 FHEMPY cur_current: 207.0
TUYA_JL04 8709 cur_current 2023-02-23 11:11:01 FHEMPY cur_current: 28.0
TUYA_JL05 31 online 2023-02-23 11:10:26 FHEMPY online: 0
TUYA_JL07 23 energy 2023-02-23 17:49:03 FHEMPY energy: 0.0
TUYA_JL08 13 energy 2023-02-23 17:48:53 FHEMPY energy: 0.0
TUYA_JL20 4 energy 2023-02-24 07:04:44 FHEMPY energy: 1.184
TUYA_JL24 15 energy 2023-02-24 00:24:40 FHEMPY energy: 0.0
TUYA_JL26 1 energy 2023-02-24 07:31:09 FHEMPY energy: 0.002
TUYA_JL29 5 energy 2023-02-23 21:46:23 FHEMPY energy: 0.035
TUYA_JL30 10 energy 2023-02-24 09:21:21 FHEMPY energy: 11.011
TUYA_JL32 1 energy 2023-02-24 07:17:04 FHEMPY energy: 0.0
TUYA_JL33 6 energy 2023-02-23 21:14:03 FHEMPY energy: 0.0
TUYA_JL34 30 energy 2023-02-24 00:09:36 FHEMPY energy: 0.127
TUYA_JL35 125 energy 2023-02-23 20:40:52 FHEMPY energy: 0.639
TUYA_JL36 1 energy 2023-02-23 22:23:09 FHEMPY energy: 0.0

in der Devicelist kommen alle energy-Werte bis auf SP04

Code Auswählen Erweitern

JL19 Heizkissen 2
on
off
JL20 Duravit Bidet
E: 1.753 kWh cP: 0.0 W cV: 230.1 V
on
off
JL21 Schnellkocher
E: energy kWh cP: 0.0 W cV: 0.0 V
on
off
JL22 frei
E: energy kWh cP: cur_power W cV: cur_voltage V
on
off
JL23 Heizdecke 2
E: energy kWh cP: cur_power W cV: cur_voltage V
on
off
JL24 USB Lader1 Bett
E: 0.453 kWh cP: 0.0 W cV: 229.3 V
on
off
JL25 USB Lader2 Thomas
E: 0.0 kWh cP: 69.0 W cV: 2277.0 V
on
off
JL26 USB Lader3 Thomas
E: 0.003 kWh cP: 0.0 W cV: 226.6 V
on
off
JL27 USB Lader4 Thomas
E: 0.001 kWh cP: 0.0 W cV: 226.6 V
on
off
JL28 Steckdose Garage 1
E: energy kWh cP: 0.0 W cV: 0.0 V
on
off
JL29 Leselampe 2
E: 0.172 kWh cP: 0.0 W cV: 229.0 V
on
off
JL30 Kaffeemaschine XELSIS
E: 21.804 kWh cP: 9.0 W cV: 232.1 V
on
off
JL31
E: energy kWh cP: 0.0 W cV: 224.0 V
on
off
JL32 Soundbar Wohnzimmer
E: 0.0 kWh cP: 0.0 W cV: 233.2 V
on
off
JL33 Schreibtisch Thomas
E: 0.086 kWh cP: 0.0 W cV: 0.0 V
on
off
JL34 Medien THOMAS
E: 4.956 kWh cP: 327.0 W cV: 230.6 V
on
off
JL35 GL AXT1800
E: 0.764 kWh cP: 0.0 W cV: 0.0 V
on
off
JL36 EX15 Fritzbox
E: 0.016 kWh cP: 0.0 W cV: 0.0 V
on
off
SP01 Waschmaschine
E: energy kWh cP: 0.0 W cV: 230.5 V
on
off
SP02 Kuehlschrank HWR
E: 3.968 kWh cP: 0.0 W cV: 227.9 V
on
off
SP03 Kuehlschrank Kueche
E: 0.543 kWh cP: 0.0 W cV: 212.1 V
on
off
SP04 Spuelmaschine
E: energy kWh cP: cur_power W cV: cur_voltage V
on
off
SP05 EX17
E: 0.195 kWh cP: 5.7 W cV: 210.7 V
on
off
SP06 Medien Wohnzimmer
E: 1.685 kWh cP: 0.0 W cV: 245.6 V
on
off
SP07 Garagenkeller
E: 0.109 kWh cP: 4.9 W cV: 224.0 V
on
off
SP08 Peugeot208
E: 26.008 kWh cP: 0.0 W cV: 225.9 V
on
off
SP09 Gartengrill
E: energy kWh cP: 0.0 W cV: 227.8 V
on
off
SP10 Medien Petra
E: 0.0 kWh cP: 0.0 W cV: 231.5 V
on
off
SP11 TH Ost
E: 0.771 kWh cP: 40.6 W cV: 229.9 V
on
off
SP12 TH Sued1
E: 1.286 kWh cP: 50.0 W cV: 229.5 V
on
off
SP13 TH Sued2 Schreibtisch
E: 1.087 kWh cP: 33.1 W cV: 228.0 V
on
off
SP14 PETRA SOst
E: 0.239 kWh cP: 6.2 W cV: 229.3 V
on
off
SP15 PETRA Bett
E: 0.152 kWh cP: 3.8 W cV: 227.6 V
on
off
SP16 TH West
E: 0.225 kWh cP: 7.8 W cV: 228.3 V
on
off[/code
Der SP04 ist aus derselben Charge wie SP01,SP02, SP04 (habe immer 4er-Packs gekauft)  übrigens sehr schaltstabil; an SP08 hängt das E-Auto zum laden


[dominik]

Bitte nicht zig Themen auf einmal ansprechen, sonst springen wir nur von einem zum nächsten und nix wird gelöst. Was soll jetzt gelöst werden?

Fokus SP4: Hat das Ding auch ein cur_power mit einem Wert >0?

[thburkhart]

Bitte nicht zig Themen auf einmal ansprechen, sonst springen wir nur von einem zum nächsten und nix wird gelöst. Was soll jetzt gelöst werden?

Fokus SP4: Hat das Ding auch ein cur_power mit einem Wert >0?

nein keine werte
nur per App

INFO:

Code Auswählen Erweitern

[code]define TUYA_SP04 fhempy tuya IGzCi97RpN2Lf9cu 045074212462ab24e988 192.168.9.34 6e637c2cfed441d8 3.3
attr TUYA_SP04 DbLogInclude energy,cur_power
attr TUYA_SP04 alias SP04 Spuelmaschine
attr TUYA_SP04 dp_01 switch_1
attr TUYA_SP04 dp_09 countdown_1
attr TUYA_SP04 dp_17 add_ele
attr TUYA_SP04 dp_18 cur_current
attr TUYA_SP04 dp_19 cur_power
attr TUYA_SP04 dp_20 cur_voltage
attr TUYA_SP04 event-min-interval .*:300
attr TUYA_SP04 group Schalter (T),Schalter Strommessung
attr TUYA_SP04 room -TUYA
attr TUYA_SP04 stateFormat E: energy kWh cP: cur_power W cV: cur_voltage V
attr TUYA_SP04 tuya_spec_functions [{'code': 'switch_1', 'dp_id': 1, 'type': 'Boolean', 'values': {}, 'desc': 'switch 1'}, {'code': 'countdown_1', 'dp_id': 9, 'type': 'Integer', 'values': {'unit': 's', 'min': 0, 'max': 86400, 'scale': 0, 'step': 1}, 'desc': 'countdown 1'}]
attr TUYA_SP04 tuya_spec_status [{'code': 'switch_1', 'dp_id': 1, 'type': 'Boolean', 'values': {}}, {'code': 'countdown_1', 'dp_id': 9, 'type': 'Integer', 'values': {'unit': 's', 'min': 0, 'max': 86400, 'scale': 0, 'step': 1}}, {'code': 'add_ele', 'dp_id': 17, 'type': 'Integer', 'values': {'unit': '', 'min': 0, 'max': 50000, 'scale': 3, 'step': 100}}, {'code': 'cur_current', 'dp_id': 18, 'type': 'Integer', 'values': {'unit': 'mA', 'min': 0, 'max': 30000, 'scale': 0, 'step': 1}}, {'code': 'cur_power', 'dp_id': 19, 'type': 'Integer', 'values': {'unit': 'W', 'min': 0, 'max': 50000, 'scale': 1, 'step': 1}}, {'code': 'cur_voltage', 'dp_id': 20, 'type': 'Integer', 'values': {'unit': 'V', 'min': 0, 'max': 5000, 'scale': 1, 'step': 1}}]
#   DEF        tuya IGzCi97RpN2Lf9cu 045074212462ab24e988 192.168.9.34 6e637c2cfed441d8 3.3 ea8453wdazquzfl08l0e 8a4b27dd759d4c6a9456aa8155d2a0ea
#   DEVICEID   045074212462ab24e988
#   FHEMPYTYPE tuya
#   FUUID      639f5053-f33f-fd5f-fbb4-5bcbd31a3c49c916
#   IODev      local_pybinding
#   NAME       TUYA_SP04
#   NR         1772
#   PYTHONTYPE tuya
#   STATE      E: energy kWh cP: cur_power W cV: cur_voltage V
#   TYPE       fhempy
#   eventCount 2
#   READINGS:
#     2023-02-24 15:44:04   online          1
#     2023-02-24 15:44:04   state           ready
#   args:
#     TUYA_SP04
#     fhempy
#     tuya
#     IGzCi97RpN2Lf9cu
#     045074212462ab24e988
#     192.168.9.34
#     6e637c2cfed441d8
#     3.3
#     ea8453wdazquzfl08l0e
#     8a4b27dd759d4c6a9456aa8155d2a0ea
#   argsh:
#
setstate TUYA_SP04 E: energy kWh cP: cur_power W cV: cur_voltage V
setstate TUYA_SP04 2023-02-24 15:44:04 online 1
setstate TUYA_SP04 2023-02-24 15:44:04 state ready

[/code]

also nur state und online ist da

zum Vergleich SP03:

Code Auswählen Erweitern

[code]define TUYA_SP03 fhempy tuya IGzCi97RpN2Lf9cu 260064612462ab24f164 192.168.9.33 b37a96597e2837b4 3.3
attr TUYA_SP03 DbLogExclude .*
attr TUYA_SP03 DbLogInclude energy
attr TUYA_SP03 alias SP03 Kuehlschrank Kueche
attr TUYA_SP03 dp_01 switch_1
attr TUYA_SP03 dp_09 countdown_1
attr TUYA_SP03 dp_17 add_ele
attr TUYA_SP03 dp_18 cur_current
attr TUYA_SP03 dp_19 cur_power
attr TUYA_SP03 dp_20 cur_voltage
attr TUYA_SP03 event-min-interval .*:300
attr TUYA_SP03 group Schalter (T),Schalter Strommessung
attr TUYA_SP03 room -TUYA
attr TUYA_SP03 stateFormat E: energy kWh cP: cur_power W cV: cur_voltage V
attr TUYA_SP03 tuya_spec_functions [{'code': 'switch_1', 'dp_id': 1, 'type': 'Boolean', 'values': {}, 'desc': 'switch 1'}, {'code': 'countdown_1', 'dp_id': 9, 'type': 'Integer', 'values': {'unit': 's', 'min': 0, 'max': 86400, 'scale': 0, 'step': 1}, 'desc': 'countdown 1'}]
attr TUYA_SP03 tuya_spec_status [{'code': 'switch_1', 'dp_id': 1, 'type': 'Boolean', 'values': {}}, {'code': 'countdown_1', 'dp_id': 9, 'type': 'Integer', 'values': {'unit': 's', 'min': 0, 'max': 86400, 'scale': 0, 'step': 1}}, {'code': 'add_ele', 'dp_id': 17, 'type': 'Integer', 'values': {'unit': '', 'min': 0, 'max': 50000, 'scale': 3, 'step': 100}}, {'code': 'cur_current', 'dp_id': 18, 'type': 'Integer', 'values': {'unit': 'mA', 'min': 0, 'max': 30000, 'scale': 0, 'step': 1}}, {'code': 'cur_power', 'dp_id': 19, 'type': 'Integer', 'values': {'unit': 'W', 'min': 0, 'max': 50000, 'scale': 1, 'step': 1}}, {'code': 'cur_voltage', 'dp_id': 20, 'type': 'Integer', 'values': {'unit': 'V', 'min': 0, 'max': 5000, 'scale': 1, 'step': 1}}]
#   DEF        tuya IGzCi97RpN2Lf9cu 260064612462ab24f164 192.168.9.33 b37a96597e2837b4 3.3 ea8453wdazquzfl08l0e 8a4b27dd759d4c6a9456aa8155d2a0ea
#   DEVICEID   260064612462ab24f164
#   FHEMPYTYPE tuya
#   FUUID      63a21338-f33f-fd5f-880d-8677bdc30df59441
#   IODev      local_pybinding
#   NAME       TUYA_SP03
#   NR         1770
#   PYTHONTYPE tuya
#   STATE      E: 0.543 kWh cP: 0.0 W cV: 212.1 V
#   TYPE       fhempy
#   eventCount 3
#   READINGS:
#     2023-01-30 08:00:12   countdown_1     0.0
#     2023-02-24 09:23:41   cur_current     0.0
#     2023-02-24 09:23:41   cur_power       0.0
#     2023-02-24 15:43:50   cur_voltage     212.1
#     2023-01-30 08:00:12   dp_21           2
#     2023-01-30 08:00:12   dp_22           0
#     2023-01-30 08:00:12   dp_23           0
#     2023-01-30 08:00:12   dp_24           0
#     2023-01-30 08:00:12   dp_25           0
#     2023-02-24 09:23:28   energy          0.543
#     2023-02-24 15:43:50   online          1
#     2023-02-24 15:44:08   state           off
#     2023-02-24 09:42:57   switch_1        off
#   args:
#     TUYA_SP03
#     fhempy
#     tuya
#     IGzCi97RpN2Lf9cu
#     260064612462ab24f164
#     192.168.9.33
#     b37a96597e2837b4
#     3.3
#     ea8453wdazquzfl08l0e
#     8a4b27dd759d4c6a9456aa8155d2a0ea
#   argsh:
#
setstate TUYA_SP03 E: 0.543 kWh cP: 0.0 W cV: 212.1 V
setstate TUYA_SP03 2023-01-30 08:00:12 countdown_1 0.0
setstate TUYA_SP03 2023-02-24 09:23:41 cur_current 0.0
setstate TUYA_SP03 2023-02-24 09:23:41 cur_power 0.0
setstate TUYA_SP03 2023-02-24 15:43:50 cur_voltage 212.1
setstate TUYA_SP03 2023-01-30 08:00:12 dp_21 2
setstate TUYA_SP03 2023-01-30 08:00:12 dp_22 0
setstate TUYA_SP03 2023-01-30 08:00:12 dp_23 0
setstate TUYA_SP03 2023-01-30 08:00:12 dp_24 0
setstate TUYA_SP03 2023-01-30 08:00:12 dp_25 0
setstate TUYA_SP03 2023-02-24 09:23:28 energy 0.543
setstate TUYA_SP03 2023-02-24 15:43:50 online 1
setstate TUYA_SP03 2023-02-24 15:44:08 state off
setstate TUYA_SP03 2023-02-24 09:42:57 switch_1 off

[/code]