Hi,
ich habe ein Modul in fhempy gebaut, welches mit allen Tuya Devices über die Cloud sprechen kann. Der große Vorteil, man bekommt real-time Updates über die Cloud und muss kein Polling der Devices machen.
Anleitung zur Einrichtung:
1. fhempy installieren
https://github.com/dominikkarall/fhempy#installation
2. Tuya einrichten
https://github.com/dominikkarall/fhempy/blob/master/FHEM/bindings/python/fhempy/lib/tuya_cloud/README.md
Hallo,
leider komme ich bei der Grundinstallation evon fhempy auf meiner fhem Instanz nicht weiter:
pi@raspberrypi:~ $ pip3 install --upgrade fhempy
WARNING: pip is being invoked by an old script wrapper. This will fail in a future version of pip.
Please see https://github.com/pypa/pip/issues/5599 for advice on fixing the underlying issue.
To avoid this problem you can invoke Python with '-m pip' instead of running pip directly.
DEPRECATION: Python 3.5 reached the end of its life on September 13th, 2020. Please upgrade your Python as Python 3.5 is no longer maintained. pip 21.0 will drop support for Python 3.5 in January 2021. pip 21.0 will remove support for this functionality.
Defaulting to user installation because normal site-packages is not writeable
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
ERROR: Could not find a version that satisfies the requirement fhempy
ERROR: No matching distribution found for fhempy
Nachtrag jetzt hab ich fhempy auf ner ubuntu 20.04 eingerichtet, aber sobald fhem darauf zugreift wirft er folgende Fehler aus:
RuntimeError: The event loop is not running
2021-07-31 08:41:34,188 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 10.10.20.109
2021-07-31 08:41:34,191 - ERROR - websockets.server: Error in connection handler
Traceback (most recent call last):
File "/home/bitnami/.local/lib/python3.8/site-packages/websockets/legacy/server.py", line 293, in handler
await self.ws_handler(self, path)
File "/home/bitnami/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 63, in pybinding
await activate_internal_modules()
File "/home/bitnami/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 46, in activate_internal_modules
await instance.activate()
File "/home/bitnami/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 82, in activate
await self.runZeroconfScan()
File "/home/bitnami/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 79, in runZeroconfScan
self.browser = ServiceBrowser(self.zeroconf, services, listener)
File "/home/bitnami/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 505, in __init__
raise RuntimeError("The event loop is not running")
Deine Python Installation ist schon end of life. Nutzt du Raspbian? Mach mal sudo apt update und dann sudo apt install python3.
habe ich bereits gemacht, hat nicht geklappt drum hab ich das auf ubuntu installiert.
defmod fhempy_remote_IP BindingsIo fhempy-ip:15733 Python
Dann ist dein Raspbian noch eine alte Distribution wahrscheinlich. Sollte Buster sein.
Jetzt hat's geklappt?
leider nein, wegen der alten buster hab ich fhempy auf ubuntu gelegt:
RuntimeError: The event loop is not running
2021-07-31 08:41:34,188 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 10.10.20.109
2021-07-31 08:41:34,191 - ERROR - websockets.server: Error in connection handler
Traceback (most recent call last):
File "/home/bitnami/.local/lib/python3.8/site-packages/websockets/legacy/server.py", line 293, in handler
await self.ws_handler(self, path)
File "/home/bitnami/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 63, in pybinding
await activate_internal_modules()
File "/home/bitnami/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 46, in activate_internal_modules
await instance.activate()
File "/home/bitnami/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 82, in activate
await self.runZeroconfScan()
File "/home/bitnami/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 79, in runZeroconfScan
self.browser = ServiceBrowser(self.zeroconf, services, listener)
File "/home/bitnami/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 505, in __init__
raise RuntimeError("The event loop is not running")
fhem versucht zu connecten, aber fhempy bringt o.g. Fehler.
Hm...mach mal
pip3 install -U websockets
pip3 install -U zeroconf
Poste auch bitte das gesamte Log vom Start weg.
war schon drauf websocket und zeroconf
bitnami@ubuntu-04:~$ fhempy
2021-07-31 10:44:31,320 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-07-31 10:44:31,325 - INFO - fhempy.lib.fhem_pythonbinding: Advertise fhempy on local network
2021-07-31 10:44:32,133 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
das hier kommt in Dauerschleife während FHem versucht zu verbinden:
2021-07-31 10:45:28,470 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 10.10.20.109
2021-07-31 10:45:28,472 - ERROR - websockets.server: Error in connection handler
Traceback (most recent call last):
File "/home/bitnami/.local/lib/python3.8/site-packages/websockets/legacy/server.py", line 293, in handler
await self.ws_handler(self, path)
File "/home/bitnami/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 63, in pybinding
await activate_internal_modules()
File "/home/bitnami/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 46, in activate_internal_modules
await instance.activate()
File "/home/bitnami/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 82, in activate
await self.runZeroconfScan()
File "/home/bitnami/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 79, in runZeroconfScan
self.browser = ServiceBrowser(self.zeroconf, services, listener)
File "/home/bitnami/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 505, in __init__
raise RuntimeError("The event loop is not running")
RuntimeError: The event loop is not running
Hallo,
Ich habe eine Frage. Könnte man damit auch die Lidl Produkte ,wie den Parkside Bewässerungscomputer, der ja auch ein Tuya device ist und im Moment mit deconz/Phoscon und zigbee2mqtt nur eingeschränkt funktioniert, benutzen?
Siehe hier:
https://forum.fhem.de/index.php/topic,121983.msg1165870.html#msg1165870
(https://forum.fhem.de/index.php/topic,121983.msg1165870.html#msg1165870)
Gruß Carlos
Zitat von: patator am 31 Juli 2021, 10:46:29
war schon drauf websocket und zeroconf
bitnami@ubuntu-04:~$ fhempy
2021-07-31 10:44:31,320 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-07-31 10:44:31,325 - INFO - fhempy.lib.fhem_pythonbinding: Advertise fhempy on local network
2021-07-31 10:44:32,133 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
das hier kommt in Dauerschleife während FHem versucht zu verbinden:
2021-07-31 10:45:28,470 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 10.10.20.109
2021-07-31 10:45:28,472 - ERROR - websockets.server: Error in connection handler
Traceback (most recent call last):
File "/home/bitnami/.local/lib/python3.8/site-packages/websockets/legacy/server.py", line 293, in handler
await self.ws_handler(self, path)
File "/home/bitnami/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 63, in pybinding
await activate_internal_modules()
File "/home/bitnami/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 46, in activate_internal_modules
await instance.activate()
File "/home/bitnami/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 82, in activate
await self.runZeroconfScan()
File "/home/bitnami/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 79, in runZeroconfScan
self.browser = ServiceBrowser(self.zeroconf, services, listener)
File "/home/bitnami/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 505, in __init__
raise RuntimeError("The event loop is not running")
RuntimeError: The event loop is not running
Hast du fhempy mit dem bitnami User installiert, oder als root/sudo?
Zitat von: carlos am 31 Juli 2021, 10:47:55
Hallo,
Ich habe eine Frage. Könnte man damit auch die Lidl Produkte ,wie den Parkside Bewässerungscomputer, der ja auch ein Tuya device ist und im Moment mit deconz/Phoscon und zigbee2mqtt nur eingeschränkt funktioniert, benutzen?
Siehe hier:
https://forum.fhem.de/index.php/topic,121983.msg1165870.html#msg1165870
(https://forum.fhem.de/index.php/topic,121983.msg1165870.html#msg1165870)
Gruß Carlos
Wenn es ein tuya device ist, sollte es problemlos funktionieren.
Zitat von: dominik am 31 Juli 2021, 13:05:43
Hast du fhempy mit dem bitnami User installiert, oder als root/sudo?
ich habe beide probiert
Zitat von: dominik am 31 Juli 2021, 13:50:35
Wenn es ein tuya device ist, sollte es problemlos funktionieren.
Cooles Modul! Danke Schön für die Arbeit! Installation hat soweit funktioniert!
Ich sehe auch den Parkside Bewässerungscomputer. Sollten zu dem Gerät noch Readings kommen wie die z.B. der Countdown? (Gerät wird über das Silvercrest Gateway in Smart Life / Tuya eingebunden)
In Tuya IoT unter Device Debug sehe ich, dass die eingestellte Bewässerungszeit mit der DP ID Countdown geführt wird.
In der folge wäre es natürlich richtig cool, wenn der Countdown geändert werden könnte über ein FHEM Attribut??
Mehr als ein Ready sehe ich bisher nicht im Device
Internals:
CFGFN
DEF tuya_cloud tuya_cloud_connector xxxxxxx
DEVICEID xxxxxxx
FUUID 61055fcd-f33f-6bbc-f1d4-8834b43445578c63
IODev local_pybinding
NAME Wassercomputer_xxxxx
NR 32
PYTHONTYPE tuya_cloud
STATE ready
TYPE PythonModule
READINGS:
2021-07-31 16:35:58 state ready
args:
Wassercomputer_xxxxxx
PythonModule
tuya_cloud
tuya_cloud_connector
xxxxxxx
argsh:
Attributes:
alias Wassercomputer
Aha, da fehlen scheinbar noch die Infos aus der Tuya Cloud.
Wäre es ok, wenn du mir per PN die Daten zum Testen schickst? So kommen wir wahrscheinlich am schnellsten weiter.
//Edit: Oder du kannst mir das Device in der SmartLife App teilen, habe ich zwar noch nicht probiert, aber müsste auch klappen.
Zitat von: dominik am 31 Juli 2021, 20:20:35
Aha, da fehlen scheinbar noch die Infos aus der Tuya Cloud.
Wäre es ok, wenn du mir per PN die Daten zum Testen schickst? So kommen wir wahrscheinlich am schnellsten weiter.
//Edit: Oder du kannst mir das Device in der SmartLife App teilen, habe ich zwar noch nicht probiert, aber müsste auch klappen.
PM is raus.
@Udomatic
Du hast den Bewässerungscomputer über das silvercrest Gateway in der Tuya Cloud eingebunden. Mit welcher App hast du das gemacht? Mit der Lidl Home App?
Man braucht wohl zwingend das Silvercrest Gateway von Lidl, das ich im Moment nicht habe.
Ist das App seitig dann auch so?
Oder geht hier auch die Tuya App?
Ich überlege wie ich hier weiter vorgehen.
Gruß
Carlos
Zitat von: carlos am 01 August 2021, 09:38:53
@Udomatic
Du hast den Bewässerungscomputer über das silvercrest Gateway in der Tuya Cloud eingebunden. Mit welcher App hast du das gemacht? Mit der Lidl Home App?
Man braucht wohl zwingend das Silvercrest Gateway von Lidl, das ich im Moment nicht habe.
Ist das App seitig dann auch so?
Oder geht hier auch die Tuya App?
Ich überlege wie ich hier weiter vorgehen.
Gruß
Carlos
Ja, die LIDL App ist nur ein abgespeckter Clon der Smart Life App. Sieht im Prinzip identisch aus, hat aber weniger Funktionen, wie zum Besipiel die fehlenden Funktion der Anbindung Sprachassistenten wie Alexa.
Daher nutze ich nur die Smart Life App bei tuya Geräten. Du kannst in der Smart Life App also das Silvercrest Gateway und den Bewässerungscomputer genauso anlernen, wie in der LIDL Home App. Du bekommst halt nur über das Silvercrest Gateway das Device in die tuya Cloud. Über Conbee kenne ich keinen Weg das Gerät in die tuya Cloud zu bekommen, da tuya das Conbee Gateway nicht kennt und ohne Gateway kann das Zigbee Device nicht angelernt werden.
Falls es über Conbee trotzdem einen Weg in die tuya Cloud gibt , sodass das Silvercrest Gateway nicht benötigt wird, lerne ich gerne dazu.
Gruß
Udo
Hallo Udo,
Danke für die Info.
Ich habe im Moment über zigbee2mqtt das Intervall auf 5min geändert und nutze ihn jetzt mit deconz als Licht mit nur an/aus. Den Rest kann man dann mit doif und/oder weekdaytimer in fhem abdecken.
Und ja meines Wissens gibt es weder bei zigbee2mqtt noch bei deconz einen Weg in die Tuya Cloud.
Vielleicht ist es aber längerfristig gesehen doch der bessere Weg über die Tuya Cloud.
Ist halt wieder eine zusätzliche Abhängigkeit.
Äber das muss man jeder selbst für sich entscheiden.
Ich beobachte das Ganze mal weiter.
Gruß
Carlos
ich weiß nicht so genau, ob das hier der richtige Ort für diese Diskussion ist?!?
ich habe gerade als "Mega Schnäppchen" ;) Ledvance WIFI GU10 RGB bekommen, 3 Stk. für 12€, aber das nur am Rande.
die Ledvance sind offensichtlich Tuya basiert. Die Tuya App zeigt sie sogar an aber ich kann sie nicht einbinden.
die Ledvance App ist gnauso offensichtlich ein "Ableger" der Tuya Smart App.
so nun meine eigentliche Frage, was macht mehr Sinn oder hat beides keine Aussicht auf Erfolg:
a) Ledvance Leuchtmittel in die Tuya App eininden
b) Ledvance App mit FHEM verheiraten
???
Verbinde es mit der SmartLife App und danach kannst du die wahrscheinlich mit dem Modul hier nutzen. SmartLife geht trotzdem parallel, man muss also auf nichts verzichten.
Mist, das funktioniert leider nicht. Das schnelle Blinken hört auf aber das Pairing klappt nicht (mit "jungfräulicher" Ledvance und auch einer, die schon ein FW bekommen hat). Auch im AP Modus komme ich nicht weiter.
das hat aber mit diesem Thema hier nichts zu tun, da muss ich woanders suchen wie ich weiter komme.
Für Tipps bin ich aber natürlich trotzdem dankbar!
Hallo,
Sorry, aber ich bekomme es nicht hin. Das Binding klappt. Aber die Verbindung zu Tuya nicht..
2021-08-02 10:59:02,357 - INFO - __main__: Attempting install of fhempy>=0.1.12
2021-08-02 10:59:34,635 - INFO - __main__: Successfully installed fhempy>=0.1.12
2021-08-02 10:59:34,637 - ERROR - __main__: Failed to import fhempy, exit now...
2021-08-02 11:00:36,005 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-08-02 11:00:36,030 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-08-02 11:07:18,401 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-08-02 11:07:18,426 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-08-02 11:07:31,486 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-08-02 11:07:31,511 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-08-02 11:07:35,534 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-08-02 11:07:35,647 - INFO - fhempy.lib.pkg_installer: Attempting install of tuya-iot-py-sdk
2021-08-02 11:07:55,483 - ERROR - tuya_cloud_connector: Tuya login error response: {'code': 1106, 'msg': 'permission deny', 'success': False, 't': 1627895275469}
Habe die Tuya-App. Devices sind in Tuya-Cloud sichtbar. User und Passwort der App vom Handy sind richtig..
Fhem neu aufgesetzt auf frischem Raspian..
Keine Ahnung, was ich falsch mache...
Beste Grüße
Jürgen K.
User und Passwort nutzt du von der SmartLife App und nicht das von der tuya iot Plattform? Hast du bereits die SmartLife App auf der tuya Plattform verlinkt und ein Device in SmartLife hinterlegt?
Hallo,
Habe die Tuya App. Die habe ich verlinkt. User und Passwort aus der Tuya App.
Danke für die Hilfe!
Gruß
Jürgen
Ah, da musst du als Parameter APPTYPE bei der Definition "tuyaSmart" verwenden, dann sollte es klappen.
define tuya_cloud PythonModule tuya_cloud setup API_KEY API_SECRET USERNAME PASSWORD tuyaSmart
Nutzt du Europe als Region? Wenn nicht, muss nach tuyaSmart noch die Region stehen. Z.B. China.
Sorry, keine Verbindung.. failed to connect.
nochmal zum Verständnis:
API_KEY=Access ID/Client ID
API_SECRET=Access Secret/Client Secret
vielleicht mache ich dort den Fehler.
Das ist korrekt.
Beim iot Projekt hast du Smart Home als "Industry" und "Development Method" ausgewählt? Europe ebenfalls?
Prüfe bitte auch noch welche Region du in der Tuya App ausgewählt hast. Unter Konto und Sicherheit sollte bei Kontostandort ein europäisches Land stehen.
So sieht das bei mir aus:
Hallo Dominik,
es will nicht. Habe alle Einstellungen nochmal getestet..
Gruß
Jürgen
Probier mal bei Region: WesternEurope
mit Western Europe sehe ich in TUYA IOT Platform meine Geräte nicht. Mit Europe schon.
Ok, dann stimmt Europe.
Bei "Service API" hast du auch die gleichen Services wie ich im Screenshot?
kann auch in der Tuya platform meine Geräte schalten..
screenshot..
und sorry für den Stress..gibt Kaffee..
Ich glaub ich habe den Fehler gefunden, gib bitte trotzdem mal "Europe" als letzten Parameter an. Da ist ein Fehler im Code der alle Parameter erwartet. Ich habe gerade einen tuyaApp Account angelegt und es bei mir mit einem Devices erfolgreich getestet :)
sorry...kein Erfolg
Internals:
DEF tuya_cloud setup aaaaaaaaaaaaaaaaaaaa bbbbbbbbbbbbbbbbbbbbbb ccccccc@freenet.de dddddddddddddddd APPTYPE=tuyaSmart REGION=Europe
FUUID 6107b477-f33f-3968-36b2-a3d91eac5a1ef733
IODev local_pybinding
NAME tuya_cloud_connector
NR 17
PYTHONTYPE tuya_cloud
STATE failed to connect
TYPE PythonModule
READINGS:
2021-08-02 18:49:58 state failed to connect
args:
tuya_cloud_connector
PythonModule
tuya_cloud
setup
aaaaaaaaaa
bbbbbbbbbbbbbbbb
ccccccc@freenet.de
passwort
argsh:
APPTYPE tuyaSmart
REGION Europe
Attributes:
room tuya
Bitte noch deine Daten rauslöschen damit sich sonst niemand anmelden kann!!
//Edit:
APPTYPE und REGION dürfen nicht mit = angegeben werden.
Du musst nur nach der Angabe des Passwort
tuyaSmart Europe
angeben. Ohne APPTYPE=/REGION=
HA, nach Änderung und Fhem reboot: CONNECTED. Devices sind sichtbar..
VIELEN DANK..Kaffee ist unterwegs... ;-)
Zitat von: juergen012 am 02 August 2021, 20:07:17
HA, nach Änderung und Fhem reboot: CONNECTED. Devices sind sichtbar..
VIELEN DANK..Kaffee ist unterwegs... ;-)
Super!! Achtung, Kennwort ist oben noch ersichtlich. Bitte löschen!!
Danke für den Kaffee :)
GERNE!!
So habe ich mir das vorgestellt. Statusänderungen kommen sofort. SUPER!!
Zitat von: dominik am 31 Juli 2021, 20:20:35
Aha, da fehlen scheinbar noch die Infos aus der Tuya Cloud.
Wäre es ok, wenn du mir per PN die Daten zum Testen schickst? So kommen wir wahrscheinlich am schnellsten weiter.
//Edit: Oder du kannst mir das Device in der SmartLife App teilen, habe ich zwar noch nicht probiert, aber müsste auch klappen.
Kurzes Update zur Integration des Parkside Bewässerungscomputer. Dominik war hier super aktiv und konnte durch Kontakt mit tuya, den LIDL Parkside Bewässerungscomputer in FHEM integrieren.
Habe bei den Tests und mit Logs unterstützt und ein List des Devices sieht derzeit so aus:
Internals:
DEF tuya_cloud tuya_cloud_connector xxx
DEVICEID xxx
FUUID 61055fcd-f33f-6bbc-f1d4-8834b43445578c63
IODev local_pybinding
NAME Wassercomputer_xxx
NR 27
PYTHONTYPE tuya_cloud
STATE off
TYPE PythonModule
READINGS:
2021-08-03 20:09:33 active_time 1627740172
2021-08-03 20:31:42 battery_percentage 90.0
2021-08-03 20:09:33 biz_type 18
2021-08-03 20:09:33 category ggq
2021-08-03 20:31:42 countdown 120.0
2021-08-03 20:31:42 countdown_left 0.0
2021-08-03 20:09:33 create_time 1625394106
2021-08-03 20:09:33 icon https://images.tuyaeu.com/smart/icon/ay1559701439060fw6BY/252620ee7b379e21c75db0d36b0aa39d.png
2021-08-03 20:09:33 id xxx
2021-08-03 20:09:33 ip
2021-08-03 20:09:33 lat 49.97126134078343
2021-08-03 20:09:33 local_key 40290c9452839c78
2021-08-03 20:09:33 lon 8.788135160961128
2021-08-03 20:09:33 name Wassercomputer
2021-08-03 20:09:33 node_id 847127fffe1aa341
2021-08-03 20:09:33 online on
2021-08-03 20:09:33 owner_id 34453065
2021-08-03 20:09:33 product_id htnnfasr
2021-08-03 20:09:33 product_name Water Computer
2021-08-03 20:31:42 state off
2021-08-03 20:09:33 sub on
2021-08-03 20:09:33 time_zone +02:00
2021-08-03 20:09:33 uid eu1626898692773kgd2p
2021-08-03 20:09:33 update_time 1627740193
2021-08-03 20:09:33 uuid 847127fffe1aa341
args:
Wassercomputer_xxx
PythonModule
tuya_cloud
tuya_cloud_connector
xxx
argsh:
Attributes:
alias Wassercomputer
room tuya
Der Timer (Countdown), wie lange die Bewässerung dauern soll, kann jetzt per Slider eingestellt werden. Nach jedem an- oder ausschalten, wird der neu eingestellte Countdown im Device eingestellt und auch dort gespeichert bis er wieder geändert wird!
Nochmals vielen Dank an der Stelle an Dominik! Super Support!
Hi,
danke auch für die Rückmeldungen hier im Forum dazu. Wirklich cool, dass tuya das Device innerhalb von 2 Tagen via API verfügbar machen konnte.
Falls also jemand die Meldung unsupported im state erhält, dann könnt ihr mir einfach eine PN mit productid und category schicken, dann erstelle ich bei tuya ein Ticket dazu.
Super das das mit dem LIDL Produkt auch klappt. Vllt besorge ich mir die auch.
mega danke,
hab meinen raspi nun auf buster aktualisiert und ich bekomme meinen entfeuchter zun laufen.
mir fällt auf, dass die status informationen nicht aktualisiert werden, muss da ein polling konfiguriert werden?
ich kann sonst nicht reagieren z.b. wenn raumfeuchtigkeit >= x dann schalte an usw.
ich sehe im log:
[2021-08-05 07:46:55,891] [tuya-openmq] error while get mqtt config
2021-08-05 07:46:55,891 - ERROR - tuya iot: error while get mqtt config
Exception in thread Thread-2:
Traceback (most recent call last):
File "/usr/lib/python3.7/threading.py", line 917, in _bootstrap_inner
self.run()
File "/opt/fhem/.local/lib/python3.7/site-packages/tuya_iot/openmq.py", line 173, in run
time.sleep(self.mq_config.expireTime - 60)
AttributeError: 'TuyaOpenMQ' object has no attribute 'mq_config'
kann man da was machen?
Nachtrag: der Fehler ist weg, nachdem ich in der Tuya IO Plattform noch das Device status notification API aktiviert habe.
Leider aktualisieren sich die Readings nicht.
Neustart von fhempy hat auch keine Änderung gebracht? Die Readings sollten eigentlich innerhalb einer Sekunden aktualisiert werden nach dem Schalten.
leider nein,
2021-08-05 11:24:49,146 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-08-05 11:24:49,173 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-08-05 11:25:24,754 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-08-05 11:25:24,816 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-08-05 11:25:32,046 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
[2021-08-05 11:25:41,067] [tuya-openmq] error while get mqtt config
2021-08-05 11:25:41,067 - ERROR - tuya iot: error while get mqtt config
2021-08-05 11:36:27,246 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-08-05 11:36:27,300 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-08-05 11:36:37,937 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-08-05 11:39:19,035 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-08-05 11:39:19,097 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-08-05 11:39:26,941 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-08-05 11:39:27,048 - WARNING - asyncio: Executing <Handle <TaskWakeupMethWrapper object at 0x75adc770>(<Future finis...events.py:396>) created at /usr/lib/python3.7/asyncio/streams.py:408> took 0.121 seconds
Exception in thread Thread-2:
Traceback (most recent call last):
File "/usr/lib/python3.7/threading.py", line 917, in _bootstrap_inner
self.run()
File "/opt/fhem/.local/lib/python3.7/site-packages/tuya_iot/openmq.py", line 170, in run
self.__run_mqtt()
File "/opt/fhem/.local/lib/python3.7/site-packages/tuya_iot/openmq.py", line 184, in __run_mqtt
mqttc = self._start(mq_config)
File "/opt/fhem/.local/lib/python3.7/site-packages/tuya_iot/openmq.py", line 204, in _start
mqttc.connect(url.hostname, url.port)
File "/opt/fhem/.local/lib/python3.7/site-packages/paho/mqtt/client.py", line 941, in connect
return self.reconnect()
File "/opt/fhem/.local/lib/python3.7/site-packages/paho/mqtt/client.py", line 1075, in reconnect
sock = self._create_socket_connection()
File "/opt/fhem/.local/lib/python3.7/site-packages/paho/mqtt/client.py", line 3546, in _create_socket_connection
return socket.create_connection(addr, source_address=source, timeout=self._keepalive)
File "/usr/lib/python3.7/socket.py", line 727, in create_connection
raise err
File "/usr/lib/python3.7/socket.py", line 716, in create_connection
sock.connect(sa)
socket.timeout: timed out
Aha, er kann keine MQTT Connection zu tuya aufbauen. Hast du irgendeine Firewall oder so aktiv?
tatsache, danke für den Hinweis.
Port 8883 muss nach extern erlaubt sein.
Prima, danke nochmal
Ich würde gerne fhempy vom fhem raspberry wegbekommen.
Ich hatte ja versucht auf einer Ubuntu 20.04 Maschine fhempy mit pyhton3.8 zu implementieren.
Sobald fhem versucht zu verbinden knallts:
2021-08-06 08:57:02,897 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 10.10.20.109
2021-08-06 08:57:02,899 - ERROR - websockets.server: Error in connection handler
Traceback (most recent call last):
File "/home/bitnami/.local/lib/python3.8/site-packages/websockets/legacy/server.py", line 293, in handler
await self.ws_handler(self, path)
File "/home/bitnami/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 64, in pybinding
await activate_internal_modules()
File "/home/bitnami/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 47, in activate_internal_modules
await instance.activate()
File "/home/bitnami/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 82, in activate
await self.runZeroconfScan()
File "/home/bitnami/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 79, in runZeroconfScan
self.browser = ServiceBrowser(self.zeroconf, services, listener)
File "/home/bitnami/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 505, in __init__
raise RuntimeError("The event loop is not running")
RuntimeError: The event loop is not running
Startest du fhempy per Commandline? Mach mal
fhempy --local
Dann startet es kein Zeroconf.
Mach bitte mal
pip3 install zeroconf==0.28.6
Ich glaub mit 0.32.0 sind da ein paar Breaking Changes reingekommen.
Hallo ich habe immer wieder das Problem,
dass auf meinem Raspi keine MQTT Informationen mehr kommen.
Im fhempy Log erscheint dann:
2021-08-08 12:42:41,823 - ERROR - tuya_cloud_connector: 'TuyaDeviceManager' object has no attribute '_on_message'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 71, in restart_mqtt_loop
await self.restart_mqtt()
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 81, in restart_mqtt
tuya_mq.add_message_listener(self.device_manager._on_message)
AttributeError: 'TuyaDeviceManager' object has no attribute '_on_message'
2021-08-08 14:41:01,847 - ERROR - tuya_cloud_connector: 'TuyaDeviceManager' object has no attribute '_on_message'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 71, in restart_mqtt_loop
await self.restart_mqtt()
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 81, in restart_mqtt
tuya_mq.add_message_listener(self.device_manager._on_message)
AttributeError: 'TuyaDeviceManager' object has no attribute '_on_message'
2021-08-08 16:39:21,960 - ERROR - tuya_cloud_connector: 'TuyaDeviceManager' object has no attribute '_on_message'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 71, in restart_mqtt_loop
await self.restart_mqtt()
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 81, in restart_mqtt
tuya_mq.add_message_listener(self.device_manager._on_message)
AttributeError: 'TuyaDeviceManager' object has no attribute '_on_message'
Restarte ich das Pythonbinding, geht es wieder für einen Weile.
Ne Idee?
Ah, da ist was bei der Tuya iot Library geändert worden. Korrigiere ich heute Abend bzw. fixiere ich dann gleich die Library Version.
//Edit
Bitte mal ein Update machen, in 0.1.82 wird nun die "alte" Tuya Library verwendet, dann klappt es wieder.
hat geklappt danke
Hallo,
leider muss ich mich nochmal melden, da ich alleine nicht weiterkomme. Eigentlich funktioniert alles wie es soll.. Bis auf meinen smart_power_strip. Dieser hat 4 Steckdosen, die alle separat geschaltet werden können. Zusätzlich noch 4 USB Ports, die gemeinsam geschaltet werden. Bis auf die Steckdose 1 (switch1) kann ich alles schalten. Der Switch wird mir in fhem nicht angezeigt. In der App funktioniert das.
Hier das List..
DEF tuya_cloud tuya_cloud_connector yyyyy
DEVICEID aaaaaaaa
FUUID xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
IODev local_pybinding
NAME smart_power_strip_xxxxxx
NR 297
PYTHONTYPE tuya_cloud
STATE off
TYPE PythonModule
READINGS:
2021-08-11 14:10:17 active_time 1626194558
2021-08-11 14:10:17 biz_type 0
2021-08-11 14:10:17 category pc
2021-08-12 12:28:11 countdown_1 0.0
2021-08-12 12:28:11 countdown_2 0.0
2021-08-12 12:28:11 countdown_3 0.0
2021-08-12 12:28:11 countdown_4 0.0
2021-08-12 12:28:11 countdown_usb1 0.0
2021-08-11 14:10:17 create_time 1620742633
2021-08-11 14:10:17 icon https://images.tuyaeu.com/smart/icon/1555585425a1oqvs7elur_0.jpg
2021-08-11 14:10:17 id aaaaa
2021-08-11 14:10:17 ip 11111
2021-08-11 14:10:17 lat 53.685hhh
2021-08-11 14:10:17 local_key 7xxxxx
2021-08-11 14:10:17 lon 10.029nnn
2021-08-11 14:10:17 model A339
2021-08-11 14:10:17 name smart power strip
2021-08-11 14:10:17 online on
2021-08-11 14:10:17 owner_id xxxxxxxxxxxxx
2021-08-11 14:10:17 product_id gl5fdiv1tc9mkvlp
2021-08-11 14:10:17 product_name smart power strip
2021-08-12 12:28:11 state off
2021-08-11 14:10:17 sub off
2021-08-12 12:28:11 switch_2 off
2021-08-12 12:28:11 switch_3 off
2021-08-12 12:28:11 switch_4 off
2021-08-12 12:28:11 switch_usb1 off
2021-08-11 14:10:17 time_zone +01:00
2021-08-11 14:10:17 uid eu1598540337292fORIB
2021-08-11 14:10:17 update_time 1628669008
2021-08-11 14:10:17 uuid xxxxxxxxxxxxxxxxxxx
args:
smart_power_strip_xxxxxxx
PythonModule
tuya_cloud
tuya_cloud_connector
xxxxxxxxxxxxxxxxxxxxx
argsh:
Attributes:
DbLogExclude .*
alias smart power strip
room tuya
verbose 2
Wenn ich am smart_power_strip die Steckdose 1 schalte, dann wird mir das in fhem angezeigt..
Beste Grüße
Jürgen K.
Hi,
schalte Mal direkt das Device On/Off
set smart_power_strip_xxxxxx on
Damit sollte es funktionieren.
Hallo dominik,
wenn ich set smart_power_strip_xxxxxxxxxxxxxxxxxxx switch_1 on mache, bekomme ich: Command not available for this device.
Mit den andere Steckdosen (2-4) funktioniert das.
Ohne switch_1, nur das Command von oben.
mit dem Kommando werden alle Steckdosen geschaltet..
Ah, dann gibt es da wahrscheinlich Switch und switch_1. Ich schau mir das am Abend an und melde mich mit einem Update.
supi! kein Stress..
Edit: ja, es ist so, dass ich alle Steckdosen auf einmal schallten kann oder jede separat.
Sollte nun funktionieren: 0.1.83
switch_1 ist der Switch 1 und das allgemeine State ist für alles Ein/Ausschalten.
Danke! Kann leider zur Zeit nicht testen.. Melde mich..
Gerade getestet.. Klappt wunderbar. Vielen Dank für den tollen Support.
Beste Grüße
Jürgen K.
Super! :)
Danke dir auch für die Kaffeespende!
Hallo!
Mein smart power strip funktionier jetzt einwandfrei. Leider kann ich jetzt aber die anderen Schalter aus fhem nicht mehr schalten. Es wird der Zustand (on/off) korrekt angezeigt, wenn ich direkt am Schalter oder in der App schalte.
DEF tuya_cloud tuya_cloud_connector xxxxxxxxxxxxxxxxxxxxxx
DEVICEID xxxxxxxxxxxxxxxxxxxxxxxxxx
FUUID xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
IODev local_pybinding
NAME Licht_WC_xxxxxxxxxxxxxxxxxxxxxxxxx
NR 305
PYTHONTYPE tuya_cloud
STATE off
TYPE PythonModule
READINGS:
2021-08-14 21:21:42 active_time 1621246250
2021-08-14 21:21:42 biz_type 0
2021-08-14 21:21:42 category kg
2021-08-15 08:43:37 countdown_1 0.0
2021-08-14 21:21:42 create_time 1621245813
2021-08-14 21:21:42 icon https://images.tuyaeu.com/smart/icon/ay15532588194335cLlF/1565281088c7cf2b22734.jpg
2021-08-14 21:21:42 id xxxxxxxxxxxxxxxxxxxxxxxxxxx
2021-08-14 21:21:42 ip xxx.xxx.xxx.xxx
2021-08-14 21:21:42 lat 53.68558099580563
2021-08-14 21:21:42 local_key xxxxxxxxxxxxxxxxxxx
2021-08-14 21:21:42 lon 10.02967337135953
2021-08-14 21:21:42 model W601
2021-08-14 21:21:42 name Licht WC
2021-08-14 21:21:42 online on
2021-08-14 21:21:42 owner_id xxxxxxxxxxxxxx
2021-08-14 21:21:42 product_id pxphdeyqak8mxld4
2021-08-14 21:21:42 product_name W601
2021-08-15 08:43:37 state off
2021-08-14 21:21:42 sub off
2021-08-14 21:21:42 time_zone +01:00
2021-08-14 21:21:42 uid euxxxxxxxxxxxxxxxxx
2021-08-14 21:21:42 update_time 1628968172
2021-08-14 21:21:42 uuid xxxxxxxxxxxxxxxxxxx
args:
Licht_WC_xxxxxxxxxxxxxxxxxxx
PythonModule
tuya_cloud
tuya_cloud_connector
xxxxxxxxxxxxxxxxxxxxxx
argsh:
Attributes:
DbLogExclude .*
alias Licht WC
devStateIcon on:radio_checked@red:off off:radio_unchecked:on
group Schalter
room Home,tuya
verbose 2
webCmd :
Ich sehe schon den Fehler. Wird am Abend gefixed! :)
AHHHHH! SUPER!
Bitte mit 0.1.84 beides testen, danke :) Hab hier leider gerade nichts zum Testen...
Sieht gut aus.Danke!
Hallo,
eben habe ich readingsProxy für die einzelnen Switche des Power Stripes eingerichtet. Dabei ist mir aufgefallen, dass für den switch_1 kein Reading generiert wird. Habe fhem und den ganzen LXC neu gestartet, ohne Erfolg.
2021-08-15 17:15:45 product_name smart power strip
2021-08-16 18:58:09 state off
2021-08-15 17:15:45 sub off
2021-08-16 18:58:09 switch_2 off
2021-08-16 18:58:09 switch_3 off
2021-08-16 18:58:09 switch_4 off
2021-08-16 18:58:09 switch_usb1 off
wäre schön, wenn das noch möglich wäre.
Beste Grüße
Jürgen K.
Yep, Fehler gefunden! :) Vielleicht schaff ich es heute noch mit der Behebung, ansonsten morgen.
0.1.86 ist online, damit müsste switch_1 wieder da sein.
Wenn noch was nicht klappt, gerne melden.
Hallo Dominik,
jetzt habe ich nichts mehr zu meckern..
Sehr gut :)
Ich glaube ich habe etwas vergessen oder überlesen/übersehen.
Meine geräte kann ich in Tyua sehen aber sie tauchen leider nicht in fhem auf. Denke ich habe da was vergessen. Ich denke ein define Gerätename und co.
Wie muss ich das schreiben.
Danke
Bitte um noch mehr Infos. Bei welchem Punkt der Anleitung traten Fehler auf? Wie ist der Status vom tuya_cloud_connector? Was steht im Log?
Anleitung: https://github.com/dominikkarall/fhempy/blob/master/FHEM/bindings/python/fhempy/lib/tuya_cloud/README.md
Hallo und danke für die Implementierung von Tuya.
Ich habe eine RGBW Led Band und kann leider die Farbe in Fhem nicht einstellen. Die Funktion fehlt noch.
Schick mir bitte den Auszug der Readings, dann kann ich das bei tuya anfragen.
ZitatSchick mir bitte den Auszug der Readings, dann kann ich das bei tuya anfragen.
READINGS:
2021-08-18 00:30:08 active_time 1628958374
2021-08-18 00:30:08 biz_type 0
2021-08-18 00:30:08 bright_value_v2 1000.0
2021-08-18 00:30:08 category dj
2021-08-18 00:30:08 colour_data_v2 {"h":60,"s":1000,"v":1000}
2021-08-18 00:30:08 control_data
2021-08-18 00:30:08 countdown_1 0.0
2021-08-18 00:30:08 create_time 1628958374
2021-08-18 00:30:08 icon https://images.tuyaeu.com/smart/icon/ay1541056239985fDGjj/37da2cc5d1ecdc83cc45fef75f2f9524.png
2021-08-18 00:30:08 id bf6699146977bb2b22unzk
2021-08-18 00:30:08 ip
2021-08-18 00:30:08 lat 51.0036614
2021-08-18 00:30:08 local_key a61c856938ef313e
2021-08-18 00:30:08 lon 13.8415266
2021-08-18 00:30:08 model 3H
2021-08-18 00:30:08 music_data
2021-08-18 00:30:08 name Pavillon
2021-08-18 00:30:08 online off
2021-08-18 00:30:08 owner_id 30271206
2021-08-18 00:30:08 product_id e3rqvdduuklcwcvl
2021-08-18 00:30:08 product_name Smart RGB Led Strip
2021-08-18 00:30:08 scene_data_v2 {"scene_num":1,"scene_units":[{"bright":200,"h":0,"s":0,"temperature":1000,"unit_change_mode":"static","unit_gradient_duration":13,"unit_switch_duration":14,"v":0}]}
2021-08-18 00:30:07 state ready
2021-08-18 00:30:08 sub off
2021-08-18 00:30:08 switch_led off
2021-08-18 00:30:08 time_zone +02:00
2021-08-18 00:30:08 uid eu16201548593270AIbt
2021-08-18 00:30:08 update_time 1629053545
2021-08-18 00:30:08 uuid 0886f7b17f4f5c77
2021-08-18 00:30:08 work_mode white
Danke :)
die installation ging eigentlich gut von der Hand. Erst wollte er Europa nicht annehmen, habe dann hier gelesen das ich mal auf Westeuropa umstellen sollte. Dieses konnte ich aber unter meiner App software leider nicht einstellen. Habe es dann nochmal mit europa ausprobiert und er hat sich verbunden.
Internals:
DEF tuya_cloud setup mk8xxxxxxxnuu6znv 9f6688f13d27480cbdf7axxxxxxxx stef@gmx.net Wak33 smartlife Europa
FUUID 611bfefa-f33f-5e7b-xxxxxxxxxxxxx
IODev local_pybinding
NAME tuya_cloud_connector
NR 161
PYTHONTYPE tuya_cloud
STATE connecting
TYPE PythonModule
READINGS:
2021-08-17 21:13:43 state connecting
args:
tuya_cloud_connector
PythonModule
tuya_cloud
setup
mk8mcxxxxxxxxddmnuu6znv
9fxxx8f13d27480xxxf7a83fxxxxx60e
stef@gmx.net
Was33
smartlife
Europa
argsh:
Attributes:
room System
verbose 5
2021.08.17 21:11:42 3: Pythonbinding_15733: read: end of file reached while sysread
2021.08.17 21:11:42 3: Pythonbinding_15733: stopped
2021.08.17 21:11:42 3: Pythonbinding_15733: starting
2021.08.17 21:11:42 3: Pythonbinding_15733: using logfile: ./log/fhempy-2021-08-17.log
2021.08.17 21:11:42 1: ws:127.0.0.1:15733 disconnected, waiting to reappear (local_pybinding)
2021.08.17 21:11:42 1: BindingsIo: ERROR local_pybinding - error while connecting: 127.0.0.1: Verbindungsaufbau abgelehnt (111)
2021.08.17 21:12:33 3: eval: Ole_LuefterDOIF: warning in condition c02
2021.08.17 21:12:35 1: ws:127.0.0.1:15733 disconnected, waiting to reappear (local_pybinding)
2021.08.17 21:12:35 3: Pythonbinding_15733: read: end of file reached while sysread
2021.08.17 21:12:35 3: Pythonbinding_15733: stopped
2021.08.17 21:12:35 1: BindingsIo: ERROR local_pybinding - error while connecting: 127.0.0.1: Verbindungsaufbau abgelehnt (111)
2021.08.17 21:13:30 3: Pythonbinding_15733: read: end of file reached while sysread
2021.08.17 21:13:30 3: Pythonbinding_15733: stopped
2021.08.17 21:13:30 3: Pythonbinding_15733: starting
2021.08.17 21:13:30 3: Pythonbinding_15733: using logfile: ./log/fhempy-2021-08-17.log
2021.08.17 21:13:30 1: BindingsIo: ERROR local_pybinding - error while connecting: 127.0.0.1: Verbindungsaufbau abgelehnt (111)
Das ist der letzte eintrag in meinen Fhem Log
2021.08.17 21:13:41 1: ws:127.0.0.1:15733 reappeared (local_pybinding)
irgendwie wurden ja wohl meine verbindungsaufbauten abgebrochen
Hallo, wollte das Fhempy:Tuya ausprobieren.
Leider bekomme ich bei der Ausführung von
define local_pybinding BindingsIo Python
immer nur
Unknown module BindingsIo
zurückgegeben.
Bin nicht so versiert mit dem ganzen , deshalb hab ich keinen Anhaltspunkt wo ich nach dem Fehler suchen muss.
Muss ich ein Modul manuell nachinstallieren, oder was sagt mir die Meldung genau?
Zitat von: MarkoP am 19 August 2021, 23:19:11
Hallo, wollte das Fhempy:Tuya ausprobieren.
Leider bekomme ich bei der Ausführung von
define local_pybinding BindingsIo Python
immer nur
Unknown module BindingsIo
zurückgegeben.
Bin nicht so versiert mit dem ganzen , deshalb hab ich keinen Anhaltspunkt wo ich nach dem Fehler suchen muss.
Muss ich ein Modul manuell nachinstallieren, oder was sagt mir die Meldung genau?
Mach mal ein "shutdown restart" hilft das nicht, den Server neu Starten. Hatte selbe Problem, obwohl Modul vorhanden.
Ok, Neustart hat einen Erfolg gebracht, Device konnte jetzt erstellt werden.
leider zeigt das local_pythonbinding-device nur "PythonBinding offline" an.
Hier das List dazu:
Internals:
BindingType Python
CFGFN
DEF Python
DeviceName ws:127.0.0.1:15733
FUUID 611ecfe9-f33f-6c14-a867-683466feea4ee551
IP 127.0.0.1
NAME local_pybinding
NEXT_OPEN 1629409270.59507
NR 88
NTFY_ORDER 50-local_pybinding
PARTIAL
PORT 15733
STATE PythonBinding offline
TYPE BindingsIo
localBinding 1
nextOpenDelay 10
.attraggr:
.attrminint:
READINGS:
2021-08-19 23:41:05 state PythonBinding offline
args:
local_pybinding
BindingsIo
Python
argsh:
Attributes:
room fhempy
Hier noch das Log:
2021-08-19 23:40:57,643 - INFO - __main__: Attempting install of fhempy>=0.1.12
2021-08-19 23:41:04,467 - INFO - __main__: Successfully installed fhempy>=0.1.12
2021-08-19 23:41:04,468 - ERROR - __main__: Failed to import fhempy, exit now...
2021-08-19 23:42:04,907 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-08-19 23:42:04,931 - INFO - fhempy.lib.pkg_installer: Attempting install of zeroconf==0.28.6
2021-08-19 23:42:06,865 - INFO - fhempy.lib.pkg_installer: Successfully installed fhempy update!
2021-08-19 23:42:06,866 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
So, das Device ist jetzt "opened" und das PythonBinding-Device "active".
Wollte also jetzt Tuya einrichten, doch schon wieder das nächste Problem.
Ich kann mich nicht auf der Website der Tuya IoT-Plattform anmelden.
Benutzername und Passwort stimmen, mehrfach geprüft und auch schon neu eingerichtet aus der SmartLife-App auf dem Handy, trotzdem kommt immer die Meldung das Benutzer oder Passwort falsch sind.
Kann mir jemand helfen? gibt es da einen Trick?
So, alles geschafft. Sehr kompliziert, aber passt schon.
Allerdings fehlen mir noch Einstellungen bei meinen Geräten wie dem Djive ARC Humilidator und dem Smart Aroma Diffuser.
Kann es sein, dass diese noch später aus der Cloud hinzugefügt werden oder ist das Fhempy:Tuya Cloud erst mal nur rudimentär mit den Grundbefehlen ausgestattet?
Zitat von: MarkoP am 20 August 2021, 16:40:45
So, alles geschafft. Sehr kompliziert, aber passt schon.
Allerdings fehlen mir noch Einstellungen bei meinen Geräten wie dem Djive ARC Humilidator und dem Smart Aroma Diffuser.
Kann es sein, dass diese noch später aus der Cloud hinzugefügt werden oder ist das Fhempy:Tuya Cloud erst mal nur rudimentär mit den Grundbefehlen ausgestattet?
Hi,
war die letzten Tage unterwegs und daher erst jetzt die Rückmeldung.
Kannst du mir mitteilen welche Punkte im README unklar waren und zu Fehlern geführt haben? Ich möchte vermeiden, dass sich neue User schwer tun.
Welche Funktionen nutzbar sind, liegt nur an Tuya selbst. Vom Modul wird wirklich alles unterstützt was Tuya zur Verfügung stellt. Welche Funktionen fehlen dir bei den beiden Geräten? Wenn du die gewünschten Funktionen beschreibst und die productid postest, kann ich das mal anfragen.
Zitat von: barneybaer am 18 August 2021, 19:05:02
READINGS:
2021-08-18 00:30:08 active_time 1628958374
2021-08-18 00:30:08 biz_type 0
2021-08-18 00:30:08 bright_value_v2 1000.0
2021-08-18 00:30:08 category dj
2021-08-18 00:30:08 colour_data_v2 {"h":60,"s":1000,"v":1000}
2021-08-18 00:30:08 control_data
2021-08-18 00:30:08 countdown_1 0.0
2021-08-18 00:30:08 create_time 1628958374
2021-08-18 00:30:08 icon https://images.tuyaeu.com/smart/icon/ay1541056239985fDGjj/37da2cc5d1ecdc83cc45fef75f2f9524.png
2021-08-18 00:30:08 id bf6699146977bb2b22unzk
2021-08-18 00:30:08 ip
2021-08-18 00:30:08 lat 51.0036614
2021-08-18 00:30:08 local_key a61c856938ef313e
2021-08-18 00:30:08 lon 13.8415266
2021-08-18 00:30:08 model 3H
2021-08-18 00:30:08 music_data
2021-08-18 00:30:08 name Pavillon
2021-08-18 00:30:08 online off
2021-08-18 00:30:08 owner_id 30271206
2021-08-18 00:30:08 product_id e3rqvdduuklcwcvl
2021-08-18 00:30:08 product_name Smart RGB Led Strip
2021-08-18 00:30:08 scene_data_v2 {"scene_num":1,"scene_units":[{"bright":200,"h":0,"s":0,"temperature":1000,"unit_change_mode":"static","unit_gradient_duration":13,"unit_switch_duration":14,"v":0}]}
2021-08-18 00:30:07 state ready
2021-08-18 00:30:08 sub off
2021-08-18 00:30:08 switch_led off
2021-08-18 00:30:08 time_zone +02:00
2021-08-18 00:30:08 uid eu16201548593270AIbt
2021-08-18 00:30:08 update_time 1629053545
2021-08-18 00:30:08 uuid 0886f7b17f4f5c77
2021-08-18 00:30:08 work_mode white
Danke :)
Ticket erstellt. Kannst du mir sagen welche set Befehlen zur Verfügung stehen?
Zitat von: Wasserwerk33 am 18 August 2021, 20:54:33
die installation ging eigentlich gut von der Hand. Erst wollte er Europa nicht annehmen, habe dann hier gelesen das ich mal auf Westeuropa umstellen sollte. Dieses konnte ich aber unter meiner App software leider nicht einstellen. Habe es dann nochmal mit europa ausprobiert und er hat sich verbunden.
Internals:
DEF tuya_cloud setup mk8xxxxxxxnuu6znv 9f6688f13d27480cbdf7axxxxxxxx stef@gmx.net Wak33 smartlife Europa
FUUID 611bfefa-f33f-5e7b-xxxxxxxxxxxxx
IODev local_pybinding
NAME tuya_cloud_connector
NR 161
PYTHONTYPE tuya_cloud
STATE connecting
TYPE PythonModule
READINGS:
2021-08-17 21:13:43 state connecting
args:
tuya_cloud_connector
PythonModule
tuya_cloud
setup
mk8mcxxxxxxxxddmnuu6znv
9fxxx8f13d27480xxxf7a83fxxxxx60e
stef@gmx.net
Was33
smartlife
Europa
argsh:
Attributes:
room System
verbose 5
2021.08.17 21:11:42 3: Pythonbinding_15733: read: end of file reached while sysread
2021.08.17 21:11:42 3: Pythonbinding_15733: stopped
2021.08.17 21:11:42 3: Pythonbinding_15733: starting
2021.08.17 21:11:42 3: Pythonbinding_15733: using logfile: ./log/fhempy-2021-08-17.log
2021.08.17 21:11:42 1: ws:127.0.0.1:15733 disconnected, waiting to reappear (local_pybinding)
2021.08.17 21:11:42 1: BindingsIo: ERROR local_pybinding - error while connecting: 127.0.0.1: Verbindungsaufbau abgelehnt (111)
2021.08.17 21:12:33 3: eval: Ole_LuefterDOIF: warning in condition c02
2021.08.17 21:12:35 1: ws:127.0.0.1:15733 disconnected, waiting to reappear (local_pybinding)
2021.08.17 21:12:35 3: Pythonbinding_15733: read: end of file reached while sysread
2021.08.17 21:12:35 3: Pythonbinding_15733: stopped
2021.08.17 21:12:35 1: BindingsIo: ERROR local_pybinding - error while connecting: 127.0.0.1: Verbindungsaufbau abgelehnt (111)
2021.08.17 21:13:30 3: Pythonbinding_15733: read: end of file reached while sysread
2021.08.17 21:13:30 3: Pythonbinding_15733: stopped
2021.08.17 21:13:30 3: Pythonbinding_15733: starting
2021.08.17 21:13:30 3: Pythonbinding_15733: using logfile: ./log/fhempy-2021-08-17.log
2021.08.17 21:13:30 1: BindingsIo: ERROR local_pybinding - error while connecting: 127.0.0.1: Verbindungsaufbau abgelehnt (111)
Das ist der letzte eintrag in meinen Fhem Log
2021.08.17 21:13:41 1: ws:127.0.0.1:15733 reappeared (local_pybinding)
irgendwie wurden ja wohl meine verbindungsaufbauten abgebrochen
Die Fehlermeldungen kommen durch den Restart von fhempy.
Ich glaub ich sehe den Fehler schon, du hast Europa statt Europe geschrieben.
Zitat von: dominik am 22 August 2021, 19:44:41
Ticket erstellt. Kannst du mir sagen welche set Befehlen zur Verfügung stehen?
Danke :)
Hier die Befehle:
set bright_value_v2 10 -1000
set countdown_1 0 - 86400
set switch_led on - off
set temp_value_v2 0 - 1000
set work_mode white, colour, scene, music (da müsste jetzt noch ein Feld für die Farbe usw. kommen)
Desweiteren wird mein Bewässerungscomputer nicht angezeigt.
Welcher Bewässerungscomputer ist es?
Poste bitte die Readings, der Parkside vom Lidl wurde von Tuya in 2 Tagen nach Ticketeröffnung integriert.
Zitat von: dominik am 22 August 2021, 21:31:44
Welcher Bewässerungscomputer ist es?
Poste bitte die Readings, der Parkside vom Lidl wurde von Tuya in 2 Tagen nach Ticketeröffnung integriert.
Ja der von Lidl.
In tuya iot steht er drin, aber bei Fhem taucht der nicht auf, nur das ZigBee Gateway.
Zitat von: barneybaer am 22 August 2021, 22:07:27
Ja der von Lidl.
In tuya iot steht er drin, aber bei Fhem taucht der nicht auf, nur das ZigBee Gateway.
Starte bitte mal fhempy neu. Den hatte ich erst unlängst integriert, der sollte eigentlich funktionieren.
Zitat von: dominik am 22 August 2021, 22:13:27
Starte bitte mal fhempy neu. Den hatte ich erst unlängst integriert, der sollte eigentlich funktionieren.
Habe bereits alles neu gestartet, ohne Erfolg. Habe im Nachhinein noch ein LED Band eingebunden, welches sofort in Fhem angelegt wurde. Vielleicht trennen ich den den Bewässerungscomputer noch einmal.
Also für mich war es beispielsweise nicht eindeutig klar womit man sich auf der Tuya IoT Plattform anmelden muss. So wie der Text formuliert ist (bezug auf das vorhanden sein eines Accounts) deutet es darauf hin, dass man sich mit den vorhandenen Kontodaten anmelden muss. Erst als ich dann die kleine grüne Infoanzeige gelesen habe, wurde klar, dass man dort neue Anmeldedaten braucht,
Zum Anderen wird nirgendwo in der Beschreibung erwähnt, dass man einen (kostenlosen) Vertrag abschließen muss, es fehlen mindesten 2 komplette Screens in der Abfolge um zum Anlegen eines neuen Projektes zu gelangen. Schwer das im Nachhinein noch mal voll zu kriegen. Vielleicht am besten den kompletten Anmeldeprozess noch mal selbst absolvieren, da wurde wahrscheinlich nachträglich was hinzugefügt.
Für den Djive ARC Ventilator fehlen alle Einstellungsmöglichkeiten für die Modi (Schlafend, Fresh und Max) sowie alle Einstellungen für den Luftbefeuchter (Stufen 1-3, Auto und Aus in der SmartLife-App im Ventilator mit ansteuerbar). Außerdem kann man in der App die UV-Desinfektion ein-/ausschalten und einen Sleeptimer für 1-9 Stunden einstellen.
Für den Luftbefeuchter fehlen alle Einstellungen für das Licht (festes Licht, Umlaufend gradiant, aus und die Einstellung der Verdunstungsstufe (Weak-Modus, Strong-Modus). Den Befeuchter kann man lediglich an und aus schalten.
Was die ProductID angeht, wo kann ich die finden?
Hallo Dominik,
bei mir ist eine Steckdose in FHEM eingebunden und es funktioniert auch.
Das Problem ist aber, nach jedem shutdown wird die Steckdose nur als online angezeigt
und ein schalten ist nicht möglich. Erst eine Neuanlage kann das Problem wieder lösen.
Anbei die RAW Def.
Was könnte man machen, dass die Wideranlage nicht mehr notwendig ist.
Beste Grüße
defmod Smart_Plug_bfc0100ce21d5d7715kbjp PythonModule tuya qexu7r2qg0i3bm9g xxxxxxxxxx xxx.xxx.xxx.xx xxxxxxxxxxxxxxxx 3.3 xxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
attr Smart_Plug_bfc0100ce21d5d7715kbjp cmdIcon on:rc_GREEN off:rc_RED
attr Smart_Plug_bfc0100ce21d5d7715kbjp devStateIcon OK:rc_YELLOW on:black_Steckdose.on off:black_Steckdose.off 1:black_Steckdose.on 0:black_Steckdose.off 0:black_Steckdose.off 0:black_Steckdose.off 0:black_Steckdose.off
attr Smart_Plug_bfc0100ce21d5d7715kbjp dp_01 switch_1
attr Smart_Plug_bfc0100ce21d5d7715kbjp dp_20 cur_voltage
attr Smart_Plug_bfc0100ce21d5d7715kbjp dp_38 relay_status
attr Smart_Plug_bfc0100ce21d5d7715kbjp icon ge_wht_steckdose
attr Smart_Plug_bfc0100ce21d5d7715kbjp room 01_0_OG->01_6_OG_Schlafzimmer,Tuya
attr Smart_Plug_bfc0100ce21d5d7715kbjp tuya_spec_functions [{'code': 'switch_1', 'type': 'Boolean', 'values': '{}', 'desc': 'switch 1'}, {'code': 'countdown_1', 'type': 'Integer', 'values': '{"unit":"s","min":0,"max":86400,"scale":0,"step":1}', 'desc': 'countdown 1'}, {'code': 'relay_status', 'type': 'Enum', 'values': '{"range":["power_off","power_on","last"]}', 'desc': 'relay status'}]
attr Smart_Plug_bfc0100ce21d5d7715kbjp tuya_spec_status [{'code': 'switch_1', 'type': 'Boolean', 'values': '{}'}, {'code': 'countdown_1', 'type': 'Integer', 'values': '{"unit":"s","min":0,"max":86400,"scale":0,"step":1}'}, {'code': 'add_ele', 'type': 'Integer', 'values': '{"unit":"kW·h","min":0,"max":50000,"scale":3,"step":100}'}, {'code': 'cur_current', 'type': 'Integer', 'values': '{"unit":"mA","min":0,"max":30000,"scale":0,"step":1}'}, {'code': 'cur_power', 'type': 'Integer', 'values': '{"unit":"W","min":0,"max":80000,"scale":1,"step":1}'}, {'code': 'cur_voltage', 'type': 'Integer', 'values': '{"unit":"V","min":0,"max":5000,"scale":1,"step":1}'}, {'code': 'relay_status', 'type': 'Enum', 'values': '{"range":["power_off","power_on","last"]}'}]
attr Smart_Plug_bfc0100ce21d5d7715kbjp webCmdLabel Drücken zum Einschalten:Drücken zum Ausschalten
Zitat von: barneybaer am 22 August 2021, 21:25:32
Danke :)
Hier die Befehle:
set bright_value_v2 10 -1000
set countdown_1 0 - 86400
set switch_led on - off
set temp_value_v2 0 - 1000
set work_mode white, colour, scene, music (da müsste jetzt noch ein Feld für die Farbe usw. kommen)
Desweiteren wird mein Bewässerungscomputer nicht angezeigt.
Ich habe gerade eine neue Version released. Teste bitte die RGB Stripes mit der neue Version. Damit solltest du mit set ... colour... {"h":60,"s":1000,"v":1000} die Stripes steuern können. Eventuell machen die Anführungszeichen noch Probleme bei der Übergabe der Parameter von FHEM. Wenn ja, muss ich mir da noch was einfallen lassen.
Zitat von: MarkoP am 23 August 2021, 09:51:59
Also für mich war es beispielsweise nicht eindeutig klar womit man sich auf der Tuya IoT Plattform anmelden muss. So wie der Text formuliert ist (bezug auf das vorhanden sein eines Accounts) deutet es darauf hin, dass man sich mit den vorhandenen Kontodaten anmelden muss. Erst als ich dann die kleine grüne Infoanzeige gelesen habe, wurde klar, dass man dort neue Anmeldedaten braucht,
Zum Anderen wird nirgendwo in der Beschreibung erwähnt, dass man einen (kostenlosen) Vertrag abschließen muss, es fehlen mindesten 2 komplette Screens in der Abfolge um zum Anlegen eines neuen Projektes zu gelangen. Schwer das im Nachhinein noch mal voll zu kriegen. Vielleicht am besten den kompletten Anmeldeprozess noch mal selbst absolvieren, da wurde wahrscheinlich nachträglich was hinzugefügt.
Für den Djive ARC Ventilator fehlen alle Einstellungsmöglichkeiten für die Modi (Schlafend, Fresh und Max) sowie alle Einstellungen für den Luftbefeuchter (Stufen 1-3, Auto und Aus in der SmartLife-App im Ventilator mit ansteuerbar). Außerdem kann man in der App die UV-Desinfektion ein-/ausschalten und einen Sleeptimer für 1-9 Stunden einstellen.
Für den Luftbefeuchter fehlen alle Einstellungen für das Licht (festes Licht, Umlaufend gradiant, aus und die Einstellung der Verdunstungsstufe (Weak-Modus, Strong-Modus). Den Befeuchter kann man lediglich an und aus schalten.
Was die ProductID angeht, wo kann ich die finden?
Danke für die Rückmeldung. Ich werde das README etwas anpassen. Die Anleitung zur Anlage des Projekts werde ich jedoch nicht anpassen, da die von HomeAssistant/Tuya selbst verwaltet wird. Nachdem sich das tuya Portal immer wieder ändert, können sich da auch die Schritte von Woche zu Woche ändern.
Die ProductID findest du in den Readings. Was ich brauche:
- ProductID
- Gewünschte Funktion
je Device.
Zitat von: Sommerfeld am 23 August 2021, 15:00:33
Hallo Dominik,
bei mir ist eine Steckdose in FHEM eingebunden und es funktioniert auch.
Das Problem ist aber, nach jedem shutdown wird die Steckdose nur als online angezeigt
und ein schalten ist nicht möglich. Erst eine Neuanlage kann das Problem wieder lösen.
Anbei die RAW Def.
Was könnte man machen, dass die Wideranlage nicht mehr notwendig ist.
Beste Grüße
defmod Smart_Plug_bfc0100ce21d5d7715kbjp PythonModule tuya qexu7r2qg0i3bm9g xxxxxxxxxx xxx.xxx.xxx.xx xxxxxxxxxxxxxxxx 3.3 xxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
attr Smart_Plug_bfc0100ce21d5d7715kbjp cmdIcon on:rc_GREEN off:rc_RED
attr Smart_Plug_bfc0100ce21d5d7715kbjp devStateIcon OK:rc_YELLOW on:black_Steckdose.on off:black_Steckdose.off 1:black_Steckdose.on 0:black_Steckdose.off 0:black_Steckdose.off 0:black_Steckdose.off 0:black_Steckdose.off
attr Smart_Plug_bfc0100ce21d5d7715kbjp dp_01 switch_1
attr Smart_Plug_bfc0100ce21d5d7715kbjp dp_20 cur_voltage
attr Smart_Plug_bfc0100ce21d5d7715kbjp dp_38 relay_status
attr Smart_Plug_bfc0100ce21d5d7715kbjp icon ge_wht_steckdose
attr Smart_Plug_bfc0100ce21d5d7715kbjp room 01_0_OG->01_6_OG_Schlafzimmer,Tuya
attr Smart_Plug_bfc0100ce21d5d7715kbjp tuya_spec_functions [{'code': 'switch_1', 'type': 'Boolean', 'values': '{}', 'desc': 'switch 1'}, {'code': 'countdown_1', 'type': 'Integer', 'values': '{"unit":"s","min":0,"max":86400,"scale":0,"step":1}', 'desc': 'countdown 1'}, {'code': 'relay_status', 'type': 'Enum', 'values': '{"range":["power_off","power_on","last"]}', 'desc': 'relay status'}]
attr Smart_Plug_bfc0100ce21d5d7715kbjp tuya_spec_status [{'code': 'switch_1', 'type': 'Boolean', 'values': '{}'}, {'code': 'countdown_1', 'type': 'Integer', 'values': '{"unit":"s","min":0,"max":86400,"scale":0,"step":1}'}, {'code': 'add_ele', 'type': 'Integer', 'values': '{"unit":"kW·h","min":0,"max":50000,"scale":3,"step":100}'}, {'code': 'cur_current', 'type': 'Integer', 'values': '{"unit":"mA","min":0,"max":30000,"scale":0,"step":1}'}, {'code': 'cur_power', 'type': 'Integer', 'values': '{"unit":"W","min":0,"max":80000,"scale":1,"step":1}'}, {'code': 'cur_voltage', 'type': 'Integer', 'values': '{"unit":"V","min":0,"max":5000,"scale":1,"step":1}'}, {'code': 'relay_status', 'type': 'Enum', 'values': '{"range":["power_off","power_on","last"]}'}]
attr Smart_Plug_bfc0100ce21d5d7715kbjp webCmdLabel Drücken zum Einschalten:Drücken zum Ausschalten
Du nutzt noch die tuya Integration die nur lokal geht und keine Realtime Updates erhält. Ich würde die Empfehlen auf tuya_cloud umzustellen:
https://github.com/dominikkarall/fhempy/blob/master/FHEM/bindings/python/fhempy/lib/tuya_cloud/README.md
Zitat von: dominik am 23 August 2021, 18:42:23
Ich habe gerade eine neue Version released. Teste bitte die RGB Stripes mit der neue Version. Damit solltest du mit set ... colour... {"h":60,"s":1000,"v":1000} die Stripes steuern können. Eventuell machen die Anführungszeichen noch Probleme bei der Übergabe der Parameter von FHEM. Wenn ja, muss ich mir da noch was einfallen lassen.
Hier der Output beim set colour_data_v2 und ein colorpicker wäre nicht schlecht :)
Zitat
Failed to execute function Set: Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/fhem_pythonbinding.py", line 351, in _onMessage
fct_timeout,
File "/usr/lib/python3.7/asyncio/tasks.py", line 416, in wait_for
return fut.result()
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/generic.py", line 94, in Set
return await utils.handle_set(self._conf_set, self, hash, args, argsh)
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/utils.py", line 243, in handle_set
fct_call = getattr(obj, fct_name)
AttributeError: 'tuya_cloud' object has no attribute 'set_json'
Sollte nun gefixt sein, bitte um Update.
Colorpicker kommt dann wenn es funktioniert ;) Aktuell ist der Code für alle Funktionen komplett generisch, das bedeutet, dass alles was tuya unterstützt wird auch so in fhempy supported. Beim Colorpicker muss ich dann Ausnahmen implementieren.
Zitat von: dominik am 24 August 2021, 00:06:48
Sollte nun gefixt sein, bitte um Update.
Colorpicker kommt dann wenn es funktioniert ;) Aktuell ist der Code für alle Funktionen komplett generisch, das bedeutet, dass alles was tuya unterstützt wird auch so in fhempy supported. Beim Colorpicker muss ich dann Ausnahmen implementieren.
Jap das klappt jetzt ohne Fehler.
Als "state" hab ich leider nur "ready" egal welcher Zustand.
...und die Farbe ändert sich auch?
Nur ready steht im state? Mit welchem Command schaltest du ein und aus? Weil es sollte on/off drin stehen wenn ein Device ein und ausgeschaltet werden kann.
Zitat von: dominik am 24 August 2021, 07:36:42
...und die Farbe ändert sich auch?
Nur ready steht im state? Mit welchem Command schaltest du ein und aus? Weil es sollte on/off drin stehen wenn ein Device ein und ausgeschaltet werden kann.
Mit "set colour_data_v2 HSV" ändert sich die Farbe.
Zum Ein und Ausschalten ist der Befehl "set xxx_Name switch_led on/off" da, welcher auch als reading drin steht.
Edit: Hab grad gesehen, dass ich dir die List von einem WW LED Band gegeben habe, du die Funktionen vom RGB LED Band eingebaut hast, da ich beides habe. Scheint aber für beide zu funktionieren nur das "set colour_data_v2" halt für das WW LED Band nicht geht was ja klar ist.
Also Ventilator:
ProduktID: 6awobc9jfnlwvqtw
Funktionen: Rotation, UV-Desinfektion, Luftbefeuchter 1-3 und Auto und Aus, Modusfunktionen Schlaf/Fresh/Max, Sleep-Timer
Der Luftbefeuchter:
ProduktID: yodwo2ujgwbgjaio
Funktionen: Modus Stark/Schwach, Beleuchtung an/aus/Farbwahl und Radiant (Umlaufend)
Ich hoffe das reicht an Informationen so.
Zitat von: dominik am 22 August 2021, 19:46:17
Die Fehlermeldungen kommen durch den Restart von fhempy.
Ich glaub ich sehe den Fehler schon, du hast Europa statt Europe geschrieben.
Habe ich geändert. In Europe leider schreibt er nun failed to connected
Habe schon einen Neustart gemacht das selbe. Überprüft habe ich die Eingaben noch einmal. Ein paar Einträge vorher hat ja einer gefragt was was ist noch als kontrolliert.
fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-08-24 15:44:28,298 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-08-24 15:44:33,066 - ERROR - tuya_cloud_connector: Tuya login error response: {'code': 1106, 'msg': 'permission deny', 'success': False, 't': 1629812673043}
2021-08-24 15:45:03,211 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-08-24 15:45:03,232 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-08-24 15:45:12,615 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-08-24 15:45:15,526 - ERROR - tuya_cloud_connector: Tuya login error response: {'code': 1106, 'msg': 'permission deny', 'success': False, 't': 1629812715502}
2021-08-24 15:45:39,443 - INFO - fhempy.lib.pkg_installer: Attempting install of fhempy
2021-08-24 15:45:59,731 - INFO - fhempy.lib.pkg_installer: Successfully installed fhempy update!2021.08.24 15:45:01 1: BindingsIo: ERROR local_pybinding - error while connecting: 127.0.0.1: Verbindungsaufbau abgelehnt (111)Weist du vielleicht was genau hinter deiner Nummer 111 steht?
Danke
Beim Anlegen der Devices wurde auch ein Filelog mit angelegt.
Wenn ich dafür den Raum ändere erscheint es nach dem nächsten Neustart von Fhem trotzdem wieder im Raum fhempy.
Könntest du das eventuell korrigieren?
Zitat von: Superposchi am 24 August 2021, 12:32:22
Also Ventilator:
ProduktID: 6awobc9jfnlwvqtw
Funktionen: Rotation, UV-Desinfektion, Luftbefeuchter 1-3 und Auto und Aus, Modusfunktionen Schlaf/Fresh/Max, Sleep-Timer
Bitte um Rückmeldung welche von diesen möglichen Commands dir fehlen:
https://developer.tuya.com/en/docs/iot/f?id=K9gf45vs7vkge
Zitat
Der Luftbefeuchter:
ProduktID: yodwo2ujgwbgjaio
Funktionen: Modus Stark/Schwach, Beleuchtung an/aus/Farbwahl und Radiant (Umlaufend)
Ich hoffe das reicht an Informationen so.
"Hello, your product does not have these functions, and I cannot add them. This is defined during product design and production. You can check the device manual to view the supported functions."
Kann es sein, dass die ProductID nicht korrekt ist? Um welches Devices handelt es sich? Link Ali/Amazon?
Zitat von: Wasserwerk33 am 24 August 2021, 16:00:56
Habe ich geändert. In Europe leider schreibt er nun failed to connected
Habe schon einen Neustart gemacht das selbe. Überprüft habe ich die Eingaben noch einmal. Ein paar Einträge vorher hat ja einer gefragt was was ist noch als kontrolliert.
fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-08-24 15:44:28,298 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-08-24 15:44:33,066 - ERROR - tuya_cloud_connector: Tuya login error response: {'code': 1106, 'msg': 'permission deny', 'success': False, 't': 1629812673043}
2021-08-24 15:45:03,211 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-08-24 15:45:03,232 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-08-24 15:45:12,615 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-08-24 15:45:15,526 - ERROR - tuya_cloud_connector: Tuya login error response: {'code': 1106, 'msg': 'permission deny', 'success': False, 't': 1629812715502}
2021-08-24 15:45:39,443 - INFO - fhempy.lib.pkg_installer: Attempting install of fhempy
2021-08-24 15:45:59,731 - INFO - fhempy.lib.pkg_installer: Successfully installed fhempy update!
2021.08.24 15:45:01 1: BindingsIo: ERROR local_pybinding - error while connecting: 127.0.0.1: Verbindungsaufbau abgelehnt (111)
Weist du vielleicht was genau hinter deiner Nummer 111 steht?
Danke
2021-08-24 15:45:15,526 - ERROR - tuya_cloud_connector: Tuya login error response: {'code': 1106, 'msg': 'permission deny', 'success': False, 't': 1629812715502}
Dein Username/Passwort ist falsch oder die Client ID/Secret => Permission deny
Zitat von: Superposchi am 24 August 2021, 17:06:38
Beim Anlegen der Devices wurde auch ein Filelog mit angelegt.
Wenn ich dafür den Raum ändere erscheint es nach dem nächsten Neustart von Fhem trotzdem wieder im Raum fhempy.
Könntest du das eventuell korrigieren?
Ist beim nächsten Update behoben.
Zitat von: dominik am 24 August 2021, 17:41:10
2021-08-24 15:45:15,526 - ERROR - tuya_cloud_connector: Tuya login error response: {'code': 1106, 'msg': 'permission deny', 'success': False, 't': 1629812715502}
Dein Username/Passwort ist falsch oder die Client ID/Secret => Permission deny
Danke ich schau nochmal nach
ZitatBitte um Rückmeldung welche von diesen möglichen Commands dir fehlen:
mode, anion, humidifier, countdown, countdown_set
Wobei ich die beiden Countdown-Einträge nicht unterscheiden kann. Der Cases nach müsste es countdown_set sein.
ZitatKann es sein, dass die ProductID nicht korrekt ist? Um welches Devices handelt es sich? Link Ali/Amazon?
product_id: yodwo2ujgwbgjaio
product_name: Smart Aroma Diffuser
Hatte ich über Amazon gekauft, hier der Link dazu:
https://www.amazon.de/gp/product/B07QPR8W3F/ref=ppx_yo_dt_b_asin_image_o05_s00?ie=UTF8&psc=1Beim Durchschauen denke ich, dass die Kategori "Diffuser (xxj)" am ehesten auf das Gerät zutrifft
Commands für den Smart Fan habe ich nochmals nachgefragt.
Beim Diffuser:
- Welche Commands werden in FHEM angezegit?
- Welche Commands von hier (https://developer.tuya.com/en/docs/iot/f?id=K9gf46lj5p3q4) sollen noch unterstützt werden, da es diese aktuell noch nicht in FHEM gibt?
Zitat von: barneybaer am 24 August 2021, 08:19:57
Mit "set colour_data_v2 HSV" ändert sich die Farbe.
Zum Ein und Ausschalten ist der Befehl "set xxx_Name switch_led on/off" da, welcher auch als reading drin steht.
Edit: Hab grad gesehen, dass ich dir die List von einem WW LED Band gegeben habe, du die Funktionen vom RGB LED Band eingebaut hast, da ich beides habe. Scheint aber für beide zu funktionieren nur das "set colour_data_v2" halt für das WW LED Band nicht geht was ja klar ist.
Gibt es hierzu was Neues?
Ja, switch_led ist jetzt der state. Damit kann man über die GUI einfach ein/ausschalten. Falls sich die Frage darauf bezog?
ZitatBeim Diffuser:
- Welche Commands werden in FHEM angezegit?
- Welche Commands von hier (https://developer.tuya.com/en/docs/iot/f?id=K9gf46lj5p3q4) sollen noch unterstützt werden, da es diese aktuell noch nicht in FHEM gibt?
Lediglich on und off
mode, switch_led, work_mode müssten es sein
Wobei mode in der App lediglich "weak und strong" auswählbar hat und
work_mode bietet in der SmartLife-App lediglich "Gradiant, Fixed und Nightlight" mit einer Farbauswahl an
Zitat von: dominik am 25 August 2021, 23:01:32
Ja, switch_led ist jetzt der state. Damit kann man über die GUI einfach ein/ausschalten. Falls sich die Frage darauf bezog?
Jap das passt. Nun müsste noch der colorpicker für colour_data_v2 integriert werden.
Hallo,
seit gestern Abend, 25.08.2021, werden die Readings in Fhem bei mir nicht mehr aktualisiert.
Das Schalten über Fhem ist möglich.
Der tuya_cloud_connector ist connected.
Hat noch jemand das Problem oder hat sich in den Einstellungen etwas geändert?
Beste Grüße
@Supersoschi,
die Commands für den Fan können nicht per API freigeschalten werden. Laut tuya hat sich der Hersteller nicht an die offizielle API gehalten und daher kann das nicht genutzt werden. Du kannst noch probieren ob du mit dem tuya (local) Modul eine Ansteuerung vornehmen kannst:
https://github.com/dominikkarall/fhempy/blob/master/FHEM/bindings/python/fhempy/lib/tuya/README.md
Das ist aber nicht so gut das Modul, da keine Realtime Updates zur Verfügung stehen.
@barneybaer
colorpicker bin ich noch dran, der ist leider etwas aufwändiger.
@Sommerfeld,
auch nach einem Neustart hast du das Problem?
bei mir auch.. nach restart wieder in Ordnung..
Beste Grüße
Jürgen K.
Ist im fhempy Log etwas zu sehen? Z.B. was der letzte Event war?
Zitat von: barneybaer am 26 August 2021, 09:51:09
Jap das passt. Nun müsste noch der colorpicker für colour_data_v2 integriert werden.
Bitte mal testen ob der colorpicker funktioniert. Ich habe diesen mal eingebaut, kann ihn aber selbst nicht testen.
Hallo Dominik,
Zitat@Sommerfeld,
auch nach einem Neustart hast du das Problem?
Nach Neustart werden die Readings einmalig aktualisiert, dann nicht mehr.
Beste Grüße
Wie sieht's im Log aus? Kommt eine Fehlermeldung?
Nein, keine Fehlermeldungen
Vielleicht auch eine Firewall aktiv oder so? Poste mal ein Log mit verbose 5 vom Device. Bitte die Credentials raus löschen aus dem Log vorm Posten.
Firewall nein, bei Neustart werden die Daten immer aktualisiert.
2021-08-26_11:47:11 Steckdosenleiste_20176841c4dd571d699b off
2021-08-26_11:48:15 Steckdosenleiste_20176841c4dd571d699b on
2021-08-26_11:48:29 Steckdosenleiste_20176841c4dd571d699b off
2021-08-26_19:59:44 Steckdosenleiste_20176841c4dd571d699b on
2021-08-26_19:59:55 Steckdosenleiste_20176841c4dd571d699b off
2021-08-26_20:02:40 Steckdosenleiste_20176841c4dd571d699b ready
2021-08-26_20:02:46 Steckdosenleiste_20176841c4dd571d699b active_time: 1620129556
2021-08-26_20:02:46 Steckdosenleiste_20176841c4dd571d699b biz_type: 0
2021-08-26_20:02:46 Steckdosenleiste_20176841c4dd571d699b category: cz
2021-08-26_20:02:46 Steckdosenleiste_20176841c4dd571d699b create_time: 1620129285
2021-08-26_20:02:46 Steckdosenleiste_20176841c4dd571d699b icon: https://images.tuyaeu.com/smart/icon/ay1519800722250B425i/1560222411c64286ea14a.jpg
2021-08-26_20:02:46 Steckdosenleiste_20176841c4dd571d699b id: xxxxxxxxxxxx
2021-08-26_20:02:46 Steckdosenleiste_20176841c4dd571d699b ip: xxxxxxxxxxxx
2021-08-26_20:02:46 Steckdosenleiste_20176841c4dd571d699b lat: xxxxxxxxxxx
2021-08-26_20:02:46 Steckdosenleiste_20176841c4dd571d699b local_key: xxxxxxxxxxx
2021-08-26_20:02:46 Steckdosenleiste_20176841c4dd571d699b lon: xxxxxxxxxx
2021-08-26_20:02:46 Steckdosenleiste_20176841c4dd571d699b model: 402A
2021-08-26_20:02:46 Steckdosenleiste_20176841c4dd571d699b name: Steckdosenleiste
2021-08-26_20:02:46 Steckdosenleiste_20176841c4dd571d699b online: on
2021-08-26_20:02:46 Steckdosenleiste_20176841c4dd571d699b owner_id: 15487476
2021-08-26_20:02:46 Steckdosenleiste_20176841c4dd571d699b product_id: okiuzzuwarvjos4a
2021-08-26_20:02:46 Steckdosenleiste_20176841c4dd571d699b product_name: Smart Socket
2021-08-26_20:02:46 Steckdosenleiste_20176841c4dd571d699b sub: off
2021-08-26_20:02:46 Steckdosenleiste_20176841c4dd571d699b time_zone: +01:00
2021-08-26_20:02:46 Steckdosenleiste_20176841c4dd571d699b uid: eu1598817427882BAzmt
2021-08-26_20:02:46 Steckdosenleiste_20176841c4dd571d699b update_time: 1629968906
2021-08-26_20:02:46 Steckdosenleiste_20176841c4dd571d699b uuid: 20176841c4dd571d699b
2021-08-26_20:02:48 Steckdosenleiste_20176841c4dd571d699b off
2021-08-26_20:02:48 Steckdosenleiste_20176841c4dd571d699b switch_2: off
2021-08-26_20:02:48 Steckdosenleiste_20176841c4dd571d699b switch_3: off
2021-08-26_20:02:48 Steckdosenleiste_20176841c4dd571d699b switch_4: off
2021-08-26_20:02:48 Steckdosenleiste_20176841c4dd571d699b switch_5: off
2021-08-26_20:02:48 Steckdosenleiste_20176841c4dd571d699b countdown_1: 0.0
2021-08-26_20:02:48 Steckdosenleiste_20176841c4dd571d699b countdown_2: 0.0
2021-08-26_20:02:48 Steckdosenleiste_20176841c4dd571d699b countdown_3: 0.0
2021-08-26_20:02:48 Steckdosenleiste_20176841c4dd571d699b countdown_4: 0.0
2021-08-26_20:02:48 Steckdosenleiste_20176841c4dd571d699b countdown_5: 0.0
2021-08-26_20:06:21 Steckdosenleiste_20176841c4dd571d699b on
2021-08-26_20:06:35 Steckdosenleiste_20176841c4dd571d699b off
2021-08-26_20:06:42 Steckdosenleiste_20176841c4dd571d699b off
2021-08-26_20:07:06 Steckdosenleiste_20176841c4dd571d699b on
2021-08-26_20:07:16 Steckdosenleiste_20176841c4dd571d699b off
2021-08-26_20:41:33 Steckdosenleiste_20176841c4dd571d699b on
2021-08-26_20:42:12 Steckdosenleiste_20176841c4dd571d699b off
2021-08-26_20:58:33 Steckdosenleiste_20176841c4dd571d699b on
2021-08-26_20:58:41 Steckdosenleiste_20176841c4dd571d699b off
Bitte das fhempy Log, nicht von FHEM direkt.
Hallo Dominik,
das fhempy-2021-08-26.log text ist leer und auch in der Vergangenheit wurde nie etwas reingeschrieben.
Schau bitte auch ob du noch ein PythonBinding Log hast. Eventuell steht dort was drin.
Ich habe dieses gefunden:
2021-08-26 01:56:13,252 - ERROR - tuya_cloud_connector: 'NoneType' object has no attribute 'disconnect'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 71, in restart_mqtt_loop
await self.restart_mqtt()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 76, in restart_mqtt
self.device_manager.mq.stop()
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openmq.py", line 224, in stop
self.client.disconnect()
AttributeError: 'NoneType' object has no attribute 'disconnect'
2021-08-26 03:08:15,368 - ERROR - pychromecast.socket_client: [Dachboden(192.168.178.74):8009] Failed to connect to service ServiceInfo(type='mdns', data='Google-Nest-Mini-143ba75a235b6b691742e0dfcf309e1a._googlecast._tcp.local.'), retrying in 5.0s
2021-08-26 03:40:55,302 - ERROR - pychromecast.socket_client: [Chromecast(192.168.178.68):8009] Failed to connect to service ServiceInfo(type='host', data=('192.168.178.68', 8009)), retrying in 5.0s
2021-08-26 03:54:33,262 - ERROR - tuya_cloud_connector: 'NoneType' object has no attribute 'disconnect'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 71, in restart_mqtt_loop
await self.restart_mqtt()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 76, in restart_mqtt
self.device_manager.mq.stop()
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openmq.py", line 224, in stop
self.client.disconnect()
AttributeError: 'NoneType' object has no attribute 'disconnect'
2021-08-26 04:50:17,499 - ERROR - pychromecast.socket_client: [Google-Nest(192.168.178.28):8009] Error reading from socket.
2021-08-26 04:50:17,586 - ERROR - pychromecast.socket_client: [Google-Nest(192.168.178.28):8009] Failed to connect to service ServiceInfo(type='host', data=('192.168.178.28', 8009)), retrying in 5.0s
2021-08-26 05:52:53,267 - ERROR - tuya_cloud_connector: 'NoneType' object has no attribute 'disconnect'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 71, in restart_mqtt_loop
await self.restart_mqtt()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 76, in restart_mqtt
self.device_manager.mq.stop()
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openmq.py", line 224, in stop
self.client.disconnect()
AttributeError: 'NoneType' object has no attribute 'disconnect'
2021-08-26 06:45:38,299 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdateIfChanged($defs{'Motorrad_Ladestation_Carport_bf5ee44c2ba7b84276eueh'},'state','off');;
2021-08-26 06:58:57,147 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdateIfChanged($defs{'Motorrad_Ladestation_Carport_bf5ee44c2ba7b84276eueh'},'dp_26','0');;
2021-08-26 07:19:06,912 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Motorrad_Ladestation_Carport_bf5ee44c2ba7b84276eueh'});;
2021-08-26 07:23:56,635 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Motorrad_Ladestation_Carport_bf5ee44c2ba7b84276eueh'});;
2021-08-26 07:23:56,645 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'spoti'});;
2021-08-26 07:40:59,025 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Motorrad_Ladestation_Carport_bf5ee44c2ba7b84276eueh'});;
2021-08-26 07:51:13,271 - ERROR - tuya_cloud_connector: 'NoneType' object has no attribute 'disconnect'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 71, in restart_mqtt_loop
await self.restart_mqtt()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 76, in restart_mqtt
self.device_manager.mq.stop()
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openmq.py", line 224, in stop
self.client.disconnect()
AttributeError: 'NoneType' object has no attribute 'disconnect'
2021-08-26 09:49:33,274 - ERROR - tuya_cloud_connector: 'NoneType' object has no attribute 'disconnect'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 71, in restart_mqtt_loop
await self.restart_mqtt()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 76, in restart_mqtt
self.device_manager.mq.stop()
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openmq.py", line 224, in stop
self.client.disconnect()
AttributeError: 'NoneType' object has no attribute 'disconnect'
2021-08-26 10:59:32,819 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdateIfChanged($defs{'Motorrad_Ladestation_Carport_bf5ee44c2ba7b84276eueh'},'cur_power','3.6');;
2021-08-26 11:24:52,791 - INFO - fhempy.lib.pkg_installer: Attempting install of fhempy
2021-08-26 11:24:59,987 - INFO - fhempy.lib.pkg_installer: Successfully installed fhempy update!
2021-08-26 11:25:00,568 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-08-26 11:25:00,579 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-08-26 11:25:11,015 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
[2021-08-26 11:25:13,645] [tuya-openmq] error while get mqtt config
2021-08-26 11:25:13,645 - ERROR - tuya iot: error while get mqtt config
Exception in thread Thread-4:
Traceback (most recent call last):
File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
self.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openmq.py", line 173, in run
time.sleep(self.mq_config.expireTime - 60)
AttributeError: 'TuyaOpenMQ' object has no attribute 'mq_config'
2021-08-26 11:25:14,349 - DEBUG - Castdevice_Aussenbereich: Start discovery
2021-08-26 11:30:39,592 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-08-26 11:30:39,603 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-08-26 11:31:23,908 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-08-26 11:31:24,776 - WARNING - asyncio: Executing <Task pending name='Task-19' coro=<PyBinding.onMessage() running at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py:129> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at /usr/lib/python3.8/asyncio/futures.py:360, <TaskWakeupMethWrapper object at 0x7f0899ca0370>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> created at /usr/lib/python3.8/asyncio/tasks.py:382> took 0.177 seconds
2021-08-26 11:31:24,960 - WARNING - asyncio: Executing <Task pending name='Task-21' coro=<PyBinding.onMessage() running at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py:129> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at /usr/lib/python3.8/asyncio/futures.py:360, <TaskWakeupMethWrapper object at 0x7f0898485190>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> created at /usr/lib/python3.8/asyncio/tasks.py:382> took 0.118 seconds
2021-08-26 11:31:38,428 - DEBUG - Castdevice_Aussenbereich: Start discovery
2021-08-26 11:31:42,655 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: AttrVal('spoti', 'update_status_interval', '')
2021-08-26 11:31:42,660 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsSingleUpdate($defs{'Ladestation_bf5ee44c2ba7b84276eueh'},'state','ready',1)
2021-08-26 11:31:42,662 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsSingleUpdate($defs{'Smart_Plug_bfc0100ce21d5d7715kbjp'},'state','ready',1)
2021-08-26 11:31:42,668 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsSingleUpdate($defs{'Steckdosenleiste_20176841c4dd571d699b'},'state','ready',1)
2021-08-26 11:31:42,681 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsSingleUpdate($defs{'tuya_cloud_connector'},'state','connecting',1)
2021-08-26 11:31:42,720 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsSingleUpdate($defs{'Wohnzimmervorhang_83652817a4e57c966258'},'state','ready',1)
[2021-08-26 11:31:43,324] [tuya-openmq] error while get mqtt config
2021-08-26 11:31:43,324 - ERROR - tuya iot: error while get mqtt config
Exception in thread Thread-79:
Traceback (most recent call last):
File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
self.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openmq.py", line 173, in run
time.sleep(self.mq_config.expireTime - 60)
AttributeError: 'TuyaOpenMQ' object has no attribute 'mq_config'
2021-08-26 11:37:20,678 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdateIfChanged($defs{'Motorrad_Ladestation_Carport_bf5ee44c2ba7b84276eueh'},'state','off');;
2021-08-26 11:39:33,546 - INFO - fhempy.lib.pkg_installer: Attempting install of fhempy
2021-08-26 11:39:37,119 - INFO - fhempy.lib.pkg_installer: Successfully installed fhempy update!
2021-08-26 11:39:37,747 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-08-26 11:39:37,759 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-08-26 11:39:47,436 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-08-26 11:39:48,026 - WARNING - asyncio: Executing <Task pending name='Task-20' coro=<PyBinding.onMessage() running at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py:129> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at /usr/lib/python3.8/asyncio/futures.py:360, <TaskWakeupMethWrapper object at 0x7f4ba8aa4100>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> created at /usr/lib/python3.8/asyncio/tasks.py:382> took 0.153 seconds
2021-08-26 11:39:48,149 - WARNING - asyncio: Executing <Task pending name='Task-21' coro=<PyBinding.onMessage() running at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py:129> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at /usr/lib/python3.8/asyncio/futures.py:360, <TaskWakeupMethWrapper object at 0x7f4ba8844e20>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> created at /usr/lib/python3.8/asyncio/tasks.py:382> took 0.120 seconds
[2021-08-26 11:39:50,189] [tuya-openmq] error while get mqtt config
2021-08-26 11:39:50,189 - ERROR - tuya iot: error while get mqtt config
Exception in thread Thread-4:
Traceback (most recent call last):
File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
self.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openmq.py", line 173, in run
time.sleep(self.mq_config.expireTime - 60)
AttributeError: 'TuyaOpenMQ' object has no attribute 'mq_config'
2021-08-26 11:39:50,514 - DEBUG - Castdevice_Aussenbereich: Start discovery
2021-08-26 11:48:44,894 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Motorrad_Ladestation_Carport_bf5ee44c2ba7b84276eueh'});;
2021-08-26 13:08:00,689 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdateIfChanged($defs{'Motorrad_Ladestation_Carport_bf5ee44c2ba7b84276eueh'},'state','off');;
2021-08-26 13:38:10,166 - ERROR - tuya_cloud_connector: 'NoneType' object has no attribute 'disconnect'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 71, in restart_mqtt_loop
await self.restart_mqtt()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 76, in restart_mqtt
self.device_manager.mq.stop()
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openmq.py", line 224, in stop
self.client.disconnect()
AttributeError: 'NoneType' object has no attribute 'disconnect'
2021-08-26 15:36:30,172 - ERROR - tuya_cloud_connector: 'NoneType' object has no attribute 'disconnect'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 71, in restart_mqtt_loop
await self.restart_mqtt()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 76, in restart_mqtt
self.device_manager.mq.stop()
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openmq.py", line 224, in stop
self.client.disconnect()
AttributeError: 'NoneType' object has no attribute 'disconnect'
2021-08-26 17:26:57,895 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdateIfChanged($defs{'Motorrad_Ladestation_Carport_bf5ee44c2ba7b84276eueh'},'state','off');;
2021-08-26 17:34:50,183 - ERROR - tuya_cloud_connector: 'NoneType' object has no attribute 'disconnect'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 71, in restart_mqtt_loop
await self.restart_mqtt()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 76, in restart_mqtt
self.device_manager.mq.stop()
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openmq.py", line 224, in stop
self.client.disconnect()
AttributeError: 'NoneType' object has no attribute 'disconnect'
2021-08-26 18:29:59,822 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdateIfChanged($defs{'Motorrad_Ladestation_Carport_bf5ee44c2ba7b84276eueh'},'cur_power','0.0');;
2021-08-26 18:45:18,632 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Motorrad_Ladestation_Carport_bf5ee44c2ba7b84276eueh'});;
2021-08-26 18:48:52,550 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Motorrad_Ladestation_Carport_bf5ee44c2ba7b84276eueh'});;
2021-08-26 19:06:14,134 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdateIfChanged($defs{'Motorrad_Ladestation_Carport_bf5ee44c2ba7b84276eueh'},'state','off');;
2021-08-26 19:33:10,189 - ERROR - tuya_cloud_connector: 'NoneType' object has no attribute 'disconnect'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 71, in restart_mqtt_loop
await self.restart_mqtt()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 76, in restart_mqtt
self.device_manager.mq.stop()
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openmq.py", line 224, in stop
self.client.disconnect()
AttributeError: 'NoneType' object has no attribute 'disconnect'
2021-08-26 20:01:46,750 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-08-26 20:01:46,761 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-08-26 20:02:30,124 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-08-26 20:02:31,652 - WARNING - asyncio: Executing <Task pending name='Task-21' coro=<PyBinding.onMessage() running at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py:129> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at /usr/lib/python3.8/asyncio/futures.py:360, <TaskWakeupMethWrapper object at 0x7f8eeab62490>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> created at /usr/lib/python3.8/asyncio/tasks.py:382> took 0.131 seconds
[2021-08-26 20:02:41,553] [tuya-openmq] error while get mqtt config
2021-08-26 20:02:41,553 - ERROR - tuya iot: error while get mqtt config
Exception in thread Thread-4:
Traceback (most recent call last):
File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
self.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openmq.py", line 173, in run
time.sleep(self.mq_config.expireTime - 60)
AttributeError: 'TuyaOpenMQ' object has no attribute 'mq_config'
2021-08-26 20:02:43,953 - DEBUG - Castdevice_Aussenbereich: Start discovery
2021-08-26 21:17:47,633 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdateIfChanged($defs{'Motorrad_Ladestation_Carport_bf5ee44c2ba7b84276eueh'},'state','off');;
Perfekt, ich schau mir das später an was da los ist.
[quote author=dominik link=topic=122288.msg1171895#msg1171895 date=1629994323]
Bitte mal testen ob der colorpicker funktioniert. Ich habe diesen mal eingebaut, kann ihn aber selbst nicht testen.
Also richtig testen kann ich es erst am Sonntag, da mein Sohn vor dem Urlaub den Stecker gezogen hat. Hier aber noch ein Fehlercode für beide LED Bänder nach dem Update.
2021-08-26 21:42:22,853 - ERROR - xxxx_Bett__bf4e9bd5b8c624f127c0io: string indices must be integers
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 272, in update_readings_arr
await self.update_readings_hsv(status["code"], status["value"])
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 307, in update_readings_hsv
hsv_json["h"] / 360, hsv_json["s"] / 1000, hsv_json["v"] / 1000
TypeError: string indices must be integers
@Sommerfeld,
der Fehler tritt bei dir schon beim Verbinden zum tuya MQTT Server auf.
[2021-08-26 11:25:13,645] [tuya-openmq] error while get mqtt config
2021-08-26 11:25:13,645 - ERROR - tuya iot: error while get mqtt config
Exception in thread Thread-4:
Traceback (most recent call last):
File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
self.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openmq.py", line 173, in run
time.sleep(self.mq_config.expireTime - 60)
AttributeError: 'TuyaOpenMQ' object has no attribute 'mq_config'
Prüfe bitte nochmals deine CLIENT_ID, CLIENT_SECRET, USERNAME, PASSWORD.
Ich habe gerade beim Reconnect noch etwas verbessert, aber das wird denke ich nicht helfen. Weil schon das Herstellen der Verbindung fehl schlägt.
@barneybaer,
Zumindest der Fehler sollte nun weg sein.
Hallo Dominik,
vielen Dank für die schnelle Antwort.
Zitat@Sommerfeld,
der Fehler tritt bei dir schon beim Verbinden zum tuya MQTT Server auf.
Ich prüfe es und melde mich dann.
Zitat von: dominik am 26 August 2021, 23:59:02
@barneybaer,
Zumindest der Fehler sollte nun weg sein.
Leider noch nicht hier ein neuer Auszug.
2021-08-27 09:20:05,690 - ERROR - xxx_Bett__bf4e9bd5b8c624f127c0io: string indices must be integers
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 272, in update_readings_arr
await self.update_readings_hsv(status["code"], status["value"])
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 309, in update_readings_hsv
int(hsv_json["h"]) / 360,
TypeError: string indices must be integers
ZitatPrüfe bitte nochmals deine CLIENT_ID, CLIENT_SECRET, USERNAME, PASSWORD.
Ich habe gerade beim Reconnect noch etwas verbessert, aber das wird denke ich nicht helfen. Weil schon das Herstellen der Verbindung fehl schlägt.
Habe die Def. geprüft, konnte keinen Fehler finden
Internals:
.AttrList .*
.FhemMetaInternals 1
DEF tuya_cloud setup xxxxxxxxxx xxxxxxxxxxx xxxx.xxxx@gmx.de xxxxxxxxx tuyaSmart Europe
FUUID 6124c892-f33f-3b5c-c331-4e9f4a1101491661
FVERSION 10_PythonModule.pm:0.182830/2019-01-16
IODev local_pybinding
NAME tuya_cloud_connector
NR 1183
PYTHONTYPE tuya_cloud
STATE connected
TYPE PythonModule
.attraggr:
.attrminint:
READINGS:
2021-08-27 12:08:26 state connected
args:
tuya_cloud_connector
PythonModule
tuya_cloud
setup
xxxxxxxx
xxxxxxxx
xxxx.xxxxx@gmx.de
xxxxxxxxxx
tuyaSmart
Europe
argsh:
Attributes:
alias tuya_cloud_connectorMerkwürdig ist, dass das Schalten möglich ist. Folglich müsste ja eine Verbindung doch existieren, oder?
@barneybaer,
bitte nochmals mit der neuen Version testen. Danke!
@Sommerfeld,
die Commands werden per HTTPS POST Request geschickt. Die Events werden aber per MQTT abgefragt. Nachdem nur MQTT nicht funktioniert, kommen bei dir keine Events an.
Hat noch jemand das Problem?
Hat es bei dir schon mal funktioniert? Hast du beim Projekt den Development Type SmartHome angegeben und eh nicht Custom?
Hallo Dominik,
seit dem 25.08.2021 abends funktioniert es nicht mehr.
Davor war alles in Ordnung.
Im Projekt ist bei Development Type SmartHome eingegeben.
Komisch ist nur, das beim Neustart von FHEM die Readings aktualisiert werden.
Ist MQTT dafür nicht notwendig?
Beim Abfragen der Devices wird auch der Status dieser zurück gegeben, das läuft nicht über MQTT.
[quote author=dominik link=topic=122288.msg1172032#msg1172032 date=1630066066
@Sommerfeld,
die Commands werden per HTTPS POST Request geschickt. Die Events werden aber per MQTT abgefragt. Nachdem nur MQTT nicht funktioniert, kommen bei dir keine Events an.
Hat noch jemand das Problem?
[/quote]
Hab auch was im Log von heute morgen.
2021-08-27 03:36:51,179 - ERROR - Efeu_Decke: Failed to get updates from miflora C4:7C:8D:xx:xx:xx
2021-08-27 03:37:20,270 - ERROR - tuya_cloud_connector: 'NoneType' object has no attribute 'disconnect'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 71, in restart_mqtt_loop
await self.restart_mqtt()
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 76, in restart_mqtt
self.device_manager.mq.stop()
File "/opt/fhem/.local/lib/python3.7/site-packages/tuya_iot/openmq.py", line 224, in stop
self.client.disconnect()
AttributeError: 'NoneType' object has no attribute 'disconnect'
Zitat von: dominik am 27 August 2021, 14:07:46
@barneybaer,
bitte nochmals mit der neuen Version testen. Danke!
Weiterer Fehler beim updaten.
2021-08-27 14:56:55,234 - ERROR - xxx_Bett__bf4e9bd5b8c624f127c0io: Unknown format code 'x' for object of type 'float'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 273, in update_readings_arr
status["code"], json.loads(status["value"])
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 319, in update_readings_hsv
rgb_hex = f"{red:02x}{green:02x}{blue:02x}"
ValueError: Unknown format code 'x' for object of type 'float'
@barneybaer,
dann werden bei dir die Readings auch nicht mehr aktualisiert? Vielleicht hat tuya etwas an der Schnittstelle gedreht, auch möglich.
Wegen colour_data...habe gerade noch ein Update gemacht.
Zitat von: dominik am 27 August 2021, 19:41:41
@barneybaer,
dann werden bei dir die Readings auch nicht mehr aktualisiert? Vielleicht hat tuya etwas an der Schnittstelle gedreht, auch möglich.
Wegen colour_data...habe gerade noch ein Update gemacht.
Readings scheinen zu gehen, wenn ich über die tuya App die Geräte schalte werden sie in Fhem auch aktualisiert.
Keine Fehler mehr beim Updaten. Colorpicker teste ich am Sonntag.
Danke dir.
Zitat von: Superposchi am 26 August 2021, 09:23:17
Lediglich on und off
mode, switch_led, work_mode müssten es sein
Wobei mode in der App lediglich "weak und strong" auswählbar hat und
work_mode bietet in der SmartLife-App lediglich "Gradiant, Fixed und Nightlight" mit einer Farbauswahl an
switch_led wird in den nächsten Tagen von tuya integriert. Die anderen Funktionen sind leider nicht tuya Standard und können daher nicht unterstützt werden.
Hallo Dominik,
ich habe alles neu aufgesetzt und habe immer noch das
gleiche Verhalten. Habe ich noch eine Chance zur Lösung?
Beste Grüße
Poste bitte noch ein aktuelles fhempy Log.
Hallo Dominik,
vielen Dank, dass du dir das noch einmal anschaust.
[code]lf._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1851, in _run_once
handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
self._context.run(self._callback, *self._args)
File "/usr/lib/python3.8/asyncio/selector_events.py", line 1021, in _read_ready
self._protocol.datagram_received(data, addr)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 295, in datagram_received
self.zc.handle_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 735, in handle_response
self.record_manager.async_updates_from_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 436, in async_updates_from_response
self.async_updates_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 369, in async_updates_complete
listener.async_update_records_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 412, in async_update_records_complete
self._fire_service_state_changed_event(event)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 423, in _fire_service_state_changed_event
self._service_state_changed.fire(
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/__init__.py", line 55, in fire
h(**kwargs)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 178, in on_change
getattr(listener, _ON_CHANGE_DISPATCH[state_change])(zeroconf, service_type, name)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 20, in update_service
asyncio.create_task(self.foundDevice(zc, type, name))
File "/usr/lib/python3.8/asyncio/tasks.py", line 382, in create_task
task = loop.create_task(coro)
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 31, in foundDevice
info = await zc.async_get_service_info(type, name)
AttributeError: 'Zeroconf' object has no attribute 'async_get_service_info'
2021-08-29 18:02:15,840 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-08-29 18:02:15,841 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-08-29 18:03:01,566 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-08-29 18:03:01,644 - ERROR - asyncio: Task exception was never retrieved
future: <Task finished name='Task-10' coro=<discover_fhempy.foundDevice() done, defined at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py:30> exception=AttributeError("'Zeroconf' object has no attribute 'async_get_service_info'") created at /usr/lib/python3.8/asyncio/tasks.py:382>
source_traceback: Object created at (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 470, in run
asyncio.get_event_loop().run_forever()
File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
self._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1851, in _run_once
handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
self._context.run(self._callback, *self._args)
File "/usr/lib/python3.8/asyncio/selector_events.py", line 1021, in _read_ready
self._protocol.datagram_received(data, addr)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 295, in datagram_received
self.zc.handle_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 735, in handle_response
self.record_manager.async_updates_from_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 436, in async_updates_from_response
self.async_updates_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 369, in async_updates_complete
listener.async_update_records_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 412, in async_update_records_complete
self._fire_service_state_changed_event(event)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 423, in _fire_service_state_changed_event
self._service_state_changed.fire(
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/__init__.py", line 55, in fire
h(**kwargs)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 178, in on_change
getattr(listener, _ON_CHANGE_DISPATCH[state_change])(zeroconf, service_type, name)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 28, in add_service
asyncio.create_task(self.foundDevice(zc, type, name))
File "/usr/lib/python3.8/asyncio/tasks.py", line 382, in create_task
task = loop.create_task(coro)
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 31, in foundDevice
info = await zc.async_get_service_info(type, name)
AttributeError: 'Zeroconf' object has no attribute 'async_get_service_info'
2021-08-29 18:03:01,687 - ERROR - asyncio: Task exception was never retrieved
future: <Task finished name='Task-11' coro=<discover_fhempy.foundDevice() done, defined at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py:30> exception=AttributeError("'Zeroconf' object has no attribute 'async_get_service_info'") created at /usr/lib/python3.8/asyncio/tasks.py:382>
source_traceback: Object created at (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 470, in run
asyncio.get_event_loop().run_forever()
File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
self._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1851, in _run_once
handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
self._context.run(self._callback, *self._args)
File "/usr/lib/python3.8/asyncio/selector_events.py", line 1021, in _read_ready
self._protocol.datagram_received(data, addr)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 295, in datagram_received
self.zc.handle_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 735, in handle_response
self.record_manager.async_updates_from_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 436, in async_updates_from_response
self.async_updates_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 369, in async_updates_complete
listener.async_update_records_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 412, in async_update_records_complete
self._fire_service_state_changed_event(event)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 423, in _fire_service_state_changed_event
self._service_state_changed.fire(
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/__init__.py", line 55, in fire
h(**kwargs)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 178, in on_change
getattr(listener, _ON_CHANGE_DISPATCH[state_change])(zeroconf, service_type, name)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 28, in add_service
asyncio.create_task(self.foundDevice(zc, type, name))
File "/usr/lib/python3.8/asyncio/tasks.py", line 382, in create_task
task = loop.create_task(coro)
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 31, in foundDevice
info = await zc.async_get_service_info(type, name)
AttributeError: 'Zeroconf' object has no attribute 'async_get_service_info'
2021-08-29 18:03:01,709 - ERROR - asyncio: Task exception was never retrieved
future: <Task finished name='Task-12' coro=<discover_fhempy.foundDevice() done, defined at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py:30> exception=AttributeError("'Zeroconf' object has no attribute 'async_get_service_info'") created at /usr/lib/python3.8/asyncio/tasks.py:382>
source_traceback: Object created at (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 470, in run
asyncio.get_event_loop().run_forever()
File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
self._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1851, in _run_once
handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
self._context.run(self._callback, *self._args)
File "/usr/lib/python3.8/asyncio/selector_events.py", line 1021, in _read_ready
self._protocol.datagram_received(data, addr)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 295, in datagram_received
self.zc.handle_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 735, in handle_response
self.record_manager.async_updates_from_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 436, in async_updates_from_response
self.async_updates_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 369, in async_updates_complete
listener.async_update_records_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 412, in async_update_records_complete
self._fire_service_state_changed_event(event)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 423, in _fire_service_state_changed_event
self._service_state_changed.fire(
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/__init__.py", line 55, in fire
h(**kwargs)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 178, in on_change
getattr(listener, _ON_CHANGE_DISPATCH[state_change])(zeroconf, service_type, name)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 28, in add_service
asyncio.create_task(self.foundDevice(zc, type, name))
File "/usr/lib/python3.8/asyncio/tasks.py", line 382, in create_task
task = loop.create_task(coro)
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 31, in foundDevice
info = await zc.async_get_service_info(type, name)
AttributeError: 'Zeroconf' object has no attribute 'async_get_service_info'
2021-08-29 18:03:01,721 - ERROR - asyncio: Task exception was never retrieved
future: <Task finished name='Task-13' coro=<discover_fhempy.foundDevice() done, defined at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py:30> exception=AttributeError("'Zeroconf' object has no attribute 'async_get_service_info'") created at /usr/lib/python3.8/asyncio/tasks.py:382>
source_traceback: Object created at (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 470, in run
asyncio.get_event_loop().run_forever()
File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
self._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1851, in _run_once
handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
self._context.run(self._callback, *self._args)
File "/usr/lib/python3.8/asyncio/selector_events.py", line 1021, in _read_ready
self._protocol.datagram_received(data, addr)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 295, in datagram_received
self.zc.handle_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 735, in handle_response
self.record_manager.async_updates_from_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 436, in async_updates_from_response
self.async_updates_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 369, in async_updates_complete
listener.async_update_records_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 412, in async_update_records_complete
self._fire_service_state_changed_event(event)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 423, in _fire_service_state_changed_event
self._service_state_changed.fire(
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/__init__.py", line 55, in fire
h(**kwargs)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 178, in on_change
getattr(listener, _ON_CHANGE_DISPATCH[state_change])(zeroconf, service_type, name)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 28, in add_service
asyncio.create_task(self.foundDevice(zc, type, name))
File "/usr/lib/python3.8/asyncio/tasks.py", line 382, in create_task
task = loop.create_task(coro)
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 31, in foundDevice
info = await zc.async_get_service_info(type, name)
AttributeError: 'Zeroconf' object has no attribute 'async_get_service_info'
2021-08-29 18:03:01,746 - ERROR - asyncio: Task exception was never retrieved
future: <Task finished name='Task-14' coro=<discover_fhempy.foundDevice() done, defined at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py:30> exception=AttributeError("'Zeroconf' object has no attribute 'async_get_service_info'") created at /usr/lib/python3.8/asyncio/tasks.py:382>
source_traceback: Object created at (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 470, in run
asyncio.get_event_loop().run_forever()
File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
self._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1851, in _run_once
handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
self._context.run(self._callback, *self._args)
File "/usr/lib/python3.8/asyncio/selector_events.py", line 1021, in _read_ready
self._protocol.datagram_received(data, addr)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 295, in datagram_received
self.zc.handle_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 735, in handle_response
self.record_manager.async_updates_from_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 436, in async_updates_from_response
self.async_updates_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 369, in async_updates_complete
listener.async_update_records_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 412, in async_update_records_complete
self._fire_service_state_changed_event(event)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 423, in _fire_service_state_changed_event
self._service_state_changed.fire(
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/__init__.py", line 55, in fire
h(**kwargs)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 178, in on_change
getattr(listener, _ON_CHANGE_DISPATCH[state_change])(zeroconf, service_type, name)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 28, in add_service
asyncio.create_task(self.foundDevice(zc, type, name))
File "/usr/lib/python3.8/asyncio/tasks.py", line 382, in create_task
task = loop.create_task(coro)
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 31, in foundDevice
info = await zc.async_get_service_info(type, name)
AttributeError: 'Zeroconf' object has no attribute 'async_get_service_info'
2021-08-29 18:03:03,214 - WARNING - asyncio: Executing <Task pending name='Task-20' coro=<PyBinding.onMessage() running at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py:129> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at /usr/lib/python3.8/asyncio/futures.py:360, <TaskWakeupMethWrapper object at 0x7f4736fe1580>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> created at /usr/lib/python3.8/asyncio/tasks.py:382> took 0.135 seconds
[2021-08-29 18:03:09,782] [tuya-openmq] error while get mqtt config
2021-08-29 18:03:09,782 - ERROR - tuya iot: error while get mqtt config
Exception in thread Thread-1:
Traceback (most recent call last):
File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
self.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openmq.py", line 173, in run
time.sleep(self.mq_config.expireTime - 60)
AttributeError: 'TuyaOpenMQ' object has no attribute 'mq_config'
2021-08-29 18:03:12,774 - DEBUG - Castdevice_Aussenbereich: Start discovery
2021-08-29 18:03:19,686 - ERROR - asyncio: Task exception was never retrieved
future: <Task finished name='Task-853' coro=<discover_fhempy.foundDevice() done, defined at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py:30> exception=AttributeError("'Zeroconf' object has no attribute 'async_get_service_info'") created at /usr/lib/python3.8/asyncio/tasks.py:382>
source_traceback: Object created at (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 470, in run
asyncio.get_event_loop().run_forever()
File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
self._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1851, in _run_once
handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
self._context.run(self._callback, *self._args)
File "/usr/lib/python3.8/asyncio/selector_events.py", line 1021, in _read_ready
self._protocol.datagram_received(data, addr)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 295, in datagram_received
self.zc.handle_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 735, in handle_response
self.record_manager.async_updates_from_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 436, in async_updates_from_response
self.async_updates_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 369, in async_updates_complete
listener.async_update_records_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 412, in async_update_records_complete
self._fire_service_state_changed_event(event)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 423, in _fire_service_state_changed_event
self._service_state_changed.fire(
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/__init__.py", line 55, in fire
h(**kwargs)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 178, in on_change
getattr(listener, _ON_CHANGE_DISPATCH[state_change])(zeroconf, service_type, name)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 20, in update_service
asyncio.create_task(self.foundDevice(zc, type, name))
File "/usr/lib/python3.8/asyncio/tasks.py", line 382, in create_task
task = loop.create_task(coro)
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 31, in foundDevice
info = await zc.async_get_service_info(type, name)
AttributeError: 'Zeroconf' object has no attribute 'async_get_service_info'
2021-08-29 18:03:19,699 - ERROR - asyncio: Task exception was never retrieved
future: <Task finished name='Task-854' coro=<discover_fhempy.foundDevice() done, defined at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py:30> exception=AttributeError("'Zeroconf' object has no attribute 'async_get_service_info'") created at /usr/lib/python3.8/asyncio/tasks.py:382>
source_traceback: Object created at (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 470, in run
asyncio.get_event_loop().run_forever()
File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
self._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1851, in _run_once
handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
self._context.run(self._callback, *self._args)
File "/usr/lib/python3.8/asyncio/selector_events.py", line 1021, in _read_ready
self._protocol.datagram_received(data, addr)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 295, in datagram_received
self.zc.handle_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 735, in handle_response
self.record_manager.async_updates_from_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 436, in async_updates_from_response
self.async_updates_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 369, in async_updates_complete
listener.async_update_records_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 412, in async_update_records_complete
self._fire_service_state_changed_event(event)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 423, in _fire_service_state_changed_event
self._service_state_changed.fire(
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/__init__.py", line 55, in fire
h(**kwargs)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 178, in on_change
getattr(listener, _ON_CHANGE_DISPATCH[state_change])(zeroconf, service_type, name)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 20, in update_service
asyncio.create_task(self.foundDevice(zc, type, name))
File "/usr/lib/python3.8/asyncio/tasks.py", line 382, in create_task
task = loop.create_task(coro)
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 31, in foundDevice
info = await zc.async_get_service_info(type, name)
AttributeError: 'Zeroconf' object has no attribute 'async_get_service_info'
2021-08-29 18:03:20,468 - ERROR - asyncio: Task exception was never retrieved
future: <Task finished name='Task-855' coro=<discover_fhempy.foundDevice() done, defined at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py:30> exception=AttributeError("'Zeroconf' object has no attribute 'async_get_service_info'") created at /usr/lib/python3.8/asyncio/tasks.py:382>
source_traceback: Object created at (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 470, in run
asyncio.get_event_loop().run_forever()
File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
self._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1851, in _run_once
handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
self._context.run(self._callback, *self._args)
File "/usr/lib/python3.8/asyncio/selector_events.py", line 1021, in _read_ready
self._protocol.datagram_received(data, addr)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 295, in datagram_received
self.zc.handle_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 735, in handle_response
self.record_manager.async_updates_from_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 436, in async_updates_from_response
self.async_updates_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 369, in async_updates_complete
listener.async_update_records_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 412, in async_update_records_complete
self._fire_service_state_changed_event(event)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 423, in _fire_service_state_changed_event
self._service_state_changed.fire(
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/__init__.py", line 55, in fire
h(**kwargs)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 178, in on_change
getattr(listener, _ON_CHANGE_DISPATCH[state_change])(zeroconf, service_type, name)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 28, in add_service
asyncio.create_task(self.foundDevice(zc, type, name))
File "/usr/lib/python3.8/asyncio/tasks.py", line 382, in create_task
task = loop.create_task(coro)
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 31, in foundDevice
info = await zc.async_get_service_info(type, name)
AttributeError: 'Zeroconf' object has no attribute 'async_get_service_info'
2021-08-29 18:03:52,035 - ERROR - asyncio: Task exception was never retrieved
future: <Task finished name='Task-2164' coro=<discover_fhempy.foundDevice() done, defined at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py:30> exception=AttributeError("'Zeroconf' object has no attribute 'async_get_service_info'") created at /usr/lib/python3.8/asyncio/tasks.py:382>
source_traceback: Object created at (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 470, in run
asyncio.get_event_loop().run_forever()
File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
self._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1851, in _run_once
handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
self._context.run(self._callback, *self._args)
File "/usr/lib/python3.8/asyncio/selector_events.py", line 1021, in _read_ready
self._protocol.datagram_received(data, addr)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 295, in datagram_received
self.zc.handle_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 735, in handle_response
self.record_manager.async_updates_from_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 436, in async_updates_from_response
self.async_updates_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 369, in async_updates_complete
listener.async_update_records_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 412, in async_update_records_complete
self._fire_service_state_changed_event(event)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 423, in _fire_service_state_changed_event
self._service_state_changed.fire(
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/__init__.py", line 55, in fire
h(**kwargs)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 178, in on_change
getattr(listener, _ON_CHANGE_DISPATCH[state_change])(zeroconf, service_type, name)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 20, in update_service
asyncio.create_task(self.foundDevice(zc, type, name))
File "/usr/lib/python3.8/asyncio/tasks.py", line 382, in create_task
task = loop.create_task(coro)
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 31, in foundDevice
info = await zc.async_get_service_info(type, name)
AttributeError: 'Zeroconf' object has no attribute 'async_get_service_info'
2021-08-29 18:23:08,613 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-08-29 18:23:08,613 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-08-29 18:23:55,514 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-08-29 18:23:55,563 - ERROR - asyncio: Task exception was never retrieved
future: <Task finished name='Task-10' coro=<discover_fhempy.foundDevice() done, defined at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py:30> exception=AttributeError("'Zeroconf' object has no attribute 'async_get_service_info'") created at /usr/lib/python3.8/asyncio/tasks.py:382>
source_traceback: Object created at (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 470, in run
asyncio.get_event_loop().run_forever()
File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
self._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1851, in _run_once
handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
self._context.run(self._callback, *self._args)
File "/usr/lib/python3.8/asyncio/selector_events.py", line 1021, in _read_ready
self._protocol.datagram_received(data, addr)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 295, in datagram_received
self.zc.handle_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 735, in handle_response
self.record_manager.async_updates_from_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 436, in async_updates_from_response
self.async_updates_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 369, in async_updates_complete
listener.async_update_records_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 412, in async_update_records_complete
self._fire_service_state_changed_event(event)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 423, in _fire_service_state_changed_event
self._service_state_changed.fire(
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/__init__.py", line 55, in fire
h(**kwargs)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 178, in on_change
getattr(listener, _ON_CHANGE_DISPATCH[state_change])(zeroconf, service_type, name)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 28, in add_service
asyncio.create_task(self.foundDevice(zc, type, name))
File "/usr/lib/python3.8/asyncio/tasks.py", line 382, in create_task
task = loop.create_task(coro)
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 31, in foundDevice
info = await zc.async_get_service_info(type, name)
AttributeError: 'Zeroconf' object has no attribute 'async_get_service_info'
2021-08-29 18:23:55,680 - ERROR - asyncio: Task exception was never retrieved
future: <Task finished name='Task-11' coro=<discover_fhempy.foundDevice() done, defined at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py:30> exception=AttributeError("'Zeroconf' object has no attribute 'async_get_service_info'") created at /usr/lib/python3.8/asyncio/tasks.py:382>
source_traceback: Object created at (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 470, in run
asyncio.get_event_loop().run_forever()
File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
self._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1851, in _run_once
handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
self._context.run(self._callback, *self._args)
File "/usr/lib/python3.8/asyncio/selector_events.py", line 1021, in _read_ready
self._protocol.datagram_received(data, addr)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 295, in datagram_received
self.zc.handle_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 735, in handle_response
self.record_manager.async_updates_from_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 436, in async_updates_from_response
self.async_updates_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 369, in async_updates_complete
listener.async_update_records_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 412, in async_update_records_complete
self._fire_service_state_changed_event(event)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 423, in _fire_service_state_changed_event
self._service_state_changed.fire(
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/__init__.py", line 55, in fire
h(**kwargs)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 178, in on_change
getattr(listener, _ON_CHANGE_DISPATCH[state_change])(zeroconf, service_type, name)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 28, in add_service
asyncio.create_task(self.foundDevice(zc, type, name))
File "/usr/lib/python3.8/asyncio/tasks.py", line 382, in create_task
task = loop.create_task(coro)
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 31, in foundDevice
info = await zc.async_get_service_info(type, name)
AttributeError: 'Zeroconf' object has no attribute 'async_get_service_info'
2021-08-29 18:23:55,683 - ERROR - asyncio: Task exception was never retrieved
future: <Task finished name='Task-12' coro=<discover_fhempy.foundDevice() done, defined at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py:30> exception=AttributeError("'Zeroconf' object has no attribute 'async_get_service_info'") created at /usr/lib/python3.8/asyncio/tasks.py:382>
source_traceback: Object created at (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 470, in run
asyncio.get_event_loop().run_forever()
File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
self._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1851, in _run_once
handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
self._context.run(self._callback, *self._args)
File "/usr/lib/python3.8/asyncio/selector_events.py", line 1021, in _read_ready
self._protocol.datagram_received(data, addr)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 295, in datagram_received
self.zc.handle_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 735, in handle_response
self.record_manager.async_updates_from_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 436, in async_updates_from_response
self.async_updates_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 369, in async_updates_complete
listener.async_update_records_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 412, in async_update_records_complete
self._fire_service_state_changed_event(event)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 423, in _fire_service_state_changed_event
self._service_state_changed.fire(
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/__init__.py", line 55, in fire
h(**kwargs)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 178, in on_change
getattr(listener, _ON_CHANGE_DISPATCH[state_change])(zeroconf, service_type, name)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 28, in add_service
asyncio.create_task(self.foundDevice(zc, type, name))
File "/usr/lib/python3.8/asyncio/tasks.py", line 382, in create_task
task = loop.create_task(coro)
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 31, in foundDevice
info = await zc.async_get_service_info(type, name)
AttributeError: 'Zeroconf' object has no attribute 'async_get_service_info'
2021-08-29 18:23:55,735 - ERROR - asyncio: Task exception was never retrieved
future: <Task finished name='Task-13' coro=<discover_fhempy.foundDevice() done, defined at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py:30> exception=AttributeError("'Zeroconf' object has no attribute 'async_get_service_info'") created at /usr/lib/python3.8/asyncio/tasks.py:382>
source_traceback: Object created at (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 470, in run
asyncio.get_event_loop().run_forever()
File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
self._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1851, in _run_once
handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
self._context.run(self._callback, *self._args)
File "/usr/lib/python3.8/asyncio/selector_events.py", line 1021, in _read_ready
self._protocol.datagram_received(data, addr)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 295, in datagram_received
self.zc.handle_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 735, in handle_response
self.record_manager.async_updates_from_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 436, in async_updates_from_response
self.async_updates_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 369, in async_updates_complete
listener.async_update_records_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 412, in async_update_records_complete
self._fire_service_state_changed_event(event)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 423, in _fire_service_state_changed_event
self._service_state_changed.fire(
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/__init__.py", line 55, in fire
h(**kwargs)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 178, in on_change
getattr(listener, _ON_CHANGE_DISPATCH[state_change])(zeroconf, service_type, name)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 28, in add_service
asyncio.create_task(self.foundDevice(zc, type, name))
File "/usr/lib/python3.8/asyncio/tasks.py", line 382, in create_task
task = loop.create_task(coro)
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 31, in foundDevice
info = await zc.async_get_service_info(type, name)
AttributeError: 'Zeroconf' object has no attribute 'async_get_service_info'
2021-08-29 18:23:56,570 - WARNING - asyncio: Executing <Task pending name='Task-16' coro=<PyBinding.onMessage() running at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py:129> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at /usr/lib/python3.8/asyncio/futures.py:360, <TaskWakeupMethWrapper object at 0x7fb623d436a0>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> created at /usr/lib/python3.8/asyncio/tasks.py:382> took 0.104 seconds
2021-08-29 18:23:56,700 - WARNING - asyncio: Executing <Task pending name='Task-17' coro=<PyBinding.onMessage() running at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py:129> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at /usr/lib/python3.8/asyncio/futures.py:360, <TaskWakeupMethWrapper object at 0x7fb623bd6ee0>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> created at /usr/lib/python3.8/asyncio/tasks.py:382> took 0.104 seconds
2021-08-29 18:23:57,044 - WARNING - asyncio: Executing <Task pending name='Task-21' coro=<PyBinding.onMessage() running at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py:129> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at /usr/lib/python3.8/asyncio/futures.py:360, <TaskWakeupMethWrapper object at 0x7fb621134e50>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> created at /usr/lib/python3.8/asyncio/tasks.py:382> took 0.119 seconds
[2021-08-29 18:24:03,586] [tuya-openmq] error while get mqtt config
2021-08-29 18:24:03,586 - ERROR - tuya iot: error while get mqtt config
Exception in thread Thread-1:
Traceback (most recent call last):
File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
self.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openmq.py", line 173, in run
time.sleep(self.mq_config.expireTime - 60)
AttributeError: 'TuyaOpenMQ' object has no attribute 'mq_config'
2021-08-29 18:24:06,529 - DEBUG - Castdevice_Aussenbereich: Start discovery
2021-08-29 18:24:09,702 - ERROR - asyncio: Task exception was never retrieved
future: <Task finished name='Task-757' coro=<discover_fhempy.foundDevice() done, defined at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py:30> exception=AttributeError("'Zeroconf' object has no attribute 'async_get_service_info'") created at /usr/lib/python3.8/asyncio/tasks.py:382>
source_traceback: Object created at (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 470, in run
asyncio.get_event_loop().run_forever()
File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
self._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1851, in _run_once
handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
self._context.run(self._callback, *self._args)
File "/usr/lib/python3.8/asyncio/selector_events.py", line 1021, in _read_ready
self._protocol.datagram_received(data, addr)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 295, in datagram_received
self.zc.handle_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 735, in handle_response
self.record_manager.async_updates_from_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 436, in async_updates_from_response
self.async_updates_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 369, in async_updates_complete
listener.async_update_records_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 412, in async_update_records_complete
self._fire_service_state_changed_event(event)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 423, in _fire_service_state_changed_event
self._service_state_changed.fire(
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/__init__.py", line 55, in fire
h(**kwargs)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 178, in on_change
getattr(listener, _ON_CHANGE_DISPATCH[state_change])(zeroconf, service_type, name)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 20, in update_service
asyncio.create_task(self.foundDevice(zc, type, name))
File "/usr/lib/python3.8/asyncio/tasks.py", line 382, in create_task
task = loop.create_task(coro)
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 31, in foundDevice
info = await zc.async_get_service_info(type, name)
AttributeError: 'Zeroconf' object has no attribute 'async_get_service_info'
2021-08-29 18:24:14,744 - ERROR - asyncio: Task exception was never retrieved
future: <Task finished name='Task-863' coro=<discover_fhempy.foundDevice() done, defined at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py:30> exception=AttributeError("'Zeroconf' object has no attribute 'async_get_service_info'") created at /usr/lib/python3.8/asyncio/tasks.py:382>
source_traceback: Object created at (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 470, in run
asyncio.get_event_loop().run_forever()
File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
self._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1851, in _run_once
handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
self._context.run(self._callback, *self._args)
File "/usr/lib/python3.8/asyncio/selector_events.py", line 1021, in _read_ready
self._protocol.datagram_received(data, addr)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 295, in datagram_received
self.zc.handle_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 735, in handle_response
self.record_manager.async_updates_from_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 436, in async_updates_from_response
self.async_updates_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 369, in async_updates_complete
listener.async_update_records_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 412, in async_update_records_complete
self._fire_service_state_changed_event(event)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 423, in _fire_service_state_changed_event
self._service_state_changed.fire(
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/__init__.py", line 55, in fire
h(**kwargs)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 178, in on_change
getattr(listener, _ON_CHANGE_DISPATCH[state_change])(zeroconf, service_type, name)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 28, in add_service
asyncio.create_task(self.foundDevice(zc, type, name))
File "/usr/lib/python3.8/asyncio/tasks.py", line 382, in create_task
task = loop.create_task(coro)
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 31, in foundDevice
info = await zc.async_get_service_info(type, name)
AttributeError: 'Zeroconf' object has no attribute 'async_get_service_info'
2021-08-29 18:24:46,453 - ERROR - asyncio: Task exception was never retrieved
future: <Task finished name='Task-2144' coro=<discover_fhempy.foundDevice() done, defined at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py:30> exception=AttributeError("'Zeroconf' object has no attribute 'async_get_service_info'") created at /usr/lib/python3.8/asyncio/tasks.py:382>
source_traceback: Object created at (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 470, in run
asyncio.get_event_loop().run_forever()
File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
self._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1851, in _run_once
handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
self._context.run(self._callback, *self._args)
File "/usr/lib/python3.8/asyncio/selector_events.py", line 1021, in _read_ready
self._protocol.datagram_received(data, addr)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 295, in datagram_received
self.zc.handle_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 735, in handle_response
self.record_manager.async_updates_from_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 436, in async_updates_from_response
self.async_updates_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 369, in async_updates_complete
listener.async_update_records_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 412, in async_update_records_complete
self._fire_service_state_changed_event(event)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 423, in _fire_service_state_changed_event
self._service_state_changed.fire(
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/__init__.py", line 55, in fire
h(**kwargs)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/brow
Zitat von: dominik am 27 August 2021, 19:41:41
@barneybaer,
Wegen colour_data...habe gerade noch ein Update gemacht.
Farbe funktioniert und wird wie eingestellt auch im Reading als RGB Code angezeigt.
Danke schön
@Sommerfeld, mach bitte noch ein Update auf 0.1.105 und poste dann bitte mit code Tag, da sonst nicht alles angezeigt wird.
@barneybaer, super! Danke für die Rückmeldung!
Log nach update Version 0.1.106
8-29 18:28:10,716 - ERROR - asyncio: Task exception was never retrieved
future: <Task finished name='Task-2369' coro=<discover_fhempy.foundDevice() done, defined at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py:30> exception=AttributeError("'Zeroconf' object has no attribute 'async_get_service_info'") created at /usr/lib/python3.8/asyncio/tasks.py:382>
source_traceback: Object created at (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 470, in run
asyncio.get_event_loop().run_forever()
File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
self._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1851, in _run_once
handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
self._context.run(self._callback, *self._args)
File "/usr/lib/python3.8/asyncio/selector_events.py", line 1021, in _read_ready
self._protocol.datagram_received(data, addr)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 295, in datagram_received
self.zc.handle_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 735, in handle_response
self.record_manager.async_updates_from_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 436, in async_updates_from_response
self.async_updates_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 369, in async_updates_complete
listener.async_update_records_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 412, in async_update_records_complete
self._fire_service_state_changed_event(event)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 423, in _fire_service_state_changed_event
self._service_state_changed.fire(
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/__init__.py", line 55, in fire
h(**kwargs)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 178, in on_change
getattr(listener, _ON_CHANGE_DISPATCH[state_change])(zeroconf, service_type, name)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 28, in add_service
asyncio.create_task(self.foundDevice(zc, type, name))
File "/usr/lib/python3.8/asyncio/tasks.py", line 382, in create_task
task = loop.create_task(coro)
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 31, in foundDevice
info = await zc.async_get_service_info(type, name)
AttributeError: 'Zeroconf' object has no attribute 'async_get_service_info'
2021-08-29 19:09:27,775 - ERROR - asyncio: Task exception was never retrieved
future: <Task finished name='Task-3944' coro=<discover_fhempy.foundDevice() done, defined at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py:30> exception=AttributeError("'Zeroconf' object has no attribute 'async_get_service_info'") created at /usr/lib/python3.8/asyncio/tasks.py:382>
source_traceback: Object created at (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 470, in run
asyncio.get_event_loop().run_forever()
File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
self._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1851, in _run_once
handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
self._context.run(self._callback, *self._args)
File "/usr/lib/python3.8/asyncio/selector_events.py", line 1021, in _read_ready
self._protocol.datagram_received(data, addr)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 295, in datagram_received
self.zc.handle_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 735, in handle_response
self.record_manager.async_updates_from_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 436, in async_updates_from_response
self.async_updates_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 369, in async_updates_complete
listener.async_update_records_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 412, in async_update_records_complete
self._fire_service_state_changed_event(event)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 423, in _fire_service_state_changed_event
self._service_state_changed.fire(
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/__init__.py", line 55, in fire
h(**kwargs)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 178, in on_change
getattr(listener, _ON_CHANGE_DISPATCH[state_change])(zeroconf, service_type, name)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 20, in update_service
asyncio.create_task(self.foundDevice(zc, type, name))
File "/usr/lib/python3.8/asyncio/tasks.py", line 382, in create_task
task = loop.create_task(coro)
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 31, in foundDevice
info = await zc.async_get_service_info(type, name)
AttributeError: 'Zeroconf' object has no attribute 'async_get_service_info'
2021-08-29 20:13:13,056 - ERROR - asyncio: Task exception was never retrieved
future: <Task finished name='Task-4591' coro=<discover_fhempy.foundDevice() done, defined at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py:30> exception=AttributeError("'Zeroconf' object has no attribute 'async_get_service_info'") created at /usr/lib/python3.8/asyncio/tasks.py:382>
source_traceback: Object created at (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 470, in run
asyncio.get_event_loop().run_forever()
File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
self._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1851, in _run_once
handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
self._context.run(self._callback, *self._args)
File "/usr/lib/python3.8/asyncio/selector_events.py", line 1021, in _read_ready
self._protocol.datagram_received(data, addr)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 295, in datagram_received
self.zc.handle_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 735, in handle_response
self.record_manager.async_updates_from_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 436, in async_updates_from_response
self.async_updates_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 369, in async_updates_complete
listener.async_update_records_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 412, in async_update_records_complete
self._fire_service_state_changed_event(event)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 423, in _fire_service_state_changed_event
self._service_state_changed.fire(
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/__init__.py", line 55, in fire
h(**kwargs)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 178, in on_change
getattr(listener, _ON_CHANGE_DISPATCH[state_change])(zeroconf, service_type, name)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 20, in update_service
asyncio.create_task(self.foundDevice(zc, type, name))
File "/usr/lib/python3.8/asyncio/tasks.py", line 382, in create_task
task = loop.create_task(coro)
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 31, in foundDevice
info = await zc.async_get_service_info(type, name)
AttributeError: 'Zeroconf' object has no attribute 'async_get_service_info'
2021-08-29 20:22:23,525 - ERROR - tuya_cloud_connector: 'TuyaDeviceManager' object has no attribute '_on_message'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 71, in restart_mqtt_loop
await self.restart_mqtt()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 85, in restart_mqtt
tuya_mq.add_message_listener(self.device_manager._on_message)
AttributeError: 'TuyaDeviceManager' object has no attribute '_on_message'
[2021-08-29 20:22:23,701] [tuya-openmq] error while get mqtt config
2021-08-29 20:22:23,701 - ERROR - tuya iot: error while get mqtt config
Exception in thread Thread-65:
Traceback (most recent call last):
File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
self.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openmq.py", line 173, in run
time.sleep(self.mq_config.expireTime - 60)
AttributeError: 'TuyaOpenMQ' object has no attribute 'mq_config'
2021-08-29 21:03:50,558 - ERROR - asyncio: Task exception was never retrieved
future: <Task finished name='Task-5111' coro=<discover_fhempy.foundDevice() done, defined at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py:30> exception=AttributeError("'Zeroconf' object has no attribute 'async_get_service_info'") created at /usr/lib/python3.8/asyncio/tasks.py:382>
source_traceback: Object created at (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 470, in run
asyncio.get_event_loop().run_forever()
File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
self._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1851, in _run_once
handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
self._context.run(self._callback, *self._args)
File "/usr/lib/python3.8/asyncio/selector_events.py", line 1021, in _read_ready
self._protocol.datagram_received(data, addr)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 295, in datagram_received
self.zc.handle_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py", line 735, in handle_response
self.record_manager.async_updates_from_response(msg)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 436, in async_updates_from_response
self.async_updates_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_handlers.py", line 369, in async_updates_complete
listener.async_update_records_complete()
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 412, in async_update_records_complete
self._fire_service_state_changed_event(event)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 423, in _fire_service_state_changed_event
self._service_state_changed.fire(
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/__init__.py", line 55, in fire
h(**kwargs)
File "/opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py", line 178, in on_change
getattr(listener, _ON_CHANGE_DISPATCH[state_change])(zeroconf, service_type, name)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 20, in update_service
asyncio.create_task(self.foundDevice(zc, type, name))
File "/usr/lib/python3.8/asyncio/tasks.py", line 382, in create_task
task = loop.create_task(coro)
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/core/discover_fhempy/discover_fhempy.py", line 31, in foundDevice
info = await zc.async_get_service_info(type, name)
AttributeError: 'Zeroconf' object has no attribute 'async_get_service_info'
2021-08-29 21:25:22,834 - INFO - fhempy.lib.pkg_installer: Attempting install of fhempy
2021-08-29 21:25:30,400 - INFO - fhempy.lib.pkg_installer: Successfully installed fhempy update!
2021-08-29 21:25:31,011 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-08-29 21:25:31,020 - INFO - fhempy.lib.pkg_installer: Attempting install of async-upnp-client==0.20.0
2021-08-29 21:25:41,464 - INFO - fhempy.lib.pkg_installer: Successfully installed async-upnp-client==0.20.0 update!
2021-08-29 21:25:41,467 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-08-29 21:25:50,849 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-08-29 21:25:51,241 - WARNING - asyncio: Executing <Task pending name='Task-17' coro=<PyBinding.onMessage() running at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py:129> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at /usr/lib/python3.8/asyncio/futures.py:360, <TaskWakeupMethWrapper object at 0x7f557a2aa8b0>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> created at /usr/lib/python3.8/asyncio/tasks.py:382> took 0.104 seconds
2021-08-29 21:25:51,537 - WARNING - asyncio: Executing <Task pending name='Task-20' coro=<PyBinding.onMessage() running at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py:129> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at /usr/lib/python3.8/asyncio/futures.py:360, <TaskWakeupMethWrapper object at 0x7f5578114fd0>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> created at /usr/lib/python3.8/asyncio/tasks.py:382> took 0.146 seconds
[2021-08-29 21:25:53,775] [tuya-openmq] error while get mqtt config
2021-08-29 21:25:53,775 - ERROR - tuya iot: error while get mqtt config
Exception in thread Thread-1:
Traceback (most recent call last):
File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
self.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openmq.py", line 173, in run
time.sleep(self.mq_config.expireTime - 60)
AttributeError: 'TuyaOpenMQ' object has no attribute 'mq_config'
2021-08-29 21:25:54,292 - DEBUG - Castdevice_Aussenbereich: Start discovery
2021-08-29 21:28:51,316 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-08-29 21:28:51,328 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-08-29 21:29:37,653 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-08-29 21:29:38,787 - WARNING - asyncio: Executing <Task pending name='Task-15' coro=<PyBinding.onMessage() running at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py:129> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at /usr/lib/python3.8/asyncio/futures.py:360, <TaskWakeupMethWrapper object at 0x7f6ee8c001c0>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> created at /usr/lib/python3.8/asyncio/tasks.py:382> took 0.101 seconds
2021-08-29 21:29:39,227 - WARNING - asyncio: Executing <Task pending name='Task-20' coro=<PyBinding.onMessage() running at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py:129> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at /usr/lib/python3.8/asyncio/futures.py:360, <TaskWakeupMethWrapper object at 0x7f6ee1997af0>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> created at /usr/lib/python3.8/asyncio/tasks.py:382> took 0.105 seconds
[2021-08-29 21:29:47,484] [tuya-openmq] error while get mqtt config
2021-08-29 21:29:47,484 - ERROR - tuya iot: error while get mqtt config
Exception in thread Thread-1:
Traceback (most recent call last):
File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
self.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openmq.py", line 173, in run
time.sleep(self.mq_config.expireTime - 60)
AttributeError: 'TuyaOpenMQ' object has no attribute 'mq_config'
2021-08-29 21:29:4
Hast du im Tuya Projekt diese Status Notification enabled? Das muss unbedingt aktiv sein.
Zitat von: dominik am 29 August 2021, 20:32:32
@barneybaer, super! Danke für die Rückmeldung!
Hab ebend noch einmal rum getestet und festgestellt, dass man die Helligkeit nicht ändern kann. Es wird bei "bright_value_v2" immer auf "work_mode white" gestellt. Wenn die Helligkeit in der APP geändert wird, werden leider keine Readings geändert nur aktualisiert. Hängt das mit HSV zusammen?
Zitat von: barneybaer am 29 August 2021, 22:55:53
Hab ebend noch einmal rum getestet und festgestellt, dass man die Helligkeit nicht ändern kann. Es wird bei "bright_value_v2" immer auf "work_mode white" gestellt. Wenn die Helligkeit in der APP geändert wird, werden leider keine Readings geändert nur aktualisiert. Hängt das mit HSV zusammen?
ich habe das gleiche Problem.
Folgendes ist aktiviert:
Smart Home Devices Management
Autorization
Smart Home Family Management
Smart Home Szene Linkage
IOT Data Analytics
Device Status Notification
vor paar Tagen hat alles wunderbar funktioniert
Gleiche Problem mit Helligkeit oder Reading Aktualisierung?
hat sich erledigt, sorry, die komische Fehlermeldungen einige Posts weiter oben resultierte bei mir aufgrund falscher Uhrzeit / Datum am Raspi.
Nun funktioniert es wieder tadellos.
ZitatHast du im Tuya Projekt diese Status Notification enabled? Das muss unbedingt aktiv sein.
Bitte um Hilfe.
Wo finde ich diese Einstellung?
Hallo Dominik,
ZitatHast du im Tuya Projekt diese Status Notification enabled? Das muss unbedingt aktiv sein.
es lag an dieser Einstellung.
Jetzt werden die Readings beim Schalten aktualisiert.
Vielen Dank für deine Hinweise und Geduld.
Beste Grüße
Super :)
Für alle die es noch suchen sollten, hier muss man unbedingt Punkt 6 beachten:
https://github.com/tuya/tuya-home-assistant/wiki/Tuya-IoT-Platform-Configuration-Guide-Using-Smart-Home-PaaS
moin,
ich wollte mich heute mal mit einer anbindung der Tuya Cloud beschäftigen, habe allerdings schon beim update der entsprechenden Fhermmodule Probleme und möchte sie gerade nicht manuell einspielen.
da hat sich scheinbar in einer Grössenangabe der "controls_pythonbinding.txt" ein Fehler eingeschlichen.
update add https://raw.githubusercontent.com/dominikkarall/fhempy/master/controls_pythonbinding.txt
update
... bricht mit entsprechendem Hinweis ab ...
2021.09.08 06:16:41 1 : Downloading https://raw.githubusercontent.com/dominikkarall/fhempy/master/controls_pythonbinding.txt
2021.09.08 06:16:41 1 :
2021.09.08 06:16:41 1 : pythonbinding
2021.09.08 06:16:42 1 : UPD FHEM/10_BindingsIo.pm
2021.09.08 06:16:43 1 : Got 14451 bytes for FHEM/10_BindingsIo.pm, expected 14714
2021.09.08 06:16:43 1 : aborting.
2021-09-08 06:16:43 Global global UPDATE
gruss Thomas
Oops, ja! Danke für die Info!
Sollte jetzt wieder klappen.
Zitat von: dominik am 08 September 2021, 07:51:27
Oops, ja! Danke für die Info!
Sollte jetzt wieder klappen.
2021.09.08 06:52:25 1 : Downloading https://raw.githubusercontent.com/dominikkarall/fhempy/master/controls_pythonbinding.txt
2021.09.08 06:52:25 1 :
2021.09.08 06:52:25 1 : pythonbinding
2021.09.08 06:52:27 1 : UPD FHEM/10_PythonBinding.pm
2021.09.08 06:52:28 1 : UPD FHEM/10_PythonModule.pm
2021.09.08 06:52:28 1 : UPD FHEM/10_BindingsIo.pm
2021.09.08 06:52:28 1 : UPD FHEM/bindings/python/bin/fhempy
2021.09.08 06:52:28 1 : saving fhem.cfg
2021.09.08 06:52:28 1 :
2021.09.08 06:52:28 1 : New entries in the CHANGED file:
2021.09.08 06:52:28 1 : 2020-12-31: Further updates are done via pip
2021.09.08 06:52:28 1 : No need to change anything, everything is done for you :)
2021.09.08 06:52:28 1 : Happy New Year!
2021.09.08 06:52:28 1 : 2020-12-23: Save xiaomi_tokens credentials
2021.09.08 06:52:29 1 : Add ip address to xiaomi_tokens
2021.09.08 06:52:29 1 : Create miio/gateway3 device out of xiaomi_tokens
2021.09.08 06:52:29 1 : Add firmware version to xiaomi_gateway3
2021.09.08 06:52:29 1 : Fix icons in googlecast
2021.09.08 06:52:29 1 : Fix python version check
2021.09.08 06:52:29 1 : First version of gfprobt (irrigation control)
2021.09.08 06:52:29 1 : 2020-12-03: Remote peers: Please read new installation instructions https://github.com/dominikkarall/fhempy
2021.09.08 06:52:29 1 : 2020-10-19: Initial release of CHANGED file :)passt, Danke !
gruss Thomas
Tolle Arbeit, danke.
anbindung hat problemlos funktioniert .
gruss Thomas
Zitat@Supersoschi, die Commands für den Fan können nicht per API freigeschalten werden. Laut tuya hat sich der Hersteller nicht an die offizielle API gehalten und daher kann das nicht genutzt werden.
Das ist Schade, aber dann muss ich wohl oder Übel damit leben.
Der Ventilator und der Diffusor sind ja prinzipiell zwei verschiedene Geräte die nur durch zusammenstecken über die gleiche Stromquelle betrieben werden.
Warum sie in der SmartLift-App als ein Gerät angezeigt werden ist mir unklar. Darum mal die Frage ob es möglich wäre manuell ein zweites Device für einen Diffusor mit der gleichen IP zu erstellen und damit eventuell die Funktionen des Diffusors doch ansteuern zu können.
Ist etwas abstrakt gedacht, aber da ich nicht weiß wie die Tuya-Devices in Fhem erstellt und gesteuert werden (vor allem wie und wo die Auswahl des Gerätetyps festgelegt wird) dachte ich, ich frage einfach mal den Schöpfer des Moduls.
ich versuche gerade fhempy ans laufen zu bringen um mein Tuya einzubinden und scheitere leider.
Ich habe auf meinem PI zunaechst Python 3.7 installiert mit
Code: [Auswählen]
sudo apt install python3 python3-pip python3-dev libffi-dev libssl-dev libjpeg-dev zlib1g-dev autoconf build-essential libglib2.0-dev libdbus-1-dev bluez libbluetooth-dev
sowie ein
Code: [Auswählen]
sudo cpan Protocol::WebSocket
ausgefuehrt.
Dann in fhem mein updatefile erweitert
Code: [Auswählen]
update add https://raw.githubusercontent.com/dom...
und das update durrchgefuehrt
ein
Code: [Auswählen]
define local_pybinding BindingsIo Python
erzeugt zwar auch ein Pytonbinding_15733 der auch active ist,
aber leider bekomme ich nicht den "opened" status im neu definierten "local_pybinding"
fhempy_log meldet:
Unable to install package fhempy>=0.1.12: Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-install-9ja41_su/websockets/
Was kann ich tun? Danke fuer die Hilfe
Mach bitte mal ein manuelles Install
sudo -u fhem bash
pip3 install --upgrade fhempy
Poste dann den Output von pip3 bitte.
Hallo, ich habe hier ein Smart PIR sensor und er erkennt die Bewegung, aber von 10 Bewegungen kommt vielleicht mal eine state Änderung bei Fhem an.
Hier die Daten:
READINGS:
2021-09-17 17:14:41 active_time 1615490051
2021-09-17 17:14:44 battery_state middle
2021-09-17 17:14:41 biz_type 0
2021-09-17 17:14:41 category pir
2021-09-17 17:14:41 create_time 1604331696
2021-09-17 17:14:41 icon https://images.tuyaeu.com/smart/icon/ay1536023421083D2Q1d/156402198180ba176223b.jpg
2021-09-17 17:14:41 ip xx. xx. xx. xx
2021-09-17 17:14:41 local_key 95c510682117187e
2021-09-17 17:14:41 lon 13.0040561
2021-09-17 17:14:41 name Bewegungsmelder
2021-09-17 17:14:41 online on
2021-09-17 17:14:41 owner_id 7466747
2021-08-29 11:02:07 pir pir
2021-09-17 17:14:41 product_id wqz93nrdomectyoz
2021-09-17 17:14:41 product_name Smart PIR sensor
2021-09-17 17:17:44 state nomotion
2021-09-17 17:14:41 sub off
2021-09-17 17:14:41 time_zone +01:00
2021-09-17 17:14:41 uid eu1574577924220XZPD4
2021-09-17 17:14:41 update_time 1615490053
2021-09-17 17:14:41 uuid 20401777d8bfc0da957b
Kann es sein, dass die nicht erkannten Events innerhalb von 3 Minuten waren? Der Sensor selbst liefert nämlich kein nomotion, das setze ich nach 180s.
Zitat von: Superposchi am 13 September 2021, 08:33:58
Das ist Schade, aber dann muss ich wohl oder Übel damit leben.
Der Ventilator und der Diffusor sind ja prinzipiell zwei verschiedene Geräte die nur durch zusammenstecken über die gleiche Stromquelle betrieben werden.
Warum sie in der SmartLift-App als ein Gerät angezeigt werden ist mir unklar. Darum mal die Frage ob es möglich wäre manuell ein zweites Device für einen Diffusor mit der gleichen IP zu erstellen und damit eventuell die Funktionen des Diffusors doch ansteuern zu können.
Ist etwas abstrakt gedacht, aber da ich nicht weiß wie die Tuya-Devices in Fhem erstellt und gesteuert werden (vor allem wie und wo die Auswahl des Gerätetyps festgelegt wird) dachte ich, ich frage einfach mal den Schöpfer des Moduls.
Die Devices kommen direkt vom Tuya Server. Ob es 1 oder 2 Devices sind liegt nur an der Definition bei Tuya. Du könntest die 2 Devices mit einem Dummy oder so kombinieren.
Zitat von: dominik am 17 September 2021, 18:44:59
Kann es sein, dass die nicht erkannten Events innerhalb von 3 Minuten waren? Der Sensor selbst liefert nämlich kein nomotion, das setze ich nach 180s.
Wenn der state nomotion ist dann heißt doch für mich es ist keine Bewegung erkannt. Wieso wird nicht auf motion geschaltet? Wie setzte ich den zurück?
Sorry, habe mich oben vertippt. Ich setze Motion für 180s und danach, wenn kein neues Motion kommt, wird auf nomotion gesetzt. Es ist also sichergestellt, dass auf jede Motion reagiert wird.
Prüfe bitte, ob nach 5 Minuten der Sensor jedes Mal reagiert, weil der Sensor reagiert sicher auch nicht immer. Die meisten Sensoren reagieren 1x und warten dann 180s bevor sie wieder ein Signal senden wenn sich jemand bewegt.
Der Sensor reagiert genau alle 10 Sekunden, da leuchtet er auf. Wie setzte ich ihn auf Motion? Steh grad aufm Schlauch :)
Ok, wenn er alle 10s reagiert, sollte auch in FHEM das Reading bei Auslösung neu gesetzt werden (auf die Zeit schauen).
Wenn sich dann 180s nichts tut, setze ich auf nomotion.
Zitat von: dominik am 17 September 2021, 20:01:22
Ok, wenn er alle 10s reagiert, sollte auch in FHEM das Reading bei Auslösung neu gesetzt werden (auf die Zeit schauen).
Wenn sich dann 180s nichts tut, setze ich auf nomotion.
In Fhem bleibt es auch bei alles 10 Sekunden Bewegung auf nomotion.
Geht es auf motion wenn du 180s wartest und dann wieder auslöst?
Zitat von: dominik am 18 September 2021, 15:37:51
Geht es auf motion wenn du 180s wartest und dann wieder auslöst?
Ich glaub er hat sich mitnaweile eingefahren.
Wie meinst du das? Reagiert er jetzt richtig?
Zitat von: dominik am 18 September 2021, 20:18:57
Wie meinst du das? Reagiert er jetzt richtig?
Jap, er reagiert nun, wenn er auf nomotion steht und schaltet dann auf motion.
ZitatDie Devices kommen direkt vom Tuya Server. Ob es 1 oder 2 Devices sind liegt nur an der Definition bei Tuya. Du könntest die 2 Devices mit einem Dummy oder so kombinieren.
Das ist mir aktuell zu hoch, da ich noch kein Verständnis für die Tuya Geräte habe. Ich sehe nur was in der SmartLife-App angezeigt wird, da ist es ein Gerät.
In Fhem funktioniert es im Moment sowieso nicht. Es kommen zwar keine Fehlermeldungen beim ausführen von Set-Anweisungen oder notify's oder DOIF's etc. doch es ändert sich auch kein state oder Reading mehr. Anbei ein Listing:
Internals:
DEF tuya_cloud tuya_cloud_connector bf75378cf6e13718e0rvcj
DEVICEID bf75378cf6e13718e0rvcj
FUUID 611fbd2a-f33f-6c14-0202-490ffa51a4026dee
FVERSION 10_PythonModule.pm:0.182830/2019-01-16
IODev local_pybinding
NAME unit_sz_ventilator
NR 62
PYTHONTYPE tuya_cloud
STATE off
TYPE PythonModule
READINGS:
2021-09-13 20:32:58 active_time 1627922506
2021-09-13 20:32:58 biz_type 18
2021-09-13 20:32:58 category fs
2021-09-13 20:32:58 create_time 1627922506
2021-09-13 20:32:58 icon https://images.tuyaeu.com/smart/icon/bay1579257011827QOvk/05cb05801c69fa7b6bdacda9c7f21196.png
2021-09-13 20:32:58 id bf75378cf6e13718e0rvcj
2021-09-13 20:32:58 ip 88.152.251.43
2021-09-13 20:32:58 lat 51.0582495
2021-09-13 20:32:58 local_key 1982dec4e5f7c905
2021-09-13 20:32:58 lon 6.1029283
2021-09-13 07:45:56 mode normal
2021-09-13 20:32:58 name Ventilator
2021-09-13 20:32:58 online off
2021-09-13 09:12:28 oszillation on
2021-09-13 20:32:58 owner_id 23921647
2021-09-13 20:32:58 product_id 6awobc9jfnlwvqtw
2021-09-13 20:32:58 product_name ARC Humidifier
2021-09-22 05:43:12 state off
2021-09-13 20:32:58 sub off
2021-09-13 20:32:58 time_zone +02:00
2021-09-13 07:45:41 timer off
2021-09-13 20:32:58 uid eu1610479166063muAw8
2021-09-13 20:32:58 update_time 1631178387
2021-09-13 20:32:58 uuid fd0c8a9f78a36684
args:
unit_sz_ventilator
PythonModule
tuya_cloud
tuya_cloud_connector
bf75378cf6e13718e0rvcj
argsh:
Attributes:
alias Ventilator
devStateIcon on:ios-on-green off:ios-off
group Geräte
icon Ventilator_fett
room Wohnung->Schlafzimmer,fhempy
verbose 1Was muss ich denn tun um ein Tuya-Device selbst manuell anzulegen - könntest du den Vorgang eventuell mal beschreiben bitte.
Starte mal fhempy neu, dann klappt es wahrscheinlich wieder. Irgendwo in der tuya iot lib dürfte es da noch einen Fehler geben wodurch es manchmal vorkommt, dass sich die Readings nach einiger Zeit nicht mehr aktualisieren.
Schau mal auf der tuya iot platform ob dort das Device als 1 oder 2 Devices gelistet ist.
Menü: Cloud -> Development -> Projekt auswaehlen -> Devices
Solange es dort 2 Devices sind, bekommst du es in FHEM auch nicht als 1 Device zusammen. Zumindest nicht mit diesem Modul. Du kannst natürlich ein dummy bauen und DOIFs und somit 1 Device draus machen.
Manuelle Anlage des Devices bringt nichts. Du kannst kein Device erzwingen, es wird alles 1:1 aus der Tuya Cloud übernommen.
Ganz doffe Frage, wie starte ich Fhempy neu?
Auf der Webseite wird der Ventilator als ein Device geführt, allerdings steht dort offline bei Status, was wohl die Probleme beim Zugriff erklärt.
ZitatSolange es dort 2 Devices sind, bekommst du es in FHEM auch nicht als 1 Device zusammen.
Will ich ja gar nicht, es war nur ein Gedanke ob man die fehlenden Befehle in einem zweiten Device von einem anderen Typ findet, da Tuya ja zwischen Ventilatoren und Luftbefeuchtern unterschiedet.
Hast du eine Idee wie ich den Status wieder online bekomme?
Zitat von: dominik am 22 September 2021, 16:52:54
Starte mal fhempy neu, dann klappt es wahrscheinlich wieder. Irgendwo in der tuya iot lib dürfte es da noch einen Fehler geben wodurch es manchmal vorkommt, dass sich die Readings nach einiger Zeit nicht mehr aktualisieren.
Schau mal auf der tuya iot platform ob dort das Device als 1 oder 2 Devices gelistet ist.
Menü: Cloud -> Development -> Projekt auswaehlen -> Devices
Solange es dort 2 Devices sind, bekommst du es in FHEM auch nicht als 1 Device zusammen. Zumindest nicht mit diesem Modul. Du kannst natürlich ein dummy bauen und DOIFs und somit 1 Device draus machen.
Manuelle Anlage des Devices bringt nichts. Du kannst kein Device erzwingen, es wird alles 1:1 aus der Tuya Cloud übernommen.
Hallo, habe bei mir auch festgestellt, das sich die Readings nicht aktualisieren. Selbst beim Schalten von Dosen und einstellen von Werten, z.B.: Temperatur eines IR-Heizkörpers.
Erst nach einen Update von local_pybinding bzw. Stop und Start von Pythonbinding_15733 (für Roomba) gibt es es danach in neues Readingfeuerwerk. Wenn im Device das "attr IODev local_pybinding" gesetzt wird, werden ebenfalls die Readings erneuert. Aber das wäre für mich kein guter Plan, dass z.B. mit einem DOIF jedes Mal mit einem "set <Device> attr IODev local_pybinding" zu aktualisieren. Ob das nun auch Zufall ist, das es so funktioniert, kann ich nicht sagen. Dafür bin ich zu viel Laie. Was könnte das Problem sein? VG...
Punkte 6 in der Anleitung auch sicher befolgt
https://github.com/tuya/tuya-home-assistant/wiki/Tuya-IoT-Platform-Configuration-Guide-Using-Smart-Home-PaaS#create-a-project
?
Bitte das prüfen, ohne den, bekommt man keine Reading Updates.
Hat sich erledigt
Hi, wäre es möglich bei Tuya Bewegungsmelder statt motion und nomotion einfach true und false zu setzten. Das würde die Verbindung mit anderen nicht Tuya Bewegungsmelder vereinfachen.
Ist das so? Ich habe Xiaomi Bewegungsmelder bei mir, die liefern aber auch motion. Ich dachte das ist FHEM "Standard"?
Wie möchtest du die Melder verbinden?
Zitat von: dominik am 30 September 2021, 17:43:15
Ist das so? Ich habe Xiaomi Bewegungsmelder bei mir, die liefern aber auch motion. Ich dachte das ist FHEM "Standard"?
Wie möchtest du die Melder verbinden?
Also meine Xiaomi liefern als Reading das:
READINGS:
2021-09-27 21:05:25 IODev MQTT2_FHEM_Server
2021-09-30 19:07:18 battery 91
2021-09-30 19:07:18 elapsed 8
2021-09-30 19:07:18 illuminance 5
2021-09-30 19:07:18 illuminance_lux 5
2021-09-30 19:07:18 last_seen 2021-09-30T19:07:18+02:00
2021-09-30 19:07:18 linkquality 255
2021-09-30 19:07:18 occupancy true
2021-09-30 19:07:18 state true
2021-09-30 19:07:18 temperature 31
2021-09-30 19:07:18 voltage 2985
Attributes:
IODev MQTT2_FHEM_Server
devStateIcon false:people_sensor@red true:people_sensor@green
MQTT publish: topic 'zigbee2mqtt/Flur_Bewegung_1', payload '{"battery":100,"illuminance":20,"illuminance_lux":20,"last_seen":"2021-09-30T16:51:39.569Z","linkquality":68,"occupancy":false,"temperature":27,"voltage":3015}'
Das liegt eher ein zigbee2mqtt, mit dem Xiaomi Modul liefern die ebenfalls motion.
Laut Wiki liefern auch andere motion
https://wiki.fhem.de/wiki/HM-Sen-MDIR-O_Funk-IR-Bewegungsmelder_au%C3%9Fen
Du kannst sonst ein Userreading erstellen.
Zitat von: dominik am 30 September 2021, 20:33:48
Das liegt eher ein zigbee2mqtt, mit dem Xiaomi Modul liefern die ebenfalls motion.
Laut Wiki liefern auch andere motion
https://wiki.fhem.de/wiki/HM-Sen-MDIR-O_Funk-IR-Bewegungsmelder_au%C3%9Fen
Du kannst sonst ein Userreading erstellen.
Danke für die Info. Ich habe ein Userreadings erstellt.
ZitatIst das so? Ich habe Xiaomi Bewegungsmelder bei mir, die liefern aber auch motion. Ich dachte das ist FHEM "Standard"?
Also Homematic und Shelly liefern auch motion und nomation
Ich frage noch mal:
ZitatAuf der Webseite wird der Ventilator als ein Device geführt, allerdings steht dort offline bei Status, was wohl die Probleme beim Zugriff erklärt.
Hat jemand eine Idee?
Zitat von: link=topic=122288.msg1176666#msg1176666 date=1632756205
Punkte 6 in der Anleitung auch sicher befolgt
https://github.com/tuya/tuya-home-assistant/wiki/Tuya-IoT-Platform-Configuration-Guide-Using-Smart-Home-PaaS#create-a-project
?
Bitte das prüfen, ohne den, bekommt man keine Reading Updates.
Danke an dominik für die info, läuft. Readings kommen jetzt.
Ähmm.... dumme Frage, weiß eigentlich jemand was passiert wenn das Testjahr abgelaufen ist. VG
Zitat von: loosu am 02 Oktober 2021, 00:49:39
Danke an dominik für die info, läuft. Readings kommen jetzt.
Ähmm.... dumme Frage, weiß eigentlich jemand was passiert wenn das Testjahr abgelaufen ist. VG
Ja, laut Tuya muss man nur nach einem Jahr nochmals kostenlos verlängern.
Zitat von: Superposchi am 01 Oktober 2021, 08:26:53
Ich frage noch mal:Hat jemand eine Idee?
Auf der tuya iot Plattform Seite meinst du, wird er als ein Device geführt? Wenn ja, dann müsste er auch als ein Device ins Modul rein kommen. Offline oder nicht spielt keine Rolle, solange das Device in der Cloud ist, wird es auch im Tuya Modul ankommen.
Poste mal einen Screenshot vom Device in der tuya iot Plattform.
Zitat
Antw:Tuya - Smart Life: LED Lampen und Schalter
« Antwort #93 am: Heute um 15:40:49 »
Zitat
Bitte verwendet diesen Thread hier
https://forum.fhem.de/index.php/topic,122288.0.html
Der iobroker tuya Adapter geht nicht über die Cloud, das hat den Nachteil, dass man das Device immer pollen muss. Tuya_cloud (siehe Thread) geht über die offizielle tuya Library und unterstützt push, somit werden Änderungen in der Sekunde übertragen. Bitte weiteres nicht hier, sondern im verlinkten Thread.
Hallo Dominik,
ich hatte im März schon versucht , dies per fhempy hinzukriegen.
Bin aber immer wieder über "cannot load module Bindingslo" nicht hinweggekommen. Dabei habe ich deine Anleitung verwendet.
Was ist dein Rat, dass ich doch weiterkomme?
Herzliche Grüße und vielen Dank
Thomas Burkhart
Poste mal das Log von fhempy und FHEM, dann schau ich mir das an.
oh super :-)
du meinst das FHEM allgemeinen Log mit dem Teil des entsprechenden Fehlers?
Wo finde ich fhempy?
Ja genau + das fhempy Log, das findest du im gleichen Log Ordner von FHEM.
ok
das steht im FHEM Log:
2021.10.08 16:12:51 1 : Downloading https://raw.githubusercontent.com/dominikkarall/fhempy/master/controls_pythonbinding.txt
2021.10.08 16:12:51 1 :
2021.10.08 16:12:51 1 : pythonbinding
2021.10.08 16:12:52 1 : UPD FHEM/10_PythonModule.pm
2021.10.08 16:12:53 3 : Watchdog WDT_THOMAS_F2 triggered
2021.10.08 16:12:53 3 : TelegramBot_SendIt THB_WarnBot: Failed with :FAILED peer not found :@thburkhart::
2021.10.08 16:12:53 3 : TelegramBot_Callback THB_WarnBot: resulted in NonBlockingGet: returned FAILED peer not found :@thburkhart: from SendIt
2021.10.08 16:12:53 3 : FAILED peer not found :@thburkhart:
2021.10.08 16:12:53 1 : UPD FHEM/10_BindingsIo.pm
2021.10.08 16:13:00 1 : saving fhem.cfg
2021.10.08 16:13:00 1 : saving ./log/fhem2.save
2021.10.08 16:13:00 1 :
2021.10.08 16:13:00 1 : New entries in the CHANGED file:
2021.10.08 16:13:00 1 : 2020-12-31: Further updates are done via pip
2021.10.08 16:13:00 1 : No need to change anything, everything is done for you :)
2021.10.08 16:13:00 1 : Happy New Year!
2021.10.08 16:13:00 1 : 2020-12-23: Save xiaomi_tokens credentials
2021.10.08 16:13:00 1 : Add ip address to xiaomi_tokens
2021.10.08 16:13:00 1 : Create miio/gateway3 device out of xiaomi_tokens
2021.10.08 16:13:00 1 : Add firmware version to xiaomi_gateway3
2021.10.08 16:13:00 1 : Fix icons in googlecast
2021.10.08 16:13:00 1 : Fix python version check
2021.10.08 16:13:00 1 : First version of gfprobt (irrigation control)
2021.10.08 16:13:00 1 : 2020-12-03: Remote peers: Please read new installation instructions https://github.com/dominikkarall/fhempy
2021.10.08 16:13:00 1 : 2020-10-19: Initial release of CHANGED file :)
2021.10.08 16:13:00 1 : Calling /usr/bin/perl ./contrib/commandref_join.pl -noWarnings, this may take a while
2021.10.08 16:13:37 1 :
2021.10.08 16:13:37 1 : update finished, "shutdown restart" is needed to activate the changes.
im Ordner log gibt's bei mir nurFhem*.log und alexa*.log
Du hast jetzt nur ein Update gemacht oder? Du musst auch noch die weiteren Commands ausführen die in der Anleitung stehen.
ja Update ist gelaufen
ich mache mich dran
bin nicht weit gekommen:
FHEM
update add https://raw.githubusercontent.com/dominikkarall/fhempy/master/controls_pythonbinding.txt
update
define local_pybinding BindingsIo Python
letzteres wird wieder mit "Cannot load module BindingsIo" quittiert
fehlt da das Python?
das hatte ich mit
root@THB-PI3B1:~# sudo apt install python3 python3-pip python3-dev libffi-dev li bssl-dev libjpeg-dev zlib1g-dev autoconf build-essential libglib2.0-dev libdbus- 1-dev bluez libbluetooth-dev git
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
autoconf ist schon die neueste Version (2.69-11).
build-essential ist schon die neueste Version (12.6).
git ist schon die neueste Version (1:2.20.1-2+deb10u3).
libdbus-1-dev ist schon die neueste Version (1.12.20-0+deb10u1).
libffi-dev ist schon die neueste Version (3.2.1-9).
libglib2.0-dev ist schon die neueste Version (2.58.3-2+deb10u2).
libjpeg-dev ist schon die neueste Version (1:1.5.2-2+deb10u1).
python3 ist schon die neueste Version (3.7.3-1).
python3-dev ist schon die neueste Version (3.7.3-1).
zlib1g-dev ist schon die neueste Version (1:1.2.11.dfsg-1).
bluez ist schon die neueste Version (5.50-1.2~deb10u1+rpt2).
libbluetooth-dev ist schon die neueste Version (5.50-1.2~deb10u1+rpt2).
libssl-dev ist schon die neueste Version (1.1.1d-0+deb10u6+rpt1).
python3-pip ist schon die neueste Version (18.1-5+rpt1).
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 12 nicht aktualisiert.
installiert
nach dem Update finde ich FHEM-Log:
2021.10.08 18:16:03 1: reload: Error:Modul 10_BindingsIo deactivated:
Can't locate Protocol/WebSocket/Frame.pm in @INC (you may need to install the Protocol::WebSocket::Frame module) (@INC contains: ./lib ./FHEM . /etc/perl /usr/local/lib/arm-linux-gnueabihf/perl/5.28.1 /usr/local/share/perl/5.28.1 /usr/lib/arm-linux-gnueabihf/perl5/5.28 /usr/share/perl5 /usr/lib/arm-linux-gnueabihf/perl/5.28 /usr/share/perl/5.28 /usr/local/lib/site_perl /usr/lib/arm-linux-gnueabihf/perl-base ./FHEM/lib) at ./FHEM/10_BindingsIo.pm line 13.
BEGIN failed--compilation aborted at ./FHEM/10_BindingsIo.pm line 13.
2021.10.08 18:16:03 0: Can't locate Protocol/WebSocket/Frame.pm in @INC (you may need to install the Protocol::WebSocket::Frame module) (@INC contains: ./lib ./FHEM . /etc/perl /usr/local/lib/arm-linux-gnueabihf/perl/5.28.1 /usr/local/share/perl/5.28.1 /usr/lib/arm-linux-gnueabihf/perl5/5.28 /usr/share/perl5 /usr/lib/arm-linux-gnueabihf/perl/5.28 /usr/share/perl/5.28 /usr/local/lib/site_perl /usr/lib/arm-linux-gnueabihf/perl-base ./FHEM/lib) at ./FHEM/10_BindingsIo.pm line 13.
BEGIN failed--compilation aborted at ./FHEM/10_BindingsIo.pm line 13.
keine Ahnung, wie ich das beheben soll...
root@THB-PI3B1:~# sudo cpan Protocol::WebSocket
Loading internal logger. Log::Log4perl recommended for better logging
Reading '/root/.cpan/Metadata'
Database was generated on Mon, 24 May 2021 15:17:02 GMT
Fetching with LWP:
http://www.cpan.org/authors/01mailrc.txt.gz
Reading '/root/.cpan/sources/authors/01mailrc.txt.gz'
............................................................................DONE
Fetching with LWP:
http://www.cpan.org/modules/02packages.details.txt.gz
Reading '/root/.cpan/sources/modules/02packages.details.txt.gz'
Database was generated on Fri, 08 Oct 2021 16:29:02 GMT
............................................................................DONE
Fetching with LWP:
http://www.cpan.org/modules/03modlist.data.gz
Reading '/root/.cpan/sources/modules/03modlist.data.gz'
DONE
Writing /root/.cpan/Metadata
Running install for module 'Protocol::WebSocket'
Checksum for /root/.cpan/sources/authors/id/V/VT/VTI/Protocol-WebSocket-0.26.tar.gz ok
'YAML' not installed, will not store persistent state
Configuring V/VT/VTI/Protocol-WebSocket-0.26.tar.gz with Build.PL
Creating new 'Build' script for 'Protocol-WebSocket' version '0.26'
VTI/Protocol-WebSocket-0.26.tar.gz
/usr/bin/perl Build.PL --installdirs site -- OK
Running Build for V/VT/VTI/Protocol-WebSocket-0.26.tar.gz
cp lib/Protocol/WebSocket/Request.pm blib/lib/Protocol/WebSocket/Request.pm
cp lib/Protocol/WebSocket/Response.pm blib/lib/Protocol/WebSocket/Response.pm
cp lib/Protocol/WebSocket/Handshake/Server.pm blib/lib/Protocol/WebSocket/Handshake/Server.pm
cp lib/Protocol/WebSocket/URL.pm blib/lib/Protocol/WebSocket/URL.pm
cp lib/Protocol/WebSocket/Cookie/Request.pm blib/lib/Protocol/WebSocket/Cookie/Request.pm
cp lib/Protocol/WebSocket/Message.pm blib/lib/Protocol/WebSocket/Message.pm
cp lib/Protocol/WebSocket/Cookie.pm blib/lib/Protocol/WebSocket/Cookie.pm
cp lib/Protocol/WebSocket/Stateful.pm blib/lib/Protocol/WebSocket/Stateful.pm
cp lib/Protocol/WebSocket.pm blib/lib/Protocol/WebSocket.pm
cp lib/Protocol/WebSocket/Handshake/Client.pm blib/lib/Protocol/WebSocket/Handshake/Client.pm
cp lib/Protocol/WebSocket/Handshake.pm blib/lib/Protocol/WebSocket/Handshake.pm
cp lib/Protocol/WebSocket/Frame.pm blib/lib/Protocol/WebSocket/Frame.pm
cp lib/Protocol/WebSocket/Cookie/Response.pm blib/lib/Protocol/WebSocket/Cookie/Response.pm
cp lib/Protocol/WebSocket/Client.pm blib/lib/Protocol/WebSocket/Client.pm
VTI/Protocol-WebSocket-0.26.tar.gz
./Build -- OK
Running Build test for VTI/Protocol-WebSocket-0.26.tar.gz
t/client.t ........................... ok
t/cookie.t ........................... ok
t/draft-hixie-75/request.t ........... ok
t/draft-hixie-75/response.t .......... ok
t/draft-ietf-hybi-00/client-ssl.t .... ok
t/draft-ietf-hybi-00/client.t ........ ok
t/draft-ietf-hybi-00/frame.t ......... ok
t/draft-ietf-hybi-00/request.t ....... ok
t/draft-ietf-hybi-00/response.t ...... ok
t/draft-ietf-hybi-00/server-ssl.t .... ok
t/draft-ietf-hybi-00/server.t ........ ok
t/draft-ietf-hybi-10/client.t ........ ok
t/draft-ietf-hybi-10/request.t ....... ok
t/draft-ietf-hybi-10/response.t ...... ok
t/draft-ietf-hybi-10/server.t ........ ok
t/draft-ietf-hybi-17/client.t ........ ok
t/draft-ietf-hybi-17/frame.t ......... ok
t/draft-ietf-hybi-17/request.t ....... ok
t/draft-ietf-hybi-17/request_psgi.t .. ok
t/draft-ietf-hybi-17/response.t ...... ok
t/draft-ietf-hybi-17/server.t ........ ok
t/frame.t ............................ Name "Protocol::WebSocket::Frame::MAX_FRAGMENTS_AMOUNT" used only once: possible typo at t/frame.t line 85.
t/frame.t ............................ ok
t/message.t .......................... ok
t/request_common.t ................... Name "Protocol::WebSocket::Message::MAX_MESSAGE_SIZE" used only once: possible typo at t/request_common.t line 26.
t/request_common.t ................... ok
t/response_common.t .................. Name "Protocol::WebSocket::Message::MAX_MESSAGE_SIZE" used only once: possible typo at t/response_common.t line 22.
t/response_common.t .................. ok
t/rsv.t .............................. ok
t/url.t .............................. ok
All tests successful.
Files=27, Tests=685, 10 wallclock secs ( 0.56 usr 0.11 sys + 8.22 cusr 0.73 csys = 9.62 CPU)
Result: PASS
VTI/Protocol-WebSocket-0.26.tar.gz
./Build test -- OK
Running Build install for VTI/Protocol-WebSocket-0.26.tar.gz
Installing /usr/local/share/perl/5.28.1/Protocol/WebSocket.pm
Installing /usr/local/share/perl/5.28.1/Protocol/WebSocket/URL.pm
Installing /usr/local/share/perl/5.28.1/Protocol/WebSocket/Message.pm
Installing /usr/local/share/perl/5.28.1/Protocol/WebSocket/Cookie.pm
Installing /usr/local/share/perl/5.28.1/Protocol/WebSocket/Frame.pm
Installing /usr/local/share/perl/5.28.1/Protocol/WebSocket/Handshake.pm
Installing /usr/local/share/perl/5.28.1/Protocol/WebSocket/Response.pm
Installing /usr/local/share/perl/5.28.1/Protocol/WebSocket/Client.pm
Installing /usr/local/share/perl/5.28.1/Protocol/WebSocket/Stateful.pm
Installing /usr/local/share/perl/5.28.1/Protocol/WebSocket/Request.pm
Installing /usr/local/share/perl/5.28.1/Protocol/WebSocket/Cookie/Response.pm
Installing /usr/local/share/perl/5.28.1/Protocol/WebSocket/Cookie/Request.pm
Installing /usr/local/share/perl/5.28.1/Protocol/WebSocket/Handshake/Server.pm
Installing /usr/local/share/perl/5.28.1/Protocol/WebSocket/Handshake/Client.pm
Installing /usr/local/man/man3/Protocol::WebSocket::Cookie::Response.3pm
Installing /usr/local/man/man3/Protocol::WebSocket::URL.3pm
Installing /usr/local/man/man3/Protocol::WebSocket::Message.3pm
Installing /usr/local/man/man3/Protocol::WebSocket::Response.3pm
Installing /usr/local/man/man3/Protocol::WebSocket::Stateful.3pm
Installing /usr/local/man/man3/Protocol::WebSocket::Request.3pm
Installing /usr/local/man/man3/Protocol::WebSocket::Cookie::Request.3pm
Installing /usr/local/man/man3/Protocol::WebSocket::Frame.3pm
Installing /usr/local/man/man3/Protocol::WebSocket::Cookie.3pm
Installing /usr/local/man/man3/Protocol::WebSocket::Client.3pm
Installing /usr/local/man/man3/Protocol::WebSocket::Handshake.3pm
Installing /usr/local/man/man3/Protocol::WebSocket::Handshake::Client.3pm
Installing /usr/local/man/man3/Protocol::WebSocket::Handshake::Server.3pm
Installing /usr/local/man/man3/Protocol::WebSocket.3pm
VTI/Protocol-WebSocket-0.26.tar.gz
./Build install -- OK
Hilfe !
Hmmm...schau Mal ob 10_BindingsIo.pm im FHEM Verzeichnis liegt.
Aus irgendeinem Grund wird das nicht heruntergeladen!?
ja das liegt dort vom 28.9.2021 5 kB groß
define local_pybinding BindingsIo Python
liefert nun "local_pybinding already defined, delete it first"
jedoch :
DeviceOverview
tuya_system
???
Internals
DEF
tuya xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
FUUID
608f0930-f33f-21fb-9ec2-59dc29258e55e0dd
NAME
tuya_system
NR
1531
PYTHONTYPE
tuya
STATE
???
TYPE
PythonModule
Ok, vorher war scheinbar Websocket nicht installiert.
Mach jetzt bitte nochmals ein define und poste das Log.
local_pybinding already defined, delete it first
DeviceOverview
tuya_system
???
Internals
DEF
tuya qxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
FUUID
608f0930-f33f-21fb-9ec2-59dc29258e55e0dd
NAME
tuya_system
NR
1531
PYTHONTYPE
tuya
STATE
???
TYPE
PythonModule
Schritt für Schritt bitte...
Wenn local_pybinding already defined, dann prüfe nun bitte, ob local_pybinding auf "opened" steht.
Bitte in deinem Post auch das DEF löschen, da dort deine Zugangsdaten enthalten sind.
ok gemacht
local_pybinding steht auf opened
Ok, das ist schon mal gut. Dann mach jetzt bitte so wie es im Readme steht (https://github.com/dominikkarall/fhempy/blob/master/FHEM/bindings/python/fhempy/lib/tuya_cloud/README.md):
define tuya_cloud_connector PythonModule tuya_cloud setup CLIENT_ID CLIENT_SECRET USERNAME PASSWORD
jetzt hat sich FHEM erst mal aufgehängt
als ich local_pybinding
angeklickt hatte
der PI ist wohl abgestürzt
Was steht im Log?
Das sieht alles gut aus.
Was steht jetzt bei tuya_system? Und bitte verwende tuya_cloud NICHT tuya. Siehe mein define von vorher.
ok
define tuya_cloud_connector PythonModule tuya_cloud setup CLIENT_ID CLIENT_SECRET USERNAME PASSWORD
was ist dabei
CLIENT_ID CLIENT_SECRET ?
USERNAME ?
PASSWORD ?
sind das die zugangsdaten aus der TuyaCloud?
das waren aber nur 2 Werte
aktuell:
Cloud Application Authorization Key
To better secure your cloud development, Tuya will upgrade the signature algorithm. Projects created after June 30, 2021 are subject to signature verification with the new algorithm. View details
Access ID/Client ID: xxxxxxxxxxxxxxxxxx
Access Secret/Client Secret: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
yepp
habs einfach mit den letzten beiden Werten versucht:
tuya_cloud_connector ready
:) :) :)
in der Cloud habe ich 94 geräte
wie kommen die nun runter ?
soll ich die def tuya_system löschen ?
bin schon mal sehr happy, dank deiner Hilfe soweit gekommen zu sein :) :)
Hi,
die Devices werden automatisch angelegt. Schau Mal ob es neue bei dir gibt.
PS: danke dir für die Spende!
nein sehe nichts
was ist der Unterschied tuya_cloud zu tuya_system ?
meine Config sieht nun so aus:
## TUYA Cloud ####################################################################################
define tuya_cloud_connector PythonModule tuya_cloud setup xxxxxxxxxxxxxx xxxxxxxxxxxxxxxxx xxx@gmx.net xxxxxxx smartlife Europe
setuuid tuya_cloud_connector 6160933e-f33f-21fb-4a78-6f28e312ea5b9f44
attr tuya_cloud_connector room TUYA
################################################################################################
# TUYAFHEM
# Integration in FHEM
# Project Type: Smart HomeIndustry: Smart HomeCreate Time : 2021-05-02 21:30:63
#
# define tuya_system PythonModule tuya setup CLIENT_ID CLIENT_SECRET DEVICE_ID
# CLIENT_ID: From tuya developer portal
# CLIENT_SECRET: From tuya developer portal
# DEVICE_ID: From SmartLife app, doesn't matter which device, we just need one to retrieve the proper uid from it
# ID aus App Heizdecke 4530056170039f4a87e5
# ID aus App Leselampe1 03132278b4e62d74ab52
define tuya_system PythonModule tuya xxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxx 03132278b4e62d74ab52
attr tuya_system room TUYA
# set tuya_system start_scan
# The scan might take some minutes to finish, please wait and take a coffee.
####################################################################################################################
in der Tuya IO Platform steht bei mir:
API Name
Smart Home Devices Management View Details DebugRevoke Authorization
Smart Home Family Management View Details DebugRevoke Authorization
Smart Home Scene Linkage View Details DebugRevoke Authorization
IoT Data Analytics View Details DebugRevoke Authorization
Device Status Notification
es fehlt also "Autorisation"; das war im Auswahlfeld nicht mehr auswählbar
Hingegen sehe ich die Devices:
Device Name
Device ID
Product
Association
Online Status
Activation Time
Operation
Haustüre 60381718500291bade80 复制-门磁--新 bkt@gmx.net Online 2020-04-28 17:32:05 Debug Device
Wassermelder 180025363c6105dcdcaf 水浸传感器 1.0.4版本 可选音乐版本 bkt@gmx.net Online 2021-07-09 19:28:06 Debug Device
Wasserpumpe 03132278b4e62d74b293 SMART SOCKET bkt@gmx.net Online 2021-05-20 21:28:52 Debug Device
SP13 THOMAS Süd2 Schreibtisch 52470320e09806c9a53f SP1-C Smart Socket-16A bkt@gmx.net Online 2020-07-01 14:15:52 Debug Device
SP14 PETRA SüdOst 00673231e09806cb6fa5 SP1-C Smart Socket-16A bkt@gmx.net Online 2020-07-01 14:21:51 Debug Device
Bad 2 07412404cc50e3746c29 WIFI Switch module E3S bkt@gmx.net Online 2020-07-29 08:42:27 Debug Device
SP11 THOMAS Ost 62066151d8f15bb08810 SP1-C Smart Socket-16A bkt@gmx.net Online 2020-06-24 12:40:53 Debug Device
PS3 - Wohnen 1
wo klemmt es wohl?
Poste Mal das fhempy Log nach einem Restart
Zitat von: dominik am 09 Oktober 2021, 12:08:31
Poste Mal das fhempy Log nach einem Restart
2021-10-09 08:57:51,113 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-09 08:57:51,139 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-09 08:58:04,523 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-09 09:07:03,321 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-09 09:07:03,348 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-09 09:07:17,934 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-09 09:10:52,188 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-09 09:10:52,212 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-09 09:11:05,907 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-09 09:42:22,046 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-09 09:42:22,071 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-09 09:42:37,062 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-09 11:37:07,382 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-09 11:37:07,406 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-09 11:37:23,113 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-09 12:07:19,516 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-09 12:07:19,540 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-09 12:07:35,964 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
Mach Mal den tuya connector auf verbose 5 und starte dann nochmals neu.
Zitat von: dominik am 09 Oktober 2021, 12:20:41
Mach Mal den tuya connector auf verbose 5 und starte dann nochmals neu.
gemacht..
im Log nicht betreffendes
PythonModule
tuya_cloud_connector ready
tuya_system PythonBinding offline
Device:
DeviceOverview
tuya_cloud_connector
ready
tuya_cloud_connector
scan_devices
Internals
API_KEY
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
API_SECRET
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
DEF
tuya_cloud setup x x x@gmx.net x smartlife Europe
DEVICEID
0
FUUID
6160933e-f33f-21fb-4a78-6f28e312ea5b9f44
IODev
local_pybinding
NAME
tuya_cloud_connector
NR
1543
PYTHONTYPE
tuya_cloud
REGION
eu
STATE
ready
TYPE
PythonModule
Readings
state
ready
2021-10-09 12:29:07Device ID 0?!
nach shutdown PI3 und FHEM
nun id der log :
2021-10-09 12:28:52,560 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-09 12:29:06,265 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-09 12:39:53,549 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-09 12:39:55,352 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-09 12:39:57,422 - WARNING - asyncio: Executing <Task pending coro=<_wrap_awaitable() running at /usr/lib/python3.7/asyncio/tasks.py:603> wait_for=<_GatheringFuture pending cb=[<TaskWakeupMethWrapper object at 0x75bcc970>()] created at /usr/lib/python3.7/asyncio/tasks.py:615> cb=[_run_until_complete_cb() at /usr/lib/python3.7/asyncio/base_events.py:158] created at /usr/lib/python3.7/asyncio/tasks.py:590> took 0.139 seconds
2021-10-09 12:40:35,317 - WARNING - asyncio: Executing <Handle BaseSelectorEventLoop._accept_connection(functools.par...protocol=None), <socket.socke....0.0', 15733)>, None, <Server socke....0', 15733)>]>, 100, None) created at /usr/lib/python3.7/asyncio/selector_events.py:249> took 12.430 seconds
2021-10-09 12:40:35,595 - WARNING - asyncio: Executing <Task pending coro=<BaseSelectorEventLoop._accept_connection2() running at /usr/lib/python3.7/asyncio/selector_events.py:210> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x75c70b50>()] created at /usr/lib/python3.7/asyncio/base_events.py:396> created at /usr/lib/python3.7/asyncio/selector_events.py:188> took 0.276 seconds
2021-10-09 12:40:36,516 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-09 12:40:36,639 - WARNING - asyncio: Executing <Handle <TaskWakeupMethWrapper object at 0x75bccab0>(<Future finis...events.py:396>) created at /usr/lib/python3.7/asyncio/streams.py:408> took 0.153 seconds
2021-10-09 12:40:37,501 - WARNING - asyncio: Executing <Task pending coro=<PyBinding.onMessage() running at /usr/local/lib/python3.7/dist-packages/fhempy/lib/fhem_pythonbinding.py:128> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at /usr/lib/python3.7/asyncio/futures.py:348, <TaskWakeupMethWrapper object at 0x75ae1dd0>()] created at /usr/lib/python3.7/asyncio/base_events.py:396> created at /usr/lib/python3.7/asyncio/tasks.py:325> took 0.141 seconds
2021-10-09 12:40:49,105 - WARNING - asyncio: Executing <Task pending coro=<tuya.Define() running at /usr/local/lib/python3.7/dist-packages/fhempy/lib/tuya/tuya.py:26> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x752c2ed0>()] created at /usr/lib/python3.7/asyncio/base_events.py:396> cb=[_release_waiter(<Future pendi...events.py:396>)() at /usr/lib/python3.7/asyncio/tasks.py:366] created at /usr/lib/python3.7/asyncio/tasks.py:403> took 7.656 seconds
2021-10-09 12:40:49,700 - WARNING - asyncio: Executing <Task pending coro=<tuya_cloud.Define() running at /usr/local/lib/python3.7/dist-packages/fhempy/lib/tuya_cloud/tuya_cloud.py:26> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x75ae1c70>()] created at /usr/lib/python3.7/asyncio/base_events.py:396> cb=[_release_waiter(<Future pendi...events.py:396>)() at /usr/lib/python3.7/asyncio/tasks.py:366] created at /usr/lib/python3.7/asyncio/tasks.py:403> took 0.589 seconds
2021-10-09 12:41:04,123 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: setDevAttrList('tuya_system', ' IODev '.$readingFnAttributes)
2021-10-09 12:41:04,705 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: setDevAttrList('tuya_cloud_connector', ' IODev '.$readingFnAttributes)
2021-10-09 12:41:19,556 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"awaitId":94776961,"error":0,"result":" IODev event-aggregator event-min-interval event-on-change-reading event-on-update-reading oldreadings stateFormat:textField-long timestamp-on-change-reading"}
2021-10-09 12:41:19,561 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"result":" IODev event-aggregator event-min-interval event-on-change-reading event-on-update-reading oldreadings stateFormat:textField-long timestamp-on-change-reading","error":0,"awaitId":82279295}
oder dauert das Einlesen von 94 Devices etwas länger ;)
tuya_cloud_connector steht auf offline..
Ok, bitte Neustart machen, dann
1. Prüfen ob local pybinding= opened
2. Prüfen ob tuya_cloud_connector= ready
3. Log prüfen
Wenn eines davon nicht passt, dann bitte das Log posten und schreiben was nicht erfüllt wurde.
Zitat von: dominik am 09 Oktober 2021, 13:07:57
Ok, bitte Neustart machen, dann
1. Prüfen ob local pybinding= opened
2. Prüfen ob tuya_cloud_connector= ready
3. Log prüfen
Wenn eines davon nicht passt, dann bitte das Log posten und schreiben was nicht erfüllt wurde.
1. ok
2. ok
3. ok
wo sollten denn die readings auftauchen ?
Die Devices werden dann automatisch in FHEM angelegt. Wenn das noch nicht der Fall war, dann poste jetzt bitte nochmals fhem und fhempy Log.
Zitat von: dominik am 09 Oktober 2021, 13:35:44
Die Devices werden dann automatisch in FHEM angelegt. Wenn das noch nicht der Fall war, dann poste jetzt bitte nochmals fhem und fhempy Log.
FHEM:
2021.10.09 13:51:21 3: BindingsIo v1.0.0
2021.10.09 13:51:21 3: PythonBinding v1.0.0
2021.10.09 13:51:21 3: defmod -temporary fhempy_log FileLog ./log/fhempy-%Y-%m-%d.log fakelog : Define -temporary first
2021.10.09 13:51:21 3: PythonModule v1.0.0 (tuya_cloud)
2021.10.09 13:51:21 3: PythonModule v1.0.0 (tuya)FHEMPY:
2021-10-09 12:57:13,035 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-09 12:57:13,062 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-09 12:57:26,960 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-09 13:29:50,465 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-09 13:29:50,489 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-09 13:30:04,097 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
stört vlt. das tuya_system ?
tuya_cloud Connect geht immer wieder offline :(
soll ich dir mal per PN meine TuyaCload zugangsdaten geben?
weiterer restart von FHEM führte zu
tuya_cloud_connector
failed to connect
kein Eintrag im FHEM-Log
und nun im fhempy-Log
2021-10-09 08:57:51,113 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-09 08:57:51,139 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-09 08:58:04,523 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-09 09:07:03,321 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-09 09:07:03,348 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-09 09:07:17,934 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-09 09:10:52,188 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-09 09:10:52,212 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-09 09:11:05,907 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-09 09:42:22,046 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-09 09:42:22,071 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-09 09:42:37,062 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-09 11:37:07,382 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-09 11:37:07,406 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-09 11:37:23,113 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-09 12:07:19,516 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-09 12:07:19,540 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-09 12:07:35,964 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-09 12:28:52,535 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-09 12:28:52,560 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-09 12:29:06,265 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-09 12:39:53,549 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-09 12:39:55,352 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-09 12:39:57,422 - WARNING - asyncio: Executing <Task pending coro=<_wrap_awaitable() running at /usr/lib/python3.7/asyncio/tasks.py:603> wait_for=<_GatheringFuture pending cb=[<TaskWakeupMethWrapper object at 0x75bcc970>()] created at /usr/lib/python3.7/asyncio/tasks.py:615> cb=[_run_until_complete_cb() at /usr/lib/python3.7/asyncio/base_events.py:158] created at /usr/lib/python3.7/asyncio/tasks.py:590> took 0.139 seconds
2021-10-09 12:40:35,317 - WARNING - asyncio: Executing <Handle BaseSelectorEventLoop._accept_connection(functools.par...protocol=None), <socket.socke....0.0', 15733)>, None, <Server socke....0', 15733)>]>, 100, None) created at /usr/lib/python3.7/asyncio/selector_events.py:249> took 12.430 seconds
2021-10-09 12:40:35,595 - WARNING - asyncio: Executing <Task pending coro=<BaseSelectorEventLoop._accept_connection2() running at /usr/lib/python3.7/asyncio/selector_events.py:210> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x75c70b50>()] created at /usr/lib/python3.7/asyncio/base_events.py:396> created at /usr/lib/python3.7/asyncio/selector_events.py:188> took 0.276 seconds
2021-10-09 12:40:36,516 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-09 12:40:36,639 - WARNING - asyncio: Executing <Handle <TaskWakeupMethWrapper object at 0x75bccab0>(<Future finis...events.py:396>) created at /usr/lib/python3.7/asyncio/streams.py:408> took 0.153 seconds
2021-10-09 12:40:37,501 - WARNING - asyncio: Executing <Task pending coro=<PyBinding.onMessage() running at /usr/local/lib/python3.7/dist-packages/fhempy/lib/fhem_pythonbinding.py:128> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at /usr/lib/python3.7/asyncio/futures.py:348, <TaskWakeupMethWrapper object at 0x75ae1dd0>()] created at /usr/lib/python3.7/asyncio/base_events.py:396> created at /usr/lib/python3.7/asyncio/tasks.py:325> took 0.141 seconds
2021-10-09 12:40:49,105 - WARNING - asyncio: Executing <Task pending coro=<tuya.Define() running at /usr/local/lib/python3.7/dist-packages/fhempy/lib/tuya/tuya.py:26> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x752c2ed0>()] created at /usr/lib/python3.7/asyncio/base_events.py:396> cb=[_release_waiter(<Future pendi...events.py:396>)() at /usr/lib/python3.7/asyncio/tasks.py:366] created at /usr/lib/python3.7/asyncio/tasks.py:403> took 7.656 seconds
2021-10-09 12:40:49,700 - WARNING - asyncio: Executing <Task pending coro=<tuya_cloud.Define() running at /usr/local/lib/python3.7/dist-packages/fhempy/lib/tuya_cloud/tuya_cloud.py:26> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x75ae1c70>()] created at /usr/lib/python3.7/asyncio/base_events.py:396> cb=[_release_waiter(<Future pendi...events.py:396>)() at /usr/lib/python3.7/asyncio/tasks.py:366] created at /usr/lib/python3.7/asyncio/tasks.py:403> took 0.589 seconds
2021-10-09 12:41:04,123 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: setDevAttrList('tuya_system', ' IODev '.$readingFnAttributes)
2021-10-09 12:41:04,705 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: setDevAttrList('tuya_cloud_connector', ' IODev '.$readingFnAttributes)
2021-10-09 12:41:19,556 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"awaitId":94776961,"error":0,"result":" IODev event-aggregator event-min-interval event-on-change-reading event-on-update-reading oldreadings stateFormat:textField-long timestamp-on-change-reading"}
2021-10-09 12:41:19,561 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"result":" IODev event-aggregator event-min-interval event-on-change-reading event-on-update-reading oldreadings stateFormat:textField-long timestamp-on-change-reading","error":0,"awaitId":82279295}
2021-10-09 12:57:13,035 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-09 12:57:13,062 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-09 12:57:26,960 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-09 13:29:50,465 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-09 13:29:50,489 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-09 13:30:04,097 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-09 13:40:15,086 - INFO - fhempy.lib.pkg_installer: Attempting install of fhempy
2021-10-09 13:40:16,111 - WARNING - asyncio: Executing <Handle <TaskWakeupMethWrapper object at 0x71d609f0>(<Future finis...events.py:396>) created at /usr/lib/python3.7/asyncio/tasks.py:368> took 1.027 seconds
2021-10-09 13:42:40,687 - WARNING - asyncio: Executing <Handle _chain_future.<locals>._set_state(<Future finis...events.py:396>, <Future at 0x...returned bool>) at /usr/lib/python3.7/asyncio/futures.py:342 created at /usr/lib/python3.7/asyncio/futures.py:362> took 0.989 seconds
2021-10-09 13:42:41,312 - WARNING - asyncio: Executing <Handle _SelectorSocketTransport._read_ready() created at /usr/lib/python3.7/asyncio/selector_events.py:249> took 0.595 seconds
2021-10-09 13:42:41,450 - ERROR - asyncio: Task exception was never retrieved
future: <Task finished coro=<PyBinding.onMessage() done, defined at /usr/local/lib/python3.7/dist-packages/fhempy/lib/fhem_pythonbinding.py:126> exception=SystemExit(1) created at /usr/lib/python3.7/asyncio/tasks.py:325>
source_traceback: Object created at (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/usr/local/lib/python3.7/dist-packages/fhempy/lib/fhem_pythonbinding.py", line 471, in run
asyncio.get_event_loop().run_forever()
File "/usr/lib/python3.7/asyncio/base_events.py", line 539, in run_forever
self._run_once()
File "/usr/lib/python3.7/asyncio/base_events.py", line 1767, in _run_once
handle._run()
File "/usr/lib/python3.7/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/local/lib/python3.7/dist-packages/websockets/legacy/server.py", line 293, in handler
await self.ws_handler(self, path)
File "/usr/local/lib/python3.7/dist-packages/fhempy/lib/fhem_pythonbinding.py", line 67, in pybinding
asyncio.create_task(pb.onMessage(message))
File "/usr/lib/python3.7/asyncio/tasks.py", line 325, in create_task
return loop.create_task(coro)
Traceback (most recent call last):
File "/usr/local/lib/python3.7/dist-packages/fhempy/lib/fhem_pythonbinding.py", line 128, in onMessage
await self._onMessage(payload)
File "/usr/local/lib/python3.7/dist-packages/fhempy/lib/fhem_pythonbinding.py", line 391, in _onMessage
raise se
File "/usr/local/lib/python3.7/dist-packages/fhempy/lib/fhem_pythonbinding.py", line 170, in _onMessage
sys.exit(1)
SystemExit: 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.7/asyncio/base_events.py", line 539, in run_forever
self._run_once()
File "/usr/lib/python3.7/asyncio/base_events.py", line 1767, in _run_once
handle._run()
File "/usr/lib/python3.7/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/local/lib/python3.7/dist-packages/fhempy/lib/fhem_pythonbinding.py", line 130, in onMessage
sys.exit(1)
SystemExit: 1
2021-10-09 13:42:49,945 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-09 13:42:49,977 - INFO - fhempy.lib.pkg_installer: Attempting install of async-upnp-client==0.20.0
2021-10-09 13:43:05,838 - INFO - fhempy.lib.pkg_installer: Successfully installed async-upnp-client==0.20.0 update!
2021-10-09 13:43:05,841 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-09 13:43:33,643 - WARNING - asyncio: Executing <Handle <TaskWakeupMethWrapper object at 0x75b18990>(<Future finis...events.py:396>) created at /usr/lib/python3.7/asyncio/futures.py:323> took 27.802 seconds
2021-10-09 13:43:33,645 - INFO - websockets.server: server listening on 0.0.0.0:15733
2021-10-09 13:43:35,478 - INFO - websockets.server: connection open
2021-10-09 13:43:35,483 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-09 13:43:36,328 - WARNING - asyncio: Executing <Task pending coro=<_ServiceBrowserBase._async_start_query_sender() running at /opt/fhem/.local/lib/python3.7/site-packages/zeroconf/_services/browser.py:450> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x750875f0>()] created at /usr/lib/python3.7/asyncio/base_events.py:396> created at /opt/fhem/.local/lib/python3.7/site-packages/zeroconf/_services/browser.py:322> took 0.815 seconds
2021-10-09 13:43:36,413 - INFO - fhempy.lib.pkg_installer: Attempting install of tuya-iot-py-sdk==0.4.1
2021-10-09 13:43:53,594 - INFO - fhempy.lib.pkg_installer: Successfully installed tuya-iot-py-sdk==0.4.1 update!
2021-10-09 13:43:57,259 - ERROR - tuya_cloud_connector: Tuya login error response: {'code': 2406, 'msg': 'skill id invalid', 'success': False, 't': 1633779837241}
2021-10-09 14:01:01,364 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-09 14:01:01,384 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-09 14:01:01,456 - INFO - websockets.server: server listening on 0.0.0.0:15733
2021-10-09 14:01:16,736 - INFO - websockets.server: connection open
2021-10-09 14:01:16,738 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-09 14:01:18,611 - ERROR - tuya_cloud_connector: Tuya login error response: {'code': 2406, 'msg': 'skill id invalid', 'success': False, 't': 1633780878594}
Ja, bitte schick Mal eine PN mit den Daten aus dem define. Ich probier es dann heute Abend bei mir.
Ich habe es gerade mit deinen Credentials getestet. So wie es aussieht, ist dein tuya Projekt schon älter. Erstell bitte ein neues Projekt, es muss nach ca. Mai/2021 angelegt sein, alles davor liefert einen Fehler.
Bitte erstell ein neues Projekt und teste es nochmals. Ich bin gespannt wie es mit 96 Devices geht. Laut tuya ist der Trial Account auf 50 Devices beschränkt. Aber lass es uns mal probieren :) Notfalls musst du 2 tuya Accounts anlegen.
@dominoc
Dumme Frage, wie komme ich noch mal an die Tuya Platform ran?
iot.tuya.com ;)
Mist
tuya lässt mich nicht mehr rein
Mein Passwort entspricht wohl nicht mehr den Kriterien, wie ich beim Anlgen eines Zweiten Accounts bemerkte
Dominik, kommst du noch drauf?
Wo lässt dich tuya nicht mehr rein? iot.tuya.com ist dein Tuya Developer Account, nicht SmartLife! Der Account mit dem du die Client ID / Secret geholt hast.
Zitat von: dominik am 09 Oktober 2021, 19:39:55
Wo lässt dich tuya nicht mehr rein? iot.tuya.com ist dein Tuya Developer Account, nicht SmartLife! Der Account mit dem du die Client ID / Secret geholt hast.
ja auf iot.tuya.com komme ich nicht mehr rein "wrong password" ; kann ja auch temporär sein ;-)
oder nudelt da das FHEM ständig rum ...
Mit "Forgot Password" bekommst du auch keinen Reset Link?
Zitat von: dominik am 09 Oktober 2021, 19:58:04
Mit "Forgot Password" bekommst du auch keinen Reset Link?
ja leider
2021-10-09 20:00:13,976 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-09 20:00:17,269 - ERROR - tuya_cloud_connector: Tuya login error response: {'code': 2406, 'msg': 'skill id invalid', 'success': False, 't': 1633802417194}
sagt fhempi
Achtung, wir reden hier von unterschiedlichen Logins.
"skill id invalid" bedeutet, dass das Projekt zu alt ist, der Login (mit ClientID/Secret) hat aber funktioniert.
Du musst auf https://auth.tuya.com/?from=https%3A%2F%2Fiot.tuya.com%2F gehen, dort den Tuya Developer Account nutzen und ein neues Projekt anlegen.
Zitat von: dominik am 09 Oktober 2021, 20:11:34
Achtung, wir reden hier von unterschiedlichen Logins.
"skill id invalid" bedeutet, dass das Projekt zu alt ist, der Login (mit ClientID/Secret) hat aber funktioniert.
Du musst auf https://auth.tuya.com/?from=https%3A%2F%2Fiot.tuya.com%2F gehen, dort den Tuya Developer Account nutzen und ein neues Projekt anlegen.
ja und dort bekomme ich "The account or password you entered is incorrect"
Und Forgot Password liefert kein Mail?
Zitat von: dominik am 09 Oktober 2021, 20:27:53
Und Forgot Password liefert kein Mail?
jetzt endlich nach ca. 5 Versuchen .. Passwort ist geändert (drei erste Stellen sind nun Großbuchstaben) :)
also lege ich nun ein neues Projekt an .....
Super!
Nachdem das neue Projekt angelegt ist und mit SmartLife verknüpft ist, musst du die neue Client ID / Secret in FHEM verwenden. Ich bin gespannt ob alle 96 Devices rüber kommen :)
Zitat von: dominik am 09 Oktober 2021, 20:50:30
Super!
Nachdem das neue Projekt angelegt ist und mit SmartLife verknüpft ist, musst du die neue Client ID / Secret in FHEM verwenden. Ich bin gespannt ob alle 96 Devices rüber kommen :)
kann es sein, dass ich nur die Services anlegen muss (wizard) und der Rest noch da ist?
2021-10-09 20:58:02,948 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-09 20:58:02,971 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-09 20:58:03,086 - WARNING - asyncio: Executing <Task pending coro=<async_main() running at /opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/fhem_pythonbinding.py:469> wait_for=<_GatheringFuture pending cb=[<TaskWakeupMethWrapper object at 0x75ab30d0>()] created at /usr/lib/python3.7/asyncio/tasks.py:615> cb=[_run_until_complete_cb() at /usr/lib/python3.7/asyncio/base_events.py:158] created at /usr/lib/python3.7/asyncio/base_events.py:563> took 0.138 seconds
2021-10-09 20:58:03,089 - INFO - websockets.server: server listening on 0.0.0.0:15733
2021-10-09 20:58:15,814 - INFO - websockets.server: connection open
2021-10-09 20:58:15,817 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-09 20:58:17,570 - ERROR - tuya_cloud_connector: Tuya login error response: {'code': 2406, 'msg': 'skill id invalid', 'success': False, 't': 1633805897546}
natürlich habe ich die Werte angepasst
Lösch das bestehende Device aus FHEM raus und dann bitte wirklich Schritt für Schritt der Anleitung folgen:
https://github.com/dominikkarall/fhempy/blob/master/FHEM/bindings/python/fhempy/lib/tuya_cloud/README.md
Zitat von: dominik am 09 Oktober 2021, 21:01:40
Lösch das bestehende Device aus FHEM raus und dann bitte wirklich Schritt für Schritt der Anleitung folgen:
https://github.com/dominikkarall/fhempy/blob/master/FHEM/bindings/python/fhempy/lib/tuya_cloud/README.md
ok ,, Link Tuya App Account fehlte
nun habe ich:
Fernseher_Schlafzimmer_10438000d8f15ba4ccd3 (Fernseher Schlafzimmer)
off
PythonModule
Gartengrill_12280017d8f15bdedda5 (Gartengrill)
off
PythonModule
Haustuere_60381718500291bade80 (Haustüre)
ready
PythonModule
Kleiderschrank_1_30180616dc4f22fc97ae (Kleiderschrank 1)
off
PythonModule
Petra_oben_bf3d3c043a37716331bhfb (Petra oben)
off
PythonModule
Rolltor_34602852ecfabc47cbe1 (Rolltor)
closed
PythonModule
SP2_Kuehlschrank_HWR_045074212cf432ca0721 (SP2 Kühlschrank HWR)
on
PythonModule
Schreibtisch_Petra_22230808bcddc2135132 (Schreibtisch Petra)
off
PythonModule
USB_Lader_1_Thomas_3367036770039f60ce2b (USB Lader 1 Thomas)
on
PythonModule
USB_Lader_2_Thomas_3367036770039f613620 (USB Lader 2 Thomas)
on
PythonModule
USB_Lader_3_Thomas_33670367c4dd573813d8 (USB Lader 3 Thomas)
on
PythonModule
Wasserpumpe_03132278b4e62d74b293 (Wasserpumpe)
ready
PythonModuleund meine Powerweerte bei Gosund :)
active_time
1573220542
2021-10-09 21:06:43
add_ele
0.001
2021-10-09 21:06:43
biz_type
18
2021-10-09 21:06:43
category
cz
2021-10-09 21:06:43
countdown_1
0.0
2021-10-09 21:06:43
create_time
1573220542
2021-10-09 21:06:43
cur_current
847.0
2021-10-09 21:06:43
cur_power
131.4
2021-10-09 21:06:43
cur_voltage
236.0
2021-10-09 21:06:43und nun sind alle 94 da :-)
Bad_2_07412404cc50e3746c29 (Bad 2)
off
PythonModule
Balkon_Stern_bf16f1788a2fd6edd6pr1d (Balkon Stern)
off
PythonModule
Camera_4_bfbeab33da30f5635ffj0r (Camera 4)
ready
PythonModule
Camera_5_Terrasse_bfd99c63a8b65928a56hdb (Camera 5 Terrasse)
ready
PythonModule
Camera_Buero_bf9e9fea71f3692d15gzrq (Camera Büro)
ready
PythonModule
Camera_Garage_bfffc31d13d14bca5dayj6 (Camera Garage)
ready
PythonModule
Camera_Garten_bf6b1900c331a78a2fkecw (Camera Garten)
ready
PythonModule
Camera_Hauseingang_bf3761a5af5f8d6361rmhh (Camera Hauseingang)
ready
PythonModule
Dimmer_2_21410806cc50e37bdb15 (Dimmer 2)
on
PythonModule
Dunstabzug_104380002462ab2f8ac0 (Dunstabzug)
on
PythonModule
Esstisch_074124042cf4326df127 (Esstisch)
on
PythonModule
Fernseher_Petra_620661512462ab30ddbd (Fernseher Petra)
off
PythonModule
Fernseher_Schlafzimmer_10438000d8f15ba4ccd3 (Fernseher Schlafzimmer)
off
PythonModule
Fernseher_Thomas_63667231dc4f22f32f01 (Fernseher Thomas)
on
PythonModule
Fernseher_Wohnzimmer_22230808bcddc2135068 (Fernseher Wohnzimmer)
on
PythonModule
Garagentor_47104178dc4f2236e437 (Garagentor)
on
PythonModule
Gartengrill_12280017d8f15bdedda5 (Gartengrill)
off
PythonModule
Globus_00715387f4cfa209ab1e (Globus)
off
PythonModule
Haustuere_60381718500291bade80 (Haustüre)
ready
PythonModule
Heizdecke_1_4530056170039f4a87e5 (Heizdecke 1)
off
PythonModule
Heizdecke_2_5062137624a1600b6d62 (Heizdecke 2)
off
PythonModule
Heizdecke_3_104380002462ab30258d (Heizdecke 3)
off
PythonModule
Heizkissen_1_50621376c4dd57131135 (Heizkissen 1)
off
PythonModule
Heizkissen_2_453005615002911dfe06 (Heizkissen 2)
off
PythonModule
JL04_BKT3_22230808807d3a23186b (JL04 BKT3)
on
PythonModule
JL07_BKT2_22230808bcddc2135137 (JL07 BKT2)
off
PythonModule
JL15_Kaffeemaschine_2223080884f3eb466414 (JL15 Kaffeemaschine)
on
PythonModule
Kleiderschrank_1_30180616dc4f22fc97ae (Kleiderschrank 1)
off
PythonModule
Kleiderschrank_2_8513738324a1601779dd (Kleiderschrank 2)
off
PythonModule
Kueche_Herd_30180616dc4f22fc9a71 (Küche Herd)
off
PythonModule
Kueche_oben_074124042cf4326f08c2 (Küche oben)
off
PythonModule
Leselampe_1_03132278b4e62d74ab52 (Leselampe 1)
off
PythonModule
Leselampe_2_03132278b4e62d74ab8f (Leselampe 2)
off
PythonModule
Leselampe_4_4530056170039f4a808b (Leselampe 4)
off
PythonModule
Leselampe_5_50621376c4dd57125717 (Leselampe 5)
off
PythonModule
PC_Schreibtisch_NAS_22230808807d3a231039 (PC Schreibtisch NAS)
off
PythonModule
PETRA_Nacht_1_00715387f4cfa2092c01 (PETRA Nacht 1)
off
PythonModule
PIR_Sensor_1_853556472cf4326e60da (PIR Sensor 1)
nomotion
PythonModule
PIR_Sensor_2_627425735002915f502b (PIR Sensor 2)
nomotion
PythonModule
PIR_Sensor_3_743066432cf43267661d (PIR Sensor 3)
nomotion
PythonModule
PS2___ESSEN_63667231dc4f22f329f1 (PS2 - ESSEN)
on
PythonModule
PS3___Wohnen_1_04086463840d8e50124b (PS3 - Wohnen 1)
off
PythonModule
PS4___Wohnen_2_63667231840d8e501cab (PS4 - Wohnen 2)
on
PythonModule
PS5___Garage_44277377840d8e5e47c8 (PS5 - Garage)
on
PythonModule
PS6___Schreibtisch_P_50050126dc4f22e5e4ee (PS6 - Schreibtisch P)
on
PythonModule
PS7___Balkon_50134218c4dd571b3390 (PS7 - Balkon)
on
PythonModule
Petra_oben_bf3d3c043a37716331bhfb (Petra oben)
off
PythonModule
Rolltor_34602852ecfabc47cbe1 (Rolltor)
closed
PythonModule
Router_EAP225_104380002462ab301b83 (Router EAP225)
on
PythonModule
SP11_THOMAS_Ost_62066151d8f15bb08810 (SP11 THOMAS Ost)
on
PythonModule
SP12_THOMAS_Sued1_00673231e09806cb13b0 (SP12 THOMAS Süd1)
on
PythonModule
SP13_THOMAS_Sued2_Schreibtisch_52470320e09806c9a53f (SP13 THOMAS Süd2 Schreibtisch)
on
PythonModule
SP14_PETRA_SuedOst_00673231e09806cb6fa5 (SP14 PETRA SüdOst)
on
PythonModule
SP15_PETRA_Bett_00673231e09806cb188e (SP15 PETRA Bett)
on
PythonModule
SP16_THOMAS_West_00673231e09806cbeaa2 (SP16 THOMAS West)
on
PythonModule
SP1_C_Smart_Socket_16A_045074212462ab24e988 (SP1-C Smart Socket-16A)
on
PythonModule
SP1_Waschmaschine_260064612cf432ca55d8 (SP1-Waschmaschine)
on
PythonModule
SP2_Kuehlschrank_HWR_045074212cf432ca0721 (SP2 Kühlschrank HWR)
on
PythonModule
SP3_Kuehlschrank_Kueche_260064612462ab24f164 (SP3 Kühlschrank Küche)
on
PythonModule
SP5_EX17_EX18_60020372840d8e6f937a (SP5 EX17 EX18)
off
PythonModule
SP6_EX20_WD125_41888155dc4f229d95af (SP6 EX20 WD125)
off
PythonModule
SP7_Garagenkeller_62066151d8f15bdec539 (SP7 Garagenkeller)
on
PythonModule
SP8_Wohnzimmer_00673231e09806cb0add (SP8 Wohnzimmer)
off
PythonModule
Schalter_Doppel_SW101E_2_0120018760019453b4b1 (Schalter Doppel SW101E-2)
off
PythonModule
Schlafzimmer_oben_30510063d8bfc00b396b (Schlafzimmer oben)
off
PythonModule
Schnellkocher_5062137624a1600b9479 (Schnellkocher)
on
PythonModule
Schreibtisch_Petra_22230808bcddc2135132 (Schreibtisch Petra)
off
PythonModule
Schreibtisch_Thomas_22230808bcddc213f838 (Schreibtisch Thomas)
on
PythonModule
Sirene_1_Temp_07847240dc4f225fdda0 (Sirene 1 Temp)
not support this device
PythonModule
Sirene_2_Temp_07847240bcddc29b03e9 (Sirene 2 Temp)
not support this device
PythonModule
Sirene_3_06515140cc50e3d62490 (Sirene 3)
ready
PythonModule
SmartBulb_LW_2_bfefd42e199ea92ee3jbwh (SmartBulb LW 2)
on
PythonModule
Springbrunnen_30180616dc4f22fc986a (Springbrunnen)
off
PythonModule
Steckdose_3_720570712462ab280270 (Steckdose 3)
off
PythonModule
Steckdose_4_720570712462ab27e625 (Steckdose 4)
off
PythonModule
Steckdose_Garage_1_3367036770039f60c576 (Steckdose Garage 1)
on
PythonModule
Steckdose_PETRA_1_17710212600194dbaba8 (Steckdose PETRA 1)
off
PythonModule
Steckdose_THOMAS_Tuere_17710212600194dba99d (Steckdose THOMAS Türe)
off
PythonModule
Thomas_oben_bf369b75b893e0b115nzuk (Thomas oben)
off
PythonModule
Toilette_067327848cce4ec3fe13 (Toilette)
on
PythonModule
TuerSensor_4_67242256f4cfa2ce1662 (TürSensor 4)
closed
PythonModule
Tuersensor_2_60381718807d3a04bbb4 (Türsensor 2)
ready
PythonModule
Tuersensor_3_60381718807d3a01eb63 (Türsensor 3)
ready
PythonModule
USB_Lader_1_Thomas_3367036770039f60ce2b (USB Lader 1 Thomas)
on
PythonModule
USB_Lader_2_Thomas_3367036770039f613620 (USB Lader 2 Thomas)
on
PythonModule
USB_Lader_3_Thomas_33670367c4dd573813d8 (USB Lader 3 Thomas)
on
PythonModule
USB_Lader_5_Bett_453005615002911e00b4 (USB Lader 5 Bett)
on
PythonModule
Wassermelder_180025363c6105dcdcaf (Wassermelder)
normal
PythonModule
Wasserpumpe_03132278b4e62d74b293 (Wasserpumpe)
off
PythonModule
Wassersensor_1_Kueche_50880180cc50e30cbe91 (Wassersensor 1 Küche)
2
PythonModule
Wassersensor_2_Heizraum_50880180840d8e87664b (Wassersensor 2 Heizraum)
2
PythonModule
Wassersensor_3_Waschmaschine_50880180cc50e30c4c90 (Wassersensor 3 Waschmaschine)
2
PythonModule
Wohnzimmer_4_887800042cf4325f15ef (Wohnzimmer 4)
off
PythonModule
ZOO_JL12_03132278a4cf12a5e7b0 (ZOO JL12)
Gehen wir mal ein Device nach dem anderen durch...
Was für Readings hast du bei einem simplen on/off Switch, wie vermutlich Fernseher_Schlafzimmer_10438000d8f15ba4ccd3?
Zitat von: dominik am 09 Oktober 2021, 21:14:02
Gehen wir mal ein Device nach dem anderen durch...
Was für Readings hast du bei einem simplen on/off Switch, wie vermutlich Fernseher_Schlafzimmer_10438000d8f15ba4ccd3?
das ist perfekt:
Readings
active_time
1561743877
2021-10-09 21:16:31
biz_type
18
2021-10-09 21:16:31
category
cz
2021-10-09 21:16:31
countdown_1
0.0
2021-10-09 21:31:22
create_time
1549400992
2021-10-09 21:16:31
cur_current
408.0
2021-10-09 21:31:22
cur_power
84.0
2021-10-09 21:31:22
cur_voltage
229.7
2021-10-09 21:31:22
icon
https://images.tuyaeu.com/smart/icon/1553147031mcc9hg5e3g_0.png
2021-10-09 21:16:31
id
22230808bcddc2135068
2021-10-09 21:16:31
ip
46.5.23.119
2021-10-09 21:16:31
lat
48.5584483
2021-10-09 21:16:31
local_key
c0aa3a00c215aa39
2021-10-09 21:16:31
lon
9.2025591
2021-10-09 21:16:31
model
HYS-01-039
2021-10-09 21:16:31
name
Fernseher Wohnzimmer
2021-10-09 21:16:31
online
on
2021-10-09 21:16:31
owner_id
3389434
2021-10-09 21:16:31
product_id
1hxNMF9lRQL2xpEA
2021-10-09 21:16:31
product_name
SMART SOCKET
2021-10-09 21:16:31
state
on
2021-10-09 21:31:22
sub
off
2021-10-09 21:16:31
time_zone
+01:00
2021-10-09 21:16:31
uid
eu1548823829280mLHX1
2021-10-09 21:16:31
update_time
1633780790
2021-10-09 21:16:31
uuid
22230808bcddc2135068
2021-10-09 21:16:31ein update erfolgt ca. alle 2 sec
Ok, das Update erfolgt nur, wenn sich Werte ändern, sonst sollte sich nix tun. Wenn du ein und aus schaltest (egal ob an der Hardware oder via SmartLife), muss das sofort auch in FHEM erscheinen.
Funktionieren allen einfachen on/off Switches? Wenn ja, dann bitte mal ein Device posten wo du Probleme hast.
Zitat von: dominik am 09 Oktober 2021, 21:36:52
Ok, das Update erfolgt nur, wenn sich Werte ändern, sonst sollte sich nix tun. Wenn du ein und aus schaltest (egal ob an der Hardware oder via SmartLife), muss das sofort auch in FHEM erscheinen.
Funktionieren allen einfachen on/off Switches? Wenn ja, dann bitte mal ein Device posten wo du Probleme hast.
schalten funktioniert mit quasi sofortiger Wirkung :-)
was nicht rüber kommt sind die "electric"-Verbrauchswerte, die ich in der App je Monat sehe
BTW: sind das für diesen Fernseher 9,8 kWh monatlich also ca. 3€
diese Verbrauchsdaten wären für mich wichtig, am wichtigsten .. die Werte müssen ja in der Cloud liegen
und aus diesem Grund habe ich mir die zig Gosund beschafft, um die Stromkosten je Gerät monitoren zu können
kann man das bei Tuya noch bekommen ?
das soll keineswegs deine super Arbeit und deinen excellenten Support schmälern!!
ich bin begeistert !!
Die Verbrauchswerte bekommst du aktuell nur in cur_power. Du kannst die mal in Log schreiben und dann als Grafik darstellen oder wahrscheinlich auch mit irgendeinem anderen Moduls summieren.
Laut Tuya Beschreibung sollte man die Verbrauchswerte auch von der Cloud bekommen können. Ich habe das noch nicht ausprobiert, werde ich aber noch testen, da mich die Werte auch interessieren :)
Hast du eigentlich alle 96 Devices angelegt bekommen?
Zitat von: dominik am 09 Oktober 2021, 21:51:58
Die Verbrauchswerte bekommst du aktuell nur in cur_power. Du kannst die mal in Log schreiben und dann als Grafik darstellen oder wahrscheinlich auch mit irgendeinem anderen Moduls summieren.
Laut Tuya Beschreibung sollte man die Verbrauchswerte auch von der Cloud bekommen können. Ich habe das noch nicht ausprobiert, werde ich aber noch testen, da mich die Werte auch interessieren :)
yepp das wäre mich auch sehr wichtig
übrigens: kann es sein, dass FHEm recht langsam wird, wenn es jede kleinste Änderung in power, voltage updaten muss?
Das kommt drauf an :) Bei mir bleibt z.B. der cur_voltage Wert teilweise 5min gleich. Schau mal wie oft sich die Readings ändern, wenn das zu oft passiert, kannst ja mit event-* Attributen spielen um die Events zu reduzieren.
Zitat von: dominik am 09 Oktober 2021, 22:07:14
Das kommt drauf an :) Bei mir bleibt z.B. der cur_voltage Wert teilweise 5min gleich. Schau mal wie oft sich die Readings ändern, wenn das zu oft passiert, kannst ja mit event-* Attributen spielen um die Events zu reduzieren.
bei diesen Werten kann ich zuschauen, wie sich alle 5-10 sec ändern:
cur_current
22.0
2021-10-09 22:12:47
cur_power
51.0
2021-10-09 22:12:47
cur_voltage
2308.0
2021-10-09 22:12:47
Falls FHEM damit zu stark belastet wird, mach einfach event-on* Attribute rein.
Btw, cur_voltage 2308.0, da stimmt was nicht, sollte 230.8 sein. Ist das bei allen Devices der Fall?
Zitat von: dominik am 09 Oktober 2021, 22:07:14
Das kommt drauf an :) Bei mir bleibt z.B. der cur_voltage Wert teilweise 5min gleich. Schau mal wie oft sich die Readings ändern, wenn das zu oft passiert, kannst ja mit event-* Attributen spielen um die Events zu reduzieren.
bewirken die nicht nur, dass die readings nur eingeschränkt ist Log geschrieben werden?
das Python-Module wir sie doch dennoch im sec-Takt pollen
Da pollt nix ;) Das ist ja das gute am tuya_cloud Modul, da wird einfach eine MQTT Verbindung zur tuya Cloud hergestellt und die schickt eine MQTT Message wenn sich was tut.
FHEM wird nur durch die Reading Updates belastet, wenn z.B. notifys/doifs/... darauf warten, dann werden diese immer geprüft.
sehe ich das richtig, dass neue Devices anhand ihrer ID angelegt werden?
d.h. Änderung des Namens (der ja auch der ALEXA-Name ist) in der SmartLifeApp schlägt nicht zu FHEM durch ?
somit können die DEFs entsprechend angepasst werden?
So, auf der Tuya Plattform wird der Ventilator jetzt wieder als Online angezeigt.
In Fhem habe ich das Device für den Ventilator gelöscht, da er sich immer noch nicht bedienen lies, trotz restart etc.
Nun wird der Ventilator aber nicht neu angelegt.
Nach dem Neustart bekomme ich jetzt auf dem zweiten Gerät auch nur noch ein "Ready" als STATE angezeigt und keinerlei Set-Befehle mehr.
Zitat von: thburkhart am 10 Oktober 2021, 13:42:30
sehe ich das richtig, dass neue Devices anhand ihrer ID angelegt werden?
d.h. Änderung des Namens (der ja auch der ALEXA-Name ist) in der SmartLifeApp schlägt nicht zu FHEM durch ?
somit können die DEFs entsprechend angepasst werden?
DEFs bitte nicht ändern, die müssen so bleiben. Namen einfach per alias setzen.
Den Device Name kannst du testweise per rename ändern, eventuell ist aber ein Neustart notwendig. Da hatte ich Mal einen Bug drin.
Zitat von: Superposchi am 10 Oktober 2021, 14:20:27
So, auf der Tuya Plattform wird der Ventilator jetzt wieder als Online angezeigt.
In Fhem habe ich das Device für den Ventilator gelöscht, da er sich immer noch nicht bedienen lies, trotz restart etc.
Nun wird der Ventilator aber nicht neu angelegt.
Nach dem Neustart bekomme ich jetzt auf dem zweiten Gerät auch nur noch ein "Ready" als STATE angezeigt und keinerlei Set-Befehle mehr.
Kannst du bitte in einem Post zusammenfassen was du hast und brauchst?
Das habe ich inzwischen schon zigmal, aber bitte gerne nochmal:
1) Ich brauche das Anlegen des Tuya-Devices für den Ventilator der auf der IoT-Plattform existiert und jetzt wieder als Online angeziegt wird in Fhem aber von mir manuell gelöscht wurde.
2) Brauche ich für das Device des Luftbefeuchters die Bedienbarkeit. Es wird nur Ready angezeigt und keine Set-Befehle.
Sorry, vielleicht schlecht formuliert von mir. Bitte technisch zusammenfassen:
- Welches tuya_cloud Device hast du aktuell in FHEM?
- Wie lautet der technische Name des Devices auf der IoT Plattform?
- Welche Devices werden angelegt, wenn du den tuya_cloud_connector aktivierst?
- Was hat es nun mit den 2 Devices auf sich die 1 sein sollen? Wo werden 2 Devices angezeigt (welche) und wo wird ein Device angezeigt (welches)?
Bitte mit Screenshots oder copy&paste wo möglich, damit ich einen Überblick habe. Ich verstehe das Problem noch nicht ganz mit dem 2->1 Devices.
Also Grundlegend zur Hardware:
Ich habe aktuell 2 Geräte mit Tuya-Steuerung.
1) einen Luftbefeuchter
2) einen Ventilator mit zusatzmodul Luftbefeuchter
Beide werden auf der Tuya-IoT-Plattform korrekt angezeigt. Siehe Screnshot #1.
In Fhem wurden beide Devices angezeigt. Da sich der Ventilator jedoch nicht bedienen ließ, habe ich ihn gelöscht um ihn neu zu erstellen.
Auf Screenshot #2 sind alle fhempy:Tuya Devices aufgelistet. Der Ventilator fehlt und wird auch nicht automatisch neu erstellt.
Habe schon den kompletten Fhem-Server neugestartet, beim local_pybinding ein Update und auch das pythonbinding_15733 neugestartet. Den Tuya-Cloud-connector kann ich nicht ändern. Dort gibt es keinerlei Einstellmöglichkeiten (siehe Screenshot #4)
Seit diesen Versuchen wird jetzt auch der Luftbefeuchter fehlerhaft angezeigt, keine Set-Befehle mehr und das STATE zeigt lediglich ready an (Screenshot #3).
Zusätzlich fehlten ja bei beiden Devices in der Vergangenheit jede Menge Optionen, was besonders beim Ventilator dumm war, da dort die komplette Befeuchter-Befehle nicht existierten. Wahrscheinlich, da der Luftbefeuchter nur als Option auf den Ventilator aufgesetzt und durch diesen mit Spannung versorgt wird. In der App sind irgendwie dann von beiden Teilgeräten alle Funktionen in einem Eintrag zusammen steuerbar. Da es sich aber um zwei zusammengebaute Einzelteile handelt hatte ich ursprünglich überlegt ob vielleicht die Möglichkeit besteht innerhalb der Tuya-Plattform ein weiteres virtuelles Device zu erstellen, mit der IP des Ventilators aber den Funktionen eines Luftbefeuchters. Wäre ja in Fhem egal wenn dort zwei Devices zum Ventilator existiert hätten. Aber das war nur eine Überlegung um an die fehlenden Funktionen ranzukommen.
Ich hoffe das deckt jetzt alle Fragen ab.
Ok, jetzt kenn ich mich aus, danke!
Anhand der Screenshots erkennt man, dass der Connector nur auf connecting statt connected steht.
Schau Mal ins fhempy Log bzw prüfe die Parameter im Define. Eventuell ist clientid/Secret oder Username/Passwort falsch. Username/Password muss von der SmartLife App sein.
Da ja alles mal funktioniert hat und ich nichts geändert habe müssen Username und Passwort stimmen.
Wie kann ich die clientid kontrollieren? wo finde ich diese in der App/Iot-Plattform?
Hier das Log von heute, vielleicht kannst du ja einen fehler entdecken, ich kenne mich zu wenig damit aus:
2021-10-10 02:00:02,501 - WARNING - asyncio: Executing <TimerHandle when=389825.150067971 _set_result_unless_cancelled(<Future finis...events.py:396>, None) at /usr/lib/python3.7/asyncio/futures.py:284 created at /usr/lib/python3.7/asyncio/tasks.py:566> took 0.261 seconds
2021-10-10 02:09:07,903 - ERROR - pychromecast.socket_client: [Musikwiedergabe(192.168.178.160):32194] Error reading from socket.
2021-10-10 02:09:48,119 - ERROR - pychromecast.socket_client: [Schlafzimmerlautsprecher(192.168.178.160):8009] Failed to connect to service ServiceInfo(type='host', data=('192.168.178.160', 8009)), retrying in 5.0s
2021-10-10 02:09:57,145 - ERROR - pychromecast.socket_client: [Musikwiedergabe(192.168.178.161):32194] Error reading from socket.
2021-10-10 13:06:40,167 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-10 13:06:40,174 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-10 13:06:42,632 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-10 13:06:42,639 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-10 13:06:46,881 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-10 13:06:46,887 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-10 13:06:49,451 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-10 13:07:02,355 - WARNING - asyncio: Executing <Task finished coro=<googlecast.connect_spotipy() done, defined at /opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/googlecast/googlecast.py:220> exception=ConnectionError(MaxRetryError("HTTPSConnectionPool(host='accounts.spotify.com', port=443): Max retries exceeded with url: /api/token (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f9e4d96a1d0>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))")) created at /usr/lib/python3.7/asyncio/tasks.py:325> took 10.021 seconds
2021-10-10 13:07:02,369 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-10 13:07:02,374 - ERROR - fhempy.lib.fhem_pythonbinding: Connection closed error
Traceback (most recent call last):
File "/usr/local/lib/python3.7/dist-packages/websockets/legacy/protocol.py", line 750, in transfer_data
message = await self.read_message()
File "/usr/local/lib/python3.7/dist-packages/websockets/legacy/protocol.py", line 819, in read_message
frame = await self.read_data_frame(max_size=self.max_size)
File "/usr/local/lib/python3.7/dist-packages/websockets/legacy/protocol.py", line 895, in read_data_frame
frame = await self.read_frame(max_size)
File "/usr/local/lib/python3.7/dist-packages/websockets/legacy/protocol.py", line 975, in read_frame
extensions=self.extensions,
File "/usr/local/lib/python3.7/dist-packages/websockets/legacy/framing.py", line 55, in read
data = await reader(2)
File "/usr/lib/python3.7/asyncio/streams.py", line 677, in readexactly
raise IncompleteReadError(incomplete, n)
asyncio.streams.IncompleteReadError: 0 bytes read on a total of 2 expected bytes
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/fhem_pythonbinding.py", line 67, in pybinding
async for message in websocket:
File "/usr/local/lib/python3.7/dist-packages/websockets/legacy/protocol.py", line 356, in __aiter__
yield await self.recv()
File "/usr/local/lib/python3.7/dist-packages/websockets/legacy/protocol.py", line 421, in recv
await self.ensure_open()
File "/usr/local/lib/python3.7/dist-packages/websockets/legacy/protocol.py", line 726, in ensure_open
raise self.connection_closed_exc()
websockets.exceptions.ConnectionClosedError: code = 1006 (connection closed abnormally [internal]), no reason
2021-10-10 13:07:02,374 - INFO - fhempy.lib.fhem_pythonbinding: Restart binding
2021-10-10 13:07:22,250 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-10 13:07:22,257 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-10 13:23:39,759 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-10 13:23:39,767 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-10 13:24:06,801 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-10 13:24:18,295 - WARNING - asyncio: Executing <Task finished coro=<googlecast.connect_spotipy() done, defined at /opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/googlecast/googlecast.py:220> exception=ConnectionError(MaxRetryError("HTTPSConnectionPool(host='accounts.spotify.com', port=443): Max retries exceeded with url: /api/token (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fcd63a1de10>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))")) created at /usr/lib/python3.7/asyncio/tasks.py:325> took 10.020 seconds
2021-10-10 13:24:28,328 - WARNING - asyncio: Executing <Task finished coro=<googlecast.connect_spotipy() done, defined at /opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/googlecast/googlecast.py:220> exception=ConnectionError(MaxRetryError("HTTPSConnectionPool(host='accounts.spotify.com', port=443): Max retries exceeded with url: /api/token (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fcd631c5320>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))")) created at /usr/lib/python3.7/asyncio/tasks.py:325> took 10.013 seconds
2021-10-10 13:24:38,369 - WARNING - asyncio: Executing <Task finished coro=<googlecast.connect_spotipy() done, defined at /opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/googlecast/googlecast.py:220> exception=ConnectionError(MaxRetryError("HTTPSConnectionPool(host='accounts.spotify.com', port=443): Max retries exceeded with url: /api/token (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fcd631c5978>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))")) created at /usr/lib/python3.7/asyncio/tasks.py:325> took 10.039 seconds
2021-10-10 14:08:07,098 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-10 14:08:07,105 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-10 14:08:16,859 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-10 14:08:28,159 - WARNING - asyncio: Executing <Task finished coro=<googlecast.connect_spotipy() done, defined at /opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/googlecast/googlecast.py:220> exception=ConnectionError(MaxRetryError("HTTPSConnectionPool(host='accounts.spotify.com', port=443): Max retries exceeded with url: /api/token (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fc7ca6c9e48>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))")) created at /usr/lib/python3.7/asyncio/tasks.py:325> took 10.010 seconds
2021-10-10 14:08:38,188 - WARNING - asyncio: Executing <Task finished coro=<googlecast.connect_spotipy() done, defined at /opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/googlecast/googlecast.py:220> exception=ConnectionError(MaxRetryError("HTTPSConnectionPool(host='accounts.spotify.com', port=443): Max retries exceeded with url: /api/token (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fc7c9e732e8>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))")) created at /usr/lib/python3.7/asyncio/tasks.py:325> took 10.013 seconds
2021-10-10 14:08:48,202 - WARNING - asyncio: Executing <Task finished coro=<googlecast.connect_spotipy() done, defined at /opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/googlecast/googlecast.py:220> exception=ConnectionError(MaxRetryError("HTTPSConnectionPool(host='accounts.spotify.com', port=443): Max retries exceeded with url: /api/token (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fc7c9e73940>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))")) created at /usr/lib/python3.7/asyncio/tasks.py:325> took 10.013 seconds
2021-10-10 14:09:03,407 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Wohnzimmerlautsprecher'});;
2021-10-10 14:09:05,696 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"error":0,"result":"2021-10-10 14:09:05","awaitId":49825440}
2021-10-10 14:09:32,804 - INFO - fhempy.lib.pkg_installer: Attempting install of fhempy
2021-10-10 14:10:42,234 - ERROR - fhempy.lib.pkg_installer: Unable to install package fhempy: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f83b5fe2278>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/fhempy/
Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f83b5fe2048>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/fhempy/
Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f83b64ab080>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/fhempy/
Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f83b64ab0f0>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/fhempy/
Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f83b64ab1d0>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/fhempy/
Could not install packages due to an EnvironmentError: HTTPSConnectionPool(host='pypi.org', port=443): Max retries exceeded with url: /simple/fhempy/ (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f83b64ab320>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))
2021-10-10 14:10:42,236 - INFO - fhempy.lib.pkg_installer: Attempting install of fhempy
2021-10-10 14:10:42,525 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-10 14:10:42,532 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-10 14:10:52,640 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-10 14:11:04,061 - WARNING - asyncio: Executing <Task finished coro=<googlecast.connect_spotipy() done, defined at /opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/googlecast/googlecast.py:220> exception=ConnectionError(MaxRetryError("HTTPSConnectionPool(host='accounts.spotify.com', port=443): Max retries exceeded with url: /api/token (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f1c05c55e80>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))")) created at /usr/lib/python3.7/asyncio/tasks.py:325> took 10.012 seconds
2021-10-10 14:11:14,094 - WARNING - asyncio: Executing <Task finished coro=<googlecast.connect_spotipy() done, defined at /opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/googlecast/googlecast.py:220> exception=ConnectionError(MaxRetryError("HTTPSConnectionPool(host='accounts.spotify.com', port=443): Max retries exceeded with url: /api/token (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f1c054005f8>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))")) created at /usr/lib/python3.7/asyncio/tasks.py:325> took 10.013 seconds
Exception in thread zeroconf-ServiceBrowser-_googlecast._tcp-139758751135488:
Traceback (most recent call last):
File "/usr/lib/python3.7/threading.py", line 917, in _bootstrap_inner
self.run()
File "/opt/fhem/.local/lib/python3.7/site-packages/zeroconf/_services/browser.py", line 541, in run
self._fire_service_state_changed_event(event)
File "/opt/fhem/.local/lib/python3.7/site-packages/zeroconf/_services/browser.py", line 427, in _fire_service_state_changed_event
state_change=state_change,
File "/opt/fhem/.local/lib/python3.7/site-packages/zeroconf/_services/__init__.py", line 55, in fire
h(**kwargs)
File "/opt/fhem/.local/lib/python3.7/site-packages/zeroconf/_services/browser.py", line 178, in on_change
getattr(listener, _ON_CHANGE_DISPATCH[state_change])(zeroconf, service_type, name)
File "/opt/fhem/.local/lib/python3.7/site-packages/pychromecast/discovery.py", line 120, in add_service
self._add_update_service(zconf, typ, name, self._cast_listener.add_cast)
File "/opt/fhem/.local/lib/python3.7/site-packages/pychromecast/discovery.py", line 195, in _add_update_service
callback(uuid, name)
File "/opt/fhem/.local/lib/python3.7/site-packages/pychromecast/discovery.py", line 66, in add_cast
self._add_callback(uuid, service)
File "/opt/fhem/.local/lib/python3.7/site-packages/pychromecast/__init__.py", line 254, in add_callback
timeout=timeout,
File "/opt/fhem/.local/lib/python3.7/site-packages/pychromecast/__init__.py", line 93, in get_chromecast_from_cast_info
zconf=zconf,
File "/opt/fhem/.local/lib/python3.7/site-packages/pychromecast/__init__.py", line 311, in __init__
dev_status = get_device_status(host, services, zconf)
File "/opt/fhem/.local/lib/python3.7/site-packages/pychromecast/dial.py", line 116, in get_device_status
context,
File "/opt/fhem/.local/lib/python3.7/site-packages/pychromecast/dial.py", line 71, in _get_status
host, _, _ = get_host_from_service(service, zconf)
File "/opt/fhem/.local/lib/python3.7/site-packages/pychromecast/dial.py", line 32, in get_host_from_service
service_info = zconf.get_service_info("_googlecast._tcp.local.", service.data)
File "/opt/fhem/.local/lib/python3.7/site-packages/zeroconf/_core.py", line 490, in get_service_info
if info.request(self, timeout, question_type):
File "/opt/fhem/.local/lib/python3.7/site-packages/zeroconf/_services/info.py", line 437, in request
return bool(run_coro_with_timeout(self.async_request(zc, timeout, question_type), zc.loop, timeout))
File "/opt/fhem/.local/lib/python3.7/site-packages/zeroconf/_utils/asyncio.py", line 96, in run_coro_with_timeout
millis_to_seconds(timeout) + _LOADED_SYSTEM_TIMEOUT
File "/usr/lib/python3.7/concurrent/futures/_base.py", line 434, in result
raise TimeoutError()
concurrent.futures._base.TimeoutError
2021-10-10 14:11:24,107 - WARNING - asyncio: Executing <Task finished coro=<googlecast.connect_spotipy() done, defined at /opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/googlecast/googlecast.py:220> exception=ConnectionError(MaxRetryError("HTTPSConnectionPool(host='accounts.spotify.com', port=443): Max retries exceeded with url: /api/token (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f1c0540e860>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))")) created at /usr/lib/python3.7/asyncio/tasks.py:325> took 10.011 seconds
2021-10-10 14:15:28,755 - INFO - fhempy.lib.pkg_installer: Attempting install of fhempy
2021-10-10 14:15:41,092 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-10 14:15:41,098 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-10 14:15:50,839 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-10 14:16:02,199 - WARNING - asyncio: Executing <Task finished coro=<googlecast.connect_spotipy() done, defined at /opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/googlecast/googlecast.py:220> exception=ConnectionError(MaxRetryError("HTTPSConnectionPool(host='accounts.spotify.com', port=443): Max retries exceeded with url: /api/token (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f8ad1284860>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))")) created at /usr/lib/python3.7/asyncio/tasks.py:325> took 10.013 seconds
2021-10-10 14:16:02,214 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-10 14:16:02,219 - ERROR - fhempy.lib.fhem_pythonbinding: Connection closed error
Traceback (most recent call last):
File "/usr/local/lib/python3.7/dist-packages/websockets/legacy/protocol.py", line 750, in transfer_data
message = await self.read_message()
File "/usr/local/lib/python3.7/dist-packages/websockets/legacy/protocol.py", line 819, in read_message
frame = await self.read_data_frame(max_size=self.max_size)
File "/usr/local/lib/python3.7/dist-packages/websockets/legacy/protocol.py", line 895, in read_data_frame
frame = await self.read_frame(max_size)
File "/usr/local/lib/python3.7/dist-packages/websockets/legacy/protocol.py", line 975, in read_frame
extensions=self.extensions,
File "/usr/local/lib/python3.7/dist-packages/websockets/legacy/framing.py", line 55, in read
data = await reader(2)
File "/usr/lib/python3.7/asyncio/streams.py", line 677, in readexactly
raise IncompleteReadError(incomplete, n)
asyncio.streams.IncompleteReadError: 0 bytes read on a total of 2 expected bytes
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/fhem_pythonbinding.py", line 67, in pybinding
async for message in websocket:
File "/usr/local/lib/python3.7/dist-packages/websockets/legacy/protocol.py", line 356, in __aiter__
yield await self.recv()
File "/usr/local/lib/python3.7/dist-packages/websockets/legacy/protocol.py", line 421, in recv
await self.ensure_open()
File "/usr/local/lib/python3.7/dist-packages/websockets/legacy/protocol.py", line 726, in ensure_open
raise self.connection_closed_exc()
websockets.exceptions.ConnectionClosedError: code = 1006 (connection closed abnormally [internal]), no reason
2021-10-10 14:16:02,220 - INFO - fhempy.lib.fhem_pythonbinding: Restart binding
2021-10-10 14:16:22,261 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-10-10 14:16:22,267 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-10-10 14:16:33,038 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-10-10 14:16:44,353 - WARNING - asyncio: Executing <Task finished coro=<googlecast.connect_spotipy() done, defined at /opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/googlecast/googlecast.py:220> exception=ConnectionError(MaxRetryError("HTTPSConnectionPool(host='accounts.spotify.com', port=443): Max retries exceeded with url: /api/token (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7ff0e17e5da0>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))")) created at /usr/lib/python3.7/asyncio/tasks.py:325> took 10.012 seconds
2021-10-10 14:16:54,379 - WARNING - asyncio: Executing <Task finished coro=<googlecast.connect_spotipy() done, defined at /opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/googlecast/googlecast.py:220> exception=ConnectionError(MaxRetryError("HTTPSConnectionPool(host='accounts.spotify.com', port=443): Max retries exceeded with url: /api/token (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7ff0e0f964e0>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))")) created at /usr/lib/python3.7/asyncio/tasks.py:325> took 10.008 seconds
Exception in thread zeroconf-ServiceBrowser-_googlecast._tcp-140672970659584:
Traceback (most recent call last):
File "/usr/lib/python3.7/threading.py", line 917, in _bootstrap_inner
self.run()
File "/opt/fhem/.local/lib/python3.7/site-packages/zeroconf/_services/browser.py", line 541, in run
self._fire_service_state_changed_event(event)
File "/opt/fhem/.local/lib/python3.7/site-packages/zeroconf/_services/browser.py", line 427, in _fire_service_state_changed_event
state_change=state_change,
File "/opt/fhem/.local/lib/python3.7/site-packages/zeroconf/_services/__init__.py", line 55, in fire
h(**kwargs)
File "/opt/fhem/.local/lib/python3.7/site-packages/zeroconf/_services/browser.py", line 178, in on_change
getattr(listener, _ON_CHANGE_DISPATCH[state_change])(zeroconf, service_type, name)
File "/opt/fhem/.local/lib/python3.7/site-packages/pychromecast/discovery.py", line 120, in add_service
self._add_update_service(zconf, typ, name, self._cast_listener.add_cast)
File "/opt/fhem/.local/lib/python3.7/site-packages/pychromecast/discovery.py", line 195, in _add_update_service
callback(uuid, name)
File "/opt/fhem/.local/lib/python3.7/site-packages/pychromecast/discovery.py", line 66, in add_cast
self._add_callback(uuid, service)
File "/opt/fhem/.local/lib/python3.7/site-packages/pychromecast/__init__.py", line 254, in add_callback
timeout=timeout,
File "/opt/fhem/.local/lib/python3.7/site-packages/pychromecast/__init__.py", line 93, in get_chromecast_from_cast_info
zconf=zconf,
File "/opt/fhem/.local/lib/python3.7/site-packages/pychromecast/__init__.py", line 311, in __init__
dev_status = get_device_status(host, services, zconf)
File "/opt/fhem/.local/lib/python3.7/site-packages/pychromecast/dial.py", line 116, in get_device_status
context,
File "/opt/fhem/.local/lib/python3.7/site-packages/pychromecast/dial.py", line 71, in _get_status
host, _, _ = get_host_from_service(service, zconf)
File "/opt/fhem/.local/lib/python3.7/site-packages/pychromecast/dial.py", line 32, in get_host_from_service
service_info = zconf.get_service_info("_googlecast._tcp.local.", service.data)
File "/opt/fhem/.local/lib/python3.7/site-packages/zeroconf/_core.py", line 490, in get_service_info
if info.request(self, timeout, question_type):
File "/opt/fhem/.local/lib/python3.7/site-packages/zeroconf/_services/info.py", line 437, in request
return bool(run_coro_with_timeout(self.async_request(zc, timeout, question_type), zc.loop, timeout))
File "/opt/fhem/.local/lib/python3.7/site-packages/zeroconf/_utils/asyncio.py", line 96, in run_coro_with_timeout
millis_to_seconds(timeout) + _LOADED_SYSTEM_TIMEOUT
File "/usr/lib/python3.7/concurrent/futures/_base.py", line 434, in result
raise TimeoutError()
concurrent.futures._base.TimeoutError
2021-10-10 14:17:04,394 - WARNING - asyncio: Executing <Task finished coro=<googlecast.connect_spotipy() done, defined at /opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/googlecast/googlecast.py:220> exception=ConnectionError(MaxRetryError("HTTPSConnectionPool(host='accounts.spotify.com', port=443): Max retries exceeded with url: /api/token (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7ff0e0fa77f0>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))")) created at /usr/lib/python3.7/asyncio/tasks.py:325> took 10.013 seconds
Edit:
clientid/secret stimmen auch. Wenn also nichts im Log ersichtlich ist ...
Im Log sind ja einige Fehler mit Name Resolution. Hast du womöglich Probleme mit deinem DNS? Richte mal 8.8.8.8 direkt am FHEM Server als DNS ein und starte danach neu, poste dann bitte ein aktuelles Log.
Das kann sein, Proplanta macht ja auch einigen Ärger mit 500er-Fehler und nicht erreichbaren Adressen.
Wie kann ich denn am Fhem-Server das DNS einstellen.
Achtung: Bei mir läuft der Fhem-Server ja in einem Docker-Container auf einem NAS.
Dann musst im Docker irgendwo den DNS setzen. Nachdem ich selbst kein Docker hab, hilft wahrscheinlich Google.
Danke läuft wieder.
War auch für Proplanta das gleiche Problem gewesen.
Hallo Dominik,
inzwischen habe ich meine 94 Devices kategorisiert und wegen der Lesbarkeit auch umbenannt. Das klappe alles fehlerfrei. Das FHEM machte zwar einige Minuten dicke Backen, aber dann waren alle Devices erfolgreich updedated.
Als Strukturmerkmale verwende ich wie üblich room und groups.
Dein Modul setzt ja wunderschön den Devicenamen lt. SmartLifeApp in alias.
Anregung: bitte ebenso gleich einen Standardroom setzen wie z.B. TUYA; dann erscheinen dort die Devices schön einzeln. (Macht übrigens das MAX-Modul, LaCrosse-Modul auch so)
Herzliche Grüße
Thomas
und dann habe ich noch eine devicespezifische Frage:
ich habe einige sog. Powerstrips, also eine Vierfachsteckdose:
product_id
D7Hl3AxFbHDS98iO
product_name
Smart Power Strip
In der App lassen sich für die einzelnen switches Namen vergeben und sie sind einzeln schaltbar.
Hier die Device Info:
DeviceOverview
PS1 Fernseher Thomas
on
off
PS1
countdown_1
Internals
DEF
tuya_cloud tuya_cloud_connector 63667231dc4f22f32f01
DEVICEID
63667231dc4f22f32f01
FUUID
616325a2-f33f-21fb-0de3-784c7b03eb0e81fb
IODev
local_pybinding
NAME
PS1
NR
1681
PYTHONTYPE
tuya_cloud
STATE
off
TYPE
PythonModule
Readings
active_time
1556280468
2021-10-11 08:22:52
biz_type
18
2021-10-11 08:22:52
category
cz
2021-10-11 08:22:52
countdown_1
0.0
2021-10-11 18:57:00
countdown_2
0.0
2021-10-11 18:57:00
countdown_3
0.0
2021-10-11 18:57:00
countdown_4
0.0
2021-10-11 18:57:00
countdown_usb1
0.0
2021-10-11 18:57:00
create_time
1556280468
2021-10-11 08:22:52
icon
https://images.tuyaeu.com/smart/icon/1504185916_0.png
2021-10-11 08:22:52
id
63667231dc4f22f32f01
2021-10-11 08:22:52
ip
78.43.211.216
2021-10-11 08:22:52
lat
48.5584232
2021-10-11 08:22:52
local_key
565c70fe237fc932
2021-10-11 08:22:52
lon
9.202587
2021-10-11 08:22:52
model
旧PID 废除不用
2021-10-11 08:22:52
name
Fernseher Thomas
2021-10-11 08:22:52
online
on
2021-10-11 08:22:52
owner_id
3389434
2021-10-11 08:22:52
product_id
D7Hl3AxFbHDS98iO
2021-10-11 08:22:52
product_name
Smart Power Strip
2021-10-11 08:22:52
state
off
2021-10-11 18:57:00
sub
off
2021-10-11 08:22:52
switch_2
off
2021-10-11 18:57:00
switch_3
off
2021-10-11 18:57:00
switch_4
off
2021-10-11 18:57:00
switch_usb1
off
2021-10-11 18:57:00
time_zone
+01:00
2021-10-11 08:22:52
uid
eu1548823829280mLHX1
2021-10-11 08:22:52
update_time
1633861658
2021-10-11 08:22:52
uuid
63667231dc4f22f32f01
2021-10-11 08:22:52
PS1
room
TUYA,Thomas
Attributes
alias
PS1 Fernseher Thomas
deleteattr
group
Schalter Fernseher,Schalter Steckdosenleiste
deleteattr
room
TUYA,Thomas
deleteattr
Ähnliches gilt für Mehrfach-Lichtschalter wie:
product_id
shdbwbr7mjjdwu1f
product_name
2G SMART WIFI SWITCH
DeviceOverview
Licht Petra oben
on
off
SCHFF02
countdown_1
Internals
DEF
tuya_cloud tuya_cloud_connector bf3d3c043a37716331bhfb
DEVICEID
bf3d3c043a37716331bhfb
FUUID
6163d81c-f33f-21fb-1fbc-286414737efbe1a6
IODev
local_pybinding
NAME
SCHFF02
NR
1699
PYTHONTYPE
tuya_cloud
STATE
off
TYPE
PythonModule
Readings
active_time
1570793479
2021-10-11 09:15:42
biz_type
18
2021-10-11 09:15:42
category
kg
2021-10-11 09:15:42
countdown_1
0.0
2021-10-11 15:17:49
countdown_2
0.0
2021-10-11 15:17:49
create_time
1570793479
2021-10-11 09:15:42
icon
https://images.tuyaeu.com/smart/program_category_icon/kg.png
2021-10-11 09:15:42
id
bf3d3c043a37716331bhfb
2021-10-11 09:15:42
ip
134.3.57.147
2021-10-11 09:15:42
lat
48.558489
2021-10-11 09:15:42
local_key
0efd0c510b0716ac
2021-10-11 09:15:42
lon
9.2024671
2021-10-11 09:15:42
model
19年2M第二代固件
2021-10-11 09:15:42
name
Petra oben
2021-10-11 09:15:42
online
on
2021-10-11 09:15:42
owner_id
3389434
2021-10-11 09:15:42
product_id
shdbwbr7mjjdwu1f
2021-10-11 09:15:42
product_name
2G SMART WIFI SWITCH
2021-10-11 09:15:42
state
off
2021-10-11 15:17:49
sub
off
2021-10-11 09:15:42
switch_2
off
2021-10-11 15:17:49
time_zone
+02:00
2021-10-11 09:15:42
uid
eu1548823829280mLHX1
2021-10-11 09:15:42
update_time
1633906872
2021-10-11 09:15:42
uuid
e31c888da5d4765f
2021-10-11 09:15:42
Ist das ähnlich wie in der App realisierbar?
Zitat von: dominik am 09 Oktober 2021, 22:07:14
Das kommt drauf an :) Bei mir bleibt z.B. der cur_voltage Wert teilweise 5min gleich. Schau mal wie oft sich die Readings ändern, wenn das zu oft passiert, kannst ja mit event-* Attributen spielen um die Events zu reduzieren.
Hallo Dominik,
kann man diese event-Attribute irgendwie global für alle TUYA devices setzen evtl. sogar schon beim Anlegen?
Also, dass nur alle 5 geloggt wird.
Könntest du ein Beispiel-Def posten ?
Herzliche Grüße
Thomas
Hallo,
Für den Power Strip und Mehrfachschalter habe ich readingsProxy definiert.
Beste Grüße
Jürgen K.
Zitat von: juergen012 am 11 Oktober 2021, 20:11:21
Hallo,
Für den Power Strip und Mehrfachschalter habe ich readingsProxy definiert.
Beste Grüße
Jürgen K.
oh gut !
könntest du ein Beispiel posten?
lg
Thomas
jo, z.B für den switch1 des Power Strip. Die weiteren sind dann identisch.
defmod proxy_Switch1 readingsProxy smart_power_strip_xxxxxxxxxxx:switch_1
attr proxy_Switch1 DbLogExclude .*
attr proxy_Switch1 alias Power Strip Switch 1
attr proxy_Switch1 devStateIcon on:radio_checked@red:off off:radio_unchecked:on
attr proxy_Switch1 room tuya
attr proxy_Switch1 setFn {($CMD eq "on")?fhem("set smart_power_strip_xxxxxxxxxx switch_1 on"):fhem("set smart_power_strip_xxxxxxx switch_1 off");; return undef}
attr proxy_Switch1 setList on off
attr proxy_Switch1 webCmd :
Beste Grüße
Jürgen K.
Hallo Jürgen,
vielen Dank.
Habe es eben mal ausprobiert:
define proxy_Switch1 readingsProxy PS1:switch_1
attr proxy_Switch1 DbLogExclude .*
attr proxy_Switch1 alias PowerStrip Fernseher Thomas Switch 1
attr proxy_Switch1 devStateIcon on:radio_checked@red:off off:radio_unchecked:on
attr proxy_Switch1 group Schalter Steckdosenleiste
attr proxy_Switch1 room THOMAS,TUYA
attr proxy_Switch1 setFn {($CMD eq "on")?fhem("set PS1 switch_1 on"):fhem("set PS1 off");; return undef}
attr proxy_Switch1 setList on off
attr proxy_Switch1 webCmd :
der Powerswitch heißt bei mir schlicht PS1.
komme jedoch über "STATE Initialized" nicht hinaus:
Internals
DEF
PS1:switch_1
DEVICE
PS1
FUUID
61654840-f33f-21fb-ced2-9b1488ba49df79dc
NAME
proxy_Switch1
NOTIFYDEV
global,PS1
NR
1692
NTFY_ORDER
50-proxy_Switch1
READING
switch_1
STATE
Initialized
TYPE
readingsProxy
was habe syntaktisch falsch übernommen?
Viele Grüße
Thomas B.
Moin,
wenn ich den Code bei mir eintrage ist der state auch "Initialized". Mit meinem device klappt es. Hast du den Namen oder den alias eingetragen?
Gruß
Jürgen K.
Zitat von: juergen012 am 12 Oktober 2021, 11:20:06
Moin,
wenn ich den Code bei mir eintrage ist der state auch "Initialized". Mit meinem device klappt es. Hast du den Namen oder den alias eingetragen?
Gruß
Jürgen K.
Moin,
ich habe den DeviceNamen eingetragen (SP21)
lg
Thomas
Tja, sorry. Sollte funktionieren..
Zitat von: juergen012 am 12 Oktober 2021, 16:28:27
Tja, sorry. Sollte funktionieren..
@Dominik
Weißt Du Rat?
was bedeutet "Initialized"?
Ansonsten läuft das Modul super :-)
Auch neue Geräte werden quasi sofort erkannt; lediglich ein Neustart von FHEM ist erforderlich.
lg
Thomas
könnte das daran liegen, dass es meinem Powerswitch
gar kein reading switch_1 gibt?
probiere es mal mit switch_2
bingo
der switch_2 tut :-)
wie schalte ich nun den 1. switch ?
wie kriege ich separate Schaltsymbole ? (also nicht nur einen roten Punkt)
Gruß
Thomas
Zitat von: thburkhart am 11 Oktober 2021, 19:44:27
Hallo Dominik,
inzwischen habe ich meine 94 Devices kategorisiert und wegen der Lesbarkeit auch umbenannt. Das klappe alles fehlerfrei. Das FHEM machte zwar einige Minuten dicke Backen, aber dann waren alle Devices erfolgreich updedated.
Als Strukturmerkmale verwende ich wie üblich room und groups.
Dein Modul setzt ja wunderschön den Devicenamen lt. SmartLifeApp in alias.
Anregung: bitte ebenso gleich einen Standardroom setzen wie z.B. TUYA; dann erscheinen dort die Devices schön einzeln. (Macht übrigens das MAX-Modul, LaCrosse-Modul auch so)
Herzliche Grüße
Thomas
Seit dem Update gestern wird room=fhempy und group=tuya_cloud (in diesem Fall) gesetzt. Somit hat man im fhempy Raum eine gute Übersicht mit den Gruppen über alle Devices.
ok
nach Update alles prima
Zitat von: thburkhart am 11 Oktober 2021, 20:09:53
Hallo Dominik,
kann man diese event-Attribute irgendwie global für alle TUYA devices setzen evtl. sogar schon beim Anlegen?
Also, dass nur alle 5 geloggt wird.
Könntest du ein Beispiel-Def posten ?
Herzliche Grüße
Thomas
Ich glaub hier gibt es leider keinen Standard der für alle passt. Ich dachte schon, dass ich alles auf Event nur bei Änderung stelle, aber dann könnte es vielleicht sein, dass bei einem Bewegungsmelder kein Event kommt.
Daher hier paar Infos die dir wahrscheinlich helfen: https://wiki.fhem.de/wiki/Event-on-change-reading
Zitat von: thburkhart am 12 Oktober 2021, 20:05:58
hmm ..
das hat bei meinen neuen Devices heute nicht so stattgefunden
Hast du auch ein FHEM update gemacht? Das war nämlich diesmal eine Anpassung im Perl Modul.
Zitat von: thburkhart am 12 Oktober 2021, 19:13:34
bingo
der switch_2 tut :-)
wie schalte ich nun den 1. switch ?
wie kriege ich separate Schaltsymbole ? (also nicht nur einen roten Punkt)
Gruß
Thomas
Das readingProxy Modul kenne ich leider nicht, da musst wahrscheinlich in der commandref nach Lösungen suchen. Aber was anderes, gibt es da wirklich keinen switch_1 oder switch? Kannst du über switch_2...4/usb nun alles schalten, oder fehlt dir eine Steckdose?
in der Tat hat der besagte Powerswich nur die im ScreenShot angebenen Readings
das sonst bei Einfachschaltern vorhandene reading "switch" wird zumindest nicht angezeigt
aber ich versuche es mal damit
Aber kannst du mit 2-4 alle Steckdosen der Leiste schalten? Hat sie 3 oder 4 Steckdosen?
Zitat von: dominik am 12 Oktober 2021, 21:35:07
Aber kannst du mit 2-4 alle Steckdosen der Leiste schalten? Hat sie 3 oder 4 Steckdosen?
der Powerswitch
hat 4 mit Smartlife und physisch schaltbare Schuko-Steckdosen plus einen Schalter für 4 USB-Steckdosen
Das heißt eine fehlt dir in FHEM oder? Womöglich ist das auch ein Bug bei tuya, weil countdown_1 wird geliefert, switch_1 aber scheinbar nicht.
Kannst du Mal schauen ob im fhempy Log zum Zeitpunkt der Erstellung irgendein Fehler vorliegt?
Zitat von: dominik am 12 Oktober 2021, 21:41:40
Das heißt eine fehlt dir in FHEM oder? Womöglich ist das auch ein Bug bei tuya, weil countdown_1 wird geliefert, switch_1 aber scheinbar nicht.
Kannst du Mal schauen ob im fhempy Log zum Zeitpunkt der Erstellung irgendein Fehler vorliegt?
genau
bug scheint wahrscheinlich (mit "switch" gings auch nicht)
im log erscheint für jedes device alle 3 min eine update Meldung ;)
das log ist je Tag über 25 MB groß
Ja, diese Logmeldung muss ich noch auf DEBUG ändern.
Kannst du bitte noch auf der tuya iot Plattform Mal bei dem Device auf Debug Device drücken. Da solltest du dann auch die Möglichkeit haben es zu steuern. Wenn dort auch Switch/switch_1 fehlt, dann mach ich einen Bug bei tuya auf.
Zitat von: dominik am 12 Oktober 2021, 20:18:10
Das readingProxy Modul kenne ich leider nicht, da musst wahrscheinlich in der commandref nach Lösungen suchen. Aber was anderes, gibt es da wirklich keinen switch_1 oder switch? Kannst du über switch_2...4/usb nun alles schalten, oder fehlt dir eine Steckdose?
wurde nicht fündig bzw. zu doof ..
@Jürgen kann man tatsächlich nur ein Schaltzustand-Icon darstellen, keine Schalt-Symbole wie im fhempy Modul?
lg
Thomas
Zitat von: dominik am 12 Oktober 2021, 21:55:01
Ja, diese Logmeldung muss ich noch auf DEBUG ändern.
Kannst du bitte noch auf der tuya iot Plattform Mal bei dem Device auf Debug Device drücken. Da solltest du dann auch die Möglichkeit haben es zu steuern. Wenn dort auch Switch/switch_1 fehlt, dann mach ich einen Bug bei tuya auf.
habe ich gemacht
der Switch ist da, lässt sich aber von dort nicht schalten
Ok, dann muss ich nochmals im Code schauen wieso der nicht übernommen wird.
Ach, ich weiß schon wo switch_1 ist. Wenn du direkt das Device mit set fhemdevname on/off steuerst, wird switch_1 genommen. Den Status siehst du im "state".
Ich hatte das so implementiert, damit man bei einfachen Steckdosen oder Devices mit nur einem switch gleich ein on/off in FHEM hat.
Zitat von: dominik am 12 Oktober 2021, 22:15:20
Ach, ich weiß schon wo switch_1 ist. Wenn du direkt das Device mit set fhemdevname on/off steuerst, wird switch_1 genommen. Den Status siehst du im "state".
Ich hatte das so implementiert, damit man bei einfachen Steckdosen oder Devices mit nur einem switch gleich ein on/off in FHEM hat.
der state von PS1 ist jedoch off, obwohl er physisch an ist
Kannst du es mit set PS1 on/off schalten?
nein
das schaltet nicht den gesamten Powerswitch
sondern nur die Untersteckdose 1
also switch_1
also nicht alle 5 (4+USB)
Hast du denn in der SmartLife App die Möglichkeit auch die ganze Leiste zu schalten?
Wenn ja, dann müsste da ein switch1-4 sein + noch ein Switch. Gibt es diesen im Debug Mode?
Zitat von: dominik am 12 Oktober 2021, 23:40:13
Hast du denn in der SmartLife App die Möglichkeit auch die ganze Leiste zu schalten?
Wenn ja, dann müsste da ein switch1-4 sein + noch ein Switch. Gibt es diesen im Debug Mode?
jaein
ja
Gugst DU:
https://wiki.fhem.de/wiki/ReadingsProxy (https://wiki.fhem.de/wiki/ReadingsProxy)
https://wiki.fhem.de/wiki/DevStateIcon (https://wiki.fhem.de/wiki/DevStateIcon)
defmod proxy_Switch1 readingsProxy smart_power_strip_xxxxxxxxxxxxxxxxxx:switch_1
attr proxy_Switch1 DbLogExclude .*
attr proxy_Switch1 alias Power Strip Switch 1
attr proxy_Switch1 devStateIcon on:radio_checked@red:off off:radio_unchecked:on
attr proxy_Switch1 room tuya
attr proxy_Switch1 setFn {($CMD eq "on")?fhem("set smart_power_strip_xxxxxxxxxxxxxxxxxx switch_1 on"):fhem("set smart_power_strip_xxxxxxxxxxxxxxxxxx switch_1 off");; return undef}
attr proxy_Switch1 setList on off
attr proxy_Switch1 webCmd :
ich schalte immer mit dem icon. Wenn du es anklickst sollte es schalten und sich das icon ändern. Fallst du es nicht willst, mal webcmd löschen..
Gruß
Jürgen K.
Hallo zusammen
bekomme einfach keine Geräte
tuya_connect status conncted und pybinding opened
Hi,
habe das heute auch installiert da meine Tuya sich nicht haben umflashen lassen. ID 02 Problem.
Die Installation war etwas beschwerlich auf meinem Rapberry.
Irgendwie wollte es nicht von allein.
Ich habe dann hier gefunden fhempy manuell als fhem user zu installieren.
Dann nochmal neu gestartet und dann ging es.
Jetzt habe ich alles eingerichtet und ich sehe auch die Steckdosen.
Ich habe eine Frage zur Aktualisierung.
Wenn ich in der App bin aktualisieren sich die Werte.
Wenn ich nichts mache scheinbar nicht.
Ich frage weil ich eventuell die Power Readings speichern wollte.
Wie sollte das denn laufen?
Sollte es automatisch aktualisieren? Wenn ja wie oft?
Oder muss man das irgendwie anstoßen? set relay_status last macht das zum Beispiel, muss ich das rufen damit regelmäßig updates passieren?
Was macht beim relay_status eigentlich power_on, power_off?
Und was ist countdown_1, circle_time und random_time?
Sorry für die vielen Fragen, bin noch ganz neu im Tuya ;-)
@ChrisA4, hast du die Geräte in der Tuya Iot Platform unter deinem Cloud Projekt unter Devices?
Danke und Gruß,
Stefan
Zitat von: ChrisA4 am 18 Oktober 2021, 06:05:38
Hallo zusammen
bekomme einfach keine Geräte
tuya_connect status conncted und pybinding opened
Schau mal im fhempy Log ob ein Fehler kommt. Wenn ja, bitte gleich posten.
Zitat von: stefanru am 18 Oktober 2021, 21:19:24
Hi,
habe das heute auch installiert da meine Tuya sich nicht haben umflashen lassen. ID 02 Problem.
Die Installation war etwas beschwerlich auf meinem Rapberry.
Irgendwie wollte es nicht von allein.
Ich habe dann hier gefunden fhempy manuell als fhem user zu installieren.
Dann nochmal neu gestartet und dann ging es.
Jetzt habe ich alles eingerichtet und ich sehe auch die Steckdosen.
Ich habe eine Frage zur Aktualisierung.
Wenn ich in der App bin aktualisieren sich die Werte.
Wenn ich nichts mache scheinbar nicht.
Ich frage weil ich eventuell die Power Readings speichern wollte.
Wie sollte das denn laufen?
Sollte es automatisch aktualisieren? Wenn ja wie oft?
Oder muss man das irgendwie anstoßen? set relay_status last macht das zum Beispiel, muss ich das rufen damit regelmäßig updates passieren?
Was macht beim relay_status eigentlich power_on, power_off?
Und was ist countdown_1, circle_time und random_time?
Sorry für die vielen Fragen, bin noch ganz neu im Tuya ;-)
@ChrisA4, hast du die Geräte in der Tuya Iot Platform unter deinem Cloud Projekt unter Devices?
Danke und Gruß,
Stefan
Die Readings werden immer automatisch aktualisiert. In welchen Abständen tuya die Power Readings aktualisiert, weiß ich leider nicht. Meiner Erfahrung nach passiert das bei größeren Änderungen z.B. 100W auf 10W, nicht aber bei 100W auf 100,8W.
Die Commands:
- Generell sei gesagt, ich kenne nicht alle Commands. Ich habe das Modul generisch gebaut, so dass alles was Tuya per API bereitstellt auch steuerbar ist. Das bedeutet aber auch, dass jegliche Begriffe (relay_status, usw.) von Tuya kommen. Ich empfehle einfach die Funktionen in der SmartLife App auszuprobieren und schauen welches Reading sich ändert.
- relay_status: Letzter Status nach dem stromlos machen
- countdown_1: Countdown wie in der App
- circle_time und random_time: Ist glaube ich ein String Wert, daher besser mal mit der App setzen und schauen was drin steht.
Danke Dominik,
das hilft mir sehr.
Und vielen Dank für das tolle Modul.
Dachte schon ich könnte mit den Dosen nichts anfangen weil ich sie nicht flashen konnte.
So finde ich es aber auch super.
Braucht man kein ESPEasy.
P.S.:
Doch noch eine mini Frage.
Gibt es einen unterschied zwischen SmartLife App und Tuya App?
Hatte beide drauf, sah absolut identisch aus.
Habe nun auf Tuya App alles eingerichtet.
Sollte es aber doch Sinn machen würde ich auch nochmal umstellen.
Danke und Gruß,
Stefan
Ich habe da keine großen Unterschiede bis jetzt erkennen können. Ich bin bei der SmartLife App geblieben.
Ok danke,
habe auch 0 Unterschied gesehen :-)
Vielen Dank nochmal für deine Hilfe und deine Arbeit,
Stefan
@ Stefanru: Ja in der Liste Alle Devices sind meine drei Geräte aufgelistet.
Smart led Strip xxx TC0315_TW03_STRIP3_IRRGB_P2 xxx Offline 2021-04-24 16:57:58 Debug Device
Smart Stecker xxx LSC Smart Plug(NL) xxx Online 2021-10-17 12:07:39 Debug Device
Buero xxx LSC SMART Connect Door/Window Sensor xxx Online 2021-05-02 16:32:00 Debug Device
dererste ist offline weil er nicht angesteckt ist.
@ dominik
Das ist in der log
2021.10.19 05:46:42 1: ws:127.0.0.1:15733 disconnected, waiting to reappear (local_pybinding)
2021.10.19 05:46:42 1: BindingsIo (local_pybinding): ERROR local_pybinding - error while connecting: 127.0.0.1: Verbindungsaufbau abgelehnt (111)
2021.10.19 05:46:52 1: ws:127.0.0.1:15733 reappeared (local_pybinding)
2021.10.19 05:46:52 3: BindingsIo v1.0.0
2021.10.19 05:46:55 3: Opening fhempy_peer_127_0_1_1 device ws:127.0.1.1:15733
2021.10.19 05:46:56 3: fhempy_peer_127_0_1_1 device opened
2021.10.19 05:47:11 1: RMDIR: ./restoreDir/save/2021-10-14
Ich hab null Ahnung worann es liegt
Bitte das fhempy Log (/opt/fhem/log/fhempy-.....), dort sollte etwas ersichtlich sein.
Hi,
ich habe ein kleines Problem.
Tuya Connect läuft bei mir wunderbar. Echt super.
Aber der fhempy wird beim stoppen von FEHM nicht mit gestoppt.
Das heißt wenn ich FHEM stoppe per
service fhem stop
Bleibt der fhempy laufen:
fhem 31616 1 0 15:00 ? 00:00:06 python3 FHEM/bindings/python/bin/fhempy --local
Starte ich FHEM wieder ist dann localbinding und fhempy rot.
Im log von fhempy sieht man:
2021-10-25 15:12:04,621 - WARNING - asyncio: Executing <Task pending coro=<async_main() running at /opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/fhem_pythonbinding.py:498> wait_for=<_GatheringFuture pending cb=[<TaskWakeupMethWrapper object at 0x75a40970>()] created at /usr/lib/python3.7/asyncio/tasks.py:615> cb=[_run_until_complete_cb() at /usr/lib/python3.7/asyncio/base_events.py:158] created at /usr/lib/python3.7/asyncio/base_events.py:563> took 0.112 seconds
Traceback (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/fhem_pythonbinding.py", line 505, in run
asyncio.get_event_loop().run_until_complete(async_main())
File "/usr/lib/python3.7/asyncio/base_events.py", line 584, in run_until_complete
return future.result()
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/fhem_pythonbinding.py", line 498, in async_main
pybinding, "0.0.0.0", port, ping_timeout=None, ping_interval=None
File "/opt/fhem/.local/lib/python3.7/site-packages/websockets/legacy/server.py", line 1042, in __await_impl__
server = await self._create_server()
File "/usr/lib/python3.7/asyncio/base_events.py", line 1378, in create_server
% (sa, err.strerror.lower())) from None
OSError: [Errno 98] error while attempting to bind on address ('0.0.0.0', 15733): address already in use
Stoppe ich den fhempy vor dem fhem start manuell klappt alles.
Fhempy wird gestertet und alles wird grün.
Wie gesagt ich hatte etwas Probleme beim installieren und habe fhempy manuell als fhem user installiert danach ging dann alles mit diesem kleinen problem.
Woran könnte das liegen?
Gruß,
Stefan
Hi Stefan,
wie hast du fhempy mit dem fhem User manuell installiert? Kann es sein, dass du kein fhempyServer/PythonBinding in deinem FHEM hast?
Hi Dominik,
das habe ich so gemacht wie du es hier beschrieben hast:
https://forum.fhem.de/index.php/topic,122288.msg1175292.html#msg1175292
Vorher hatte ich nach Anleitung installiert und irgendetwas ging nicht. Der Server blieb rot und es fehlten Abhängigkeiten.
Ich habe in fhem local_pybinding und fhempyserver_15733.
Es scheint auch alles einwandfrei zu funktionieren.
Hier mal ein List der 2 Devices:
fhempyserver_15733
Internals:
DEF 0
FD 63
FUUID 616d861e-f33f-0c45-df44-2b4b04fd2fa1d2a8
LAST_START 2021-10-26 09:51:48
NAME fhempyserver_15733
NR 1965
NTFY_ORDER 50-fhempyserver_15733
PID 14835
STARTS 1
STATE ???
TYPE fhempyServer
currentlogfile ./log/fhempy-2021-10-26.log
logfile ./log/fhempy-%Y-%m-%d.log
CoProcess:
cmdFn fhempyServer_getCmd
name fhempy
state running FHEM/bindings/python/bin/fhempy
READINGS:
2021-10-26 09:51:48 fhempy running FHEM/bindings/python/bin/fhempy
Attributes:
devStateIcon { my $status_img = "10px-kreis-gruen";; my $status_txt = "running";; if (substr(ReadingsVal($name, "fhempy", "running"),0,7) ne "running") { $status_img = "10px-kreis-rot";; $status_txt = "stopped";; } "<div><a>".FW_makeImage($status_img, $status_txt)."</a><a href=\"/fhem?cmd.dummy=set $name restart&XHR=1\" title=\"Restart\">".FW_makeImage("audio_repeat")."</a></div>" }
group fhempy
icon python
logfile ./log/fhempy-%Y-%m-%d.log
nrarchive 10
room fhempy
local_pybinding
Internals:
BindingType fhempy
DEF fhempy
DeviceName ws:127.0.0.1:15733
FD 72
FUUID 616d861e-f33f-0c45-d55e-237882898735bc0b
IP 127.0.0.1
NAME local_pybinding
NR 1964
NTFY_ORDER 50-local_pybinding
PARTIAL
PORT 15733
STATE opened
TYPE BindingsIo
WEBSOCKET 1
localBinding 1
nextOpenDelay 10
READINGS:
2021-10-26 09:51:57 state opened
2021-10-22 17:25:30 version 0.1.151
args:
local_pybinding
BindingsIo
fhempy
argsh:
Attributes:
devStateIcon { my $status_img = "10px-kreis-gruen";; my $status_txt = "connected";; if (ReadingsVal($name, "state", "disconnected") eq "disconnected") { $status_img = "10px-kreis-rot";; $status_txt = "disconnected";; } my $ver = ReadingsVal($name, "version", "-");; "<div><a>".FW_makeImage($status_img, $status_txt)."</a><a> ".$ver." </a><a href=\"/fhem?cmd.dummy=set $name update&XHR=1\" title=\"Start update\">".FW_makeImage("refresh")."</a></div>" }
group fhempy
icon file_json-ld2
room fhempy
Gruß und Danke,
Stefan
Hallo Zusammen,
das System legte teilweise keine neuen Devices an !
Lösung: Devicenamen: auf die Restrictionen von FHEM achten (z.B.: kein Backslash) war bei mir so.
@dominik: kann hier vielleicht ein Fehlercode angezeigt werden? Oder direkt in die richtige Form umwandeln?
Ok just tried to install all of this, i cant get the fileserver to start, the only thing my fhempy log says is:
File "FHEM/bindings/python/bin/fhempy", line 87
logging.getLogger(__name__).info(f"Successfully installed {package}")
^
SyntaxError: invalid syntax
NOTE, i am a copy/paster, not a coder! :P
My defmod is:
defmod tuya_cloud_connector fhempy tuya_cloud setup clientIDcodehere Clientsecrethere emailhere@gmail.com passwordhere tuyaSmart Europe
You need Python 3 instead of Python 2:
https://github.com/dominikkarall/fhempy#fhempy-beta
@dominik
leider kann ich meine GU10 RGBW mit FHEM nicht die Farben einstellen und schalten.
Entsprechend funktioniert auch die Einbindung in "Lightscene" nicht richtig. Hier kann ich nur
ON/OFF schalten
bright_value etc. funktioniert.
Auch die Schaltung aus der Tuya-Cloud funktioniert.
Hast du eine Idee was ich ändern muss?
Bernd
ZitatInternals:
DEF tuya_cloud tuya_cloud_connectorNEU 02200318600194719d4c
DEVICEID 02200318600194719d4c
FHEMPYTYPE tuya_cloud
FUUID 61815a43-f33f-f967-fea3-51e97d1c582b3644
FVERSION 10_PythonModule.pm:0.182830/2019-01-16
IODev local_pybinding
NAME A70RGBW_A2_02200318600194719d4c
NR 534
PYTHONTYPE tuya_cloud
STATE off
TYPE PythonModule
READINGS:
2021-11-04 15:03:25 active_time 1635785872
2021-11-04 15:03:25 biz_type 18
2021-11-06 16:14:10 bright_value 130.0
2021-11-04 15:03:25 category dj
2021-11-06 16:14:10 colour_data 28a-3ef28a
2021-11-04 15:03:25 create_time 1635577443
2021-11-06 16:14:10 flash_scene_1 {"bright":255,"frequency":80,"hsv":[{"h":120.0,"s":255.0,"v":255.0}],"temperature":255}
2021-11-06 16:14:10 flash_scene_2 {"bright":255,"frequency":128,"hsv":[{"h":0.0,"s":255.0,"v":255.0},{"h":120.0,"s":255.0,"v":255.0},{"h":240.0,"s":255.0,"v":255.0},{"h":0.0,"s":0.0,"v":0.0},{"h":0.0,"s":0.0,"v":0.0},{"h":0.0,"s":0.0,"v":0.0}],"temperature":255}
2021-11-06 16:14:10 flash_scene_3 {"bright":255,"frequency":80,"hsv":[{"h":0.0,"s":255.0,"v":255.0}],"temperature":255}
2021-11-06 16:14:10 flash_scene_4 {"bright":255,"frequency":5,"hsv":[{"h":0.0,"s":255.0,"v":255.0},{"h":120.0,"s":255.0,"v":255.0},{"h":60.0,"s":255.0,"v":255.0},{"h":300.0,"s":255.0,"v":255.0},{"h":240.0,"s":255.0,"v":255.0},{"h":0.0,"s":0.0,"v":0.0}],"temperature":255}
2021-11-04 15:03:25 icon https://images.tuyaeu.com/smart/icon/1502765611_0.png
2021-11-04 15:03:25 id 02200318600194719d4c
2021-11-04 15:03:25 ip 95.88.176.139
2021-11-04 15:03:25 lat 50.4420
2021-11-04 15:03:25 local_key 762e2286f8f6a942
2021-11-04 15:03:25 lon 7.5621
2021-11-04 15:03:25 model
2021-11-04 15:03:25 name A70RGBW_A2
2021-11-04 15:03:25 online on
2021-11-04 15:03:25 owner_id 1048434
2021-11-04 15:03:25 product_id HGZ7aIKOHk99IAoA
2021-11-04 15:03:25 product_name io-WiFiA70/GU10
2021-11-06 16:14:10 scene_data {"h":0.0,"s":0.0,"v":0.0}
2021-11-06 16:14:10 state off
2021-11-04 15:03:25 sub off
2021-11-06 16:14:10 temp_value 255.0
2021-11-04 15:03:25 time_zone +01:00
2021-11-04 15:03:25 uid eu1523555094960JvBlL
2021-11-04 15:03:25 update_time 1635866825
2021-11-04 15:03:25 uuid 02200318600194719d4c
2021-11-06 16:14:10 work_mode colour
args:
A70RGBW_A2_02200318600194719d4c
PythonModule
tuya_cloud
tuya_cloud_connectorNEU
02200318600194719d4c
argsh:
Attributes:
alias A70RGBW_A2
group tuya_cloud
room fhempy
Was hast du für Set Commands?
Zitat von: dominik am 06 November 2021, 00:25:52
You need Python 3 instead of Python 2:
https://github.com/dominikkarall/fhempy#fhempy-beta
I did before i wrote this message, also removed all 3 fempy "defines" from fhem en reinstalled them, still no change
pi@raspberrypi:~ $ sudo apt install python3 python3-pip
Reading package lists... Done
Building dependency tree
Reading state information... Done
python3 is already the newest version (3.5.3-1).
python3-pip is already the newest version (9.0.1-2+rpt2).
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
pi@raspberrypi:~ $ python --version
Python 3.10.0
Do also a check with
python3 --version
meine Set-Commands sind:
bright_value
Colour-data
flash_scene_1 bis _4
off
on
scene_data
work_mode
schau dir bitte mal bei meinem List die colour_data an?
die sind irgendwie kryptisch? die anderen sehen ganz anders aus?
HSV? HUE? RGB? wegen "Lightscene?
anbei noch n list-r
Zitatdefine A70RGBW_A1_02200318600194717fa9 PythonModule tuya_cloud tuya_cloud_connectorNEU 02200318600194717fa9
attr A70RGBW_A1_02200318600194717fa9 userattr lightSceneParamsToSave lightSceneRestoreOnlyIfChanged:1,0
attr A70RGBW_A1_02200318600194717fa9 alias A70RGBW_A1
attr A70RGBW_A1_02200318600194717fa9 genericDeviceType light
attr A70RGBW_A1_02200318600194717fa9 group tuya_cloud
attr A70RGBW_A1_02200318600194717fa9 room fhempy
setstate A70RGBW_A1_02200318600194717fa9 on
setstate A70RGBW_A1_02200318600194717fa9 2021-11-04 15:03:25 active_time 1635785914
setstate A70RGBW_A1_02200318600194717fa9 2021-11-04 15:03:25 biz_type 18
setstate A70RGBW_A1_02200318600194717fa9 2021-11-07 01:01:46 bright_value 255.0
setstate A70RGBW_A1_02200318600194717fa9 2021-11-04 15:03:25 category dj
setstate A70RGBW_A1_02200318600194717fa9 2021-11-07 01:01:46 colour_data 68-30528a
setstate A70RGBW_A1_02200318600194717fa9 2021-11-04 15:03:25 create_time 1635577439
setstate A70RGBW_A1_02200318600194717fa9 2021-11-07 01:01:46 flash_scene_1 {"bright":255,"frequency":80,"hsv":[{"h":120.0,"s":255.0,"v":255.0}],"temperature":255}
setstate A70RGBW_A1_02200318600194717fa9 2021-11-07 01:01:46 flash_scene_2 {"bright":255,"frequency":128,"hsv":[{"h":0.0,"s":255.0,"v":255.0},{"h":120.0,"s":255.0,"v":255.0},{"h":240.0,"s":255.0,"v":255.0},{"h":0.0,"s":0.0,"v":0.0},{"h":0.0,"s":0.0,"v":0.0},{"h":0.0,"s":0.0,"v":0.0}],"temperature":255}
setstate A70RGBW_A1_02200318600194717fa9 2021-11-07 01:01:46 flash_scene_3 {"bright":255,"frequency":80,"hsv":[{"h":0.0,"s":255.0,"v":255.0}],"temperature":255}
setstate A70RGBW_A1_02200318600194717fa9 2021-11-07 01:01:46 flash_scene_4 {"bright":255,"frequency":5,"hsv":[{"h":0.0,"s":255.0,"v":255.0},{"h":120.0,"s":255.0,"v":255.0},{"h":60.0,"s":255.0,"v":255.0},{"h":300.0,"s":255.0,"v":255.0},{"h":240.0,"s":255.0,"v":255.0},{"h":0.0,"s":0.0,"v":0.0}],"temperature":255}
setstate A70RGBW_A1_02200318600194717fa9 2021-11-04 15:03:25 icon https://images.tuyaeu.com/smart/icon/1502765611_0.png
setstate A70RGBW_A1_02200318600194717fa9 2021-11-04 15:03:25 id 02200318600194717fa9
setstate A70RGBW_A1_02200318600194717fa9 2021-11-04 15:03:25 ip 95.88.176.139
setstate A70RGBW_A1_02200318600194717fa9 2021-11-04 15:03:25 lat 50.4420
setstate A70RGBW_A1_02200318600194717fa9 2021-11-04 15:03:25 local_key cfc57ad6b6866db1
setstate A70RGBW_A1_02200318600194717fa9 2021-11-04 15:03:25 lon 7.5621
setstate A70RGBW_A1_02200318600194717fa9 2021-11-04 15:03:25 model
setstate A70RGBW_A1_02200318600194717fa9 2021-11-04 15:03:25 name A70RGBW_A1
setstate A70RGBW_A1_02200318600194717fa9 2021-11-04 15:03:25 online on
setstate A70RGBW_A1_02200318600194717fa9 2021-11-04 15:03:25 owner_id 1048434
setstate A70RGBW_A1_02200318600194717fa9 2021-11-04 15:03:25 product_id HGZ7aIKOHk99IAoA
setstate A70RGBW_A1_02200318600194717fa9 2021-11-04 15:03:25 product_name io-WiFiA70/GU10
setstate A70RGBW_A1_02200318600194717fa9 2021-11-07 01:01:46 scene_data {"h":0.0,"s":0.0,"v":0.0}
setstate A70RGBW_A1_02200318600194717fa9 2021-11-07 01:01:46 state on
setstate A70RGBW_A1_02200318600194717fa9 2021-11-04 15:03:25 sub off
setstate A70RGBW_A1_02200318600194717fa9 2021-11-07 01:01:46 temp_value 255.0
setstate A70RGBW_A1_02200318600194717fa9 2021-11-04 15:03:25 time_zone +01:00
setstate A70RGBW_A1_02200318600194717fa9 2021-11-04 15:03:25 uid eu1523555094960JvBlL
setstate A70RGBW_A1_02200318600194717fa9 2021-11-04 15:03:25 update_time 1636010249
setstate A70RGBW_A1_02200318600194717fa9 2021-11-04 15:03:25 uuid 02200318600194717fa9
setstate A70RGBW_A1_02200318600194717fa9 2021-11-07 01:01:46 work_mode colour
Gruß
Bernd
Zitat von: dominik am 07 November 2021, 14:59:38
Do also a check with
python3 --version
I made a mistake updating python3, the server is running now, but now this happens:
2021-11-09 11:15:07,539 - WARNING - __main__: Failed to load fhempy: No module named 'fhempy'
2021-11-09 11:15:07,540 - INFO - __main__: Attempting install of fhempy>=0.1.12
2021-11-09 11:15:27,793 - ERROR - __main__: Unable to install package fhempy>=0.1.12: WARNING: pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available.
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/fhempy/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/fhempy/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/fhempy/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/fhempy/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/fhempy/
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/fhempy/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/fhempy/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/fhempy/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/fhempy/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/fhempy/
ERROR: Could not find a version that satisfies the requirement fhempy>=0.1.12 (from versions: none)
ERROR: No matching distribution found for fhempy>=0.1.12
WARNING: pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available.
2021-11-09 11:15:27,794 - ERROR - __main__: Failed to install fhempy, exit now...It's strange because i have everything installed on the pi:
pi@raspberrypi:~ $ python3 -V
Python 3.10.0
pi@raspberrypi:~ $ openssl version
OpenSSL 1.1.0l 10 Sep 2019
EDIT: just upgraded to Buster, still same msg as above
Zitat von: bewa58 am 07 November 2021, 18:31:11
meine Set-Commands sind:
bright_value
Colour-data
flash_scene_1 bis _4
off
on
scene_data
work_mode
schau dir bitte mal bei meinem List die colour_data an?
die sind irgendwie kryptisch? die anderen sehen ganz anders aus?
HSV? HUE? RGB? wegen "Lightscene?
anbei noch n list-r
Gruß
Bernd
Wenn du colour_data set auswählst, kommt dann die RGB Auswahl?
Zitat von: xypzo am 09 November 2021, 11:23:35
I made a mistake updating python3, the server is running now, but now this happens:
2021-11-09 11:15:07,539 - WARNING - __main__: Failed to load fhempy: No module named 'fhempy'
2021-11-09 11:15:07,540 - INFO - __main__: Attempting install of fhempy>=0.1.12
2021-11-09 11:15:27,793 - ERROR - __main__: Unable to install package fhempy>=0.1.12: WARNING: pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available.
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/fhempy/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/fhempy/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/fhempy/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/fhempy/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/fhempy/
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/fhempy/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/fhempy/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/fhempy/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/fhempy/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/fhempy/
ERROR: Could not find a version that satisfies the requirement fhempy>=0.1.12 (from versions: none)
ERROR: No matching distribution found for fhempy>=0.1.12
WARNING: pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available.
2021-11-09 11:15:27,794 - ERROR - __main__: Failed to install fhempy, exit now...
It's strange because i have everything installed on the pi:
pi@raspberrypi:~ $ python3 -V
Python 3.10.0
pi@raspberrypi:~ $ openssl version
OpenSSL 1.1.0l 10 Sep 2019
EDIT: just upgraded to Buster, still same msg as above
Please set the default python 3 interpreter which is 3.7 for Buster. I assume you compiled Python 3.10 on your own and maybe you forgot some flag to activate ssl.
Hallo,
in der fhempy Logfile habe ich die folgenden Einträge.
Merkwürdig ist auch der Hinweis zum Contact_Sensor_bfe51adb47726ca7ads0pb
2021-11-12 12:12:08,005 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.193 seconds
2021-11-12 12:12:08,805 - WARNING - asyncio: Executing <Task pending name='Task-34138' coro=<tuya_cloud_device.update() running at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py:266> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x7f97f5d46d60>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> cb=[_chain_future.<locals>._call_set_state() at /usr/lib/python3.8/asyncio/futures.py:367] created at /usr/lib/python3.8/asyncio/tasks.py:922> took 0.111 seconds
2021-11-12 12:12:09,816 - WARNING - asyncio: Executing <Handle run_coroutine_threadsafe.<locals>.callback() at /usr/lib/python3.8/asyncio/tasks.py:920 created at /usr/lib/python3.8/asyncio/tasks.py:930> took 0.520 seconds
2021-11-12 12:12:10,322 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.110 seconds
2021-11-12 12:12:10,478 - WARNING - asyncio: Executing <Task pending name='Task-34138' coro=<tuya_cloud_device.update() running at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py:266> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x7f989c651370>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> cb=[_chain_future.<locals>._call_set_state() at /usr/lib/python3.8/asyncio/futures.py:367] created at /usr/lib/python3.8/asyncio/tasks.py:922> took 0.134 seconds
2021-11-12 12:14:10,105 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to execute function Set: Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/urllib3/util/ssl_.py", line 381, in ssl_wrap_socket
OSError: [Errno 24] Too many open files
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 699, in urlopen
File "/opt/fhem/.local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 382, in _make_request
File "/opt/fhem/.local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 1010, in _validate_conn
File "/opt/fhem/.local/lib/python3.8/site-packages/urllib3/connection.py", line 411, in connect
File "/opt/fhem/.local/lib/python3.8/site-packages/urllib3/util/ssl_.py", line 383, in ssl_wrap_socket
urllib3.exceptions.SSLError: [Errno 24] Too many open files
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/requests/adapters.py", line 439, in send
File "/opt/fhem/.local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 755, in urlopen
File "/opt/fhem/.local/lib/python3.8/site-packages/urllib3/util/retry.py", line 574, in increment
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='openapi.tuyaeu.com', port=443): Max retries exceeded with url: /v1.0/iot-03/users/token/f1fcf5a99a15b8f50ef25c71a95e15d8 (Caused by SSLError(OSError(24, 'Too many open files')))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 411, in _onMessage
ret = await asyncio.wait_for(
File "/usr/lib/python3.8/asyncio/tasks.py", line 494, in wait_for
return fut.result()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/generic.py", line 158, in Set
return await utils.handle_set(self._conf_set, self, hash, args, argsh)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/utils.py", line 274, in handle_set
return await fct_call(hash, final_params)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud.py", line 34, in set_boolean
await self.device.set_boolean(hash, params)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 155, in set_boolean
await self.send_commands([{"code": code, "value": onoff}])
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 202, in send_commands
await self.tuyaiot.send_commands(self._t_deviceid, commands)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 237, in send_commands
await utils.run_blocking(
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/utils.py", line 33, in run_blocking
return await asyncio.get_event_loop().run_in_executor(pool, function)
File "/usr/lib/python3.8/concurrent/futures/thread.py", line 57, in run
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/device.py", line 497, in send_commands
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/device.py", line 621, in send_commands
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openapi.py", line 324, in post
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openapi.py", line 238, in __request
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openapi.py", line 164, in __refresh_access_token_if_need
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openapi.py", line 324, in post
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openapi.py", line 267, in __request
File "/opt/fhem/.local/lib/python3.8/site-packages/requests/sessions.py", line 542, in request
File "/opt/fhem/.local/lib/python3.8/site-packages/requests/sessions.py", line 655, in send
File "/opt/fhem/.local/lib/python3.8/site-packages/requests/adapters.py", line 514, in send
requests.exceptions.SSLError: HTTPSConnectionPool(host='openapi.tuyaeu.com', port=443): Max retries exceeded with url: /v1.0/iot-03/users/token/f1fcf5a99a15b8f50ef25c71a95e15d8 (Caused by SSLError(OSError(24, 'Too many open files')))
(id: 18775936)
2021-11-12 12:14:10,129 - WARNING - urllib3.connectionpool: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f970bc44ee0>: Failed to establish a new connection: [Errno 22] Invalid argument')': /api/6031048/store/
2021-11-12 12:14:10,130 - WARNING - urllib3.connectionpool: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f98b893d520>: Failed to establish a new connection: [Errno 22] Invalid argument')': /api/6031048/store/
2021-11-12 12:14:10,130 - WARNING - urllib3.connectionpool: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f98137666d0>: Failed to establish a new connection: [Errno 22] Invalid argument')': /api/6031048/store/
2021-11-12 12:16:02,825 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.106 seconds
2021-11-12 12:16:35,477 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.173 seconds
2021-11-12 12:17:20,648 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.105 seconds
2021-11-12 12:18:50,776 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.615 seconds
2021-11-12 12:19:36,872 - WARNING - asyncio: Executing <TimerHandle when=239650.94416018456 _ServiceBrowserBase._async_send_ready_queries_schedule_next() created at /opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py:485> took 0.400 seconds
2021-11-12 12:21:52,291 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.125 seconds
2021-11-12 12:22:23,977 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.103 seconds
2021-11-12 12:24:56,016 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.127 seconds
2021-11-12 12:25:32,725 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.113 seconds
2021-11-12 12:25:32,934 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.110 seconds
2021-11-12 12:25:36,938 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.146 seconds
2021-11-12 12:26:26,299 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.147 seconds
2021-11-12 12:29:45,404 - ERROR - Contact_Sensor_bfe51adb47726ca7ads0pb: unsupported operand type(s) for ** or pow(): 'int' and 'str'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 298, in update_readings_dict
self._convert_value2fhem(st_name, status_dic[st_name]),
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 234, in _convert_value2fhem
return value / (10 ** values["scale"])
TypeError: unsupported operand type(s) for ** or pow(): 'int' and 'str'
2021-11-12 12:29:45,415 - WARNING - urllib3.connectionpool: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f94ff0e2be0>: Failed to establish a new connection: [Errno 22] Invalid argument')': /api/6031048/store/
2021-11-12 12:29:45,416 - WARNING - urllib3.connectionpool: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f94ff0e29d0>: Failed to establish a new connection: [Errno 22] Invalid argument')': /api/6031048/store/
2021-11-12 12:29:45,417 - WARNING - urllib3.connectionpool: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f96c6092340>: Failed to establish a new connection: [Errno 22] Invalid argument')': /api/6031048/store/
2021-11-12 12:29:45,662 - ERROR - Contact_Sensor_bfe51adb47726ca7ads0pb: unsupported operand type(s) for ** or pow(): 'int' and 'str'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 298, in update_readings_dict
self._convert_value2fhem(st_name, status_dic[st_name]),
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 234, in _convert_value2fhem
return value / (10 ** values["scale"])
TypeError: unsupported operand type(s) for ** or pow(): 'int' and 'str'
2021-11-12 12:29:45,675 - WARNING - urllib3.connectionpool: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f98349e6760>: Failed to establish a new connection: [Errno 22] Invalid argument')': /api/6031048/store/
2021-11-12 12:29:45,676 - WARNING - urllib3.connectionpool: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f9852deccd0>: Failed to establish a new connection: [Errno 22] Invalid argument')': /api/6031048/store/
2021-11-12 12:29:45,676 - WARNING - urllib3.connectionpool: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f9668c2ddf0>: Failed to establish a new connection: [Errno 22] Invalid argument')': /api/6031048/store/
2021-11-12 12:29:54,822 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.101 seconds
2021-11-12 12:33:49,368 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.152 seconds
2021-11-12 12:35:00,113 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to execute function Set: Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/urllib3/connection.py", line 169, in _new_conn
File "/opt/fhem/.local/lib/python3.8/site-packages/urllib3/util/connection.py", line 73, in create_connection
File "/usr/lib/python3.8/socket.py", line 918, in getaddrinfo
OSError: [Errno 22] Invalid argument
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 699, in urlopen
File "/opt/fhem/.local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 382, in _make_request
File "/opt/fhem/.local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 1010, in _validate_conn
File "/opt/fhem/.local/lib/python3.8/site-packages/urllib3/connection.py", line 353, in connect
File "/opt/fhem/.local/lib/python3.8/site-packages/urllib3/connection.py", line 181, in _new_conn
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPSConnection object at 0x7f965ab47ee0>: Failed to establish a new connection: [Errno 22] Invalid argument
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/requests/adapters.py", line 439, in send
File "/opt/fhem/.local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 755, in urlopen
File "/opt/fhem/.local/lib/python3.8/site-packages/urllib3/util/retry.py", line 574, in increment
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='openapi.tuyaeu.com', port=443): Max retries exceeded with url: /v1.0/devices/bf5ee44c2ba7b84276eueh/commands (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f965ab47ee0>: Failed to establish a new connection: [Errno 22] Invalid argument'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 411, in _onMessage
ret = await asyncio.wait_for(
File "/usr/lib/python3.8/asyncio/tasks.py", line 494, in wait_for
return fut.result()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/generic.py", line 158, in Set
return await utils.handle_set(self._conf_set, self, hash, args, argsh)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/utils.py", line 274, in handle_set
return await fct_call(hash, final_params)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud.py", line 34, in set_boolean
await self.device.set_boolean(hash, params)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 155, in set_boolean
await self.send_commands([{"code": code, "value": onoff}])
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 202, in send_commands
await self.tuyaiot.send_commands(self._t_deviceid, commands)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 237, in send_commands
await utils.run_blocking(
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/utils.py", line 33, in run_blocking
return await asyncio.get_event_loop().run_in_executor(pool, function)
File "/usr/lib/python3.8/concurrent/futures/thread.py", line 57, in run
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/device.py", line 497, in send_commands
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/device.py", line 621, in send_commands
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openapi.py", line 324, in post
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openapi.py", line 267, in __request
File "/opt/fhem/.local/lib/python3.8/site-packages/requests/sessions.py", line 542, in request
File "/opt/fhem/.local/lib/python3.8/site-packages/requests/sessions.py", line 655, in send
File "/opt/fhem/.local/lib/python3.8/site-packages/requests/adapters.py", line 516, in send
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='openapi.tuyaeu.com', port=443): Max retries exceeded with url: /v1.0/devices/bf5ee44c2ba7b84276eueh/commands (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f965ab47ee0>: Failed to establish a new connection: [Errno 22] Invalid argument'))
(id: 30716344)
2021-11-12 12:35:00,132 - WARNING - urllib3.connectionpool: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f94e6f7c670>: Failed to establish a new connection: [Errno 22] Invalid argument')': /api/6031048/store/
2021-11-12 12:35:00,133 - WARNING - urllib3.connectionpool: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f94e6f7c4f0>: Failed to establish a new connection: [Errno 22] Invalid argument')': /api/6031048/store/
2021-11-12 12:35:00,133 - WARNING - urllib3.connectionpool: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f94e6f7c6a0>: Failed to establish a new connection: [Errno 22] Invalid argument')': /api/6031048/store/
2021-11-12 12:37:04,851 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.168 seconds
2021-11-12 12:39:29,853 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.102 seconds
2021-11-12 12:41:04,747 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.116 seconds
2021-11-12 12:42:33,901 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.193 seconds
2021-11-12 12:43:48,579 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.106 seconds
Kann mir jemand helfen, was ich ändern müsste?
Vielen Dank
Hi,
hast du nur tuya_cloud im Einsatz oder auch andere Module? Mich würde nämlich interessieren, ob die hier
Zitat2021-11-12 12:37:04,851 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.168 seconds
von der tuya Library kommen.
Zum Contact Sensor:
Log dich bitte auf der tuya iot Plattform ein und wähle beim Contact Sensor "Debug Device" aus - siehe Screenshot. Dann kommt ein neues Fenster und dort wählst du "Device Debugging" aus. Da kommt dann eine Übersicht - bitte Standard Status Set auswählen. Sieht z.B. so aus:
switch_1 Boolean
"{true,false}"
countdown_1 Integer
{
"unit": "s",
"min": 0,
"max": 86400,
"scale": 0,
"step": 1
}
relay_status Enum
{
"range": [
"power_off",
"power_on",
"last"
]
}
cycle_time String
{}
random_time String
{}Das kopiere bitte hier rein.
Guten Morgen Dominik,
Ja, ich habe tuya_cloud im Einsatz.
Ich nutze auch noch googlecast.
ZitatLog dich bitte auf der tuya iot Plattform ein und wähle beim Contact Sensor "Debug Device" aus - siehe Screenshot. Dann kommt ein neues Fenster und dort wählst du "Device Debugging" aus. Da kommt dann eine Übersicht - bitte Standard Status Set auswählen. Sieht z.B. so aus:
Es wird nichts angezeigt, nur die Meldung:
An unexpected error has occurred.
Wo kommt diese Fehlermeldung? Auf der iot Plattform? Poste bitte einen Screenshot dazu.
Hallo,
ZitatWo kommt diese Fehlermeldung? Auf der iot Plattform?
Ja, wenn ich Device Debugging aufrufe
Das ist ja eigenartig, was ist das für ein Device?
Ich bau mal einen Fix ein, aber wieso der Fehler kommt ist mir nicht klar.
Hier das List
Internals:
.AttrList IODev:local_pybinding event-aggregator event-min-interval event-on-change-reading event-on-update-reading oldreadings stateFormat:textField-long timestamp-on-change-reading
.FhemMetaInternals 1
DEF tuya_cloud tuya_cloud_connector bfe51adb47726ca7ads0pb
DEVICEID bfe51adb47726ca7ads0pb
FHEMPYTYPE tuya_cloud
FUUID 6161ecb2-f33f-3b5c-eebd-6271c1833636c5a9
FVERSION 10_PythonModule.pm:0.182830/2019-01-16
IODev local_pybinding
NAME Contact_Sensor_bfe51adb47726ca7ads0pb
NR 1200
PYTHONTYPE tuya_cloud
STATE closed
TYPE PythonModule
.attraggr:
.attrminint:
READINGS:
2021-11-13 09:28:05 active_time 1633807537
2021-11-13 09:28:05 biz_type 0
2021-11-13 09:28:05 category mcs
2021-11-13 09:28:05 create_time 1633807537
2021-11-13 09:28:05 icon https://images.tuyaeu.com/smart/icon/ay1537847617560vAgbw/5526564c1ac295a5a9eeea014fb2d02e.jpg
2021-11-13 09:28:05 id bfe51adb47726ca7ads0pb
2021-11-13 09:28:05 ip 93.203.78.66
2021-11-13 09:28:05 lat 52.8048
2021-11-13 09:28:05 local_key 934b787a5ee3ce02
2021-11-13 09:28:05 lon 13.0446
2021-11-13 09:28:05 model MC400D
2021-11-13 09:28:05 name Contact Sensor
2021-11-13 09:28:05 online on
2021-11-13 09:28:05 owner_id 15487476
2021-11-13 09:28:05 product_id 5etnzhfidcmm0ang
2021-11-13 09:28:05 product_name Contact Sensor
2021-11-13 09:28:13 state closed
2021-11-13 09:28:05 sub off
2021-11-13 09:28:05 time_zone +02:00
2021-11-13 09:28:05 uid eu1598817427882BAzmt
2021-11-13 09:28:05 update_time 1636790408
2021-11-13 09:28:05 uuid 902c4e13a28b5504
args:
Contact_Sensor_bfe51adb47726ca7ads0pb
PythonModule
tuya_cloud
tuya_cloud_connector
bfe51adb47726ca7ads0pb
argsh:
Attributes:
alias Contact Sensor
group tuya_cloud
room Tuya
ZitatWenn du colour_data set auswählst, kommt dann die RGB Auswahl?
beim set-Befehl clour-data wird der color-picker angezeigt. Kann dann Farbe wählen
und dann ?
anbei 3 Bilder vom Device: 1. Farbe rot ist eingestellt
-dann set colour-data aufgerufen, Farbe auf Grün eingestellt
2. set Befehl ausgeführt
3. nach set-Befehl (und die Farbe im Leuchtmittel wird auf Standard-Weis eingestellt)
? RGB Color 6 Zeichen Colour_data 10 Zeichen ? und dort sind nach dem set nur die Standard 6 Zeichen
Kannst du bitte mal auf die iot Plattform von tuya schauen, dort beim Device selbst "Debug Device" auswählen und dann Standard Status Set auswählen? Da sollte bei colour_data ein Wert stehen, das bitte hier posten. Da dürfte die Konvertierung nicht korrekt sein.
Bitte 0.1.174 testen, ich denke ich habe den Fehler gefunden.
Hi Dominik,
kannst du mir sagen wer beim stop von fhem den fhempyserver_15733 stoppen sollte?
Ich habe nochmal alle logfiles durchsucht und leider nichts zum stoppen gefunden.
Gestartet wird er ja von FHEM beim start.
Das einzige was ich in den Logs finde ist:
eventTypes.txt:580 fhempyserver_15733 fhempy: running FHEM/bindings/python/bin/fhempy
eventTypes.txt:573 fhempyserver_15733 fhempy: stopped
eventTypes.txt:2 fhempyserver_15733 fhempy: stopping
fhem.save:setstate fhempyserver_15733 2021-11-16 11:33:12 fhempy running FHEM/bindings/python/bin/fhempy
fhem.save_old:setstate fhempyserver_15733 2021-10-22 21:33:02 fhempy running FHEM/bindings/python/bin/fhempy
Gruß und Danke,
Stefan
Zitat von: dominik am 11 November 2021, 19:43:37
Please set the default python 3 interpreter which is 3.7 for Buster. I assume you compiled Python 3.10 on your own and maybe you forgot some flag to activate ssl.
As i said before, i have no clue what i am doing! I am a copy paster, I search for a solution on the web en and copy paste it.
No idea how to switch between 3.10 and 3.7.3. All i can find is by making an alternetive, but there is no 3.10 in my usr/bin folder, just 2.7 and 3.7 .
Also downloading 3.10 to that folder is not working
CLUELESS :-X
ZitatBitte 0.1.174 testen, ich denke ich habe den Fehler gefunden
Update auf 0.1.174 gemacht.
Funktioniert jetzt !
Danke.
Zitat von: stefanru am 16 November 2021, 11:45:45
Hi Dominik,
kannst du mir sagen wer beim stop von fhem den fhempyserver_15733 stoppen sollte?
Ich habe nochmal alle logfiles durchsucht und leider nichts zum stoppen gefunden.
Gestartet wird er ja von FHEM beim start.
Das einzige was ich in den Logs finde ist:
eventTypes.txt:580 fhempyserver_15733 fhempy: running FHEM/bindings/python/bin/fhempy
eventTypes.txt:573 fhempyserver_15733 fhempy: stopped
eventTypes.txt:2 fhempyserver_15733 fhempy: stopping
fhem.save:setstate fhempyserver_15733 2021-11-16 11:33:12 fhempy running FHEM/bindings/python/bin/fhempy
fhem.save_old:setstate fhempyserver_15733 2021-10-22 21:33:02 fhempy running FHEM/bindings/python/bin/fhempy
Gruß und Danke,
Stefan
Das fhempyServer Modul stoppt auch den Server beim Shutdown. Genauso wird fhempy durch das fhempyServer Modul gestartet.
Zitat von: xypzo am 16 November 2021, 14:37:09
As i said before, i have no clue what i am doing! I am a copy paster, I search for a solution on the web en and copy paste it.
No idea how to switch between 3.10 and 3.7.3. All i can find is by making an alternetive, but there is no 3.10 in my usr/bin folder, just 2.7 and 3.7 .
Also downloading 3.10 to that folder is not working
CLUELESS :-X
Ok, you did some copy/paste in the past which installed 3.10. Please check how to uninstall that manual 3.10 installation. As I haven't installed python manually yet, I would also need to google it.
Zitat von: bewa58 am 16 November 2021, 19:13:12
Update auf 0.1.174 gemacht.
Funktioniert jetzt !
Danke.
Super, danke für die Rückmeldung!
ZitatZitat von: bewa58 am 16 November 2021, 19:13:12
Update auf 0.1.174 gemacht.
Funktioniert jetzt !
Danke.
Super, danke für die Rückmeldung!
Die Farbeinstellung über den Color-Picker funktioniert einwandfrei !
Neues Problem: nehme ich den angezeigten Wert aus Reading colour_data
und setze diesen über set Device colour-Data rgb??? ab schmiert das Programm ab.
Setze ich diesen set-Befahl über "Lightscene" ab schmiert FHEM komplett ab !!
Möchte die Lampen in "Lightscene" einbinden !
Verstehe ich das richtig?
Der Color-Picker zeigt RGB Wert an, dieser wird umgerechnet in ? welchen -Wert
und dann nochmal für die Übermittlung an Tuya-Cloud formatiert?
Auch erkennt Lightscene die Werte in den Readings nicht.
Kannst mir evtl. zeigen wie der set Befehl aussehen muss? Sind das HSV Werte?
Bernd
Schick mir Mal was aktuell im colour_data für Werte drin stehen. Sollte nämlich FHEM RGB Hex sein.
Hi Dominik,
ach so klar.
Dann schaue ich mal im fhempyServer Modul was da nicht klappt.
Danke,
Stefan
ZitatNeues Problem: nehme ich den angezeigten Wert aus Reading colour_data
und setze diesen über set Device colour-Data rgb??? ab schmiert das Programm ab.
Setze ich diesen set-Befahl über "Lightscene" ab schmiert FHEM komplett ab !!
Das Problem hat sich zwischenzeitlich erledigt.
nach einigem Probieren habe ich FHEM neu gestartet, dann funktioniert es.
Heute ein weiteres Device angelegt (RGBW Fluter),
gleiche und andere Probleme, erst nach Neustart FHEM funktioniert nun alles.
TIPP: Wenn neues DEVICE angelegt Neustart FHEM durchführen.
Gruß
Bernd
Kannst du mir bitte etwas genauer beschreiben was für Probleme das waren? Ein Neustart sollte nämlich nicht notwendig sein. Steht was im fhempy Log dazu?
Probleme bei Neuanlage von Licht-Devices:
1. kein Update der Readings wenn über ALEXA oder Smart-Life App Änderungen vorgenommen wurden
2. set Anweisungen in FHEM wurden nicht oder nur sporadisch ausgeführt, die Readings wurden nicht aktualisiert
Im LOG nichts zu finden
LOG FHEM hab ich auch nach Meldungen gesucht verbose 5 eingestellt: keinerlei Meldungen im FHEM log !
Nach Neustart alles ok.
Hallo Dominik,
mein Fhem Server stürzt nach ca. 8 Stunden immer wieder wegen über 100% CPU Überlastung
bei python3 ab. Nach einem Neustart läuft dann alles wieder normal bis zum nächsten Absturz.
PID USER PR NI VIRT RES SHR S %CPU %MEM ZEIT+ BEFEHL
1052366 fhem 20 0 35,7g 453568 9416 R 142,2 5,7 854:49.54 python3
821686 armin 20 0 16,4g 74848 38916 S 15,5 0,9 39:16.19 chrome
1956 armin 20 0 4038816 222740 48972 R 14,2 2,8 35:34.01 gnome-s+
821644 armin 20 0 16,5g 190532 100332 S 10,6 2,4 27:20.52 chrome
821958 armin 20 0 24,4g 114260 70264 S 6,6 1,4 72:12.54 chrome
1754 armin 20 0 755272 31072 11104 S 4,6 0,4 34:01.99 Xorg
1050930 armin 20 0 815832 37976 25260 S 0,7 0,5 0:01.99 gnome-t+
1113348 root 20 0 0 0 0 I 0,7 0,0 0:00.86 kworker+
1113526 armin 20 0 12484 4212 3416 R 0,7 0,1 0:00.32 top
113 root 0 -20 0 0 0 I 0,3 0,0 0:35.79 kworker+
317359 armin 20 0 1971408 210080 29332 S 0,3 2,6 42:38.39 dropbox
821688 armin 20 0 16,3g 69968 49428 S 0,3 0,9 8:34.42 chrome
1052347 fhem 20 0 455600 274412 9396 R 0,3 3,4 83:30.08 perl
1110347 root 20 0 0 0 0 I 0,3 0,0 0:00.12 kworker+
1 root 20 0 169832 11456 5800 S 0,0 0,1 0:53.31 systemd
2 root 20 0 0 0 0 S 0,0 0,0 0:00.21 kthreadd
3 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 rcu_gp
Es scheint so, als ob python3 nicht abgearbeitet wird. Hast du einen Tipp,
was ich machen könnte? Nachfolgend das fhempy_log vom gestrigen Tag
nach einem Neustart.
[code]2021-11-20 08:33:37,221 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-11-20 08:33:37,240 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-11-20 08:33:37,298 - INFO - websockets.server: server listening on 0.0.0.0:15733
2021-11-20 08:33:52,405 - INFO - websockets.server: connection open
2021-11-20 08:33:52,406 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-11-20 08:35:32,605 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-11-20 08:35:32,612 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-11-20 08:35:32,638 - INFO - websockets.server: server listening on 0.0.0.0:15733
2021-11-20 08:36:07,483 - INFO - websockets.server: connection open
2021-11-20 08:36:07,484 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-11-20 08:36:19,539 - WARNING - asyncio: Executing <Task pending name='Task-583' coro=<spotify.connect_spotipy() running at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/spotify/spotify.py:218> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at /usr/lib/python3.8/asyncio/futures.py:360, <TaskWakeupMethWrapper object at 0x7f14e9c3f340>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> created at /usr/lib/python3.8/asyncio/tasks.py:382> took 0.216 seconds
2021-11-20 08:36:24,722 - DEBUG - Castdevice_Aussenbereich: Start discovery
2021-11-20 08:41:09,658 - INFO - fhempy.lib.pkg_installer: Attempting install of fhempy
2021-11-20 08:41:14,658 - INFO - fhempy.lib.pkg_installer: Successfully installed fhempy update!
2021-11-20 08:41:15,807 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-11-20 08:41:15,814 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-11-20 08:41:15,839 - INFO - websockets.server: server listening on 0.0.0.0:15733
2021-11-20 08:41:24,966 - INFO - websockets.server: connection open
2021-11-20 08:41:24,970 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-11-20 08:41:29,428 - DEBUG - Castdevice_Aussenbereich: Start discovery
2021-11-20 08:41:30,287 - WARNING - asyncio: Executing <Task pending name='Task-621' coro=<run_blocking() running at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/utils.py:33> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at /usr/lib/python3.8/asyncio/futures.py:360, <TaskWakeupMethWrapper object at 0x7fd0e49dbca0>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> created at /usr/lib/python3.8/asyncio/tasks.py:382> took 0.100 seconds
2021-11-20 08:43:52,483 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-11-20 08:43:52,491 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-11-20 08:43:52,519 - INFO - websockets.server: server listening on 0.0.0.0:15733
2021-11-20 08:44:35,138 - INFO - websockets.server: connection failed (400 Bad Request)
2021-11-20 08:44:35,140 - INFO - websockets.server: connection closed
2021-11-20 08:44:37,081 - INFO - websockets.server: connection open
2021-11-20 08:44:37,082 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-11-20 08:44:44,578 - DEBUG - Castdevice_Aussenbereich: Start discovery
2021-11-20 08:45:18,497 - ERROR - pychromecast.socket_client: [Google-Nest(192.168.178.28):8009] Failed to connect to service ServiceInfo(type='mdns', data='google-nest-hub-5c8f0c586b0fcf88151443201b9df76a._googlecast._tcp.local.'), retrying in 5.0s
2021-11-20 09:21:33,585 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.117 seconds
2021-11-20 10:14:19,838 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.216 seconds
2021-11-20 10:21:38,998 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.221 seconds
2021-11-20 10:30:12,515 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.236 seconds
2021-11-20 10:30:13,007 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.161 seconds
2021-11-20 10:30:13,867 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.113 seconds
2021-11-20 10:30:14,664 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.138 seconds
2021-11-20 10:30:15,326 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.280 seconds
2021-11-20 10:30:16,406 - WARNING - asyncio: Executing <Handle _release_waiter(<Future finis...events.py:422>)(<Task finishe.../tasks.py:475>) at /usr/lib/python3.8/asyncio/tasks.py:429 created at /usr/lib/python3.8/asyncio/events.py:81> took 0.135 seconds
2021-11-20 10:30:18,568 - WARNING - asyncio: Executing <Task pending name='Task-6' coro=<WebSocketServerProtocol.handler() running at /opt/fhem/.local/lib/python3.8/site-packages/websockets/legacy/server.py:224> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x7f450605fd00>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> created at /opt/fhem/.local/lib/python3.8/site-packages/websockets/legacy/server.py:141> took 0.181 seconds
2021-11-20 10:35:22,489 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.360 seconds
2021-11-20 10:41:02,259 - WARNING - asyncio: Executing <TimerHandle when=924936.4742631689 _ServiceBrowserBase._async_send_ready_queries_schedule_next() created at /opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py:485> took 0.257 seconds
2021-11-20 10:53:28,909 - WARNING - asyncio: Executing <TimerHandle when=925683.0969688209 _ServiceBrowserBase._async_send_ready_queries_schedule_next() created at /opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py:485> took 0.284 seconds
2021-11-20 11:05:31,466 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.311 seconds
2021-11-20 11:19:08,172 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.311 seconds
2021-11-20 12:24:57,559 - WARNING - asyncio: Executing <TimerHandle when=931171.6471141931 _ServiceBrowserBase._async_send_ready_queries_schedule_next() created at /opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py:485> took 0.385 seconds
2021-11-20 12:26:05,959 - WARNING - asyncio: Executing <Task pending name='Task-651' coro=<spotify.update_playback_loop() running at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/spotify/spotify.py:237> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at /usr/lib/python3.8/asyncio/futures.py:360, <TaskWakeupMethWrapper object at 0x7f447f8f30a0>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> created at /usr/lib/python3.8/asyncio/tasks.py:382> took 0.416 seconds
2021-11-20 12:29:29,289 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.421 seconds
2021-11-20 12:48:10,815 - WARNING - spotipy.cache_handler: Couldn't read cache at: .spoti_spotify_token
2021-11-20 12:48:10,816 - INFO - spotipy.oauth2: User authentication requires interaction with your web browser. Once you enter your credentials and give authorization, you will be redirected to a url. Paste that url you were directed to to complete the authorization.
2021-11-20 12:48:10,817 - INFO - spotipy.oauth2: Opened https://accounts.spotify.com/authorize?client_id=e92855a009e74eb69ba6609d3bfd7d96&response_type=code&redirect_uri=https%3A%2F%2Feurope-west1-fhem-ga-connector.cloudfunctions.net%2Fcodelanding%2Fstart&code_challenge_method=S256&code_challenge=5RI3KosYyuf5TgtUErCkVTrm6PIgtYQgD1NsJ1-9zLg&scope=user-read-recently-played+user-top-read+user-read-playback-position+user-read-playback-state+user-modify-playback-state+user-read-currently-playing+streaming+playlist-read-private+playlist-read-collaborative+user-follow-read+user-library-read+user-read-email+user-read-private in your browser
Enter the URL you were redirected to: 2021-11-20 12:49:50,922 - WARNING - spotipy.cache_handler: Couldn't read cache at: .spoti_spotify_token
2021-11-20 12:49:50,923 - INFO - spotipy.oauth2: User authentication requires interaction with your web browser. Once you enter your credentials and give authorization, you will be redirected to a url. Paste that url you were directed to to complete the authorization.
2021-11-20 12:49:50,924 - INFO - spotipy.oauth2: Opened https://accounts.spotify.com/authorize?client_id=e92855a009e74eb69ba6609d3bfd7d96&response_type=code&redirect_uri=https%3A%2F%2Feurope-west1-fhem-ga-connector.cloudfunctions.net%2Fcodelanding%2Fstart&code_challenge_method=S256&code_challenge=5RI3KosYyuf5TgtUErCkVTrm6PIgtYQgD1NsJ1-9zLg&scope=user-read-recently-played+user-top-read+user-read-playback-position+user-read-playback-state+user-modify-playback-state+user-read-currently-playing+streaming+playlist-read-private+playlist-read-collaborative+user-follow-read+user-library-read+user-read-email+user-read-private in your browser
Enter the URL you were redirected to: 2021-11-20 12:57:33,205 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 1.059 seconds
2021-11-20 12:57:34,324 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.347 seconds
2021-11-20 12:57:34,625 - WARNING - asyncio: Executing <Handle run_coroutine_threadsafe.<locals>.callback() at /usr/lib/python3.8/asyncio/tasks.py:920 created at /usr/lib/python3.8/asyncio/tasks.py:930> took 0.145 seconds
2021-11-20 12:57:34,997 - WARNING - asyncio: Executing <Handle run_coroutine_threadsafe.<locals>.callback() at /usr/lib/python3.8/asyncio/tasks.py:920 created at /usr/lib/python3.8/asyncio/tasks.py:930> took 0.336 seconds
2021-11-20 12:57:35,759 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.196 seconds
2021-11-20 12:57:36,135 - WARNING - asyncio: Executing <Task pending name='Task-32464' coro=<googlecast.do_set_speak() running at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/googlecast/googlecast.py:312> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x7f439c813310>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> created at /usr/lib/python3.8/asyncio/tasks.py:382> took 0.159 seconds
2021-11-20 12:57:37,659 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.781 seconds
2021-11-20 12:57:39,026 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.302 seconds
2021-11-20 12:57:39,208 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.152 seconds
2021-11-20 12:57:39,622 - WARNING - asyncio: Executing <Handle run_coroutine_threadsafe.<locals>.callback() at /usr/lib/python3.8/asyncio/tasks.py:920 created at /usr/lib/python3.8/asyncio/tasks.py:930> took 0.335 seconds
2021-11-20 13:02:36,772 - WARNING - asyncio: Executing <TimerHandle when=933430.8405506731 _ServiceBrowserBase._async_send_ready_queries_schedule_next() created at /opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py:485> took 0.403 seconds
2021-11-20 13:02:47,346 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.396 seconds
2021-11-20 13:02:47,503 - WARNING - asyncio: Executing <Task pending name='Task-36720' coro=<send_and_wait() running at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem.py:307> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x7f447f01abe0>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> cb=[_release_waiter(<Future pendi...events.py:422>)() at /usr/lib/python3.8/asyncio/tasks.py:429] created at /usr/lib/python3.8/asyncio/tasks.py:475> took 0.156 seconds
2021-11-20 13:02:49,815 - WARNING - asyncio: Executing <Handle run_coroutine_threadsafe.<locals>.callback() at /usr/lib/python3.8/asyncio/tasks.py:920 created at /usr/lib/python3.8/asyncio/tasks.py:930> took 0.408 seconds
2021-11-20 13:02:51,687 - WARNING - asyncio: Executing <Handle run_coroutine_threadsafe.<locals>.callback() at /usr/lib/python3.8/asyncio/tasks.py:920 created at /usr/lib/python3.8/asyncio/tasks.py:930> took 0.132 seconds
2021-11-20 13:02:54,474 - WARNING - asyncio: Executing <Handle run_coroutine_threadsafe.<locals>.callback() at /usr/lib/python3.8/asyncio/tasks.py:920 created at /usr/lib/python3.8/asyncio/tasks.py:930> took 0.168 seconds
2021-11-20 13:02:55,193 - WARNING - asyncio: Executing <Handle run_coroutine_threadsafe.<locals>.callback() at /usr/lib/python3.8/asyncio/tasks.py:920 created at /usr/lib/python3.8/asyncio/tasks.py:930> took 0.402 seconds
2021-11-20 13:18:00,435 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.105 seconds
2021-11-20 13:25:14,600 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.444 seconds
2021-11-20 13:37:08,581 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.404 seconds
2021-11-20 13:37:55,701 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.436 seconds
2021-11-20 13:39:17,216 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.109 seconds
2021-11-20 13:45:30,072 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.101 seconds
2021-11-20 13:46:16,307 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.108 seconds
2021-11-20 13:49:39,764 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.105 seconds
2021-11-20 13:52:26,141 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.129 seconds
2021-11-20 13:53:57,923 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.223 seconds
2021-11-20 13:54:19,267 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.108 seconds
2021-11-20 13:54:21,271 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.123 seconds
2021-11-20 13:54:21,539 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.151 seconds
2021-11-20 13:54:21,752 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.139 seconds
2021-11-20 13:54:22,085 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.209 seconds
2021-11-20 13:54:22,308 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.170 seconds
2021-11-20 13:54:22,856 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.156 seconds
2021-11-20 13:54:23,018 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.112 seconds
2021-11-20 13:54:23,311 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.113 seconds
2021-11-20 13:54:23,427 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.102 seconds
2021-11-20 13:54:23,719 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.111 seconds
2021-11-20 13:54:23,941 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.116 seconds
2021-11-20 13:54:24,198 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.249 seconds
2021-11-20 13:54:24,319 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.120 seconds
2021-11-20 13:54:24,526 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.205 seconds
2021-11-20 13:54:24,673 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.123 seconds
2021-11-20 13:54:24,837 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.162 seconds
2021-11-20 13:54:25,360 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.314 seconds
2021-11-20 13:54:25,628 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.224 seconds
2021-11-20 13:54:25,779 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.151 seconds
2021-11-20 13:54:26,167 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.332 seconds
2021-11-20 13:54:26,358 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.182 seconds
2021-11-20 13:54:26,493 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.109 seconds
2021-11-20 13:54:26,685 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.150 seconds
2021-11-20 13:54:26,829 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.127 seconds
2021-11-20 13:54:26,997 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.120 seconds
2021-11-20 13:54:27,346 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.294 seconds
2021-11-20 13:54:27,528 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.179 seconds
2021-11-20 13:54:28,252 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.389 seconds
2021-11-20 13:54:28,422 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.169 seconds
2021-11-20 13:54:28,904 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.167 seconds
2021-11-20 13:54:29,192 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.261 seconds
2021-11-20 13:54:29,474 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.104 seconds
2021-11-20 13:54:30,242 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.439 seconds
2021-11-20 13:54:30,441 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.189 seconds
2021-11-20 13:54:30,715 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.121 seconds
2021-11-20 13:54:31,752 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.134 seconds
2021-11-20 13:54:32,888 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.265 seconds
2021-11-20 13:54:33,918 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.334 seconds
2021-11-20 13:54:34,226 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.285 seconds
2021-11-20 13:54:34,515 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.262 seconds
2021-11-20 13:54:34,830 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.313 seconds
2021-11-20 13:54:35,069 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.208 seconds
2021-11-20 13:54:35,187 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.101 seconds
2021-11-20 13:54:35,333 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.118 seconds
2021-11-20 13:54:35,615 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.129 seconds
2021-11-20 13:54:35,785 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.110 seconds
2021-11-20 13:54:36,180 - WARNING - asyncio: Executing <TimerHandle when=936550.308275907 AsyncEngine._async_cache_cleanup() created at /opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py:178> took 0.141 seconds
2021-11-20 13:54:36,671 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.224 seconds
2021-11-20 13:54:36,886 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.157 seconds
2021-11-20 13:54:37,331 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.159 seconds
2021-11-20 13:54:37,528 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.138 seconds
2021-11-20 13:54:37,836 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.259 seconds
2021-11-20 13:54:39,549 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 1.507 seconds
2021-11-20 13:54:39,885 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.285 seconds
2021-11-20 13:54:40,098 - WARNING - asyncio: Executing <TimerHandle when=936553.2798882081 _ServiceBrowserBase._async_send_ready_queries_schedule_next() created at /opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py:485> took 0.130 seconds
2021-11-20 13:54:40,488 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.229 seconds
2021-11-20 13:54:40,735 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.138 seconds
2021-11-20 13:54:40,877 - WARNING - asyncio: Executing <Handle run_coroutine_threadsafe.<locals>.callback() at /usr/lib/python3.8/asyncio/tasks.py:920 created at /usr/lib/python3.8/asyncio/tasks.py:930> took 0.108 seconds
2021-11-20 13:54:41,124 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.112 seconds
2021-11-20 13:54:41,547 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.269 seconds
2021-11-20 13:54:42,267 - WARNING - asyncio: Executing <Handle run_coroutine_threadsafe.<locals>.callback() at /usr/lib/python3.8/asyncio/tasks.py:920 created at /usr/lib/python3.8/asyncio/tasks.py:930> took 0.111 seconds
2021-11-20 13:54:42,507 - WARNING - asyncio: Executing <Task finished name='Task-42549' coro=<ServiceInfo.async_request() done, defined at /opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/info.py:460> result=True created at /usr/lib/python3.8/asyncio/tasks.py:922> took 0.119 seconds
2021-11-20 13:54:42,618 - WARNING - asyncio: Executing <TimerHandle when=936556.657960301 _ServiceBrowserBase._async_send_ready_queries_schedule_next() created at /opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py:485> took 0.109 seconds
2021-11-20 13:54:42,797 - WARNING - asyncio: Executing <TimerHandle when=936556.6579633191 _ServiceBrowserBase._async_send_ready_queries_schedule_next() created at /opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py:485> took 0.143 seconds
2021-11-20 13:54:43,029 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.100 seconds
2021-11-20 13:54:43,274 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.129 seconds
2021-11-20 13:54:43,511 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.191 seconds
2021-11-20 13:54:43,994 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.109 seconds
2021-11-20 13:54:44,189 - WARNING - asyncio: Executing <TimerHandle when=936558.540790765 _ServiceBrowserBase._async_send_ready_queries_schedule_next() created at /opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py:485> took 0.102 seconds
2021-11-20 13:55:21,730 - WARNING - asyncio: Executing <TimerHandle when=936595.851637029 _ServiceBrowserBase._async_send_ready_queries_schedule_next() created at /opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py:485> took 0.140 seconds
2021-11-20 13:55:21,899 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.167 seconds
2021-11-20 13:56:30,692 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.168 seconds
2021-11-20 13:58:20,142 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.107 seconds
2021-11-20 13:58:34,258 - WARNING - asyncio: Executing <TimerHandle when=936788.507797718 _ServiceBrowserBase._async_send_ready_queries_schedule_next() created at /opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py:485> took 0.134 seconds
2021-11-20 13:58:34,381 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.121 seconds
2021-11-20 13:59:19,137 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.220 seconds
2021-11-20 14:00:06,117 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.162 seconds
2021-11-20 14:00:36,773 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.125 seconds
2021-11-20 14:00:38,813 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.104 seconds
2021-11-20 14:00:39,943 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.252 seconds
2021-11-20 14:00:41,528 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.133 seconds
2021-11-20 14:00:41,719 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.120 seconds
2021-11-20 14:00:48,927 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.202 seconds
2021-11-20 14:01:35,770 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.100 seconds
2021-11-20 14:01:39,558 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.107 seconds
2021-11-20 14:03:09,514 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.152 seconds
2021-11-20 14:03:14,385 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.142 seconds
2021-11-20 14:04:06,783 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.119 seconds
2021-11-20 14:04:28,719 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.159 seconds
2021-11-20 14:04:31,651 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.116 seconds
2021-11-20 14:04:32,727 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.184 seconds
2021-11-20 14:04:39,697 - WARNING - asyncio: Executing <Handle run_coroutine_threadsafe.<locals>.callback() at /usr/lib/python3.8/asyncio/tasks.py:920 created at /usr/lib/python3.8/asyncio/tasks.py:930> took 0.153 seconds
2021-11-20 14:04:39,861 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.128 seconds
2021-11-20 14:04:49,326 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.120 seconds
2021-11-20 14:05:19,443 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.169 seconds
2021-11-20 14:05:24,071 - WARNING - asyncio: Executing <TimerHandle when=937198.0359252191 _ServiceBrowserBase._async_send_ready_queries_schedule_next() created at /opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py:485> took 0.507 seconds
2021-11-20 14:05:24,565 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.182 seconds
2021-11-20 14:06:12,846 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.162 seconds
2021-11-20 14:06:16,138 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.113 seconds
2021-11-20 14:06:36,363 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.154 seconds
2021-11-20 14:06:39,966 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.119 seconds
2021-11-20 14:06:49,813 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.103 seconds
2021-11-20 14:06:56,120 - WARNING - asyncio: Executing <TimerHandle when=937290.098523227 _ServiceBrowserBase._async_send_ready_queries_schedule_next() created at /opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py:485> took 0.132 seconds
2021-11-20 14:06:56,235 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.103 seconds
2021-11-20 14:06:57,230 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.138 seconds
2021-11-20 14:06:59,286 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.235 seconds
2021-11-20 14:07:36,812 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.106 seconds
2021-11-20 14:07:41,452 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.301 seconds
2021-11-20 14:08:28,450 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.139 seconds
2021-11-20 14:10:52,751 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.133 seconds
2021-11-20 14:10:53,896 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.162 seconds
2021-11-20 14:13:26,885 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.112 seconds
2021-11-20 14:14:49,904 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.116 seconds
2021-11-20 14:14:50,625 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.104 seconds
2021-11-20 14:15:10,366 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.118 seconds
2021-11-20 14:15:38,559 - WARNING - asyncio: Executing <TimerHandle when=937812.615635614 _ServiceBrowserBase._async_send_ready_queries_schedule_next() created at /opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py:485> took 0.109 seconds
2021-11-20 14:16:26,975 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.104 seconds
2021-11-20 14:17:40,774 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.100 seconds
2021-11-20 14:18:53,154 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.111 seconds
2021-11-20 14:18:54,291 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.234 seconds
2021-11-20 14:18:55,751 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.161 seconds
2021-11-20 14:20:05,380 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.123 seconds
2021-11-20 14:20:28,455 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.151 seconds
2021-11-20 14:20:29,194 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.122 seconds
2021-11-20 14:20:37,177 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.157 seconds
2021-11-20 14:22:05,478 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.107 seconds
2021-11-20 14:22:50,912 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.112 seconds
2021-11-20 14:22:54,003 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.248 seconds
2021-11-20 14:24:11,488 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.105 seconds
2021-11-20 14:24:24,586 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.152 seconds
2021-11-20 14:24:29,873 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.140 seconds
2021-11-20 14:25:17,562 - WARNING - asyncio: Executing <TimerHandle when=938391.503227373 AsyncEngine._async_cache_cleanup() created at /opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_core.py:178> took 0.532 seconds
2021-11-20 14:25:24,507 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.111 seconds
2021-11-20 14:26:17,726 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.101 seconds
2021-11-20 14:26:55,810 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.125 seconds
2021-11-20 14:27:41,375 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.190 seconds
2021-11-20 14:27:42,106 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.123 seconds
2021-11-20 14:27:42,999 - WARNING - asyncio: Executing <Handle run_coroutine_threadsafe.<locals>.callback() at /usr/lib/python3.8/asyncio/tasks.py:920 created at /usr/lib/python3.8/asyncio/tasks.py:930> took 0.117 seconds
2021-11-20 14:27:44,222 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.243 seconds
2021-11-20 14:28:27,201 - WARNING - asyncio: Executing <TimerHandle when=938581.3116040601 _ServiceBrowserBase._async_send_ready_queries_schedule_next() created at /opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py:485> took 0.109 seconds
2021-11-20 14:28:28,371 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.186 seconds
2021-11-20 14:29:17,858 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.145 seconds
2021-11-20 14:30:00,915 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.119 seconds
2021-11-20 14:30:50,609 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.167 seconds
2021-11-20 14:31:27,905 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.102 seconds
2021-11-20 14:31:39,050 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.120 seconds
2021-11-20 14:32:10,570 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.178 seconds
2021-11-20 14:33:15,997 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.102 seconds
2021-11-20 14:33:16,114 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.110 seconds
2021-11-20 14:33:16,234 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.119 seconds
2021-11-20 14:33:16,409 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.103 seconds
2021-11-20 14:33:16,713 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.155 seconds
2021-11-20 14:33:17,215 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.111 seconds
2021-11-20 14:34:04,641 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.113 seconds
2021-11-20 14:34:27,695 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.106 seconds
2021-11-20 14:34:41,053 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.165 seconds
2021-11-20 14:35:10,831 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.103 seconds
2021-11-20 14:35:11,101 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.114 seconds
2021-11-20 14:35:11,473 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.281 seconds
2021-11-20 14:35:11,792 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.132 seconds
2021-11-20 14:35:11,944 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.146 seconds
2021-11-20 14:35:12,383 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.115 seconds
2021-11-20 14:35:12,707 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.181 seconds
2021-11-20 14:35:12,970 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.128 seconds
2021-11-20 14:35:13,323 - WARNING - asyncio: Executing <TimerHandle when=938987.6221583501 _ServiceBrowserBase._async_send_ready_queries_schedule_next() created at /opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py:485> took 0.106 seconds
2021-11-20 14:35:14,187 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.106 seconds
2021-11-20 14:35:14,700 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.170 seconds
2021-11-20 14:35:15,210 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.125 seconds
2021-11-20 14:36:29,225 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.112 seconds
2021-11-20 14:38:57,113 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.128 seconds
Exception in thread Thread-2863:
Traceback (most recent call last):
File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
File "/opt/fhem/.local/lib/python3.8/site-packages/sentry_sdk/integrations/threading.py", line 69, in run
File "/opt/fhem/.local/lib/python3.8/site-packages/sentry_sdk/_compat.py", line 54, in reraise
File "/opt/fhem/.local/lib/python3.8/site-packages/sentry_sdk/integrations/threading.py", line 67, in run
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openmq.py", line 171, in run
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openmq.py", line 185, in __run_mqtt
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/openmq.py", line 192, in _start
File "/opt/fhem/.local/lib/python3.8/site-packages/paho/mqtt/client.py", line 569, in __init__
File "/opt/fhem/.local/lib/python3.8/site-packages/paho/mqtt/client.py", line 269, in _socketpair_compat
File "/usr/lib/python3.8/socket.py", line 231, in __init__
OSError: [Errno 24] Too many open files
2021-11-20 14:39:41,919 - WARNING - urllib3.connectionpool: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(OSError(24, 'Too many open files'))': /api/6031048/store/
2021-11-20 14:39:41,921 - WARNING - urllib3.connectionpool: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f43c4b13eb0>: Failed to establish a new connection: [Errno 22] Invalid argument')': /api/6031048/store/
2021-11-20 14:39:41,921 - WARNING - urllib3.connectionpool: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f429e05cd60>: Failed to establish a new connection: [Errno 22] Invalid argument')': /api/6031048/store/
2021-11-20 14:39:45,467 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.203 seconds
2021-11-20 14:40:38,558 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.123 seconds
2021-11-20 14:41:26,909 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.391 seconds
2021-11-20 14:43:04,220 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.316 seconds
2021-11-20 14:43:04,953 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.146 seconds
2021-11-20 14:43:05,093 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.138 seconds
2021-11-20 14:43:05,266 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.139 seconds
2021-11-20 14:43:05,548 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.185 seconds
2021-11-20 14:43:05,840 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.162 seconds
2021-11-20 14:43:05,991 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.128 seconds
2021-11-20 14:43:06,311 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.193 seconds
2021-11-20 14:43:06,553 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.207 seconds
2021-11-20 14:43:07,061 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.182 seconds
2021-11-20 14:43:44,972 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.133 seconds
2021-11-20 14:43:45,228 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.207 seconds
2021-11-20 14:43:45,748 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.111 seconds
2021-11-20 14:44:52,148 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.101 seconds
2021-11-20 14:45:29,209 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.625 seconds
2021-11-20 14:45:50,263 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.114 seconds
2021-11-20 14:46:18,964 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.192 seconds
2021-11-20 14:47:58,433 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.139 seconds
2021-11-20 14:48:00,333 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.173 seconds
2021-11-20 14:48:00,526 - WARNING - asyncio: Executing <TimerHandle when=939754.648068571 _ServiceBrowserBase._async_send_ready_queries_schedule_next() created at /opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py:485> took 0.142 seconds
2021-11-20 14:48:00,744 - WARNING - asyncio: Executing <Handle _ServiceBrowserBase._async_start() created at /opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py:517> took 0.184 seconds
2021-11-20 14:48:01,030 - WARNING - asyncio: Executing <TimerHandle when=939754.9406658631 _ServiceBrowserBase._async_send_ready_queries_schedule_next() created at /opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py:485> took 0.221 seconds
2021-11-20 14:48:01,174 - WARNING - asyncio: Executing <Handle run_coroutine_threadsafe.<locals>.callback() at /usr/lib/python3.8/asyncio/tasks.py:920 created at /usr/lib/python3.8/asyncio/tasks.py:930> took 0.143 seconds
2021-11-20 14:48:01,320 - WARNING - asyncio: Executing <Task finished name='Task-44789' coro=<_ServiceBrowserBase._async_start_query_sender() done, defined at /opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py:448> result=None created at /opt/fhem/.local/lib/python3.8/site-packages/zeroconf/_services/browser.py:322> took 0.146 seconds
2021-11-20 14:48:01,644 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.129 seconds
2021-11-20 14:48:02,164 - WARNING - asyncio: Executing <Handle run_coroutine_threadsafe.<locals>.callback() at /usr/lib/python3.8/asyncio/tasks.py:920 created at /usr/lib/python3.8/asyncio/tasks.py:930> took 0.134 seconds
2021-11-20 14:48:48,575 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.155 seconds
2021-11-20 14:48:51,162 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.128 seconds
2021-11-20 14:48:51,369 - WARNING - asyncio: Executing <Handle _SelectorDatagramTransport._read_ready() created at /usr/lib/python3.8/asyncio/selector_events.py:259> took 0.109 seconds
Bitte Code Tag korrigieren, sonst fehlt wahrscheinlich ein Teil vom Log.
Ich denke es liegt am Googlecast Device. Probier bitte mal Version 0.1.175
Hallo Dominik,
ich benutze Version 0.1.175
Internals:
.FhemMetaInternals 1
BindingType Python
DEF Python
DeviceName ws:127.0.0.1:15733
FD 210
FUUID 5f513675-f33f-3b5c-6a47-c3e970bbbfac9d07
FVERSION 10_BindingsIo.pm:0.182830/2019-01-16
IP 127.0.0.1
NAME local_pybinding
NR 1051
NTFY_ORDER 50-local_pybinding
PARTIAL
PORT 15733
STATE opened
TYPE BindingsIo
WEBSOCKET 1
localBinding 1
nextOpenDelay 10
.attraggr:
.attrminint:
READINGS:
2021-05-24 08:11:30 info ready
2021-11-21 13:09:08 state opened
2021-11-21 13:09:08 version 0.1.175
args:
local_pybinding
BindingsIo
Python
argsh:
Attributes:
alias local_pybinding
comment Wird für Castdevice_ benötigt
https://github.com/dominikkarall/fhem_pythonbinding
https://forum.fhem.de/index.php/topic,45505.765.html
https://forum.fhem.de/index.php/topic,116455.165.html
devStateIcon { my $status_img = "10px-kreis-gruen";; my $status_txt = "connected";; if (ReadingsVal($name, "state", "disconnected") eq "disconnected") { $status_img = "10px-kreis-rot";; $status_txt = "disconnected";; } my $ver = ReadingsVal($name, "version", "-");; "<div><a>".FW_makeImage($status_img, $status_txt)."</a><a> ".$ver." </a><a href=\"/fhem?cmd.dummy=set $name update&XHR=1\" title=\"Start update\">".FW_makeImage("refresh")."</a></div>" }
group fhempy
icon file_json-ld2@#36A3D9
room 06_1_Sprachausgabe,Tuya,fhempy,hidden
verbose 3
Der Bug von heute ist aber noch mit einer Version davor gewesen, da 0.1.175 erst gegen 10Uhr released ist. Hast du mit 0.1.175 schon den gleichen Bug gehabt?
Ich hatte mittags ein update gemacht. Danach habe ich bis jetzt keinen Absturz.
Mal sehen, ob dadurch die Abstürze behoben sind.
Vielen Dank vorerst.
Ok, gib bitte Bescheid und poste dann bitte die Logs.
Hab leider immernoch das Problem mit den Readings
Nach pybinding update kommen die Readings
nach zwei bis dreimal Schalten einer Steckdose bleibt Readings stehen und aktualisiert erst nach pybinding update
Woran kann das liegen? Bitte um Hilfe
bei mir der gleiche Fehler, wie bei ChrisA4.
Hatte schon super funktioniert..
ZitatOk, gib bitte Bescheid und poste dann bitte die Logs.
Der Server stürzt nicht mehr ab. Im Log sind jetzt noch die
nachfolgenden Einträge
2021-11-23 02:26:36,808 - ERROR - pychromecast.socket_client: [OG.Badezimmer(192.168.178.48):8009] Failed to connect to service ServiceInfo(type='host', data=('192.168.178.48', 8009)), retrying in 5.0s
2021-11-23 02:33:02,497 - ERROR - pychromecast.socket_client: [Dachboden(192.168.178.74):8009] Failed to connect to service ServiceInfo(type='host', data=('192.168.178.74', 8009)), retrying in 5.0s
2021-11-23 02:34:05,079 - ERROR - pychromecast.socket_client: [Schlafzimmer(192.168.178.22):8009] Failed to connect to service ServiceInfo(type='host', data=('192.168.178.22', 8009)), retrying in 5.0s
2021-11-23 02:36:34,984 - ERROR - pychromecast.socket_client: [Schlafzimmer(192.168.178.22):8009] Failed to connect to service ServiceInfo(type='host', data=('192.168.178.22', 8009)), retrying in 5.0s
2021-11-23 02:52:49,489 - ERROR - pychromecast.socket_client: [Wohnzimmer(192.168.178.52):8009] Failed to connect to service ServiceInfo(type='host', data=('192.168.178.52', 8009)), retrying in 5.0s
2021-11-23 02:56:28,494 - ERROR - pychromecast.socket_client: [Chromecast(192.168.178.68):8009] Failed to connect to service ServiceInfo(type='host', data=('192.168.178.68', 8009)), retrying in 5.0s
2021-11-23 04:44:09,666 - ERROR - pychromecast.socket_client: [Google-Nest(192.168.178.28):8009] Error reading from socket.
2021-11-23 04:44:09,836 - ERROR - pychromecast.socket_client: [Google-Nest(192.168.178.28):8009] Failed to connect to service ServiceInfo(type='host', data=('192.168.178.28', 8009)), retrying in 5.0s
2021-11-23 06:29:58,973 - ERROR - asyncio: Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x7f9a1b1006d0>
source_traceback: Object created at (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 539, in run
asyncio.get_event_loop().run_forever()
File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
self._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1851, in _run_once
handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
self._context.run(self._callback, *self._args)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/googlecast/googlecast.py", line 347, in playDefaultMedia
session = aiohttp.ClientSession()
2021-11-23 06:29:58,979 - ERROR - asyncio: Unclosed connector
connections: ['[(<aiohttp.client_proto.ResponseHandler object at 0x7f9a1b06b8e0>, 148973.54781846)]']
connector: <aiohttp.connector.TCPConnector object at 0x7f9a1b100ca0>
source_traceback: Object created at (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 539, in run
asyncio.get_event_loop().run_forever()
File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
self._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1851, in _run_once
handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
self._context.run(self._callback, *self._args)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/googlecast/googlecast.py", line 347, in playDefaultMedia
session = aiohttp.ClientSession()
File "/opt/fhem/.local/lib/python3.8/site-packages/aiohttp/client.py", line 228, in __init__
connector = TCPConnector(loop=loop)
File "/opt/fhem/.local/lib/python3.8/site-packages/aiohttp/connector.py", line 756, in __init__
super().__init__(
2021-11-23 06:29:58,985 - ERROR - asyncio: Unclosed connection
client_connection: Connection<ConnectionKey(host='topradio-stream28.radiohost.de', port=80, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=None)>
source_traceback: Object created at (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 539, in run
asyncio.get_event_loop().run_forever()
File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
self._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1851, in _run_once
handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
self._context.run(self._callback, *self._args)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/googlecast/googlecast.py", line 348, in playDefaultMedia
res = await session.get(uri)
File "/opt/fhem/.local/lib/python3.8/site-packages/aiohttp/client.py", line 520, in _request
conn = await self._connector.connect(
File "/opt/fhem/.local/lib/python3.8/site-packages/aiohttp/connector.py", line 560, in connect
return Connection(self, key, proto, self._loop)
2021-11-23 06:29:58,989 - ERROR - asyncio: Unclosed response
client_response: <ClientResponse(http://topradio-stream28.radiohost.de/rs2_mp3-128?ref=internetradio&amsparams=internetradio&listenerrmid=31363337363435333937-39332e3230312e37342e3633-3538343138-507974686f6e2f332e382061696f687474702f33) [200 OK]>
<CIMultiDictProxy('Cache-Control': 'no-cache', 'Pragma': 'no-cache', 'Expires': 'Mon, 26 Jul 1997 05:00:00 GMT', 'icy-br': '128', 'Instance-id': '151e228e65543646613def902e8279bb', 'Server': 'Radiohost.de - topradio-stream28.radiohost.de 9.0.2', 'icy-genre': 'various', 'icy-metaint': '0', 'Content-Type': 'audio/mpeg', 'icy-name': 'rs2', 'Access-Control-Allow-Origin': '*', 'Connection': 'close', 'icy-url': 'www.rs2.de', 'icy-audio-info': 'channels=2;samplerate=44100;bitrate=128', 'icy-pub': '0', 'icy-description': 'Unspecified description', 'P3P': 'CP="ALL IND DSP COR ADM CONo CUR CUSo IVAo IVDo PSA PSD TAI TELo OUR SAMo CNT COM INT NAV ONL PHY PRE PUR UNI"', 'X-Loudness': '-11.511092', 'Set-Cookie': 'AISSessionId=6137d9b01a678ea4_6595237_EDOzPyQL__0000000leXc; Path=/; Domain=topradio-stream28.radiohost.de; Max-Age=6000; Expires=Tue, 23 Nov 2021 07:09:57 GMT')>
source_traceback: Object created at (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 539, in run
asyncio.get_event_loop().run_forever()
File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
self._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1851, in _run_once
handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
self._context.run(self._callback, *self._args)
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/googlecast/googlecast.py", line 348, in playDefaultMedia
res = await session.get(uri)
File "/opt/fhem/.local/lib/python3.8/site-packages/aiohttp/client.py", line 542, in _request
resp = await req.send(conn)
File "/opt/fhem/.local/lib/python3.8/site-packages/aiohttp/client_reqrep.py", line 674, in send
self.response = response_class(
2021-11-23 11:30:02,771 - ERROR - pychromecast.socket_client: [Dachboden(192.168.178.74):8009] Failed to connect to service ServiceInfo(type='mdns', data='Google-Nest-Mini-143ba75a235b6b691742e0dfcf309e1a._googlecast._tcp.local.'), retrying in 5.0s
2021-11-23 11:30:02,916 - ERROR - pychromecast.socket_client: [Schlafzimmer(192.168.178.22):8009] Failed to connect to service ServiceInfo(type='host', data=('192.168.178.22', 8009)), retrying in 5.0s
2021-11-23 11:30:09,400 - ERROR - pychromecast.socket_client: [Wohnzimmer(192.168.178.52):8009] Failed to connect to service ServiceInfo(type='mdns', data='Google-Home-cb6ffc04c65ce8afd0127c0acb87a510._googlecast._tcp.local.'), retrying in 5.0s
2021-11-23 11:30:09,436 - ERROR - pychromecast.socket_client: [OG.Badezimmer(192.168.178.48):8009] Failed to connect to service ServiceInfo(type='host', data=('192.168.178.48', 8009)), retrying in 5.0s
2021-11-23 11:30:10,292 - ERROR - pychromecast.socket_client: [Google-Nest(192.168.178.28):8009] Failed to connect to service ServiceInfo(type='host', data=('192.168.178.28', 8009)), retrying in 5.0s
ZitatProbleme bei Neuanlage von Licht-Devices:
Muss mich ChrisA4 und juergen012 anschließen.
Der Neustart hilft nur eine kurze Zeit!
Readings werden nur teilweise oder gar nicht aktualisiert!
on/off werden nie aktualisiert (wenn ich z.B. direkt über die Smart-App schalte)
Moin,
ich habe hier eine Deckenlampe per Wifi und Tuya eingebunden. Kann mir jemand einen Denkanstoß gegen wie die desse jetzt über fhem / fhempy schalten kann? Per tuya-mqtt habe ich schon mal 3 Werte, aber mir fehlt einfach der Ansatz wo ich beginnen muss um das in fhem / fhempy zu integrieren? Danke. Gesund bleiben!
on/off
pi@fhem-pi4:~ $ mosquitto_pub -t 'tuya/baby/DPS/20/command' -m 'true'
pi@fhem-pi4:~ $ mosquitto_pub -t 'tuya/baby/DPS/20/command' -m 'false'
dimmer
pi@fhem-pi4:~ $ mosquitto_pub -t 'tuya/baby/DPS/22/command' -m '10'
pi@fhem-pi4:~ $ mosquitto_pub -t 'tuya/baby/DPS/22/command' -m '400'
pi@fhem-pi4:~ $ mosquitto_pub -t 'tuya/baby/DPS/22/command' -m '1000'
defmod tuya_baby_1 PythonModule tuya 2mdih0ds0q8wzncp bfc079fb02a1dc6664zrqn 172.31.100.16 5f5879c706e3d34a
attr tuya_baby_1 IODev local_pybinding
attr tuya_baby_1 room zTuya
setstate tuya_baby_1 online
setstate tuya_baby_1 2021-11-25 09:42:46 dp_20 1
setstate tuya_baby_1 2021-11-25 08:49:44 dp_21 white
setstate tuya_baby_1 2021-11-25 09:43:34 dp_22 10
setstate tuya_baby_1 2021-11-25 09:40:08 dp_23 1
setstate tuya_baby_1 2021-11-25 08:42:09 dp_24 000003e803e8
setstate tuya_baby_1 2021-11-25 08:49:44 dp_25 FF5f5f01000003E803E8000000005f5f01001E03E803E8000000005f5f01003C03E803E8000000005f5f01007803E803E8000000005f5f0100B403E803E8000000005f5f0100F003E803E8000000005f5f01012C03E803E800000000
setstate tuya_baby_1 2021-11-25 08:42:09 dp_26 0
setstate tuya_baby_1 2021-11-25 08:42:09 dp_34 0
setstate tuya_baby_1 2021-11-25 09:20:47 state online
Zitat von: bewa58 am 24 November 2021, 17:23:04
Muss mich ChrisA4 und juergen012 anschließen.
Der Neustart hilft nur eine kurze Zeit!
Readings werden nur teilweise oder gar nicht aktualisiert!
on/off werden nie aktualisiert (wenn ich z.B. direkt über die Smart-App schalte)
Habt ihr auch sicher bei tuya iot die Notifications aktiviert?
Punkt 6: https://github.com/tuya/tuya-home-assistant/wiki/Tuya-IoT-Platform-Configuration-Guide
Zitat von: fhem@supergut am 25 November 2021, 09:58:49
Moin,
ich habe hier eine Deckenlampe per Wifi und Tuya eingebunden. Kann mir jemand einen Denkanstoß gegen wie die desse jetzt über fhem / fhempy schalten kann? Per tuya-mqtt habe ich schon mal 3 Werte, aber mir fehlt einfach der Ansatz wo ich beginnen muss um das in fhem / fhempy zu integrieren? Danke. Gesund bleiben!
on/off
pi@fhem-pi4:~ $ mosquitto_pub -t 'tuya/baby/DPS/20/command' -m 'true'
pi@fhem-pi4:~ $ mosquitto_pub -t 'tuya/baby/DPS/20/command' -m 'false'
dimmer
pi@fhem-pi4:~ $ mosquitto_pub -t 'tuya/baby/DPS/22/command' -m '10'
pi@fhem-pi4:~ $ mosquitto_pub -t 'tuya/baby/DPS/22/command' -m '400'
pi@fhem-pi4:~ $ mosquitto_pub -t 'tuya/baby/DPS/22/command' -m '1000'
defmod tuya_baby_1 PythonModule tuya 2mdih0ds0q8wzncp bfc079fb02a1dc6664zrqn 172.31.100.16 5f5879c706e3d34a
attr tuya_baby_1 IODev local_pybinding
attr tuya_baby_1 room zTuya
setstate tuya_baby_1 online
setstate tuya_baby_1 2021-11-25 09:42:46 dp_20 1
setstate tuya_baby_1 2021-11-25 08:49:44 dp_21 white
setstate tuya_baby_1 2021-11-25 09:43:34 dp_22 10
setstate tuya_baby_1 2021-11-25 09:40:08 dp_23 1
setstate tuya_baby_1 2021-11-25 08:42:09 dp_24 000003e803e8
setstate tuya_baby_1 2021-11-25 08:49:44 dp_25 FF5f5f01000003E803E8000000005f5f01001E03E803E8000000005f5f01003C03E803E8000000005f5f01007803E803E8000000005f5f0100B403E803E8000000005f5f0100F003E803E8000000005f5f01012C03E803E800000000
setstate tuya_baby_1 2021-11-25 08:42:09 dp_26 0
setstate tuya_baby_1 2021-11-25 08:42:09 dp_34 0
setstate tuya_baby_1 2021-11-25 09:20:47 state online
Ich empfehle tuya_cloud statt tuya zu nutzen, hier die Anleitung:
https://github.com/dominikkarall/fhempy/blob/master/FHEM/bindings/python/fhempy/lib/tuya_cloud/README.md
ZitatHabt ihr auch sicher bei tuya iot die Notifications aktiviert?
Ja, natürlich. Hat doch eine Zeit lang funktioniert.
Zitat von: dominik am 25 November 2021, 22:15:10
Ich empfehle tuya_cloud statt tuya zu nutzen, hier die Anleitung:
https://github.com/dominikkarall/fhempy/blob/master/FHEM/bindings/python/fhempy/lib/tuya_cloud/README.md
Jau, danke.
defmod Baby_bfc079fb02a1dc6664zrqn PythonModule tuya_cloud tuya_cloud_connector bfc079fb02a1dc6664zrqn
attr Baby_bfc079fb02a1dc6664zrqn IODev local_pybinding
attr Baby_bfc079fb02a1dc6664zrqn alias Baby
attr Baby_bfc079fb02a1dc6664zrqn group tuya_cloud
attr Baby_bfc079fb02a1dc6664zrqn room fhempy
setstate Baby_bfc079fb02a1dc6664zrqn on
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:17 active_time 1637760821
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:17 biz_type 0
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:18 bright_value 10.0
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:17 category xdd
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:18 colour_data ff0000
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:18 countdown 0.0
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:17 create_time 1637757837
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:18 do_not_disturb off
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:17 icon https://images.tuyaeu.com/smart/icon/ay15302565619159aD9o/82fa8dc5a0ff1f44788060dcc4b3acea.png
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:17 id bfc079fb02a1dc6664zrqn
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:17 ip 92.116.12.212
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:17 lat 52.1918
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:17 local_key 5f5879c706e3d34a
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:17 lon 8.7143
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:17 model D36C-WIFI
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:17 name Baby
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:17 online off
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:17 owner_id 28686958
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:17 product_id 2mdih0ds0q8wzncp
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:17 product_name Baby
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:18 scene_data {"scene_num":256,"scene_units":[{"bright":0,"h":0,"s":1000,"temperature":0,"unit_change_mode":"jump","unit_gradient_duration":95,"unit_switch_duration":95,"v":1000},{"bright":0,"h":30,"s":1000,"temperature":0,"unit_change_mode":"jump","unit_gradient_duration":95,"unit_switch_duration":95,"v":1000},{"bright":0,"h":60,"s":1000,"temperature":0,"unit_change_mode":"jump","unit_gradient_duration":95,"unit_switch_duration":95,"v":1000},{"bright":0,"h":120,"s":1000,"temperature":0,"unit_change_mode":"jump","unit_gradient_duration":95,"unit_switch_duration":95,"v":1000},{"bright":0,"h":180,"s":1000,"temperature":0,"unit_change_mode":"jump","unit_gradient_duration":95,"unit_switch_duration":95,"v":1000},{"bright":0,"h":240,"s":1000,"temperature":0,"unit_change_mode":"jump","unit_gradient_duration":95,"unit_switch_duration":95,"v":1000},{"bright":0,"h":300,"s":1000,"temperature":0,"unit_change_mode":"jump","unit_gradient_duration":95,"unit_switch_duration":95,"v":1000}]}
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:18 state on
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:17 sub off
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:18 temp_value 0.0
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:17 time_zone +01:00
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:17 uid eu161760599381547022
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:17 update_time 1637827601
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:17 uuid 31c22c3ba8ef21a1
setstate Baby_bfc079fb02a1dc6664zrqn 2021-11-26 09:17:18 work_mode white
Zitat von: dominik am 25 November 2021, 21:34:43
Habt ihr auch sicher bei tuya iot die Notifications aktiviert?
Punkt 6: https://github.com/tuya/tuya-home-assistant/wiki/Tuya-IoT-Platform-Configuration-Guide
Ja und ich hab auch nochmal das ganze komplett neu gemacht und weiterhin selbiges problem mit der Status aktualisierung
Auch bei mir, wie bei den Anderen..
Gruß
Ich habe gerade 0.1.176 released und dort wieder eine alte Version der tuya Library (0.4.1) eingebaut. Bitte mal damit testen.
jetzt tauchen im LOG Meldungen auf! (vor dem update auf 0.1.176)
Habe 2 neue Devices angelegt. Set Befehle werden nicht angenommen, oder mal doch.
Neustart fhempyserver_15733 muss ich dann machen und die Readings werden aktualisiert.
hier mal der LOG dazu:
Zitat2021-11-26 19:45:42,316 - WARNING - asyncio: Executing () created at /usr/lib/python3.7/asyncio/tasks.py:368> took 0.351 seconds
2021-11-26 19:50:45,135 - WARNING - ring_doorbell.doorbot: Your Ring account does not have an active subscription.
2021-11-26 19:50:45,807 - WARNING - asyncio: Executing () created at /usr/lib/python3.7/asyncio/tasks.py:368> took 0.358 seconds
2021-11-26 19:53:09,539 - INFO - tuya_cloud_connectorNEU: add_device received for 53557412c82b960cbbd0
2021-11-26 19:53:11,840 - INFO - tuya_cloud_connectorNEU: create: Smart_light__4_53557412c82b960cbbd0 PythonModule tuya_cloud tuya_cloud_connectorNEU 53557412c82b960cbbd0
2021-11-26 19:54:04,131 - DEBUG - tuya_cloud_connectorNEU: update_device received for 53557412c82b960cbbd0
2021-11-26 19:54:04,225 - ERROR - Smart_light__4_53557412c82b960cbbd0: Expecting value: line 1 column 1 (char 0)
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 292, in update_readings_dict
st_name, json.loads(status_dic[st_name])
File "/usr/lib/python3.7/json/__init__.py", line 348, in loads
return _default_decoder.decode(s)
File "/usr/lib/python3.7/json/decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python3.7/json/decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
2021-11-26 19:54:54,557 - DEBUG - tuya_cloud_connectorNEU: update_device received for 41518006f4cfa25b52db
2021-11-26 19:55:48,353 - WARNING - ring_doorbell.doorbot: Your Ring account does not have an active subscription.
2021-11-26 19:55:49,016 - WARNING - asyncio: Executing () created at /usr/lib/python3.7/asyncio/tasks.py:368> took 0.343 seconds
2021-11-26 20:00:51,789 - WARNING - ring_doorbell.doorbot: Your Ring account does not have an active subscription.
2021-11-26 20:00:52,763 - WARNING - asyncio: Executing () created at /usr/lib/python3.7/asyncio/tasks.py:368> took 0.349 seconds
2021-11-26 20:04:44,447 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-11-26 20:04:44,473 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-11-26 20:04:44,566 - WARNING - asyncio: Executing wait_for=<_GatheringFuture pending cb=[()] created at /usr/lib/python3.7/asyncio/tasks.py:615> cb=[_run_until_complete_cb() at /usr/lib/python3.7/asyncio/base_events.py:158] created at /usr/lib/python3.7/asyncio/base_events.py:563> took 0.119 seconds
2021-11-26 20:04:44,569 - INFO - websockets.server: server listening on 0.0.0.0:15733
2021-11-26 20:04:52,300 - INFO - websockets.server: connection open
2021-11-26 20:04:52,303 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-11-26 20:04:56,427 - WARNING - asyncio: Executing () created at /usr/lib/python3.7/asyncio/tasks.py:368> took 0.359 seconds
2021-11-26 20:04:57,882 - WARNING - ring_doorbell.doorbot: Your Ring account does not have an active subscription.
2021-11-26 20:04:59,967 - WARNING - asyncio: Executing () created at /usr/lib/python3.7/asyncio/tasks.py:368> took 0.335 seconds
2021-11-26 20:09:09,590 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-11-26 20:09:09,616 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-11-26 20:09:09,691 - INFO - websockets.server: server listening on 0.0.0.0:15733
2021-11-26 20:09:17,121 - INFO - websockets.server: connection open
2021-11-26 20:09:17,124 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-11-26 20:09:22,496 - WARNING - asyncio: Executing () created at /usr/lib/python3.7/asyncio/tasks.py:368> took 0.338 seconds
2021-11-26 20:09:24,421 - WARNING - ring_doorbell.doorbot: Your Ring account does not have an active subscription.
2021-11-26 20:09:25,709 - WARNING - asyncio: Executing () created at /usr/lib/python3.7/asyncio/tasks.py:368> took 0.414 seconds
Teste das bitte nochmals mit 0.1.176.
Der gepostete Fehler sollte nur colour_data nicht aktualisieren, der Rest sollte dennoch klappen.
Hab jetzt die 177 drauf
in der App werden die Status aktualisiert aber unter fhem nur wenn man fhempy updatet, ansonsten von 10 schaltungen ca 1/1min ca 2 von 10 werden aktualisiert.
Hoffe es hilft weiter
Bei mir ebenso wie bei ChrisA4
dito
1x klappt es, dann wieder nicht.
Auch die Schaltungen per Smartlive App werden nur sporadisch in FHEM angezeigt.
Wenn es mal funktioniert dauert readings update bis zu 1ner Minute !
kann da keine Regelmäßgigkeit erkennen.
Noch etwas:
webCmd :
colour_data_v2:colour_data_v2 ff0000:colour_data_v2 F24CE7:colour_data_v2 38FF05:colour_data_v2 DEFF26:colour_data_v2 0000ff:toggle:on:off
beim anklicken auf das Lampen-Icon
kommt Fehlermeldung: Command not available for this device !
??? fehlt da noch eine Implementierung ?
Ok, ich werde heute auf die letzte Version der Library aktualisieren. Diese ist aber erst ab Python 3.8 nutzbar, habt ihr 3.8 oder noch 3.7?
Update auf 0.1.178 ist da. Bitte beachten, Python 3.8 oder höher ist notwendig! Ich empfehle ein Update auf Bullseye wer es noch nicht gemacht hat, dort ist Python 3.9 standard. Von einer manuellen Installation von Python würde ich absehen.
Ein paar Tests mit Thermostaten liefen bei mir jetzt ohne Aussetzer.
@bewa58, wegen colour_data_v2, hat das Device auch sicher ein set Command mit colour_data_v2? Eventuell ohne _v2?
Habe Python 3.7. Kann nicht auf Bullseye upgraden, da fhem im LXC unter Proxmox läuft. Dort bekomme ich eine Fehlermeldung, wenn ich den Test zum Update laufen lasse..
Zitat@bewa58, wegen colour_data_v2, hat das Device auch sicher ein set Command mit colour_data_v2? Eventuell ohne _v2?
Danke für den Tipp (hatte falsches devstateIcon drin !
Hiermit funktioniert es:
ZitatdevStateIcon
{(Color::HUEDevice_devStateIcon($name,"rgb","colour_data_v2","state"),"toggle")}
UPGRADE erst kommende Woche Zeit! Melde mich dann.
kann mir jemand helfen mit dem update auf python 3.9 am raspi
hab das update dürchgeführt jedoch bleict fhempy nach neustart immer auf 3.7
Ich find den fehler nicht
Du bist jetzt auf bullseye? Hast du ein "sudo apt full-upgrade" gemacht?
raspian buster 10
full upgrade wurde gemacht
python 3.9.9 wird angezeigt
fhempy gibt:
Failed to load module tuya_cloud: Traceback (most recent call last):
File "/home/pi/.local/lib/python3.7/site-packages/fhempy/lib/fhem_pythonbinding.py", line 301, in _onMessage
functools.partial(importlib.import_module, pymodule)
File "/home/pi/.local/lib/python3.7/site-packages/fhempy/lib/utils.py", line 33, in run_blocking
return await asyncio.get_event_loop().run_in_executor(pool, function)
File "/usr/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
File "<frozen importlib._bootstrap>", line 983, in _find_and_load
File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 728, in exec_module
File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
File "/home/pi/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud.py", line 5, in <module>
from fhempy.lib.tuya_cloud.tuya_cloud_device import tuya_cloud_device
File "/home/pi/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 5, in <module>
from tuya_iot.device import TuyaDevice
File "/home/pi/.local/lib/python3.7/site-packages/tuya_iot/__init__.py", line 2, in <module>
from .device import TuyaDevice, TuyaDeviceListener, TuyaDeviceManager
File "/home/pi/.local/lib/python3.7/site-packages/tuya_iot/device.py", line 7, in <module>
from typing import Any, Literal, Optional
ImportError: cannot import name 'Literal' from 'typing' (/usr/lib/python3.7/typing.py)
Weiss nicht weiter
Mach mal
sudo -u fhem bash
pip3 uninstall fhempy
pip3 install fhempy
Und danach fhempy in FHEM neu starten.
es kommt bei der deinstallation
WARNING: Skipping fhempy as it is not installed.
??
Habs Fhempy Lief noch
so bei der neuinstallation kommt
fhem@fhem:/home/pi$ pip3 install fhempy
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting fhempy
Using cached https://files.pythonhosted.org/packages/b2/af/84cc06adf521e54deb5079dedec932b9c4143cc07ccc575c7d7ef3daf02e/fhempy-0.1.178-py3-none-any.whl
Requirement already satisfied: markdown==3.3.4 in /opt/fhem/.local/lib/python3.7/site-packages (from fhempy) (3.3.4)
Requirement already satisfied: dbus-python==1.2.18 in /opt/fhem/.local/lib/python3.7/site-packages (from fhempy) (1.2.18)
Requirement already satisfied: cryptography==3.3.2 in /opt/fhem/.local/lib/python3.7/site-packages (from fhempy) (3.3.2)
Requirement already satisfied: zeroconf==0.36.12 in /opt/fhem/.local/lib/python3.7/site-packages (from fhempy) (0.36.12)
Requirement already satisfied: sentry-sdk==1.4.3 in /opt/fhem/.local/lib/python3.7/site-packages (from fhempy) (1.4.3)
Requirement already satisfied: aiohttp[speedups]==3.7.4.post0 in /opt/fhem/.local/lib/python3.7/site-packages (from fhempy) (3.7.4.post0)
Requirement already satisfied: websockets==10.0 in /opt/fhem/.local/lib/python3.7/site-packages (from fhempy) (10.0)
Requirement already satisfied: importlib-metadata==4.8.1 in /opt/fhem/.local/lib/python3.7/site-packages (from fhempy) (4.8.1)
Requirement already satisfied: cffi>=1.12 in /opt/fhem/.local/lib/python3.7/site-packages (from cryptography==3.3.2->fhempy) (1.15.0)
Requirement already satisfied: six>=1.4.1 in /usr/lib/python3/dist-packages (from cryptography==3.3.2->fhempy) (1.12.0)
Requirement already satisfied: ifaddr>=0.1.7 in /opt/fhem/.local/lib/python3.7/site-packages (from zeroconf==0.36.12->fhempy) (0.1.7)
Requirement already satisfied: urllib3>=1.10.0 in /usr/lib/python3/dist-packages (from sentry-sdk==1.4.3->fhempy) (1.24.1)
Requirement already satisfied: certifi in /usr/lib/python3/dist-packages (from sentry-sdk==1.4.3->fhempy) (2018.8.24)
Requirement already satisfied: attrs>=17.3.0 in /opt/fhem/.local/lib/python3.7/site-packages (from aiohttp[speedups]==3.7.4.post0->fhempy) (21.2.0)
Requirement already satisfied: async-timeout<4.0,>=3.0 in /opt/fhem/.local/lib/python3.7/site-packages (from aiohttp[speedups]==3.7.4.post0->fhempy) (3.0.1)
Requirement already satisfied: multidict<7.0,>=4.5 in /opt/fhem/.local/lib/python3.7/site-packages (from aiohttp[speedups]==3.7.4.post0->fhempy) (5.2.0)
Requirement already satisfied: typing-extensions>=3.6.5 in /opt/fhem/.local/lib/python3.7/site-packages (from aiohttp[speedups]==3.7.4.post0->fhempy) (4.0.0)
Requirement already satisfied: yarl<2.0,>=1.0 in /opt/fhem/.local/lib/python3.7/site-packages (from aiohttp[speedups]==3.7.4.post0->fhempy) (1.7.2)
Requirement already satisfied: chardet<5.0,>=2.0 in /usr/lib/python3/dist-packages (from aiohttp[speedups]==3.7.4.post0->fhempy) (3.0.4)
Requirement already satisfied: cchardet; extra == "speedups" in /opt/fhem/.local/lib/python3.7/site-packages (from aiohttp[speedups]==3.7.4.post0->fhempy) (2.1.7)
Requirement already satisfied: aiodns; extra == "speedups" in /opt/fhem/.local/lib/python3.7/site-packages (from aiohttp[speedups]==3.7.4.post0->fhempy) (3.0.0)
Requirement already satisfied: brotlipy; extra == "speedups" in /opt/fhem/.local/lib/python3.7/site-packages (from aiohttp[speedups]==3.7.4.post0->fhempy) (0.7.0)
Requirement already satisfied: zipp>=0.5 in /opt/fhem/.local/lib/python3.7/site-packages (from importlib-metadata==4.8.1->fhempy) (3.6.0)
Requirement already satisfied: pycparser in /opt/fhem/.local/lib/python3.7/site-packages (from cffi>=1.12->cryptography==3.3.2->fhempy) (2.21)
Requirement already satisfied: idna>=2.0 in /usr/lib/python3/dist-packages (from yarl<2.0,>=1.0->aiohttp[speedups]==3.7.4.post0->fhempy) (2.6)
Requirement already satisfied: pycares>=4.0.0 in /opt/fhem/.local/lib/python3.7/site-packages (from aiodns; extra == "speedups"->aiohttp[speedups]==3.7.4.post0->fhempy) (4.1.2)
Installing collected packages: fhempy
Successfully installed fhempy-0.1.178
fhem@fhem:/home/pi$
da steht doch was von python 3.7
Mach mal
fhem@raspberrypi:~$ pip3 -V
pip 20.3.4 from /usr/lib/python3/dist-packages/pip (python 3.9)
fhem@raspberrypi:~$ python3 -V
Python 3.9.2
kommt diese Meldung
pi@fhem:~ $ pip3 -V
-bash: pip3: Kommando nicht gefunden.
pi@fhem:~ $ pip3 -V
-bash: pip3: Kommando nicht gefunden.
pi@fhem:~ $ python3 -V
Python 3.7.3
pi@fhem:~ $
aber bei
pi@fhem:~ $ python --version
Python 3.9.7
ich steh am schlauch
Bist du sicher auf bullseye? /etc/debian_version = 11.1?
Ich kann aber "beruhigen", alle die Probleme haben, es liegt an Tuya selbst:
https://github.com/home-assistant/core/issues/60034#issuecomment-979682872
Das ist ein Post von einem Tuya Engineer. Es sollte also hoffentlich in den nächsten Tagen wieder funktionieren. Sehr ärgerlich...ich habe meine ganze Heizungssteuerung auf Tuya Basis ???
Zitat von: ChrisA4 am 27 November 2021, 18:59:01
raspian buster 10
full upgrade wurde gemacht
python 3.9.9 wird angezeigt
fhempy gibt:
Failed to load module tuya_cloud: Traceback (most recent call last):
File "/home/pi/.local/lib/python3.7/site-packages/fhempy/lib/fhem_pythonbinding.py", line 301, in _onMessage
functools.partial(importlib.import_module, pymodule)
File "/home/pi/.local/lib/python3.7/site-packages/fhempy/lib/utils.py", line 33, in run_blocking
return await asyncio.get_event_loop().run_in_executor(pool, function)
File "/usr/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
File "<frozen importlib._bootstrap>", line 983, in _find_and_load
File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 728, in exec_module
File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
File "/home/pi/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud.py", line 5, in <module>
from fhempy.lib.tuya_cloud.tuya_cloud_device import tuya_cloud_device
File "/home/pi/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 5, in <module>
from tuya_iot.device import TuyaDevice
File "/home/pi/.local/lib/python3.7/site-packages/tuya_iot/__init__.py", line 2, in <module>
from .device import TuyaDevice, TuyaDeviceListener, TuyaDeviceManager
File "/home/pi/.local/lib/python3.7/site-packages/tuya_iot/device.py", line 7, in <module>
from typing import Any, Literal, Optional
ImportError: cannot import name 'Literal' from 'typing' (/usr/lib/python3.7/typing.py)
Weiss nicht weiter
Buster 10
Buster hat kein Python 3.9
https://packages.debian.org/buster/python3
Da ist Python 3.7 max, daher ein Update auf Bullseye machen und bitte nicht manuell installieren, das macht meistens nur Probleme.
@dominik
Vielen vielen Dank
Jetzt läufts
Update auf Bullseye gemacht, fhempy neu drauf und die Geräte wieder da.
Das mit der State aktualisierung funkt trotzdem nicht so, werden wir warten müssen was TuyaIot da noch bastellt.
Super!
Ich habe gerade einen Workaround eingebaut, dass alle 15min der aktuelle Status von Tuya via API (statt MQTT) bezogen wird. Funktioniert zwar auch nicht 100%, aber hilft ein bisschen. Sobald es bei Tuya wieder läuft, werde ich das entfernen.
Ah, jetzt habe ich das auch kapiert.
Mein Raspberry lief auch noch mit python 3.7.
Habe eben leider, weil ichs hier zu spät gelesen habe, manuell auf 3.8.12 upgedated.
Mache jetzt aber auch das update auf Bullseye.
Hoffe dann sind auch die seltsamen stop Probleme die ich noch hatte behoben.
Gruß und Danke,
Stefan
Hallo,
habe heute auf einem Raspi 4 Bullseye, Fhem und Tuya neu installiert. Tuya läuft wieder super..
Gruß
Hi Dominik,
I did a clean install of bullseye, things are actually running and showing up now, but my fhemserver starts and then stops quickly.
2021-11-29 14:41:38,679 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2021-11-29 14:41:38,713 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2021-11-29 14:41:38,826 - WARNING - asyncio: Executing <Task pending name='Task-1' coro=<async_main() running at /opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py:530> wait_for=<_GatheringFuture pending cb=[<TaskWakeupMethWrapper object at 0x75235dd8>()] created at /usr/lib/python3.9/asyncio/tasks.py:704> cb=[_run_until_complete_cb() at /usr/lib/python3.9/asyncio/base_events.py:184] created at /usr/lib/python3.9/asyncio/base_events.py:621> took 0.147 seconds
Traceback (most recent call last):
File "/opt/fhem/FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 538, in run
asyncio.get_event_loop().run_until_complete(async_main())
File "/usr/lib/python3.9/asyncio/base_events.py", line 642, in run_until_complete
return future.result()
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 530, in async_main
await websockets.serve(
File "/opt/fhem/.local/lib/python3.9/site-packages/websockets/legacy/server.py", line 1042, in __await_impl__
server = await self._create_server()
File "/usr/lib/python3.9/asyncio/base_events.py", line 1494, in create_server
raise OSError(err.errno, 'error while attempting '
OSError: [Errno 98] error while attempting to bind on address ('0.0.0.0', 15733): address already in use
Sentry is attempting to send 2 pending error messages
Waiting up to 2 seconds
Press Ctrl-C to quit
what to do?
Edit: Oh damn i think i installed the systemd_fhempy.sh option. Sry bad reader... Can i uninstall that?
Could it be that you did this step:
https://github.com/dominikkarall/fhempy#installation-short
There is a fhempy instance already running on your host ("15733 port already in use").
yes i did that step, i didn't read. FML.
I will try a new install again and come back in an hour, thnx
Läuft bei mir wieder unter Python 3.7
Upgrade auf Bullseye mit einigen Hindernissen erledigt.
Läuft !
Anscheinend läuft auch die Tuya-Cloud wieder.
Schaltungen werden sofort angezeigt!
bitte mal testen.
Dann kann Dominik
ZitatIch habe gerade einen Workaround eingebaut, dass alle 15min der aktuelle Status von Tuya via API (statt MQTT) bezogen wird. Funktioniert zwar auch nicht 100%, aber hilft ein bisschen. Sobald es bei Tuya wieder läuft, werde ich das entfernen.
den Workaround wieder entfernen.
Ja, scheint wieder zu laufen. Workaround ist in 0.1.181 wieder entfernt :)
Die Tuya Devs haben mitgeteilt, dass es "im Laufe der Woche" behoben sein sollte. Also wenn es die nächsten Tage noch "ruckelig" ist, sollte man sich nicht wundern.
Hallo,
So, ich habe mir jetzt mal das gateway, die Steckdosenleiste und die Türklingel zu gelegt.
Funktioniert soweit ganz gut, jedoch bei der Steckdosenleiste fehlt mir der Ausschalter für alle 3 dosen, den gibt es in der smartlife app.
Die 1. Dose ist dann auch auf state gemappt, die 2. auf switch_2, die 3. auf switch_3.
Finde ich nicht so ganz intuitive.
Internals:
DEF tuya_cloud tuya_cloud_connector bf30d34283b00ae207ikft
DEVICEID bf30d34283b00ae207ikft
FHEMPYTYPE tuya_cloud
FUUID 61a2bfba-f33f-b077-29fe-ead4c8a6c62b800c
IODev local_pybinding
NAME Steckdosenleiste_bf30d34283b00ae207ikft
NR 257
PYTHONTYPE tuya_cloud
STATE on
TYPE PythonModule
READINGS:
2021-11-29 16:51:53 active_time 1637967723
2021-11-29 16:51:53 biz_type 18
2021-11-29 16:51:53 category cz
2021-11-29 18:23:59 countdown_1 0.0
2021-11-29 18:23:59 countdown_2 0.0
2021-11-29 18:23:59 countdown_3 0.0
2021-11-29 16:51:53 create_time 1637967723
2021-11-29 16:51:53 icon https://images.tuyaeu.com/smart/icon/ay15084906260158s3Dr/1a1039c464e4370e237f5564672869c1.png
2021-11-29 16:51:53 id bf30d34283b00ae207ikft
2021-11-29 16:51:53 ip
2021-11-29 16:51:53 lat 49.2530
2021-11-29 16:51:53 local_key 6a439d7be42975d1
2021-11-29 16:51:53 lon 9.1277
2021-11-29 16:51:53 model Three-way smart socket (EU)
2021-11-29 16:51:53 name Steckdosenleiste
2021-11-29 16:51:53 node_id bc33acfffed841f9
2021-11-29 16:51:53 online off
2021-11-29 16:51:53 owner_id 43011480
2021-11-29 16:51:53 product_id 1obwwnmq
2021-11-29 16:51:53 product_name Power Strip
2021-11-29 18:23:59 state on
2021-11-29 16:51:53 sub on
2021-11-29 18:23:59 switch_2 on
2021-11-29 18:23:59 switch_3 on
2021-11-29 16:51:53 time_zone +01:00
2021-11-29 16:51:53 uid eu1637961043703mVBOO
2021-11-29 16:51:53 update_time 1638056786
2021-11-29 16:51:53 uuid bc33acfffed841f9
args:
Steckdosenleiste_bf30d34283b00ae207ikft
PythonModule
tuya_cloud
tuya_cloud_connector
bf30d34283b00ae207ikft
argsh:
Attributes:
alias Steckdosenleiste
group tuya_cloud
room fhempy
Die Türklingel sieht in FHEM so aus:
Internals:
DEF tuya_cloud tuya_cloud_connector bf7d83cc0888d028cdouzy
DEVICEID bf7d83cc0888d028cdouzy
FHEMPYTYPE tuya_cloud
FUUID 61a2bfbb-f33f-b077-ef60-eb4ced9a03b88cfa
IODev local_pybinding
NAME Tuerklingel_bf7d83cc0888d028cdouzy
NR 258
PYTHONTYPE tuya_cloud
STATE open
TYPE PythonModule
READINGS:
2021-11-29 16:51:53 active_time 1637965512
2021-11-29 18:18:18 battery_percentage 100.0
2021-11-29 16:51:53 biz_type 18
2021-11-29 16:51:53 category mcs
2021-11-29 16:51:53 create_time 1637965512
2021-11-29 16:51:53 icon https://images.tuyaeu.com/smart/icon/ay1559701439060fw6BY/84e150cd3935aa21975a5f28b9927753.png
2021-11-29 16:51:53 id bf7d83cc0888d028cdouzy
2021-11-29 16:51:53 ip
2021-11-29 16:51:53 lat 49.2530
2021-11-29 16:51:53 local_key 6a439d7be42975d1
2021-11-29 16:51:53 lon 9.1277
2021-11-29 16:51:53 model
2021-11-29 16:51:53 name Türklingel
2021-11-29 16:51:53 node_id 842e14fffef81989
2021-11-29 16:51:53 online on
2021-11-29 16:51:53 owner_id 43011480
2021-11-29 16:51:53 product_id ladpngdx
2021-11-29 16:51:53 product_name Doorbell
2021-11-29 18:18:18 state open
2021-11-29 16:51:53 sub on
2021-11-29 18:18:18 temper_alarm on
2021-11-29 16:51:53 time_zone +01:00
2021-11-29 16:51:53 uid eu1637961043703mVBOO
2021-11-29 16:51:53 update_time 1638178932
2021-11-29 16:51:53 uuid 842e14fffef81989
args:
Tuerklingel_bf7d83cc0888d028cdouzy
PythonModule
tuya_cloud
tuya_cloud_connector
bf7d83cc0888d028cdouzy
argsh:
Attributes:
alias Türklingel
group tuya_cloud
room fhempy
Der state bleibt hier immer auf open nur die readings zeit ändert sich.
Ist auch nicht so ganz einsichtig, oder?
Gruß
Carlos
Hi,
das mit switch_1, usw. ist leider nicht optimal, ich habe nur noch keine bessere Lösung gefunden.
Hintergrund:
Wenn man einen Zwischenstecker hat, der nur switch_1 kann, ist es umständlich immer switch_1 on/off zu machen und der Gesamtstatus des Devices ist dann auch unbekannt. Bei den meisten Steckdosenleisten ist _1 dann auch für alle, so habe ich es bis jetzt verstanden. In SmartLife dürfte die Gesamtschaltung ein "fake" sein. Da musst du dir wahrscheinlich ein DOIF oder so basteln welches alle schaltet.
Falls es eine bessere Idee für die Handhabung gibt, gerne melden :)
Geht der Status beim debuggen auf tuyaiot von False auf True?
Das ist der Code aktuell
# door window sensor
elif code == "doorcontact_state":
if value is True:
return "open"
return "closed"
Ist eigenartig, dass das auf open hängen bleibt. Kann nur sein, wenn tuya das nicht als bool sondern als Text liefert.
Hallo,
nachdem tuya mit python 3.7 wieder lief, habe ich ein update gemacht.. Leider bekomme ich jetzt folgende Fehlermeldung:
Failed to load module tuya_cloud: Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/fhem_pythonbinding.py", line 301, in _onMessage
functools.partial(importlib.import_module, pymodule)
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/utils.py", line 33, in run_blocking
return await asyncio.get_event_loop().run_in_executor(pool, function)
File "/usr/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
File "<frozen importlib._bootstrap>", line 983, in _find_and_load
File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 728, in exec_module
File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud.py", line 5, in <module>
from fhempy.lib.tuya_cloud.tuya_cloud_device import tuya_cloud_device
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 5, in <module>
from tuya_iot.device import TuyaDevice
File "/opt/fhem/.local/lib/python3.7/site-packages/tuya_iot/__init__.py", line 2, in <module>
from .device import TuyaDevice, TuyaDeviceListener, TuyaDeviceManager
File "/opt/fhem/.local/lib/python3.7/site-packages/tuya_iot/device.py", line 7, in <module>
from typing import Any, Literal, Optional
ImportError: cannot import name 'Literal' from 'typing' (/usr/lib/python3.7/typing.py)
Kann ich das fixen, oder .. Fhem läuft ja in einem LXC. Wenn ich den Snapshot zurückspiele, läuft es wieder..
Gruß
Jürgen k.
Ich hab seit heute ein kleines Problemchen. Ich wollte ein neues Gerät anlernen und hab den Server neu gestartet. Seitdem hab ich als State bei allen Geräten folgendes stehen:
Failed to load module tuya_cloud: Traceback (most recent call last): File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/fhem_pythonbinding.py", line 301, in _onMessage functools.partial(importlib.import_module, pymodule) File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/utils.py", line 33, in run_blocking return await asyncio.get_event_loop().run_in_executor(pool, function) File "/usr/lib/python3.7/concurrent/futures/thread.py", line 57, in run result = self.fn(*self.args, **self.kwargs) File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1006, in _gcd_import File "", line 983, in _find_and_load File "", line 967, in _find_and_load_unlocked File "", line 677, in _load_unlocked File "", line 728, in exec_module File "", line 219, in _call_with_frames_removed File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud.py", line 5, in from fhempy.lib.tuya_cloud.tuya_cloud_device import tuya_cloud_device File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 5, in from tuya_iot.device import TuyaDevice File "/opt/fhem/.local/lib/python3.7/site-packages/tuya_iot/__init__.py", line 2, in from .device import TuyaDevice, TuyaDeviceListener, TuyaDeviceManager File "/opt/fhem/.local/lib/python3.7/site-packages/tuya_iot/device.py", line 7, in from typing import Any, Literal, Optional ImportError: cannot import name 'Literal' from 'typing' (/usr/lib/python3.7/typing.py)
Und das neue Gerät wird auch nicht erkannt.
Gibt's dafür schon eine Lösung?
0.1.182 ist released, damit geht auch Python 3.7 wieder und es wird die tuya Library in der Version 0.5.0 verwendet solange 0.6.x noch nicht Python 3.7 ready ist.
Die 0.1.182 läuft schon. Ändert aber nichts.
Yep, hatte vergessen, dass paar Änderungen auch schon bei 0.5.0 von tuya kamen. Mit 0.1.183 sollte es jetzt klappen.
Läuft wieder mit 0.1.183.
Danke.
Jepp! löppt !!! Danke!!!
my tuya christmas lights come up in fhem as "8 Functies Lichten"
This is a name with spaces and i would like to change them in a name without spaces for easy commands.
rename 8 Functies Lichten christmaslights1 wont work.
Also rename 8_Functies_Lichten christmaslights1 doesnt.
How can i change this?
Provide a list of that device. I don't think that the device is with spaces, as fhem as far as I know doesn't allow spaces in names.
Hallo dominik,
nachdem ich mit meiner Weisheit am Ende bin, nun doch der Hilferuf...
Die Installation unter FHEM hat funktioniert, local_pybinding ist auf grün, fhempyserver_15733 ist auf status stopped, weil der tuya_cloud_connector mit dem state "fhempy server offline" keine Verbindung zu tuya iot aufbaut. Und da liegt wohl auch erst mal mein Problem, da komme ich nicht weiter. Das Cloud Project auf iot.tuya.com ist angelegt, Verbindung zur App (smartlife) ist hergestellt und meine beiden Devices (Gateway und Heizkörperthermostat) werden angezeigt und sind online.
Im Unterschied zu Deinen Service API sieht das bei mir aber anders aus. Ich bekomme nicht die Service API "Smart Home Devices Management" und "Smart Home Family Management" zu fassen, die ja wohl nicht ganz unerheblich sind. Weder beim Einrichten eines Projects noch danach. Woher bezieht man die?
Danke und Gruß
Uwe
local_pybinding steht sich auf Open? Weil wenn das Device fhempy Server offline schreibt, ist dort wahrscheinlich auch nicht Open.
Ansonsten mach nochmals das Define vom Setup Device und schau was im fhempy Log kommt.
Der sieht so aus:
Internals:
BindingType fhempy
DEF fhempy
DeviceName ws:127.0.0.1:15733
FUUID 61ab259e-f33f-342e-2989-ef7c1105f700535c
IP 127.0.0.1
NAME local_pybinding
NEXT_OPEN 1638692763.70962
NR 508
NTFY_ORDER 50-local_pybinding
PARTIAL
PORT 15733
STATE fhempy server offline
TYPE BindingsIo
localBinding 1
nextOpenDelay 10
READINGS:
2021-12-05 09:25:54 state fhempy server offline
args:
local_pybinding
BindingsIo
fhempy
argsh:
Attributes:
devStateIcon { my $status_img = "10px-kreis-gruen";; my $status_txt = "connected";; if (ReadingsVal($name, "state", "disconnected") eq "disconnected") { $status_img = "10px-kreis-rot";; $status_txt = "disconnected";; } my $ver = ReadingsVal($name, "version", "-");; "<div><a>".FW_makeImage($status_img, $status_txt)."</a><a> ".$ver." </a><a href=\"/fhem?cmd.dummy=set $name update&XHR=1\" title=\"Start update\">".FW_makeImage("refresh")."</a></div>" }
group fhempy
icon file_json-ld2
room fhempy
Und das steht endlos im Log:
SyntaxError: invalid syntax
File "FHEM/bindings/python/bin/fhempy", line 87
logging.getLogger(__name__).info(f"Successfully installed {package}")
^
Ah, welche Python Version hast du? Python 3.7 oder höher ist notwendig.
Danke, ja, Recht Du hast. Ich habe 2.7.13
Werde mich gleich mal drum kümmern.
Eigentlich sollte da eine Fehlermeldung kommen, dass die Version zu alt ist. Muss ich mir mal anschauen wieso das nicht kommt.
Die Aktualisierung von python ist ein größeres Projekt...meine Fresse. Das dauert noch, bis ich dahinter gestiegen bin.
Gruß
Uwe
Was nutzt du für ein System? Falls Debian, dann am besten auf bullseye aktualisieren.
Ja, Debian, und Danke für den Hinweis, der Bulle rennt gerade. Dauert etwas... ;)
Sodele, ich sträube mich etwas, diese Frage hier zu stellen, weil das eigentlich nicht der richtige Thread dafür ist, irgendwie passt's aber trotzdem.
Ich habe mich an folgende Installationsanweisung gehalten (https://www.linuxcapable.com/how-to-install-python-3-8-on-debian-11-bullseye/) und die Installation ist fehlerlos durchgelaufen.
Das Ergebnis von "ls -ls /usr/bin/python*" ist (sowohl vor als auch nach der Installation von 3.8.12):
0 lrwxrwxrwx 1 root root 9 Jan 24 2017 /usr/bin/python -> python2.7
0 lrwxrwxrwx 1 root root 9 Jan 24 2017 /usr/bin/python2 -> python2.7
3688 -rwxr-xr-x 1 root root 3775416 Apr 16 2021 /usr/bin/python2.7
0 lrwxrwxrwx 1 root root 9 Jan 20 2017 /usr/bin/python3 -> python3.5
4640 -rwxr-xr-x 2 root root 4751216 Nov 4 16:29 /usr/bin/python3.5
0 lrwxrwxrwx 1 root root 33 Nov 4 16:29 /usr/bin/python3.5-config -> x86_64-linux-gnu-python3.5-config
4640 -rwxr-xr-x 2 root root 4751216 Nov 4 16:29 /usr/bin/python3.5m
0 lrwxrwxrwx 1 root root 34 Nov 4 16:29 /usr/bin/python3.5m-config -> x86_64-linux-gnu-python3.5m-config
0 lrwxrwxrwx 1 root root 16 Jan 20 2017 /usr/bin/python3-config -> python3.5-config
0 lrwxrwxrwx 1 root root 10 Jan 20 2017 /usr/bin/python3m -> python3.5m
0 lrwxrwxrwx 1 root root 17 Jan 20 2017 /usr/bin/python3m-config -> python3.5m-config
Bei Eingabe von "python3 --version" erhalte ich:
Python 3.5.3
mit "python3.8 --version"
Python 3.8.12
Jetzt zum eigentlichen Problem. Irgendwie oder -wo muss ich dem System beibringen, nunmehr auf die Version 3.8.12 zuzugreifen. Laut Anleitung sollte dies durch
"sudo ldconfig /opt/Python-3.8.12" passieren (Der Bindestrich vor der 3 ist korrekt, entgegen der Anleitung lautet der Verzeichnisname Python-3.8.12). Tut es aber nicht. Auch ein Neustart bringt keinen Erfolg.
Hat jemand eine Idee, was ich noch tun muss?
Danke und Gruß
Uwe
Bitte, bitte nicht Python manuell installieren, das macht sonst nur Probleme.
Bullseye bringt per default Python 3.9 mit. Mach einfach ein
sudo apt update
sudo apt full-upgrade
sudo apt install python3
Das Upgrade hatte ich so anstoßen wollen, da meldet sich aber ein
python3 ist schon die neueste Version (3.5.3-1)
Daraufhin wollte ich den Heini überlisten und habe es manuell installiert. Klappt aber offenbar auch nicht.
Da bist du noch immer auf Stretch. Hast du alle /etc/apt/sources* angepasst?
Und...verdammt, ich muss mich korrigieren, mein Debian ist 9.13 stretch
Zitat von: dominik am 05 Dezember 2021, 16:51:46
Da bist du noch immer auf Stretch. Hast du alle /etc/apt/sources* angepasst?
Bin dabei. Das wird alles lustig. Never change... :-\
Ja, bisschen arbeit wird es sicher ;) Kommt immer darauf an, was man alles manuell installiert hat. Nicht vergessen danach mit Python 3.9 auch fhempy nochmals installieren. Python installiert nämlich die Packages pro Version.
So, der Sonntag ist fast rum und ich habe Bullseye laufen...Nun aber...da fehlt noch was:
Hast du auch das fhempyserver_15733 Device? Wenn ja, mach dort mal einen restart.
Das hab ich nicht und vermisse es...bei der ersten Installation hatte ich es. Wie bekomme ich das zu fassen?
Lösch nochmals das local_pybinding und erstell es nochmals, dann sollte automatisch das Device erstellt werden.
Ha...erwischt...10_fhempyServer und 10_fhempy fehlen im fhem-Verzeichnis. Wie kann das denn sein?
https://github.com/dominikkarall/fhempy#fhem
Die 3 Befehle nochmals ausführen. Keine Ahnung wie die verschluckt wurden :o
Nö, will nicht. Erst nachdem ich die controls_pythonbinding.txt gelöscht und alles nochmal angeworfen hatte, wurden die Dateien ins fhem-Verzeichnis geschoben.
Trotzdem fehlt das fhempyserver_15733 Device.
Folgende Meldung finde ich im Log:
2021.12.05 19:27:46 1: local_pybinding: Can't connect to ws:127.0.0.1:15733: Operation now in progress
2021.12.05 19:27:46 1: local_pybinding: Can't connect to ws:127.0.0.1:15733: 127.0.0.1: Verbindungsaufbau abgelehnt (111)
2021.12.05 19:27:46 1: BindingsIo (local_pybinding): ERROR local_pybinding - error while connecting: 127.0.0.1: Verbindungsaufbau abgelehnt (111)
Hast du local_pybinding gelöscht und neu angelegt?
Ja, eben nochmal - kein Erfolg
Jetzt hat mich der Kleister gepackt und ich habe dreimal hintereinander das Teil rausgeworfen und neu angelegt - jetzt ist er da.
Der tuya connector ist immer noch offline, aber das wird wohl auch noch werden... :D
Mach mal einen FHEM Neustart und dann poste mal ein list vom tuya connector (Credentials entfernen!)
Nach dem Neustart kann ich nun nicht mehr auf FHEM zugreifen, im Log sehe ich dieses:
2021.12.05 19:52:22 1: PERL WARNING: Use of uninitialized value in hash element at ./FHEM/10_PythonModule.pm line 65.
Undefined subroutine &CoProcess::start called at ./FHEM/10_fhempyServer.pm line 184.
Ich schmeiß erst mal alles wieder raus, damit wenigstens der Rest wieder läuft...oder?
Mach bitte mal in 10_fhempyServer.pm ein "use CoProcess;" unter use warnings; rein und starte dann FHEM wieder neu. Interessant dass das sonst noch niemand hatte.
Aber ich! Das Problem hatten wir (Prof. Dr. Peter A. Henning und ich) vor Jahren schon mal beim Testn der OWX-Module...bei mir treten immer die unmöglichsten Fehler auf...nix neues.
So, aber nun:
Ist im nächsten Update behoben ;)
Super, dass es jetzt läuft!
Vielen Dank für Deine Mühe. Zeit ist unbezahlbar, aber für einen Kaffee hat's gereicht ;)
Hehe, ja, danke dir! :)
Geht gleich weiter...aber nun keine Eile ;)
Ich habe ein Tuya Heizkörperthermostat:
Internals:
DEF tuya_cloud tuya_cloud bf2e450f5f4184fd52dfvt
DEVICEID bf2e450f5f4184fd52dfvt
FHEMPYTYPE tuya_cloud
FUUID 61ad1261-f33f-342e-716e-5ad98fe5c91d6d4f
IODev local_pybinding
NAME Ventil_AZ_bf2e450f5f4184fd52dfvt
NR 518
PYTHONTYPE tuya_cloud
STATE ready
TYPE PythonModule
READINGS:
2021-12-05 20:26:28 active_time 1638554106
2021-12-05 20:26:28 biz_type 18
2021-12-05 20:26:28 category wk
2021-12-05 21:36:44 child_lock off
2021-12-05 20:26:28 create_time 1638554106
2021-12-05 20:26:28 icon https://images.tuyaeu.com/smart/icon/ay1523512777050bLIId/f2360f527259e6e8662cb351095cd056.jpg
2021-12-05 20:26:28 id bf2e450f5f4184fd52dfvt
2021-12-05 20:26:28 ip
2021-12-05 20:26:28 lat 53.6132
2021-12-05 20:26:28 local_key 66f64dbe94a78f6a
2021-12-05 20:26:28 lon 9.8825
2021-12-05 21:36:44 mode eco
2021-12-05 20:26:28 model HY368Zigbee
2021-12-05 20:26:28 name Ventil AZ
2021-12-05 20:26:28 node_id 50325ffffe2c8656
2021-12-05 20:26:28 online on
2021-12-05 20:26:28 owner_id 43728709
2021-12-05 20:26:28 product_id cwnjrr72
2021-12-05 20:26:28 product_name HYTRV Smart
2021-12-05 20:26:27 state ready
2021-12-05 20:26:28 sub on
2021-12-05 21:36:44 temp_current 24.0
2021-12-05 21:36:44 temp_set 12.0
2021-12-05 20:26:28 time_zone +01:00
2021-12-05 20:26:28 uid eu16384762426707Xj66
2021-12-05 20:26:28 update_time 1638674913
2021-12-05 20:26:28 uuid 50325ffffe2c8656
args:
Ventil_AZ_bf2e450f5f4184fd52dfvt
PythonModule
tuya_cloud
tuya_cloud
bf2e450f5f4184fd52dfvt
Nun fehlt mir das WICHTIGSTE Reading überhaupt...die Ventilstellung. Meinst Du, Du kannst Deine neuen Freunde dort überreden, den Wert zu liefern?
Hintergrund: An Hand der Ventilstellung regele ich meine Heizung. Die Thermostate, die ich gerne ersetzen möchte, liefern mir diesen Wert und ein DOIF macht den Rest.
Danke und Gruß
Uwe
Da muss ich dich jetzt leider bitter enttäuschen, genau dieses Reading hat tuya nicht.
Ich habe auch tuya Thermostate, meine liefern zumindest work_mode als Reading mit Open/Closed. Ich habe bei mir überlegt über die Temperaturdifferenz zu gehen, das sollte ähnlich gut für die Steuerung funktionieren, falls du auch die Vorlauftemperatur regeln willst.
Schade, damit hat sich das mit diesem Thermostat erledigt. Ich brauche die Ventilstellung. Kennst Du oder einer der Mitstreiter hier ein unterstütztes Thermostat, welches die Ventilstellung liefert?
Gruß
Uwe
Die Thermostate liefern glaube ich die Werte via ZigBee. Du könntest zigbee2mqtt einsetzen, dann klappt es vielleicht.
Oder gerne bei tuya auch Feedback geben, dass du die valve Position gerne hättest. Vielleicht bauen sie es mal ein.
heute FHEM Update gemacht. BindingsIo etc.
Nach jedem Update sind im Attribut "ROOM" Filelog "fhempy"
die Einträge verschwunden!
Ist das Absicht?
Gruß
Bernd
Zitat von: dominik am 05 Dezember 2021, 22:39:31
Oder gerne bei tuya auch Feedback geben, dass du die valve Position gerne hättest. Vielleicht bauen sie es mal ein.
Danke für den Tipp, habe ich gemacht. Mal sehen, was sich da tut.
Danke und Gruß
Uwe
Zitat von: bewa58 am 06 Dezember 2021, 18:58:43
heute FHEM Update gemacht. BindingsIo etc.
Nach jedem Update sind im Attribut "ROOM" Filelog "fhempy"
die Einträge verschwunden!
Ist das Absicht?
Gruß
Bernd
Meinst du das fhempy_log Device oder ein anderes?
ZitatMeinst du das fhempy_log Device oder ein anderes?
JA
ZitatInternals
DEF
./log/fhempy-%Y-%m-%d.log fakelog
FD
87
FUUID
61af60ee-f33f-f967-f494-94b34d393cd4966a
FVERSION
92_FileLog.pm:0.249670/2021-09-13
NAME
fhempy_log
NR
524
NTFY_ORDER
50-fhempy_log
REGEXP
fakelog
STATE
active
TEMPORARY
1
TYPE
FileLog
currentlogfile
./log/fhempy-2021-12-07.log
logfile
./log/fhempy-%Y-%m-%d.log
habe gerade festgestellt: passiert bei jedem Neustart von FHEM
Wird anscheinend immer neu angelegt/überschrieben?
Und aus dem WIKI Filelog:
ZitatBis August 2021 war die Spezifikation von fakelog erforderlich bzw. möglich, um die Sonderbehandlung für diese Logdatei zu unterstützen. Mittlerweile ist das nicht mehr nötig und es wird (auch in der Beispielkonfiguration) der Wert Logfile empfohlen.
Zitat von: dominik am 05 Dezember 2021, 22:39:31
Oder gerne bei tuya auch Feedback geben, dass du die valve Position gerne hättest. Vielleicht bauen sie es mal ein.
Hallo dominik,
die Antwort von denen kam prompt, aber ich kann nicht allzu viel damit anfangen. Dass "valve_state" nicht im Standard-Status-Set enthalten ist, kann ich im Device Debugging sehen, aber der Part mit der APP sagt mir nichts. Kannst Du das interpretieren?
"
Hello, the valve status of your current device does not meet the cloud standard state set valve_state. Only in the APP control on https://developer.tuya.com/en/docs/iot/s?id=K9gf48r3k5ctd#title-0-Support%20reporting%20instructions%20to%20the %20cloud%20and%20sending%20instructions%20to%20the%20device"
Danke und Gruß
Uwe
Zitat von: bewa58 am 07 Dezember 2021, 14:38:31
JA
habe gerade festgestellt: passiert bei jedem Neustart von FHEM
Wird anscheinend immer neu angelegt/überschrieben?
Und aus dem WIKI Filelog:
Danke für den Hinweis. Werde ich korrigieren. Der Fehler war, dass ich -temporary verwendet hatte und daher das Device nicht gespeichert wurde. Ist im nächsten Update behoben.
Zitat von: UweH am 07 Dezember 2021, 18:05:51
Hallo dominik,
die Antwort von denen kam prompt, aber ich kann nicht allzu viel damit anfangen. Dass "valve_state" nicht im Standard-Status-Set enthalten ist, kann ich im Device Debugging sehen, aber der Part mit der APP sagt mir nichts. Kannst Du das interpretieren?
"Hello, the valve status of your current device does not meet the cloud standard state set valve_state. Only in the APP control on https://developer.tuya.com/en/docs/iot/s?id=K9gf48r3k5ctd#title-0-Support%20reporting%20instructions%20to%20the %20cloud%20and%20sending%20instructions%20to%20the%20device"
Danke und Gruß
Uwe
Genau, der Link zeigt auch, dass Tuya leider nur valve_state mit opened/closed rückmeldet. Ich verstehe das auch nicht, wieso sie den Öffnungsgrad nicht mitliefern. Ich denke da wirst du um zigbee2mqtt nicht herum kommen, ich werde es mal in nächster Zeit bei mir mit meinen Meross Thermostaten (auch tuya) probieren. Dongle um 20€ (sonoff zigbee 3.0 usb dongle plus) habe ich bereits.
Hallo, ich verscuhe mich an der lokalen Version um die Unterschiede zwischen den beiden Modulen zu erkennen.
Leider habe ich bei den Punkten 10 und 11 Probleme die genannten Aktionen auszuführen, da ich weder "API Groups" noch "Apply" irfendwo finde.
Wahrscheinlich wurde auf der Tuya-Seite was umbenannt.
Kannst du behilflich sein und die Punkte mit der aktuellen Tuya-Webseite abgleichen, bitte.
Hi,
Tuya hat im Oktober da etwas umgestellt, wenn ich das richtig verstanden habe. Einige der benötigten API´s sollten nun alle in IoTCore enthalten sein. Zusätzlich wird sicherlich Authorization, General Permissions Management und Device Status Notification benötigt werden...
Ich habe so einige Probleme neue Geräte einzubinden. Über den Cloudconnector habe ich gestern ein neues Heizgerät eingebunden. In den Readings sind dann auch local_key, device_id und product_id enthalten, die man auch benötigt, um Tuya Devices lokal einzubinden, was komischerweise nicht mehr geht :-( Ich habe 2 baugleiche Heizgeräte. Eines ist schon seit langer Zeit lokal eingebunden, das andere neue bekomme ich einfach nicht online, wieso auch immer... IP stimmt, local_key, device_id product_id sind richtig (hab ich auch über BlueStacks und BSTweaker extrahiert Anleitung unter https://www.youtube.com/watch?v=YKvGYXw-_cE), aber kommt einfach nicht online :-(
Über die Cloud Anbindung kann ich zwar schalten, aber die Readings werden exakt 1 mal aktualisiert, wenn das Gerät angelegt wird...
Auch habe ich auf iot.tuya.com Probleme, die Cloud Development Umgebung ordentlich zum Laufen zu bringen. Ich konnte das Cloud Projekt anlegen, und auch meinen Account linken. Wenn ich aber auf den Reiter "Devices" gehe kommt eine Fehlermeldung "Params Illegal"... Ich bin im richtigen DataCenter und auch im API-Explorer kann ich die Infos meiner Geräte abfragen...
Alles ziemlich bizarr...
Im Übrigen werden auch unter IO-Broker (läuft nicht parallel zu fhempy ----> tuya kann sich nur mit 1 mal verbinden, parallel Verbindungen nicht möglich) neue Geräte nicht mehr angelegt... Und hier frage ich mich, ob die Verbindung zur Cloud aufrecht erhalten bleibt und dadurch eine lokale Verbindung nicht mehr möglich ist...
Aber, wenn ich das Gerät aus der App lösche, dann verliert es auch die WiFi Verbindung bei mir...
Alles ziemlich bizarr...
Falls jemand noch so bizarre Phänome hat, oder die Lösung kennt, gerne posten ;-)
Gruss Jan
Mir fehlen folgende Punkte:
Open "API Groups" on the tuya portal
Click "Apply" for
Authorization management
Device management
Device ControlZitatEinige der benötigten API´s sollten nun alle in IoTCore enthalten sein. Zusätzlich wird sicherlich Authorization, General Permissions Management und Device Status Notification benötigt werden...
Diese Aussage bringt mich leider nicht wirklich weiter, da offenbar nicht nur verschoben wurde sondern auch Begriffe/Buttons umbenannt.
Hallo,
Neuer Tag, neue Recherche, neue Erkenntnisse :-)
Also laut Installationsaleitung von Tuya für den IOBroker https://github.com/Apollon77/ioBroker.tuya (https://github.com/Apollon77/ioBroker.tuya) soll man für die Geräte unbedingt mit der Smartlife App Version < 3.14 in Betrieb nehmen, da ab den neueren Versionen der Traffic verschlüsselt wird... Also, App Downgrade, Geräte neu eingebunden et voila... Es läuft :-)
Diese Info sollte vielleicht ins Readme für die Tuya lib mit aufgenommen werden... Ich denke dieser Thread ist auch nicht der Richtige hier, da Tuya Cloud...
Gruss Jan
Zitat von: Superposchi am 11 Dezember 2021, 14:56:43
Mir fehlen folgende Punkte:
Open "API Groups" on the tuya portal
Click "Apply" for
Authorization management
Device management
Device Control
Diese Aussage bringt mich leider nicht wirklich weiter, da offenbar nicht nur verschoben wurde sondern auch Begriffe/Buttons umbenannt.
Diese Punkte gibt es auch nicht mehr.. Ist nun standartmässig im IoT Core enthalten. Du musst eine Cloudprojekt anlegenm bei Industry und Development Method "Smart Home" auswählen. Dann unter My Services noch schauen, ob Authorisation, Device Status Notification,General Permission Management subscribed sind.
Gruss Jan
Zitat von: dominik am 05 Dezember 2021, 22:39:31
Die Thermostate liefern glaube ich die Werte via ZigBee. Du könntest zigbee2mqtt einsetzen, dann klappt es vielleicht.
Moin,
ich habe jetzt mal den ganzen Kram installiert und war auch teilweise erfolgreich. Meine beiden ZigBee-Fensterkontakte sehe ich mittlerweile in FHEM und sie liefern mir auch den richtigen Status. Nur dieses Thermostat redet nicht mit mir. Ich kann das noch so oft in den Anlernmodus versetzen und alles mögliche mit dem MQTT-Broker, Device und Server veranstalten, das Ding meldet sich nicht. Ich suche den Fehler auch immer noch auf meiner Seite, aber da ich die beiden Kontakte erfolgreich integriert habe, scheint es doch eher am Thermostat zu liegen. Nun übe ich mich mal in Geduld und warte, bis Du dein Thermostat über zigbee2mqtt anschließt. Vielleicht funktioniert es ja mit diesem.
Gruß
Uwe
EDIT: Laut Liste der kompatiblen Devices sollte es funktionieren und der Ventilstand wird ausgegeben...https://www.zigbee2mqtt.io/devices/TS0601_thermostat.html (https://www.zigbee2mqtt.io/devices/TS0601_thermostat.html).
Erstmal sorry, dass ich mit dem Thema eigentlich im falschen Thread unterwegs bin, aber da wir hier davon angefangen haben, beende ich es hier auch ;-)
UPDATE:
Kaum macht man's richtig, schon funktioniert's. Mittlerweile läuft's auch über zigbee2mqtt, ich bekomme u.a. die Ventilstellung geliefert und kann das Thermostat über FHEM bedienen. Schon mal nicht schlecht.
zigbee2mqtt hat einige Fallstricke zu bieten. Die Installation ist relativ problemlos, aber bei der Konfigurationsdatei geht's los und endet bei der Geräteerkennung, die wohl auch nicht auf jedem System gleich abläuft. Da ist ganz viel try and error angesagt. Offenbar können auch Geräte nicht gleichzeitig von der tuya-App und zigbee2mqtt genutzt werden. Wenn man das aber will, ist fhempy die bessere Wahl. Andererseits hat es auch einen gewissen Charme, zigbee-Geräte ohne chinesische Cloud-Server zu bedienen...
In der Zwischenzeit habe ich 4 weitere Thermostate getestet und alle wieder zurückgeschickt, bäh... (essentials Smart Home Heizungsthermostat Premium, MoesGo Zigbee Smart Heizungsthermostat (https://www.amazon.de/dp/B09BCF66T8/ref=pe_27091401_487024491_TE_item (https://www.amazon.de/dp/B09BCF66T8/ref=pe_27091401_487024491_TE_item)), EUROTRONIC Spirit, essentials Smart Home Heizkörperthermostat Zigbee). Das verwendete tuya-Teil hebt sich schon deutlich ab, sowohl im Design als auch funktional. Nun ist noch das Thermostat von Fritz und von Shelly im Zulauf. Beide nicht zigbee, aber das ist ein anderes Thema.
Viele Grüße und schöne Feiertage
Uwe
ZitatZitat von: bewa58 am 07 Dezember 2021, 14:38:31
FILELOG
habe gerade festgestellt: passiert bei jedem Neustart von FHEM
Wird anscheinend immer neu angelegt/überschrieben?
Danke für den Hinweis. Werde ich korrigieren. Der Fehler war, dass ich -temporary verwendet hatte und daher das Device nicht gespeichert wurde. Ist im nächsten Update behoben.
habe ich die vergangenen Tage nicht richtig beobachtet, aber ich glaube das hattest du schon korrigiert !?
Heute nach Update aber wieder verschwunden! Filelog werden die Raumzuordnungen gelöscht.
Hi,
nach meinem Update auf Bullseye habe ich irgendwie Probleme mit Tuya.
Es läuft ne ganz Zeit lang und dann kann ich keine Steckdosen mehr schalten.
Python habe ich von Bullseye und sagt:
python3 ist schon die neueste Version (3.9.2-3).
Im Log finde ich dieses:
[2021-12-21 03:04:26,548] [tuya-openmq] Unexpected disconnection.7
2021-12-21 03:04:26,548 - ERROR - tuya iot: Unexpected disconnection.7
[2021-12-21 03:31:08,572] [tuya-openmq] error while get mqtt config
2021-12-21 03:31:08,572 - ERROR - tuya iot: error while get mqtt config
Exception in thread Thread-34:
Traceback (most recent call last):
File "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
self.run()
File "/opt/fhem/.local/lib/python3.9/site-packages/sentry_sdk/integrations/threading.py", line 69, in run
reraise(*_capture_exception())
File "/opt/fhem/.local/lib/python3.9/site-packages/sentry_sdk/_compat.py", line 54, in reraise
raise value
File "/opt/fhem/.local/lib/python3.9/site-packages/sentry_sdk/integrations/threading.py", line 67, in run
return old_run_func(self, *a, **kw)
File "/opt/fhem/.local/lib/python3.9/site-packages/tuya_iot/openmq.py", line 174, in run
time.sleep(self.mq_config.expire_time - 60)
AttributeError: 'NoneType' object has no attribute 'expire_time'
[2021-12-21 09:26:08,758] [tuya-openmq] error while get mqtt config
2021-12-21 09:26:08,758 - ERROR - tuya iot: error while get mqtt config
Exception in thread Thread-39:
Traceback (most recent call last):
File "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
self.run()
File "/opt/fhem/.local/lib/python3.9/site-packages/sentry_sdk/integrations/threading.py", line 69, in run
reraise(*_capture_exception())
File "/opt/fhem/.local/lib/python3.9/site-packages/sentry_sdk/_compat.py", line 54, in reraise
raise value
File "/opt/fhem/.local/lib/python3.9/site-packages/sentry_sdk/integrations/threading.py", line 67, in run
return old_run_func(self, *a, **kw)
File "/opt/fhem/.local/lib/python3.9/site-packages/tuya_iot/openmq.py", line 174, in run
time.sleep(self.mq_config.expire_time - 60)
AttributeError: 'NoneType' object has no attribute 'expire_time'
[2021-12-21 17:19:28,688] [tuya-openmq] error while get mqtt config
2021-12-21 17:19:28,688 - ERROR - tuya iot: error while get mqtt config
Exception in thread Thread-46:
Traceback (most recent call last):
File "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
self.run()
File "/opt/fhem/.local/lib/python3.9/site-packages/sentry_sdk/integrations/threading.py", line 69, in run
reraise(*_capture_exception())
File "/opt/fhem/.local/lib/python3.9/site-packages/sentry_sdk/_compat.py", line 54, in reraise
raise value
File "/opt/fhem/.local/lib/python3.9/site-packages/sentry_sdk/integrations/threading.py", line 67, in run
return old_run_func(self, *a, **kw)
File "/opt/fhem/.local/lib/python3.9/site-packages/tuya_iot/openmq.py", line 174, in run
time.sleep(self.mq_config.expire_time - 60)
AttributeError: 'NoneType' object has no attribute 'expire_time'
2021-12-21 20:47:07,548 - WARNING - zeroconf: Received invalid packet from ('192.168.69.57', 5353) at offset 107 while unpacking b'\x00\x00\x00\x00\x00\x04\x00\x00\x00\x00\x00\x00<amzn.dmgr:AF1F129AEFDDE8D4F7AD7476377359FF:XVM/zoXQ0O:665688\x0b_amzn-wplay\x04_tcp\x05local\x00\x00!\x00\x01\xc0\x0c\x00\x10\x00\x01\x9b92-168-69-69-fritz-box-fritz-box-fritz-box-fritz-.fritz-box-fritz-box0\x01\xc0\x80\x10\x01\xc0\x80\xc0\x80\x0e\x0f\xc0\x80\xc7\x83a=0\x13c=da:be.65:1e:15:c5\x10ad=ATNLRCEBX3W4P\x04pv=1\x03f=0\x04mv=2\x05dpv=1\x0fn=Sybille Fire\x0fat=2Ib17DjsDrBx\x03s=0\x03t=2"u=A1F129AEFDDE8D4F7AD7476377359FF\x03v=2\x08sp=46516\x06tr=tcp\x00\x00\x01\x00\x01\xc0k\x00\x1c\x00\x01'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/zeroconf/_protocol/incoming.py", line 111, in _parse_data
parser_call()
File "/opt/fhem/.local/lib/python3.9/site-packages/zeroconf/_protocol/incoming.py", line 103, in _initial_parse
self.read_questions()
File "/opt/fhem/.local/lib/python3.9/site-packages/zeroconf/_protocol/incoming.py", line 159, in read_questions
self.questions = [
File "/opt/fhem/.local/lib/python3.9/site-packages/zeroconf/_protocol/incoming.py", line 160, in <listcomp>
DNSQuestion(self.read_name(), *self.unpack(b'!HH', 4)) for _ in range(self.num_questions)
File "/opt/fhem/.local/lib/python3.9/site-packages/zeroconf/_protocol/incoming.py", line 275, in read_name
self.offset = self._decode_labels_at_offset(self.offset, labels, seen_pointers)
File "/opt/fhem/.local/lib/python3.9/site-packages/zeroconf/_protocol/incoming.py", line 295, in _decode_labels_at_offset
raise IncomingDecodeError(f"DNS compression type {length} is unknown at {off}")
zeroconf._exceptions.IncomingDecodeError: DNS compression type 155 is unknown at 107
Irgendeine Idee was ich tun kann?
P.S.: Ok habe die Steckdose über die App geschaltet das ging.
Über FHEM ging nichts, selbst nach FHEMPY neustert usw.
Dann habe ich die Steckdose Stromlos gemacht und wieder reingesteckt und sie lies sich wieder schalten.
Kennt ihr soetwas?
Danke und Gruß,
Stefan
Zitat von: JF Mennedy am 10 Dezember 2021, 17:41:03
Auch habe ich auf iot.tuya.com Probleme, die Cloud Development Umgebung ordentlich zum Laufen zu bringen. Ich konnte das Cloud Projekt anlegen, und auch meinen Account linken. Wenn ich aber auf den Reiter "Devices" gehe kommt eine Fehlermeldung "Params Illegal"... Ich bin im richtigen DataCenter und auch im API-Explorer kann ich die Infos meiner Geräte abfragen...
Gibt es dafür schon ein Workaround? Das gehört ja eigentlich nicht hier hin, frage aber trotzdem einmal.
Ich wollte das heute auch Einrichten nach dieser Anleitung hier: "https://www.home-assistant.io/integrations/tuya/"
Bin bei dem Kapitel "LINK DEVICES BY APP ACCOUNT"
Sobald ich aber auf den Reiter Device klicke, kommt: "Beim Verbinden mit eu.iot.tuya.com trat ein Fehler auf. .. Dieses Problem kann manchmal auftreten, wenn Cookies deaktiviert oder abgelehnt werden"
Hab schon den Browser gewechselt, mit den Cookies gespielt, ein neues Cloud Projekt angelegt. Keine Wirkung. :(
Danke und Gruß Michael
Hi,
mein Problem besteht leider weiterhin.
Habe dazu auch etwas gefunden:
https://github.com/tuya/tuya-home-assistant/issues/741
Wüsste aber nicht wie ich das hier anwenden kann.
Heute morgen sind 3 Steckdosen tot und lassen sich nicht mehr per FHEM schalten.
Erst wenn ich die Steckdosen stromlos mache und wieder einstecke.
Ich bin in der Tuya App, eventuell wechsle ich mal auf die SmartHome App.
Ich denke das verwenden die meisten hier?
Gruß und Danke,
Stefan
Zitat von: Meesus am 21 Dezember 2021, 23:53:10
Gibt es dafür schon ein Workaround? Das gehört ja eigentlich nicht hier hin, frage aber trotzdem einmal.
Ich wollte das heute auch Einrichten nach dieser Anleitung hier: "https://www.home-assistant.io/integrations/tuya/"
Bin bei dem Kapitel "LINK DEVICES BY APP ACCOUNT"
Sobald ich aber auf den Reiter Device klicke, kommt: "Beim Verbinden mit eu.iot.tuya.com trat ein Fehler auf. .. Dieses Problem kann manchmal auftreten, wenn Cookies deaktiviert oder abgelehnt werden"
Hab schon den Browser gewechselt, mit den Cookies gespielt, ein neues Cloud Projekt angelegt. Keine Wirkung. :(
Danke und Gruß Michael
Hat sich erledigt.
Habe nochmal eine Anmeldung am TuyaSmartDeveloperCenter mit einem neuen Account gemacht und die Schritte wiederholt. Nun kann ich auch auf den "Device" Reiter klicken und sehe mein Tuya TR9B (WIFI) Thermostat für die Fussboden Heizung. Am Handy nehme ich die SmartLife App.
Aber hier unter FHEM habe ich das Problem das nicht alle "Set" Befehle funktionieren.
Alle set temp_xxxx Befehle funktionieren nicht. Er nimmt diese einfach nicht an. Normale ohne Temperatur, wie Kindersicherung / On / Off /Frost / WorkDay, funktionieren einwandfrei.
Woran könnte das liegen?
defmod Floor_Heating_bfdf3cdcd304788d08r7kw PythonModule tuya_cloud tuya_cloud_connector bfdf3cdcd304788d08r7kw
attr Floor_Heating_bfdf3cdcd304788d08r7kw alias Floor Heating
attr Floor_Heating_bfdf3cdcd304788d08r7kw group tuya_cloud
attr Floor_Heating_bfdf3cdcd304788d08r7kw room fhempy
setstate Floor_Heating_bfdf3cdcd304788d08r7kw on
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 21:29:53 active_time 1640085444
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 21:29:53 biz_type 18
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 21:29:53 category wk
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 22:05:25 child_lock off
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 21:29:53 create_time 1616097419
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 22:05:25 frost off
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 21:29:53 icon https://images.tuyaeu.com/smart/icon/ay1547209623516pqlXf/010b3328b726f7547fbdba8d74f192fb.png
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 21:29:53 id bfdf3cdcd304788d08r7kw
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 21:29:53 ip 84.139.98.93
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 21:29:53 lat 51.4934
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 21:29:53 local_key xxxxxx
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 21:29:53 lon 7.5792
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 22:05:25 lower_temp 5.0
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 22:05:25 mode manual
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 21:29:53 model
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 21:29:53 name Floor Heating
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 21:29:53 online on
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 21:29:53 owner_id 45631160
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 21:29:53 product_id 7qx0q329p61h1ace
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 21:29:53 product_name Floor Heating
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 22:05:25 state on
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 21:29:53 sub off
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 22:05:25 temp_current 21.2
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 22:05:25 temp_set 20.5
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 22:05:25 temp_unit_convert c
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 21:29:53 time_zone +01:00
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 21:29:53 uid eu1640085171343OoE8z
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 21:29:53 update_time 1640291217
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 22:05:25 upper_temp 50.0
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 21:29:53 uuid be3a8c49a105fc76
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 22:05:25 valve_state close
setstate Floor_Heating_bfdf3cdcd304788d08r7kw 2021-12-23 22:05:25 work_days 6_1
@Messus
Funktionieren die set Befehle über die Tuya IOT Plattform wenn du dort Debug Device auswählst?
@stefanru
Der Fehler dürfte mit 0.6.4 vor 3h behoben worden sein. Das Problem, weiterhin kein Python 3.7 support. Nachdem dort aber auch Token Fehler behoben wurde, neige ich dazu 0.6.4 zu releasen. Gibt es hier noch jemanden der Python 3.7 verwendet?
@bewa98
Kannst du bitte nochmals ein Update machen und testen? Ist mit 0.1.188 behoben. Update machen, dann neu starten, dann Raum setzen und nochmals neu starten. Danach sollte der Raum zugeordnet bleiben.
@UweH
Danke für die Info. Ich werde meine Thermostate auch noch testen. Ich werde auch noch ein fhempy zigbee2mqtt Modul releasen, damit man nicht umständlich installieren/updaten muss. Bisher bin ich bei mir mit zigbee2mqtt mit 40 Devices super zufrieden.
Hi Dominik,
vielen Dank!
Ich bin irgendwie zu blöd zu kapieren was du mit 0.6.4 meinst?
Ich sehe in deinem GIT keine Änderung und auch die Version passt nicht zu fhempy.
Kannst du mir erklären auf was du dich genau beziehst?
P.S.: Meinst du das tuya sdk?
Installiere ich mit
pip install tuya-iot-py-sdk==0.6.4
richtig?
Oh das bringt wohl nichts da der Server beim starten folgendes sagt:
2021-12-25 01:42:53,011 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2021-12-25 01:42:53,349 - INFO - fhempy.lib.pkg_installer: Attempting install of tuya-iot-py-sdk==0.5.0
2021-12-25 01:43:05,861 - INFO - fhempy.lib.pkg_installer: Successfully installed tuya-iot-py-sdk==0.5.0 update!
Da muss ich wohl warten bis du es updatest.
Vielen Dank,
Stefan
Sorry, war von mir unklar ausgedrückt. Genau, ich meinte die tuya-iot-py-sdk Library.
Ich habe gerade ein fhempy update released (0.1.189), teste bitte damit.
ACHTUNG: Release 0.1.189 erfordert Python>3.7!!
Hi Dominik,
Zitat
@Messus
Funktionieren die set Befehle über die Tuya IOT Plattform wenn du dort Debug Device auswählst?
Danke für den Tip mit dem testen in der "Device Debugging" Umgebung. Hier wird mir optisch auch jetzt klar warum das in FHEM nicht funktionierte.
Wenn ich die Zahlen durch 10 teile dann stimmt der Wert und kommt dann auch mit dem ..."temp_set" an. Da stimmt also etwas bei der Umrechnung dieser Zahlen bei meinem Thermostat nicht.
Beispiel: Also die Temperatur 23° wird als 230° ausgeben. Der Bereich ist von 50-10000C° (!) wählbar, das wäre mir dann doch ein wenig zu heiß im Bad. :-) Gibt es die Möglichkeit das direkt in der "Device Debugging" Umgebung auf der Tuya IOT Plattform Seite zu korrigieren?
Danke und Gruß Michael
Zitat von: dominik am 26 Dezember 2021, 10:41:46
Ich habe gerade ein fhempy update released (0.1.189), teste bitte damit.
Bin ich der Zeit voraus? ;)
Zitat von: Meesus am 26 Dezember 2021, 13:09:28
Beispiel: Also die Temperatur 23° wird als 230° ausgeben. D
Das Problem habe ich auch. Ich muss 210° einstellen, um 21,0° zu setzen.
Uij, da wird es aber warm bei euch :D
Erstellt bitte mal hier einen Request bei tuya und fügt die product id und category id hinzu:
https://service.console.tuya.com/8/2/create?step=3&id=01030503&source=support_center
Vielleicht kann das Tuya selbst korrigieren, weil da fehlt ein Wert (scale) und daher erfolgt keine Umrechnung. Falls die Rückmeldung kommt, dass es nicht möglich ist, kann es die product id als Ausnahme hinterlegen - da würde ich aber gerne vermeiden.
ZitatHi Dominik,
alles klar, mach ich so.
Danke für die Info & Deine Mühe, mal gespannt ob das von denen gefixt wird.
Gruß Michael
Ich hatte gestern dann noch ein Service Request bei Tuya deswegen aufgemacht.
Heute dann prompt die Antwort:
Zitat
Tuya engineer12-27 02:53:18
Hello, thank you for waiting. The functional instructions of the device are defined by the manufacturer during production. The data you see (230) is actually delivered by API, but the data displayed by the manufacturer on the APP is 23.
You can feedback to the manufacturer for modification
So wie sie es schreiben, soll ich das Problem an den Hersteller des Thermostats weiterleiten. Das wird vermutlich ins leere laufen da ich das Ding bei AliExpress vor einem Jahr bestellt hatte und das ich nur den Typ kenne. Auf der Bedienungsanleitung & dem Gerät steht leider kein Hersteller. :(
Hi Dominik,
vielen Dank. Alle Fehler im Log sind weg und es scheint jetzt auch wieder durchgängig zu funktionieren.
Ich hätte noch eine Frage bzw. Anregung.
Ich habe einen Kühschrank zur Verbrauchsmessung angeschlossen.
Die power readings kommen aber in FHEM halt doch relativ sporadisch und in unterschiedlichen Abständen an.
Die App zeigt das viel schneller an.
Ich habe mal etwas rumgesucht und bin auf dieses hier gestoßen:
https://github.com/rospogrigio/localtuya/pull/549 (Periodically send update dps command)
Es wurde ein update interval eingeführt, dass wohl ein update dps im intervall sendet, besonders für WiFi Socket scheint dies gut zu funktionieren.
UPDATEDPS: {"hexByte": 0x12, "command": {"dpId": [18, 19, 20]}},
Ich habe auch etwas in deinem Coding rumgeschaut aber blicke noch nicht ganz durch wo ich das zum testen mal einhacken könnte.
Danke und Gruß,
Stefan
Hallo,
ich habe eine Kamera von Action erworben, welche auch erkannt und in Fhem mit einigen Set Befehlen eingebunden ist. Gibt es die Möglichkeit auch das Video zu übertragen, um es im TabletUi anzuzeigen?
Zitat@bewa98
Kannst du bitte nochmals ein Update machen und testen? Ist mit 0.1.188 behoben. Update machen, dann neu starten, dann Raum setzen und nochmals neu starten. Danach sollte der Raum zugeordnet bleiben.
funktioniert jetzt.
Neues Problem(chen):
Ist es möglich bei Lampen Devices etc. "Toggle" mit in die Set-Anweisung zu bringen?
In der Smartlife-App wird auch so geschaltet.
Hallo,
ich hatte Fhempy und Tuya cloud schon erfolgreich laut Anleitungen installiert und am Laufen. Nach ein paar Tagen funktionierte es nicht mehr.
Hab den Tuya Connector auch mal aus Fhem gelöscht und wieder neu definiert aber es kommen immer diese Fehlermeldungen:
Failed to load module tuya_cloud: Traceback (most recent call last): File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/fhem_pythonbinding.py", line 301, in _onMessage functools.partial(importlib.import_module, pymodule) File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/utils.py", line 33, in run_blocking return await asyncio.get_event_loop().run_in_executor(pool, function) File "/usr/lib/python3.7/concurrent/futures/thread.py", line 57, in run result = self.fn(*self.args, **self.kwargs) File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1006, in _gcd_import File "", line 983, in _find_and_load File "", line 967, in _find_and_load_unlocked File "", line 677, in _load_unlocked File "", line 728, in exec_module File "", line 219, in _call_with_frames_removed File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud.py", line 5, in from fhempy.lib.tuya_cloud.tuya_cloud_device import tuya_cloud_device File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 5, in from tuya_iot.device import TuyaDevice File "/opt/fhem/.local/lib/python3.7/site-packages/tuya_iot/__init__.py", line 2, in from .device import TuyaDevice, TuyaDeviceListener, TuyaDeviceManager File "/opt/fhem/.local/lib/python3.7/site-packages/tuya_iot/device.py", line 7, in from typing import Any, Literal, Optional ImportError: cannot import name 'Literal' from 'typing' (/usr/lib/python3.7/typing.py)
Komme hier nicht mehr weiter. Hat jemand eine Idee wie ich vorgehen könnte?
fhempy_server "RESTART" probieren.
Das hilft bei mir wenn ich Probleme mit der Ring Doorbell habe
Hi scank,
dein Problem weißt aber eher darauf hin das python 3.7 nicht mehr geht weil typing.py in 3.7 das noch nicht kann.
Siehe hier:
https://stackoverflow.com/questions/61206437/importerror-cannot-import-name-literal-from-typing?noredirect=1&lq=1
Gruß,
Stefan
Zitat von: scank am 05 Januar 2022, 09:17:04
Hallo,
ich hatte Fhempy und Tuya cloud schon erfolgreich laut Anleitungen installiert und am Laufen. Nach ein paar Tagen funktionierte es nicht mehr.
Hab den Tuya Connector auch mal aus Fhem gelöscht und wieder neu definiert aber es kommen immer diese Fehlermeldungen:
Failed to load module tuya_cloud: Traceback (most recent call last): File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/fhem_pythonbinding.py", line 301, in _onMessage functools.partial(importlib.import_module, pymodule) File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/utils.py", line 33, in run_blocking return await asyncio.get_event_loop().run_in_executor(pool, function) File "/usr/lib/python3.7/concurrent/futures/thread.py", line 57, in run result = self.fn(*self.args, **self.kwargs) File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1006, in _gcd_import File "", line 983, in _find_and_load File "", line 967, in _find_and_load_unlocked File "", line 677, in _load_unlocked File "", line 728, in exec_module File "", line 219, in _call_with_frames_removed File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud.py", line 5, in from fhempy.lib.tuya_cloud.tuya_cloud_device import tuya_cloud_device File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 5, in from tuya_iot.device import TuyaDevice File "/opt/fhem/.local/lib/python3.7/site-packages/tuya_iot/__init__.py", line 2, in from .device import TuyaDevice, TuyaDeviceListener, TuyaDeviceManager File "/opt/fhem/.local/lib/python3.7/site-packages/tuya_iot/device.py", line 7, in from typing import Any, Literal, Optional ImportError: cannot import name 'Literal' from 'typing' (/usr/lib/python3.7/typing.py)
Komme hier nicht mehr weiter. Hat jemand eine Idee wie ich vorgehen könnte?
ich habe dasselbe Problem seit wenigen Tagen - ohne das System verändert zu haben
genauer habe ich jedoch ein FHEM-Update durchgeführt
wie kann das Problem gelöst werden ?
ich bitte um Hilfe
Herzliche Grüße
Thomas
Zitat von: dominik am 26 Dezember 2021, 10:41:46
Sorry, war von mir unklar ausgedrückt. Genau, ich meinte die tuya-iot-py-sdk Library.
Ich habe gerade ein fhempy update released (0.1.189), teste bitte damit.
ACHTUNG: Release 0.1.189 erfordert Python>3.7!!
Hallo dominic,
kann es sein, dass dies hier die heute vormittag angesprochene Problematik erklärt?
Wie kriege ich heraus, welche Python Version bei mir installiert ist bzw. wie date ich sie up?
Herzliche Grüße
Thomas
inzwischen habe ich eine Anleitung gefunden, um von 3.7 auf 3.9.5 upzudaten:
https://itheo.tech/install-python-395-on-raspberry-pi-step-by-step (https://itheo.tech/install-python-395-on-raspberry-pi-step-by-step)
nach "sudo make install"
bekomme ich die Fehlermeldung
fi
ERROR: Exception:
Traceback (most recent call last):
File "/tmp/tmpsozrb6nn/pip-21.1.1-py3-none-any.whl/pip/_internal/cli/base_command.py", line 180, in _main
status = self.run(options, args)
File "/tmp/tmpsozrb6nn/pip-21.1.1-py3-none-any.whl/pip/_internal/cli/req_command.py", line 204, in wrapper
return func(self, options, args)
File "/tmp/tmpsozrb6nn/pip-21.1.1-py3-none-any.whl/pip/_internal/commands/install.py", line 269, in run
session = self.get_default_session(options)
File "/tmp/tmpsozrb6nn/pip-21.1.1-py3-none-any.whl/pip/_internal/cli/req_command.py", line 77, in get_default_session
self._session = self.enter_context(self._build_session(options))
File "/tmp/tmpsozrb6nn/pip-21.1.1-py3-none-any.whl/pip/_internal/cli/req_command.py", line 87, in _build_session
session = PipSession(
File "/tmp/tmpsozrb6nn/pip-21.1.1-py3-none-any.whl/pip/_internal/network/session.py", line 275, in __init__
self.headers["User-Agent"] = user_agent()
File "/tmp/tmpsozrb6nn/pip-21.1.1-py3-none-any.whl/pip/_internal/network/session.py", line 132, in user_agent
linux_distribution = distro.linux_distribution() # type: ignore
File "/tmp/tmpsozrb6nn/pip-21.1.1-py3-none-any.whl/pip/_vendor/distro.py", line 125, in linux_distribution
return _distro.linux_distribution(full_distribution_name)
File "/tmp/tmpsozrb6nn/pip-21.1.1-py3-none-any.whl/pip/_vendor/distro.py", line 681, in linux_distribution
self.version(),
File "/tmp/tmpsozrb6nn/pip-21.1.1-py3-none-any.whl/pip/_vendor/distro.py", line 741, in version
self.lsb_release_attr('release'),
File "/tmp/tmpsozrb6nn/pip-21.1.1-py3-none-any.whl/pip/_vendor/distro.py", line 903, in lsb_release_attr
return self._lsb_release_info.get(attribute, '')
File "/tmp/tmpsozrb6nn/pip-21.1.1-py3-none-any.whl/pip/_vendor/distro.py", line 556, in __get__
ret = obj.__dict__[self._fname] = self._f(obj)
File "/tmp/tmpsozrb6nn/pip-21.1.1-py3-none-any.whl/pip/_vendor/distro.py", line 1014, in _lsb_release_info
stdout = subprocess.check_output(cmd, stderr=devnull)
File "/root/Python-3.9.5/Lib/subprocess.py", line 424, in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/root/Python-3.9.5/Lib/subprocess.py", line 528, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '('lsb_release', '-a')' returned non-zero exit status 1.
Traceback (most recent call last):
File "/root/Python-3.9.5/Lib/runpy.py", line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/root/Python-3.9.5/Lib/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/root/Python-3.9.5/Lib/ensurepip/__main__.py", line 5, in <module>
sys.exit(ensurepip._main())
File "/root/Python-3.9.5/Lib/ensurepip/__init__.py", line 210, in _main
return _bootstrap(
File "/root/Python-3.9.5/Lib/ensurepip/__init__.py", line 129, in _bootstrap
return _run_pip(args + [p[0] for p in _PROJECTS], additional_paths)
File "/root/Python-3.9.5/Lib/ensurepip/__init__.py", line 38, in _run_pip
return subprocess.run([sys.executable, "-c", code], check=True).returncode
File "/root/Python-3.9.5/Lib/subprocess.py", line 528, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['/root/Python-3.9.5/python', '-c', '\nimport runpy\nimport sys\nsys.path = [\'/tmp/tmpsozrb6nn/setuptools-56.0.0-py3-none-any.whl\', \'/tmp/tmpsozrb6nn/pip-21.1.1-py3-none-any.whl\'] + sys.path\nsys.argv[1:] = [\'install\', \'--no-cache-dir\', \'--no-index\', \'--find-links\', \'/tmp/tmpsozrb6nn\', \'--root\', \'/\', \'--upgrade\', \'setuptools\', \'pip\']\nrunpy.run_module("pip", run_name="__main__", alter_sys=True)\n']' returned non-zero exit status 2.
make: *** [Makefile:1265: install] Fehler 1
root@THB-PI3B1:~/Python-3.9.5# Python --version
-bash: Python: Kommando nicht gefunden.das ähnelt der Fehlermeldung in fhempy
ich bitte erneut um Hilfe
Ein Versuch vom Update auf Bullseye sollte das Problem lösen. Bei mir läuft es damit wieder.
danke, erst mal
ui das neue Debian 11?
ist das Update problemlos bzgl. gesamt FHEM mit Maria SQL?
da mache ich wohl vorab ein Image-backup auf SD?
G***le ist dein Freund. z.B.
https://schroederdennis.de/tutorial-howto/debian-10-buster-auf-debian-11-bullseye-linux-updaten-anleitung/
hallo Juergen,
inzwischen habe ich auf ner geclonten SSD von Buster auf BullsEye ein upgrade gemacht .(mit mirror)
nach der Neuistallation vopn FMEMPY in der Bullseye-Version laufen nun meine TUYA devisces nun einwandfrei.
Leider habe ich es noch nicht geschafft, die MariaDb mit 15 Mio Einträgen umzuziehen.
Ich möchte deshalb die BUster-SSD bis auf weiterers weiterlaufen lassen und nach Lösch- und Verdichtungsmöglichkeiten in der SQL-DB zu suchen, um diese dann in die neue BULLSEYE Installation übertragen.
In der Zwischen zeit versuche ich die MYSQL unter BULLSEY zum fliegen zu bringen. Bei identischer DB-Struktur müsste ich ja dann meine Vergangenheitsdaten aus der BUSTER-Installation übertragen können??
Gibt es wirklich keine Möglichkeit, das Pythonmodul unter Buster wieder lauffähig zu machen ?
Ich hoffe auf eure kundige Hilfe.
beste Grüße
Thomas
Hallo zusammen,
bei mir hat das Update auf Bullseye das Problem behoben.
Vielen Dank.
Zitat von: scank am 10 Januar 2022, 15:54:53
Hallo zusammen,
bei mir hat das Update auf Bullseye das Problem behoben.
Vielen Dank.
bei mir auch; ich musste noch die Installation fhempy für Bullseye nachholen.
Danke Jürgen für die Hilfe
im Oktober 21 sind wir auf die Problematik gestoßen, dass zwar Power etc. bei GOSUND Steckdosen zwar Power etc. als reading zur Verfügung stehen ;
nicht jedoch die Verbrauchswerte.
In der TuyaCloud und der SmartLife App sind sie ja vorhanden.
Die war eigentlich der Hauptzweck.
Hat sich da TUYA-seitig was getan ?
Freue mich auf gute Nachrichten.
Herzliche Grüße
Thomas
Hallo zusammen,
kann man sich eigentlich gefahrlos bei tuya als developer anmelden oder schicken die einem irgendwann eine Rechnung?
Irgendwie werde ich aus der Seite nicht ganz schlau.
Danke und gruß,
Thorsten
Hallo Zusammen,
bei mir läuft Bullseye mit Python 3.9.2
Nach Anweisung von https://github.com/dominikkarall/fhempy alles installiert.
Ab hier klappt was nicht : define local_pybinding BindingsIo fhempy
BindingType fhempy
CFGFN
DEF fhempy
DeviceName ws:127.0.0.1:15733
FUUID 61e959d1-f33f-9369-e30e-162facd6d524cb10
IP 127.0.0.1
NAME local_pybinding
NEXT_OPEN 1642682960.06944
NR 2214
NTFY_ORDER 50-local_pybinding
PARTIAL
PORT 15733
STATE fhempy server offline
TYPE BindingsIo
localBinding 1
nextOpenDelay 10
READINGS:
2022-01-20 13:49:50 state fhempy server offline
Server ist offline. Warum?
Im gleichen Ornder fhempy liegt das Device fhempyserver_15733:
CFGFN
DEF 0
FD 45
FUUID 61e959d1-f33f-9369-29ab-1ffef9a6626b8c44
LAST_START 2022-01-20 13:49:53
LAST_STOP 2022-01-20 13:49:52
NAME fhempyserver_15733
NR 2215
NTFY_ORDER 50-fhempyserver_15733
PID 28448
STARTS 10
STATE ???
TYPE fhempyServer
currentlogfile ./log/fhempy-2022-01-20.log
logfile ./log/fhempy-%Y-%m-%d.log
CoProcess:
cmdFn fhempyServer_getCmd
name fhempy
state running FHEM/bindings/python/bin/fhempy
READINGS:
2022-01-20 13:49:53 fhempy running FHEM/bindings/python/bin/fhempy
Mit Verbose 5 habe ich im Logfile:
2022-01-20 13:17:46,080 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
Traceback (most recent call last):
File "/opt/fhem/FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 538, in run
asyncio.get_event_loop().run_until_complete(async_main())
File "/usr/lib/python3.9/asyncio/base_events.py", line 642, in run_until_complete
return future.result()
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 511, in async_main
await pkg_installer.check_and_install_dependencies("core")
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/pkg_installer.py", line 113, in check_and_install_dependencies
if is_installed(req) is False:
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/pkg_installer.py", line 145, in is_installed
ret = version(req.project_name) in req
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3129, in __contains__
return self.specifier.contains(item, prereleases=True)
File "/usr/lib/python3/dist-packages/pkg_resources/_vendor/packaging/specifiers.py", line 789, in contains
item = parse(item)
File "/usr/lib/python3/dist-packages/pkg_resources/_vendor/packaging/version.py", line 56, in parse
return Version(version)
File "/usr/lib/python3/dist-packages/pkg_resources/_vendor/packaging/version.py", line 275, in __init__
match = self._regex.search(version)
TypeError: expected string or bytes-like object
Sentry is attempting to send 2 pending error messages
Kann mir jemand einen Tip geben?
Hi RitterSport,
hab genau das selbe Setup und laufe mit Python 3.9.2. Das sollte also ohne Probleme gehen.
Kannst du mal auf der Console als fhem User ein "python -V" machen?
Gruß,
Stefan
Ich bekomme unter der normalen Anwender pi und bei Anmeldung als fhem:
pi@raspberrypi:~ $ su - fhem
Passwort:
pi@raspberrypi:~ $ python -V
Python 3.9.2
pi@raspberrypi:~ $
Allerdings müsste es doch gleich sein, der User fhem hat doch keine Shell oder?
Danke für die Hilfe.
LG
Joe
Hallo miteinander,
mein tuya_cloud_connector will sich einfach nicht erfolgreich verbinden. Status bleibt auf connecting
IODev local_pybinding
NAME tuya_cloud_connector
NR 403
PYTHONTYPE tuya_cloud
STATE connecting
TYPE fhempy
READINGS:
2022-01-21 16:48:20 state connecting
fhempyserver ist online
LAST_START 2022-01-21 16:48:07
LAST_STOP 2022-01-21 16:48:07
NAME fhempyserver_15733
NR 402
NTFY_ORDER 50-fhempyserver_15733
PID 29301
STARTS 2
STATE ???
TYPE fhempyServer
currentlogfile ./log/fhempy-2022-01-21.log
logfile ./log/fhempy-%Y-%m-%d.log
CoProcess:
cmdFn fhempyServer_getCmd
name fhempy
state running FHEM/bindings/python/bin/fhempy
local_pybinding is open
BindingType fhempy
DEF fhempy
DeviceName ws:127.0.0.1:15733
FD 137
FUUID 61eaa12b-f33f-b08c-de6c-2fd790f1af023e81
IP 127.0.0.1
NAME local_pybinding
NR 401
NTFY_ORDER 50-local_pybinding
PARTIAL
PORT 15733
STATE opened
TYPE BindingsIo
WEBSOCKET 1
localBinding 1
nextOpenDelay 10
READINGS:
2022-01-21 16:48:19 state opened
2022-01-21 16:48:19 version 0.1.197
2022-01-21 16:48:09,660 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2022-01-21 16:48:09,670 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2022-01-21 16:48:09,709 - INFO - websockets.server: server listening on 0.0.0.0:15733
2022-01-21 16:48:19,881 - INFO - websockets.server: connection open
2022-01-21 16:48:19,883 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
Mir gehen langsam die Ideen aus, kann wer bitte helfen?
Hab das ganze mal auf einem Raspi 2B mit Bullseye neu aufgesetzt.
Gleiches Ergebniss. fhempyserver ist offline
Im Device local_pybinding steht unter Def: fhempy
Ist das richtig?
Wenn ich dort
127.0.0.1:15733
oder
Python
hinterlege, startet ein update und er steht kurzfristig auf opened
hallo.
selbiges bei mir. beide stateicons grün, beim server steht unter state??? und fhembindingpy fhempy server offline.
passt das wirklich? oder muss die tuyacloud verbunden sein? das gehe ich erst heute an
[edit]
Hallo. Habe gerade mal local_binding + fhempyserver_15733 deleted, localbinding neu angelegt und schwupp jetzt klappts.
[/edit]
jetzt zickt die tuya_cloud "failed to login: {'code': 1114, 'msg': "your ip(xx.xx.xx.66) don't have access to this API", 'success': False, 't': 1642837159334}
zumindest teilerfolg.
[edit] jetzt steht ewig "connecting"
[/edit]
und jetzt " Tuya project too old, create new one"
habe aber schon neues angelegt. denke es ist jetzt kostenpflöichtig. https://developer.tuya.com/en/docs/iot/membership-service?id=K9m8k45jwvg9j
soooo, jetzt klappt zumindest verbindung zum tuya_server.
Nach längeren suchen in den einstellungen habe ich neues projekt angelegt, aber (!) , man muss CentralEurope Server auswählen, siehe link (https://developer.tuya.com/en/docs/iot/oem-app-data-center-distributed?id=Kafi0ku9l07qb#title-7-Countries%20or%20regions%20supporting%20only%20certain%20data%20centers). erst dann sieht man seine Devices gelistet.
Auch alle statusänderungen, sogar die werte. siehe anhang.
Aber wie bekomme ich die jetzt in fhem gelistet? connection steht.
[edit] DNS umgestellt, PiHole störte rein
[/edit]
Kaffeespende unterwegs, geiles Modul!! Danke
So, auch hier ging es teilweise.
Beides auch nochmal gelöscht, dennoch stand der fhempy server laufend auf offline.
Trotzdem habe ich den Tuya Connector angelegt, und siehe da, es trudelten fast alle Tuya Devices ein.
Toll.
Wollte das ganze dann vom Hauptserver per Fhem2Fhem protkollieren lassen, und bei Anlegen des Telnetports 7072 sind alle Tuya Devices auf offline gegangen.,
LSC tuya kompatibel. Angebote (https://www.action.com/de-de/p/lsc-smart-connect-intelligenter-stecker/)
Hi,
wer Probleme mit dem Server hat könnt ihr mal schauen ob er eventuell schon läuft?
Ich habe dieses Problem das mein FHEM bei einem stop bzw restart den Server Prozess nicht beendet.
Ich weiß nicht warum das so ist und konnte es auch noch nicht lösen.
Das Verhalten ist dann wie beschrieben.
FHEM startet aber es funktioniert nicht und der Server ist rot.
Beende ich per Kommandozeile den noch laufenden fhempy Server Prozess und starte ihn im FHEM neu geht alles.
Herausfinden ob ihr das Problem habt:
FHEM stoppen
ps -ef | grep fhempy
Seht ihr solch eine Zeile läuft der Server noch und wird beim neuen Starten von FHEM zu Problemen führen:
fhem 3255 1239 0 Jan23 ? 00:06:58 python3 FHEM/bindings/python/bin/fhempy --local
Beenden in dem ihr einen kill auf die PUID ausführt.
Bei euch ist die PID anders!
Also in meinem Fall:
kill 3255
Danach FHEM starten.
Das funktioniert auch wenn FHEM schon läuft.
Alten Serverprozess killen und neu starten in FHEM.
Gruß,
Stefan
@stefanru:
Danke für den Hinweis.
Ich habe meinen alten Raspi soweit dazu bekommen zu laufen ,werde aber deine Hinweise austesten.
seit gestern sind auf 2 fhem instanzen beide "fhempy server offline", trotz
"fhempy
running FHEM/bindings/python/bin/fhempy"
[edit] tuya_cloud_connector neu angelegt, jetzt passts wieder. ärgerlich. bug?
Hallo.
seit kurzem werden keine devices mehr synchronisiert, trotz connection zum server.
gestern 2 geräte angelernt, am tuya server auch sichtbar, nur in fhem leider nicht. hat es was mit neuerster version 0.1.209 zu tun?
Hi,
Tuya Cloud macht scheinbar wieder Probleme. Ich bekomme aktuell nur in sehr unregelmäßigen Abständen Reading Updates von Tuya. Das ist das gleiche Problem wie vor einigen Wochen.
Neue Devices habe ich bislang immer bekommen. Werden diese auch nicht angelegt wenn du fhempy neu startest?
Hi,
kann ich auch bestätigen Updates sind sehr unregelmäßig.
Gruß,
Stefan
Zitat von: dominik am 04 Februar 2022, 20:09:51
Hi,
Tuya Cloud macht scheinbar wieder Probleme. Ich bekomme aktuell nur in sehr unregelmäßigen Abständen Reading Updates von Tuya. Das ist das gleiche Problem wie vor einigen Wochen.
Neue Devices habe ich bislang immer bekommen. Werden diese auch nicht angelegt wenn du fhempy neu startest?
nein, habe es manuel angelegt und sofort die readings erhalten. steuern klappt auch sekundenschnell.
Hi,
habe noch eine Frage, kennt jemand diese Phänomen?
Wenn ich den Raspberry oder FHEM neu starte bekomme ich diese Meldung im Globals:
Messages collected while initializing FHEM:configfile: fhempy_log already defined, delete it first
Ich habe geschaut fhempy_log ist genau einmal in deer fhem.cfg und nicht in fhem.save.
Irgendeine Idee wie ich das weg bekomme?
Gruß und Danke,
Stefan
Ja, ist noch ein Fehler in fhempy. Behebe ich beim nächsten Update.
Ah super, danke!
Hi Dominik,
leider bekomme ich nach einer komplette Neuinstallation Fhempy nicht mehr ans laufen.
fhempyserver_15733 scheint zu laufen
Internals:
DEF 0
FD 55
FUUID 61d82555-f33f-e50d-543e-38cdfc6302672afc
LAST_START 2022-02-12 17:56:53
LAST_STOP 2022-02-12 17:56:33
NAME fhempyserver_15733
NR 30
NTFY_ORDER 50-fhempyserver_15733
PID 692
STARTS 2
STATE ???
TYPE fhempyServer
currentlogfile ./log/fhempy-2022-02-12.log
logfile ./log/fhempy-%Y-%m-%d.log
CoProcess:
cmdFn fhempyServer_getCmd
name fhempy
state running FHEM/bindings/python/bin/fhempy
READINGS:
2022-02-12 17:56:53 fhempy running FHEM/bindings/python/bin/fhempy
Attributes:
devStateIcon { my $status_img = "10px-kreis-gruen";; my $status_txt = "running";; if (substr(ReadingsVal($name, "fhempy", "running"),0,7) ne "running") { $status_img = "10px-kreis-rot";; $status_txt = "stopped";; } "<div><a>".FW_makeImage($status_img, $status_txt)."</a><a href=\"/fhem?cmd.dummy=set $name restart&XHR=1\" title=\"Restart\">".FW_makeImage("audio_repeat")."</a></div>" }
group fhempy
icon python
logfile ./log/fhempy-%Y-%m-%d.log
nrarchive 10
room Gateways
verbose 0
local_pybinding scheint auch zu laufen :
Internals:
BindingType fhempy
CFGFN
DEF fhempy
DeviceName ws:127.0.0.1:15733
FD 69
FUUID 6207f63c-f33f-caec-45de-1e6f79ea23935707
IP 127.0.0.1
NAME fhempy_local
NR 1578
NTFY_ORDER 50-fhempy_local
PARTIAL
PORT 15733
STATE opened
TYPE BindingsIo
WEBSOCKET 1
localBinding 1
nextOpenDelay 10
READINGS:
2022-02-12 18:02:39 state opened
2022-02-12 18:02:39 version 0.1.228
args:
fhempy_local
BindingsIo
fhempy
argsh:
hmccu:
Attributes:
devStateIcon { my $status_img = "10px-kreis-gruen";; my $status_txt = "connected";; if (ReadingsVal($name, "state", "disconnected") eq "disconnected") { $status_img = "10px-kreis-rot";; $status_txt = "disconnected";; } my $ver = ReadingsVal($name, "version", "-");; "<div><a>".FW_makeImage($status_img, $status_txt)."</a><a> ".$ver." </a><a href=\"/fhem?cmd.dummy=set $name update&XHR=1\" title=\"Start update\">".FW_makeImage("refresh")."</a></div>" }
group fhempy
icon file_json-ld2
room New_Defined
aber den Tuya cloud connector bekomme ich nicht hin :
Internals:
CFGFN
DEF tuya_cloud setup xxx
FHEMPYTYPE tuya_cloud
FUUID 6207f69e-f33f-caec-0534-05898754dd0729bb
IODev fhempy_local
NAME tuya_cloud_connector
NR 1856
PYTHONTYPE tuya_cloud
STATE Failed to load module tuya_cloud: Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/fhem_pythonbinding.py", line 269, in _onMessage
functools.partial(importlib.import_module, pymodule)
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/utils.py", line 34, in run_blocking
return await asyncio.get_event_loop().run_in_executor(pool, function)
File "/usr/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
File "<frozen importlib._bootstrap>", line 983, in _find_and_load
File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 728, in exec_module
File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud.py", line 5, in <module>
from fhempy.lib.tuya_cloud.tuya_cloud_device import tuya_cloud_device
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 5, in <module>
from tuya_iot.device import TuyaDevice
File "/opt/fhem/.local/lib/python3.7/site-packages/tuya_iot/__init__.py", line 2, in <module>
from .device import TuyaDevice, TuyaDeviceListener, TuyaDeviceManager
File "/opt/fhem/.local/lib/python3.7/site-packages/tuya_iot/device.py", line 7, in <module>
from typing import Any, Literal, Optional
ImportError: cannot import name 'Literal' from 'typing' (/usr/lib/python3.7/typing.py)
TYPE PythonModule
READINGS:
2022-02-12 18:04:14 state Failed to load module tuya_cloud: Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/fhem_pythonbinding.py", line 269, in _onMessage
functools.partial(importlib.import_module, pymodule)
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/utils.py", line 34, in run_blocking
return await asyncio.get_event_loop().run_in_executor(pool, function)
File "/usr/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
File "<frozen importlib._bootstrap>", line 983, in _find_and_load
File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 728, in exec_module
File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud.py", line 5, in <module>
from fhempy.lib.tuya_cloud.tuya_cloud_device import tuya_cloud_device
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 5, in <module>
from tuya_iot.device import TuyaDevice
File "/opt/fhem/.local/lib/python3.7/site-packages/tuya_iot/__init__.py", line 2, in <module>
from .device import TuyaDevice, TuyaDeviceListener, TuyaDeviceManager
File "/opt/fhem/.local/lib/python3.7/site-packages/tuya_iot/device.py", line 7, in <module>
from typing import Any, Literal, Optional
ImportError: cannot import name 'Literal' from 'typing' (/usr/lib/python3.7/typing.py)
args:
tuya_cloud_connector
PythonModule
tuya_cloud
setup
xxx
xxx
xxx
argsh:
hmccu:
Attributes:
room New_Defined
kannst du mir da ggf. helfen ,ich weiss nicht wirklich weiter.
gruss Thomas
Bitte auf bullseye aktualisieren damit du Python 3.9 als Standard bekommst.
Die tuya Library unterstützt aktuell nur Python 3.8 oder höher. Mein Patch für 3.7 Support wurde mittlerweile eingepflegt, nur fehlt noch das Release von Tuya und daher geht im Moment noch kein 3.7.
Zitat von: dominik am 12 Februar 2022, 20:09:26
Bitte auf bullseye aktualisieren damit du Python 3.9 als Standard bekommst.
Die tuya Library unterstützt aktuell nur Python 3.8 oder höher. Mein Patch für 3.7 Support wurde mittlerweile eingepflegt, nur fehlt noch das Release von Tuya und daher geht im Moment noch kein 3.7.
dank dir für die schnelle Info ( habe eben gesehen , das das lesen von 2 seiten rückwärts bereits geholfen hätte - war gestresst davon und habe das wieder besseren Wissens nicht getan . Sorry dafür.)
gruss Thomas
hallo.
heute mail erhalten das mein zuganf an 22.2. abläuft. verlängerung kostet.
klapot das modul dann weiterhin?
Echt? Nachdem man mehrere Services dort buchen kann, um welchen Service geht es? Kannst du das Mail ohne Namen Posten?
Dear Tuya IoT Platform Account Manager,
The service Basic Resource Pack you subscribed to will expire on 2022-02-22,If you need to continue to use,please renew this service.
How to renew your contract:
Please check the services you subscribe to and select the corresponding expired / expiring services to renew:
www.tuya.com/vas/user/service
You have received this email because you are the account owner of the Tuya IoT platform and you have the right to know the changes of service information on the platform
Läuft es auch ohne dem Package?
Wenn nicht, sehe ich richtig, dass es 0,2USD pro Monat sind? Das wäre Mal nicht so schlimm. Mach aber bitte auch ein Ticket bei Tuya auf, dass du gerne weiterhin Trial möchtest. Es gab Mal eine Antwort von Tuya, dass Trial jährlich for free verlängert werden kann.
Sollte das nicht gehen, müssen wir wohl tuya_local weiter vorantreiben.
hallo. jährlich? habe es nicht mal 1 monat......
Hmm...ich habe es seit Juni oder Juli 2021 und da läuft es jährlich. Ich schau später Mal welche Services bei mir drin stehen.
Ist dein IoT Core Service auch ausgelaufen? Versuch dieses mal zu verlängern...
ZitatBasic resources include the quota of API calls and message services. When you call most cloud services, the usage will be deducted from the basic resource pack. Currently, this resource pack is not sold separately. You can subscribe to the device connection service to get the free basic resource pack. ViewIoT Core Service
Laut der Meldung, sollte es auch einen "free basic resource pack" geben.
Hallo Dominik,
bei einem Stecker bekomme ich die folgende im Logfile:
2022.02.19 22:35:48.606 1: readingsUpdate(Stecker_SilverCrest_Hub_Ueberwachung_bf7a36070c5531b25aubiy,state,on) missed to call readingsBeginUpdate first.
2022.02.19 22:35:48.606 1: stacktrace:
2022.02.19 22:35:48.606 1: main::readingsBulkUpdate called by (eval 63483) (1)
2022.02.19 22:35:48.606 1: (eval) called by ./FHEM/10_BindingsIo.pm (463)
2022.02.19 22:35:48.607 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (574)
2022.02.19 22:35:48.607 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (336)
2022.02.19 22:35:48.607 1: main::BindingsIo_Write called by fhem.pl (1060)
2022.02.19 22:35:48.607 1: main::IOWrite called by ./FHEM/10_PythonModule.pm (96)
2022.02.19 22:35:48.607 1: main::PythonModule_Set called by fhem.pl (3929)
2022.02.19 22:35:48.607 1: main::CallFn called by fhem.pl (1944)
2022.02.19 22:35:48.607 1: main::DoSet called by fhem.pl (1986)
2022.02.19 22:35:48.608 1: main::CommandSet called by fhem.pl (2865)
2022.02.19 22:35:48.608 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3283)
2022.02.19 22:35:48.608 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3176)
2022.02.19 22:35:48.608 1: main::FW_Notify called by fhem.pl (3929)
2022.02.19 22:35:48.608 1: main::CallFn called by fhem.pl (3842)
2022.02.19 22:35:48.608 1: main::DoTrigger called by fhem.pl (4944)
2022.02.19 22:35:48.608 1: main::readingsEndUpdate called by (eval 63481) (1)
2022.02.19 22:35:48.608 1: (eval) called by ./FHEM/10_BindingsIo.pm (463)
2022.02.19 22:35:48.609 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (574)
2022.02.19 22:35:48.609 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (222)
2022.02.19 22:35:48.609 1: main::BindingsIo_Read called by fhem.pl (3929)
2022.02.19 22:35:48.609 1: main::CallFn called by fhem.pl (780)
2022.02.19 22:35:48.633 1: readingsUpdate(Stecker_SilverCrest_Hub_Ueberwachung_bf7a36070c5531b25aubiy,countdown_1,0.0) missed to call readingsBeginUpdate first.
2022.02.19 22:35:48.633 1: stacktrace:
2022.02.19 22:35:48.633 1: main::readingsBulkUpdate called by (eval 63485) (1)
2022.02.19 22:35:48.634 1: (eval) called by ./FHEM/10_BindingsIo.pm (463)
2022.02.19 22:35:48.634 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (574)
2022.02.19 22:35:48.634 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (222)
2022.02.19 22:35:48.638 1: main::BindingsIo_Read called by fhem.pl (3929)
2022.02.19 22:35:48.638 1: main::CallFn called by fhem.pl (780)
2022.02.19 22:35:48.661 1: readingsUpdate(Stecker_SilverCrest_Hub_Ueberwachung_bf7a36070c5531b25aubiy,add_ele,0.001) missed to call readingsBeginUpdate first.
2022.02.19 22:35:48.661 1: stacktrace:
2022.02.19 22:35:48.661 1: main::readingsBulkUpdate called by (eval 63488) (1)
2022.02.19 22:35:48.661 1: (eval) called by ./FHEM/10_BindingsIo.pm (463)
2022.02.19 22:35:48.661 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (574)
2022.02.19 22:35:48.661 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (222)
2022.02.19 22:35:48.661 1: main::BindingsIo_Read called by fhem.pl (3929)
2022.02.19 22:35:48.662 1: main::CallFn called by fhem.pl (780)
2022.02.19 22:35:48.679 1: readingsUpdate(Stecker_SilverCrest_Hub_Ueberwachung_bf7a36070c5531b25aubiy,cur_current,0.0) missed to call readingsBeginUpdate first.
2022.02.19 22:35:48.679 1: stacktrace:
2022.02.19 22:35:48.679 1: main::readingsBulkUpdate called by (eval 63491) (1)
2022.02.19 22:35:48.679 1: (eval) called by ./FHEM/10_BindingsIo.pm (463)
2022.02.19 22:35:48.680 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (574)
2022.02.19 22:35:48.680 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (222)
2022.02.19 22:35:48.680 1: main::BindingsIo_Read called by fhem.pl (3929)
2022.02.19 22:35:48.680 1: main::CallFn called by fhem.pl (780)
2022.02.19 22:35:48.701 1: readingsUpdate(Stecker_SilverCrest_Hub_Ueberwachung_bf7a36070c5531b25aubiy,cur_power,0.0) missed to call readingsBeginUpdate first.
2022.02.19 22:35:48.701 1: stacktrace:
2022.02.19 22:35:48.701 1: main::readingsBulkUpdate called by (eval 63494) (1)
2022.02.19 22:35:48.701 1: (eval) called by ./FHEM/10_BindingsIo.pm (463)
2022.02.19 22:35:48.701 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (574)
2022.02.19 22:35:48.701 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (222)
2022.02.19 22:35:48.701 1: main::BindingsIo_Read called by fhem.pl (3929)
2022.02.19 22:35:48.701 1: main::CallFn called by fhem.pl (780)
2022.02.19 22:35:48.721 1: readingsUpdate(Stecker_SilverCrest_Hub_Ueberwachung_bf7a36070c5531b25aubiy,cur_voltage,232.0) missed to call readingsBeginUpdate first.
2022.02.19 22:35:48.721 1: stacktrace:
2022.02.19 22:35:48.721 1: main::readingsBulkUpdate called by (eval 63497) (1)
2022.02.19 22:35:48.721 1: (eval) called by ./FHEM/10_BindingsIo.pm (463)
2022.02.19 22:35:48.721 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (574)
2022.02.19 22:35:48.721 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (222)
2022.02.19 22:35:48.722 1: main::BindingsIo_Read called by fhem.pl (3929)
2022.02.19 22:35:48.722 1: main::CallFn called by fhem.pl (780)
2022.02.19 22:35:48.742 1: readingsUpdate(Stecker_SilverCrest_Hub_Ueberwachung_bf7a36070c5531b25aubiy,relay_status,last) missed to call readingsBeginUpdate first.
2022.02.19 22:35:48.743 1: stacktrace:
2022.02.19 22:35:48.743 1: main::readingsBulkUpdate called by (eval 63500) (1)
2022.02.19 22:35:48.743 1: (eval) called by ./FHEM/10_BindingsIo.pm (463)
2022.02.19 22:35:48.743 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (574)
2022.02.19 22:35:48.743 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (222)
2022.02.19 22:35:48.743 1: main::BindingsIo_Read called by fhem.pl (3929)
2022.02.19 22:35:48.743 1: main::CallFn called by fhem.pl (780)
2022.02.19 22:35:48.861 1: readingsUpdate(Stecker_SilverCrest_Hub_Ueberwachung_bf7a36070c5531b25aubiy,light_mode,relay) missed to call readingsBeginUpdate first.
2022.02.19 22:35:48.861 1: stacktrace:
2022.02.19 22:35:48.862 1: main::readingsBulkUpdate called by (eval 63503) (1)
2022.02.19 22:35:48.862 1: (eval) called by ./FHEM/10_BindingsIo.pm (463)
2022.02.19 22:35:48.862 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (574)
2022.02.19 22:35:48.862 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (336)
2022.02.19 22:35:48.862 1: main::BindingsIo_Write called by fhem.pl (1060)
2022.02.19 22:35:48.862 1: main::IOWrite called by ./FHEM/10_PythonModule.pm (96)
2022.02.19 22:35:48.862 1: main::PythonModule_Set called by fhem.pl (3929)
2022.02.19 22:35:48.862 1: main::CallFn called by fhem.pl (1944)
2022.02.19 22:35:48.862 1: main::DoSet called by fhem.pl (1986)
2022.02.19 22:35:48.862 1: main::CommandSet called by fhem.pl (2865)
2022.02.19 22:35:48.862 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3283)
2022.02.19 22:35:48.862 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3176)
2022.02.19 22:35:48.862 1: main::FW_Notify called by fhem.pl (3929)
2022.02.19 22:35:48.862 1: main::CallFn called by fhem.pl (3842)
2022.02.19 22:35:48.863 1: main::DoTrigger called by fhem.pl (4944)
2022.02.19 22:35:48.863 1: main::readingsEndUpdate called by (eval 63501) (1)
2022.02.19 22:35:48.863 1: (eval) called by ./FHEM/10_BindingsIo.pm (463)
2022.02.19 22:35:48.863 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (574)
2022.02.19 22:35:48.863 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (222)
2022.02.19 22:35:48.863 1: main::BindingsIo_Read called by fhem.pl (3929)
2022.02.19 22:35:48.863 1: main::CallFn called by fhem.pl (780)
2022.02.19 22:35:48.894 1: readingsUpdate(Stecker_SilverCrest_Hub_Ueberwachung_bf7a36070c5531b25aubiy,child_lock,off) missed to call readingsBeginUpdate first.
2022.02.19 22:35:48.894 1: stacktrace:
2022.02.19 22:35:48.894 1: main::readingsBulkUpdate called by (eval 63505) (1)
2022.02.19 22:35:48.895 1: (eval) called by ./FHEM/10_BindingsIo.pm (463)
2022.02.19 22:35:48.895 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (574)
2022.02.19 22:35:48.895 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (222)
2022.02.19 22:35:48.895 1: main::BindingsIo_Read called by fhem.pl (3929)
2022.02.19 22:35:48.895 1: main::CallFn called by fhem.pl (780)
2022.02.19 22:35:48.978 1: readingsUpdate(Stecker_SilverCrest_Hub_Ueberwachung_bf7a36070c5531b25aubiy,cycle_time,) missed to call readingsBeginUpdate first.
2022.02.19 22:35:48.978 1: stacktrace:
2022.02.19 22:35:48.978 1: main::readingsBulkUpdate called by (eval 63508) (1)
2022.02.19 22:35:48.979 1: (eval) called by ./FHEM/10_BindingsIo.pm (463)
2022.02.19 22:35:48.979 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (574)
2022.02.19 22:35:48.979 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (336)
2022.02.19 22:35:48.979 1: main::BindingsIo_Write called by fhem.pl (1060)
2022.02.19 22:35:48.979 1: main::IOWrite called by ./FHEM/10_PythonModule.pm (96)
2022.02.19 22:35:48.979 1: main::PythonModule_Set called by fhem.pl (3929)
2022.02.19 22:35:48.979 1: main::CallFn called by fhem.pl (1944)
2022.02.19 22:35:48.979 1: main::DoSet called by fhem.pl (1986)
2022.02.19 22:35:48.979 1: main::CommandSet called by fhem.pl (2865)
2022.02.19 22:35:48.979 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3283)
2022.02.19 22:35:48.979 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3176)
2022.02.19 22:35:48.979 1: main::FW_Notify called by fhem.pl (3929)
2022.02.19 22:35:48.979 1: main::CallFn called by fhem.pl (3842)
2022.02.19 22:35:48.979 1: main::DoTrigger called by fhem.pl (4944)
2022.02.19 22:35:48.980 1: main::readingsEndUpdate called by (eval 63507) (1)
2022.02.19 22:35:48.980 1: (eval) called by ./FHEM/10_BindingsIo.pm (463)
2022.02.19 22:35:48.980 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (574)
2022.02.19 22:35:48.980 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (222)
2022.02.19 22:35:48.980 1: main::BindingsIo_Read called by fhem.pl (3929)
2022.02.19 22:35:48.980 1: main::CallFn called by fhem.pl (780)
2022.02.19 22:35:49.069 1: readingsUpdate(Stecker_SilverCrest_Hub_Ueberwachung_bf7a36070c5531b25aubiy,random_time,) missed to call readingsBeginUpdate first.
2022.02.19 22:35:49.069 1: stacktrace:
2022.02.19 22:35:49.069 1: main::readingsBulkUpdate called by (eval 63519) (1)
2022.02.19 22:35:49.069 1: (eval) called by ./FHEM/10_BindingsIo.pm (463)
2022.02.19 22:35:49.069 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (574)
2022.02.19 22:35:49.069 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (222)
2022.02.19 22:35:49.070 1: main::BindingsIo_Read called by fhem.pl (3929)
2022.02.19 22:35:49.070 1: main::CallFn called by fhem.pl (780)
2022.02.19 22:35:55.063 1: Perfmon: possible freeze starting at 22:35:51, delay is 4.063
Das List:
Internals:
.AttrList IODev:local_pybinding event-aggregator event-min-interval event-on-change-reading event-on-update-reading oldreadings stateFormat:textField-long timestamp-on-change-reading
.FhemMetaInternals 1
.eventMapCmd An:noArg Aus:noArg
DEF tuya_cloud tuya_cloud_connector bf7a36070c5531b25aubiy
DEVICEID bf7a36070c5531b25aubiy
FHEMPYTYPE tuya_cloud
FUUID 62066382-f33f-3b5c-ac35-bc3b55409c363997
FVERSION 10_PythonModule.pm:0.182830/2019-01-16
IODev local_pybinding
NAME Stecker_SilverCrest_Hub_Ueberwachung_bf7a36070c5531b25aubiy
NR 1175
PYTHONTYPE tuya_cloud
STATE An
TYPE PythonModule
.attraggr:
.attrminint:
READINGS:
2022-02-19 21:34:28 active_time 1644584256
2022-02-19 22:45:31 add_ele 0.001
2022-02-19 21:34:28 biz_type 0
2022-02-19 21:34:28 category cz
2022-02-19 22:45:30 child_lock off
2022-02-19 22:45:30 countdown_1 0.0
2022-02-19 21:34:28 create_time 1644584256
2022-02-19 22:45:30 cur_current 0.0
2022-02-19 22:45:30 cur_power 0.0
2022-02-19 22:45:30 cur_voltage 232.0
2022-02-19 22:45:30 cycle_time
2022-02-19 21:34:28 icon https://images.tuyaeu.com/smart/icon/ay15148582002916nitB/c58a91c23c2e2b5309c7c5d776871390.png
2022-02-19 21:34:28 id bf7a36070c5531b25aubiy
2022-02-19 21:34:28 ip 93.201.86.170
2022-02-19 21:34:28 lat 52.8048
2022-02-19 22:45:30 light_mode relay
2022-02-19 21:34:28 local_key 6bceb9fd35fc9dec
2022-02-19 21:34:28 lon 13.0448
2022-02-19 21:34:28 model BSD34BP
2022-02-19 21:34:28 name Stecker_SilverCrest_Hub_Ueberwachung
2022-02-19 21:34:28 online on
2022-02-19 21:34:28 owner_id 15487476
2022-02-19 21:34:28 product_id apszn7k8yhgsin28
2022-02-19 21:34:28 product_name WIFI 插座
2022-02-19 22:45:30 random_time
2022-02-19 22:45:30 relay_status last
2022-02-19 22:45:30 state on
2022-02-19 21:34:28 sub off
2022-02-19 21:34:28 time_zone +01:00
2022-02-19 21:34:28 uid eu1598817427882BAzmt
2022-02-19 21:34:28 update_time 1644585575
2022-02-19 21:34:28 uuid 11e21d2d225a8c56
args:
Stecker_SilverCrest_Hub_Ueberwachung_bf7a36070c5531b25aubiy
PythonModule
tuya_cloud
tuya_cloud_connector
bf7a36070c5531b25aubiy
argsh:
Attributes:
alias Stecker_SilverCrest_Hub_Ueberwachung
cmdIcon on:rc_GREEN off:rc_RED
devStateIcon An:black_Steckdose.on Aus:black_Steckdose.off
eventMap on:An off:Aus
group tuya_cloud
icon ge_wht_steckdose
room 00_1_Aussenbereich,00_2_Carport,Tuya
webCmd on:off
Hast du einen Rat, was ich ändern könnte?
Viele Grüße
Poste bitte noch das fhempy Log.
Guten Morgen,
2022-02-19 01:33:35,206 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Air_conditioner_33051602e09806002e71_Test'});;
2022-02-19 01:33:35,208 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Air_conditioner_33051602e09806002e71'});;
2022-02-19 01:34:04,045 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"awaitId":49952389,"result":"2022-02-19 01:34:04","error":0}
2022-02-19 01:34:04,047 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"error":0,"result":"2022-02-19 01:34:04","awaitId":77499684}
2022-02-19 02:17:31,951 - ERROR - pychromecast.socket_client: [Wohnzimmer(192.168.178.52):8009] Failed to connect to service ServiceInfo(type='host', data=('192.168.178.52', 8009)), retrying in 5.0s
2022-02-19 02:47:33,391 - ERROR - pychromecast.socket_client: [Chromecast(192.168.178.68):8009] Failed to connect to service ServiceInfo(type='host', data=('192.168.178.68', 8009)), retrying in 5.0s
2022-02-19 02:54:11,353 - ERROR - pychromecast.socket_client: [Dachboden(192.168.178.74):8009] Failed to connect to service ServiceInfo(type='host', data=('192.168.178.74', 8009)), retrying in 5.0s
2022-02-19 03:23:38,388 - ERROR - pychromecast.socket_client: [OG.Badezimmer(192.168.178.48):8009] Failed to connect to service ServiceInfo(type='host', data=('192.168.178.48', 8009)), retrying in 5.0s
2022-02-19 04:11:37,007 - ERROR - pychromecast.socket_client: [Schlafzimmer(192.168.178.22):8009] Failed to connect to service ServiceInfo(type='host', data=('192.168.178.22', 8009)), retrying in 5.0s
2022-02-19 04:12:02,912 - ERROR - pychromecast.socket_client: [Google-Nest(192.168.178.28):8009] Error reading from socket.
2022-02-19 06:33:32,655 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Air_conditioner_33051602e09806002e71_Test'});;
2022-02-19 06:33:32,656 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Air_conditioner_33051602e09806002e71'});;
2022-02-19 06:34:05,740 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"error":0,"awaitId":40791225,"result":"2022-02-19 06:34:05"}
2022-02-19 06:34:05,742 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"awaitId":86641201,"result":"2022-02-19 06:34:05","error":0}
2022-02-19 06:59:11,984 - ERROR - pychromecast.socket_client: [Google-Nest(192.168.178.28):8009] Failed to connect to service ServiceInfo(type='host', data=('192.168.178.28', 8009)), retrying in 5.0s
2022-02-19 06:59:12,229 - ERROR - pychromecast.socket_client: [Chromecast(192.168.178.68):8009] Failed to connect to service ServiceInfo(type='host', data=('192.168.178.68', 8009)), retrying in 5.0s
2022-02-19 06:59:12,783 - ERROR - pychromecast.socket_client: [OG.Badezimmer(192.168.178.48):8009] Failed to connect to service ServiceInfo(type='host', data=('192.168.178.48', 8009)), retrying in 5.0s
2022-02-19 06:59:15,311 - ERROR - pychromecast.socket_client: [Schlafzimmer(192.168.178.22):8009] Failed to connect to service ServiceInfo(type='mdns', data='Google-Nest-Mini-a1ec327743b470c827cfa149576f807e._googlecast._tcp.local.'), retrying in 5.0s
2022-02-19 06:59:16,018 - ERROR - pychromecast.socket_client: [Dachboden(192.168.178.74):8009] Failed to connect to service ServiceInfo(type='host', data=('192.168.178.74', 8009)), retrying in 5.0s
2022-02-19 06:59:16,143 - ERROR - pychromecast.socket_client: [Wohnzimmer(192.168.178.52):8009] Failed to connect to service ServiceInfo(type='mdns', data='Google-Home-cb6ffc04c65ce8afd0127c0acb87a510._googlecast._tcp.local.'), retrying in 5.0s
2022-02-19 07:33:32,711 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Air_conditioner_33051602e09806002e71_Test'});;
2022-02-19 07:33:32,712 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Air_conditioner_33051602e09806002e71'});;
2022-02-19 07:33:53,638 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"error":0,"result":"2022-02-19 07:33:53","awaitId":51271062}
2022-02-19 07:33:53,640 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"error":0,"result":"2022-02-19 07:33:53","awaitId":46587985}
2022-02-19 08:01:27,988 - INFO - fhempy.lib.pkg_installer: Attempting install of fhempy
2022-02-19 08:01:36,572 - INFO - fhempy.lib.pkg_installer: Successfully installed fhempy update!
2022-02-19 08:01:37,159 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2022-02-19 08:01:37,169 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2022-02-19 08:01:37,203 - INFO - websockets.server: server listening on 0.0.0.0:15733
2022-02-19 08:01:46,865 - INFO - websockets.server: connection open
2022-02-19 08:01:46,866 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2022-02-19 08:01:47,450 - INFO - fhempy.lib.pkg_installer: Attempting install of spotipy==2.19.0
2022-02-19 08:01:51,887 - INFO - fhempy.lib.pkg_installer: Successfully installed spotipy==2.19.0 update!
2022-02-19 08:01:56,166 - ERROR - Robot_bf623c4459370bd192tywm: 'result'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 30, in _init_device
await self._setup_device()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 58, in _setup_device
self._t_info = await utils.run_blocking(
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/utils.py", line 34, in run_blocking
return await asyncio.get_event_loop().run_in_executor(pool, function)
File "/usr/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/device.py", line 332, in get_device_info
return self.device_manage.get_device_info(device_id)
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/device.py", line 580, in get_device_info
response["result"].pop("status")
KeyError: 'result'
2022-02-19 08:02:00,889 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 08:02:00,891 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 08:02:00,901 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 08:02:01,969 - ERROR - Wohnzimmerkamera_bf905cb6a14a43dbf9hhfu: unsupported operand type(s) for /: 'str' and 'int'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 280, in update_readings_arr
self._convert_value2fhem(status["code"], status["value"]),
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 234, in _convert_value2fhem
return value / (10 ** int(values["scale"]))
TypeError: unsupported operand type(s) for /: 'str' and 'int'
2022-02-19 08:02:02,223 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 08:05:45,986 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2022-02-19 08:05:45,997 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2022-02-19 08:05:46,036 - INFO - websockets.server: server listening on 0.0.0.0:15733
2022-02-19 08:06:18,203 - INFO - websockets.server: connection open
2022-02-19 08:06:18,204 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2022-02-19 08:06:20,801 - INFO - fhempy.lib.pkg_installer: Attempting install of spotipy==2.18.0
2022-02-19 08:06:25,487 - INFO - fhempy.lib.pkg_installer: Successfully installed spotipy==2.18.0 update!
2022-02-19 08:06:29,967 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 08:06:29,967 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 08:06:30,275 - ERROR - Robot_bf623c4459370bd192tywm: 'result'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 30, in _init_device
await self._setup_device()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 58, in _setup_device
self._t_info = await utils.run_blocking(
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/utils.py", line 34, in run_blocking
return await asyncio.get_event_loop().run_in_executor(pool, function)
File "/usr/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/device.py", line 332, in get_device_info
return self.device_manage.get_device_info(device_id)
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/device.py", line 580, in get_device_info
response["result"].pop("status")
KeyError: 'result'
2022-02-19 08:06:30,318 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 08:06:38,297 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 08:06:38,302 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 08:06:38,307 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 08:06:38,312 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 08:06:38,313 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 08:06:41,099 - ERROR - Wohnzimmerkamera_bf905cb6a14a43dbf9hhfu: unsupported operand type(s) for /: 'str' and 'int'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 280, in update_readings_arr
self._convert_value2fhem(status["code"], status["value"]),
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 234, in _convert_value2fhem
return value / (10 ** int(values["scale"]))
TypeError: unsupported operand type(s) for /: 'str' and 'int'
2022-02-19 08:07:05,187 - ERROR - pychromecast.socket_client: [Google-Nest(192.168.178.28):8009] Failed to connect to service ServiceInfo(type='mdns', data='google-nest-hub-5c8f0c586b0fcf88151443201b9df76a._googlecast._tcp.local.'), retrying in 5.0s
2022-02-19 10:06:28,817 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Air_conditioner_33051602e09806002e71_Test'});;
2022-02-19 10:06:28,818 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Air_conditioner_33051602e09806002e71'});;
2022-02-19 10:06:34,535 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"error":0,"result":"2022-02-19 10:06:34","awaitId":69037205}
2022-02-19 10:06:34,537 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"awaitId":46937867,"result":"2022-02-19 10:06:34","error":0}
2022-02-19 11:07:34,667 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Air_conditioner_33051602e09806002e71_Test'},'temp_set','26.0');;
2022-02-19 11:07:34,669 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Air_conditioner_33051602e09806002e71'},'temp_set','26.0');;
2022-02-19 12:07:27,344 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Air_conditioner_33051602e09806002e71_Test'},'temp_set','26.0');;
2022-02-19 12:07:27,347 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Air_conditioner_33051602e09806002e71'},'temp_set','26.0');;
2022-02-19 12:07:27,399 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Stecker_Homatic_Hub_Ueberwachung_bf35cb0f514fd1e576x3hp'});;
2022-02-19 12:07:45,859 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"result":"temp_set: 26.0","awaitId":50128697,"error":0}
2022-02-19 12:07:45,861 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"error":0,"result":"temp_set: 26.0","awaitId":55137792}
2022-02-19 12:07:45,863 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"result":"2022-02-19 12:07:45","awaitId":62534566,"error":0}
2022-02-19 13:06:09,444 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Stecker_Homatic_Hub_Ueberwachung_bf35cb0f514fd1e576x3hp'});;
2022-02-19 13:06:25,883 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Air_conditioner_33051602e09806002e71_Test'});;
2022-02-19 13:06:25,884 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Air_conditioner_33051602e09806002e71'});;
2022-02-19 13:06:48,593 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"awaitId":13118690,"result":"2022-02-19 13:06:48","error":0}
2022-02-19 13:06:48,595 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"result":"2022-02-19 13:06:48","awaitId":57077948,"error":0}
2022-02-19 13:06:48,597 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"error":0,"result":"2022-02-19 13:06:48","awaitId":95924423}
2022-02-19 13:07:53,730 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Stecker_SilverCrest_Hub_Ueberwachung_bf7a36070c5531b25aubiy'});;
2022-02-19 13:07:53,738 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsEndUpdate($defs{'Air_conditioner_33051602e09806002e71'},1);;
2022-02-19 13:07:53,740 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsEndUpdate($defs{'Air_conditioner_33051602e09806002e71_Test'},1);;
2022-02-19 13:08:41,639 - ERROR - pychromecast.socket_client: [Schlafzimmer(192.168.178.22):8009] Failed to connect to service ServiceInfo(type='host', data=('192.168.178.22', 8009)), retrying in 5.0s
2022-02-19 14:06:11,194 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdateIfChanged($defs{'Castdevice_Schlafzimmer'},'connection','connecting');;
2022-02-19 14:06:31,687 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"result":"connection: connecting","awaitId":48045716,"error":0}
2022-02-19 14:08:30,588 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Stecker_SilverCrest_Hub_Ueberwachung_bf7a36070c5531b25aubiy'},'cur_voltage','233.8');;
2022-02-19 14:08:30,593 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Air_conditioner_33051602e09806002e71'},'temp_current','23.0');;
2022-02-19 14:08:30,597 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Air_conditioner_33051602e09806002e71_Test'},'temp_current','23.0');;
2022-02-19 14:08:30,695 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Toilettenvorhang_84076817a4e57c109f68'});;
2022-02-19 16:06:08,858 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Stecker_Homatic_Hub_Ueberwachung_bf35cb0f514fd1e576x3hp'});;
2022-02-19 16:06:22,907 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Air_conditioner_33051602e09806002e71_Test'});;
2022-02-19 16:06:22,908 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Air_conditioner_33051602e09806002e71'});;
2022-02-19 16:06:27,163 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"error":0,"awaitId":63156624,"result":"2022-02-19 16:06:27"}
2022-02-19 16:07:22,911 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Air_conditioner_33051602e09806002e71_Test'},'temp_current','23.0');;
2022-02-19 16:07:22,912 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Air_conditioner_33051602e09806002e71'},'temp_current','23.0');;
2022-02-19 16:07:27,544 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Stecker_Homatic_Hub_Ueberwachung_bf35cb0f514fd1e576x3hp'});;
2022-02-19 16:07:46,713 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"error":0,"awaitId":79837999,"result":"2022-02-19 16:07:46"}
2022-02-19 16:08:48,154 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Air_conditioner_33051602e09806002e71_Test'},'temp_set','26.0');;
2022-02-19 16:08:48,155 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Air_conditioner_33051602e09806002e71'},'temp_set','26.0');;
2022-02-19 16:08:48,156 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Stecker_SilverCrest_Hub_Ueberwachung_bf7a36070c5531b25aubiy'},'state','off');;
2022-02-19 17:06:09,467 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Air_conditioner_33051602e09806002e71'},'temp_set','26.0');;
2022-02-19 17:06:09,475 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Air_conditioner_33051602e09806002e71_Test'},'temp_set','26.0');;
2022-02-19 17:06:53,842 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Stecker_Homatic_Hub_Ueberwachung_bf35cb0f514fd1e576x3hp'});;
2022-02-19 17:07:09,471 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Air_conditioner_33051602e09806002e71'},'temp_current','24.0');;
2022-02-19 17:07:09,478 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Air_conditioner_33051602e09806002e71_Test'},'temp_current','24.0');;
2022-02-19 17:07:11,711 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"error":0,"awaitId":20760239,"result":"2022-02-19 17:07:11"}
2022-02-19 17:07:11,713 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"result":"temp_current: 24.0","awaitId":10408603,"error":0}
2022-02-19 17:07:11,715 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"result":"temp_current: 24.0","awaitId":68094845,"error":0}
2022-02-19 17:08:14,862 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsEndUpdate($defs{'Air_conditioner_33051602e09806002e71'},1);;
2022-02-19 17:08:14,865 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsEndUpdate($defs{'Air_conditioner_33051602e09806002e71_Test'},1);;
2022-02-19 17:08:14,883 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Stecker_SilverCrest_Hub_Ueberwachung_bf7a36070c5531b25aubiy'},'state','off');;
2022-02-19 18:06:41,800 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Air_conditioner_33051602e09806002e71_Test'});;
2022-02-19 18:06:41,801 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Air_conditioner_33051602e09806002e71'});;
2022-02-19 18:07:03,107 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsSingleUpdate($defs{'Bewegungsmelder_Tuya_bf728d260af2218b1b1gpk'},'state','nomotion',1)
2022-02-19 18:07:28,144 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Stecker_Homatic_Hub_Ueberwachung_bf35cb0f514fd1e576x3hp'});;
2022-02-19 18:07:41,804 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Air_conditioner_33051602e09806002e71_Test'},'state','off');;
2022-02-19 18:07:41,805 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Air_conditioner_33051602e09806002e71'},'state','off');;
2022-02-19 18:07:46,532 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"result":"2022-02-19 18:07:46","awaitId":81679180,"error":0}
2022-02-19 18:07:46,536 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"error":0,"result":null,"awaitId":95997206}
2022-02-19 18:07:46,540 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"result":null,"awaitId":95208219,"error":0}
2022-02-19 18:08:47,208 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Stecker_SilverCrest_Hub_Ueberwachung_bf7a36070c5531b25aubiy'},'state','off');;
2022-02-19 18:08:47,213 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsEndUpdate($defs{'Air_conditioner_33051602e09806002e71_Test'},1);;
2022-02-19 18:08:47,217 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsEndUpdate($defs{'Air_conditioner_33051602e09806002e71'},1);;
2022-02-19 18:08:47,223 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsSingleUpdate($defs{'Bewegungsmelder_Tuya_bf728d260af2218b1b1gpk'},'state','nomotion',1)
2022-02-19 18:58:23,920 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Wohnzimmervorhang6_84076817a4e57c10dabb'});;
2022-02-19 19:06:11,319 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Kuechenvorhang_83652817dc4f22618a08'},'border','down');;
2022-02-19 19:06:11,326 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Wohnzimmervorhang1_84076817a4e57c10f479'});;
2022-02-19 19:06:11,336 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Toilettenvorhang_84076817a4e57c109f68'});;
2022-02-19 19:06:19,955 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Air_conditioner_33051602e09806002e71_Test'});;
2022-02-19 19:06:19,956 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Air_conditioner_33051602e09806002e71'});;
2022-02-19 19:06:29,854 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"error":0,"awaitId":56745445,"result":"border: down"}
2022-02-19 19:06:29,856 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"result":"2022-02-19 19:06:29","awaitId":45515250,"error":0}
2022-02-19 19:06:29,859 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"result":"2022-02-19 19:06:29","awaitId":52847429,"error":0}
2022-02-19 19:06:29,860 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"error":0,"awaitId":97402114,"result":"2022-02-19 19:06:29"}
2022-02-19 19:06:29,862 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"awaitId":29933338,"result":"2022-02-19 19:06:29","error":0}
2022-02-19 19:07:29,996 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Wohnzimmervorhang1_84076817a4e57c10f479'},'work_state','opening');;
2022-02-19 19:07:30,000 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Toilettenvorhang_84076817a4e57c109f68'},'work_state','opening');;
2022-02-19 19:07:30,005 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Air_conditioner_33051602e09806002e71'});;
2022-02-19 19:07:30,012 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Air_conditioner_33051602e09806002e71_Test'});;
2022-02-19 19:07:30,021 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Kuechenvorhang_83652817dc4f22618a08'});;
2022-02-19 19:07:30,096 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Stecker_Homatic_Hub_Ueberwachung_bf35cb0f514fd1e576x3hp'});;
2022-02-19 19:07:48,543 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"awaitId":47137269,"result":"work_state: opening","error":0}
2022-02-19 19:07:48,544 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"error":0,"awaitId":19393312,"result":"work_state: opening"}
2022-02-19 19:07:48,546 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"awaitId":39123660,"result":"2022-02-19 19:07:48","error":0}
2022-02-19 19:07:48,548 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"result":"2022-02-19 19:07:48","awaitId":55697775,"error":0}
2022-02-19 19:07:48,549 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"error":0,"awaitId":54950812,"result":"2022-02-19 19:07:48"}
2022-02-19 19:07:48,551 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"awaitId":77012582,"result":"2022-02-19 19:07:48","error":0}
2022-02-19 19:08:52,630 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsEndUpdate($defs{'Wohnzimmervorhang2_83652817a4e57c966258'},1);;
2022-02-19 19:08:52,632 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Wohnzimmervorhang1_84076817a4e57c10f479'},'work_state','opening');;
2022-02-19 19:08:52,640 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Toilettenvorhang_84076817a4e57c109f68'},'work_state','opening');;
2022-02-19 19:08:52,643 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Air_conditioner_33051602e09806002e71_Test'},'mode','cold');;
2022-02-19 19:08:52,648 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Air_conditioner_33051602e09806002e71'},'mode','cold');;
2022-02-19 19:08:52,651 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Stecker_SilverCrest_Hub_Ueberwachung_bf7a36070c5531b25aubiy'},'cur_current','0.0');;
2022-02-19 19:08:52,655 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Kuechenvorhang_83652817dc4f22618a08'},'work_state','opening');;
2022-02-19 19:08:52,871 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Wechselschalter_Treppenhaus_unten_bf2f62ca78c544ff14bnmx'});;
2022-02-19 19:53:43,780 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2022-02-19 19:53:43,791 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2022-02-19 19:53:43,831 - INFO - websockets.server: server listening on 0.0.0.0:15733
2022-02-19 19:54:11,156 - INFO - websockets.server: connection open
2022-02-19 19:54:11,157 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2022-02-19 19:55:16,071 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2022-02-19 19:55:16,082 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2022-02-19 19:55:16,121 - INFO - websockets.server: server listening on 0.0.0.0:15733
2022-02-19 19:56:49,112 - INFO - websockets.server: connection open
2022-02-19 19:56:49,113 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2022-02-19 19:56:51,349 - INFO - fhempy.lib.pkg_installer: Attempting install of spotipy==2.19.0
2022-02-19 19:56:55,710 - INFO - fhempy.lib.pkg_installer: Successfully installed spotipy==2.19.0 update!
2022-02-19 19:57:00,822 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 19:57:00,867 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 19:57:00,881 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 19:57:00,884 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 19:57:01,640 - ERROR - Robot_bf623c4459370bd192tywm: 'result'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 30, in _init_device
await self._setup_device()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 58, in _setup_device
self._t_info = await utils.run_blocking(
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/utils.py", line 34, in run_blocking
return await asyncio.get_event_loop().run_in_executor(pool, function)
File "/usr/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/device.py", line 332, in get_device_info
return self.device_manage.get_device_info(device_id)
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/device.py", line 580, in get_device_info
response["result"].pop("status")
KeyError: 'result'
2022-02-19 19:57:08,281 - ERROR - Wohnzimmerkamera_bf905cb6a14a43dbf9hhfu: unsupported operand type(s) for /: 'str' and 'int'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 280, in update_readings_arr
self._convert_value2fhem(status["code"], status["value"]),
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 234, in _convert_value2fhem
return value / (10 ** int(values["scale"]))
TypeError: unsupported operand type(s) for /: 'str' and 'int'
2022-02-19 19:57:39,003 - ERROR - pychromecast.socket_client: [Google-Nest(192.168.178.28):8009] Failed to connect to service ServiceInfo(type='mdns', data='google-nest-hub-5c8f0c586b0fcf88151443201b9df76a._googlecast._tcp.local.'), retrying in 5.0s
2022-02-19 21:13:53,417 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2022-02-19 21:13:53,429 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2022-02-19 21:13:53,469 - INFO - websockets.server: server listening on 0.0.0.0:15733
2022-02-19 21:15:27,469 - INFO - websockets.server: connection open
2022-02-19 21:15:27,470 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2022-02-19 21:15:31,086 - INFO - fhempy.lib.pkg_installer: Attempting install of spotipy==2.18.0
2022-02-19 21:15:35,824 - INFO - fhempy.lib.pkg_installer: Successfully installed spotipy==2.18.0 update!
2022-02-19 21:15:42,603 - WARNING - asyncio: Executing <Task pending name='Task-389' coro=<tuya_cloud_device._init_device() running at /opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py:30> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at /usr/lib/python3.8/asyncio/futures.py:360, <TaskWakeupMethWrapper object at 0x7f0d06564880>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> created at /usr/lib/python3.8/asyncio/tasks.py:382> took 0.106 seconds
2022-02-19 21:15:42,728 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 21:15:42,962 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 21:15:42,966 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 21:15:42,968 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 21:15:43,077 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 21:15:43,087 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 21:15:43,090 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 21:15:43,090 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 21:15:43,092 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 21:15:43,259 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 21:15:43,663 - ERROR - Robot_bf623c4459370bd192tywm: 'result'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 30, in _init_device
await self._setup_device()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 58, in _setup_device
self._t_info = await utils.run_blocking(
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/utils.py", line 34, in run_blocking
return await asyncio.get_event_loop().run_in_executor(pool, function)
File "/usr/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/device.py", line 332, in get_device_info
return self.device_manage.get_device_info(device_id)
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/device.py", line 580, in get_device_info
response["result"].pop("status")
KeyError: 'result'
2022-02-19 21:15:53,482 - ERROR - Wohnzimmerkamera_bf905cb6a14a43dbf9hhfu: unsupported operand type(s) for /: 'str' and 'int'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 280, in update_readings_arr
self._convert_value2fhem(status["code"], status["value"]),
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 234, in _convert_value2fhem
return value / (10 ** int(values["scale"]))
TypeError: unsupported operand type(s) for /: 'str' and 'int'
2022-02-19 21:16:39,598 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsSingleUpdate($defs{'Castdevice_OG.Badezimmer'},'spotify_user','login required',1)
2022-02-19 21:16:39,658 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsSingleUpdate($defs{'Castdevice_Ultra'},'spotify_user','login required',1)
2022-02-19 21:16:39,663 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsSingleUpdate($defs{'Castdevice_Wohnzimmer'},'spotify_user','login required',1)
2022-02-19 21:32:39,699 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2022-02-19 21:32:39,711 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2022-02-19 21:32:39,749 - INFO - websockets.server: server listening on 0.0.0.0:15733
2022-02-19 21:34:16,155 - INFO - websockets.server: connection open
2022-02-19 21:34:16,157 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2022-02-19 21:34:16,494 - INFO - fhempy.lib.pkg_installer: Attempting install of spotipy==2.19.0
2022-02-19 21:34:21,494 - INFO - fhempy.lib.pkg_installer: Successfully installed spotipy==2.19.0 update!
2022-02-19 21:34:27,883 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 21:34:27,901 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 21:34:28,329 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 21:34:28,359 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 21:34:28,518 - ERROR - Robot_bf623c4459370bd192tywm: 'result'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 30, in _init_device
await self._setup_device()
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 58, in _setup_device
self._t_info = await utils.run_blocking(
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/utils.py", line 34, in run_blocking
return await asyncio.get_event_loop().run_in_executor(pool, function)
File "/usr/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/device.py", line 332, in get_device_info
return self.device_manage.get_device_info(device_id)
File "/opt/fhem/.local/lib/python3.8/site-packages/tuya_iot/device.py", line 580, in get_device_info
response["result"].pop("status")
KeyError: 'result'
2022-02-19 21:34:39,115 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 21:34:39,166 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 21:34:39,184 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 21:34:39,211 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com. Connection pool size: 10
2022-02-19 21:34:42,327 - ERROR - Wohnzimmerkamera_bf905cb6a14a43dbf9hhfu: unsupported operand type(s) for /: 'str' and 'int'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 280, in update_readings_arr
self._convert_value2fhem(status["code"], status["value"]),
File "/opt/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 234, in _convert_value2fhem
return value / (10 ** int(values["scale"]))
TypeError: unsupported operand type(s) for /: 'str' and 'int'
2022-02-19 21:35:08,626 - ERROR - pychromecast.socket_client: [Google-Nest(192.168.178.28):8009] Failed to connect to service ServiceInfo(type='mdns', data='google-nest-hub-5c8f0c586b0fcf88151443201b9df76a._googlecast._tcp.local.'), retrying in 5.0s
2022-02-19 22:34:23,579 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsEndUpdate($defs{'Air_conditioner_33051602e09806002e71_Test'},1);;
2022-02-19 22:34:23,582 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsEndUpdate($defs{'Air_conditioner_33051602e09806002e71'},1);;
2022-02-19 22:34:23,660 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Stecker_Homatic_Hub_Ueberwachung_bf35cb0f514fd1e576x3hp'});;
2022-02-19 22:34:42,231 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"error":0,"awaitId":75289182,"result":"2022-02-19 22:34:42"}
2022-02-19 22:34:42,236 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"error":0,"awaitId":40695196,"result":null}
2022-02-19 22:34:42,243 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"result":null,"error":0,"awaitId":59595978}
2022-02-19 22:34:44,267 - WARNING - asyncio: Executing <Task pending name='Task-4' coro=<WebSocketServerProtocol.handler() running at /opt/fhem/.local/lib/python3.8/site-packages/websockets/legacy/server.py:224> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x7ff539aac400>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> created at /opt/fhem/.local/lib/python3.8/site-packages/websockets/legacy/server.py:141> took 0.137 seconds
2022-02-19 22:35:48,535 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Air_conditioner_33051602e09806002e71'},'temp_set_f','61.0');;
2022-02-19 22:35:48,553 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsEndUpdate($defs{'Air_conditioner_33051602e09806002e71_Test'},1);;
2022-02-19 22:35:48,558 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Stecker_SilverCrest_Hub_Ueberwachung_bf7a36070c5531b25aubiy'});;
2022-02-19 23:34:22,378 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Ladestation_bf5ee44c2ba7b84276eueh'});;
2022-02-19 23:34:22,380 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Air_conditioner_33051602e09806002e71_Test'},'temp_set','26.0');;
2022-02-19 23:34:22,382 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Air_conditioner_33051602e09806002e71'},'temp_set','26.0');;
2022-02-19 23:34:22,449 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBeginUpdate($defs{'Stecker_Homatic_Hub_Ueberwachung_bf35cb0f514fd1e576x3hp'});;
2022-02-19 23:34:40,762 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"result":"2022-02-19 23:34:40","awaitId":81795006,"error":0}
2022-02-19 23:34:40,764 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"result":"temp_set: 26.0","awaitId":37336900,"error":0}
2022-02-19 23:34:40,765 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"awaitId":71639529,"error":0,"result":"temp_set: 26.0"}
2022-02-19 23:34:40,767 - ERROR - fhempy.lib.fhem: Failed to set result, received: {"result":"2022-02-19 23:34:40","error":0,"awaitId":96107125}
2022-02-19 23:35:42,159 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Ladestation_bf5ee44c2ba7b84276eueh'},'cur_power','0.0');;
2022-02-19 23:35:42,161 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsEndUpdate($defs{'Air_conditioner_33051602e09806002e71_Test'},1);;
2022-02-19 23:35:42,165 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsEndUpdate($defs{'Air_conditioner_33051602e09806002e71'},1);;
2022-02-19 23:35:42,174 - ERROR - fhempy.lib.fhem: Timeout - NO RESPONSE for command: readingsBulkUpdate($defs{'Stecker_SilverCrest_Hub_Ueberwachung_bf7a36070c5531b25aubiy'},'state','off');;
Hmm...dein FHEM hat die ganzen Commands nicht verarbeitet. Hast du womöglich ein Modul im Einsatz, dass FHEM ab und zu blockiert?
Ansonsten probier Mal fhempy Neustart ob der Fehler dann wieder auftritt?
Zitat von: dominik am 16 Februar 2022, 20:01:25
Ist dein IoT Core Service auch ausgelaufen? Versuch dieses mal zu verlängern...
Laut der Meldung, sollte es auch einen "free basic resource pack" geben.
ich hab ja free basic.
Von IoT Core? Ist das auch abgelaufen?
Zitat von: dominik am 20 Februar 2022, 20:32:02
Von IoT Core? Ist das auch abgelaufen?
??? keine ahnung :-[
Zitat von: satprofi am 21 Februar 2022, 14:14:47
??? keine ahnung :-[
Cloud - Development - Projekt auswählen - Service API
Schau ob dort IoT Core steht und ob das schon abgelaufen ist.
Ich habe die trial, und das ist max. 1 monat gültig. :-[
update/verlängern nicht möglich
Hmm,
was ist das für ein Screenshot?
Ich habe folgende Services.
Wobei:
Core abgelaufen ist aber kein Problem darstellt.
Subscribe : Trial Edition, Expiration Time : 2021-11-18
Authorization ist in der Basic Edition und ok.
Dort steht 12 Monate und Price ist 0$
Smart Home Scene Linkage, Data Dashboard Service ist gelistet als Time-Limited Free.
Dort steht 12 Monate und Price ist 0$
Device Status Notification
Subscribe : Trial EditionExpiration Time : 2022-10-18
Gruß,
Stefan
deine gewünschte seite, sieht bei mir eben anders aus.
Wie sieht diese Seite bei dir aus? Poste bitte den gesamten Screen damit man sieht in welchem Menüpunkt du bist.
Hi,
erstmal danke für das Modul. Ich habe folgenden Wireless Schalter mit 2x Taster (Bild 1).
Ich würde gerne mit der Linken Taste "switch1_value" Lichter einschalten und mit der Rechten Taste "switch_mode2" Lichter ausschalten. Leider wird beim schalten von Taste 2 auch immer "switch1_value" mit getriggert (Bild 2), so dass ich das Licht nur einschalten aber nicht ausschalten kann. Kann man irgendwie zwei unterschiedliche Readings für Taste 1 und Taste 2 integrieren?
defmod Schalter_Flur_Oben DOIF ([Wireless_Switch__bfc6fc95442d988644evzt:switch1_value] eq "single_click")\
(set MQTT2_zigbee_WohnzimmerOben1 on, set MQTT2_zigbee_WohnzimmerOben2 on, set MQTT2_zigbee_WohnzimmerOben3 on)\
DOELSEIF ([Wireless_Switch__bfc6fc95442d988644evzt:switch_mode2] eq "click")\
(set MQTT2_zigbee_WohnzimmerOben1 off, set MQTT2_zigbee_WohnzimmerOben2 off, set MQTT2_zigbee_WohnzimmerOben3 off)
attr Schalter_Flur_Oben do always
setstate Schalter_Flur_Oben cmd_1
setstate Schalter_Flur_Oben 2022-03-01 19:10:33 Device Wireless_Switch__bfc6fc95442d988644evzt
setstate Schalter_Flur_Oben 2022-03-01 19:10:33 cmd 1
setstate Schalter_Flur_Oben 2022-03-01 19:10:33 cmd_event Wireless_Switch__bfc6fc95442d988644evzt
setstate Schalter_Flur_Oben 2022-03-01 19:10:33 cmd_nr 1
setstate Schalter_Flur_Oben 2022-03-01 19:10:33 e_Wireless_Switch__bfc6fc95442d988644evzt_switch1_value single_click
setstate Schalter_Flur_Oben 2022-03-01 19:10:33 e_Wireless_Switch__bfc6fc95442d988644evzt_switch_mode2 click
setstate Schalter_Flur_Oben 2022-03-01 19:10:28 mode enabled
setstate Schalter_Flur_Oben 2022-03-01 19:10:33 state cmd_1
Wie sieht das beim Debuggen des Devices im TuYa Web aus, schalten da auch immer beide?
Ich habe im Modul eigentlich keine Business Logik implementiert die irgendwas auf 1 Reading zusammen führt.
meinst du das Debug "Log"? Da wird immer zwischen Button 1 und 2 unterschieden.
Stell bitte Mal auf verbose 5 und poste das fhempy Log beim Schalten.
so korrekt
"FHEMPYTYPE": "ring", "PYTHONTYPE": "ring", "argsh": {}, "function": "Set", "args": ["RingDoorBell", "?"], "finished": 1, "returnval": ""}
2022.03.01 21:00:24 5: BindingsIo (local_pybinding): QUEUE: finished handling - 0
2022.03.01 21:00:24 4: BindingsIo (local_pybinding): end fhempyFunction: RingDoorBell => Set (66702568) - result:
2022.03.01 21:00:41 4: BindingsIo (local_pybinding): start fhempyFunction: Wireless_Switch__bfc6fc95442d988644evzt => Set (26311981)
2022.03.01 21:00:41 4: BindingsIo (local_pybinding): <<< WS: {"defargsh":{},"NAME":"Wireless_Switch__bfc6fc95442d988644evzt","defargs":["Wireless_Switch__bfc6fc95442d988644evzt","PythonModule","tuya_cloud","tuya_cloud_connector","bfc6fc95442d988644evzt"],"msgtype":"function","id":"26311981","PYTHONTYPE":"tuya_cloud","argsh":{},"FHEMPYTYPE":"tuya_cloud","function":"Set","args":["Wireless_Switch__bfc6fc95442d988644evzt","?"]}
2022.03.01 21:00:41 5: DevIo_SimpleWrite local_pybinding: 7b226465666172677368223a7b7d2c224e414d45223a22576972656c6573735f5377697463685f5f62666336666339353434326439383836343465767a74222c2264656661726773223a5b22576972656c6573735f5377697463685f5f62666336666339353434326439383836343465767a74222c22507974686f6e4d6f64756c65222c22747579615f636c6f7564222c22747579615f636c6f75645f636f6e6e6563746f72222c2262666336666339353434326439383836343465767a74225d2c226d736774797065223a2266756e6374696f6e222c226964223a223236333131393831222c22505954484f4e54595045223a22747579615f636c6f7564222c226172677368223a7b7d2c224648454d505954595045223a22747579615f636c6f7564222c2266756e6374696f6e223a22536574222c2261726773223a5b22576972656c6573735f5377697463685f5f62666336666339353434326439383836343465767a74222c223f225d7d
2022.03.01 21:00:41 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2022.03.01 21:00:41 5: BindingsIo (local_pybinding): DevIo_SimpleRead WithTimeout
2022.03.01 21:00:41 4: BindingsIo (local_pybinding): >>> WS: {"defargsh": {}, "NAME": "Wireless_Switch__bfc6fc95442d988644evzt", "defargs": ["Wireless_Switch__bfc6fc95442d988644evzt", "PythonModule", "tuya_cloud", "tuya_cloud_connector", "bfc6fc95442d988644evzt"], "msgtype": "function", "id": "26311981", "PYTHONTYPE": "tuya_cloud", "argsh": {}, "FHEMPYTYPE": "tuya_cloud", "function": "Set", "args": ["Wireless_Switch__bfc6fc95442d988644evzt", "?"], "finished": 1, "returnval": "Unknown argument ?, choose one of "}
2022.03.01 21:00:41 5: BindingsIo (local_pybinding): QUEUE: start handling - 1
2022.03.01 21:00:41 5: processMessage: {"defargsh": {}, "NAME": "Wireless_Switch__bfc6fc95442d988644evzt", "defargs": ["Wireless_Switch__bfc6fc95442d988644evzt", "PythonModule", "tuya_cloud", "tuya_cloud_connector", "bfc6fc95442d988644evzt"], "msgtype": "function", "id": "26311981", "PYTHONTYPE": "tuya_cloud", "argsh": {}, "FHEMPYTYPE": "tuya_cloud", "function": "Set", "args": ["Wireless_Switch__bfc6fc95442d988644evzt", "?"], "finished": 1, "returnval": "Unknown argument ?, choose one of "}
2022.03.01 21:00:41 5: BindingsIo (local_pybinding): QUEUE: finished handling - 0
2022.03.01 21:00:41 4: BindingsIo (local_pybinding): end fhempyFunction: Wireless_Switch__bfc6fc95442d988644evzt => Set (26311981) - result: Unknown argument ?, choose one of
2022.03.01 21:00:41 4: BindingsIo (local_pybinding): start fhempyFunction: Wireless_Switch__bfc6fc95442d988644evzt => FW_detailFn (35156442)
2022.03.01 21:00:41 4: BindingsIo (local_pybinding): <<< WS: {"id":"35156442","msgtype":"function","defargs":["Wireless_Switch__bfc6fc95442d988644evzt","PythonModule","tuya_cloud","tuya_cloud_connector","bfc6fc95442d988644evzt"],"NAME":"Wireless_Switch__bfc6fc95442d988644evzt","defargsh":{},"args":["WEB","Wireless_Switch__bfc6fc95442d988644evzt","fhempy",null],"function":"FW_detailFn","FHEMPYTYPE":"tuya_cloud","argsh":{},"PYTHONTYPE":"tuya_cloud"}
2022.03.01 21:00:41 5: DevIo_SimpleWrite local_pybinding: 7b226964223a223335313536343432222c226d736774797065223a2266756e6374696f6e222c2264656661726773223a5b22576972656c6573735f5377697463685f5f62666336666339353434326439383836343465767a74222c22507974686f6e4d6f64756c65222c22747579615f636c6f7564222c22747579615f636c6f75645f636f6e6e6563746f72222c2262666336666339353434326439383836343465767a74225d2c224e414d45223a22576972656c6573735f5377697463685f5f62666336666339353434326439383836343465767a74222c226465666172677368223a7b7d2c2261726773223a5b22574542222c22576972656c6573735f5377697463685f5f62666336666339353434326439383836343465767a74222c226668656d7079222c6e756c6c5d2c2266756e6374696f6e223a2246575f64657461696c466e222c224648454d505954595045223a22747579615f636c6f7564222c226172677368223a7b7d2c22505954484f4e54595045223a22747579615f636c6f7564227d
2022.03.01 21:00:41 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2022.03.01 21:00:41 5: BindingsIo (local_pybinding): DevIo_SimpleRead WithTimeout
2022.03.01 21:00:41 5: BindingsIo (local_pybinding): QUEUE: start handling - 0
2022.03.01 21:00:41 5: BindingsIo (local_pybinding): QUEUE: finished handling - 0
2022.03.01 21:00:41 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2022.03.01 21:00:41 5: BindingsIo (local_pybinding): DevIo_SimpleRead WithTimeout
2022.03.01 21:00:41 4: BindingsIo (local_pybinding): >>> WS: {"id": "35156442", "msgtype": "function", "defargs": ["Wireless_Switch__bfc6fc95442d988644evzt", "PythonModule", "tuya_cloud", "tuya_cloud_connector", "bfc6fc95442d988644evzt"], "NAME": "Wireless_Switch__bfc6fc95442d988644evzt", "defargsh": {}, "args": ["WEB", "Wireless_Switch__bfc6fc95442d988644evzt", "fhempy", null], "function": "FW_detailFn", "FHEMPYTYPE": "tuya_cloud", "argsh": {}, "PYTHONTYPE": "tuya_cloud", "finished": 1, "returnval": "<script type=\"text/javascript\">\n function displayHelp() {\n var x = document.getElementById(\"fhempyReadme\");\n if (x.style.display === \"none\") {\n x.style.display = \"block\";\n } else {\n x.style.display = \"none\";\n }\n var off = $(\"#fhempyReadme\").position().top-20;\n $('body, html').animate({scrollTop:off}, 500);\n }\n \n $(document).ready(function() {\n $(\"#content\").append('<div class=\"makeTable help\" id=\"fhempyReadme\"></div>');\n $(\"#fhempyReadme\").html(`<h1>Tuya Cloud</h1><br><br><p>This module uses the official tuya library to communicate with all sort of tuya devices supported by the Tuya Cloud API.</p><br><br><h2>Installation</h2><br><br><p>You need to setup a Tuya IoT project on the tuya development platform. It also requires you to create a Tuya Developer account which is used in the first step of the instructions. That's not the SmartLife or TuyaApp account!</p><br><br><p>Please follow the instructions here:</p><br><br><p>https://github.com/tuya/tuya-home-assistant/wiki/Tuya-IoT-Platform-Configuration-Guide-Using-Smart-Home-PaaS</p><br><br><h2>Usage</h2><br><br><p>Please read installation instructions before! You need the tuya developer account and a smart home project on the tuya platform to get client id and client secret.</p><br><br><p><code><br>define tuya_cloud_connector fhempy tuya_cloud setup <CLIENT_ID> <CLIENT_SECRET> <USERNAME> <PASSWORD> [<APPTYPE>] [<REGION>]<br></code></p><br><br><p>This command will create the tuya cloud connector device which automatically create all tuya devices in your FHEM installation.</p><br><br><ul><br><li>CLIENT_ID: From tuya developer portal</li><br><li>CLIENT_SECRET: From tuya developer portal</li><br><li>USERNAME: From SmartLife/Tuya app (not developer account)</li><br><li>PASSWORD: From SmartLife/Tuya app (not developer account)</li><br><li>APPTYPE: smartlife (default) or tuyaSmart, depending on the app you use</li><br><li>REGION: Europe (default), China, America, India, EasternAmerica, WesternEurope</li><br></ul><br>`);\n document.getElementById(\"fhempyReadme\").style.display = \"none\";\n\n var helpCmdStr = '{}';\n var helpCmdJson = JSON.parse(helpCmdStr);\n $(\"select.set\").change(helpSetAction);\n function\n helpSetAction(){\n var cmd = $(\"select.set\").val()\n if(helpCmdJson[cmd] && helpCmdJson[cmd].help) {\n if (document.getElementById(\"idCmdHelp\")===null) {\n $('<div id=\"idCmdHelp\" class=\"makeTable help\"></div>')\n .insertBefore(\"div.makeTable.internals\");\n }\n $(\"div#idCmdHelp\").html(helpCmdJson[cmd].help + \"<br>\");\n } else {\n $(\"div#idCmdHelp\").remove();\n }\n }\n helpSetAction();\n\n var helpAttrStr = '{}';\n var helpAttrJson = JSON.parse(helpAttrStr);\n $(\"select.attr\").change(helpAttrAction);\n function\n helpAttrAction(){\n var cmd = $(\"select.attr\").val()\n if(helpAttrJson[cmd] && helpAttrJson[cmd].help) {\n if (document.getElementById(\"idAttrHelp\")===null) {\n $('<div id=\"idAttrHelp\" class=\"makeTable help\"></div>')\n .insertBefore(\"div.makeTable.attributes\");\n }\n $(\"div#idAttrHelp\").html(helpAttrJson[cmd].help + \"<br>\");\n } else {\n $(\"div#idAttrHelp\").remove();\n }\n }\n helpAttrAction();\n\n var helpLink = document.getElementById(\"content\")\n .getElementsByClassName(\"detLink devSpecHelp\");\n helpLink[0].innerHTML = '<div class=\"detLink devSpecHelp\"><a href=\"#\" onclick=\"displayHelp();return false;\">Device specific help</a></div>';\n });\n </script>"}
2022.03.01 21:00:41 5: BindingsIo (local_pybinding): QUEUE: start handling - 1
2022.03.01 21:00:41 5: processMessage: {"id": "35156442", "msgtype": "function", "defargs": ["Wireless_Switch__bfc6fc95442d988644evzt", "PythonModule", "tuya_cloud", "tuya_cloud_connector", "bfc6fc95442d988644evzt"], "NAME": "Wireless_Switch__bfc6fc95442d988644evzt", "defargsh": {}, "args": ["WEB", "Wireless_Switch__bfc6fc95442d988644evzt", "fhempy", null], "function": "FW_detailFn", "FHEMPYTYPE": "tuya_cloud", "argsh": {}, "PYTHONTYPE": "tuya_cloud", "finished": 1, "returnval": "<script type=\"text/javascript\">\n function displayHelp() {\n var x = document.getElementById(\"fhempyReadme\");\n if (x.style.display === \"none\") {\n x.style.display = \"block\";\n } else {\n x.style.display = \"none\";\n }\n var off = $(\"#fhempyReadme\").position().top-20;\n $('body, html').animate({scrollTop:off}, 500);\n }\n \n $(document).ready(function() {\n $(\"#content\").append('<div class=\"makeTable help\" id=\"fhempyReadme\"></div>');\n $(\"#fhempyReadme\").html(`<h1>Tuya Cloud</h1><br><br><p>This module uses the official tuya library to communicate with all sort of tuya devices supported by the Tuya Cloud API.</p><br><br><h2>Installation</h2><br><br><p>You need to setup a Tuya IoT project on the tuya development platform. It also requires you to create a Tuya Developer account which is used in the first step of the instructions. That's not the SmartLife or TuyaApp account!</p><br><br><p>Please follow the instructions here:</p><br><br><p>https://github.com/tuya/tuya-home-assistant/wiki/Tuya-IoT-Platform-Configuration-Guide-Using-Smart-Home-PaaS</p><br><br><h2>Usage</h2><br><br><p>Please read installation instructions before! You need the tuya developer account and a smart home project on the tuya platform to get client id and client secret.</p><br><br><p><code><br>define tuya_cloud_connector fhempy tuya_cloud setup <CLIENT_ID> <CLIENT_SECRET> <USERNAME> <PASSWORD> [<APPTYPE>] [<REGION>]<br></code></p><br><br><p>This command will create the tuya cloud connector device which automatically create all tuya devices in your FHEM installation.</p><br><br><ul><br><li>CLIENT_ID: From tuya developer portal</li><br><li>CLIENT_SECRET: From tuya developer portal</li><br><li>USERNAME: From SmartLife/Tuya app (not developer account)</li><br><li>PASSWORD: From SmartLife/Tuya app (not developer account)</li><br><li>APPTYPE: smartlife (default) or tuyaSmart, depending on the app you use</li><br><li>REGION: Europe (default), China, America, India, EasternAmerica, WesternEurope</li><br></ul><br>`);\n document.getElementById(\"fhempyReadme\").style.display = \"none\";\n\n var helpCmdStr = '{}';\n var helpCmdJson = JSON.parse(helpCmdStr);\n $(\"select.set\").change(helpSetAction);\n function\n helpSetAction(){\n var cmd = $(\"select.set\").val()\n if(helpCmdJson[cmd] && helpCmdJson[cmd].help) {\n if (document.getElementById(\"idCmdHelp\")===null) {\n $('<div id=\"idCmdHelp\" class=\"makeTable help\"></div>')\n .insertBefore(\"div.makeTable.internals\");\n }\n $(\"div#idCmdHelp\").html(helpCmdJson[cmd].help + \"<br>\");\n } else {\n $(\"div#idCmdHelp\").remove();\n }\n }\n helpSetAction();\n\n var helpAttrStr = '{}';\n var helpAttrJson = JSON.parse(helpAttrStr);\n $(\"select.attr\").change(helpAttrAction);\n function\n helpAttrAction(){\n var cmd = $(\"select.attr\").val()\n if(helpAttrJson[cmd] && helpAttrJson[cmd].help) {\n if (document.getElementById(\"idAttrHelp\")===null) {\n $('<div id=\"idAttrHelp\" class=\"makeTable help\"></div>')\n .insertBefore(\"div.makeTable.attributes\");\n }\n $(\"div#idAttrHelp\").html(helpAttrJson[cmd].help + \"<br>\");\n } else {\n $(\"div#idAttrHelp\").remove();\n }\n }\n helpAttrAction();\n\n var helpLink = document.getElementById(\"content\")\n .getElementsByClassName(\"detLink devSpecHelp\");\n helpLink[0].innerHTML = '<div class=\"detLink devSpecHelp\"><a href=\"#\" onclick=\"displayHelp();return false;\">Device specific help</a></div>';\n });\n </script>"}
2022.03.01 21:00:41 5: BindingsIo (local_pybinding): QUEUE: finished handling - 0
2022.03.01 21:00:41 4: BindingsIo (local_pybinding): end fhempyFunction: Wireless_Switch__bfc6fc95442d988644evzt => FW_detailFn (35156442) - result: <script type="text/javascript">
function displayHelp() {
var x = document.getElementById("fhempyReadme");
if (x.style.display === "none") {
x.style.display = "block";
} else {
x.style.display = "none";
}
var off = $("#fhempyReadme").position().top-20;
$('body, html').animate({scrollTop:off}, 500);
}
$(document).ready(function() {
$("#content").append('<div class="makeTable help" id="fhempyReadme"></div>');
$("#fhempyReadme").html(`<h1>Tuya Cloud</h1><br><br><p>This module uses the official tuya library to communicate with all sort of tuya devices supported by the Tuya Cloud API.</p><br><br><h2>Installation</h2><br><br><p>You need to setup a Tuya IoT project on the tuya development platform. It also requires you to create a Tuya Developer account which is used in the first step of the instructions. That's not the SmartLife or TuyaApp account!</p><br><br><p>Please follow the instructions here:</p><br><br><p>https://github.com/tuya/tuya-home-assistant/wiki/Tuya-IoT-Platform-Configuration-Guide-Using-Smart-Home-PaaS</p><br><br><h2>Usage</h2><br><br><p>Please read installation instructions before! You need the tuya developer account and a smart home project on the tuya platform to get client id and client secret.</p><br><br><p><code><br>define tuya_cloud_connector fhempy tuya_cloud setup <CLIENT_ID> <CLIENT_SECRET> <USERNAME> <PASSWORD> [<APPTYPE>] [<REGION>]<br></code></p><br><br><p>This command will create the tuya cloud connector device which automatically create all tuya devices in your FHEM installation.</p><br><br><ul><br><li>CLIENT_ID: From tuya developer portal</li><br><li>CLIENT_SECRET: From tuya developer portal</li><br><li>USERNAME: From SmartLife/Tuya app (not developer account)</li><br><li>PASSWORD: From SmartLife/Tuya app (not developer account)</li><br><li>APPTYPE: smartlife (default) or tuyaSmart, depending on the app you use</li><br><li>REGION: Europe (default), China, America, India, EasternAmerica, WesternEurope</li><br></ul><br>`);
document.getElementById("fhempyReadme").style.display = "none";
var helpCmdStr = '{}';
var helpCmdJson = JSON.parse(helpCmdStr);
$("select.set").change(helpSetAction);
function
helpSetAction(){
var cmd = $("select.set").val()
if(helpCmdJson[cmd] && helpCmdJson[cmd].help) {
if (document.getElementById("idCmdHelp")===null) {
$('<div id="idCmdHelp" class="makeTable help"></div>')
.insertBefore("div.makeTable.internals");
}
$("div#idCmdHelp").html(helpCmdJson[cmd].help + "<br>");
} else {
$("div#idCmdHelp").remove();
}
}
helpSetAction();
var helpAttrStr = '{}';
var helpAttrJson = JSON.parse(helpAttrStr);
$("select.attr").change(helpAttrAction);
function
helpAttrAction(){
var cmd = $("select.attr").val()
if(helpAttrJson[cmd] && helpAttrJson[cmd].help) {
if (document.getElementById("idAttrHelp")===null) {
$('<div id="idAttrHelp" class="makeTable help"></div>')
.insertBefore("div.makeTable.attributes");
}
$("div#idAttrHelp").html(helpAttrJson[cmd].help + "<br>");
} else {
$("div#idAttrHelp").remove();
}
}
helpAttrAction();
var helpLink = document.getElementById("content")
.getElementsByClassName("detLink devSpecHelp");
helpLink[0].innerHTML = '<div class="detLink devSpecHelp"><a href="#" onclick="displayHelp();return false;">Device specific help</a></div>';
});
</script>
2022.03.01 21:00:41 4: BindingsIo (local_pybinding): start fhempyFunction: Wireless_Switch__bfc6fc95442d988644evzt => Set (97917442)
2022.03.01 21:00:41 4: BindingsIo (local_pybinding): <<< WS: {"args":["Wireless_Switch__bfc6fc95442d988644evzt","?"],"function":"Set","FHEMPYTYPE":"tuya_cloud","argsh":{},"PYTHONTYPE":"tuya_cloud","id":"97917442","defargs":["Wireless_Switch__bfc6fc95442d988644evzt","PythonModule","tuya_cloud","tuya_cloud_connector","bfc6fc95442d988644evzt"],"msgtype":"function","NAME":"Wireless_Switch__bfc6fc95442d988644evzt","defargsh":{}}
2022.03.01 21:00:41 5: DevIo_SimpleWrite local_pybinding: 7b2261726773223a5b22576972656c6573735f5377697463685f5f62666336666339353434326439383836343465767a74222c223f225d2c2266756e6374696f6e223a22536574222c224648454d505954595045223a22747579615f636c6f7564222c226172677368223a7b7d2c22505954484f4e54595045223a22747579615f636c6f7564222c226964223a223937393137343432222c2264656661726773223a5b22576972656c6573735f5377697463685f5f62666336666339353434326439383836343465767a74222c22507974686f6e4d6f64756c65222c22747579615f636c6f7564222c22747579615f636c6f75645f636f6e6e6563746f72222c2262666336666339353434326439383836343465767a74225d2c226d736774797065223a2266756e6374696f6e222c224e414d45223a22576972656c6573735f5377697463685f5f62666336666339353434326439383836343465767a74222c226465666172677368223a7b7d7d
2022.03.01 21:00:41 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2022.03.01 21:00:41 5: BindingsIo (local_pybinding): DevIo_SimpleRead WithTimeout
2022.03.01 21:00:41 4: BindingsIo (local_pybinding): >>> WS: {"args": ["Wireless_Switch__bfc6fc95442d988644evzt", "?"], "function": "Set", "FHEMPYTYPE": "tuya_cloud", "argsh": {}, "PYTHONTYPE": "tuya_cloud", "id": "97917442", "defargs": ["Wireless_Switch__bfc6fc95442d988644evzt", "PythonModule", "tuya_cloud", "tuya_cloud_connector", "bfc6fc95442d988644evzt"], "msgtype": "function", "NAME": "Wireless_Switch__bfc6fc95442d988644evzt", "defargsh": {}, "finished": 1, "returnval": "Unknown argument ?, choose one of "}
2022.03.01 21:00:41 5: BindingsIo (local_pybinding): QUEUE: start handling - 1
2022.03.01 21:00:41 5: processMessage: {"args": ["Wireless_Switch__bfc6fc95442d988644evzt", "?"], "function": "Set", "FHEMPYTYPE": "tuya_cloud", "argsh": {}, "PYTHONTYPE": "tuya_cloud", "id": "97917442", "defargs": ["Wireless_Switch__bfc6fc95442d988644evzt", "PythonModule", "tuya_cloud", "tuya_cloud_connector", "bfc6fc95442d988644evzt"], "msgtype": "function", "NAME": "Wireless_Switch__bfc6fc95442d988644evzt", "defargsh": {}, "finished": 1, "returnval": "Unknown argument ?, choose one of "}
2022.03.01 21:00:41 5: BindingsIo (local_pybinding): QUEUE: finished handling - 0
2022.03.01 21:00:41 4: BindingsIo (local_pybinding): end fhempyFunction: Wireless_Switch__bfc6fc95442d988644evzt => Set (97917442) - result: Unknown argument ?, choose one of
2022.03.01 21:00:41 4: BindingsIo (local_pybinding): start fhempyFunction: Wireless_Switch__bfc6fc95442d988644evzt => Get (80887871)
2022.03.01 21:00:41 4: BindingsIo (local_pybinding): <<< WS: {"id":"80887871","msgtype":"function","defargs":["Wireless_Switch__bfc6fc95442d988644evzt","PythonModule","tuya_cloud","tuya_cloud_connector","bfc6fc95442d988644evzt"],"NAME":"Wireless_Switch__bfc6fc95442d988644evzt","defargsh":{},"function":"Get","args":["Wireless_Switch__bfc6fc95442d988644evzt","?"],"FHEMPYTYPE":"tuya_cloud","PYTHONTYPE":"tuya_cloud","argsh":{}}
2022.03.01 21:00:41 5: DevIo_SimpleWrite local_pybinding: 7b226964223a223830383837383731222c226d736774797065223a2266756e6374696f6e222c2264656661726773223a5b22576972656c6573735f5377697463685f5f62666336666339353434326439383836343465767a74222c22507974686f6e4d6f64756c65222c22747579615f636c6f7564222c22747579615f636c6f75645f636f6e6e6563746f72222c2262666336666339353434326439383836343465767a74225d2c224e414d45223a22576972656c6573735f5377697463685f5f62666336666339353434326439383836343465767a74222c226465666172677368223a7b7d2c2266756e6374696f6e223a22476574222c2261726773223a5b22576972656c6573735f5377697463685f5f62666336666339353434326439383836343465767a74222c223f225d2c224648454d505954595045223a22747579615f636c6f7564222c22505954484f4e54595045223a22747579615f636c6f7564222c226172677368223a7b7d7d
2022.03.01 21:00:41 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2022.03.01 21:00:41 5: BindingsIo (local_pybinding): DevIo_SimpleRead WithTimeout
2022.03.01 21:00:41 4: BindingsIo (local_pybinding): >>> WS: {"id": "80887871", "msgtype": "function", "defargs": ["Wireless_Switch__bfc6fc95442d988644evzt", "PythonModule", "tuya_cloud", "tuya_cloud_connector", "bfc6fc95442d988644evzt"], "NAME": "Wireless_Switch__bfc6fc95442d988644evzt", "defargsh": {}, "function": "Get", "args": ["Wireless_Switch__bfc6fc95442d988644evzt", "?"], "FHEMPYTYPE": "tuya_cloud", "PYTHONTYPE": "tuya_cloud", "argsh": {}, "finished": 1, "returnval": ""}
2022.03.01 21:00:41 5: BindingsIo (local_pybinding): QUEUE: start handling - 1
2022.03.01 21:00:41 5: processMessage: {"id": "80887871", "msgtype": "function", "defargs": ["Wireless_Switch__bfc6fc95442d988644evzt", "PythonModule", "tuya_cloud", "tuya_cloud_connector", "bfc6fc95442d988644evzt"], "NAME": "Wireless_Switch__bfc6fc95442d988644evzt", "defargsh": {}, "function": "Get", "args": ["Wireless_Switch__bfc6fc95442d988644evzt", "?"], "FHEMPYTYPE": "tuya_cloud", "PYTHONTYPE": "tuya_cloud", "argsh": {}, "finished": 1, "returnval": ""}
2022.03.01 21:00:41 5: BindingsIo (local_pybinding): QUEUE: finished handling - 0
2022.03.01 21:00:41 4: BindingsIo (local_pybinding): end fhempyFunction: Wireless_Switch__bfc6fc95442d988644evzt => Get (80887871) - result:
2022.03.01 21:00:42 4: BindingsIo (local_pybinding): start fhempyFunction: Wireless_Switch__bfc6fc95442d988644evzt => Set (9754220)
2022.03.01 21:00:42 4: BindingsIo (local_pybinding): <<< WS: {"NAME":"Wireless_Switch__bfc6fc95442d988644evzt","defargsh":{},"id":"9754220","msgtype":"function","defargs":["Wireless_Switch__bfc6fc95442d988644evzt","PythonModule","tuya_cloud","tuya_cloud_connector","bfc6fc95442d988644evzt"],"FHEMPYTYPE":"tuya_cloud","argsh":{},"PYTHONTYPE":"tuya_cloud","args":["Wireless_Switch__bfc6fc95442d988644evzt","?"],"function":"Set"}
2022.03.0
[code]
Bitte fhempy Log, nicht FHEM Log
ich hoffe so ist es besser, hatte oben auch noch geändert. Danke
Hat das Device auch ein state Reading? Ändert sich dieses?
Ich muss wohl das Logging erweitern damit ich was sehe. Ich mach morgen ein neues Release mit mehr Log Output dann kann man das weiter analysieren.
ist immer -> STATE ready
defmod Wireless_Switch__bfc6fc95442d988644evzt PythonModule tuya_cloud tuya_cloud_connector bfc6fc95442d988644evzt
attr Wireless_Switch__bfc6fc95442d988644evzt alias Wireless Switch
attr Wireless_Switch__bfc6fc95442d988644evzt group tuya_cloud
attr Wireless_Switch__bfc6fc95442d988644evzt room fhempy
setstate Wireless_Switch__bfc6fc95442d988644evzt ready
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 21:58:28 active_time 1646140172
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 15:52:42 alarm_active
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 21:58:28 biz_type 0
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 15:52:42 bright_value_1 500
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 15:52:42 bright_value_2 10
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 15:52:42 brightness_max_1 10
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 15:52:42 brightness_max_2 10
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 15:52:42 brightness_min_1 10
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 15:52:42 brightness_min_2 10
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 21:58:28 category wxkg
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 15:52:42 countdown_1 0
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 15:52:42 countdown_2 0
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 21:58:28 create_time 1646140172
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 15:52:42 factory_reset off
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 21:58:28 icon https://images.tuyaeu.com/smart/icon/ay1555059089863sMgqv/4c20ba802ef497cb51ab4fa933518ed6.png
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 21:58:28 id bfc6fc95442d988644evzt
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 21:58:28 ip
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 21:58:28 lat 56.7916
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 21:58:28 local_key 35daa79d7719990e
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 21:58:28 lon 12.6863
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 15:52:42 master_state normal
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 21:58:28 model
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 21:58:28 name Wireless Switch
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 15:52:42 night_light_bright 0
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 15:52:42 night_light_delay 0
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 21:58:28 node_id 0018
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 21:58:28 online on
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 21:58:28 owner_id 50210322
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 21:58:28 product_id eg9bol3v
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 21:58:28 product_name Wireless Switch
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 15:52:42 relay_status off
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 21:58:24 state ready
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 21:58:28 sub on
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 22:09:21 switch1_value single_click
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 22:09:21 switch1a_value 01.03.2022 22:09:21
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 22:09:21 switch2_value 01.03.2022 22:09:21
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 15:52:42 switch_alarm_sound off
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 15:52:42 switch_backlight off
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 15:52:42 switch_led_1 off
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 15:52:42 switch_led_2 off
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 22:09:21 switch_mode2 click
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 15:52:42 system_volume 0
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 21:58:28 time_zone +01:00
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 21:58:28 uid eu16438442825683DyaA
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 21:58:28 update_time 1646140172
setstate Wireless_Switch__bfc6fc95442d988644evzt 2022-03-01 21:58:28 uuid 96f6f37d2d2ade2f
Super, dann warte ich auf das neue Release und dann mal sehen was das Log Output hergibt.
Update released.
Bitte tuya_connector dann auf verbose 5 stellen und fhempy neu starten.
so korrekt? 2x Linke Taste und 2x Rechte Taste hintereinander gedrückt.
2022-03-02 22:53:59,773 - INFO - fhempy.lib.pkg_installer: Successfully installed fhempy update!
2022-03-02 22:54:00,273 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2022-03-02 22:54:00,280 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2022-03-02 22:54:00,311 - INFO - websockets.server: server listening on 0.0.0.0:15733
2022-03-02 22:54:10,014 - INFO - websockets.server: connection open
2022-03-02 22:54:10,015 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2022-03-02 22:55:06,590 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2022-03-02 22:55:06,607 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2022-03-02 22:55:06,664 - INFO - websockets.server: server listening on 0.0.0.0:15733
2022-03-02 22:55:10,815 - INFO - websockets.server: connection open
2022-03-02 22:55:10,816 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2022-03-02 22:57:51,911 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2022-03-02 22:57:51,919 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2022-03-02 22:57:51,943 - INFO - websockets.server: server listening on 0.0.0.0:15733
2022-03-02 22:58:02,013 - INFO - websockets.server: connection open
2022-03-02 22:58:02,014 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
/home/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud.py:30: RuntimeWarning: coroutine 'AttrVal' was never awaited
Coroutine created at (most recent call last)
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/home/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 507, in run
asyncio.get_event_loop().run_forever()
File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
self._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1851, in _run_once
handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
self._context.run(self._callback, *self._args)
File "/home/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud.py", line 30, in Define
if fhem.AttrVal(self.hash["NAME"], "verbose", "3") == "5":
if fhem.AttrVal(self.hash["NAME"], "verbose", "3") == "5":
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
2022-03-02 22:58:04,156 - INFO - fhempy.lib.pkg_installer: Attempting install of fhempy
2022-03-02 22:58:04,795 - INFO - tuya_cloud_connector: Tuya Open Pulsar connected
2022-03-02 22:58:05,315 - INFO - tuya_cloud_connector: create: USB智能遥控器（通用）_bf9a2d0837b2c754c8f1qf PythonModule tuya_cloud tuya_cloud_connector bf9a2d0837b2c754c8f1qf
2022-03-02 22:58:06,087 - INFO - fhempy.lib.pkg_installer: Successfully installed fhempy update!
2022-03-02 22:58:06,686 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2022-03-02 22:58:06,695 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2022-03-02 22:58:06,723 - INFO - websockets.server: server listening on 0.0.0.0:15733
2022-03-02 22:58:16,544 - INFO - websockets.server: connection open
2022-03-02 22:58:16,544 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
/home/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud.py:30: RuntimeWarning: coroutine 'AttrVal' was never awaited
Coroutine created at (most recent call last)
File "FHEM/bindings/python/bin/fhempy", line 113, in <module>
fpb.run()
File "/home/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 507, in run
asyncio.get_event_loop().run_forever()
File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
self._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1851, in _run_once
handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
self._context.run(self._callback, *self._args)
File "/home/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud.py", line 30, in Define
if fhem.AttrVal(self.hash["NAME"], "verbose", "3") == "5":
if fhem.AttrVal(self.hash["NAME"], "verbose", "3") == "5":
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
2022-03-02 22:58:19,293 - INFO - tuya_cloud_connector: Tuya Open Pulsar connected
2022-03-02 22:58:19,778 - INFO - tuya_cloud_connector: create: USB智能遥控器（通用）_bf9a2d0837b2c754c8f1qf PythonModule tuya_cloud tuya_cloud_connector bf9a2d0837b2c754c8f1qf
2022-03-02 22:59:18,239 - DEBUG - tuya_cloud_connector: update_device received for bfc6fc95442d988644evzt
2022-03-02 22:59:18,313 - DEBUG - tuya_cloud_connector: update_device received: {'dataId': 'AAXZQ2SmNPknRN7sYOoABB', 'devId': 'bfc6fc95442d988644evzt', 'productKey': 'eg9bol3v', 'status': [{'1': 'single_click', 'code': 'switch1_value', 't': 1646258358203, 'value': 'single_click'}]}
2022-03-02 22:59:20,813 - DEBUG - tuya_cloud_connector: update_device received: {'dataId': 'AAXZQ2TNScMnRN7sYOoABC', 'devId': 'bfc6fc95442d988644evzt', 'productKey': 'eg9bol3v', 'status': [{'1': 'single_click', 'code': 'switch1_value', 't': 1646258360764, 'value': 'single_click'}]}
2022-03-02 22:59:20,913 - DEBUG - tuya_cloud_connector: update_device received for bfc6fc95442d988644evzt
2022-03-02 22:59:23,460 - DEBUG - tuya_cloud_connector: update_device received for bfc6fc95442d988644evzt
2022-03-02 22:59:23,462 - DEBUG - tuya_cloud_connector: update_device received: {'dataId': 'AAXZQ2T13xInRN7sYOoABD', 'devId': 'bfc6fc95442d988644evzt', 'productKey': 'eg9bol3v', 'status': [{'2': 'single_click', 'code': 'switch_mode2', 't': 1646258363424, 'value': 'click'}]}
2022-03-02 22:59:25,849 - DEBUG - tuya_cloud_connector: update_device received: {'dataId': 'AAXZQ2UZ36AnRN7sYOoACA', 'devId': 'bfc6fc95442d988644evzt', 'productKey': 'eg9bol3v', 'status': [{'2': 'single_click', 'code': 'switch_mode2', 't': 1646258365783, 'value': 'click'}]}
Hast du um 22:59:18-20 Button 1 und um 22:59:23-25 Button 2 gedrückt? Wenn ja, wurde das Reading switch1_value um 22:59:25 auf single_click gesetzt?
ZitatHast du um 22:59:18-20 Button 1 und um 22:59:23-25 Button 2 gedrückt?
Ja und ja.
ZitatWenn ja, wurde das Reading switch1_value um 22:59:25 auf single_click gesetzt?
Ja, es wird immer auf single_click gesetzt, beim drücken von Button 1 und Button2.
Und switch_mode2 wird immer mit click gesetzt.
Was hat das Device selbst für Commands und was passiert wenn du diese ausführst?
gar keine set Commands.
Bitte PN lesen die ich dir geschickt habe, ohne es selbst zu testen, tappe ich im Dunkeln.
ups, jetzt erst gesehen. Die Daten habe ich geschickt.
Moinsen,
nach update gerade eben und Neustart
"fhempy server offline"
????
Zitat von: bewa58 am 05 März 2022, 09:09:30
Moinsen,
nach update gerade eben und Neustart
"fhempy server offline"
????
Ja, sorry, da ist bei mir was schief gegangen. Bitte noch ein update in FHEM machen, dann läuft es wieder.
Hallo Dominik,
fhempy lief Problemlos bis ich heute ein Fhemupdate gemacht habe.
Ich bin jetzt auf der Modulversion 0.1.261
in allen Geräten steht jetzt:
Failed to load module tuya_cloud: Traceback (most recent call last): File "/usr/local/lib/python3.7/dist-packages/fhempy/lib/fhem_pythonbinding.py", line 269, in _onMessage functools.partial(importlib.import_module, pymodule) File "/usr/local/lib/python3.7/dist-packages/fhempy/lib/utils.py", line 34, in run_blocking return await asyncio.get_event_loop().run_in_executor(pool, function) File "/usr/lib/python3.7/concurrent/futures/thread.py", line 57, in run result = self.fn(*self.args, **self.kwargs) File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1006, in _gcd_import File "", line 983, in _find_and_load File "", line 967, in _find_and_load_unlocked File "", line 677, in _load_unlocked File "", line 728, in exec_module File "", line 219, in _call_with_frames_removed File "/usr/local/lib/python3.7/dist-packages/fhempy/lib/tuya_cloud/tuya_cloud.py", line 7, in from fhempy.lib.tuya_cloud.tuya_cloud_device import tuya_cloud_device File "/usr/local/lib/python3.7/dist-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 5, in from tuya_iot.device import TuyaDevice File "/usr/local/lib/python3.7/dist-packages/tuya_iot/__init__.py", line 2, in from .device import TuyaDevice, TuyaDeviceListener, TuyaDeviceManager File "/usr/local/lib/python3.7/dist-packages/tuya_iot/device.py", line 7, in from typing import Any, Literal, Optional ImportError: cannot import name 'Literal' from 'typing' (/usr/lib/python3.7/typing.py)
Wenn ich fhempy manuell auf der Console starte versucht es immer ein Update von async-upnp-client welches fehl schägt.
2022-03-05 15:34:12,531 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2022-03-05 15:34:12,544 - INFO - fhempy.lib.pkg_installer: Attempting install of async-upnp-client==0.20.0
2022-03-05 15:34:20,785 - ERROR - fhempy.lib.pkg_installer: Unable to install package async-upnp-client==0.20.0: Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-knot7a62/aiohttp/
2022-03-05 15:34:20,788 - INFO - fhempy.lib.pkg_installer: Attempting install of async-upnp-client==0.20.0
2022-03-05 15:34:28,934 - ERROR - fhempy.lib.pkg_installer: Unable to install package async-upnp-client==0.20.0: Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-n_6g1vd8/aiohttp/
2022-03-05 15:34:28,936 - INFO - fhempy.lib.pkg_installer: Attempting install of async-upnp-client==0.20.0
2022-03-05 15:34:36,941 - ERROR - fhempy.lib.pkg_installer: Unable to install package async-upnp-client==0.20.0: Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-vzksf3qv/aiohttp/
2022-03-05 15:34:36,943 - INFO - fhempy.lib.fhem_pythonbinding: Advertise fhempy on local network
2022-03-05 15:34:37,327 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2022-03-05 15:34:37,412 - INFO - websockets.server: server listening on 0.0.0.0:15733
2022-03-05 15:34:42,386 - INFO - websockets.server: connection open
2022-03-05 15:34:42,396 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
Alles läuft auf Ubuntu 18.04.6 LTS auf einen Ordroid System.
Habe schon einiges probiert, ohne Erfolg. Würde mich über einen Hinweis freuen.
Gruß Rene
Das Tuya Cloud Modul erfordert nun leider Python 3.8 oder höher. Leider hat Tuya noch keinen Fix dafür released, damit es auch mit Python 3.7 wieder funktioniert.
Danke für die schnelle Info sowie dein Einsatz bei diesem Modul.
Vor dem Update lief es in dem alten Modulstand. Komme ich da wieder hin oder wäre der Weg nach vorne mit einem "sudo apt install python3.8" der bessere Weg.
Gruß
Zitat
Ja, sorry, da ist bei mir was schief gegangen. Bitte noch ein update in FHEM machen, dann läuft es wieder.
gerade update gemacht, server ist connected
aber fhempy_server15..... fehlt
und es wird kein Log-File erzeugt (letzter Eintrag von heute morgen vor dem ersten update)
Nachtrag:
Nachdem ich diesen Text erstellt habe:
local_pybindung update angestossen
und siehe da
alle devices ohne fehlermeldung.
Das hatte ich bereits mehrfach so festgestellt, aber leider funktioniert das sehr selten.
Folgende Fehlermeldungen bei mehreren Devices:
Ring Doorbell
Zitat
Failed to load module ring: Traceback (most recent call last): File "/home/pi/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 268, in _onMessage module_object = await utils.run_blocking( File "/home/pi/.local/lib/python3.9/site-packages/fhempy/lib/utils.py", line 34, in run_blocking return await asyncio.get_event_loop().run_in_executor(pool, function) File "/usr/lib/python3.9/concurrent/futures/thread.py", line 52, in run result = self.fn(*self.args, **self.kwargs) File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1030, in _gcd_import File "", line 1007, in _find_and_load File "", line 986, in _find_and_load_unlocked File "", line 680, in _load_unlocked File "", line 790, in exec_module File "", line 228, in _call_with_frames_removed File "/home/pi/.local/lib/python3.9/site-packages/fhempy/lib/ring/ring.py", line 9, in from ring_doorbell import Auth, Ring File "/home/pi/.local/lib/python3.9/site-packages/ring_doorbell/__init__.py", line 15, in from .auth import Auth # noqa File "/home/pi/.local/lib/python3.9/site-packages/ring_doorbell/auth.py", line 5, in from requests_oauthlib import OAuth2Session File "/home/pi/.local/lib/python3.9/site-packages/requests_oauthlib/__init__.py", line 3, in from .oauth1_auth import OAuth1 File "/home/pi/.local/lib/python3.9/site-packages/requests_oauthlib/oauth1_auth.py", line 9, in from requests.compat import is_py3 File "", line 1007, in _find_and_load File "", line 989, in _find_and_load_unlocked KeyError: 'requests'
TuyaCloud
Zitat
Failed to load module tuya_cloud: Traceback (most recent call last): File "/home/pi/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 268, in _onMessage module_object = await utils.run_blocking( File "/home/pi/.local/lib/python3.9/site-packages/fhempy/lib/utils.py", line 34, in run_blocking return await asyncio.get_event_loop().run_in_executor(pool, function) File "/usr/lib/python3.9/concurrent/futures/thread.py", line 52, in run result = self.fn(*self.args, **self.kwargs) File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1030, in _gcd_import File "", line 1007, in _find_and_load File "", line 986, in _find_and_load_unlocked File "", line 680, in _load_unlocked File "", line 790, in exec_module File "", line 228, in _call_with_frames_removed File "/home/pi/.local/lib/python3.9/site-packages/fhempy/lib/tuya_cloud/tuya_cloud.py", line 7, in from fhempy.lib.tuya_cloud.tuya_cloud_device import tuya_cloud_device File "/home/pi/.local/lib/python3.9/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 5, in from tuya_iot.device import TuyaDevice File "/home/pi/.local/lib/python3.9/site-packages/tuya_iot/__init__.py", line 1, in from .asset import TuyaAssetManager File "/home/pi/.local/lib/python3.9/site-packages/tuya_iot/asset.py", line 6, in from .openapi import TuyaOpenAPI File "/home/pi/.local/lib/python3.9/site-packages/tuya_iot/openapi.py", line 10, in import requests File "/usr/lib/python3/dist-packages/requests/__init__.py", line 118, in from . import utils File "/usr/lib/python3/dist-packages/requests/utils.py", line 27, in from ._internal_utils import to_native_string File "/usr/lib/python3/dist-packages/requests/_internal_utils.py", line 11, in from .compat import is_py2, builtin_str, str ImportError: cannot import name 'builtin_str' from partially initialized module 'requests.compat' (most likely due to a circular import) (/usr/lib/python3/dist-packages/requests/compat.py)
hatte mich seit Weihnachten nicht mehr um dein Modul gekümmert wg. Zeitmangel und hatte
abgewartet.
Was ich vor 2 Tagen noch festgestellt hatte:
es werden nach update bzw auch nur nach Neustart
bereits vorhandene Devices wieder angelegt.
Zitat
2022-03-04 01:30:23,913 - INFO - tuya_cloud: create: Fluter_A1_41518006f4cfa25b52db PythonModule tuya_cloud tuya_cloud 41518006f4cfa25b52db
hier Bildschirmcopy aus Tuya Iot Platform
Zitat
Fluter_A1 41518006f4cfa25b52db Smart light vorname.name@gmail.com Online 2021-11-26 19:23:39 Debug Device
nach mehreren Neustarts funktioniert es dann, aber auch nicht immer.
Erst wenn ich alle devices aus fhem lösche läuft es dann
aber nur bis zum nächsten neustart.
???
Nachtrag:
gerade nochmal update local binding gemacht
alle devices ohne fehlermeldung
Zitat von: skycrack am 05 März 2022, 16:21:02
Danke für die schnelle Info sowie dein Einsatz bei diesem Modul.
Vor dem Update lief es in dem alten Modulstand. Komme ich da wieder hin oder wäre der Weg nach vorne mit einem "sudo apt install python3.8" der bessere Weg.
Gruß
Ich empfehle eher gleich auf bullseye zu gehen, dort ist Python 3.9 Standard. Falls Ubuntu Python3.8 im Standard auch anbietet, kannst du es mal versuchen.
Zurück auf die alte Version würde ich nicht empfehlen. Tuya hat im Update ein paar Sachen geändert, könnte daher sein, dass es mit dem alten Modul irgendwann zu Problemen kommt.
@bewa58, tritt das Problem bei dir immer wieder bei Neustarts auf? Wenn ja, poste mir bitte nochmals den Fehler wenn es wieder auftritt. Laut Tuya Cloud Log das du gepostet hast, dürfte da ein "circular import" vorliegen.
Noch dazu...
Zitat2022-03-04 01:30:23,913 - INFO - tuya_cloud: create: Fluter_A1_41518006f4cfa25b52db PythonModule tuya_cloud tuya_cloud 41518006f4cfa25b52db
Devices werden nur neu angelegt, wenn diese nicht existieren. Bedeutet natürlich auch, dass wenn du ein Device löscht, es nach dem Neustart wieder angelegt wird.
Zitat
Devices werden nur neu angelegt, wenn diese nicht existieren. Bedeutet natürlich auch, dass wenn du ein Device löscht, es nach dem Neustart wieder angelegt wird.
Nein, die diese Meldung kommt auch wenn bereits angelegt !!!
um es zum Laufen zu bringen lösche alle und dann funktioniert es 1x
dann wieder das gleiche Spiel !
Ich dem englischen nicht so mächtig: was bedeutet "circular import"
ja, es kommt immer wieder vor, habe ich doch beschrieben.
warum habe ich kein logfile mehr ?
warum ist der fhempy_15.... nicht mehr in FHEM vorhanden.
Alleas seit dem crash heute morgen
Ok, bitte ein Thema nach dem anderen.
Verstehe ich richtig, dass fhempy_15733 nicht mehr in FHEM vorhanden ist? fhempy_local existiert aber? Wenn ja, dann mach bitte mal einen Neustart von FHEM.
ja fhempy_15733 nicht mehr vorhanden.
Neustart gemacht mit update vorher!
Alle Devices vorhanden ohne Fehlermeldung,
aber kein fhempy_15733
und kein fhempy log letzter Eintrag heute morgen vor crash
Bildschirmausdruck:
Zitat
ZX2832ZX2891 A1 on off
ZX2832ZX2891 A2 on off
FILELOG
fhempy_log
fhempy-2022-02-24.log text
fhempy-2022-02-25.log text
fhempy-2022-02-26.log text
fhempy-2022-02-27.log text
fhempy-2022-02-28.log text
fhempy-2022-03-01.log text
fhempy-2022-03-02.log text
fhempy-2022-03-03.log text
fhempy-2022-03-04.log text
fhempy-2022-03-05.log text
FHEMPY
local_pybinding
connected update finished...please wait
hier war der fhempy_15733 immer vorhanden
RING
ringDoorbell connected
TUYA_CLOUD
Fluter_A1 on off
Fluter_A2 on off
Fluter_A3 on off
Wassercomputer on off
ZX-5060 on off
ZX2832ZX2891 A1 on off
ZX2832ZX2891 A2 on off
ZigBee Gateway Lidl not support this device
tuya_cloud connected
Ok, dann mach einfach:
define fhempyserver_15733 fhempyServer
define fhempyserver_15733 fhempyServer
gemacht
ging online dann offline usw.
Neustart gemacht
jetzt
fhempyserver_15733 online
aber jetzt
local_pybinding
disconnected 0.1.260 update wird aber nicht ausgeführt, beim aufrufen
ich muss jetzt gleich Schluss machen, bin ab 02:00 Uhr wieder unterwegs.
bischen Schlaf muss sein
Bitte das fhempy Log posten
hier log von heute seit letztem eintrag vor crash
gelöscht
Leider ist es nicht komplett, poste bitte nur seit dem letzten Start - also wahrscheinlich so ab 22 Uhr.
gelöscht
Sieht eigentlich gut aus, was funktioniert nun nicht?
local binding disconnect immer noch
Zitatdefine fhempyserver_15733 fhempyServer
gemacht
ging online dann offline usw.
Neustart gemacht
jetzt
fhempyserver_15733 online
aber jetzt
local_pybinding
disconnected 0.1.260 update wird aber nicht ausgeführt, beim aufrufen
ich muss jetzt gleich Schluss machen, bin ab 02:00 Uhr wieder unterwegs.
bischen Schlaf muss sein
Zitat
BELEUCHT. AUSSEN STATISCH
ZX2832ZX2891 A1
fhempy server offline
ZX2832ZX2891 A2
fhempy server offline
FILELOG
fhempy_log
fhempy-2022-02-24.log
text
fhempy-2022-02-25.log
text
fhempy-2022-02-26.log
text
fhempy-2022-02-27.log
text
fhempy-2022-02-28.log
text
fhempy-2022-03-01.log
text
fhempy-2022-03-02.log
text
fhempy-2022-03-03.log
text
fhempy-2022-03-04.log
text
fhempy-2022-03-05.log
text
AT
atRestartFhempyServer
inactive
FHEMPY
fhempyserver_15733
running
local_pybinding
disconnected 0.1.260
RING
ringDoorbell
fhempy server offline
TUYA_CLOUD
Fluter_A1
fhempy server offline
Fluter_A2
fhempy server offline
Fluter_A3
fhempy server offline
Wassercomputer
fhempy server offline
ZX-5060
fhempy server offline
ZX2832ZX2891 A1
fhempy server offline
Kann es sein, dass du 2 BindingIo Devices hast?
Bitte häng hier das gesamte Log als File an, dann prüf noch ob du nicht 2 BindingIo Devices hast. Hast du eventuell 2 FHEM Instanzen?
Ich schau mir das morgen weiter an.
wie kann ich prüfen ob 2 bindings io devices vorhanden sind?
habe ich eben versucht das logfile anzuhängen, leider funktioniert das hier im forum
anscheinend nicht richtig,
auch die code tags wurden nicht ausgeführt obwohl in der vorschau ok.
ich muss auch schluss machen
ich sende dir das morgen früh, wenn es funktioniert
hier noch das log
nochmal neustart gemacht
jetzt läuft es (aber wie lange)
und jetzt wieder die fehlermeldungen
ZitatFHEMPY
fhempyserver_15733
running
local_pybinding
connected 0.1.260
RING
ringDoorbell
Failed to load module ring: Traceback (most recent call last): File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 268, in _onMessage module_object = await utils.run_blocking( File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/utils.py", line 34, in run_blocking return await asyncio.get_event_loop().run_in_executor(pool, function) File "/usr/lib/python3.9/concurrent/futures/thread.py", line 52, in run result = self.fn(*self.args, **self.kwargs) File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1030, in _gcd_import File "", line 1007, in _find_and_load File "", line 986, in _find_and_load_unlocked File "", line 680, in _load_unlocked File "", line 790, in exec_module File "", line 228, in _call_with_frames_removed File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/ring/ring.py", line 9, in from ring_doorbell import Auth, Ring File "/opt/fhem/.local/lib/python3.9/site-packages/ring_doorbell/__init__.py", line 15, in from .auth import Auth # noqa File "/opt/fhem/.local/lib/python3.9/site-packages/ring_doorbell/auth.py", line 5, in from requests_oauthlib import OAuth2Session File "/opt/fhem/.local/lib/python3.9/site-packages/requests_oauthlib/__init__.py", line 3, in from .oauth1_auth import OAuth1 File "/opt/fhem/.local/lib/python3.9/site-packages/requests_oauthlib/oauth1_auth.py", line 9, in from requests.compat import is_py3 File "", line 1007, in _find_and_load File "", line 989, in _find_and_load_unlocked KeyError: 'requests'
TUYA_CLOUD
Fluter_A1
Failed to load module tuya_cloud: Traceback (most recent call last): File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 268, in _onMessage module_object = await utils.run_blocking( File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/utils.py", line 34, in run_blocking return await asyncio.get_event_loop().run_in_executor(pool, function) File "/usr/lib/python3.9/concurrent/futures/thread.py", line 52, in run result = self.fn(*self.args, **self.kwargs) File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1030, in _gcd_import File "", line 1007, in _find_and_load File "", line 986, in _find_and_load_unlocked File "", line 680, in _load_unlocked File "", line 790, in exec_module File "", line 228, in _call_with_frames_removed File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya_cloud/tuya_cloud.py", line 7, in from fhempy.lib.tuya_cloud.tuya_cloud_device import tuya_cloud_device File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 5, in from tuya_iot.device import TuyaDevice File "/opt/fhem/.local/lib/python3.9/site-packages/tuya_iot/__init__.py", line 1, in from .asset import TuyaAssetManager File "/opt/fhem/.local/lib/python3.9/site-packages/tuya_iot/asset.py", line 6, in from .openapi import TuyaOpenAPI File "/opt/fhem/.local/lib/python3.9/site-packages/tuya_iot/openapi.py", line 10, in import requests File "/usr/lib/python3/dist-packages/requests/__init__.py", line 118, in from . import utils File "/usr/lib/python3/dist-packages/requests/utils.py", line 27, in from ._internal_utils import to_native_string File "/usr/lib/python3/dist-packages/requests/_internal_utils.py", line 11, in from .compat import is_py2, builtin_str, str ImportError: cannot import name 'builtin_str' from partially initialized module 'requests.compat' (most likely due to a circular import) (/usr/lib/python3/dist-packages/requests/compat.py)
Fluter_A2
Fluter_A3
Wassercomputer
ZX-5060
ZX2832ZX2891 A1
ZX2832ZX2891 A2
ZigBee Gateway Lidl
not support this device
tuya_cloud
connected
und der Rest vom Log:
gelöscht
hat die code tags wieder abgeschnitten
hier das log per 23:27 Uhr
gute nacht
Moinsen,
habe eben mal fhempy_server15733 neu gestartet ! 08:52 Uhr
FHEM lief bis dahin durch (seit gestern 23:00 Uhr)
und das Device Fluter_A1 war in FHEM vorhanden !!
Trotzdem erscheint im LOG Create Fluter_A1 (LOG anbei)
in rot Tuya_cloud doppelt?
Zitat
022-03-06 08:52:29,181 - INFO - tuya_cloud: create: Fluter_A1_41518006f4cfa25b52db PythonModule tuya_cloud tuya_cloud 41518006f4cfa25b52db
RingDoorbell Fehlermeldung nun weg
hier die Fehlermeldung von gestern
bei Neustart
Zitat
RING
ringDoorbell
Failed to load module ring: Traceback (most recent call last): File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 268, in _onMessage module_object = await utils.run_blocking( File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/utils.py", line 34, in run_blocking return await asyncio.get_event_loop().run_in_executor(pool, function) File "/usr/lib/python3.9/concurrent/futures/thread.py", line 52, in run result = self.fn(*self.args, **self.kwargs) File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1030, in _gcd_import File "", line 1007, in _find_and_load File "", line 986, in _find_and_load_unlocked File "", line 680, in _load_unlocked File "", line 790, in exec_module File "", line 228, in _call_with_frames_removed File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/ring/ring.py", line 9, in from ring_doorbell import Auth, Ring File "/opt/fhem/.local/lib/python3.9/site-packages/ring_doorbell/__init__.py", line 15, in from .auth import Auth # noqa File "/opt/fhem/.local/lib/python3.9/site-packages/ring_doorbell/auth.py", line 5, in from requests_oauthlib import OAuth2Session File "/opt/fhem/.local/lib/python3.9/site-packages/requests_oauthlib/__init__.py", line 3, in from .oauth1_auth import OAuth1 File "/opt/fhem/.local/lib/python3.9/site-packages/requests_oauthlib/oauth1_auth.py", line 9, in from requests.compat import is_py3 File "", line 1007, in _find_and_load File "", line 989, in _find_and_load_unlocked KeyError: 'requests'
Fluter_A1 Fehlermeldung wie folgt
Zitat
Failed to load module tuya_cloud: Traceback (most recent call last): File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 268, in _onMessage module_object = await utils.run_blocking( File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/utils.py", line 34, in run_blocking return await asyncio.get_event_loop().run_in_executor(pool, function) File "/usr/lib/python3.9/concurrent/futures/thread.py", line 52, in run result = self.fn(*self.args, **self.kwargs) File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1030, in _gcd_import File "", line 1007, in _find_and_load File "", line 986, in _find_and_load_unlocked File "", line 680, in _load_unlocked File "", line 790, in exec_module File "", line 228, in _call_with_frames_removed File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya_cloud/tuya_cloud.py", line 7, in from fhempy.lib.tuya_cloud.tuya_cloud_device import tuya_cloud_device File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 5, in from tuya_iot.device import TuyaDevice File "/opt/fhem/.local/lib/python3.9/site-packages/tuya_iot/__init__.py", line 1, in from .asset import TuyaAssetManager File "/opt/fhem/.local/lib/python3.9/site-packages/tuya_iot/asset.py", line 6, in from .openapi import TuyaOpenAPI File "/opt/fhem/.local/lib/python3.9/site-packages/tuya_iot/openapi.py", line 10, in import requests File "/usr/lib/python3/dist-packages/requests/__init__.py", line 118, in from . import utils File "/usr/lib/python3/dist-packages/requests/utils.py", line 27, in from ._internal_utils import to_native_string File "/usr/lib/python3/dist-packages/requests/_internal_utils.py", line 11, in from .compat import is_py2, builtin_str, str ImportError: cannot import name 'builtin_str' from partially initialized module 'requests.compat' (most likely due to a circular import) (/usr/lib/python3/dist-packages/requests/compat.py)
Hoffe damit kannst du was anfangen.
noch n Bildschirmcopy anbei !
Nachtrag: gerade Up-Date Check FHEM gemacht und wollte updaten
dann gesehen das local_bindung "wait update" anzeigt.
angeklickt und hat auf 264 aktualisiert
und
Fehlermeldungen alle weg !
Ich mach jetzt ein FHEM update und starte neu
local_binding steht nur auf wait update... wenn du draufdrückst damit es ein Update macht oder du in FHEM ein Update gestartet hast.
Ich hab mir das Log von gestern angesehen. Du hast 2x fhempy am Laufen gehabt, vielleicht manuell auch gestartet? Das sollte man auf der FHEM Instanz unterlassen. Irgendwann war das 2. fhempy dann weg und dann lief es ohne Probleme laut Log.
Bitte wenn die code Tags nicht funktionieren auch nachträglich das Log löschen, das kann hier sonst niemand mehr vernünftig lesen. Danke!
Ring Fehler bitte in den Ring Thread.
nach neustart jetzt
wieder alles beim alten
Server offline
local_binding war auf 260
dann update local binding jetzt auf 264
und läuft mit Fehlermeldung
Zitat
Failed to load module tuya_cloud: Traceback (most recent call last): File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 268, in _onMessage module_object = await utils.run_blocking( File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/utils.py", line 34, in run_blocking return await asyncio.get_event_loop().run_in_executor(pool, function) File "/usr/lib/python3.9/concurrent/futures/thread.py", line 52, in run result = self.fn(*self.args, **self.kwargs) File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1030, in _gcd_import File "", line 1007, in _find_and_load File "", line 986, in _find_and_load_unlocked File "", line 680, in _load_unlocked File "", line 790, in exec_module File "", line 228, in _call_with_frames_removed File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya_cloud/tuya_cloud.py", line 7, in from fhempy.lib.tuya_cloud.tuya_cloud_device import tuya_cloud_device File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 5, in from tuya_iot.device import TuyaDevice File "/opt/fhem/.local/lib/python3.9/site-packages/tuya_iot/__init__.py", line 1, in from .asset import TuyaAssetManager File "/opt/fhem/.local/lib/python3.9/site-packages/tuya_iot/asset.py", line 6, in from .openapi import TuyaOpenAPI File "/opt/fhem/.local/lib/python3.9/site-packages/tuya_iot/openapi.py", line 10, in import requests File "/usr/lib/python3/dist-packages/requests/__init__.py", line 118, in from . import utils File "/usr/lib/python3/dist-packages/requests/utils.py", line 27, in from ._internal_utils import to_native_string File "/usr/lib/python3/dist-packages/requests/_internal_utils.py", line 11, in from .compat import is_py2, builtin_str, str ImportError: cannot import name 'builtin_str' from partially initialized module 'requests.compat' (most likely due to a circular import) (/usr/lib/python3/dist-packages/requests/compat.py)
habe nichts per hand gestartet, weis gar nicht wie das funktioniert
ok, mach jetzt mal einen fhempy restart
set fhempyserver_15733 restart
gemacht!
Device Fluter_A1 wieder die Fehlermeldung
Zitat
Failed to load module tuya_cloud: Traceback (most recent call last): File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 268, in _onMessage module_object = await utils.run_blocking( File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/utils.py", line 34, in run_blocking return await asyncio.get_event_loop().run_in_executor(pool, function) File "/usr/lib/python3.9/concurrent/futures/thread.py", line 52, in run result = self.fn(*self.args, **self.kwargs) File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1030, in _gcd_import File "", line 1007, in _find_and_load File "", line 986, in _find_and_load_unlocked File "", line 680, in _load_unlocked File "", line 790, in exec_module File "", line 228, in _call_with_frames_removed File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya_cloud/tuya_cloud.py", line 7, in from fhempy.lib.tuya_cloud.tuya_cloud_device import tuya_cloud_device File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 5, in from tuya_iot.device import TuyaDevice File "/opt/fhem/.local/lib/python3.9/site-packages/tuya_iot/__init__.py", line 1, in from .asset import TuyaAssetManager File "/opt/fhem/.local/lib/python3.9/site-packages/tuya_iot/asset.py", line 6, in from .openapi import TuyaOpenAPI File "/opt/fhem/.local/lib/python3.9/site-packages/tuya_iot/openapi.py", line 10, in import requests File "/usr/lib/python3/dist-packages/requests/__init__.py", line 118, in from . import utils File "/usr/lib/python3/dist-packages/requests/utils.py", line 27, in from ._internal_utils import to_native_string File "/usr/lib/python3/dist-packages/requests/_internal_utils.py", line 11, in from .compat import is_py2, builtin_str, str ImportError: cannot import name 'builtin_str' from partially initialized module 'requests.compat' (most likely due to a circular import) (/usr/lib/python3/dist-packages/requests/compat.py)
melde mich jetzt erst mal bis 15:00 Uhr ab.
habe die Nacht wenig geschlafen und dann noch bis 8 Uhr gearbeitet.
Zitat von: dominik am 05 März 2022, 20:23:45
Ich empfehle eher gleich auf bullseye zu gehen, dort ist Python 3.9 Standard. Falls Ubuntu Python3.8 im Standard auch anbietet, kannst du es mal versuchen.
Zurück auf die alte Version würde ich nicht empfehlen. Tuya hat im Update ein paar Sachen geändert, könnte daher sein, dass es mit dem alten Modul irgendwann zu Problemen kommt.
Danke,
habe nach einem Backup python3.8 installiert. Läuft wieder!
apt-get install python3.8
apt-get install python3.8-dev
update-alternatives --install /usr/bin/python3 python3 /usr/bin/python3.8 2
pip3 install --upgrade pip
systemctl restart fhempy.service
Ubuntu 18.04.6 LTS
Gruß
Rene
Zitat von: bewa58 am 06 März 2022, 10:02:46
melde mich jetzt erst mal bis 15:00 Uhr ab.
habe die Nacht wenig geschlafen und dann noch bis 8 Uhr gearbeitet.
Gerade ein Update released, teste bitte mit 0.1.267.
Zitat
Gerade ein Update released, teste bitte mit 0.1.267.
funktioniert leider immer noch nicht !
nach Neustart FHEM oder kompletter Neustart (Raspi) erscheinen wieder die gleichen Fehlermeldungen!
Zitat2022-03-07 17:54:23,414 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2022-03-07 17:54:23,432 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2022-03-07 17:54:23,508 - INFO - websockets.server: server listening on 0.0.0.0:15733
2022-03-07 17:55:02,597 - INFO - websockets.server: connection open
2022-03-07 17:55:02,600 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
ZitatFailed to load module tuya_cloud: Traceback (most recent call last): File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 268, in _onMessage module_object = await utils.run_blocking( File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/utils.py", line 34, in run_blocking return await asyncio.get_event_loop().run_in_executor(pool, function) File "/usr/lib/python3.9/concurrent/futures/thread.py", line 52, in run result = self.fn(*self.args, **self.kwargs) File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1030, in _gcd_import File "", line 1007, in _find_and_load File "", line 986, in _find_and_load_unlocked File "", line 680, in _load_unlocked File "", line 790, in exec_module File "", line 228, in _call_with_frames_removed File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya_cloud/tuya_cloud.py", line 8, in from fhempy.lib.tuya_cloud.tuya_cloud_setup import tuya_cloud_setup File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 5, in from tuya_iot import ( File "/opt/fhem/.local/lib/python3.9/site-packages/tuya_iot/__init__.py", line 1, in from .asset import TuyaAssetManager File "/opt/fhem/.local/lib/python3.9/site-packages/tuya_iot/asset.py", line 6, in from .openapi import TuyaOpenAPI File "/opt/fhem/.local/lib/python3.9/site-packages/tuya_iot/openapi.py", line 10, in import requests File "/usr/lib/python3/dist-packages/requests/__init__.py", line 118, in from . import utils File "/usr/lib/python3/dist-packages/requests/utils.py", line 27, in from ._internal_utils import to_native_string File "/usr/lib/python3/dist-packages/requests/_internal_utils.py", line 11, in from .compat import is_py2, builtin_str, str ImportError: cannot import name 'builtin_str' from partially initialized module 'requests.compat' (most likely due to a circular import) (/usr/lib/python3/dist-packages/requests/compat.py)
was ich nun festgestellt habe:
wenn ich ca. 5 Minuten nach Neustart ein Update local-pybinding 267 auf 267 anstosse
sind die Fehlermeldungen nach dem Update verschwunden und es läuft alles.
UND: nach jedem Neustart FHEM oder auch kompletter Neustart (Raspi)
erscheint wieder die Meldung
Zitat
INFO - tuya_cloud: create: Fluter_A1_41518006f4cfa25b52db PythonModule tuya_cloud tuya_cloud 41518006f4cfa25b52db
Das Device "Fluter_A1" ist definitiv angelegt und nicht gelöscht worden !!
UND: fhempyserver_15733 "STOP" funktioniert nicht, wird sofort wieder gestartet
Wie gesagt, ein Thema nach dem anderen. Bitte daher mal Fokus auf den Start. Die anderen Logs sind vorerst nicht relevant.
Teste bitte mit 0.1.268.
Der Grund ist ein circular import Error. Bei einem Restart ist das manchmal weg, weil es tw. nur um wenige Millisekunden in denen der Import noch nicht fertig ist.
Zitat
Der Grund ist ein circular import Error
Update auf 268 gemacht
leider keine Besserung
genau wie bei 0.1.267
Noch eine Verständnisfrage:
- local_pybinding update angestossen
- neue Vers. wird angezeigt
-FHEM neu gestartet local_pybinding wird dann "alte" Version angezeigt, muss nochmals update fahren
-RASPI komplett Neustart wird die "neue" Version angezeigt.
Ist das so korrekt?
Nein, das ist nicht korrekt.
Kannst du es reproduzieren? Bitte auch noch das Log vom Fehler.
hmm, nachdem dein super Support den Wirelss Switch zum laufen gebracht hat mag nun das Tuya Gateway nach einem Neustart plötzlich nicht mehr, alles löschen und neu anlegen funktioniert nur bis zum Neustart. Ich hoffe da ist etwas dabei was dir zur Lösung hilft.
setstate fhempy_local opened
setstate fhempy_local 2022-03-09 00:20:57 hostname ubuntu
setstate fhempy_local 2022-03-09 00:20:57 os posix
setstate fhempy_local 2022-03-09 00:20:57 python 3.8.10
setstate fhempy_local 2022-03-09 00:20:57 release 5.4.0-104-generic
setstate fhempy_local 2022-03-09 00:20:57 state opened
setstate fhempy_local 2022-03-09 00:20:57 system Linux
setstate fhempy_local 2022-03-09 00:20:57 version 0.1.268
Failed to load module tuya_cloud: Traceback (most recent call last): File "/home/fhem/.local/lib/python3.8/site-packages/fhempy/lib/fhem_pythonbinding.py", line 268, in _onMessage module_object = await utils.run_blocking( File "/home/fhem/.local/lib/python3.8/site-packages/fhempy/lib/utils.py", line 34, in run_blocking return await asyncio.get_event_loop().run_in_executor(pool, function) File "/usr/lib/python3.8/concurrent/futures/thread.py", line 57, in run result = self.fn(*self.args, **self.kwargs) File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1014, in _gcd_import File "", line 991, in _find_and_load File "", line 975, in _find_and_load_unlocked File "", line 671, in _load_unlocked File "", line 848, in exec_module File "", line 219, in _call_with_frames_removed File "/home/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud.py", line 8, in from fhempy.lib.tuya_cloud.tuya_cloud_setup import tuya_cloud_setup File "/home/fhem/.local/lib/python3.8/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 5, in import tuya_iot File "/home/fhem/.local/lib/python3.8/site-packages/tuya_iot/__init__.py", line 1, in from .asset import TuyaAssetManager File "/home/fhem/.local/lib/python3.8/site-packages/tuya_iot/asset.py", line 6, in from .openapi import TuyaOpenAPI File "/home/fhem/.local/lib/python3.8/site-packages/tuya_iot/openapi.py", line 10, in import requests File "/home/fhem/.local/lib/python3.8/site-packages/requests/__init__.py", line 135, in from .models import Request, Response, PreparedRequest File "/home/fhem/.local/lib/python3.8/site-packages/requests/models.py", line 28, in from .auth import HTTPBasicAuth File "/home/fhem/.local/lib/python3.8/site-packages/requests/auth.py", line 22, in from .utils import parse_dict_header ImportError: cannot import name 'parse_dict_header' from partially initialized module 'requests.utils' (most likely due to a circular import) (/home/fhem/.local/lib/python3.8/site-packages/requests/utils.py)
2022-03-09 00:01:54,972 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2022-03-09 00:01:54,981 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2022-03-09 00:01:55,045 - INFO - websockets.server: server listening on 0.0.0.0:15733
2022-03-09 00:01:59,046 - INFO - websockets.server: connection open
2022-03-09 00:01:59,047 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2022-03-09 00:01:59,707 - WARNING - asyncio: Executing <Task pending name='Task-33' coro=<ring.ring_login() running at /home/fhem/.local/lib/python3.8/site-packages/fhempy/lib/ring/ring.py:96> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x7fb31ace5520>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> created at /usr/lib/python3.8/asyncio/tasks.py:382> took 0.141 seconds
2022-03-09 00:02:00,471 - ERROR - RingDoorBell: Failed to update devices
Traceback (most recent call last):
File "/home/fhem/.local/lib/python3.8/site-packages/ring_doorbell/auth.py", line 94, in query
req = getattr(self._oauth, method.lower())(url, **kwargs)
File "/home/fhem/.local/lib/python3.8/site-packages/requests/sessions.py", line 577, in post
return self.request('POST', url, data=data, json=json, **kwargs)
File "/home/fhem/.local/lib/python3.8/site-packages/requests_oauthlib/oauth2_session.py", line 477, in request
url, headers, data = self._client.add_token(
File "/usr/lib/python3/dist-packages/oauthlib/oauth2/rfc6749/clients/base.py", line 198, in add_token
raise TokenExpiredError()
oauthlib.oauth2.rfc6749.errors.TokenExpiredError: (token_expired)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/fhem/.local/lib/python3.8/site-packages/fhempy/lib/ring/ring.py", line 117, in update_loop
await utils.run_blocking(functools.partial(self._ring.update_data))
File "/home/fhem/.local/lib/python3.8/site-packages/fhempy/lib/utils.py", line 34, in run_blocking
return await asyncio.get_event_loop().run_in_executor(pool, function)
File "/usr/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/home/fhem/.local/lib/python3.8/site-packages/ring_doorbell/__init__.py", line 52, in update_data
self.create_session()
File "/home/fhem/.local/lib/python3.8/site-packages/ring_doorbell/__init__.py", line 65, in create_session
self.session = self.query(
File "/home/fhem/.local/lib/python3.8/site-packages/ring_doorbell/__init__.py", line 107, in query
return self.auth.query(
File "/home/fhem/.local/lib/python3.8/site-packages/ring_doorbell/auth.py", line 96, in query
self._oauth.token = self.refresh_tokens()
File "/home/fhem/.local/lib/python3.8/site-packages/ring_doorbell/auth.py", line 56, in refresh_tokens
token = self._oauth.refresh_token(
File "/home/fhem/.local/lib/python3.8/site-packages/requests_oauthlib/oauth2_session.py", line 446, in refresh_token
self.token = self._client.parse_request_body_response(r.text, scope=self.scope)
File "/usr/lib/python3/dist-packages/oauthlib/oauth2/rfc6749/clients/base.py", line 421, in parse_request_body_response
self.token = parse_token_response(body, scope=scope)
File "/usr/lib/python3/dist-packages/oauthlib/oauth2/rfc6749/parameters.py", line 431, in parse_token_response
validate_token_parameters(params)
File "/usr/lib/python3/dist-packages/oauthlib/oauth2/rfc6749/parameters.py", line 438, in validate_token_parameters
raise_from_error(params.get('error'), params)
File "/usr/lib/python3/dist-packages/oauthlib/oauth2/rfc6749/errors.py", line 405, in raise_from_error
raise cls(**kwargs)
oauthlib.oauth2.rfc6749.errors.InvalidGrantError: (invalid_grant) token is invalid or does not exists
2022-03-09 00:03:51,413 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2022-03-09 00:03:51,429 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2022-03-09 00:03:51,491 - INFO - websockets.server: server listening on 0.0.0.0:15733
2022-03-09 00:03:55,955 - INFO - websockets.server: connection open
2022-03-09 00:03:55,956 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2022-03-09 00:04:49,547 - INFO - fhempy.lib.pkg_installer: Attempting install of fhempy
2022-03-09 00:04:52,110 - INFO - fhempy.lib.pkg_installer: Successfully installed fhempy update!
2022-03-09 00:04:52,501 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2022-03-09 00:04:52,509 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2022-03-09 00:04:52,532 - INFO - websockets.server: server listening on 0.0.0.0:15733
2022-03-09 00:05:03,013 - INFO - websockets.server: connection open
2022-03-09 00:05:03,015 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2022-03-09 00:07:53,410 - WARNING - asyncio: Executing <Task pending name='Task-587' coro=<ring.ring_login() running at /home/fhem/.local/lib/python3.8/site-packages/fhempy/lib/ring/ring.py:110> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x7f5bd414c0d0>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> created at /usr/lib/python3.8/asyncio/tasks.py:382> took 0.307 seconds
2022-03-09 00:07:54,352 - WARNING - ring_doorbell.doorbot: Your Ring account does not have an active subscription.
2022-03-09 00:07:54,859 - WARNING - asyncio: Executing <Task pending name='Task-587' coro=<ring.ring_login() running at /home/fhem/.local/lib/python3.8/site-packages/fhempy/lib/ring/ring.py:110> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x7f5bd6910e20>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> created at /usr/lib/python3.8/asyncio/tasks.py:382> took 0.430 seconds
2022-03-09 00:12:56,681 - WARNING - ring_doorbell.doorbot: Your Ring account does not have an active subscription.
2022-03-09 00:13:03,506 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2022-03-09 00:13:03,531 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2022-03-09 00:13:03,576 - INFO - websockets.server: server listening on 0.0.0.0:15733
2022-03-09 00:13:07,942 - INFO - websockets.server: connection open
2022-03-09 00:13:07,943 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2022-03-09 00:13:10,261 - WARNING - asyncio: Executing <Task pending name='Task-108' coro=<ring.ring_login() running at /home/fhem/.local/lib/python3.8/site-packages/fhempy/lib/ring/ring.py:110> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x7fe473fd18e0>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> created at /usr/lib/python3.8/asyncio/tasks.py:382> took 0.308 seconds
2022-03-09 00:13:11,196 - WARNING - ring_doorbell.doorbot: Your Ring account does not have an active subscription.
2022-03-09 00:13:11,601 - WARNING - asyncio: Executing <Task pending name='Task-108' coro=<ring.ring_login() running at /home/fhem/.local/lib/python3.8/site-packages/fhempy/lib/ring/ring.py:110> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x7fe4736acee0>()] created at /usr/lib/python3.8/asyncio/base_events.py:422> created at /usr/lib/python3.8/asyncio/tasks.py:382> took 0.324 seconds
2022-03-09 00:17:15,025 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2022-03-09 00:17:15,035 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2022-03-09 00:17:15,069 - INFO - websockets.server: server listening on 0.0.0.0:15733
2022-03-09 00:20:52,650 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2022-03-09 00:20:52,667 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2022-03-09 00:20:52,718 - INFO - websockets.server: server listening on 0.0.0.0:15733
2022-03-09 00:20:57,159 - INFO - websockets.server: connection open
2022-03-09 00:20:57,160 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
@MiKn
habe dieses Problem schon länger und Dominik ist dran das Problem zu lösen
.
Was bei mir zwischenzeitlich hilft:
Nach Neustart FHEM, wenn die Fehlermeldungen auftauchen, ca. 5-6 Minuten warten
dann local_Pybindung update anstoßen (auch wenn schon neueste Version).
Dann verschwinden bei mir die Fehlermeldungen komplett (auch bei Ring)
Ihr müsst wahrscheinlich kein Update machen, sondern einfach einen Restart von fhempyServer.
Danke für das Log, ich schau mal weiter.
Bitte mal 0.1.269 testen und Log posten.
update gemacht. Ring und ein Tuya Aktor wieder weg. Restart von fhempyserver_15733 ändert nichts.
Klappt es hier womöglich auch mit requests 2.26.0?
Zitat von: dominik am 09 März 2022, 23:23:11
Klappt es hier womöglich auch mit requests 2.26.0?
ja, wie von dir empfohlen geht es aktuell mit requests 2.26.0.
https://forum.fhem.de/index.php/topic,117381.msg1212787.html#msg1212787 (https://forum.fhem.de/index.php/topic,117381.msg1212787.html#msg1212787)
Sehr gut!
Ich hab die Version 2.26.0 bei der Package Installation fix gesetzt. Das bedeutet, wenn du nun ein Update machst, sollte es auch weiterhin laufen.
Zitat von: dominik am 09 März 2022, 23:30:31
Sehr gut!
Ich hab die Version 2.26.0 bei der Package Installation fix gesetzt. Das bedeutet, wenn du nun ein Update machst, sollte es auch weiterhin laufen.
Hi,
also nach ein paar Tagen inklusive update auf 0.1.270, fhem update, neustarts etc läuft alles wieder prima :D top!
Zitat von: thburkhart am 10 Januar 2022, 16:52:35
im Oktober 21 sind wir auf die Problematik gestoßen, dass zwar Power etc. bei GOSUND Steckdosen zwar Power etc. als reading zur Verfügung stehen ;
nicht jedoch die Verbrauchswerte.
In der TuyaCloud und der SmartLife App sind sie ja vorhanden.
Die war eigentlich der Hauptzweck.
Hat sich da TUYA-seitig was getan ?
Freue mich auf gute Nachrichten.
Herzliche Grüße
Thomas
Hallo Dominic,
gibt es da was Neues?
Herzliche Grüße
Thomas
Zitat von: dominik am 26 Dezember 2021, 10:41:46
Sorry, war von mir unklar ausgedrückt. Genau, ich meinte die tuya-iot-py-sdk Library.
Ich habe gerade ein fhempy update released (0.1.189), teste bitte damit.
ACHTUNG: Release 0.1.189 erfordert Python>3.7!!
Hallo Dominik,
nach dem Update im Januar lief bei mir Tuya nicht mehr. Ich habe mein FHEM eben ohne Tuya auf nem 3B unter Buster weiterlaufen lassen und wollte auf eine RASPI 4B warten.
Dieser war nicht ja nicht zu bekommen. Vorgestern ist mein 3B nun abgeraucht und ich habe auf einem 2B nun ein SD-Backup von Anfang Januar eingespielt; ebenso die gesicherte FHEM config vom vergangenen Donnerstag.
Und siehe da :-) alles läuft prima, mySQL und Tuya :-)
allerdings traue ich mich nicht ein FHEM Update zu machen:
... rest of lines skipped.
Downloading https://raw.githubusercontent.com/dominikkarall/fhempy/master/controls_pythonbinding.txt
pythonbinding
List of new / modified files since last update:
UPD FHEM/10_PythonModule.pm
UPD FHEM/10_fhempy.pm
UPD FHEM/10_PythonBinding.pm
UPD FHEM/10_fhempyServer.pm
UPD FHEM/10_BindingsIo.pm
UPD FHEM/bindings/python/bin/fhempy
New entries in the CHANGED file:
See https://github.com/dominikkarall/fhempy/releases for details
Hier im Thread habe ich allerdings gesehen, dass einiges gefixt wurde.
Kann ich das FHEM-Updade gefahrlos machen?
Herzliche Grüße
Thomas
Aus anderen Gründen musste
ja es leider so ..
nach FHEM Update hat sich das wieder "verschlimmbessert":
Failed to load module tuya_cloud: Traceback (most recent call last): File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/fhem_pythonbinding.py", line 269, in _onMessage functools.partial(importlib.import_module, pymodule) File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/utils.py", line 34, in run_blocking return await asyncio.get_event_loop().run_in_executor(pool, function) File "/usr/lib/python3.7/concurrent/futures/thread.py", line 57, in run result = self.fn(*self.args, **self.kwargs) File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1006, in _gcd_import File "", line 983, in _find_and_load File "", line 967, in _find_and_load_unlocked File "", line 677, in _load_unlocked File "", line 728, in exec_module File "", line 219, in _call_with_frames_removed File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud.py", line 8, in import fhempy.lib.tuya_cloud.tuya_cloud_setup as tcs File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 5, in import tuya_iot File "/opt/fhem/.local/lib/python3.7/site-packages/tuya_iot/__init__.py", line 2, in from .device import TuyaDevice, TuyaDeviceListener, TuyaDeviceManager File "/opt/fhem/.local/lib/python3.7/site-packages/tuya_iot/device.py", line 7, in from typing import Any, Literal, Optional ImportError: cannot import name 'Literal' from 'typing' (/usr/lib/python3.7/typing.py)
ich habe doch wohl Python 3.7
Ich bitte um Hilfe
Hi,
ja, du benötigst leider weiterhin Python 3.8 oder höher. Mach ein Update auf bullseye, dann klappt es.
hallo.
sieht man in den readings den gesamtverbrauch auch? oder bin ich blind?
komme leider mit app nicht mehr zu meinen steckdosen.
Nein, sieht man leider nicht. Bisher hat diese Schnittstelle von tuya bei mir noch nicht funktioniert, wo man diese Daten abfragen kann.
Abhilfe schaffen kann man vermutlich mit dem statistics Modul und dann add_ele oder current_power "zusammen zaehlen". Hab es selbst nicht probiert.
Hallo,
nachdem ich vergeblich versucht habe, meine Alarmanlage lokal über fhempy zu verbinden, habe ich jetzt die Option über die Cloud versucht.
Da ich Buster auf dem Raspi habe, hab' ich zuerst die Python Version auf 3.8.13 upgedatet und danach nach Anleitung
sudo apt install python3 python3-pip python3-dev libffi-dev libssl-dev libjpeg-dev zlib1g-dev autoconf build-essential libglib2.0-dev libdbus-1-dev bluez libbluetooth-dev git
sudo cpan Protocol::WebSocket
....in FHEM:
update add https://raw.githubusercontent.com/dominikkarall/fhempy/master/controls_pythonbinding.txt (war schon drin)
update
define fhempy_local BindingsIo fhempy
Leider funktionierts nicht. fhempy_local startet nicht (fhempy_server hat aber einen grünen Punkt)
Im Log sind viele Fehler...
Liegt es an meiner manuellen Installation von Python 3.8.13 oder was läuft hier falsch?
Vielen Dank für die Hilfe im Voraus.
ich folgte dem Rat von dominic und bin auf Bullseye umgestiegen
Dabei habe ich den RASPI neu aufgesetzt.
Das Upgrade von Buster wird ja nicht empfohlen und hat bei mir 5 Stunden gedauert; war dann immer noch nicht brauchbar
dann fhempi nach Anleitung von dominik neu installieren.
erster Start dauert einige minuten; shutdown restart nicht vergessen
Läuft nun wie geschmiert
ich habe nun ein neues Thema zu Tuya-Cloud
nachdem ich heute die Email erhielt:
Tuya IoT Platform Service Expiration Notice
Dear Tuya IoT Platform Account Manager,
The service Authorization you subscribed to will expire on 2022-05-03,If you need to continue to use,please renew this service.
How to renew your contract:
Please check the services you subscribe to and select the corresponding expired / expiring services to renew:
[url]www.tuya.com/vas/user/service[/url]
You have received this email because you are the account owner of the Tuya IoT platform and you have the right to know the changes of service information on the platform. If you do not use the above services in a business environment，you can ignore this email notification.
If the above instructions cannot conduct through the relevant operation, please contact your business manager or submit a help ticket on the Tuya IoT Platform.
This email is automatically sent by the system. Please do not reply. If you have any questions, please contact customer service.Contact: service@tuya.com
Sincerely,
dem Link folgend kann ich beim Service nur Billings einsehen aber nicht renewen
Was muss ich genauer machen ?
Herzliche Grüße
Thomas
Zitat von: thburkhart am 18 April 2022, 10:58:51
ich folgte dem Rat von dominic und bin auf Bullseye umgestiegen
Dabei habe ich den RASPI neu aufgesetzt.
Das Upgrade von Buster wird ja nicht empfohlen und hat bei mir 5 Stunden gedauert; war dann immer noch nicht brauchbar
dann fhempi nach Anleitung von dominik neu installieren.
erster Start dauert einige minuten; shutdown restart nicht vergessen
Läuft nun wie geschmiert
Gibt's keine andere Option?
Ich hab' soviel gemacht am System, das möchte ich ungern alles wieder neu machen...
Gruß Rainer
Kurz und knapp...ja, es liegt an der manuellen Installation.
Ich empfehle Bullseye zu installieren, das macht dir weniger Kopfzerbrechen als sich jetzt Schritt für Schritt von einem Fehler zum nächsten zu hanteln.
No permissions. This project is not authorized to call this API.
Seit ein paar Tagen habe ich diese Meldung. In der Tuya Devel Console steht:
My Cloud Projects ---> Upgrade IoT Core Plan
Kostet dann schlappe 25.000$. Muss man nach Ablauf der Trials ein neues Project anlegen? Oder wie löst man das?
Danke. Gesund bleiben!
Edit: Lösung: Die Service API IOT Core hinzufügen, ohne sie zu kaufen (?). Siehe Anhang. Geht wieder.
Nachdem für mich die Tuya Cloud leider immer wieder Probleme bei der Stabilität macht, da keine Updates bei Statusänderungen geschickt werden, habe ich an der lokalen Integration weiter gearbeitet.
In der neuen Version erhält man nun auch in der lokalen Versionen sofort Updates und kann die Geräte komplett lokal steuern. Die Anleitung dazu hier:
https://forum.fhem.de/index.php/topic,127441.0.html
Bitte weitere Fragen zur lokalen Integration im verlinkten Thread stellen. Hier geht es weiter nur mit Tuya Cloud.
Hallo Dominik,
soll die lokale Version komplett die Cloud-Version ersetzen?
Das wäre erstrebenswert, da die Trials in der Cloud nur noch monatlich erneuert werden können.
Und obwohl ich das gemacht habe, kommt immer noch:
Dear Tuya IoT Platform Account Manager,
The service Authorization you subscribed to will expire on 2022-05-03,If you need to continue to use,please renew this service.
How to renew your contract:
Please check the services you subscribe to and select the corresponding expired / expiring services to renew:
www.tuya.com/vas/user/service
Ich bin da wohl zu blöd...
Es wird weiterhin beide Versionen geben, sowohl Cloud, als auch lokal.
Mit der lokalen Version geht nämlich kein ZigBee, das geht nur über die Cloud. Für ZigBee sollte man Zigbee2mqtt nehmen, dazu gibt es auch fhempy Modul.
ich habe seit einigen Wochen einen paradoxen Effekt bei der SmartLifeApp:
wenn ich mich mich mich im heimischen Wlan befinde; also dasselbe WLAN, in dem die 80 Tuyas eingemeldet sind, erhalte ich keinen Zugriff auf diese über die SmartLife App.
Sobald ich das WLAN abschalte, also über 4G verbunden bin, geht alles blitzschnell. Hat jemand eine Erklärung für dies paradoxe Verhalten?
Ich habe eine Fritzbox 6591.
Das passiert, wenn eine lokale Verbindung zum Device besteht. Die Devices können nur maximal eine Verbindung akzeptieren. Hast du vielleicht noch irgendwas anderes laufen was auf deine Devices zugreift?
Zitat von: dominik am 26 April 2022, 19:17:13
Nachdem für mich die Tuya Cloud leider immer wieder Probleme bei der Stabilität macht, da keine Updates bei Statusänderungen geschickt werden, habe ich an der lokalen Integration weiter gearbeitet.
In der neuen Version erhält man nun auch in der lokalen Versionen sofort Updates und kann die Geräte komplett lokal steuern. Die Anleitung dazu hier:
https://forum.fhem.de/index.php/topic,127441.0.html
Bitte weitere Fragen zur lokalen Integration im verlinkten Thread stellen. Hier geht es weiter nur mit Tuya Cloud.
also bei mir klappts bestens. was sind die neuen probleme?
Bei mir hat's jetzt auch wieder geklappt, hatte nur immer wieder Mal das Thema, dass keine Updates (Status Änderungen) von der Cloud gepusht wurden.
Also keine Sorgen, man muss nicht wechseln, dieses Modul bleibt auch bestehen, da es auch alle Devices (inkl. ZigBee) unterstützt.
bitte schreibt doch nochmals für dummies, wie genauer und welche services im Tuya-Account als Trial erneuert werden müssen
Du brauchst
- IoT Core
- Authorization
- Device Status Notification
Das sollte ausreichend sein.
hmm
ich sehe zwar den Service und dass er am 3.5.22 abläuft
siehe PIC
aber wo ist das "renew"?
Der ist noch bis 3.5. aktiv, daher gibt es noch kein renew.
Zitat von: dominik am 01 Mai 2022, 11:26:17
Du brauchst
- IoT Core
- Authorization
- Device Status Notification
Das sollte ausreichend sein.
IoT Core konnte ich nur bis heute (1 Monat trial) verlängern.
Heute sagt man mir, dass man nur 1 mal ein trial kaufen könne.
Was tun, wenn ich 25000$ nicht bezahlen möchte?
Zitat von: fhem@supergut am 20 April 2022, 08:29:39
No permissions. This project is not authorized to call this API.
Seit ein paar Tagen habe ich diese Meldung. In der Tuya Devel Console steht:
My Cloud Projects ---> Upgrade IoT Core Plan
Kostet dann schlappe 25.000$. Muss man nach Ablauf der Trials ein neues Project anlegen? Oder wie löst man das?
Danke. Gesund bleiben!
Edit: Lösung: Die Service API IOT Core hinzufügen, ohne sie zu kaufen (?). Siehe Anhang. Geht wieder.
wie kann man ohne kaufen hinzufügen ?
den Anhang kann ich nicht zuordnen
danke für Hilfe
Falls du Tuya für WiFi Devices nutzt, dann empfehle ich auf das local tuya Modul umzusteigen. Bei Zigbee Geräten wirst du vermutlich um Zigbee2MQTT nicht herum kommen, das geht aber mit fhempy auch schnell installieren. Sonoff Zigbee USB Plus 3.0 kann ich empfehlen und funktioniert mit Zigbee2MQTT hervorragend. Wenn man auch ohne Herstellerapp leben kann, ist Z2M wirklich ein Traum.
Zitat von: dominik am 01 Juni 2022, 22:08:23
Falls du Tuya für WiFi Devices nutzt, dann empfehle ich auf das local tuya Modul umzusteigen..
brauch man beim local tuya Modul nicht dieselbe Registrierung in der Tuya-Cloud?
Falls du die local Keys schon hast, kannst du auch damit arbeiten.
https://github.com/dominikkarall/fhempy/blob/master/FHEM/bindings/python/fhempy/lib/tuya/README.md#individual-device
Bei local Tuya wird nur einmalig eine Abfrage gemacht, damit man das Mapping der Datapoints hat, danach wird die Cloud nicht mehr gebraucht.
Moin,
heute habe ich von Cloud auf local umgestellt. Einige Geräte konnte ich einbinden. Bei anderen kommt:
Specify IP address in define instead of offline
Brauche Hilfe..
Gruß
Jürgen K.
Edit: Nach einem shutdown restart werden keine Geräte erkannt..
Du musst das define nachträglich anpassen und statt offline die statische IP des Gerätes eintragen.
Danach fhempy restart.
Danke! Wer lesen kann.. Läuft jetzt.
Zitat von: juergen012 am 04 Juni 2022, 12:40:49
Moin,
heute habe ich von Cloud auf local umgestellt. Einige Geräte konnte ich einbinden. Bei anderen kommt:
Specify IP address in define instead of offline
Brauche Hilfe..
Gruß
Jürgen K.
Edit: Nach einem shutdown restart werden keine Geräte erkannt..
Bei mir auch, 1 Gerät wird erkannt,das erst angelegte, der Rest nicht.
Zitat von: satprofi am 05 Juni 2022, 07:49:30
Bei mir auch, 1 Gerät wird erkannt,das erst angelegte, der Rest nicht.
Mit statischer IP klappt es aber, oder?
erstklassiges Modul :)
allerdings stelle ich gerade fest das anscheinend die Werte der Readings
cur_power sollte W
cur_voltage sollte V
um den factor 10 zu hoch angegeben werden.
Bei mir z.B. 2524.0 für cur_power und 2387.0 cur_voltage. Ist das so gewollt ?
Edit: huch kann ja keiner was mit anfangen mit den Angaben ;-)
konkret geht es um die EP2 Steckdosen von Gosund und es handelt sich um die Werte der Leistungsmessung. Funktion ist einwandfrei, nur die Werte sind halt um oben genannte Faktoren verschoben.
Ich habe mit der Erweiterung mein Smart Meter erfolgreich ins FHEM gebracht.
Wie ist das nun mit dem Tuya Developer Account? Ist das nur ein kostenloser Testzeitraum oder bleibt die Verlinkung der Cloud
mit FHEM dauerrhaft bestehen?
Zitat von: kleinerDrache am 05 Juni 2022, 15:59:14
erstklassiges Modul :)
allerdings stelle ich gerade fest das anscheinend die Werte der Readings
cur_power sollte W
cur_voltage sollte V
um den factor 10 zu hoch angegeben werden.
Bei mir z.B. 2524.0 für cur_power und 2387.0 cur_voltage. Ist das so gewollt ?
Edit: huch kann ja keiner was mit anfangen mit den Angaben ;-)
konkret geht es um die EP2 Steckdosen von Gosund und es handelt sich um die Werte der Leistungsmessung. Funktion ist einwandfrei, nur die Werte sind halt um oben genannte Faktoren verschoben.
Hi,
bitte dazu bei TuYa ein Issue anlegen, dass die Werte über die API mit Faktor 10 falsch sind. Das müssen leider die korrigieren. In der Zwischenzeit kannst du userReadings anlegen.
Zitat von: Konfusius am 17 Juli 2022, 10:20:56
Ich habe mit der Erweiterung mein Smart Meter erfolgreich ins FHEM gebracht.
Wie ist das nun mit dem Tuya Developer Account? Ist das nur ein kostenloser Testzeitraum oder bleibt die Verlinkung der Cloud
mit FHEM dauerrhaft bestehen?
Wenn es ein WiFi Device ist, empfehle ich fhempy TuYa (local). Dann gibt es da keine Probleme. Ich weiß leider auch noch nicht wie es TuYa handhaben wird.
siehe fhempy_local
Danke, das stehts alles...
Hi,
ich habe solche Antela Smart Steckdosen, die auch den Stromverbrauch messen können. Leider bekomme ich dazu keine Readings in FHEM, obwohl in der Tuya App alles da ist.
Liegt das an irgendeiner Konfiguration, die ich falsch eingerichtet habe, oder liegt das irgendwo bei Tuya, die diese Readings einfach nicht weitergeben?
Hat jemand einen Tipp, wie man das zum Laufen bringt?
Verwendest du das tuya_cloud Modul oder tuya? Poste mal ein list vom Device. Bitte API KEY/SECRET unkenntlich machen.
Anbei das list, hoffe das hilft. Im Moment ist fhempy bei mir down, irgendwie läuft ein Update - aber das geht schon 2h, da scheint irgendwas kaputt gegangen zu sein. Das ist aber ein anderes Problem. Vorher lief fhempty.
Internals:
DEF tuya_cloud tuya_cloud_connector XXX
FHEMPYTYPE tuya_cloud
FUUID XXX
FVERSION 10_fhempy.pm:0.182830/2019-01-16
IODev fhempy_local
NAME StromTV_XXX
NR 87
PYTHONTYPE tuya_cloud
STATE fhempy server offline
TYPE fhempy
eventCount 1
READINGS:
2022-09-10 17:31:14 active_time 1652379870
2022-09-10 17:31:14 biz_type 18
2022-09-10 17:31:14 category cz
2022-09-10 17:31:14 create_time 1652379870
2022-09-10 17:31:14 icon https://images.tuyaeu.com/smart/icon/bay1603247053327gtRW/f0615f7985374fe0bb0504e3f34bfb42.png
2022-09-10 17:31:14 id XXX
2022-09-10 17:31:14 ip XXX
2022-09-10 17:31:14 lat XXX
2022-09-10 17:31:14 local_key XXX
2022-09-10 17:31:14 lon 8.5305
2022-09-10 17:31:14 model F1s202-EU
2022-09-10 17:31:14 name StromTV
2022-09-10 17:31:14 online on
2022-09-10 17:31:14 owner_id XX
2022-09-10 17:31:14 product_id XXX
2022-09-10 17:31:14 product_name Antela Smart Plug
2022-09-10 21:03:31 state fhempy server offline
2022-09-10 17:31:14 sub off
2022-09-10 17:31:14 time_zone +02:00
2022-09-10 17:31:14 uid XXX
2022-09-10 17:31:14 update_time 1652454993
2022-09-10 17:31:14 uuid XXX
args:
StromTV_XXX
fhempy
tuya_cloud
tuya_cloud_connector
XXX
argsh:
Attributes:
DbLogExclude .*
alias StromTV
group tuya_cloud
room 1.1_Wohnzimmer,2.3_Tuya,fhempy
on/off funktioniert darüber? Wenn ja, dann liefert tuya wahrscheinlich die Werte nicht über die Cloud.
Du kannst versuchen direkt lokal das Device zu verwenden. Geht mit dem tuya (nicht tuya_cloud) Modul. Zuerst aber das aktuell erstellte Device löschen.
Wegen hängendem fhempy Update:
- fhempyServer_15733 restart machen
on/off etc funktioniert problemlos.
Ich werde jetzt mal tuya lokal probieren. Aber irgendwie stimmt mit dem fhempy Server was nicht. fhempy_local und fhempy Server sind "grün", aber "fhempy server offline" kommt trotzdem bei tuya_system. Komisch.
Auch nach einem fhempyServer Neustart?
Ja, ich habe inzwischen alles neu gestartet, aber kein Effekt.
Schau mal im fhempy.log was drin steht, vielleicht sieht man dort einen Fehler.
hier der Auszug aus dem fhempy Log:
hier der Beginn des Logs und scheinbar der Zeitpunkt des Updates. Der Task pending name='Task-1' Teil wiederholt sich dann erstmal endlos.
2022-09-10 17:31:00,634 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2022-09-10 17:31:00,684 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2022-09-10 17:31:00,898 - WARNING - asyncio: Executing <Task pending name='Task-1' coro=<async_main() running at /opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py:498> wait_for=<_GatheringFuture pending cb=[<TaskWakeupMethWr$
2022-09-10 17:31:00,903 - INFO - websockets.server: server listening on 0.0.0.0:15733
2022-09-10 17:31:02,687 - INFO - websockets.server: connection open
2022-09-10 17:31:02,694 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2022-09-10 17:31:02,790 - WARNING - asyncio: Executing <Task pending name='Task-4' coro=<WebSocketServerProtocol.handler() running at /opt/fhem/.local/lib/python3.9/site-packages/websockets/legacy/server.py:224> wait_for=<Future pending cb=[<TaskWakeup$
2022-09-10 17:31:03,509 - WARNING - asyncio: Executing <Task pending name='Task-4' coro=<WebSocketServerProtocol.handler() running at /opt/fhem/.local/lib/python3.9/site-packages/websockets/legacy/server.py:224> wait_for=<Future pending cb=[<TaskWakeup$
2022-09-10 17:31:11,914 - ERROR - tuya_cloud_connector: Please activate OpenPulsar: https://developer.tuya.com/en/docs/iot/subscribe-mq?id=Kavqcrvckbh9h
2022-09-10 17:31:14,147 - WARNING - asyncio: Executing <Task pending name='Task-179' coro=<tuya_cloud_device._init_device() running at /opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py:30> wait_for=<Future pending $
2022-09-10 20:07:39,059 - INFO - fhempy.lib.pkg_installer: Attempting install of fhempy
2022-09-10 20:11:24,346 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2022-09-10 20:11:24,397 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2022-09-10 20:11:24,677 - WARNING - asyncio: Executing <Task pending name='Task-1' coro=<async_main() running at /opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py:498> wait_for=<_GatheringFuture pending cb=[<TaskWakeupMethWr$
Traceback (most recent call last):
File "/opt/fhem/FHEM/bindings/python/bin/fhempy", line 118, in <module>
fpb.run()
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 506, in run
asyncio.get_event_loop().run_until_complete(async_main())
File "/usr/lib/python3.9/asyncio/base_events.py", line 642, in run_until_complete
return future.result()
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 498, in async_main
await websockets.serve(
File "/opt/fhem/.local/lib/python3.9/site-packages/websockets/legacy/server.py", line 1042, in __await_impl__
server = await self._create_server()
File "/usr/lib/python3.9/asyncio/base_events.py", line 1494, in create_server
raise OSError(err.errno, 'error while attempting '
OSError: [Errno 98] error while attempting to bind on address ('0.0.0.0', 15733): address already in use
2022-09-10 20:11:50,014 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2022-09-10 20:11:50,062 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
Nach dem fhempy-Server-Neustart wiederholen sich dann folgende Einträge endlos:
2022-09-10 20:38:31,148 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy...
2022-09-10 20:38:31,221 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2022-09-10 20:38:31,414 - WARNING - asyncio: Executing <Task pending name='Task-1' coro=<async_main() running at /opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py:498> wait_for=<_GatheringFuture pending cb=[<TaskWakeupMethWr$
2022-09-10 20:38:31,421 - INFO - websockets.server: server listening on 0.0.0.0:15733
2022-09-10 20:38:34,013 - INFO - websockets.server: connection open
2022-09-10 20:38:34,020 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2022-09-10 20:38:34,147 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message: b'{"PYTHONTYPE":"tuya_cloud","FHEMPYTYPE":"tuya_cloud","args":["Antela_Smart_Plug_2_bfe173b4c08837c9c6cnxh","fhempy","tuya_cloud","tuya_cloud_connector","bfe17$
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 129, in onMessage
await self._onMessage(payload)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 137, in _onMessage
logger.debug(">>> WS: " + msg)
TypeError: can only concatenate str (not "bytes") to str
2022-09-10 20:38:34,149 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message: b'{"defargs":["fhempy_local","BindingsIo","fhempy"],"function":"event","defargsh":{},"argsh":{},"PYTHONTYPE":null,"NAME":"fhempy_local","FHEMPYTYPE":null,"args$
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 129, in onMessage
await self._onMessage(payload)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 137, in _onMessage
logger.debug(">>> WS: " + msg)
TypeError: can only concatenate str (not "bytes") to str
2022-09-10 20:38:44,119 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message: b'{"function":"Define","defargs":["Bewegungssensor_Toilette_bf7f9ec38f1f0c78e3c6tx","fhempy","tuya_cloud","tuya_cloud_connector","bf7f9ec38f1f0c78e3c6tx"],"msg$
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 129, in onMessage
await self._onMessage(payload)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 137, in _onMessage
logger.debug(">>> WS: " + msg)
TypeError: can only concatenate str (not "bytes") to str
2022-09-10 2
Dein fhempy ist nicht aktuell.
Mach ein
sudo -u them bash
pip3 install --upgrade fhempy
Zitat von: dominik am 11 September 2022, 09:22:59
Dein fhempy ist nicht aktuell.
Mach ein
sudo -u them bash
pip3 install --upgrade fhempy
bei mir läuft FHEM in einem Docker Container - geht das dann so auch? Ich hatte den Container jetzt nochmal neu erstellt, aber scheinbar wird dadurch fhempy leider nicht in neuer Version installiert.
Zitat von: maddhin am 11 September 2022, 13:16:44
bei mir läuft FHEM in einem Docker Container - geht das dann so auch? Ich hatte den Container jetzt nochmal neu erstellt, aber scheinbar wird dadurch fhempy leider nicht in neuer Version installiert.
Kannst du dich nicht per ssh in den Docker Container verbinden? Ich habe mit Docker nicht so viel Erfahrung.
So, habe heute den ganzen Tag versucht das fhempy-Problem zu lösen, bin aber nicht weitergekommen. Tuya cloud sagt immer noch "fhempy server offline".
Ich habe nun ein vergleichsweise aktuelles Fhem-docker:Bullseye image (das "empfohlene") am laufen (davor war es das experimental:dev), hat aber genau garnichts geändert. Bis auf, dass das fhempy Log nun auf 185MB angewachsen ist...
Hat noch jemand eine Idee? Ins docker-image möchte ich eigentlich nicht reingehen, das würde die Sache ja nur temporär lösen.
Poste bitte das Log. Der vorige Fehler kann es ja nun nicht mehr sein
hm, eigentlich immer noch der gleiche Fehler. 180MB von dem:
2022-09-11 20:40:13,878 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message: b'{"defargs":null,"FHEMPYTYPE":null,"args":["volume_alarm: 30"],"function":"event","id":91011323,"argsh":{},"defargsh":null,"msgtype":"event","NAME":"ECHO_G091AA081132005B","PYTHONTYPE":null}'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 129, in onMessage
await self._onMessage(payload)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 137, in _onMessage
logger.debug(">>> WS: " + msg)
TypeError: can only concatenate str (not "bytes") to str
2022-09-11 20:40:13,893 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message: b'{"function":"event","id":86815192,"FHEMPYTYPE":null,"args":["volume_alarm: 0"],"defargs":null,"PYTHONTYPE":null,"msgtype":"event","NAME":"ECHO_G090XG121505114X","defargsh":null,"argsh":{}}'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 129, in onMessage
await self._onMessage(payload)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 137, in _onMessage
logger.debug(">>> WS: " + msg)
TypeError: can only concatenate str (not "bytes") to str
Was kommt bei fhempy Start für eine Versionsnummer? Also im Log
im Log kann ich keine Version finden - in Fhem steht 0.1.242
Das ist viel zu alt. Wir hast du das installiert? Wie sieht dein Dockerfile aus?
ich habe fhempy über docker-compose installiert:
fhem:
#image: fhem/fhem:latest
#image: ghcr.io/fhem/fhem-experimental:dev
image: ghcr.io/fhem/fhem/fhem-docker:bullseye
container_name: fhem
privileged: true
restart: always
ports:
- "8083:8083"
- "7072:7072"
- "3002:3002"
volumes:
- ./fhem/core/:/opt/fhem/
networks:
- fhem-network
#devices:
# - "/dev/ttyUSB0:/dev/ttyUSB0"
environment:
FHEM_UID: 1000
FHEM_GID: 1000
TIMEOUT: 10
RESTART: 1
TELNETPORT: 7072
TZ: Europe/Berlin
APT_PKGS: "python3 python3-pip python3-dev libffi-dev libssl-dev libjpeg-dev zlib1g-dev autoconf build-essential libglib2.0-dev libdbus-1-dev bluez libbluetooth-dev git"
NPM_PKGS: "alexa-fhem alexa-cookie2"
CPAN_PKGS: "Protocol::WebSocket"
depends_on:
- "mysql"
- "mqtt"
Ich war der Meinung, dass dann aktuelle Versionen installiert werden.
Ich lasse gerade pip3 install --upgrade fhempy laufen - das installiert die aktuelle Version 1.461. Kennt jemand eine Möglichkeit das beim Start/Build des Containers laufen zu lassen?
Sollte das Update nicht auch über die FHEM Oberfläche anstoßbar sein? Aktuell passiert da bei mir gar nichts:(
Bei der alten Version geht das Update über fhem leider nicht.
ok, nun eine dumme Frage: wo habe ich denn die stein-alte Version von fhempy her? Lag das an dem alten Docker-Image oder wurde da eine alte Version runtergeladen? Meiner Meinung nach wurde fhempy über FHEM beim Anlegen des devices installiert, oder?
Hintergrund meiner Frage ist einfach, wie ich in Zukunft dann automatisch eine aktuelle Version bekommen. Das Update jetzt hält ja (wohl) nur bis zum nächsten Start des Containers. Das ist ja nicht nachhaltig:(
Warum nur bis zum Restart? Der Container hält ja seine Daten und baut sich ja nicht dauernd neu, oder?
Soweit ich weiß, ist das so. Beim Neustart lädt wieder das ursprüngliche Image - nur die Daten im Volume bleiben erhalten. Ich kenne mich da aber auch nicht aus. Meine Linux-Kenntnisse sind weitestgehend c&p ;)
Die manuelle Installation / Update von fhempy scheitert an cryptography bzw. fehlendem rust. Komisch, das hatte alles monatelang gut funktioniert. Irgendwas hat mir das letzte FHEM-Update da zerschossen.
Poste die Fehler von der Installation.
Bei Docker kann ich leider nicht viel helfen.
das ist der Teil, wo die Fehler anfangen
Building wheels for collected packages: aiohttp, cryptography, dbus-python, websockets, frozenlist, multidict, yarl, pycares, Brotli, cchardet
Building wheel for aiohttp (PEP 517) ... done
Created wheel for aiohttp: filename=aiohttp-3.8.1-cp39-cp39-linux_armv7l.whl size=1123292 sha256=3c733a97da4b908873d8d6b0093a27a7df5a31e2a9018ecf225762395e4c8757
Stored in directory: /root/.cache/pip/wheels/18/3d/16/11bf4b984ebad9a308297e1dd7ece9703314c8a4361f770e4f
Building wheel for cryptography (PEP 517) ... error
ERROR: Command errored out with exit status 1:
command: /usr/bin/python3 /tmp/tmpdx_c70sz_in_process.py build_wheel /tmp/tmp9o0lauww
cwd: /tmp/pip-install-khzjojv5/cryptography_63bdf7e594694206afd129c5250bb489
Complete output (192 lines):
running bdist_wheel
running build
running build_py
creating build
creating build/lib.linux-armv7l-cpython-39
creating build/lib.linux-armv7l-cpython-39/cryptography
copying src/cryptography/__init__.py -> build/lib.linux-armv7l-cpython-39/cryptography
copying src/cryptography/__about__.py -> build/lib.linux-armv7l-cpython-39/cryptography
copying src/cryptography/fernet.py -> build/lib.linux-armv7l-cpython-39/cryptography
copying src/cryptography/utils.py -> build/lib.linux-armv7l-cpython-39/cryptography
copying src/cryptography/exceptions.py -> build/lib.linux-armv7l-cpython-39/cryptography
creating build/lib.linux-armv7l-cpython-39/cryptography/hazmat
copying src/cryptography/hazmat/__init__.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat
copying src/cryptography/hazmat/_oid.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat
creating build/lib.linux-armv7l-cpython-39/cryptography/x509
copying src/cryptography/x509/base.py -> build/lib.linux-armv7l-cpython-39/cryptography/x509
copying src/cryptography/x509/ocsp.py -> build/lib.linux-armv7l-cpython-39/cryptography/x509
copying src/cryptography/x509/__init__.py -> build/lib.linux-armv7l-cpython-39/cryptography/x509
copying src/cryptography/x509/general_name.py -> build/lib.linux-armv7l-cpython-39/cryptography/x509
copying src/cryptography/x509/oid.py -> build/lib.linux-armv7l-cpython-39/cryptography/x509
copying src/cryptography/x509/extensions.py -> build/lib.linux-armv7l-cpython-39/cryptography/x509
copying src/cryptography/x509/name.py -> build/lib.linux-armv7l-cpython-39/cryptography/x509
copying src/cryptography/x509/certificate_transparency.py -> build/lib.linux-armv7l-cpython-39/cryptography/x509
creating build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/cmac.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/poly1305.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/padding.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/hashes.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/constant_time.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/__init__.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/_asymmetric.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/keywrap.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/hmac.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/_cipheralgorithm.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/_serialization.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives
creating build/lib.linux-armv7l-cpython-39/cryptography/hazmat/bindings
copying src/cryptography/hazmat/bindings/__init__.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/bindings
creating build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends
copying src/cryptography/hazmat/backends/__init__.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends
creating build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/serialization
copying src/cryptography/hazmat/primitives/serialization/pkcs7.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/serialization
copying src/cryptography/hazmat/primitives/serialization/base.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/serialization
copying src/cryptography/hazmat/primitives/serialization/ssh.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/serialization
copying src/cryptography/hazmat/primitives/serialization/__init__.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/serialization
copying src/cryptography/hazmat/primitives/serialization/pkcs12.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/serialization
creating build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/x25519.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/dh.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/x448.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/padding.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/types.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/ec.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/__init__.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/ed25519.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/dsa.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/utils.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/ed448.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/rsa.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/asymmetric
creating build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/twofactor
copying src/cryptography/hazmat/primitives/twofactor/hotp.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/twofactor
copying src/cryptography/hazmat/primitives/twofactor/__init__.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/twofactor
copying src/cryptography/hazmat/primitives/twofactor/totp.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/twofactor
creating build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/ciphers
copying src/cryptography/hazmat/primitives/ciphers/base.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/ciphers
copying src/cryptography/hazmat/primitives/ciphers/__init__.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/ciphers
copying src/cryptography/hazmat/primitives/ciphers/modes.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/ciphers
copying src/cryptography/hazmat/primitives/ciphers/aead.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/ciphers
copying src/cryptography/hazmat/primitives/ciphers/algorithms.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/ciphers
creating build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/kdf
copying src/cryptography/hazmat/primitives/kdf/scrypt.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/kdf
copying src/cryptography/hazmat/primitives/kdf/x963kdf.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/kdf
copying src/cryptography/hazmat/primitives/kdf/__init__.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/kdf
copying src/cryptography/hazmat/primitives/kdf/concatkdf.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/kdf
copying src/cryptography/hazmat/primitives/kdf/pbkdf2.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/kdf
copying src/cryptography/hazmat/primitives/kdf/kbkdf.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/kdf
copying src/cryptography/hazmat/primitives/kdf/hkdf.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/kdf
creating build/lib.linux-armv7l-cpython-39/cryptography/hazmat/bindings/openssl
copying src/cryptography/hazmat/bindings/openssl/__init__.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/bindings/openssl
copying src/cryptography/hazmat/bindings/openssl/_conditional.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/bindings/openssl
copying src/cryptography/hazmat/bindings/openssl/binding.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/bindings/openssl
creating build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/cmac.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/x25519.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/dh.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/x448.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/poly1305.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/decode_asn1.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/x509.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/ec.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/hashes.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/__init__.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/ed25519.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/hmac.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/dsa.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/aead.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/backend.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/utils.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/encode_asn1.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/ciphers.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/ed448.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/rsa.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
running egg_info
writing src/cryptography.egg-info/PKG-INFO
writing dependency_links to src/cryptography.egg-info/dependency_links.txt
writing requirements to src/cryptography.egg-info/requires.txt
writing top-level names to src/cryptography.egg-info/top_level.txt
reading manifest file 'src/cryptography.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
no previously-included directories found matching 'docs/_build'
warning: no previously-included files found matching 'vectors'
warning: no previously-included files matching '*' found under directory 'vectors'
warning: no previously-included files matching '*' found under directory '.github'
warning: no previously-included files found matching 'release.py'
warning: no previously-included files found matching '.coveragerc'
warning: no previously-included files found matching 'codecov.yml'
warning: no previously-included files found matching '.readthedocs.yml'
warning: no previously-included files found matching 'dev-requirements.txt'
warning: no previously-included files found matching 'tox.ini'
warning: no previously-included files found matching 'mypy.ini'
warning: no previously-included files matching '*' found under directory '.circleci'
adding license file 'LICENSE'
adding license file 'LICENSE.APACHE'
adding license file 'LICENSE.BSD'
adding license file 'LICENSE.PSF'
writing manifest file 'src/cryptography.egg-info/SOURCES.txt'
/tmp/pip-build-env-esr8i7h2/overlay/lib/python3.9/site-packages/setuptools/command/build_py.py:202: SetuptoolsDeprecationWarning: Installing 'cryptography.hazmat.bindings._rust' as data is deprecated, please list it in `packages`.
!!
############################
# Package would be ignored #
############################
Python recognizes 'cryptography.hazmat.bindings._rust' as an importable package,
but it is not listed in the `packages` configuration of setuptools.
'cryptography.hazmat.bindings._rust' has been automatically added to the distribution only
because it may contain data files, but this behavior is likely to change
in future versions of setuptools (and therefore is considered deprecated).
Please make sure that 'cryptography.hazmat.bindings._rust' is included as a package by using
the `packages` configuration field or the proper discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" and "data files" on setuptools
documentation page.
!!
check.warn(importable)
copying src/cryptography/py.typed -> build/lib.linux-armv7l-cpython-39/cryptography
creating build/lib.linux-armv7l-cpython-39/cryptography/hazmat/bindings/_rust
copying src/cryptography/hazmat/bindings/_rust/__init__.pyi -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/bindings/_rust
copying src/cryptography/hazmat/bindings/_rust/asn1.pyi -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/bindings/_rust
copying src/cryptography/hazmat/bindings/_rust/ocsp.pyi -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/bindings/_rust
copying src/cryptography/hazmat/bindings/_rust/x509.pyi -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/bindings/_rust
running build_ext
running build_rust
=============================DEBUG ASSISTANCE=============================
If you are seeing a compilation error please try the following steps to
successfully install cryptography:
1) Upgrade to the latest pip and try again. This will fix errors for most
users. See: https://pip.pypa.io/en/stable/installing/#upgrading-pip
2) Read https://cryptography.io/en/latest/installation/ for specific
instructions for your platform.
3) Check our frequently asked questions for more information:
https://cryptography.io/en/latest/faq/
4) Ensure you have a recent Rust toolchain installed:
https://cryptography.io/en/latest/installation/#rust
Python: 3.9.2
platform: Linux-5.10.103-v7+-armv7l-with-glibc2.31
pip: n/a
setuptools: 65.3.0
setuptools_rust: 1.5.1
=============================DEBUG ASSISTANCE=============================
error: can't find Rust compiler
If you are using an outdated pip version, it is possible a prebuilt wheel is available for this package but pip is not able to install from it. Installing from the wheel would avoid the need for a Rust compiler.
To update pip, run:
pip install --upgrade pip
and then retry package installation.
If you did intend to build this package from source, try installing a Rust compiler from your system package manager and ensure it is on the PATH during installation. Alternatively, rustup (available at https://rustup.rs) is the recommended way to download and update the Rust compiler toolchain.
This package requires Rust >=1.41.0.
----------------------------------------
ERROR: Failed building wheel for cryptography
Building wheel for dbus-python (setup.py) ... done
Created wheel for dbus-python: filename=dbus_python-1.2.18-cp39-cp39-linux_armv7l.whl size=374188 sha256=4b93a7f16109fd7b9734a1041b9a5fcf680f0e1fd166613dca297ddc708375ef
Stored in directory: /root/.cache/pip/wheels/48/d1/96/05b72337093d7d112f03ec7d121fb5426ae2353bd6a50ba97c
Building wheel for websockets (setup.py) ... done
Created wheel for websockets: filename=websockets-10.3-cp39-cp39-linux_armv7l.whl size=104260 sha256=b1d28b6f65c3733fba2cf722bd899e3e6a3517ef182daabca3d92342f0f24fa7
Stored in directory: /root/.cache/pip/wheels/2f/1e/77/097069d35580f93f02355c49a0e7a8f78b7661566239e34bae
Building wheel for frozenlist (PEP 517) ... done
Created wheel for frozenlist: filename=frozenlist-1.3.1-cp39-cp39-linux_armv7l.whl size=135212 sha256=0ea514ca99dcadfa59eb47e9dad98934f99dae0970fcd0d33decc2f1df6c1914
Stored in directory: /root/.cache/pip/wheels/09/e2/6d/51973d3dad5063063920221ce5379c1fd7e65cd5fca17b4f35
Building wheel for multidict (PEP 517) ... done
Created wheel for multidict: filename=multidict-6.0.2-cp39-cp39-linux_armv7l.whl size=109421 sha256=1124e32715af978ecdb67a3515f5d55ed77d416638d101f7cde2ad71b9848972
Stored in directory: /root/.cache/pip/wheels/09/2e/af/35665f2dc3fdfa03603e3164d8d900effca39bd1ca5598f8d2
Building wheel for yarl (PEP 517) ... done
Created wheel for yarl: filename=yarl-1.8.1-cp39-cp39-linux_armv7l.whl size=204432 sha256=3ca4ca1958442c82c93e998e60d7cde0279da03f412168b9a47102d8f9a984d8
Stored in directory: /root/.cache/pip/wheels/5f/b3/e8/8e9829e063b11e43799fbe97f90dc6b123275822e2553ecbc2
Building wheel for pycares (PEP 517) ... done
Created wheel for pycares: filename=pycares-4.2.2-cp39-cp39-linux_armv7l.whl size=243215 sha256=2045603a4c8187fdfc4b21d5e89eecb95cce6a403b1e8ed3deeee0669d1faad8
Stored in directory: /root/.cache/pip/wheels/71/9e/4b/354d231631ca0eb996e5999f82ff15959d6219671e83d06e54
Building wheel for Brotli (setup.py) ... done
Created wheel for Brotli: filename=Brotli-1.0.9-cp39-cp39-linux_armv7l.whl size=2521773 sha256=f354c252ed584dadd0bf7b9e2d5af630b7a4638907174ddbebfe4cd9d89088ff
Stored in directory: /root/.cache/pip/wheels/fc/64/ad/723809ab7a5b321a3e5997a75e00f388547f49f73b3192a32a
Building wheel for cchardet (setup.py) ... done
Created wheel for cchardet: filename=cchardet-2.1.7-cp39-cp39-linux_armv7l.whl size=244233 sha256=26e741e20b1d79911e519af0e9f128d8d99aafe14b5fea974d0eb5e01dc6bc06
Stored in directory: /root/.cache/pip/wheels/53/72/df/32cb431a786ba2674993d3ea636aa0712c7f65495a9a3dbec9
Successfully built aiohttp dbus-python websockets frozenlist multidict yarl pycares Brotli cchardet
Failed to build cryptography
ERROR: Could not build wheels for cryptography which use PEP 517 and cannot be installed directly
Schon das probiert was im Log steht
pip install --upgrade pip
pip Update installiert:
root@864b2806dcc1:/opt/fhem# pip install --upgrade pip
Requirement already satisfied: pip in /usr/lib/python3/dist-packages (20.3.4)
Collecting pip
Downloading pip-22.2.2-py3-none-any.whl (2.0 MB)
|████████████████████████████████| 2.0 MB 47 kB/s
Installing collected packages: pip
Attempting uninstall: pip
Found existing installation: pip 20.3.4
Not uninstalling pip at /usr/lib/python3/dist-packages, outside environment /usr
Can't uninstall 'pip'. No files were found to uninstall.
Successfully installed pip-22.2.2
Dann wieder der fhempy Update Versuch:
Requirement already satisfied: certifi>=2017.4.17 in /usr/lib/python3/dist-packages (from requests==2.26.0->fhempy) (2020.6.20)
Requirement already satisfied: idna<4,>=2.5 in /usr/lib/python3/dist-packages (from requests==2.26.0->fhempy) (2.10)
Requirement already satisfied: ifaddr>=0.1.7 in /usr/lib/python3/dist-packages (from zeroconf==0.36.12->fhempy) (0.1.7)
Collecting pycparser
Using cached pycparser-2.21-py2.py3-none-any.whl (118 kB)
Collecting pycares>=4.0.0
Using cached pycares-4.2.2-cp39-cp39-linux_armv7l.whl
Building wheels for collected packages: cryptography
Building wheel for cryptography (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for cryptography (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [192 lines of output]
running bdist_wheel
running build
running build_py
creating build
creating build/lib.linux-armv7l-cpython-39
creating build/lib.linux-armv7l-cpython-39/cryptography
copying src/cryptography/__init__.py -> build/lib.linux-armv7l-cpython-39/cryptography
copying src/cryptography/__about__.py -> build/lib.linux-armv7l-cpython-39/cryptography
copying src/cryptography/fernet.py -> build/lib.linux-armv7l-cpython-39/cryptography
copying src/cryptography/utils.py -> build/lib.linux-armv7l-cpython-39/cryptography
copying src/cryptography/exceptions.py -> build/lib.linux-armv7l-cpython-39/cryptography
creating build/lib.linux-armv7l-cpython-39/cryptography/hazmat
copying src/cryptography/hazmat/__init__.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat
copying src/cryptography/hazmat/_oid.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat
creating build/lib.linux-armv7l-cpython-39/cryptography/x509
copying src/cryptography/x509/base.py -> build/lib.linux-armv7l-cpython-39/cryptography/x509
copying src/cryptography/x509/ocsp.py -> build/lib.linux-armv7l-cpython-39/cryptography/x509
copying src/cryptography/x509/__init__.py -> build/lib.linux-armv7l-cpython-39/cryptography/x509
copying src/cryptography/x509/general_name.py -> build/lib.linux-armv7l-cpython-39/cryptography/x509
copying src/cryptography/x509/oid.py -> build/lib.linux-armv7l-cpython-39/cryptography/x509
copying src/cryptography/x509/extensions.py -> build/lib.linux-armv7l-cpython-39/cryptography/x509
copying src/cryptography/x509/name.py -> build/lib.linux-armv7l-cpython-39/cryptography/x509
copying src/cryptography/x509/certificate_transparency.py -> build/lib.linux-armv7l-cpython-39/cryptography/x509
creating build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/cmac.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/poly1305.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/padding.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/hashes.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/constant_time.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/__init__.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/_asymmetric.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/keywrap.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/hmac.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/_cipheralgorithm.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives
copying src/cryptography/hazmat/primitives/_serialization.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives
creating build/lib.linux-armv7l-cpython-39/cryptography/hazmat/bindings
copying src/cryptography/hazmat/bindings/__init__.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/bindings
creating build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends
copying src/cryptography/hazmat/backends/__init__.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends
creating build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/serialization
copying src/cryptography/hazmat/primitives/serialization/pkcs7.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/serialization
copying src/cryptography/hazmat/primitives/serialization/base.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/serialization
copying src/cryptography/hazmat/primitives/serialization/ssh.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/serialization
copying src/cryptography/hazmat/primitives/serialization/__init__.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/serialization
copying src/cryptography/hazmat/primitives/serialization/pkcs12.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/serialization
creating build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/x25519.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/dh.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/x448.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/padding.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/types.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/ec.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/__init__.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/ed25519.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/dsa.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/utils.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/ed448.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/asymmetric
copying src/cryptography/hazmat/primitives/asymmetric/rsa.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/asymmetric
creating build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/twofactor
copying src/cryptography/hazmat/primitives/twofactor/hotp.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/twofactor
copying src/cryptography/hazmat/primitives/twofactor/__init__.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/twofactor
copying src/cryptography/hazmat/primitives/twofactor/totp.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/twofactor
creating build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/ciphers
copying src/cryptography/hazmat/primitives/ciphers/base.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/ciphers
copying src/cryptography/hazmat/primitives/ciphers/__init__.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/ciphers
copying src/cryptography/hazmat/primitives/ciphers/modes.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/ciphers
copying src/cryptography/hazmat/primitives/ciphers/aead.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/ciphers
copying src/cryptography/hazmat/primitives/ciphers/algorithms.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/ciphers
creating build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/kdf
copying src/cryptography/hazmat/primitives/kdf/scrypt.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/kdf
copying src/cryptography/hazmat/primitives/kdf/x963kdf.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/kdf
copying src/cryptography/hazmat/primitives/kdf/__init__.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/kdf
copying src/cryptography/hazmat/primitives/kdf/concatkdf.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/kdf
copying src/cryptography/hazmat/primitives/kdf/pbkdf2.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/kdf
copying src/cryptography/hazmat/primitives/kdf/kbkdf.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/kdf
copying src/cryptography/hazmat/primitives/kdf/hkdf.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/primitives/kdf
creating build/lib.linux-armv7l-cpython-39/cryptography/hazmat/bindings/openssl
copying src/cryptography/hazmat/bindings/openssl/__init__.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/bindings/openssl
copying src/cryptography/hazmat/bindings/openssl/_conditional.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/bindings/openssl
copying src/cryptography/hazmat/bindings/openssl/binding.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/bindings/openssl
creating build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/cmac.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/x25519.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/dh.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/x448.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/poly1305.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/decode_asn1.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/x509.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/ec.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/hashes.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/__init__.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/ed25519.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/hmac.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/dsa.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/aead.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/backend.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/utils.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/encode_asn1.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/ciphers.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/ed448.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
copying src/cryptography/hazmat/backends/openssl/rsa.py -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/backends/openssl
running egg_info
writing src/cryptography.egg-info/PKG-INFO
writing dependency_links to src/cryptography.egg-info/dependency_links.txt
writing requirements to src/cryptography.egg-info/requires.txt
writing top-level names to src/cryptography.egg-info/top_level.txt
reading manifest file 'src/cryptography.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
no previously-included directories found matching 'docs/_build'
warning: no previously-included files found matching 'vectors'
warning: no previously-included files matching '*' found under directory 'vectors'
warning: no previously-included files matching '*' found under directory '.github'
warning: no previously-included files found matching 'release.py'
warning: no previously-included files found matching '.coveragerc'
warning: no previously-included files found matching 'codecov.yml'
warning: no previously-included files found matching '.readthedocs.yml'
warning: no previously-included files found matching 'dev-requirements.txt'
warning: no previously-included files found matching 'tox.ini'
warning: no previously-included files found matching 'mypy.ini'
warning: no previously-included files matching '*' found under directory '.circleci'
adding license file 'LICENSE'
adding license file 'LICENSE.APACHE'
adding license file 'LICENSE.BSD'
adding license file 'LICENSE.PSF'
writing manifest file 'src/cryptography.egg-info/SOURCES.txt'
/tmp/pip-build-env-ko_nf87n/overlay/lib/python3.9/site-packages/setuptools/command/build_py.py:202: SetuptoolsDeprecationWarning: Installing 'cryptography.hazmat.bindings._rust' as data is deprecated, please list it in `packages`.
!!
############################
# Package would be ignored #
############################
Python recognizes 'cryptography.hazmat.bindings._rust' as an importable package,
but it is not listed in the `packages` configuration of setuptools.
'cryptography.hazmat.bindings._rust' has been automatically added to the distribution only
because it may contain data files, but this behavior is likely to change
in future versions of setuptools (and therefore is considered deprecated).
Please make sure that 'cryptography.hazmat.bindings._rust' is included as a package by using
the `packages` configuration field or the proper discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" and "data files" on setuptools
documentation page.
!!
check.warn(importable)
copying src/cryptography/py.typed -> build/lib.linux-armv7l-cpython-39/cryptography
creating build/lib.linux-armv7l-cpython-39/cryptography/hazmat/bindings/_rust
copying src/cryptography/hazmat/bindings/_rust/__init__.pyi -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/bindings/_rust
copying src/cryptography/hazmat/bindings/_rust/asn1.pyi -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/bindings/_rust
copying src/cryptography/hazmat/bindings/_rust/ocsp.pyi -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/bindings/_rust
copying src/cryptography/hazmat/bindings/_rust/x509.pyi -> build/lib.linux-armv7l-cpython-39/cryptography/hazmat/bindings/_rust
running build_ext
running build_rust
=============================DEBUG ASSISTANCE=============================
If you are seeing a compilation error please try the following steps to
successfully install cryptography:
1) Upgrade to the latest pip and try again. This will fix errors for most
users. See: https://pip.pypa.io/en/stable/installing/#upgrading-pip
2) Read https://cryptography.io/en/latest/installation/ for specific
instructions for your platform.
3) Check our frequently asked questions for more information:
https://cryptography.io/en/latest/faq/
4) Ensure you have a recent Rust toolchain installed:
https://cryptography.io/en/latest/installation/#rust
Python: 3.9.2
platform: Linux-5.10.103-v7+-armv7l-with-glibc2.31
pip: 22.2.2
setuptools: 65.3.0
setuptools_rust: 1.5.1
=============================DEBUG ASSISTANCE=============================
error: can't find Rust compiler
If you are using an outdated pip version, it is possible a prebuilt wheel is available for this package but pip is not able to install from it. Installing from the wheel would avoid the need for a Rust compiler.
To update pip, run:
pip install --upgrade pip
and then retry package installation.
If you did intend to build this package from source, try installing a Rust compiler from your system package manager and ensure it is on the PATH during installation. Alternatively, rustup (available at https://rustup.rs) is the recommended way to download and update the Rust compiler toolchain.
This package requires Rust >=1.41.0.
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for cryptography
Failed to build cryptography
ERROR: Could not build wheels for cryptography, which is required to install pyproject.toml-based projects
Danach dachte ich, ich versuche pip nochmal zu installieren:
root@864b2806dcc1:/opt/fhem# pip install --upgrade pip
Requirement already satisfied: pip in /usr/lib/python3/dist-packages (20.3.4)
Collecting pip
Using cached pip-22.2.2-py3-none-any.whl (2.0 MB)
Installing collected packages: pip
Attempting uninstall: pip
Found existing installation: pip 20.3.4
Uninstalling pip-20.3.4:
Successfully uninstalled pip-20.3.4
Successfully installed pip-22.2.2
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
root@864b2806dcc1:/opt/fhem# pip3 install --upgrade fhempy
bash: /usr/bin/pip3: No such file or directory
root@864b2806dcc1:/opt/fhem# pip3 install --upgrade fhempy
bash: /usr/bin/pip3: No such file or directory
root@864b2806dcc1:/opt/fhem# pip install --upgrade fhempy
bash: /usr/bin/pip: No such file or directory
root@864b2806dcc1:/opt/fhem# pip install --upgrade pip
bash: /usr/bin/pip: No such file or directory
Achtung, warum machst du das als root?
Bitte den User fhem verwenden und nicht root.
hab das Ganze jetzt nochmal als fhem user gemacht, hat aber die Fehlermeldung nicht geändert:(
Hallo zusammen,
ich habe das Problem auch. Habe jetzt alles auf den neuesten Stand gebracht und bekomme folgende Fehlermeldung Siehe Bild. Der fhempy Server und das localbinding scheinen zu laufen. Zumindest habe ich einen grünen Punkt am Symbol. Beim Tuya Cloud setup kommt dann diese Meldung:
Failed to load module tuya_cloud: Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/fhem_pythonbinding.py", line 318, in handle_function
module_object = await self.import_module(hash)
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/fhem_pythonbinding.py", line 526, in import_module
functools.partial(importlib.import_module, pymodule)
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/utils.py", line 35, in run_blocking
return await asyncio.get_event_loop().run_in_executor(pool, function)
File "/usr/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
File "<frozen importlib._bootstrap>", line 983, in _find_and_load
File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 728, in exec_module
File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud.py", line 8, in <module>
import fhempy.lib.tuya_cloud.tuya_cloud_setup as tcs
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 5, in <module>
import tuya_iot
File "/opt/fhem/.local/lib/python3.7/site-packages/tuya_iot/__init__.py", line 2, in <module>
from .device import TuyaDevice, TuyaDeviceListener, TuyaDeviceManager
File "/opt/fhem/.local/lib/python3.7/site-packages/tuya_iot/device.py", line 7, in <module>
from typing import Any, Literal, Optional
ImportError: cannot import name 'Literal' from 'typing' (/usr/lib/python3.7/typing.py)
Hat jemand eine Idee !?
Nachdem ich nun eine Nacht über das Problem geschlafen habe, bin ich der Meinung, dass das ein fhempy-Problem ist. Mein Fhem und Bullseye sind aktuell, aber bei einem define fhempy_lokal ... wird nachwievor so eine alte Version installiert. Irgendwas kann da doch nicht stimmen, oder?
Zitat von: dobiwan am 12 September 2022, 08:26:33
Hallo zusammen,
ich habe das Problem auch. Habe jetzt alles auf den neuesten Stand gebracht und bekomme folgende Fehlermeldung Siehe Bild. Der fhempy Server und das localbinding scheinen zu laufen. Zumindest habe ich einen grünen Punkt am Symbol. Beim Tuya Cloud setup kommt dann diese Meldung:
Failed to load module tuya_cloud: Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/fhem_pythonbinding.py", line 318, in handle_function
module_object = await self.import_module(hash)
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/fhem_pythonbinding.py", line 526, in import_module
functools.partial(importlib.import_module, pymodule)
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/utils.py", line 35, in run_blocking
return await asyncio.get_event_loop().run_in_executor(pool, function)
File "/usr/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
File "<frozen importlib._bootstrap>", line 983, in _find_and_load
File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 728, in exec_module
File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud.py", line 8, in <module>
import fhempy.lib.tuya_cloud.tuya_cloud_setup as tcs
File "/opt/fhem/.local/lib/python3.7/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 5, in <module>
import tuya_iot
File "/opt/fhem/.local/lib/python3.7/site-packages/tuya_iot/__init__.py", line 2, in <module>
from .device import TuyaDevice, TuyaDeviceListener, TuyaDeviceManager
File "/opt/fhem/.local/lib/python3.7/site-packages/tuya_iot/device.py", line 7, in <module>
from typing import Any, Literal, Optional
ImportError: cannot import name 'Literal' from 'typing' (/usr/lib/python3.7/typing.py)
Hat jemand eine Idee !?
Tuya cloud benötigt Python 3.8 oder höher.
Zitat von: maddhin am 12 September 2022, 09:10:26
Nachdem ich nun eine Nacht über das Problem geschlafen habe, bin ich der Meinung, dass das ein fhempy-Problem ist. Mein Fhem und Bullseye sind aktuell, aber bei einem define fhempy_lokal ... wird nachwievor so eine alte Version installiert. Irgendwas kann da doch nicht stimmen, oder?
Kann es sein, dass pip nicht aktuell ist? Kannst du sicherstellen, dass pip in der letzten Version im Docker Image ist? Vielleicht liegt es daran.
Zitat von: dominik am 12 September 2022, 22:42:29
Kann es sein, dass pip nicht aktuell ist?
pip-22.2.2 das sollte die aktuellste Version sein. Bullseye und Fhem habe ich beide komplett aktualisiert.
Ich weiß nicht, was nach dem define passiert, aber irgendwie sollte sichergestellt werden, dass eine aktuelle Version von fhempy installiert wird. Ggf. hat das was mit Docker zu tun, ich verstehe aber zu wenig davon, um hier fachlich wirklich helfen zu können:( Probiere aber gerne Lösungen aus, die vielleicht weiterhelfen:)
Ich hab mal eine Änderung gemacht, probier es bitte nochmals.
Wie ist das bei Docker, machst du da auch automatisch ein update add in FHEM, oder machst du das danach manuell via WEB?
bei docker geht eigentlich alles genauso wie bei einer normalen Installation. Nur eben ändert man am OS nichts (mehr), benötigte Pakete könnten aber installiert werden. Insofern geht update add in FHEM auch ganz normal.
Habe das Update gemacht, hat aber leider wieder 0.1.242 installiert:(
Hilft es vielleicht zu überlegen, wo die 0.1.242 herkommt? Irgendwie scheint das ja eine Altlast auf meinem System zu sein, die nicht aktualisiert wird/wurde. Ich kann mir nicht vorstellen, dass die 0.1.242 aktuell runtergeladen wird. Vielleicht liegt das an der Ordnerstruktur, die bei Docker ggf. anders ist.
Die 242 ist nirgends hinterlegt.
Wie meinst du mit Altlast? Ich dachte mit Docker wird immer alles "frisch" gemacht und es kann daher gar keine Altlasten geben, oder? fhempy darf natürlich nicht vorher noch da sein, sonst wird das genommen. Das musst du zuerst löschen.
Also wenn es eine Altlast ist, dann kannst du am einfachsten
ssh ...
sudo -u fhem bash
pip3 install --upgrade fhempy
Weil wenn die Altlast auf einem Volume mitgenommen wird, dann wird das Update auch mitgenommen. fhempy liegt unter /opt/fhem, falls das dein Volume ist.
mit Altlast meinte ich, dass irgendwo in FHEM was von fhempy rumliegt und nicht geupdatet wird.
Ich habe jetzt mal die fhempy im Ordner gelöscht und es kamen folgende Fehlermeldungen im fhem.log:
:
2022.09.13 21:48:56.823 3: BindingsIo v1.0.0
2022.09.13 21:48:58.005 3: fhempyServer v1.0.0
2022.09.13 21:48:59.085 2: fhempyserver_15733: FHEM/bindings/python/bin/fhempy: not executable
2022.09.13 21:48:59.277 2: fhempyserver_15733: FHEM/bindings/python/bin/fhempy: not executable
2022.09.13 21:49:03.064 3: Opening fhempy_local device ws:127.0.0.1:15733
2022.09.13 21:49:03.119 1: fhempy_local: Can't connect to ws:127.0.0.1:15733: 127.0.0.1: Connection refused (111)
2022.09.13 21:49:03.120 1: BindingsIo (fhempy_local): ERROR during connection setup: 127.0.0.1: Connection refused (111)
Nach einem update stand da, dass bindings aktualisiert wurde und dass fhempy aktualisiert wird.
Aber irgendwie tat sich da nichts.
Ich habe dann fhempy direkt beim Start des Containers installieren lassen (-e pip_pkg "fhempy") und das hat dann fhempy (wieder) installiert. Aber kurioserweise wieder die 0.1.242... D.h. die v0.1.242 muss dann ja eigentlich runtergeladen worden sein, oder? Aber wieso wird dann eine alte Version runtergeladen? Habe ich hier irgendwie eine alte Referenz/deb zu fhempy?
Moin,
ist https://pypi.org/project/fhempy/ down? Egal welches Modul man anklickt. es kommt immer ein 404.
https://pypi.org/project/fhempy/FHEM/bindings/python/fhempy/lib/tuya_cloud/README.md (https://pypi.org/project/fhempy/FHEM/bindings/python/fhempy/lib/tuya_cloud/README.md)
Kann mal bitte jemand anders schauen? Danke.
Bis denne
Edit: Seit heute morgen habe ich massenweise Fehler im Log:
2022-09-14 09:03:39,013 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message: b'{"defargs":null,"NAME":"BlinkSchalter","argsh":{},"id":"25604374","FHEMPYTYPE":null,"PYTHONTYPE":null,"defargsh":null,"msgtype":"event","function":"event","args":["on"]}'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 144, in onMessage
await self._onMessage(payload)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 150, in _onMessage
logger.debug(">>> WS: " + msg)
TypeError: can only concatenate str (not "bytes") to str
2022-09-14 09:03:39,031 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message: b'{"msgtype":"event","args":["state: Next: 09:03:49"],"function":"event","FHEMPYTYPE":null,"id":"9368728","defargs":null,"argsh":{},"NAME":"Blink1Start","PYTHONTYPE":null,"defargsh":null}'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 144, in onMessage
await self._onMessage(payload)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 150, in _onMessage
logger.debug(">>> WS: " + msg)
TypeError: can only concatenate str (not "bytes") to str
2022-09-14 09:03:39,042 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message: b'{"msgtype":"event","function":"event","args":["on"],"FHEMPYTYPE":null,"id":"86599642","argsh":{},"NAME":"Blink2Schalter","defargs":null,"defargsh":null,"PYTHONTYPE":null}'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 144, in onMessage
await self._onMessage(payload)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 150, in _onMessage
logger.debug(">>> WS: " + msg)
TypeError: can only concatenate str (not "bytes") to str
2022-09-14 09:03:39,057 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message: b'{"msgtype":"event","args":["state: Next: 09:03:43"],"function":"event","FHEMPYTYPE":null,"id":"25536032","defargs":null,"NAME":"Blink2Start","argsh":{},"PYTHONTYPE":null,"defargsh":null}'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 144, in onMessage
await self._onMessage(payload)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 150, in _onMessage
logger.debug(">>> WS: " + msg)
TypeError: can only concatenate str (not "bytes") to str
Den gleichen Fehler habe ich auch. Ggf ist der durch das Neuinstallieren behoben worden, muss aber heute Abend gucken.
was läuft da falsch?
root@fhem-z2w:/opt.tmpfs/fhem# sudo -u fhem bash
fhem@fhem-z2w:~$ pwd
/opt.tmpfs/fhem
fhem@fhem-z2w:~$ /usr/bin/python3 -m pip install fhempy>=0.1.12 --upgrade
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='pypi.org', port=443): Read timed out. (read timeout=15)")': /simple/fhempy/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='pypi.org', port=443): Read timed out. (read timeout=15)")': /simple/fhempy/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='pypi.org', port=443): Read timed out. (read timeout=15)")': /simple/fhempy/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='pypi.org', port=443): Read timed out. (read timeout=15)")': /simple/fhempy/
Das klingt nach einem Netzwerkproblem oder pypi Problem.
Könnt ihr mal ein anderes Package installieren probieren?
Zitat von: maddhin am 14 September 2022, 00:38:55
mit Altlast meinte ich, dass irgendwo in FHEM was von fhempy rumliegt und nicht geupdatet wird.
Ich habe jetzt mal die fhempy im Ordner gelöscht und es kamen folgende Fehlermeldungen im fhem.log:
:
2022.09.13 21:48:56.823 3: BindingsIo v1.0.0
2022.09.13 21:48:58.005 3: fhempyServer v1.0.0
2022.09.13 21:48:59.085 2: fhempyserver_15733: FHEM/bindings/python/bin/fhempy: not executable
2022.09.13 21:48:59.277 2: fhempyserver_15733: FHEM/bindings/python/bin/fhempy: not executable
2022.09.13 21:49:03.064 3: Opening fhempy_local device ws:127.0.0.1:15733
2022.09.13 21:49:03.119 1: fhempy_local: Can't connect to ws:127.0.0.1:15733: 127.0.0.1: Connection refused (111)
2022.09.13 21:49:03.120 1: BindingsIo (fhempy_local): ERROR during connection setup: 127.0.0.1: Connection refused (111)
Nach einem update stand da, dass bindings aktualisiert wurde und dass fhempy aktualisiert wird.
Aber irgendwie tat sich da nichts.
Ich habe dann fhempy direkt beim Start des Containers installieren lassen (-e pip_pkg "fhempy") und das hat dann fhempy (wieder) installiert. Aber kurioserweise wieder die 0.1.242... D.h. die v0.1.242 muss dann ja eigentlich runtergeladen worden sein, oder? Aber wieso wird dann eine alte Version runtergeladen? Habe ich hier irgendwie eine alte Referenz/deb zu fhempy?
Lösch mal /opt/fhem/.local/lib/python3.9/site-packages/fhempy* und starte dann neu.
jetzt kommen wir der Sache näher... Da war auch ein Verzeichnis "fhempy-0.1.242.dist-info", d.h. jetzt wissen wir, wo die 0.1.242 immer herkam...
Habe beide Verzeichnisse gelöscht. Bis jetzt habe ich trotz Neuinstallation von fhempy und (nach Löschen) erneutem define der devices fhempy noch nicht wieder zum Laufen gebracht.
Ich probiere es heute Abend nochmal.
also automatisch installiert sich bei mir nach dem define leider nichts (mehr).
Auszug aus dem FHEM-Log:
2022.09.15 21:10:41.007 1: Downloading https://raw.githubusercontent.com/dominikkarall/fhempy/master/controls_pythonbinding.txt
2022.09.15 21:10:41.010 1:
2022.09.15 21:10:41.013 1: pythonbinding
2022.09.15 21:10:41.684 1: nothing to do...
2022.09.15 21:12:38.163 3: BindingsIo v1.0.0
2022.09.15 21:12:38.200 3: fhempyServer v1.0.0
2022.09.15 21:12:38.299 3: fhempyserver_15733: starting
2022.09.15 21:12:38.319 3: fhempyserver_15733: using logfile: ./log/fhempy-2022-09-15.log
2022.09.15 21:12:38.925 1: mqtt:1883 disconnected, waiting to reappear (Mosquitto)
2022.09.15 21:12:39.152 3: fhempyserver_15733: read: end of file reached while sysread
2022.09.15 21:12:39.154 3: fhempyserver_15733: stopped
2022.09.15 21:12:39.181 3: fhempyserver_15733: starting
2022.09.15 21:12:39.202 3: fhempyserver_15733: using logfile: ./log/fhempy-2022-09-15.log
2022.09.15 21:12:39.558 1: mqtt:1883 reappeared (Mosquitto)
2022.09.15 21:13:02.836 3: Opening fhempy_local device ws:127.0.0.1:15733
2022.09.15 21:13:03.530 1: fhempy_local: Can't connect to ws:127.0.0.1:15733: 127.0.0.1: Connection refused (111)
2022.09.15 21:13:03.531 1: BindingsIo (fhempy_local): ERROR during connection setup: 127.0.0.1: Connection refused (111)
Ich habe versucht rust, cryptography und eben fhempy manuell zu installieren, aber cryptography will einfach nicht. Das übersteigt meine Fähigkeiten und mein RPI ist durch die ganzen docker images / rebuilds inzwischen an das Speicherlimit gekommen. Musste erstmal GBs löschen. Zudem befürchte ich, dass das manuelle Wursteln mit bash im Dockerimage nicht gut ist und spätestens beim Umzug auf einen neuen Server wieder alles neu gewurstelt werden muss (und ich bis dahin keine Ahnung mehr habe, was getan werden muss).
Gibt es hier nicht die Möglichkeit, dass das PIP fhempy Paket alles installiert, was notwendig ist, damit es funktioniert? Ggf. so wie das Alexa-Fhem Paket oder ähnliche, die man dann in der docker-compose nur eintragen muss. Der Aufwand rust und dann cyprtography und dann fhempy manuell zu installieren (plus pip Update) um Tuya zum Laufen zu bringen erscheint mir ziemlich groß.
Ich habe auch das Gefühl, dass bei der fhempy Installation irgendetwas nicht korrekt läuft. Irgendwie scheinen bestehende Pakete nicht durch neue ersetzt zu werden.
Sorry für die Kritik, ich hoffe das alles ist irgendwie meiner Konfiguration und Docker geschuldet.
Bei guten Ideen freue ich mich weiter zu testen...
pip3 install --upgrade fhempy
installiert alle Pakete die fhempy braucht automatisch. Man muss nichts manuell installieren.
Wenn du ein define machst, passiert das automatisch. Für mich ist immer noch unklar was nun Teil vom Docker ist und was nicht? Ist /opt/fhem automatisch von Docker erstellt? Wenn ja, wird es bei jedem Neustart neu erstellt?
In deinem Fall nun...
du hast etwas manuell gelöscht, nämlich /opt/fhem/FHEM/bin/fhempy, das wird über ein update in FHEM installiert. Daher müsstest du nun ein Update machen, damit das wieder installiert wird und danach ein define fhempy_local
Hallo erstmal....
Ich stehe etwas auf dem schlauch
Ich habe soweit alles hinbekommen aber irgendwie bekomme ich bei den Heizungs Thermostaten
nur ein ready angezeigt was mache ich da falsch
ich möchte gerne die Temperatur angezeigt bekommen und den Status
shut down restart gemacht?
und lange warten; dann kommen auch die schönen Icons zum Anzeigen und Schalten
Ja Neustart komplett sowohl den pi als auch fhem diverse male, alles leider ohne erfolg.
Keine icons ☹
Ich wird noch verrückt mit dem ding
Poste mal was bei den Heizungsthermostaten kommt. Screenshot oder Kopie fürs Forum.
hallo.
nach gestrigem update. klappt die cloud nicht mehr.
beispiel:
Failed to execute function Define: Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 169, in _new_conn
conn = connection.create_connection(
File "/usr/lib/python3/dist-packages/urllib3/util/connection.py", line 73, in create_connection
for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
File "/usr/lib/python3.9/socket.py", line 953, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -3] Temporary failure in name resolution
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 699, in urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 382, in _make_request
self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 1012, in _validate_conn
conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 353, in connect
conn = self._new_conn()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 181, in _new_conn
raise NewConnectionError(
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPSConnection object at 0x747d5910>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/requests/adapters.py", line 439, in send
resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 755, in urlopen
retries = retries.increment(
File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 574, in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='openapi.tuyaeu.com', port=443): Max retries exceeded with url: /v1.0/token?grant_type=1 (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x747d5910>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 367, in handle_function
ret = await self.execute_function(hash, fhem_reply_done, nmInstance)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 438, in execute_function
ret = await asyncio.wait_for(
File "/usr/lib/python3.9/asyncio/tasks.py", line 481, in wait_for
return fut.result()
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 85, in Define
await self.setup_cloud()
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 93, in setup_cloud
self.tuya_cloud = await utils.run_blocking(
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/utils.py", line 62, in run_blocking
return await asyncio.get_event_loop().run_in_executor(pool, function)
File "/usr/lib/python3.9/concurrent/futures/thread.py", line 52, in run
result = self.fn(*self.args, **self.kwargs)
File "/opt/fhem/.local/lib/python3.9/site-packages/tinytuya/Cloud.py", line 96, in __init__
self.token = self._gettoken()
File "/opt/fhem/.local/lib/python3.9/site-packages/tinytuya/Cloud.py", line 201, in _gettoken
response_dict = self._tuyaplatform('token?grant_type=1')
File "/opt/fhem/.local/lib/python3.9/site-packages/tinytuya/Cloud.py", line 162, in _tuyaplatform
response = requests.get(url, headers=headers)
File "/opt/fhem/.local/lib/python3.9/site-packages/requests/api.py", line 75, in get
return request('get', url, params=params, **kwargs)
File "/opt/fhem/.local/lib/python3.9/site-packages/requests/api.py", line 61, in request
return session.request(method=method, url=url, **kwargs)
File "/opt/fhem/.local/lib/python3.9/site-packages/requests/sessions.py", line 542, in request
resp = self.send(prep, **send_kwargs)
File "/opt/fhem/.local/lib/python3.9/site-packages/requests/sessions.py", line 655, in send
r = adapter.send(request, **kwargs)
File "/opt/fhem/.local/lib/python3.9/site-packages/requests/adapters.py", line 516, in send
raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='openapi.tuyaeu.com', port=443): Max retries exceeded with url: /v1.0/token?grant_type=1 (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x747d5910>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))
und hier eine steckdose
Failed to execute function Define: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 169, in _new_conn conn = connection.create_connection( File "/usr/lib/python3/dist-packages/urllib3/util/connection.py", line 73, in create_connection for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM): File "/usr/lib/python3.9/socket.py", line 953, in getaddrinfo for res in _socket.getaddrinfo(host, port, family, type, proto, flags): socket.gaierror: [Errno -3] Temporary failure in name resolution During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 699, in urlopen httplib_response = self._make_request( File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 382, in _make_request self._validate_conn(conn) File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 1012, in _validate_conn conn.connect() File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 353, in connect conn = self._new_conn() File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 181, in _new_conn raise NewConnectionError( urllib3.exceptions.NewConnectionError: : Failed to establish a new connection: [Errno -3] Temporary failure in name resolution During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/fhem/.local/lib/python3.9/site-packages/requests/adapters.py", line 439, in send resp = conn.urlopen( File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 755, in urlopen retries = retries.increment( File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 574, in increment raise MaxRetryError(_pool, url, error or ResponseError(cause)) urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='openapi.tuyaeu.com', port=443): Max retries exceeded with url: /v1.0/token?grant_type=1 (Caused by NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 367, in handle_function ret = await self.execute_function(hash, fhem_reply_done, nmInstance) File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 438, in execute_function ret = await asyncio.wait_for( File "/usr/lib/python3.9/asyncio/tasks.py", line 481, in wait_for return fut.result() File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 85, in Define await self.setup_cloud() File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 93, in setup_cloud self.tuya_cloud = await utils.run_blocking( File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/utils.py", line 62, in run_blocking return await asyncio.get_event_loop().run_in_executor(pool, function) File "/usr/lib/python3.9/concurrent/futures/thread.py", line 52, in run result = self.fn(*self.args, **self.kwargs) File "/opt/fhem/.local/lib/python3.9/site-packages/tinytuya/Cloud.py", line 96, in __init__ self.token = self._gettoken() File "/opt/fhem/.local/lib/python3.9/site-packages/tinytuya/Cloud.py", line 201, in _gettoken response_dict = self._tuyaplatform('token?grant_type=1') File "/opt/fhem/.local/lib/python3.9/site-packages/tinytuya/Cloud.py", line 162, in _tuyaplatform response = requests.get(url, headers=headers) File "/opt/fhem/.local/lib/python3.9/site-packages/requests/api.py", line 75, in get return request('get', url, params=params, **kwargs) File "/opt/fhem/.local/lib/python3.9/site-packages/requests/api.py", line 61, in request return session.request(method=method, url=url, **kwargs) File "/opt/fhem/.local/lib/python3.9/site-packages/requests/sessions.py", line 542, in request resp = self.send(prep, **send_kwargs) File "/opt/fhem/.local/lib/python3.9/site-packages/requests/sessions.py", line 655, in send r = adapter.send(request, **kwargs) File "/opt/fhem/.local/lib/python3.9/site-packages/requests/adapters.py", line 516, in send raise ConnectionError(e, request=request) requests.exceptions.ConnectionError: HTTPSConnectionPool(host='openapi.tuyaeu.com', port=443): Max retries exceeded with url: /v1.0/token?grant_type=1 (Caused by NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))
Da dürfte es Probleme mit der Namensauflösung geben:
socket.gaierror: [Errno -3] Temporary failure in name resolution
sah das update vorhanden ist, fehler weg.
Ich habe nach wie vor Probleme mein fhempy wieder ans Laufen zu bringen.
Überall wird immer nur Python Server Offline angezeigt.
Jetzt habe ich probiert alles neu zu erstellen, dabei ist mir dann aufgefallen, dass ich mit
define fhempy_local BindingsIo fhempykein Device erstellen kann. Rückmeldung von Fhem ist immer, Device existiert bereits und ist in Verwendung.
Ändere ich das define in modify gibt Fhem aber komischerweise zurück ich sollte erst das Device erstellen.
Das passt doch nicht, oder?
Das Problem scheint bei mir auch in einem Device Namens "local_pybinding" zu stecken, dass sich überhaupt nicht mehr bearbeiten lässt. Weder Update noch Restart haben irgendeine Wirkung. Unter Device Name wird "ws:localhost:15733" angezeigt. Kann es sein, dass der Port erst freigegeben werden muss?
Ich bekomme beim "local_pybinding"-Device bei "prev_error" ein "DNS 127.0.0.11 timed out" angezeigt.
Wieso 127.0.0.11? - sonst ist localhost doch immer mit 127.0.0.1 angegeben.
Klingt danach, als hättest du in deine /etc/hosts Datei localhost auf 127.0.0.11 gemappt statt 127.0.0.1.
Was passiert wenn du fhempy_local löscht? Das sollte ja möglich sein.
also bewusst gemappt habe ich nichts. Fiel mir auch erst auf den 10 Blick auf.
Keine Ahnung ob das relevant ist, aber bei mir heißt das Device local_fhempy - also genau anders herum. Habe aber nichts beim anlegen umbenannt oder so.
Das löschen des device macht jedenfalls keinerlei Veränderung. Die STATE's der betroffenen Devices zeigen immer noch "Python Server Offline" an.
Bei einem Neustart des Fhem-Servers habe ich im Startlog wieder diesen Eintrag gefunden:
fhempy_local: Can't connect to ws:localhost:15733: DNS 127.0.0.11 timed out
Wo kommt das 127.0.0.11 her und wie kann ich es wieder auf 1 zurücksetzen?
Komisch irgendwie hat er die zweite Antwort geschluckt.
Habe das Device gelöscht und neu angelegt. Das Device zeigt zwar jetzt den grünen Punkt an, im STATE steht aber "Installing fhempy (15min)..." und alle Geräte Devices - egal ob TUYA oder Googlecast zeigen weiterhin "Python Server offline" an.
hallo zusammen
inzwischen habe ich fast auf tuya-local umgestellt-
Das DEF für tuya-cloud hatte ich herausgenommen, da dieses "ungefragt" immer wieder alle Devices eingelesen und DB-logs geschrieben hatte.
Kann man das Einlesen auf nur gewünschte Geräte begrenzen? z.B. nur Thermostate oder nur ZIG-Bee Geräte (die ja von tuya-local nicht unterstützt werden ; richtig?)
Ich frage auch unter dem Hintergrund meines neuesten Testkaufs: https://www.amazon.de/gp/product/B09PQW3H85/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 (https://www.amazon.de/gp/product/B09PQW3H85/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1)
ein Tuya-BT und ZIG-Bee Gateway:
【Fernbedienungsfunktion】 Das drahtlose Smart-Home-Bridge-Gateway ist mit Smart Life und der Tuya-App verbunden, sodass Sie Ihre Smart-Home-Geräte auch dann, wenn Sie weit weg von zu Hause sind, überall und jederzeit per Smartphone fernsteuern können.
【Einfache Einrichtung】 Stecken Sie einfach das drahtlose Smart-Gateway in die Steckdose, öffnen Sie die App, das hinzuzufügende Gateway wird automatisch angezeigt, Sie klicken einfach auf "Hinzufügen", um die Kopplungseinstellung abzuschließen, dann können Sie dem Gateway weitere Smart-Home-Geräte hinzufügen.
【Kompatibel Mit Allen Tuya Smart-GeräTen】 Das Gateway ist ein notwendiges Gerät für alle Tuya Smart-Home-Geräte. Es kann nicht nur Bluetooth-Smart-Geräte, sondern auch Zigbee-Smart-Geräte hinzufügen, so dass es eine stabile Verbindung und automatische Steuerung für alle Tuya Smart-Geräte bietet Geräte.
【3 Modi In 1 Gateway】 Das drahtlose Smart Gateway verfügt über 3 Modi in 1 Gateway, es ist in den Modi Bluetooth 5.0, WLAN 2.4G und ZigBee 3.0 verfügbar, so dass es einen breiten Anwendungsbereich hat, Sie können Bluetooth-Geräte und Zigbee-Geräte steuern in einem intelligenten Gateway.
【Hinweis Und Anleitung】 Dieser Smart-Home-Hub verbindet sich mit maximal bis zu 128 Geräten. Die Nutzungsvoraussetzung erfordert eine 2,4-G-WLAN-Frequenzverbindung. Bitte überprüfen Sie vor dem Kauf die Kompatibilität. Wenn Sie Probleme haben, können Sie sich gerne an uns wenden.
das müsste doch von tuya_cloud gefunden werden?
Gibt es Erfahrungen mit diesem Gateway?
Hallo zusammen,
soweit ich gelesen habe muss für Tuya Cloud mind. Python Version 3.8 installiert sein. Da ich noch eine ältere Version auf meinem Raspi (Buster) hatte,
habe ich auf Python 3.8.5 upgedatet.
Jetzt läuft das bindingIo nicht mehr.
Im Log von fhem wiederholt sich immer wieder jede Minute:
2023.01.13 12:59:47 3: Pythonbinding_15733: read: end of file reached while sysread
2023.01.13 12:59:47 3: Pythonbinding_15733: stopped
2023.01.13 12:59:47 3: Pythonbinding_15733: starting
2023.01.13 12:59:47 3: Pythonbinding_15733: using logfile: ./log/fhempy-2023-01-13.log
Im Log von fhempy steht:
2023-01-13 13:05:57,318 - ERROR - __main__: Failed to install fhempy, exit now...
2023-01-13 13:06:57,609 - ERROR - __main__: Failed to load fhempy
Traceback (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 139, in <module>
import fhempy.lib.fhem_pythonbinding as fpb
ModuleNotFoundError: No module named 'fhempy'
2023-01-13 13:06:57,609 - INFO - __main__: Attempting install of fhempy>=0.1.462
2023-01-13 13:06:58,764 - ERROR - __main__: Unable to install package fhempy>=0.1.462: ERROR: Exception:
Traceback (most recent call last):
File "/usr/lib/python3.8/site-packages/pip/_internal/cli/base_command.py", line 188, in _main
status = self.run(options, args)
File "/usr/lib/python3.8/site-packages/pip/_internal/cli/req_command.py", line 185, in wrapper
return func(self, options, args)
File "/usr/lib/python3.8/site-packages/pip/_internal/commands/install.py", line 278, in run
session = self.get_default_session(options)
File "/usr/lib/python3.8/site-packages/pip/_internal/cli/req_command.py", line 83, in get_default_session
self._session = self.enter_context(self._build_session(options))
File "/usr/lib/python3.8/site-packages/pip/_internal/cli/req_command.py", line 93, in _build_session
session = PipSession(
File "/usr/lib/python3.8/site-packages/pip/_internal/network/session.py", line 249, in __init__
self.headers["User-Agent"] = user_agent()
File "/usr/lib/python3.8/site-packages/pip/_internal/network/session.py", line 132, in user_agent
zip(["name", "version", "id"], distro.linux_distribution()),
File "/usr/lib/python3.8/site-packages/pip/_vendor/distro.py", line 125, in linux_distribution
return _distro.linux_distribution(full_distribution_name)
File "/usr/lib/python3.8/site-packages/pip/_vendor/distro.py", line 681, in linux_distribution
self.version(),
File "/usr/lib/python3.8/site-packages/pip/_vendor/distro.py", line 741, in version
self.lsb_release_attr('release'),
File "/usr/lib/python3.8/site-packages/pip/_vendor/distro.py", line 903, in lsb_release_attr
return self._lsb_release_info.get(attribute, '')
File "/usr/lib/python3.8/site-packages/pip/_vendor/distro.py", line 556, in __get__
ret = obj.__dict__[self._fname] = self._f(obj)
File "/usr/lib/python3.8/site-packages/pip/_vendor/distro.py", line 1014, in _lsb_release_info
stdout = subprocess.check_output(cmd, stderr=devnull)
File "/usr/lib/python3.8/subprocess.py", line 411, in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.8/subprocess.py", line 512, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '('lsb_release', '-a')' returned non-zero exit status 1.
Traceback (most recent call last):
File "/usr/lib/python3.8/runpy.py", line 194, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/lib/python3.8/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/usr/lib/python3.8/site-packages/pip/__main__.py", line 26, in <module>
sys.exit(_main())
File "/usr/lib/python3.8/site-packages/pip/_internal/cli/main.py", line 75, in main
return command.main(cmd_args)
File "/usr/lib/python3.8/site-packages/pip/_internal/cli/base_command.py", line 114, in main
return self._main(args)
File "/usr/lib/python3.8/site-packages/pip/_internal/cli/base_command.py", line 226, in _main
self.handle_pip_version_check(options)
File "/usr/lib/python3.8/site-packages/pip/_internal/cli/req_command.py", line 152, in handle_pip_version_check
session = self._build_session(
File "/usr/lib/python3.8/site-packages/pip/_internal/cli/req_command.py", line 93, in _build_session
session = PipSession(
File "/usr/lib/python3.8/site-packages/pip/_internal/network/session.py", line 249, in __init__
self.headers["User-Agent"] = user_agent()
File "/usr/lib/python3.8/site-packages/pip/_internal/network/session.py", line 132, in user_agent
zip(["name", "version", "id"], distro.linux_distribution()),
File "/usr/lib/python3.8/site-packages/pip/_vendor/distro.py", line 125, in linux_distribution
return _distro.linux_distribution(full_distribution_name)
File "/usr/lib/python3.8/site-packages/pip/_vendor/distro.py", line 681, in linux_distribution
self.version(),
File "/usr/lib/python3.8/site-packages/pip/_vendor/distro.py", line 741, in version
self.lsb_release_attr('release'),
File "/usr/lib/python3.8/site-packages/pip/_vendor/distro.py", line 903, in lsb_release_attr
return self._lsb_release_info.get(attribute, '')
File "/usr/lib/python3.8/site-packages/pip/_vendor/distro.py", line 556, in __get__
ret = obj.__dict__[self._fname] = self._f(obj)
File "/usr/lib/python3.8/site-packages/pip/_vendor/distro.py", line 1014, in _lsb_release_info
stdout = subprocess.check_output(cmd, stderr=devnull)
File "/usr/lib/python3.8/subprocess.py", line 411, in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.8/subprocess.py", line 512, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '('lsb_release', '-a')' returned non-zero exit status 1.
2023-01-13 13:06:58,764 - ERROR - __main__: Failed to install fhempy, exit now...
Was habe ich kaputt gemacht?
Grüße
ergerd
Ich bin etwas weiter gekommen in dem ich die erste Zeile von /usr/bin/lsb_release auf python3.7 geändert habe.
Im fhempi Log steht jetzt:
2023-01-13 14:48:34,954 - ERROR - __main__: Failed to load fhempy
Traceback (most recent call last):
File "FHEM/bindings/python/bin/fhempy", line 139, in <module>
import fhempy.lib.fhem_pythonbinding as fpb
ModuleNotFoundError: No module named 'fhempy'
2023-01-13 14:48:34,955 - INFO - __main__: Attempting install of fhempy>=0.1.462
2023-01-13 14:48:41,348 - ERROR - __main__: Unable to install package fhempy>=0.1.462: ERROR: Could not find a version that sati$
ERROR: No matching distribution found for bluetooth-adapters==0.15.2 (from fhempy>=0.1.462)
WARNING: You are using pip version 20.1.1; however, version 22.3.1 is available.
You should consider upgrading via the '/usr/bin/python3 -m pip install --upgrade pip' command.
2023-01-13 14:48:41,349 - ERROR - __main__: Failed to install fhempy, exit now...
Hat sich erledigt, ich habe meinen Raspi mit Bullseye neu aufgesetzt.
Hallo zusammen,
ich bekomme via tuya_cloud die Daten von meinen aqara Temperatur und Luftfeuchte Sensoren.
Das klappt auch wunderbar jedoch ist das Reading va_battery immer 0.0
Ist da etwas bekannt? Irgendwo noch ein Bug? Kann ich etwas tun?
Danke und Grüße
ergerd
hallo zusammen
inzwischen habe ich meine 60 TUYA-Devices in cloud und local mühsam angepasst (unter anderem dblogexclude .* gesetzt)
Nun legt FHEM mehrminütige Pausen ein, bis es überhaupt startet und eiert ca. 10 minute bis es den Raum fhempy anzeigt.
das habe ich im fhempi-log (auszug ab Zeile 22600!):
2023-01-15 20:26:31,691 - ERROR - TUYA_JL03: Exception raised by task: <Task finished name='Task-25425' coro=<FhemModule._run_coro() done, defined at /opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/generic.py:194> exception=RuntimeError('Lock is not acquired.') created at /usr/lib/python3.9/asyncio/tasks.py:361>
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/generic.py", line 202, in _handle_task_result
task.result()
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/generic.py", line 196, in _run_coro
await coro
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 400, in async_status_updated
await self.update_readings(status)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 685, in update_readings
await fhem.readingsEndUpdate(self.hash, 1)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 166, in readingsEndUpdate
update_locks[hash["NAME"]].release()
File "/usr/lib/python3.9/asyncio/locks.py", line 146, in release
raise RuntimeError('Lock is not acquired.')
RuntimeError: Lock is not acquired.
2023-01-15 20:26:31,783 - WARNING - asyncio: socket.send() raised exception.
2023-01-15 20:26:31,784 - WARNING - asyncio: socket.send() raised exception.
2023-01-15 20:26:31,789 - WARNING - asyncio: socket.send() raised exception.
2023-01-15 20:26:31,791 - WARNING - asyncio: socket.send() raised exception.
2023-01-15 20:26:35,376 - WARNING - asyncio: socket.send() raised exception.
2023-01-15 20:26:36,215 - WARNING - asyncio: Executing <Task pending name='Task-7557' coro=<main() running at /opt/fhem/.local/lib/python3.9/site-packages/tinytuya/__init__.py:247> wait_for=<Future pending cb=[BaseSelectorEventLoop._sock_write_done(24, handle=<Handle BaseS...events.py:296>)(), <TaskWakeupMethWrapper object at 0xb25ed9b8>()] created at /usr/lib/python3.9/asyncio/base_events.py:424> created at /usr/lib/python3.9/asyncio/tasks.py:361> took 0.101 seconds
2023-01-15 20:26:36,228 - WARNING - asyncio: socket.send() raised exception.
2023-01-15 20:26:36,243 - WARNING - asyncio: socket.send() raised exception.
2023-01-15 20:26:36,250 - WARNING - asyncio: socket.send() raised exception.
2023-01-15 20:26:36,272 - WARNING - asyncio: socket.send() raised exception.
2023-01-15 20:26:36,306 - WARNING - asyncio: socket.send() raised exception.
was läuft da wohl schief?
wie kann ich denn Fhempy temporär deaktivieren?
kennt niemand eine Lösungsmöglichkeit?
ich habe mich nur so behelfen können:
# ausgeblendet 2023-01-15
# define TUYA fhempy tuya_cloud setup xxxxxxxxxxx
# setuuid TUYA 63bea76c-f33f-fd5f-f922-b863332c636feb8b
# attr TUYA group TUYA
# attr TUYA room TUYA
# attr TUYA verbose 1
also durch schlichtes Auskommentieren.
natürlich sind damit alle tuya_cloud Devices noch da, die ich händisch löschen müsste. Sie bescheren mir wohl immer noch Performance-Probleme
Behalten möchte ich nur die Temperatur.Devices per ZigBee.
Wenn ich # wieder wegnehme liest tuya-cloud ja wieder alle Devices ein.
Wie kann ich also
a) alle tuya_cloud devices entfernen
b) nur bestimmte tuya_cloud-devices wieder zufügen?
edit:
a) konnte ich so selbst lösen:
list PYTHONTYPE=tuya_cloud
delete PYTHONTYPE=tuya_cloud
b) habe keinen Plan. Wenn ich autocreate ausschalte, wie kriege ich die Gewünschten ? es gibt ja kein create_device
Grüße
Thomas
Guten Morgen Dominik,
wie könnte ich es bewerkstelligen, dass nur 2 neue ZigBee-devices von tuya_cloud eingelesen werden.
Sobald ich Tuya_cloud ja aktiviere, holt es ja ungefragt ALLE TUYA-Devices aus der Cloud.
Die ZigBee-Temperatur-Devices sind inzwischen sehr günstig geworden. Die Datenhistorie wird in Smart-Live wunderbar angezeigt. Ich möchte das in FHEM nachführen.
Hoffe auf baldige Hinweise
Zitat von: dominik am 21 Januar 2023, 10:00:44
Aktuell gar nicht. Nach einem Neustart werden die automatisch wieder angelegt. Das muss ich noch umbauen.
Bitte für tuya_cloud den anderen Threads verwenden ;)
dann brauche ich noch Geduld ;-) und hoffe auch baldige Implementiertierung.
Es könnte ja wie bei den locals durch ein Aktiv/inaktiv-Attribut gehen ?
Da die devices ja sehr,sehr gesprächig sind, führt das zu nicht unerheblichen Performance-Problemen.
Kann man das Polling im Sekundentakt irgendwie beeinflussen?
Ist die Frage was sinnvoller ist? Am schönsten wäre eine Übersicht aller Geräte, wo man dann per Click das Gerät anlegt. Weil danach per disable zu deaktivieren ist wahrscheinlich umständlicher.
Es gibt bei tuya_cloud kein Polling. Es wird eine Verbindung zur tuya Cloud aufgebaut und die meldet die Events. Sollte aber nicht so sein, dass da minütlich was rein kommt. Bei welchen Devices passiert das?
Zitat von: dominik am 21 Januar 2023, 10:57:53
Es gibt bei tuya_cloud kein Polling. Es wird eine Verbindung zur tuya Cloud aufgebaut und die meldet die Events. Sollte aber nicht so sein, dass da minütlich was rein kommt. Bei welchen Devices passiert das?
Events (Filter: fhempy.*) FHEM log ResetCreate/Modify Device
2023-01-21 11:40:17 fhempy TUYA_SP08 cur_voltage: 228.8
2023-01-21 11:40:17 fhempy TUYA_SP07 cur_voltage: 223.7
2023-01-21 11:40:17 fhempy TUYA_SP11 cur_current: 78.0
2023-01-21 11:40:17 fhempy TUYA_SP11 cur_power: 8.7
2023-01-21 11:40:17 fhempy TUYA_SP13 cur_current: 358.0
2023-01-21 11:40:17 fhempy TUYA_SP13 cur_power: 45.6
2023-01-21 11:40:17 fhempy TUYA_SP13 cur_voltage: 228.3
2023-01-21 11:40:17 fhempy TUYA_SP14 cur_current: 116.0
2023-01-21 11:40:17 fhempy TUYA_SP14 cur_power: 15.0
2023-01-21 11:40:17 fhempy TUYA_SP16 cur_power: 1.5
2023-01-21 11:40:17 fhempy TUYA_SP16 cur_voltage: 227.6
2023-01-21 11:40:18 fhempy TUYA_SP14 cur_current: 119.0
2023-01-21 11:40:18 fhempy TUYA_SP14 cur_power: 12.1
2023-01-21 11:40:18 fhempy TUYA_SP14 cur_voltage: 230.3
2023-01-21 11:40:18 fhempy TUYA_SP15 cur_current: 18.0
2023-01-21 11:40:18 fhempy TUYA_SP15 cur_power: 2.6
2023-01-21 11:40:18 fhempy TUYA_SP15 cur_voltage: 228.3
2023-01-21 11:40:18 fhempy TUYA_SP16 cur_power: 1.6
2023-01-21 11:40:18 fhempy TUYA_SP11 cur_current: 73.0
2023-01-21 11:40:18 fhempy TUYA_SP11 cur_power: 8.0
2023-01-21 11:40:18 fhempy TUYA_Temp4 va_temperature: 18.8
2023-01-21 11:40:18 fhempy TUYA_Temp4 temp_unit_convert: 0
2023-01-21 11:40:18 fhempy TUYA_Temp4 dp_18: 119
2023-01-21 11:40:18 fhempy TUYA_Temp4 dp_19: 121
2023-01-21 11:40:18 fhempy TUYA_Temp4 dp_20: 2303
2023-01-21 11:40:18 fhempy TUYA_Temp4 dp_21: 1
2023-01-21 11:40:18 fhempy TUYA_Temp4 dp_22: 715
2023-01-21 11:40:18 fhempy TUYA_Temp4 dp_23: 30666
2023-01-21 11:40:18 fhempy TUYA_Temp4 dp_24: 20680
2023-01-21 11:40:18 fhempy TUYA_Temp4 dp_25: 1010
2023-01-21 11:40:18 fhempy TUYA_Temp4 va_humidity: 43.0
2023-01-21 11:40:18 fhempy TUYA_Temp4 online: 1
2023-01-21 11:40:18 fhempy TUYA_Temp4 ready
2023-01-21 11:40:20 fhempy TUYA_Temp3 va_temperature: 18.8
2023-01-21 11:40:20 fhempy TUYA_Temp3 temp_unit_convert: 0
2023-01-21 11:40:20 fhempy TUYA_Temp3 dp_18: 119
2023-01-21 11:40:20 fhempy TUYA_Temp3 dp_19: 121
2023-01-21 11:40:20 fhempy TUYA_Temp3 dp_20: 2303
2023-01-21 11:40:20 fhempy TUYA_Temp3 dp_21: 1
2023-01-21 11:40:20 fhempy TUYA_Temp3 dp_22: 715
2023-01-21 11:40:20 fhempy TUYA_Temp3 dp_23: 30666
2023-01-21 11:40:20 fhempy TUYA_Temp3 dp_24: 20680
2023-01-21 11:40:20 fhempy TUYA_Temp3 dp_25: 1010
2023-01-21 11:40:20 fhempy TUYA_Temp3 va_humidity: 43.0
2023-01-21 11:40:20 fhempy TUYA_Temp3 online: 1
2023-01-21 11:40:20 fhempy TUYA_Temp3 ready
2023-01-21 11:40:20 fhempy TUYA_Temp5 va_temperature: 18.8
2023-01-21 11:40:20 fhempy TUYA_Temp5 temp_unit_convert: 0
2023-01-21 11:40:20 fhempy TUYA_Temp5 dp_18: 119
2023-01-21 11:40:20 fhempy TUYA_Temp5 dp_19: 121
2023-01-21 11:40:20 fhempy TUYA_Temp5 dp_20: 2303
2023-01-21 11:40:20 fhempy TUYA_Temp5 dp_21: 1
2023-01-21 11:40:20 fhempy TUYA_Temp5 dp_22: 715
2023-01-21 11:40:20 fhempy TUYA_Temp5 dp_23: 30666
2023-01-21 11:40:20 fhempy TUYA_Temp5 dp_24: 20680
2023-01-21 11:40:20 fhempy TUYA_Temp5 dp_25: 1010
2023-01-21 11:40:20 fhempy TUYA_Temp5 va_humidity: 43.0
2023-01-21 11:40:20 fhempy TUYA_Temp5 online: 1
2023-01-21 11:40:20 fhempy TUYA_Temp5 ready
2023-01-21 11:40:20 fhempy TUYA_SP15 cur_power: 2.4
2023-01-21 11:40:20 fhempy TUYA_SP14 cur_current: 101.0
2023-01-21 11:40:20 fhempy TUYA_SP14 cur_power: 12.0
2023-01-21 11:40:21 fhempy TUYA_SP14 cur_current: 119.0
2023-01-21 11:40:21 fhempy TUYA_SP14 cur_power: 11.9
2023-01-21 11:40:26 fhempy TUYA_SP13 cur_current: 354.0
2023-01-21 11:40:26 fhempy TUYA_SP13 cur_power: 42.9
2023-01-21 11:40:26 fhempy TUYA_SP01 cur_voltage: 228.2
2023-01-21 11:40:30 fhempy TUYA_SP11 cur_current: 71.0
2023-01-21 11:40:30 fhempy TUYA_SP11 cur_power: 7.3
2023-01-21 11:40:30 fhempy TUYA_SP11 cur_voltage: 229.9
2023-01-21 11:40:31 fhempy TUYA_SP16 cur_power: 1.7
2023-01-21 11:40:31 fhempy TUYA_SP16 cur_voltage: 228.3
2023-01-21 11:40:32 fhempy TUYA_SP11 cur_power: 8.1
2023-01-21 11:40:32 fhempy TUYA_SP14 cur_current: 122.0
2023-01-21 11:40:32 fhempy TUYA_SP14 cur_power: 12.8
2023-01-21 11:40:32 fhempy TUYA_SP14 cur_voltage: 228.3
2023-01-21 11:40:34 fhempy TUYA_Temp1 va_temperature: 16.9
2023-01-21 11:40:34 fhempy TUYA_Temp1 humidity_value: 34.0
2023-01-21 11:40:34 fhempy TUYA_SP14 cur_current: 117.0
2023-01-21 11:40:34 fhempy TUYA_SP14 cur_power: 12.0
2023-01-21 11:40:36 fhempy TUYA_SP15 cur_current: 16.0
2023-01-21 11:40:36 fhempy TUYA_SP15 cur_power: 2.2
2023-01-21 11:40:36 fhempy TUYA_SP15 cur_voltage: 228.6
2023-01-21 11:40:37 fhempy TUYA_SP16 cur_power: 1.6
2023-01-21 11:40:38 fhempy TUYA_SP11 cur_power: 7.5
2023-01-21 11:40:38 fhempy TUYA_SP15 cur_power: 2.4
2023-01-21 11:40:39 fhempy TUYA_SP16 cur_power: 1.7
2023-01-21 11:40:39 fhempy TUYA_SP14 cur_current: 116.0
2023-01-21 11:40:39 fhempy TUYA_SP14 cur_power: 10.5
2023-01-21 11:40:39 fhempy TUYA_SP14 cur_voltage: 230.3
2023-01-21 11:40:41 fhempy TUYA_SP14 cur_current: 117.0
2023-01-21 11:40:41 fhempy TUYA_SP14 cur_power: 12.4
2023-01-21 11:40:43 fhempy TUYA_SP11 cur_current: 74.0
2023-01-21 11:40:43 fhempy TUYA_SP11 cur_power: 8.1
2023-01-21 11:40:43 fhempy TUYA_SP11 cur_voltage: 230.3
2023-01-21 11:40:43 fhempy TUYA_SP05 cur_current: 54.0
2023-01-21 11:40:43 fhempy TUYA_SP05 cur_power: 5.7
2023-01-21 11:40:43 fhempy TUYA_SP05 cur_voltage: 210.1
2023-01-21 11:40:44 fhempy TUYA_SP16 cur_power: 1.6
2023-01-21 11:40:44 fhempy TUYA_SP16 cur_voltage: 229.3
2023-01-21 11:40:48 fhempy TUYA_SP11 cur_current: 71.0
2023-01-21 11:40:48 fhempy TUYA_SP11 cur_power: 7.6
2023-01-21 11:40:48 fhempy TUYA_SP15 cur_power: 2.2
2023-01-21 11:40:48 fhempy TUYA_SP15 cur_voltage: 226.0
2023-01-21 11:40:54 fhempy TUYA_Temp2 va_temperature: 18.7
2023-01-21 11:40:55 fhempy TUYA_SP16 cur_power: 1.5
2023-01-21 11:40:55 fhempy TUYA_SP16 cur_voltage: 225.6
2023-01-21 11:40:55 fhempy TUYA_SP15 cur_power: 2.0
2023-01-21 11:40:58 fhempy TUYA_SP05 cur_current: 52.0
2023-01-21 11:40:58 fhempy TUYA_SP05 cur_power: 5.4
2023-01-21 11:40:58 fhempy TUYA_SP05 cur_voltage: 208.0
2023-01-21 11:41:00 fhempy TUYA_SP15 cur_power: 2.3
2023-01-21 11:41:00 fhempy TUYA_SP15 cur_voltage: 227.0
2023-01-21 11:41:00 fhempy TUYA_SP05 cur_power: 5.1
2023-01-21 11:41:00 fhempy TUYA_SP14 cur_current: 116.0
2023-01-21 11:41:00 fhempy TUYA_SP14 cur_power: 11.1
2023-01-21 11:41:00 fhempy TUYA_SP14 cur_voltage: 228.3
2023-01-21 11:41:02 fhempy TUYA_SP14 cur_current: 118.0
2023-01-21 11:41:02 fhempy TUYA_SP14 cur_power: 12.2
2023-01-21 11:41:04 fhempy TUYA_SP16 cur_power: 1.6
2023-01-21 11:41:04 fhempy TUYA_SP16 cur_voltage: 227.3
2023-01-21 11:41:06 fhempy TUYA_SP05 cur_current: 53.0
2023-01-21 11:41:06 fhempy TUYA_SP05 cur_power: 5.4
2023-01-21 11:41:06 fhempy TUYA_SP05 cur_voltage: 209.5
2023-01-21 11:41:08 fhempy TUYA_SP03 cur_current: 177.0
2023-01-21 11:41:08 fhempy TUYA_SP03 cur_power: 26.1
2023-01-21 11:41:08 fhempy TUYA_SP03 cur_voltage: 212.5
2023-01-21 11:41:12 fhempy TUYA_SP14 cur_current: 117.0
2023-01-21 11:41:12 fhempy TUYA_SP14 cur_power: 12.9
2023-01-21 11:41:15 fhempy TUYA_SP16 cur_current: 15.0
2023-01-21 11:41:15 fhempy TUYA_SP16 cur_power: 1.7
2023-01-21 11:41:15 fhempy TUYA_SP16 cur_voltage: 228.6
2023-01-21 11:41:15 fhempy TUYA_SP05 cur_current: 55.0
2023-01-21 11:41:15 fhempy TUYA_SP05 cur_power: 5.7
2023-01-21 11:41:15 fhempy TUYA_SP05 cur_voltage: 211.0
2023-01-21 11:41:16 fhempy TUYA_SP11 cur_current: 77.0
2023-01-21 11:41:16 fhempy TUYA_SP11 cur_power: 8.8
2023-01-21 11:41:16 fhempy TUYA_SP11 cur_voltage: 229.9
2023-01-21 11:41:17 fhempy TUYA_SP11 cur_current: 74.0
2023-01-21 11:41:17 fhempy TUYA_SP11 cur_power: 8.2
2023-01-21 11:41:17 fhempy TUYA_SP16 cur_power: 1.5
2023-01-21 11:41:18 fhempy TUYA_SP14 cur_power: 12.2
2023-01-21 11:41:19 fhempy TUYA_SP16 cur_current: 14.0
2023-01-21 11:41:19 fhempy TUYA_SP16 cur_power: 1.6
2023-01-21 11:41:21 fhempy TUYA_SP16 cur_power: 1.5
2023-01-21 11:41:22 fhempy TUYA_SP11 cur_current: 71.0
2023-01-21 11:41:22 fhempy TUYA_SP11 cur_power: 7.5
2023-01-21 11:41:23 fhempy TUYA_SP16 cur_power: 1.6
2023-01-21 11:41:25 fhempy TUYA_SP16 cur_power: 1.5
2023-01-21 11:41:25 fhempy TUYA_SP16 cur_voltage: 229.3
2023-01-21 11:41:27 fhempy TUYA_SP16 cur_power: 1.7
2023-01-21 11:41:29 fhempy TUYA_SP16 cur_power: 1.6
2023-01-21 11:41:30 fhempy TUYA_SP05 cur_current: 52.0
2023-01-21 11:41:30 fhempy TUYA_SP05 cur_power: 5.3
2023-01-21 11:41:34 fhempy TUYA_SP16 cur_power: 1.7
2023-01-21 11:41:36 fhempy TUYA_SP16 cur_power: 1.6
2023-01-21 11:41:36 fhempy TUYA_SP16 cur_voltage: 228.6
2023-01-21 11:41:37 fhempy TUYA_SP11 cur_power: 7.9
2023-01-21 11:41:37 fhempy TUYA_SP11 cur_voltage: 230.3
2023-01-21 11:41:39 fhempy TUYA_SP11 cur_current: 73.0
2023-01-21 11:41:39 fhempy TUYA_SP11 cur_power: 8.5
2023-01-21 11:41:39 fhempy TUYA_Temp1 va_temperature: 16.8
2023-01-21 11:41:41 fhempy TUYA_SP11 cur_power: 8.0
2023-01-21 11:41:42 fhempy TUYA_SP16 cur_power: 1.5
2023-01-21 11:41:44 fhempy TUYA_SP05 cur_current: 55.0
2023-01-21 11:41:44 fhempy TUYA_SP05 cur_power: 5.8
2023-01-21 11:41:44 fhempy TUYA_SP05 cur_voltage: 211.5
2023-01-21 11:41:44 fhempy TUYA_SP16 cur_power: 1.7
2023-01-21 11:41:48 fhempy TUYA_SP11 cur_current: 78.0
2023-01-21 11:41:48 fhempy TUYA_SP11 cur_power: 9.0
2023-01-21 11:41:50 fhempy TUYA_SP16 cur_power: 1.6
2023-01-21 11:41:50 fhempy TUYA_SP16 cur_voltage: 229.3
2023-01-21 11:41:50 fhempy TUYA_SP11 cur_current: 76.0
2023-01-21 11:41:50 fhempy TUYA_SP11 cur_power: 8.5
2023-01-21 11:41:52 fhempy TUYA_SP11 cur_current: 73.0
2023-01-21 11:41:52 fhempy TUYA_SP11 cur_power: 8.0
2023-01-21 11:42:00 fhempy TUYA_SP05 cur_current: 52.0
2023-01-21 11:42:00 fhempy TUYA_SP05 cur_power: 5.4
2023-01-21 11:42:00 fhempy TUYA_SP05 cur_voltage: 212.1
2023-01-21 11:42:08 fhempy TUYA_SP15 cur_power: 2.1
2023-01-21 11:42:09 fhempy TUYA_SP11 cur_current: 75.0
2023-01-21 11:42:09 fhempy TUYA_SP11 cur_power: 8.5
2023-01-21 11:42:09 fhempy TUYA_SP11 cur_voltage: 229.3
2023-01-21 11:42:09 fhempy TUYA_SP15 cur_current: 17.0
2023-01-21 11:42:09 fhempy TUYA_SP15 cur_power: 2.3
2023-01-21 11:42:10 fhempy TUYA_SP14 cur_current: 120.0
2023-01-21 11:42:10 fhempy TUYA_SP14 cur_power: 13.5
2023-01-21 11:42:10 fhempy TUYA_SP14 cur_voltage: 228.6
2023-01-21 11:42:11 fhempy TUYA_SP16 cur_current: 15.0
2023-01-21 11:42:11 fhempy TUYA_SP16 cur_power: 1.7
2023-01-21 11:42:11 fhempy TUYA_SP16 cur_voltage: 228.3
2023-01-21 11:42:12 fhempy TUYA_SP14 cur_current: 121.0
2023-01-21 11:42:12 fhempy TUYA_SP14 cur_power: 12.2
2023-01-21 11:42:13 fhempy TUYA_SP16 cur_power: 1.6
2023-01-21 11:42:21 fhempy TUYA_SP16 cur_current: 14.0
2023-01-21 11:42:21 fhempy TUYA_SP16 cur_power: 1.4
2023-01-21 11:42:21 fhempy TUYA_SP16 cur_voltage: 229.3
2023-01-21 11:42:21 fhempy TUYA_SP11 cur_current: 80.0
2023-01-21 11:42:21 fhempy TUYA_SP11 cur_power: 9.3
2023-01-21 11:42:21 fhempy TUYA_SP11 cur_voltage: 230.3
2023-01-21 11:42:23 fhempy TUYA_SP16 cur_power: 1.6
2023-01-21 11:42:23 fhempy TUYA_SP11 cur_current: 76.0
2023-01-21 11:42:23 fhempy TUYA_SP11 cur_power: 8.5
2023-01-21 11:42:25 fhempy TUYA_SP16 cur_power: 1.7
2023-01-21 11:42:25 fhempy TUYA_SP11 cur_current: 73.0
2023-01-21 11:42:25 fhempy TUYA_SP11 cur_power: 7.9
2023-01-21 11:42:27 fhempy TUYA_SP16 cur_power: 1.6
2023-01-21 11:42:30 fhempy TUYA_SP15 cur_current: 16.0
2023-01-21 11:42:30 fhempy TUYA_SP15 cur_power: 2.1
2023-01-21 11:42:30 fhempy TUYA_SP15 cur_voltage: 228.6
2023-01-21 11:42:33 fhempy TUYA_SP06 cur_current: 109.0
2023-01-21 11:42:33 fhempy TUYA_SP06 cur_power: 18.5
2023-01-21 11:42:33 fhempy TUYA_SP06 cur_voltage: 245.6
2023-01-21 11:42:35 fhempy TUYA_SP06 cur_current: 112.0
2023-01-21 11:42:35 fhempy TUYA_SP06 cur_power: 19.5
2023-01-21 11:42:36 fhempy TUYA_SP16 cur_power: 1.5
2023-01-21 11:42:38 fhempy TUYA_SP16 cur_power: 1.7
2023-01-21 11:42:38 fhempy TUYA_SP15 cur_power: 2.3
2023-01-21 11:42:38 fhempy TUYA_SP15 cur_voltage: 227.0
2023-01-21 11:42:40 fhempy TUYA_SP16 cur_power: 1.5
2023-01-21 11:42:44 fhempy TUYA_SP05 cur_current: 55.0
2023-01-21 11:42:44 fhempy TUYA_SP05 cur_power: 5.7
2023-01-21 11:42:44 fhempy TUYA_SP05 cur_voltage: 211.5
2023-01-21 11:42:45 fhempy TUYA_SP16 cur_power: 1.6
2023-01-21 11:42:45 fhempy TUYA_SP16 cur_voltage: 228.6
2023-01-21 11:42:47 fhempy TUYA_SP16 cur_power: 1.5
2023-01-21 11:42:49 fhempy TUYA_SP16 cur_power: 1.7
2023-01-21 11:42:49 fhempy TUYA_SP15 cur_current: 21.0
2023-01-21 11:42:49 fhempy TUYA_SP15 cur_power: 2.4
2023-01-21 11:42:49 fhempy TUYA_SP15 cur_voltage: 227.6
2023-01-21 11:42:51 fhempy TUYA_SP16 cur_power: 1.8
2023-01-21 11:42:51 fhempy TUYA_SP15 cur_current: 18.0
2023-01-21 11:42:51 fhempy TUYA_SP15 cur_power: 2.5
2023-01-21 11:42:54 fhempy TUYA_SP11 cur_current: 77.0
2023-01-21 11:42:54 fhempy TUYA_SP11 cur_power: 8.8
2023-01-21 11:42:56 fhempy TUYA_SP16 cur_power: 1.5
2023-01-21 11:42:56 fhempy TUYA_SP16 cur_voltage: 229.3
2023-01-21 11:42:58 fhempy TUYA_SP16 cur_power: 1.6
2023-01-21 11:42:59 fhempy TUYA_SP05 cur_current: 52.0
2023-01-21 11:42:59 fhempy TUYA_SP05 cur_power: 5.3
2023-01-21 11:42:59 fhempy TUYA_SP05 cur_voltage: 211.0
2023-01-21 11:42:59 fhempy TUYA_SP11 cur_current: 72.0
2023-01-21 11:42:59 fhempy TUYA_SP11 cur_power: 7.9
2023-01-21 11:43:00 fhempy TUYA_SP16 cur_power: 1.7
2023-01-21 11:43:05 fhempy TUYA_SP16 cur_power: 1.6
2023-01-21 11:43:05 fhempy TUYA_SP16 cur_voltage: 228.6
2023-01-21 11:43:05 fhempy TUYA_Temp2 va_temperature: 18.8
2023-01-21 11:43:05 fhempy TUYA_SP15 cur_current: 16.0
2023-01-21 11:43:05 fhempy TUYA_SP15 cur_power: 2.2
2023-01-21 11:43:07 fhempy TUYA_SP15 cur_current: 21.0
[color=yellow]2023-01-21 11:43:07 fhempy TUYA_SP15 cur_power: 2.6[/color]
2023-01-21 11:43:13 fhempy TUYA_SP15 cur_current: 18.0
2023-01-21 11:43:13 fhempy TUYA_SP15 cur_power: 2.4
2023-01-21 11:43:14 fhempy TUYA_SP14 cur_current: 116.0
2023-01-21 11:43:14 fhempy TUYA_SP14 cur_power: 11.2
2023-01-21 11:43:14 fhempy TUYA_SP14 cur_voltage: 229.7
2023-01-21 11:43:16 fhempy TUYA_SP14 cur_power: 12.1
2023-01-21 11:43:19 fhempy TUYA_SP16 cur_power: 1.5
2023-01-21 11:43:19 fhempy TUYA_SP16 cur_voltage: 229.3
2023-01-21 11:43:22 fhempy TUYA_SP11 cur_current: 76.0
2023-01-21 11:43:22 fhempy TUYA_SP11 cur_power: 8.3
2023-01-21 11:43:22 fhempy TUYA_SP15 cur_current: 16.0
[color=yellow]2023-01-21 11:43:22 fhempy TUYA_SP15 cur_power: 2.2[/color]
2023-01-21 11:43:22 fhempy TUYA_SP15 cur_voltage: 229.3
2023-01-21 11:43:24 fhempy TUYA_SP16 cur_power: 1.6
2023-01-21 11:43:31 fhempy TUYA_SP16 cur_power: 1.7
2023-01-21 11:43:31 fhempy TUYA_SP16 cur_voltage: 229.9
2023-01-21 11:43:33 fhempy TUYA_SP16 cur_power: 1.6
2023-01-21 11:43:33 fhempy TUYA_SP15 cur_current: 17.0
2023-01-21 11:43:33 fhempy TUYA_SP15 cur_power: 2.4
2023-01-21 11:43:36 fhempy TUYA_SP15 cur_current: 16.0
[color=yellow]2023-01-21 11:43:36 fhempy TUYA_SP15 cur_power: 2.2[/color]
2023-01-21 11:43:40 fhempy TUYA_SP11 cur_current: 72.0
2023-01-21 11:43:40 fhempy TUYA_SP11 cur_power: 7.8
2023-01-21 11:43:40 fhempy TUYA_SP11 cur_voltage: 230.9
2023-01-21 11:43:44 fhempy TUYA_SP05 cur_current: 55.0
2023-01-21 11:43:44 fhempy TUYA_SP05 cur_power: 5.7
2023-01-21 11:43:44 fhempy TUYA_SP05 cur_voltage: 211.5
2023-01-21 11:43:44 fhempy TUYA_SP16 cur_power: 1.5
2023-01-21 11:43:46 fhempy TUYA_SP16 cur_power: 1.7
2023-01-21 11:43:51 fhempy TUYA_SP16 cur_power: 1.6
2023-01-21 11:43:51 fhempy TUYA_SP16 cur_voltage: 228.3
2023-01-21 11:43:52 fhempy TUYA_SP11 cur_current: 74.0
2023-01-21 11:43:52 fhempy TUYA_SP11 cur_power: 8.2
2023-01-21 11:43:52 fhempy TUYA_SP11 cur_voltage: 229.3
2023-01-21 11:43:53 fhempy TUYA_SP16 cur_power: 1.5
2023-01-21 11:43:58 fhempy TUYA_SP16 cur_power: 1.6
2023-01-21 11:44:00 fhempy TUYA_SP11 cur_current: 75.0
2023-01-21 11:44:00 fhempy TUYA_SP11 cur_power: 8.7
2023-01-21 11:44:00 fhempy TUYA_SP11 cur_voltage: 228.6
2023-01-21 11:44:01 fhempy TUYA_SP05 cur_current: 53.0
2023-01-21 11:44:01 fhempy TUYA_SP05 cur_power: 5.4
2023-01-21 11:44:01 fhempy TUYA_SP05 cur_voltage: 210.7
2023-01-21 11:44:04 fhempy TUYA_SP16 cur_power: 1.5
2023-01-21 11:44:05 fhempy TUYA_SP11 cur_current: 72.0
2023-01-21 11:44:05 fhempy TUYA_SP11 cur_power: 7.8
2023-01-21 11:44:06 fhempy TUYA_SP16 cur_power: 1.6
2023-01-21 11:44:07 fhempy TUYA_SP15 cur_current: 17.0
2023-01-21 11:44:07 fhempy TUYA_SP15 cur_power: 2.4
2023-01-21 11:44:07 fhempy TUYA_SP15 cur_voltage: 227.0
2023-01-21 11:44:09 fhempy TUYA_SP15 cur_current: 16.0
2023-01-21 11:44:09 fhempy TUYA_SP15 cur_power: 2.2
2023-01-21 11:44:11 fhempy TUYA_Temp2 va_temperature: 18.7
2023-01-21 11:44:19 fhempy TUYA_SP15 cur_power: 2.4
2023-01-21 11:44:21 fhempy TUYA_SP15 cur_power: 2.2
2023-01-21 11:44:22 fhempy TUYA_SP16 cur_power: 1.7
2023-01-21 11:44:22 fhempy TUYA_SP16 cur_voltage: 227.6
2023-01-21 11:44:22 fhempy TUYA_SP11 cur_current: 74.0
2023-01-21 11:44:22 fhempy TUYA_SP11 cur_power: 8.2
2023-01-21 11:44:22 fhempy TUYA_SP11 cur_voltage: 229.3
2023-01-21 11:44:24 fhempy TUYA_SP16 cur_power: 1.6
2023-01-21 11:44:29 fhempy TUYA_SP16 cur_power: 1.5
2023-01-21 11:44:33 fhempy TUYA_SP15 cur_current: 14.0
2023-01-21 11:44:33 fhempy TUYA_SP15 cur_power: 2.1
2023-01-21 11:44:33 fhempy TUYA_SP15 cur_voltage: 226.7
2023-01-21 11:44:34 fhempy TUYA_SP16 cur_power: 1.6
2023-01-21 11:44:35 fhempy TUYA_SP15 cur_current: 16.0
2023-01-21 11:44:35 fhempy TUYA_SP15 cur_power: 2.2
2023-01-21 11:44:44 fhempy TUYA_SP16 cur_power: 1.7
2023-01-21 11:44:44 fhempy TUYA_SP16 cur_voltage: 227.3das SP15 liefert eher im Sekundentakt ;-)
edit:
und FHEM ist (deshalb) wieder richtig unter Laste, seit ich die 16 SPs hereingenommen habe.
Diese messen die Ströme von großen Haushaltgeräten und Verbrauchergruppen wie Schreibtische etc.
Die Gesprächigkeit zu reduzieren wäre also wohl gut ;-)
Ok. Das sieht aber richtig aus, da sich die Werte auch ändern.
Du kannst ja event-min-change-intervall setzen, dann sollte es passen. Wie gesagt, sieht alles korrekt aus...oder übersehe ich was?
Zitat von: dominik am 21 Januar 2023, 10:57:53
Ist die Frage was sinnvoller ist? Am schönsten wäre eine Übersicht aller Geräte, wo man dann per Click das Gerät anlegt. Weil danach per disable zu deaktivieren ist wahrscheinlich umständlicher.
hmm zumindest bei mir werden die devices mit einigen Attributen und GPLOTs angereichert.
Wenn man also ein oder mehrere bereits definierte Devices aus einer Tabelle heraus aktivieren/deaktivieren könnte, wäre super
Zitat von: dominik am 21 Januar 2023, 12:15:14
Ok. Das sieht aber richtig aus, da sich die Werte auch ändern.
Du kannst ja event-min-change-intervall setzen, dann sollte es passen. Wie gesagt, sieht alles korrekt aus...oder übersehe ich was?
stimmt :-)
ich könnte z.B. auf
attr event-min-change-intervall .*:300 setzen ?
wofür stehen eigentlich diese DatenPunkte:
dp_02
43
2023-01-21 11:40:08
dp_04
0
2023-01-21 11:40:08
dp_21
1
2023-01-21 11:39:58
dp_22
715
2023-01-21 11:40:08
dp_23
30666
2023-01-21 11:40:08
dp_24
20680
2023-01-21 11:40:08
dp_25
1010
2023-01-21 11:40:08
dp_32
normal
2023-01-21 11:40:08
Lieber Dominik,
überhaupt wollte ich mich mal wieder herzlich für Dein unermüdliches Engagement bei den bockigen TUYA-Devices bedanken!!!!
Diese werden ja zunehmend interessanter.
Du musst neue device-Typen anhand ihrer Produkt-ID einzeln anpassen?
Gibt es dazu einen eigenen Thread von Dir, um die productid einzumelden?
Zitat von: thburkhart am 21 Januar 2023, 13:05:42
stimmt :-)
ich könnte z.B. auf attr event-min-change-intervall .*:300 setzen ?
wofür stehen eigentlich diese DatenPunkte:
dp_02
43
2023-01-21 11:40:08
dp_04
0
2023-01-21 11:40:08
dp_21
1
2023-01-21 11:39:58
dp_22
715
2023-01-21 11:40:08
dp_23
30666
2023-01-21 11:40:08
dp_24
20680
2023-01-21 11:40:08
dp_25
1010
2023-01-21 11:40:08
dp_32
normal
2023-01-21 11:40:08
Sind meistens interne Datenpunkte die nicht verwendet werden. Dazu gibt es aus der tuya Cloud auch keine Spezifikation, daher heißen die dann nur dp_...
Zitat von: thburkhart am 21 Januar 2023, 13:14:20
Lieber Dominik,
überhaupt wollte ich mich mal wieder herzlich für Dein unermüdliches Engagement bei den bockigen TUYA-Devices bedanken!!!!
Diese werden ja zunehmend interessanter.
Du musst neue device-Typen anhand ihrer Produkt-ID einzeln anpassen?
Gibt es dazu einen eigenen Thread von Dir, um die productid einzumelden?
Gerne!
Übrigens, bei den ZigBee Devices würde ich die zigbee2mqtt empfehlen, dann bist die Cloud komplett los.
Die productids muss ich nicht pflegen, solange alle die api Keys/secret verwenden, werden die Spezifikationen aus der tuya Cloud geholt. Nachdem man den localkey auch nur dort bekommt, sind die hinterlegten Mappings nur für die interessant, die den localkey bereits kennen und gar keine Cloud Anfrage machen wollen.
Zitat von: dominik am 21 Januar 2023, 13:54:54
Sind meistens interne Datenpunkte die nicht verwendet werden. Dazu gibt es aus der tuya Cloud auch keine Spezifikation, daher heißen die dann nur dp_...
und die sinnvollen versorgst du mit einem "sprechenden" Attribut, das dann auch zum reading wird?
was bedeutet dabei
cur_current und
add_ele genauer?
Zitat von: dominik am 21 Januar 2023, 13:58:32
Übrigens, bei den ZigBee Devices würde ich die zigbee2mqtt empfehlen, dann bist die Cloud komplett los.
ich kann diese Devices aber auch nur per tuya_cloud bekommen; richtig?
Hab mir ein Smart ir remote Model SRW-002-pro Fernbedienung zugelegt, diese auch in smartlife eingebunden und eine LED Lampe angelernt.
Funkt auch alles soweit
In fhem aber wird die Fernbedienung als "not support this device" und die LED nur in "ready" angezeigt und ich kann nichts weiter machen.
Jemand eine Idee ??
LED
Internals:
CFGFN
DEF tuya_cloud tuya_cloud_connector bf5a138aa791d117d0m3y3
DEVICEID bf5a138aa791d117d0m3y3
FHEMPYTYPE tuya_cloud
FUUID 63d01c36-f33f-c95d-33f2-c1abfeb2784ca604
IODev local_pybinding
NAME tuya_cloud_bf5a138aa791d117d0m3y3
NR 137612
PYTHONTYPE tuya_cloud
STATE ready
TYPE fhempy
eventCount 4
READINGS:
2023-01-24 19:08:17 active_time 1674583092
2023-01-24 19:08:17 biz_type 18
2023-01-24 19:08:17 category infrared_light
2023-01-24 19:08:17 create_time 1674583092
2023-01-24 19:08:17 icon https://images.tuyaeu.com/smart/icon/001453365846342fhj9e/76b9aaad801101a3a2cacb31ecca75ad.png
2023-01-24 19:08:17 id bf5a138aa791d117d0m3y3
2023-01-24 19:08:17 ip
2023-01-24 19:08:17 lat 48.6951
2023-01-24 18:58:15 local_key 3f108af73cbbf5a2
2023-01-24 19:08:17 lon 15.9707
2023-01-24 19:08:17 model
2023-01-24 19:08:17 name Light
2023-01-24 19:08:17 node_id 4d66801fd1205563
2023-01-24 19:08:17 online on
2023-01-24 19:08:17 owner_id 9189095
2023-01-24 19:08:17 product_id bca2coksogyhhhov
2023-01-24 19:08:17 product_name Light
2023-01-24 19:08:10 state ready
2023-01-24 19:08:17 sub on
2023-01-24 19:08:17 time_zone +01:00
2023-01-24 19:08:17 uid eu1577993184739WO7bA
2023-01-24 19:08:17 update_time 1674583259
2023-01-24 19:08:17 uuid bf5a138aa791d117d0m3y3
args:
tuya_cloud_bf5a138aa791d117d0m3y3
fhempy
tuya_cloud
tuya_cloud_connector
bf5a138aa791d117d0m3y3
argsh:
hmccu:
Attributes:
alias Light
group tuya_cloud
room fhempy
Fernbedienung
Internals:
CFGFN
DEF tuya_cloud tuya_cloud_connector bf097fa77d739cfc18wqgc
DEVICEID bf097fa77d739cfc18wqgc
FHEMPYTYPE tuya_cloud
FUUID 63d01adf-f33f-c95d-6a0d-d12a8f5a7d770a07
IODev local_pybinding
NAME tuya_cloud_bf097fa77d739cfc18wqgc
NR 137583
PYTHONTYPE tuya_cloud
STATE not support this device
TYPE fhempy
eventCount 6
READINGS:
2023-01-24 19:08:17 active_time 1674582750
2023-01-24 19:08:17 biz_type 18
2023-01-24 19:08:17 category wnykq
2023-01-24 19:08:17 create_time 1674582750
2023-01-24 19:08:17 icon https://images.tuyaeu.com/smart/icon/ay1506337792739cXrIR/a4d4883109fc3d535d0542a298a33b77.png
2023-01-24 19:08:17 id bf097fa77d739cfc18wqgc
2023-01-24 19:08:17 ip 62.46.103.185
2023-01-24 18:52:33 lat 48.6951
2023-01-24 19:08:17 local_key 3f108af73cbbf5a2
2023-01-24 19:08:17 lon 15.9707
2023-01-24 19:08:17 model BW-RC02
2023-01-24 19:08:17 name Universal Fernbedienung
2023-01-24 19:08:17 online on
2023-01-24 19:08:17 owner_id 9189095
2023-01-24 19:08:17 product_id d8ahyp53yju3dccz
2023-01-24 19:08:17 product_name Smart IR
2023-01-24 19:08:16 state not support this device
2023-01-24 19:08:17 sub off
2023-01-24 19:08:17 time_zone +01:00
2023-01-24 19:08:17 uid eu1577993184739WO7bA
2023-01-24 19:08:17 update_time 1674582781
2023-01-24 19:08:17 uuid cce3ae3d696957b3
args:
tuya_cloud_bf097fa77d739cfc18wqgc
fhempy
tuya_cloud
tuya_cloud_connector
bf097fa77d739cfc18wqgc
argsh:
hmccu:
Attributes:
alias Smart IR
group tuya_cloud
room fhempy
Wenn "not supported" kommt, geht über tuya cloud auch nicht mehr.
Seh ich das richtig, dass die LED nur eine IR LED ist? Also nur über die Fernbedienung gesteuert werden kann? Wenn ja, dann kann da auch nix über die Cloud gehen.
Habe so etwas Ähnliches über eine ZigbeeGateway über TuyaCloud und da funktionieren die Teile
Zigbee Gatway steht auch auf "not supportet this device"
Die Jalousie aber funktioniert
Gateway
Internals:
DEF tuya_cloud tuya_cloud_connector bfc3994a988ae0cf2admvs
DEVICEID bfc3994a988ae0cf2admvs
FHEMPYTYPE tuya_cloud
FUUID 6373f2ed-f33f-c95d-0784-2245f19fcaf9541e
IODev local_pybinding
NAME ZigBee_Gateway_bfc3994a988ae0cf2admvs
NR 365
PYTHONTYPE tuya_cloud
STATE not support this device
TYPE fhempy
eventCount 30
READINGS:
2023-01-24 19:08:18 active_time 1670160853
2023-01-24 19:08:18 biz_type 18
2023-01-24 19:08:18 category wfcon
2022-12-04 14:34:19 control stop
2022-12-04 14:34:19 control_back_mode forward
2023-01-24 19:08:18 create_time 1668529266
2022-12-04 14:34:19 fault 0
2023-01-24 00:22:34 icon https://images.tuyaeu.com/smart/icon/ay1559701439060fw6BY/b5f28ff251f0f3af885af39c4ef41e39.png
2023-01-24 19:08:18 id bfc3994a988ae0cf2admvs
2023-01-24 19:08:18 ip 92.248.27.155
2023-01-24 19:08:18 lat 48.6950
2023-01-24 19:08:18 local_key fa70c75b237e563c
2023-01-24 19:08:18 lon 15.9706
2023-01-24 19:08:18 model 341809
2023-01-24 19:08:18 name ZigBee Gateway
2023-01-24 19:08:18 online on
2023-01-24 19:08:18 owner_id 9189095
2022-12-04 14:34:19 percent_control 100
2022-12-04 14:34:19 percent_state 100
2023-01-24 19:08:18 product_id b25mh8sxawsgndck
2023-01-24 19:08:18 product_name ZigBee Gateway
2022-12-04 14:34:19 situation_set fully_open
2023-01-24 19:08:17 state not support this device
2023-01-24 19:08:18 sub off
2023-01-24 19:08:18 time_zone +01:00
2023-01-24 19:08:18 uid eu1577993184739WO7bA
2023-01-24 19:08:18 update_time 1670160853
2023-01-24 19:08:18 uuid 5671949dc2c9c857
2022-12-04 14:34:19 work_state opening
args:
ZigBee_Gateway_bfc3994a988ae0cf2admvs
fhempy
tuya_cloud
tuya_cloud_connector
bfc3994a988ae0cf2admvs
argsh:
Attributes:
alias ZigBee Gateway
group tuya_cloud
room fhempy
Jalousie
Internals:
DEF tuya_cloud tuya_cloud_connector bfa0522f291b3756ecjqhp
DEVICEID bfa0522f291b3756ecjqhp
FHEMPYTYPE tuya_cloud
FUUID 6373f2eb-f33f-c95d-4aaa-255dce7022bf7792
IODev local_pybinding
NAME Jalousie_Stefanie
NR 364
PYTHONTYPE tuya_cloud
STATE 0.0
TYPE fhempy
eventCount 403
READINGS:
2023-01-24 19:08:16 active_time 1670160853
2023-01-24 19:08:16 biz_type 18
2023-01-24 19:08:16 category cl
2023-01-24 19:08:17 control stop
2023-01-24 19:08:17 control_back_mode forward
2023-01-24 19:08:16 create_time 1668535237
2023-01-24 19:05:00 fault 0
2023-01-24 19:08:16 icon https://images.tuyaeu.com/smart/icon/ay1520042877959dqQoX/cabc06d56803a5a189c9fff9fc78c56b.png
2023-01-24 19:08:16 id bfa0522f291b3756ecjqhp
2023-01-24 19:08:16 ip
2023-01-24 19:08:16 lat 48.6950
2023-01-24 19:08:16 local_key fa70c75b237e563c
2023-01-24 19:08:16 lon 15.9706
2023-01-24 19:08:16 model AM43
2023-01-24 19:08:16 name Jalousie Stefanie
2023-01-24 19:08:16 node_id cc86ecfffefe3879
2023-01-24 19:08:16 online on
2023-01-24 19:08:16 owner_id 9189095
2023-01-24 19:08:17 percent_control 0.0
2023-01-24 19:08:17 percent_state 0.0
2023-01-24 19:08:16 product_id zah67ekd
2023-01-24 19:08:16 product_name AM43拉绳电机-Zigbee
2023-01-24 19:08:17 situation_set fully_open
2023-01-24 19:08:10 state ready
2023-01-24 19:08:16 sub on
2023-01-24 19:08:16 time_zone +01:00
2023-01-24 19:08:16 uid eu1577993184739WO7bA
2023-01-24 19:08:16 update_time 1670160853
2023-01-24 19:08:16 uuid cc86ecfffefe3879
2023-01-24 19:08:17 work_state closing
args:
Jalousie_Stefanie
fhempy
tuya_cloud
tuya_cloud_connector
bfa0522f291b3756ecjqhp
argsh:
Attributes:
alias Jalousie Stefanie
devStateIcon 0.0:fts_shutter_100 [91-100].\d.*:fts_shutter_10 [81-90]\d.*:fts_shutter_10 [71-80].\d.*:fts_shutter_20 [61-70].\d*:fts_shutter_30 [51-60].\d.*:fts_shutter_40 [41-50].\d.*:fts_shutter_50 [31-40].\d.*:fts_shutter_60 [21-30].\d.*:fts_shutter_70 [11-20].\d.*:fts_shutter_80 [1-10].\d.*:fts_shutter_90 0.\d.*:fts_shutter_100
event-on-change-reading .*
genericDeviceType blind
group tuya_cloud
icon fts_shutter_100
room Jalousien,Obergeschoss->Stefanie,fhempy
stateFormat percent_state
verbose 0
Zitat von: dominik am 24 Januar 2023, 21:07:52
Seh ich das richtig, dass die LED nur eine IR LED ist? Also nur über die Fernbedienung gesteuert werden kann? Wenn ja, dann kann da auch nix über die Cloud gehen.
Bitte die Frage beantworten 8)
Ja ist eine IR LED die über die Universal Fernbedienung steuerbar ist ;D
Ok, das wird über die Cloud nicht steuerbar sein. Die LED Lampe hat ja keinerlei Verbindung zum Internet.
Warum kaufst du sowas? ;) Ich würde nur mehr Zigbee Lampen kaufen, da bist von der Cloud unabhängig und musst nicht so Sachen wie diesen IR Sender verwenden, der dann wieder irgendwo steht, wo er nicht alle gewünschten Lampen per IR erreicht.
Naja habe in den Schränken einiger dieser Led Strips mit ir fernbedienung und möchte diese gerne smart machen, das der grund.
über die cloud funkt es wunderbar und ein device in fhem wurde ja auch angelegt und da hoffte ich es gäbe möglichkeiten
Achso, das sind diese LED Strips...
Du kannst mal mit tuya (nicht _cloud) probieren was du da für Rückmeldung bekommst. Lokal sollte IR machbar sein. In der tinytuya Library wurde da auch schon dran gearbeitet.
https://github.com/jasonacox/tinytuya/issues/74
Seit Tagen wird mein log stündlich mit den folgenden Meldungen beschrieben:
[code]2023.01.26 05:29:37.103 1: readingsUpdate(Air_conditioner_33051602e09806002e71,humidity_current,0.0) missed to call readingsBeginUpdate first.
2023.01.26 05:29:37.103 1: stacktrace:
2023.01.26 05:29:37.103 1: main::readingsBulkUpdate called by (eval 1024727) (1)
2023.01.26 05:29:37.103 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:37.103 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:37.103 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:37.103 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:37.103 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:37.103 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:37.103 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:37.558 3: FS20 set Kue_Licht_Dunstabzughaube off
2023.01.26 05:29:38.460 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,fault,0) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.460 1: stacktrace:
2023.01.26 05:29:38.460 1: main::readingsBulkUpdate called by (eval 1024868) (1)
2023.01.26 05:29:38.460 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.460 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.460 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.460 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.460 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.460 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.461 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.461 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.461 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.461 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.461 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.461 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.461 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.461 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.461 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.461 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.461 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.461 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.461 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.461 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.462 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.462 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.462 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.462 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.462 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.462 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.464 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,status,chargecompleted) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.464 1: stacktrace:
2023.01.26 05:29:38.464 1: main::readingsBulkUpdate called by (eval 1024869) (1)
2023.01.26 05:29:38.464 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.464 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.464 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.464 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.464 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.464 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.465 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.465 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.465 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.465 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.465 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.465 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.465 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.465 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.465 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.465 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.465 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.465 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.465 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.465 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.465 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.466 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.466 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.466 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.466 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.466 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.468 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,status,chargecompleted) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.468 1: stacktrace:
2023.01.26 05:29:38.468 1: main::readingsBulkUpdate called by (eval 1024870) (1)
2023.01.26 05:29:38.468 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.468 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.468 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.468 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.468 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.468 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.468 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.468 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.468 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.469 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.469 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.469 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.469 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.469 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.469 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.469 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.469 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.469 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.469 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.469 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.469 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.469 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.469 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.469 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.470 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.470 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.471 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,status,chargecompleted) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.471 1: stacktrace:
2023.01.26 05:29:38.472 1: main::readingsBulkUpdate called by (eval 1024871) (1)
2023.01.26 05:29:38.472 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.472 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.472 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.472 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.472 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.472 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.472 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.472 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.472 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.472 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.472 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.472 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.473 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.473 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.473 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.473 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.473 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.473 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.473 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.473 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.473 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.473 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.473 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.473 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.473 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.473 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.475 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,status,chargecompleted) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.475 1: stacktrace:
2023.01.26 05:29:38.475 1: main::readingsBulkUpdate called by (eval 1024872) (1)
2023.01.26 05:29:38.475 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.476 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.476 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.476 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.476 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.476 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.476 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.476 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.476 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.476 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.476 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.476 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.476 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.476 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.476 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.477 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.477 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.477 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.477 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.477 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.477 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.477 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.477 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.477 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.477 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.477 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.479 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,status,chargecompleted) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.479 1: stacktrace:
2023.01.26 05:29:38.479 1: main::readingsBulkUpdate called by (eval 1024873) (1)
2023.01.26 05:29:38.479 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.479 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.479 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.480 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.480 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.480 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.480 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.480 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.480 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.480 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.480 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.480 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.480 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.480 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.480 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.480 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.480 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.481 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.481 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.481 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.481 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.481 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.481 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.481 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.481 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.481 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.483 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,status,chargecompleted) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.483 1: stacktrace:
2023.01.26 05:29:38.483 1: main::readingsBulkUpdate called by (eval 1024874) (1)
2023.01.26 05:29:38.483 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.483 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.483 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.484 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.484 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.484 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.484 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.484 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.484 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.484 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.484 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.484 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.484 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.484 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.484 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.484 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.484 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.484 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.485 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.485 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.485 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.485 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.485 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.485 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.485 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.485 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.487 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,status,chargecompleted) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.487 1: stacktrace:
2023.01.26 05:29:38.487 1: main::readingsBulkUpdate called by (eval 1024875) (1)
2023.01.26 05:29:38.487 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.487 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.487 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.487 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.488 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.488 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.488 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.488 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.488 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.488 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.488 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.488 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.488 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.488 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.488 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.488 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.488 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.488 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.489 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.489 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.489 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.489 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.489 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.489 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.489 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.489 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.491 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,status,chargecompleted) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.491 1: stacktrace:
2023.01.26 05:29:38.491 1: main::readingsBulkUpdate called by (eval 1024876) (1)
2023.01.26 05:29:38.491 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.491 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.491 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.491 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.491 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.491 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.492 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.492 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.492 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.492 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.492 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.492 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.492 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.492 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.492 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.492 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.492 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.492 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.492 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.492 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.493 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.493 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.493 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.493 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.493 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.493 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.495 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,power_go,off) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.495 1: stacktrace:
2023.01.26 05:29:38.495 1: main::readingsBulkUpdate called by (eval 1024877) (1)
2023.01.26 05:29:38.495 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.495 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.495 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.495 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.495 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.495 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.495 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.496 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.496 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.496 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.496 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.496 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.496 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.496 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.496 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.496 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.496 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.496 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.496 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.496 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.497 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.497 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.497 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.497 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.497 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.497 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.499 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,power_go,off) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.499 1: stacktrace:
2023.01.26 05:29:38.499 1: main::readingsBulkUpdate called by (eval 1024878) (1)
2023.01.26 05:29:38.499 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.499 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.499 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.499 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.499 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.499 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.499 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.499 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.499 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.500 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.500 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.500 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.500 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.500 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.500 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.500 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.500 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.500 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.500 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.500 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.500 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.501 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.501 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.501 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.501 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.501 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.503 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,status,chargecompleted) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.503 1: stacktrace:
2023.01.26 05:29:38.503 1: main::readingsBulkUpdate called by (eval 1024879) (1)
2023.01.26 05:29:38.503 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.503 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.503 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.503 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.503 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.503 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.503 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.503 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.504 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.504 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.504 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.504 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.504 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.504 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.504 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.504 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.504 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.504 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.504 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.505 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.505 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.505 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.505 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.505 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.505 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.505 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.507 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,suction,normal) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.507 1: stacktrace:
2023.01.26 05:29:38.507 1: main::readingsBulkUpdate called by (eval 1024880) (1)
2023.01.26 05:29:38.507 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.507 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.507 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.507 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.507 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.508 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.508 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.508 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.508 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.508 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.508 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.508 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.508 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.508 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.508 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.508 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.508 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.508 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.508 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.509 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.509 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.509 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.509 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.509 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.509 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.509 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.511 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,suction,normal) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.511 1: stacktrace:
2023.01.26 05:29:38.511 1: main::readingsBulkUpdate called by (eval 1024881) (1)
2023.01.26 05:29:38.511 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.511 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.511 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.511 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.511 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.511 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.512 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.512 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.512 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.512 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.512 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.512 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.512 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.512 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.512 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.512 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.512 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.512 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.512 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.512 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.513 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.513 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.513 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.513 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.513 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.513 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.525 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,electricity_left,100.0) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.525 1: stacktrace:
2023.01.26 05:29:38.525 1: main::readingsBulkUpdate called by (eval 1024888) (1)
2023.01.26 05:29:38.525 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.525 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.525 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (428)
2023.01.26 05:29:38.525 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.525 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.526 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.526 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:
packe das mal doch in code
Zitatpacke das mal doch in code
Geht leider nicht. Die Daten werden nicht als code übernommen.
Füge die Datei als Anlage an.
[code]2023.01.26 05:29:37.103 1: readingsUpdate(Air_conditioner_33051602e09806002e71,humidity_current,0.0) missed to call readingsBeginUpdate first.
2023.01.26 05:29:37.103 1: stacktrace:
2023.01.26 05:29:37.103 1: main::readingsBulkUpdate called by (eval 1024727) (1)
2023.01.26 05:29:37.103 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:37.103 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:37.103 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:37.103 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:37.103 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:37.103 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:37.103 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:37.558 3: FS20 set Kue_Licht_Dunstabzughaube off
2023.01.26 05:29:38.460 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,fault,0) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.460 1: stacktrace:
2023.01.26 05:29:38.460 1: main::readingsBulkUpdate called by (eval 1024868) (1)
2023.01.26 05:29:38.460 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.460 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.460 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.460 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.460 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.460 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.461 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.461 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.461 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.461 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.461 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.461 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.461 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.461 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.461 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.461 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.461 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.461 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.461 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.461 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.462 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.462 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.462 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.462 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.462 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.462 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.464 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,status,chargecompleted) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.464 1: stacktrace:
2023.01.26 05:29:38.464 1: main::readingsBulkUpdate called by (eval 1024869) (1)
2023.01.26 05:29:38.464 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.464 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.464 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.464 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.464 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.464 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.465 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.465 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.465 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.465 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.465 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.465 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.465 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.465 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.465 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.465 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.465 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.465 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.465 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.465 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.465 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.466 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.466 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.466 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.466 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.466 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.468 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,status,chargecompleted) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.468 1: stacktrace:
2023.01.26 05:29:38.468 1: main::readingsBulkUpdate called by (eval 1024870) (1)
2023.01.26 05:29:38.468 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.468 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.468 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.468 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.468 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.468 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.468 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.468 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.468 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.469 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.469 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.469 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.469 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.469 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.469 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.469 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.469 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.469 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.469 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.469 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.469 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.469 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.469 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.469 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.470 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.470 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.471 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,status,chargecompleted) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.471 1: stacktrace:
2023.01.26 05:29:38.472 1: main::readingsBulkUpdate called by (eval 1024871) (1)
2023.01.26 05:29:38.472 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.472 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.472 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.472 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.472 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.472 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.472 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.472 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.472 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.472 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.472 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.472 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.473 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.473 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.473 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.473 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.473 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.473 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.473 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.473 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.473 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.473 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.473 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.473 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.473 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.473 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.475 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,status,chargecompleted) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.475 1: stacktrace:
2023.01.26 05:29:38.475 1: main::readingsBulkUpdate called by (eval 1024872) (1)
2023.01.26 05:29:38.475 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.476 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.476 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.476 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.476 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.476 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.476 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.476 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.476 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.476 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.476 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.476 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.476 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.476 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.476 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.477 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.477 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.477 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.477 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.477 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.477 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.477 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.477 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.477 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.477 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.477 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.479 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,status,chargecompleted) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.479 1: stacktrace:
2023.01.26 05:29:38.479 1: main::readingsBulkUpdate called by (eval 1024873) (1)
2023.01.26 05:29:38.479 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.479 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.479 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.480 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.480 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.480 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.480 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.480 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.480 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.480 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.480 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.480 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.480 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.480 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.480 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.480 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.480 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.481 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.481 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.481 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.481 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.481 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.481 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.481 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.481 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.481 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.483 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,status,chargecompleted) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.483 1: stacktrace:
2023.01.26 05:29:38.483 1: main::readingsBulkUpdate called by (eval 1024874) (1)
2023.01.26 05:29:38.483 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.483 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.483 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.484 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.484 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.484 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.484 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.484 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.484 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.484 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.484 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.484 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.484 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.484 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.484 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.484 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.484 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.484 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.485 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.485 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.485 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.485 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.485 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.485 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.485 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.485 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.487 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,status,chargecompleted) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.487 1: stacktrace:
2023.01.26 05:29:38.487 1: main::readingsBulkUpdate called by (eval 1024875) (1)
2023.01.26 05:29:38.487 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.487 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.487 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.487 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.488 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.488 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.488 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.488 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.488 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.488 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.488 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.488 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.488 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.488 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.488 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.488 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.488 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.488 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.489 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.489 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.489 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.489 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.489 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.489 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.489 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.489 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.491 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,status,chargecompleted) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.491 1: stacktrace:
2023.01.26 05:29:38.491 1: main::readingsBulkUpdate called by (eval 1024876) (1)
2023.01.26 05:29:38.491 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.491 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.491 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.491 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.491 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.491 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.492 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.492 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.492 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.492 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.492 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.492 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.492 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.492 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.492 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.492 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.492 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.492 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.492 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.492 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.493 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.493 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.493 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.493 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.493 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.493 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.495 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,power_go,off) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.495 1: stacktrace:
2023.01.26 05:29:38.495 1: main::readingsBulkUpdate called by (eval 1024877) (1)
2023.01.26 05:29:38.495 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.495 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.495 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.495 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.495 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.495 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.495 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.496 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.496 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.496 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.496 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.496 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.496 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.496 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.496 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.496 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.496 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.496 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.496 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.496 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.497 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.497 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.497 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.497 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.497 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.497 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.499 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,power_go,off) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.499 1: stacktrace:
2023.01.26 05:29:38.499 1: main::readingsBulkUpdate called by (eval 1024878) (1)
2023.01.26 05:29:38.499 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.499 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.499 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.499 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.499 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.499 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.499 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.499 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.499 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.500 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.500 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.500 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.500 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.500 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.500 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.500 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.500 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.500 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.500 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.500 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.500 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.501 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.501 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.501 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.501 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.501 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.503 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,status,chargecompleted) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.503 1: stacktrace:
2023.01.26 05:29:38.503 1: main::readingsBulkUpdate called by (eval 1024879) (1)
2023.01.26 05:29:38.503 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.503 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.503 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.503 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.503 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.503 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.503 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.503 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.504 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.504 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.504 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.504 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.504 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.504 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.504 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.504 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.504 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.504 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.504 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.505 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.505 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.505 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.505 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.505 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.505 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.505 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.507 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,suction,normal) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.507 1: stacktrace:
2023.01.26 05:29:38.507 1: main::readingsBulkUpdate called by (eval 1024880) (1)
2023.01.26 05:29:38.507 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.507 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.507 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.507 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.507 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.508 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.508 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.508 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.508 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.508 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.508 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.508 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.508 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.508 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.508 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.508 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.508 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.508 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.508 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.509 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.509 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.509 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.509 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.509 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.509 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.509 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.511 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,suction,normal) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.511 1: stacktrace:
2023.01.26 05:29:38.511 1: main::readingsBulkUpdate called by (eval 1024881) (1)
2023.01.26 05:29:38.511 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.511 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.511 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (412)
2023.01.26 05:29:38.511 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.511 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.511 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.512 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.512 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.512 1: main::__ANON__ called by fhem.pl (1954)
2023.01.26 05:29:38.512 1: main::DoSet called by fhem.pl (1996)
2023.01.26 05:29:38.512 1: main::CommandSet called by fhem.pl (2904)
2023.01.26 05:29:38.512 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.26 05:29:38.512 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.26 05:29:38.512 1: main::FW_Notify called by fhem.pl (3971)
2023.01.26 05:29:38.512 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.512 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.512 1: main::__ANON__ called by fhem.pl (3888)
2023.01.26 05:29:38.512 1: main::DoTrigger called by fhem.pl (4995)
2023.01.26 05:29:38.512 1: main::readingsEndUpdate called by (eval 1024867) (1)
2023.01.26 05:29:38.512 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.513 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.513 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (299)
2023.01.26 05:29:38.513 1: main::BindingsIo_Read called by fhem.pl (3971)
2023.01.26 05:29:38.513 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:38.513 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2023.01.26 05:29:38.513 1: main::__ANON__ called by fhem.pl (784)
2023.01.26 05:29:38.525 1: readingsUpdate(tuya_cloud_bf623c4459370bd192tywm,electricity_left,100.0) missed to call readingsBeginUpdate first.
2023.01.26 05:29:38.525 1: stacktrace:
2023.01.26 05:29:38.525 1: main::readingsBulkUpdate called by (eval 1024888) (1)
2023.01.26 05:29:38.525 1: (eval) called by ./FHEM/10_BindingsIo.pm (564)
2023.01.26 05:29:38.525 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (679)
2023.01.26 05:29:38.525 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (428)
2023.01.26 05:29:38.525 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.26 05:29:38.525 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.26 05:29:38.526 1: main::fhempy_Set called by fhem.pl (3971)
2023.01.26 05:29:38.526 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2023.01.26 05:29:
Bekommst du auch nach einem fhempy Neustart diesen Fehler?
Zur Info wegen code Tag:
- Log reinkopieren
- Artikel posten
- Nachträglich bearbeiten und dabei die letzte Zeile löschen damit der code Tag noch Platz hat
Ohne Code Tag macht es sonst wirklich keinen Spaß das zu lesen.
Hallo Dominik,
gerade einen fhempy Neustart gemacht und im Log sind keine Fehlermeldungen
Hallo Dominik,
ich habe alles nach Anleitung installiert.
1. python 3.8.4 und pip installiert, python und python3 mit alias auf python 3.8.4 gesetzt, das wird bei python -V bzw. python3 -V auch angezeigt.
2. update add https://raw.githubusercontent.com/fhempy/fhempy/master/controls_pythonbinding.txt
update
shutdown restart
define fhempy_local BindingsIo fhempy
3. Ein Projekt auf der Tuya Platform angelegt
im room fhempy wurden fhempy_local und fhempyserver_15733 angelegt.
Folgender Eintrag im Logfile:
2023.01.29 22:31:39 3: BindingsIo v1.0.1
2023.01.29 22:31:39 3: found IP 127.0.0.1
2023.01.29 22:31:39 3: fhempyServer v1.0.0
2023.01.29 22:31:43 3: Opening fhempy_local device ws:localhost:15733
2023.01.29 22:31:43 1: fhempy_local: Can't connect to ws:localhost:15733: Operation now in progress
2023.01.29 22:31:43 1: fhempy_local: Can't connect to ws:localhost:15733: localhost: Verbindungsaufbau abgelehnt (111)
2023.01.29 22:31:43 1: BindingsIo (fhempy_local): ERROR during connection setup: localhost: Verbindungsaufbau abgelehnt (111)
Folgender Eintrag im Reading des Servers:
python Python 3.7.2 or higher required 2023-01-29 22:31:39
Folgender Eintrag in Internals in fhempy_local:
prev_error localhost: Verbindungsaufbau abgelehnt (111)
Was muss ich einstellen, damit der Server python 3.8.4 erkennt und eine Verbindung zulässt?
Viele Grüße
Werner
Hier noch lists:
Internals:
BindingType fhempy
CFGFN
DEF fhempy
DeviceName ws:localhost:15733
FUUID 63d6e5bb-f33f-f21b-cd0c-623e5a023eab3d0c
IP 127.0.0.1
NAME fhempy_local
NEXT_OPEN 1675029386.90307
NR 1018
NTFY_ORDER 50-fhempy_local
PARTIAL
PORT 15733
STATE disconnected
TYPE BindingsIo
binary 1
devioLoglevel 0
eventCount 2
localBinding 1
nextOpenDelay 10
prev_error localhost: Verbindungsaufbau abgelehnt (111)
READINGS:
2023-01-29 22:56:16 state disconnected
args:
fhempy_local
BindingsIo
fhempy
Attributes:
devStateIcon { my $attr_ver = "1.0.0";; my $status_img = "10px-kreis-gruen";; my $status_txt = "connected";; my $ver = ReadingsVal($name, "version", "-");; my $ver_available = ReadingsVal($name, "version_available", $ver);; my $update_icon = "";; my $refresh_img = "refresh";; my $refresh_txt = "Update fhempy";; if ($ver_available ne $ver) { $refresh_img = "refresh\@orange";; $refresh_txt = "Version ".$ver_available." available for update";; } if (ReadingsVal($name, "state", "disconnected") eq "disconnected") { $status_img = "10px-kreis-rot";; $status_txt = "disconnected";; } $update_icon = "<a href=\"/fhem?cmd.dummy=set $name update&XHR=1\" title=\"Start ".$ver_available." update\">".FW_makeImage($refresh_img, $refresh_txt)."</a>";; my $restart_icon = "<a href=\"/fhem?cmd.dummy=set $name update&XHR=1\" title=\"Restart fhempy\">".FW_makeImage("control_reboot")."</a>";; "<div><a>".FW_makeImage($status_img, $status_txt)."</a><a> ".$ver." </a>".$update_icon.$restart_icon."</div>" }
group fhempy
icon file_json-ld2
room fhempy
Internals:
CFGFN
DEF 0
FUUID 63d6e5bb-f33f-f21b-78f9-d0f05581bf99a7f2
NAME fhempyserver_15733
NR 1019
NTFY_ORDER 50-fhempyserver_15733
STATE ???
TYPE fhempyServer
eventCount 2
logfile ./log/fhempy-%Y-%m-%d.log
CoProcess:
cmdFn fhempyServer_getCmd
name fhempy
READINGS:
2023-01-29 22:31:39 python Python 3.7.2 or higher required
Attributes:
devStateIcon { my $status_img = "10px-kreis-gruen";; my $status_txt = "running";; if (substr(ReadingsVal($name, "fhempy", "running"),0,7) ne "running") { $status_img = "10px-kreis-rot";; $status_txt = "stopped";; } "<div><a>".FW_makeImage($status_img, $status_txt)."</a><a href=\"/fhem?cmd.dummy=set $name restart&XHR=1\" title=\"Kill and restart\">".FW_makeImage("audio_repeat")."</a></div>" }
group fhempy
icon python
logfile ./log/fhempy-%Y-%m-%d.log
nrarchive 10
room fhempy
Du hast Python wahrscheinlich nicht systemweit auf 3.8.2 gestellt.
Bevor du damit weiter machst, bitte spar dir die Zeit und aktualisiere auf bullseye mit Python 3.9. Python 3.8 wird bei manchen fhempy Modulen auch nicht mehr unterstützt. Die manuelle Installation von Python macht dir sonst auf Dauer nur Probleme.
Ich habe zunächst nur nach Anleitung fhempy_local und fhempyserver angelegte.
Welche Daten aus der Cloud fehlen dabei.
Das device mit den Projektdaten habe ich noch nicht angelegt, da ja die Punkte 1 und 2 erst mal fehlerfrei laufe sollen.
Wenn ich das richtig verstehe liegt der Fehler offenbar darin,
das der Server auf die falsche python Version, die ja standardmäßig installiert ist (2.7 ?), zugreift und das im beim
updateversuch auch als Fehler anzeigt.
Siehe Anhang
Hallo Dominik,
Danke für die schnelle Antwort.
Ich würde ungern auf bullseye upgraden, da ich eine umfangreiche Installation habe und nicht weiß, was dann womöglich alles nicht mehr funktioniert.
In 14 Tagen habe ich mein Testsystem zurück, da kann ich dann verschiedenes ausprobieren, auch upgrade.
Aber falls du eine Lösung mit Stretch siehst wäre mir das die liebste Lösung.
Viele Grüße
Werner
noch ein Nachtrag:
Ich habe jetzt mal "Python -V" in die Commandline von fhem eingegeben.
das Ergebnis im Logfile ist:
Python 2.7.13
Wo kann ich fhem beibringen, python 3.8.4 zu nehmen.
Viele Grüße
Werner
Jetzt funktioniert es, zumindest schon der Server und das BindingIo.
Das device zur Steuerung von Tuya (Ölradiator von Kesser) trage ich später ein.
Die in vielen Beiträgen beschriebene alias definition reicht nicht aus, um die neue Version systemweit als default zu deklarieren.
Die Deklaration muss gemäß der Beschreibung in dem folgenden Link ausgeführt werden.
https://linuxconfig.org/how-to-change-from-default-to-alternative-python-version-on-debian-linux
Dabei ist zu beachten, dass die neue Version nicht, wie beschrieben, in /usr/bin steht sondern in /usr/local/bin steht.
also ändern in
# update-alternatives --install /usr/bin/python python /usr/bin/python2.7 1
update-alternatives: using /usr/bin/python2.7 to provide /usr/bin/python (python) in auto mode
# update-alternatives --install /usr/bin/python python /usr/bin/python3.8 2
update-alternatives: using /usr/bin/python3.4 to provide /usr/local/bin/python (python) in auto mode
viele Grüße
Werner
hallo dominik,
wie Berichtet habe ich tuya_cloud bei mir wieder aktiviert.
Meine Temperatur-Devices nun wieder wie geschmiert :-)
Jedoch hagelt es in der FHEM.log Fehler:
2023.01.30 15:02:56 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'tuya_cloud_8877821724a160151069'},1);;
2023.01.30 15:02:56 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'tuya_cloud_8877821724a160151069'},1);;
2023.01.30 15:02:56 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'tuya_cloud_8877821724a160151069'},1);;
2023.01.30 15:02:56 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL13'},1);;
2023.01.30 15:02:56 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL13'},1);;
2023.01.30 15:02:57 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL06'},1);;
2023.01.30 15:02:57 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL06'},1);;
2023.01.30 15:02:58 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL35'},1);;
2023.01.30 15:02:58 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL35'},1);;
2023.01.30 15:02:58 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL04'},1);;
2023.01.30 15:02:58 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL04'},1);;
2023.01.30 15:02:58 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL04'},1);;
2023.01.30 15:02:58 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL04'},1);;
2023.01.30 15:02:58 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'tuya_cloud_22230808bcddc213f838'},1);;
2023.01.30 15:02:58 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'tuya_cloud_22230808bcddc213f838'},1);;
2023.01.30 15:02:58 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL15'},1);;
2023.01.30 15:02:58 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL15'},1);;
2023.01.30 15:02:58 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL29'},1);;
2023.01.30 15:02:58 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL29'},1);;
2023.01.30 15:02:58 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL29'},1);;
2023.01.30 15:02:58 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL29'},1);;
2023.01.30 15:02:58 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL29'},1);;
2023.01.30 15:02:58 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL29'},1);;
2023.01.30 15:02:59 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL04'},1);;
2023.01.30 15:02:59 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL04'},1);;
2023.01.30 15:03:00 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL04'},1);;
2023.01.30 15:03:00 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL04'},1);;
2023.01.30 15:03:00 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_Temp02'},1);;
2023.01.30 15:03:00 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'TUYA_Temp02'},1);;
2023.01.30 15:03:00 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL21'},1);;
2023.01.30 15:03:00 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL21'},1);;
2023.01.30 15:03:00 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL25'},1);;
2023.01.30 15:03:00 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL25'},1);;
2023.01.30 15:03:00 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL33'},1);;
2023.01.30 15:03:00 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL33'},1);;
2023.01.30 15:03:00 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL33'},1);;
2023.01.30 15:03:00 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL33'},1);;
2023.01.30 15:03:00 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL33'},1);;
2023.01.30 15:03:00 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL33'},1);;
2023.01.30 15:03:00 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL04'},1);;
2023.01.30 15:03:00 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL04'},1);;
2023.01.30 15:03:00 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'tuya_cloud_8877821724a160151069'},1);;
2023.01.30 15:03:00 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'tuya_cloud_8877821724a160151069'},1);;
2023.01.30 15:03:00 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'tuya_cloud_8877821724a160151069'},1);;
2023.01.30 15:03:00 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'tuya_cloud_8877821724a160151069'},1);;
2023.01.30 15:03:00 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'tuya_cloud_8877821724a160151069'},1);;
2023.01.30 15:03:00 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'tuya_cloud_8877821724a160151069'},1);;
2023.01.30 15:03:01 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL31'},1);;
2023.01.30 15:03:01 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL31'},1);;
2023.01.30 15:03:01 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL29'},1);;
2023.01.30 15:03:01 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL29'},1);;
2023.01.30 15:03:02 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL04'},1);;
2023.01.30 15:03:02 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL04'},1);;
2023.01.30 15:03:03 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL04'},1);;
2023.01.30 15:03:03 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL04'},1);;
2023.01.30 15:03:05 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL21'},1);;
2023.01.30 15:03:05 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL21'},1);;
2023.01.30 15:03:05 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL33'},1);;
2023.01.30 15:03:05 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL33'},1);;
2023.01.30 15:03:05 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL33'},1);;
2023.01.30 15:03:05 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1295.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL33'},1);;
aus den local-devices
auch im fhempy-log hagelt es immer die diselbe Meldung:
2023-01-30 15:06:20,138 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:20,928 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:21,778 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:22,137 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:22,173 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:22,821 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:23,891 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:25,136 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:25,136 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:25,150 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:27,184 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:27,833 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:28,903 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:30,149 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:30,149 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:30,150 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:30,939 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:31,790 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:32,149 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:32,196 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:32,845 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:33,916 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:35,160 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:35,161 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:35,162 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:37,209 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:37,858 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:38,928 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:40,162 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:40,173 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:40,173 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:40,951 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:41,801 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:42,161 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:42,222 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:42,870 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:43,940 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:45,175 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:45,186 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:45,186 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:47,234 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:47,882 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:48,951 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:50,174 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:50,197 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:50,198 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:50,962 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:51,813 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:52,172 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:52,245 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:52,894 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:53,963 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:55,188 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:55,209 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:55,210 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:57,259 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:57,906 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:58,880 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:58,975 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:59,378 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:59,489 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:06:59,547 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:00,187 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:00,221 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:00,221 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:00,974 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:01,829 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:02,184 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:02,270 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:02,919 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:03,987 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:05,199 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:05,232 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:05,233 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:07,281 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:07,930 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:08,999 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:10,200 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:10,245 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:10,245 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:10,985 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:11,840 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:12,198 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:12,293 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:12,943 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:14,012 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:15,211 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:15,257 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:15,258 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:17,304 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:17,955 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:19,022 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:19,927 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:20,212 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:20,269 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:20,270 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:20,997 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:21,852 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:22,209 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:22,316 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:22,966 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:24,034 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:25,223 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:25,281 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:25,281 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:27,328 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:27,978 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:29,047 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:30,224 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:30,293 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:30,294 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:31,009 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:31,864 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:32,222 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:32,339 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:32,989 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:34,058 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:35,235 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:35,306 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:35,307 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:37,351 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:38,001 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:39,070 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:40,238 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:40,319 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:40,320 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:41,022 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:41,876 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:42,234 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:42,363 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:43,014 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:44,082 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:45,246 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:45,331 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:45,332 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:47,376 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:48,026 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:49,093 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:50,250 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:50,344 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:50,345 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:51,034 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:51,891 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:52,246 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:52,388 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:53,038 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:54,106 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:55,260 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:55,356 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:55,357 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:57,400 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:58,051 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:58,893 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:59,118 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:59,390 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:59,502 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:07:59,559 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:00,263 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:00,369 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:00,370 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:01,046 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:01,903 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:02,257 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:02,412 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:03,062 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:04,129 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:05,272 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:05,382 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:05,382 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:07,425 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:08,074 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:09,142 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:10,276 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:10,394 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:10,395 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:11,057 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:11,922 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:12,270 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:12,437 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:13,087 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:14,155 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:15,284 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:15,407 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:15,407 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:17,448 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:18,099 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:19,166 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:19,939 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:20,289 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:20,419 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:20,419 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:21,069 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:21,934 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:22,281 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:22,460 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:23,111 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:24,178 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:25,297 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:25,430 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:25,432 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:27,472 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:28,122 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:29,190 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:30,301 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:30,443 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:30,444 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:31,082 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:31,946 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:32,293 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:32,485 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:33,136 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:34,203 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:35,309 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:35,456 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:35,456 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:37,497 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:38,147 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:39,215 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:40,313 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:40,468 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:40,468 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:41,094 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:41,957 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:42,306 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:42,511 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:43,159 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:44,227 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:45,321 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:45,481 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:45,481 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:47,523 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:48,170 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:49,239 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:50,325 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:50,492 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:50,493 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:51,106 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:51,971 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:52,317 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:52,534 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:53,182 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:54,251 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:55,332 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:55,505 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:55,506 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:57,546 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:58,193 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:58,905 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:59,262 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:59,402 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:59,514 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:08:59,573 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:09:00,337 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:09:00,518 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:09:00,520 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:09:01,118 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:09:01,982 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:09:02,328 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:09:02,559 - WARNING - asyncio: socket.send() raised exception.
2023-01-30 15:09:03,205 - WARNING - asyncio: socket.send() raised exception.
das trat wohl auf, als ich das FHEM update gefahren hatte
habe mehrfach shutdown restart gemacht
Hilfe!!
meine 36 Tuya-Steckdosen erzeugen jede alle Sekunde ein Event
ich schalte Tuya-cloud mal lieber wieder ab.
Erbitte eilige Hilfe
viele Grüße
Thomas
Deine Steckdosen machen die Events? Sind die nicht mit tuya local verbunden?
Oder liegt es an DbLog?
https://forum.fhem.de/index.php?topic=112168.0
ja sind local verbunden und in dblog excluded
hatte sie in local wiederactiviert, damit cloud sie nicht findet
eigentlich will ich sie garnicht solange consumtion nicht kumuliert wird
kann man sie nicht ausfiltern?
Ehm, ich verstehe nur Bahnhof 😀 hab mit dblog nix am Hut.
Zitat von: dominik am 30 Januar 2023, 21:58:32
Ehm, ich verstehe nur Bahnhof 😀 hab mit dblog nix am Hut.
ja an dblog liegt es nicht, dass soviele events erzeugt werden und die fhempy-log wie geschildert mit Fehlern geflutet wird
alldies tritt erst auf, nachdem pythonbindings über FHEM update ausgeführt wurde
Teste es bitte mit einer älteren Version von BindingsIo.pm.
https://github.com/fhempy/fhempy/blob/v0.1.575/FHEM/10_BindingsIo.pm
Zitat von: dominik am 30 Januar 2023, 22:18:38
Teste es bitte mit einer älteren Version von BindingsIo.pm.
https://github.com/fhempy/fhempy/blob/v0.1.575/FHEM/10_BindingsIo.pm
wie genauer?
auf Windows PC runterladen und dann auf Raspi in welches Verzeichnis laden?
oder kann ich das irgendwie in FHEM machen?
Ja, einfach die 10_BindingsIo.pm im FHEM Verzeichnis austauschen und FHEM neu starten.
Achte auf die Rechte der Datei wenn du die kopierst. Am besten danach mit folgenden Commands richten:
sudo chown fhem:dialout 10_BindingsIo.pm
ok
dann kann ich das auch aus meiner FHEM sicherung von vorgestern zurückziehen ?
Ja, aber nur diese eine Datei zurückspielen.
Hi,
ich habe hier das gleiche Problem wie Sommerfeld, siehe unten.
Aber ein restart von fhempy löst das Problem nicht.
Ich benutze Cloud und local und mein local_pybinding ist 0.1.578.
Denke das hat angefangen als ich local_pybinding geupdated habe.
Habe auch das Gefühl das fhem langsam geworden ist.
Welche Infos sind noch hilfreich?
Danke und Gruß,
Stefan
Apptime zeigt auch nur noch Tuya als Hauptzeitfresser.
active-timers: 107; max-active timers: 116; max-timer-load: 15 min-tmrHandlingTm: 0.2ms; max-tmrHandlingTm: 1375.1ms; totAvgDly: 595.3ms
name function max count total average maxDly avgDly TS Max call param Max call
local_pybinding CODE(0x7810e98) 4899 404 165502.38 409.66 0.00 0.00 30.01. 23:30:45 HASH(local_pybinding)
WEB_192.168.69.30_54138 FW_Notify 4482 2869 234687.87 81.80 0.00 0.00 30.01. 23:32:25 HASH(WEB_192.168.69.30_54138); HASH(tuya_local_bf4f644bc7dd2fc71d9q52)
tuya_local_bf4f644bc7dd2fc71d9q52 fhempy_Set 4475 81 58360.69 720.50 0.00 0.00 30.01. 23:32:25 HASH(tuya_local_bf4f644bc7dd2fc71d9q52); ARRAY(0x86c36e8); HASH(0x8f5bf38)
Sybille_Tablet_bf68d9b41c16be3713vcc1 fhempy_Set 3040 448 51411.94 114.76 0.00 0.00 30.01. 23:31:51 HASH(Sybille_Tablet_bf68d9b41c16be3713vcc1); ARRAY(0x7f17328); HASH(0x8e6a180)
WEB_192.168.69.69_34854 FW_Notify 2897 4760 189056.63 39.72 0.00 0.00 30.01. 23:30:06 HASH(WEB_192.168.69.69_34854); HASH(Fernseher_bfb7810a3e397c5fa4u7ud)
Fernseher_bfb7810a3e397c5fa4u7ud fhempy_Set 2888 443 56820.96 128.26 0.00 0.00 30.01. 23:30:06 HASH(Fernseher_bfb7810a3e397c5fa4u7ud); ARRAY(0x836f0e8); HASH(0x89a7980)
tuya_local_bf881b7977c814af88jmrc fhempy_Set 2745 237 96374.31 406.64 0.00 0.00 30.01. 23:30:06 HASH(tuya_local_bf881b7977c814af88jmrc); ARRAY(0x8452168); HASH(0x8e223c8)
tuya_local_bf68d9b41c16be3713vcc1 fhempy_Set 2649 222 94437.72 425.40 0.00 0.00 30.01. 23:32:24 HASH(tuya_local_bf68d9b41c16be3713vcc1); ARRAY(0x8f60970); HASH(0x91b40d8)
Computer_Stefan_bf881b7977c814af88jmrc fhempy_Set 2499 506 58722.53 116.05 0.00 0.00 30.01. 23:34:05 HASH(Computer_Stefan_bf881b7977c814af88jmrc); ARRAY(0x918d2f0); HASH(0x924bf00)
tuya_local_bfb7810a3e397c5fa4u7ud fhempy_Set 2293 223 89811.46 402.74 0.00 0.00 30.01. 23:32:38 HASH(tuya_local_bfb7810a3e397c5fa4u7ud); ARRAY(0x8e87138); HASH(0x8730058)
WEB_192.168.69.94_57716 FW_Notify 2164 4760 151801.55 31.89 0.00 0.00 30.01. 23:31:04 HASH(WEB_192.168.69.94_57716); HASH(tuya_local_bf7bbcb9a4b03a2c97cqid)
tuya_local_bf7bbcb9a4b03a2c97cqid fhempy_Set 2158 232 40378.17 174.04 0.00 0.00 30.01. 23:31:04 HASH(tuya_local_bf7bbcb9a4b03a2c97cqid); ARRAY(0x8b44e68); HASH(0x8f845d8)
tuya_local_bf0572e0fb6ccbe356ykuh fhempy_Set 2093 163 29876.03 183.29 0.00 0.00 30.01. 23:34:44 HASH(tuya_local_bf0572e0fb6ccbe356ykuh); ARRAY(0x8fc38e8); HASH(0x8f47ae0)
tuya_cloud_bffa550a829a269630vhcn fhempy_Set 1894 2 1903.53 951.76 0.00 0.00 30.01. 23:31:53 HASH(tuya_cloud_bffa550a829a269630vhcn); ARRAY(0x8e43270); HASH(0x8b4ddf0)
Stefan_Tablet_bf0572e0fb6ccbe356ykuh fhempy_Set 1889 323 39856.40 123.39 0.00 0.00 30.01. 23:30:05 HASH(Stefan_Tablet_bf0572e0fb6ccbe356ykuh); ARRAY(0x8b42350); HASH(0x8e40298)
Fernseher_Schlafzimmer_bf4f644bc7dd2fc71d9q52 fhempy_Set 1573 161 21112.36 131.13 0.00 0.00 30.01. 23:32:06 HASH(Fernseher_Schlafzimmer_bf4f644bc7dd2fc71d9q52); ARRAY(0x86ad280); HASH(0x7cdf940)
Und hier die Fehler im Log:
2023.01.30 23:24:40 1: readingsUpdate(Computer_Stefan_bf881b7977c814af88jmrc,switch_inching,) missed to call readingsBeginUpdate first.
2023.01.30 23:24:40 1: stacktrace:
2023.01.30 23:24:40 1: main::readingsBulkUpdate called by (eval 2596951) (1)
2023.01.30 23:24:40 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.30 23:24:40 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.30 23:24:40 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (425)
2023.01.30 23:24:40 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.30 23:24:40 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.30 23:24:40 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.30 23:24:40 1: main::CallFn called by fhem.pl (1954)
2023.01.30 23:24:40 1: main::DoSet called by fhem.pl (1996)
2023.01.30 23:24:40 1: main::CommandSet called by fhem.pl (2904)
2023.01.30 23:24:40 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.30 23:24:40 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.30 23:24:40 1: main::FW_Notify called by fhem.pl (3976)
2023.01.30 23:24:40 1: main::CallFn called by fhem.pl (3888)
2023.01.30 23:24:40 1: main::DoTrigger called by fhem.pl (4995)
2023.01.30 23:24:40 1: main::readingsEndUpdate called by (eval 2596927) (1)
2023.01.30 23:24:40 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.30 23:24:40 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.30 23:24:40 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (425)
2023.01.30 23:24:40 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.30 23:24:40 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.30 23:24:40 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.30 23:24:40 1: main::CallFn called by fhem.pl (1954)
2023.01.30 23:24:40 1: main::DoSet called by fhem.pl (1996)
2023.01.30 23:24:40 1: main::CommandSet called by fhem.pl (2904)
2023.01.30 23:24:40 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.30 23:24:40 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.30 23:24:40 1: main::FW_Notify called by fhem.pl (3976)
2023.01.30 23:24:40 1: main::CallFn called by fhem.pl (3888)
2023.01.30 23:24:40 1: main::DoTrigger called by fhem.pl (4995)
2023.01.30 23:24:40 1: main::readingsEndUpdate called by (eval 2596926) (1)
2023.01.30 23:24:40 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.30 23:24:40 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.30 23:24:40 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (425)
2023.01.30 23:24:40 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.30 23:24:40 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.30 23:24:40 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.30 23:24:40 1: main::CallFn called by fhem.pl (1954)
2023.01.30 23:24:40 1: main::DoSet called by fhem.pl (1996)
2023.01.30 23:24:40 1: main::CommandSet called by fhem.pl (2904)
2023.01.30 23:24:40 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.30 23:24:40 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.30 23:24:40 1: main::FW_Notify called by fhem.pl (3976)
2023.01.30 23:24:40 1: main::CallFn called by fhem.pl (3888)
2023.01.30 23:24:40 1: main::DoTrigger called by fhem.pl (4995)
2023.01.30 23:24:40 1: main::readingsEndUpdate called by (eval 2596925) (1)
2023.01.30 23:24:40 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.30 23:24:40 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.30 23:24:43 1: readingsUpdate(Computer_Stefan_bf881b7977c814af88jmrc,light_mode,relay) missed to call readingsBeginUpdate first.
2023.01.30 23:24:43 1: stacktrace:
2023.01.30 23:24:43 1: main::readingsBulkUpdate called by (eval 2597106) (1)
2023.01.30 23:24:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.30 23:24:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.30 23:24:43 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (409)
2023.01.30 23:24:43 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.30 23:24:43 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.30 23:24:43 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.30 23:24:43 1: main::CallFn called by fhem.pl (1954)
2023.01.30 23:24:43 1: main::DoSet called by fhem.pl (1996)
2023.01.30 23:24:43 1: main::CommandSet called by fhem.pl (2904)
2023.01.30 23:24:43 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.30 23:24:43 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.30 23:24:43 1: main::FW_Notify called by fhem.pl (3976)
2023.01.30 23:24:43 1: main::CallFn called by fhem.pl (3888)
2023.01.30 23:24:43 1: main::DoTrigger called by fhem.pl (4995)
2023.01.30 23:24:43 1: main::readingsEndUpdate called by (eval 2597105) (1)
2023.01.30 23:24:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.30 23:24:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.30 23:24:43 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (425)
2023.01.30 23:24:43 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.30 23:24:43 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.30 23:24:43 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.30 23:24:43 1: main::CallFn called by fhem.pl (1954)
2023.01.30 23:24:43 1: main::DoSet called by fhem.pl (1996)
2023.01.30 23:24:43 1: main::CommandSet called by fhem.pl (2904)
2023.01.30 23:24:43 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.30 23:24:43 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.30 23:24:43 1: main::FW_Notify called by fhem.pl (3976)
2023.01.30 23:24:43 1: main::CallFn called by fhem.pl (3888)
2023.01.30 23:24:43 1: main::DoTrigger called by fhem.pl (4995)
2023.01.30 23:24:43 1: main::readingsEndUpdate called by (eval 2597094) (1)
2023.01.30 23:24:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.30 23:24:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.30 23:24:43 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.30 23:24:43 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.30 23:24:43 1: main::CallFn called by fhem.pl (784)
2023.01.30 23:24:43 1: readingsUpdate(Computer_Stefan_bf881b7977c814af88jmrc,child_lock,off) missed to call readingsBeginUpdate first.
2023.01.30 23:24:43 1: stacktrace:
2023.01.30 23:24:43 1: main::readingsBulkUpdate called by (eval 2597113) (1)
2023.01.30 23:24:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.30 23:24:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.30 23:24:43 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (425)
2023.01.30 23:24:43 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.30 23:24:43 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.30 23:24:43 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.30 23:24:43 1: main::CallFn called by fhem.pl (1954)
2023.01.30 23:24:43 1: main::DoSet called by fhem.pl (1996)
2023.01.30 23:24:43 1: main::CommandSet called by fhem.pl (2904)
2023.01.30 23:24:43 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.30 23:24:43 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.30 23:24:43 1: main::FW_Notify called by fhem.pl (3976)
2023.01.30 23:24:43 1: main::CallFn called by fhem.pl (3888)
2023.01.30 23:24:43 1: main::DoTrigger called by fhem.pl (4995)
2023.01.30 23:24:43 1: main::readingsEndUpdate called by (eval 2597105) (1)
2023.01.30 23:24:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.30 23:24:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.30 23:24:43 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (425)
2023.01.30 23:24:43 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.30 23:24:43 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.30 23:24:43 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.30 23:24:43 1: main::CallFn called by fhem.pl (1954)
2023.01.30 23:24:43 1: main::DoSet called by fhem.pl (1996)
2023.01.30 23:24:43 1: main::CommandSet called by fhem.pl (2904)
2023.01.30 23:24:43 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.30 23:24:43 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.30 23:24:43 1: main::FW_Notify called by fhem.pl (3976)
2023.01.30 23:24:43 1: main::CallFn called by fhem.pl (3888)
2023.01.30 23:24:43 1: main::DoTrigger called by fhem.pl (4995)
2023.01.30 23:24:43 1: main::readingsEndUpdate called by (eval 2597094) (1)
2023.01.30 23:24:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.30 23:24:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.30 23:24:43 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.30 23:24:43 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.30 23:24:43 1: main::CallFn called by fhem.pl (784)
2023.01.30 23:24:43 1: readingsUpdate(Computer_Stefan_bf881b7977c814af88jmrc,cycle_time,) missed to call readingsBeginUpdate first.
2023.01.30 23:24:43 1: stacktrace:
2023.01.30 23:24:43 1: main::readingsBulkUpdate called by (eval 2597114) (1)
2023.01.30 23:24:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.30 23:24:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.30 23:24:43 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (409)
2023.01.30 23:24:43 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.30 23:24:43 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.30 23:24:43 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.30 23:24:43 1: main::CallFn called by fhem.pl (1954)
2023.01.30 23:24:43 1: main::DoSet called by fhem.pl (1996)
2023.01.30 23:24:43 1: main::CommandSet called by fhem.pl (2904)
2023.01.30 23:24:43 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.30 23:24:43 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.30 23:24:43 1: main::FW_Notify called by fhem.pl (3976)
2023.01.30 23:24:43 1: main::CallFn called by fhem.pl (3888)
2023.01.30 23:24:43 1: main::DoTrigger called by fhem.pl (4995)
2023.01.30 23:24:43 1: main::readingsEndUpdate called by (eval 2597105) (1)
2023.01.30 23:24:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.30 23:24:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.30 23:24:43 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (425)
2023.01.30 23:24:43 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.30 23:24:43 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.30 23:24:43 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.30 23:24:43 1: main::CallFn called by fhem.pl (1954)
2023.01.30 23:24:43 1: main::DoSet called by fhem.pl (1996)
2023.01.30 23:24:43 1: main::CommandSet called by fhem.pl (2904)
2023.01.30 23:24:43 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.30 23:24:43 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.30 23:24:43 1: main::FW_Notify called by fhem.pl (3976)
2023.01.30 23:24:43 1: main::CallFn called by fhem.pl (3888)
2023.01.30 23:24:43 1: main::DoTrigger called by fhem.pl (4995)
2023.01.30 23:24:43 1: main::readingsEndUpdate called by (eval 2597094) (1)
2023.01.30 23:24:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.30 23:24:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.30 23:24:43 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.30 23:24:43 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.30 23:24:43 1: main::CallFn called by fhem.pl (784)
2023.01.30 23:24:43 1: readingsUpdate(Computer_Stefan_bf881b7977c814af88jmrc,random_time,) missed to call readingsBeginUpdate first.
2023.01.30 23:24:43 1: stacktrace:
2023.01.30 23:24:43 1: main::readingsBulkUpdate called by (eval 2597121) (1)
2023.01.30 23:24:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.30 23:24:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.30 23:24:43 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (425)
2023.01.30 23:24:43 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.30 23:24:43 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.30 23:24:43 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.30 23:24:43 1: main::CallFn called by fhem.pl (1954)
2023.01.30 23:24:43 1: main::DoSet called by fhem.pl (1996)
2023.01.30 23:24:43 1: main::CommandSet called by fhem.pl (2904)
2023.01.30 23:24:43 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.30 23:24:43 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.30 23:24:43 1: main::FW_Notify called by fhem.pl (3976)
2023.01.30 23:24:43 1: main::CallFn called by fhem.pl (3888)
2023.01.30 23:24:43 1: main::DoTrigger called by fhem.pl (4995)
2023.01.30 23:24:43 1: main::readingsEndUpdate called by (eval 2597120) (1)
2023.01.30 23:24:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.30 23:24:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.30 23:24:43 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (425)
2023.01.30 23:24:43 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.30 23:24:43 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.30 23:24:43 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.30 23:24:43 1: main::CallFn called by fhem.pl (1954)
2023.01.30 23:24:43 1: main::DoSet called by fhem.pl (1996)
2023.01.30 23:24:43 1: main::CommandSet called by fhem.pl (2904)
2023.01.30 23:24:43 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.30 23:24:43 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.30 23:24:43 1: main::FW_Notify called by fhem.pl (3976)
2023.01.30 23:24:43 1: main::CallFn called by fhem.pl (3888)
2023.01.30 23:24:43 1: main::DoTrigger called by fhem.pl (4995)
2023.01.30 23:24:43 1: main::readingsEndUpdate called by (eval 2597105) (1)
2023.01.30 23:24:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.30 23:24:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.30 23:24:43 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (425)
2023.01.30 23:24:43 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.30 23:24:43 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.30 23:24:43 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.30 23:24:43 1: main::CallFn called by fhem.pl (1954)
2023.01.30 23:24:43 1: main::DoSet called by fhem.pl (1996)
2023.01.30 23:24:43 1: main::CommandSet called by fhem.pl (2904)
2023.01.30 23:24:43 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.30 23:24:43 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.30 23:24:43 1: main::FW_Notify called by fhem.pl (3976)
2023.01.30 23:24:43 1: main::CallFn called by fhem.pl (3888)
2023.01.30 23:24:43 1: main::DoTrigger called by fhem.pl (4995)
2023.01.30 23:24:43 1: main::readingsEndUpdate called by (eval 2597094) (1)
2023.01.30 23:24:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.30 23:24:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.30 23:24:43 1: readingsUpdate(Computer_Stefan_bf881b7977c814af88jmrc,switch_inching,) missed to call readingsBeginUpdate first.
2023.01.30 23:24:43 1: stacktrace:
2023.01.30 23:24:43 1: main::readingsBulkUpdate called by (eval 2597127) (1)
2023.01.30 23:24:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.30 23:24:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.30 23:24:43 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (425)
2023.01.30 23:24:43 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.30 23:24:43 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.30 23:24:43 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.30 23:24:43 1: main::CallFn called by fhem.pl (1954)
2023.01.30 23:24:43 1: main::DoSet called by fhem.pl (1996)
2023.01.30 23:24:43 1: main::CommandSet called by fhem.pl (2904)
2023.01.30 23:24:43 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.30 23:24:43 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.30 23:24:43 1: main::FW_Notify called by fhem.pl (3976)
2023.01.30 23:24:43 1: main::CallFn called by fhem.pl (3888)
2023.01.30 23:24:43 1: main::DoTrigger called by fhem.pl (4995)
2023.01.30 23:24:43 1: main::readingsEndUpdate called by (eval 2597124) (1)
2023.01.30 23:24:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.30 23:24:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.30 23:24:43 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (425)
2023.01.30 23:24:43 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.30 23:24:43 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.30 23:24:43 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.30 23:24:43 1: main::CallFn called by fhem.pl (1954)
2023.01.30 23:24:43 1: main::DoSet called by fhem.pl (1996)
2023.01.30 23:24:43 1: main::CommandSet called by fhem.pl (2904)
2023.01.30 23:24:43 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.30 23:24:43 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.30 23:24:43 1: main::FW_Notify called by fhem.pl (3976)
2023.01.30 23:24:43 1: main::CallFn called by fhem.pl (3888)
2023.01.30 23:24:43 1: main::DoTrigger called by fhem.pl (4995)
2023.01.30 23:24:43 1: main::readingsEndUpdate called by (eval 2597120) (1)
2023.01.30 23:24:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.30 23:24:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.30 23:24:43 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (425)
2023.01.30 23:24:43 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.30 23:24:43 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.30 23:24:43 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.30 23:24:43 1: main::CallFn called by fhem.pl (1954)
2023.01.30 23:24:43 1: main::DoSet called by fhem.pl (1996)
2023.01.30 23:24:43 1: main::CommandSet called by fhem.pl (2904)
2023.01.30 23:24:43 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.30 23:24:43 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.30 23:24:43 1: main::FW_Notify called by fhem.pl (3976)
2023.01.30 23:24:43 1: main::CallFn called by fhem.pl (3888)
2023.01.30 23:24:43 1: main::DoTrigger called by fhem.pl (4995)
2023.01.30 23:24:43 1: main::readingsEndUpdate called by (eval 2597105) (1)
2023.01.30 23:24:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.30 23:24:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
Hast du Devices gelöscht? Mach mal ein save und dann nur einen fhempy restart.
Hi Dominik,
nein ich hab keine Devices gelöscht.
Ja save und restart habe ich gamcht, hat leider nicht geholfen.
Habe auch schon fhem komplett neu gestartet und auch den ganzen Rapberry.
Hat aber alles nicht geholfen.
Kann ich dir noch irgendwelche Logs zeigen?
Hier noch ein List des local bindings:
Internals:
BindingType fhempy
DEF fhempy
DeviceName ws:localhost:15733
FD 51
FUUID 61ebfd4f-f33f-0c45-6307-c6f25f4c826817c3
IP 127.0.0.1
NAME local_pybinding
NR 2079
NTFY_ORDER 50-local_pybinding
PARTIAL
PORT 15733
STATE opened
TYPE BindingsIo
WEBSOCKET 1
binary 1
connecttime 1675118510.5041
devioLoglevel 0
eventCount 1
installing 0
localBinding 1
nextOpenDelay 10
prev_error
READINGS:
2023-01-30 12:39:49 hostname raspberrypi
2023-01-30 12:39:49 os posix
2023-01-30 12:39:49 python 3.9.2
2023-01-30 12:39:49 release 5.15.84-v7+
2023-01-30 23:41:50 state opened
2023-01-30 12:39:49 system Linux
2023-01-30 12:39:49 version 0.1.578
2023-01-30 21:32:47 version_available 0.1.580
2023-01-30 21:32:47 version_release_notes <html><a href="https://github.com/fhempy/fhempy/releases" target="_blank">Release Notes</a></html>
args:
local_pybinding
BindingsIo
fhempy
Attributes:
devStateIcon { my $status_img = "10px-kreis-gruen";; my $status_txt = "connected";; if (ReadingsVal($name, "state", "disconnected") eq "disconnected") { $status_img = "10px-kreis-rot";; $status_txt = "disconnected";; } my $ver = ReadingsVal($name, "version", "-");; "<div><a>".FW_makeImage($status_img, $status_txt)."</a><a> ".$ver." </a><a href=\"/fhem?cmd.dummy=set $name update&XHR=1\" title=\"Start update\">".FW_makeImage("refresh")."</a></div>" }
group fhempy
icon file_json-ld2
room fhempy
verbose 0
Oh ich sehe es gibt eine neue Version. Ich mach mal ein Update.
Gruß,
Stefan
Teste bitte mit 0.1.581 und schau ob im fhempy Log ein Fehler auftritt.
Zitat von: dominik am 31 Januar 2023, 00:10:36
Teste bitte mit 0.1.581 und schau ob im fhempy Log ein Fehler auftritt.
Guten Morgen Dominik,
es sieht nun ein wenig besser aus:
fhempy-log:
2023-01-31 09:23:41,543 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_PS2'},'state','on');;
2023-01-31 09:23:41,544 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_EMYLO1'},'countdown_1','0.0');;
2023-01-31 09:23:41,544 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL26'},'state','on');;
2023-01-31 09:23:41,550 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SCHF3'},'state','off');;
2023-01-31 09:23:41,553 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL08'},'cur_current','0.0');;
2023-01-31 09:23:41,554 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL34'},'state','off');;
2023-01-31 09:23:41,557 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL31'},'state','off');;
2023-01-31 09:23:41,558 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP06'},'state','off');;
2023-01-31 09:23:41,566 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL35'},'state','on');;
2023-01-31 09:23:41,570 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP05'},'state','on');;
2023-01-31 09:23:41,570 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL28'},'state','off');;
2023-01-31 09:23:41,571 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsEndUpdate($defs{'TUYA_JL15'},1);;
2023-01-31 09:23:41,601 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'TUYA_SP07'});;
2023-01-31 09:23:41,604 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'TUYA_SP09'});;
2023-01-31 09:23:41,605 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'TUYA_SP08'});;
2023-01-31 09:23:41,614 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP01'},'state','on');;
2023-01-31 09:23:41,616 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP03'},'state','on');;
2023-01-31 09:23:41,616 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_EMYLO2'},'dp_101','0');;
2023-01-31 09:23:41,618 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP02'},'state','on');;
2023-01-31 09:23:41,618 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_EMYLO3'},'countdown_1','0.0');;
2023-01-31 09:23:41,620 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL04'},'countdown_1','0.0');;
2023-01-31 09:23:41,622 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL06'},'countdown_1','0.0');;
2023-01-31 09:23:41,623 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL07'},'countdown_1','0.0');;
2023-01-31 09:23:41,625 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL25'},'cur_power','48.0');;
2023-01-31 09:23:41,626 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL21'},'countdown_1','0.0');;
2023-01-31 09:23:41,628 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL29'},'countdown_1','0.0');;
2023-01-31 09:23:41,630 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL24'},'countdown_1','0.0');;
2023-01-31 09:23:41,631 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_MMG'},'state','off');;
2023-01-31 09:23:41,633 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL09'},'countdown_1','0.0');;
2023-01-31 09:23:41,637 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL18'},'countdown_1','0.0');;
2023-01-31 09:23:41,637 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL11Z'},'countdown_1','0.0');;
2023-01-31 09:23:41,639 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL13'},'countdown_1','0.0');;
2023-01-31 09:23:41,641 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL20'},'countdown_1','0.0');;
2023-01-31 09:23:41,643 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP11'},'cur_power','8.3');;
2023-01-31 09:23:41,645 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SCHF2'},'switch_2','off');;
2023-01-31 09:23:41,646 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_EMYLO4'},'countdown_1','0.0');;
2023-01-31 09:23:41,647 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsEndUpdate($defs{'TUYA_DIY3'},1);;
2023-01-31 09:23:41,649 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL27'},'countdown_1','0.0');;
2023-01-31 09:23:41,649 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP16'},'cur_voltage','227.3');;
2023-01-31 09:23:41,651 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SCHF1'},'countdown_1','0.0');;
2023-01-31 09:23:41,693 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL33'},'countdown_1','0.0');;
Folgende Devices wurden übrigens von tuya_cloud doppelt erfasst; sie waren in _local schon angelegt
tuya_cloud
Bad 2
on
off
Balkon Stern
on
off
Dimmer 2
on
off
EMYLOD
on
off
Garagentor
on
off
Globus
on
off
Heizdecke 1
on
off
Heizdecke 3
on
off
Heizkissen 2
on
off
JL06 frei
on
off
JL07 BKT2
on
off
JL11Z UV Pflanzenlampe
on
off
Kaffeemaschine XELSIS
on
off
Kleiderschrank 1
on
off
Kleiderschrank 2
on
off
Kueche Herd
on
off
Kueche oben
on
off
Medien THOMAS
on
off
erklärbare wäre dies zu großen Teilen, dass die Schaltsteckdosen JL oder EMYLO Mini schlicht nicht eingesteckt oder installiert sind.
BULBS sind doppelt. Der SChalter EMYLOx ist aber installiert und doppelt vorhanden.
Aus mneiner Sicht wäre es nützlich, das tuya_cloud nach Gerätetyp filtern könnte ; so das z.B. nur Temperaturt Sensoren eingelesen werden.
Cameras und PIR-Sensoren geben ja eh keinen Sinn.
Anregung:
im Modul Buderus km200 kann man mit "DoNotPoll" einzelne readings ausblenden.
und die pollingtime einstellen.
Auch das deaktiveren von Geräten wie in "at" wäre schick. So könnten zwar alle erfasst werden, der Müll aber ausgeblendet werden.
In jedem Fall sollten tuya_cloud und tuya_cloud (wie von dir geplant) echt disjunkt ohne Redundanzen Tuya-devices anlegen.
Vielen Dank für deine excellente Mühe
Thomas
Hi Dominik,
habe geupdated.
Fhem kommt mir wieder schneller vor, doch jetzt hatte ich doch wieder Probleme im Log.
Es scheint nun aber tuya_local zu betreffen!
Hätte ich nach dem Update neu starten müssen?
Hier das log:
2023.01.31 11:15:33 1: readingsUpdate(tuya_local_bf4f644bc7dd2fc71d9q52,state,on) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.01.31 11:15:33 1: main::readingsBulkUpdateIfChanged called by (eval 2692630) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(tuya_local_bf68d9b41c16be3713vcc1,cur_current,93.0) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.01.31 11:15:33 1: main::readingsBulkUpdateIfChanged called by (eval 2692644) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (425)
2023.01.31 11:15:33 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.31 11:15:33 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.31 11:15:33 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (1954)
2023.01.31 11:15:33 1: main::DoSet called by fhem.pl (1996)
2023.01.31 11:15:33 1: main::CommandSet called by fhem.pl (2904)
2023.01.31 11:15:33 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.31 11:15:33 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.31 11:15:33 1: main::FW_Notify called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (3888)
2023.01.31 11:15:33 1: main::DoTrigger called by fhem.pl (4995)
2023.01.31 11:15:33 1: main::readingsEndUpdate called by (eval 2692643) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(tuya_local_bf68d9b41c16be3713vcc1,cur_power,12.3) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.01.31 11:15:33 1: main::readingsBulkUpdateIfChanged called by (eval 2692645) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (425)
2023.01.31 11:15:33 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.31 11:15:33 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.31 11:15:33 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (1954)
2023.01.31 11:15:33 1: main::DoSet called by fhem.pl (1996)
2023.01.31 11:15:33 1: main::CommandSet called by fhem.pl (2904)
2023.01.31 11:15:33 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.31 11:15:33 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.31 11:15:33 1: main::FW_Notify called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (3888)
2023.01.31 11:15:33 1: main::DoTrigger called by fhem.pl (4995)
2023.01.31 11:15:33 1: main::readingsEndUpdate called by (eval 2692643) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,state,on) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by (eval 2692646) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,countdown_1,0.0) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by (eval 2692649) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,add_ele,0.001) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by (eval 2692652) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,cur_current,92.0) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by (eval 2692655) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,cur_power,11.5) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by (eval 2692658) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,cur_voltage,230.8) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by (eval 2692661) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (425)
2023.01.31 11:15:33 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.31 11:15:33 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.31 11:15:33 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (1954)
2023.01.31 11:15:33 1: main::DoSet called by fhem.pl (1996)
2023.01.31 11:15:33 1: main::CommandSet called by fhem.pl (2904)
2023.01.31 11:15:33 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.31 11:15:33 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.31 11:15:33 1: main::FW_Notify called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (3888)
2023.01.31 11:15:33 1: main::DoTrigger called by fhem.pl (4995)
2023.01.31 11:15:33 1: main::readingsEndUpdate called by (eval 2692660) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,relay_status,last) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by (eval 2692663) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (425)
2023.01.31 11:15:33 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.31 11:15:33 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.31 11:15:33 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (1954)
2023.01.31 11:15:33 1: main::DoSet called by fhem.pl (1996)
2023.01.31 11:15:33 1: main::CommandSet called by fhem.pl (2904)
2023.01.31 11:15:33 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.31 11:15:33 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.31 11:15:33 1: main::FW_Notify called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (3888)
2023.01.31 11:15:33 1: main::DoTrigger called by fhem.pl (4995)
2023.01.31 11:15:33 1: main::readingsEndUpdate called by (eval 2692660) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,overcharge_switch,off) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by (eval 2692688) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,light_mode,relay) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by (eval 2692691) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (425)
2023.01.31 11:15:33 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.31 11:15:33 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.31 11:15:33 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (1954)
2023.01.31 11:15:33 1: main::DoSet called by fhem.pl (1996)
2023.01.31 11:15:33 1: main::CommandSet called by fhem.pl (2904)
2023.01.31 11:15:33 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.31 11:15:33 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.31 11:15:33 1: main::FW_Notify called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (3888)
2023.01.31 11:15:33 1: main::DoTrigger called by fhem.pl (4995)
2023.01.31 11:15:33 1: main::readingsEndUpdate called by (eval 2692689) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,child_lock,off) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by (eval 2692693) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (425)
2023.01.31 11:15:33 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.31 11:15:33 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.31 11:15:33 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (1954)
2023.01.31 11:15:33 1: main::DoSet called by fhem.pl (1996)
2023.01.31 11:15:33 1: main::CommandSet called by fhem.pl (2904)
2023.01.31 11:15:33 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.31 11:15:33 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.31 11:15:33 1: main::FW_Notify called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (3888)
2023.01.31 11:15:33 1: main::DoTrigger called by fhem.pl (4995)
2023.01.31 11:15:33 1: main::readingsEndUpdate called by (eval 2692689) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,cycle_time,) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by (eval 2692695) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,random_time,) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by (eval 2692698) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,switch_inching,) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by (eval 2692701) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (425)
2023.01.31 11:15:33 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.31 11:15:33 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.31 11:15:33 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (1954)
2023.01.31 11:15:33 1: main::DoSet called by fhem.pl (1996)
2023.01.31 11:15:33 1: main::CommandSet called by fhem.pl (2904)
2023.01.31 11:15:33 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.31 11:15:33 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.31 11:15:33 1: main::FW_Notify called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (3888)
2023.01.31 11:15:33 1: main::DoTrigger called by fhem.pl (4995)
2023.01.31 11:15:33 1: main::readingsEndUpdate called by (eval 2692700) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
Danke und Gruß,
Stefan
Zitat von: stefanru am 31 Januar 2023, 11:42:46
Hätte ich nach dem Update neu starten müssen?
FHEM shutdown restart ist ein Muss ;-)
manchmal hilft auch ein reboot des Systems
Zitat von: thburkhart am 31 Januar 2023, 12:54:00
FHEM shutdown restart ist ein Muss ;-)
manchmal hilft auch ein reboot des Systems
Nein, bitte keinesfall! Es reicht vollkommen aus ein fhempy restart zu machen. FHEM kannst ohne weiteres weiter laufen - außer man hat ein FHEM "update" gemacht.
Zitat von: thburkhart am 31 Januar 2023, 10:01:41
In jedem Fall sollten tuya_cloud und tuya_cloud (wie von dir geplant) echt disjunkt ohne Redundanzen Tuya-devices anlegen.
Nachdem du so viele NO RESPONSE hast, gehe ich davon aus, dass auch die Abfrage nach vorhandenen DEVICEIDs aus FHEM keine Antwort geliefert hat. Nur in so einem Fall, werden die doppelt angelegt, sonst nicht.
Bekommst du die NO RESPONSE nach jedem fhempy Neustart? Ich versuche die Thematik gerade einzugrenzen, ob es wirklich am überlasteten FHEM liegt, oder noch andere Gründe hat.
Zitat von: stefanru am 31 Januar 2023, 11:42:46
Hi Dominik,
habe geupdated.
Fhem kommt mir wieder schneller vor, doch jetzt hatte ich doch wieder Probleme im Log.
Es scheint nun aber tuya_local zu betreffen!
Hätte ich nach dem Update neu starten müssen?
Hier das log:
2023.01.31 11:15:33 1: readingsUpdate(tuya_local_bf4f644bc7dd2fc71d9q52,state,on) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.01.31 11:15:33 1: main::readingsBulkUpdateIfChanged called by (eval 2692630) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(tuya_local_bf68d9b41c16be3713vcc1,cur_current,93.0) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.01.31 11:15:33 1: main::readingsBulkUpdateIfChanged called by (eval 2692644) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (425)
2023.01.31 11:15:33 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.31 11:15:33 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.31 11:15:33 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (1954)
2023.01.31 11:15:33 1: main::DoSet called by fhem.pl (1996)
2023.01.31 11:15:33 1: main::CommandSet called by fhem.pl (2904)
2023.01.31 11:15:33 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.31 11:15:33 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.31 11:15:33 1: main::FW_Notify called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (3888)
2023.01.31 11:15:33 1: main::DoTrigger called by fhem.pl (4995)
2023.01.31 11:15:33 1: main::readingsEndUpdate called by (eval 2692643) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(tuya_local_bf68d9b41c16be3713vcc1,cur_power,12.3) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.01.31 11:15:33 1: main::readingsBulkUpdateIfChanged called by (eval 2692645) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (425)
2023.01.31 11:15:33 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.31 11:15:33 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.31 11:15:33 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (1954)
2023.01.31 11:15:33 1: main::DoSet called by fhem.pl (1996)
2023.01.31 11:15:33 1: main::CommandSet called by fhem.pl (2904)
2023.01.31 11:15:33 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.31 11:15:33 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.31 11:15:33 1: main::FW_Notify called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (3888)
2023.01.31 11:15:33 1: main::DoTrigger called by fhem.pl (4995)
2023.01.31 11:15:33 1: main::readingsEndUpdate called by (eval 2692643) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,state,on) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by (eval 2692646) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,countdown_1,0.0) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by (eval 2692649) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,add_ele,0.001) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by (eval 2692652) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,cur_current,92.0) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by (eval 2692655) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,cur_power,11.5) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by (eval 2692658) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,cur_voltage,230.8) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by (eval 2692661) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (425)
2023.01.31 11:15:33 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.31 11:15:33 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.31 11:15:33 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (1954)
2023.01.31 11:15:33 1: main::DoSet called by fhem.pl (1996)
2023.01.31 11:15:33 1: main::CommandSet called by fhem.pl (2904)
2023.01.31 11:15:33 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.31 11:15:33 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.31 11:15:33 1: main::FW_Notify called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (3888)
2023.01.31 11:15:33 1: main::DoTrigger called by fhem.pl (4995)
2023.01.31 11:15:33 1: main::readingsEndUpdate called by (eval 2692660) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,relay_status,last) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by (eval 2692663) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (425)
2023.01.31 11:15:33 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.31 11:15:33 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.31 11:15:33 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (1954)
2023.01.31 11:15:33 1: main::DoSet called by fhem.pl (1996)
2023.01.31 11:15:33 1: main::CommandSet called by fhem.pl (2904)
2023.01.31 11:15:33 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.31 11:15:33 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.31 11:15:33 1: main::FW_Notify called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (3888)
2023.01.31 11:15:33 1: main::DoTrigger called by fhem.pl (4995)
2023.01.31 11:15:33 1: main::readingsEndUpdate called by (eval 2692660) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,overcharge_switch,off) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by (eval 2692688) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,light_mode,relay) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by (eval 2692691) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (425)
2023.01.31 11:15:33 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.31 11:15:33 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.31 11:15:33 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (1954)
2023.01.31 11:15:33 1: main::DoSet called by fhem.pl (1996)
2023.01.31 11:15:33 1: main::CommandSet called by fhem.pl (2904)
2023.01.31 11:15:33 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.31 11:15:33 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.31 11:15:33 1: main::FW_Notify called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (3888)
2023.01.31 11:15:33 1: main::DoTrigger called by fhem.pl (4995)
2023.01.31 11:15:33 1: main::readingsEndUpdate called by (eval 2692689) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,child_lock,off) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by (eval 2692693) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (425)
2023.01.31 11:15:33 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.31 11:15:33 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.31 11:15:33 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (1954)
2023.01.31 11:15:33 1: main::DoSet called by fhem.pl (1996)
2023.01.31 11:15:33 1: main::CommandSet called by fhem.pl (2904)
2023.01.31 11:15:33 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.31 11:15:33 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.31 11:15:33 1: main::FW_Notify called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (3888)
2023.01.31 11:15:33 1: main::DoTrigger called by fhem.pl (4995)
2023.01.31 11:15:33 1: main::readingsEndUpdate called by (eval 2692689) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,cycle_time,) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by (eval 2692695) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,random_time,) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by (eval 2692698) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
2023.01.31 11:15:33 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,switch_inching,) missed to call readingsBeginUpdate first.
2023.01.31 11:15:33 1: stacktrace:
2023.01.31 11:15:33 1: main::readingsBulkUpdate called by (eval 2692701) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (425)
2023.01.31 11:15:33 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.01.31 11:15:33 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.01.31 11:15:33 1: main::fhempy_Set called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (1954)
2023.01.31 11:15:33 1: main::DoSet called by fhem.pl (1996)
2023.01.31 11:15:33 1: main::CommandSet called by fhem.pl (2904)
2023.01.31 11:15:33 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.01.31 11:15:33 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.01.31 11:15:33 1: main::FW_Notify called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (3888)
2023.01.31 11:15:33 1: main::DoTrigger called by fhem.pl (4995)
2023.01.31 11:15:33 1: main::readingsEndUpdate called by (eval 2692700) (1)
2023.01.31 11:15:33 1: (eval) called by ./FHEM/10_BindingsIo.pm (561)
2023.01.31 11:15:33 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (676)
2023.01.31 11:15:33 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (296)
2023.01.31 11:15:33 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 11:15:33 1: main::CallFn called by fhem.pl (784)
Danke und Gruß,
Stefan
Steht auch was im fhempy Log?
Zitat von: dominik am 31 Januar 2023, 17:12:00
Nachdem du so viele NO RESPONSE hast, gehe ich davon aus, dass auch die Abfrage nach vorhandenen DEVICEIDs aus FHEM keine Antwort geliefert hat. Nur in so einem Fall, werden die doppelt angelegt, sonst nicht.
ja das trifft für für einen Teil zu. Z.B. Das EMYLO Device ist jedoch Online
Zitat von: dominik am 31 Januar 2023, 17:12:00
Bekommst du die NO RESPONSE nach jedem fhempy Neustart? Ich versuche die Thematik gerade einzugrenzen, ob es wirklich am überlasteten FHEM liegt, oder noch andere Gründe hat.
habe ich aktuell nach Neustart FHEM bekommen:
2023-01-31 17:48:20,986 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_EMYLO4'},'state','off');;
2023-01-31 17:48:20,987 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP11'},'countdown_1','0.0');;
2023-01-31 17:48:20,988 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_BULB2'},'temp_value_v2','0.0');;
2023-01-31 17:48:20,989 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP07'},'state','off');;
2023-01-31 17:48:20,990 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP09'},'countdown_1','0.0');;
2023-01-31 17:48:20,991 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL09'},'countdown_1','0.0');;
2023-01-31 17:48:20,992 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SCHF1'},'state','on');;
2023-01-31 17:48:20,993 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP03'},'cur_power','27.0');;
2023-01-31 17:48:20,997 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL26'},'cur_current','0.0');;
2023-01-31 17:48:20,998 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL33'},'state','on');;
2023-01-31 17:48:20,999 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL21'},'cur_current','0.0');;
2023-01-31 17:48:20,999 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL31'},'cur_current','0.0');;
2023-01-31 17:48:20,999 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_MMG'},'master_state','normal');;
2023-01-31 17:48:21,000 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL24'},'cur_current','0.0');;
2023-01-31 17:48:21,002 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL20'},'cur_current','0.0');;
2023-01-31 17:48:21,003 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_PS2'},'switch_2','on');;
2023-01-31 17:48:21,004 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_STF1'},'relay_status','0');;
2023-01-31 17:48:21,005 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsEndUpdate($defs{'TUYA_EMYLO1'},1);;
2023-01-31 17:48:21,005 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsEndUpdate($defs{'TUYA_DIY3'},1);;
2023-01-31 17:48:21,006 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'TUYA_JL13'});;
2023-01-31 17:48:21,037 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP05'},'countdown_1','0.0');;
2023-01-31 17:48:21,039 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL34'},'countdown_1','0.0');;
2023-01-31 17:48:21,041 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL35'},'countdown_1','0.0');;
2023-01-31 17:48:21,043 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL36'},'countdown_1','0.0');;
2023-01-31 17:48:21,045 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP13'},'countdown_1','0.0');;
2023-01-31 17:48:21,047 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP01'},'countdown_1','0.0');;
2023-01-31 17:48:21,049 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL28'},'countdown_1','0.0');;
2023-01-31 17:48:21,050 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL15'},'countdown_1','0.0');;
2023-01-31 17:48:21,052 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP15'},'cur_current','38.0');;
2023-01-31 17:48:21,054 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP14'},'cur_current','81.0');;
2023-01-31 17:48:21,056 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL07'},'cur_power','0.0');;
2023-01-31 17:48:21,058 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SCHF2'},'switch_2','on');;
2023-01-31 17:48:21,060 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsEndUpdate($defs{'TUYA_EMYLO3'},1);;
2023-01-31 17:48:21,061 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL08'},'countdown_1','0.0');;
2023-01-31 17:48:21,063 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP12'},'dp_24','20947');;
2023-01-31 17:48:21,065 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL04'},'countdown_1','0.0');;
2023-01-31 17:48:21,067 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL18'},'countdown_1','0.0');;
2023-01-31 17:48:21,069 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP06'},'countdown_1','0.0');;
2023-01-31 17:48:21,071 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP02'},'cur_current','0.0');;
2023-01-31 17:48:21,072 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL27'},'countdown_1','0.0');;
2023-01-31 17:48:21,074 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL25'},'countdown_1','0.0');;
2023-01-31 17:48:21,076 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL29'},'countdown_1','0.0');;
2023-01-31 17:48:21,077 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsEndUpdate($defs{'TUYA_SCHF3'},1);;
2023-01-31 17:48:21,078 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_STF2'},'relay_status','0');;
2023-01-31 17:48:21,079 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP08'},'cur_current','0.0');;
2023-01-31 17:48:21,081 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL11Z'},'countdown_1','0.0');;
2023-01-31 17:48:21,082 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP16'},'cur_current','14.0');;
das sind die local- Devices, die aber in der Mehrzahl am Netz sind.
der room fhempy hat eben 30 min gebraucht, bis er wieder angezeigt wurde. In der Zeit passiert wohl intensiver Traffic zwischen PC und RASPI, sodass auch meine Internet-Verbing ausgebremst werden z.B. Outlook.
in tuya_cloud tauchen alle 36 Stecker-Schalter doppelt zu tuya auf; egal ob online oder offline
btw
gerne stehe ich dir zum Nachstellen, Überprüfung per TeamViewer zu Verfügung, sofern hilfreich
update
nach der erwähnten Gedenkpause:
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 180, in onMessage
await self._onMessage(payload)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 214, in _onMessage
await self.sendBackError(hash, "fhempy failed to handle message")
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 132, in sendBackError
duration = (time.time() - id_received_timestamp[retHash["id"]]) * 1000
KeyError: 'id'
2023-01-31 18:09:04,181 - ERROR - fhempy.lib.fhem: FHEM took 20028ms for readingsEndUpdate($defs{'TUYA_JL15'},1);;
2023-01-31 18:09:04,294 - ERROR - fhempy.lib.fhem: FHEM took 20142ms for readingsEndUpdate($defs{'TUYA_JL29'},1);;
2023-01-31 18:09:19,605 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsEndUpdate($defs{'tuya_cloud_bf4ae6b15fe239b42bxvpl'},1);;
2023-01-31 18:09:36,133 - ERROR - fhempy.lib.fhem: FHEM took 26983ms for readingsEndUpdate($defs{'TUYA_JL33'},1);;
2023-01-31 18:09:55,760 - ERROR - root: tuya_cloud_22230808807d3a23186b: readingsBeginUpdate couldn't acquire lock, caused by readingsBeginUpdate without End or Single update inbetween
2023-01-31 18:09:57,859 - ERROR - root: tuya_cloud_22230808807d3a23186b: readingsBeginUpdate couldn't acquire lock, caused by readingsBeginUpdate without End or Single update inbetween
2023-01-31 18:10:09,109 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_22230808bcddc213f838'},'state','off');;
2023-01-31 18:10:09,110 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP11'},'cur_current','83.0');;
2023-01-31 18:10:09,110 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL13'},'cur_voltage','222.5');;
2023-01-31 18:10:09,110 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'tuya_cloud_22230808807d3a231039'});;
2023-01-31 18:10:09,230 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_22230808807d3a23186b'},'cur_voltage','221.1');;
2023-01-31 18:10:39,096 - ERROR - fhempy.lib.fhem: FHEM took 25720ms for readingsEndUpdate($defs{'TUYA_JL18'},1);;
2023-01-31 18:10:39,229 - ERROR - fhempy.lib.fhem: FHEM took 25858ms for readingsEndUpdate($defs{'TUYA_JL33'},1);;
2023-01-31 18:10:39,706 - ERROR - fhempy.lib.fhem: FHEM took 26337ms for readingsEndUpdate($defs{'TUYA_JL15'},1);;
2023-01-31 18:10:50,064 - ERROR - fhempy.lib.fhem: FHEM took 36811ms for readingsEndUpdate($defs{'TUYA_JL31'},1);;
2023-01-31 18:10:50,185 - ERROR - fhempy.lib.fhem: FHEM took 36936ms for readingsEndUpdate($defs{'TUYA_JL04'},1);;
2023-01-31 18:10:54,267 - ERROR - fhempy.lib.fhem: FHEM took 41494ms for readingsEndUpdate($defs{'tuya_cloud_22230808807d3a23186b'},1);;
2023-01-31 18:10:56,589 - ERROR - fhempy.lib.fhem: FHEM took 43954ms for readingsEndUpdate($defs{'TUYA_JL20'},1);;
2023-01-31 18:11:08,281 - ERROR - fhempy.lib.fhem: FHEM took 55648ms for readingsEndUpdate($defs{'TUYA_JL21'},1);;
2023-01-31 18:11:08,283 - ERROR - fhempy.lib.fhem: FHEM took 58480ms for readingsEndUpdate($defs{'tuya_cloud_22230808bcddc213f838'},1);;
2023-01-31 18:11:36,374 - ERROR - fhempy.lib.fhem: FHEM took 22771ms for readingsEndUpdate($defs{'TUYA_JL13'},1);;
2023-01-31 18:11:36,498 - ERROR - fhempy.lib.fhem: FHEM took 22904ms for readingsEndUpdate($defs{'tuya_cloud_22230808807d3a231039'},1);;
da tauchen nun auch auch _cloud devices auf
'tuya_cloud_22230808807d3a23186b entspircht JL04 local und schaltet den Rechner, an dem ich eben sitze. Ist eben Doppelt
probier es bitte mit 0.1.584.
Damit sollte nun keine Devices doppelt angelegt werden und hoffentlich auch kein NO RESPONSE kommen. Bitte sowohl fhempy update UND FHEM update. Danach musst du shutdown restart machen, wg. FHEM update.
Zitat von: dominik am 31 Januar 2023, 18:31:35
probier es bitte mit 0.1.584.
Damit sollte nun keine Devices doppelt angelegt werden und hoffentlich auch kein NO RESPONSE kommen. Bitte sowohl fhempy update UND FHEM update. Danach musst du shutdown restart machen, wg. FHEM update.
ok
genau in der Reihenfolge ? werden die doppelten dann beseitigt oder soll ich manuell in der .cfg löschen?
1. Doppelten löschen
2. set fhempy_local update
3. update
4. shutdown restart
Ok,
fhempy.log zeigt ein ziemlich ähnliches Verhalten wie das von thburkhart.
023-01-31 20:21:32,565 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'Stefan_Tablet_bf0572e0fb6ccbe356ykuh'},'overcharge_switch','off');;
2023-01-31 20:21:35,602 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'tuya_local_bfb7810a3e397c5fa4u7ud'});;
2023-01-31 20:21:35,606 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'tuya_local_bf68d9b41c16be3713vcc1'});;
2023-01-31 20:21:35,613 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'tuya_local_bf7bbcb9a4b03a2c97cqid'});;
2023-01-31 20:21:35,640 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'tuya_local_bf881b7977c814af88jmrc'});;
2023-01-31 20:21:35,651 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'Fernseher_bfb7810a3e397c5fa4u7ud'});;
2023-01-31 20:21:35,658 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'Fernseher_Wohnzimmer_bf7bbcb9a4b03a2c97cqid'});;
2023-01-31 20:21:35,663 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'Sybille_Tablet_bf68d9b41c16be3713vcc1'});;
2023-01-31 20:21:35,683 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:21:39,599 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:21:40,696 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:21:45,708 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:21:49,611 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:21:50,721 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:21:55,734 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:21:59,625 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:21:59,635 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:22:00,748 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:22:05,762 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:22:09,640 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:22:10,777 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:22:15,791 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:22:19,653 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:22:20,805 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:22:25,820 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:22:29,665 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:22:30,833 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:22:35,847 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:22:39,679 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:22:40,861 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:22:45,874 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:22:49,691 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:22:50,887 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:22:55,901 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:22:59,650 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:22:59,704 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:23:00,123 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'Stefan_Tablet_bf0572e0fb6ccbe356ykuh'},'cur_voltage','232.5');;
2023-01-31 20:23:00,125 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'Fernseher_Wohnzimmer_bf7bbcb9a4b03a2c97cqid'},'add_ele','0.1');;
2023-01-31 20:23:00,915 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:23:05,929 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:23:09,717 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:23:10,946 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:23:15,959 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:23:19,730 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:23:20,971 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:23:25,984 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:23:29,743 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:23:30,999 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:23:36,013 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:23:39,756 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:23:41,026 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:23:46,040 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:23:49,770 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:23:51,054 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:23:56,067 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:23:59,665 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:23:59,783 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:24:01,081 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:24:06,094 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:24:09,795 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:24:11,108 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:24:16,121 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:24:19,809 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:24:21,135 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:24:26,149 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:24:29,822 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:24:31,161 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:24:36,174 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:24:39,837 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:24:41,187 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:24:46,200 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:24:49,849 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 20:24:51,214 - WARNING - asyncio: socket.send() raised exception.
Ich update auch und mach ein restart.
Danke,
Stefan
Ok,
habe geupdated und gleich beim starten folgendes im fhempy.log:
2023-01-31 20:32:47,440 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.584...
2023-01-31 20:32:47,446 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-01-31 20:32:47,527 - INFO - websockets.server: server listening on 0.0.0.0:15733
2023-01-31 20:32:56,018 - INFO - websockets.server: connection open
2023-01-31 20:32:56,019 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2023-01-31 20:36:22,987 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.584...
2023-01-31 20:36:22,993 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-01-31 20:36:23,076 - INFO - websockets.server: server listening on 0.0.0.0:15733
2023-01-31 20:36:28,489 - INFO - websockets.server: connection open
2023-01-31 20:36:28,490 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2023-01-31 20:37:32,521 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'tuya_local_bf0572e0fb6ccbe356ykuh'});;readingsBulkUpdateIfChanged($defs{'tuya_local_bf0572e0fb6ccbe356ykuh'},'online','0');;readingsEndUpdate($defs{'tuya_local_bf0572e0fb6ccbe356ykuh'},1);;
2023-01-31 20:37:32,534 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'tuya_local_bf68d9b41c16be3713vcc1'});;readingsBulkUpdateIfChanged($defs{'tuya_local_bf68d9b41c16be3713vcc1'},'online','0');;readingsEndUpdate($defs{'tuya_local_bf68d9b41c16be3713vcc1'},1);;
2023-01-31 20:37:32,548 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'tuya_local_bf4f644bc7dd2fc71d9q52'});;readingsBulkUpdateIfChanged($defs{'tuya_local_bf4f644bc7dd2fc71d9q52'},'online','0');;readingsEndUpdate($defs{'tuya_local_bf4f644bc7dd2fc71d9q52'},1);;
2023-01-31 20:37:32,562 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'tuya_local_bf7bbcb9a4b03a2c97cqid'});;readingsBulkUpdateIfChanged($defs{'tuya_local_bf7bbcb9a4b03a2c97cqid'},'online','0');;readingsEndUpdate($defs{'tuya_local_bf7bbcb9a4b03a2c97cqid'},1);;
2023-01-31 20:37:32,576 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsSingleUpdate($defs{'tuya_system'},'state','ready',1)
2023-01-31 20:37:32,593 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'tuya_local_bffa550a829a269630vhcn'});;readingsBulkUpdateIfChanged($defs{'tuya_local_bffa550a829a269630vhcn'},'online','0');;readingsEndUpdate($defs{'tuya_local_bffa550a829a269630vhcn'},1);;
2023-01-31 20:37:32,606 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'tuya_local_bfb7810a3e397c5fa4u7ud'});;readingsBulkUpdateIfChanged($defs{'tuya_local_bfb7810a3e397c5fa4u7ud'},'online','0');;readingsEndUpdate($defs{'tuya_local_bfb7810a3e397c5fa4u7ud'},1);;
2023-01-31 20:37:32,621 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'tuya_local_bf881b7977c814af88jmrc'});;readingsBulkUpdateIfChanged($defs{'tuya_local_bf881b7977c814af88jmrc'},'online','0');;readingsEndUpdate($defs{'tuya_local_bf881b7977c814af88jmrc'},1);;
2023-01-31 20:37:32,634 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsSingleUpdate($defs{'Computer_Stefan_bf881b7977c814af88jmrc'},'state','ready',1)
2023-01-31 20:37:32,649 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsSingleUpdate($defs{'Fernseher_Schlafzimmer_bf4f644bc7dd2fc71d9q52'},'state','ready',1)
2023-01-31 20:37:32,667 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsSingleUpdate($defs{'Fernseher_Wohnzimmer_bf7bbcb9a4b03a2c97cqid'},'state','ready',1)
2023-01-31 20:37:33,374 - ERROR - fhempy.lib.fhem: FHEM took 60740ms for readingsSingleUpdate($defs{'Computer_Stefan_bf881b7977c814af88jmrc'},'state','ready',1)
2023-01-31 20:37:33,375 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 360, in listener
fut.set_result(rmsg)
asyncio.exceptions.InvalidStateError: invalid state
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 211, in _onMessage
await self.handle_message(msg, hash)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 221, in handle_message
listener["func"](msg)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 362, in listener
logger.error("Failed to set result, received: " + rmsg)
TypeError: can only concatenate str (not "dict") to str
2023-01-31 20:37:33,380 - ERROR - fhempy.lib.fhem_pythonbinding: fhempy failed to handle message with hash: {'awaitId': 89332287, 'error': 0, 'result': 'ready'}
2023-01-31 20:37:33,381 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message: b'{"awaitId":89332287,"error":0,"result":"ready"}'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 360, in listener
fut.set_result(rmsg)
asyncio.exceptions.InvalidStateError: invalid state
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 211, in _onMessage
await self.handle_message(msg, hash)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 221, in handle_message
listener["func"](msg)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 362, in listener
logger.error("Failed to set result, received: " + rmsg)
TypeError: can only concatenate str (not "dict") to str
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 180, in onMessage
await self._onMessage(payload)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 214, in _onMessage
await self.sendBackError(hash, "fhempy failed to handle message")
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 132, in sendBackError
duration = (time.time() - id_received_timestamp[retHash["id"]]) * 1000
KeyError: 'id'
2023-01-31 20:37:33,418 - ERROR - fhempy.lib.fhem: FHEM took 60798ms for readingsBeginUpdate($defs{'tuya_local_bf881b7977c814af88jmrc'});;readingsBulkUpdateIfChanged($defs{'tuya_local_bf881b7977c814af88jmrc'},'online','0');;readingsEndUpdate($defs{'tuya_local_bf881b7977c814af88jmrc'},1);;
2023-01-31 20:37:33,418 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 360, in listener
fut.set_result(rmsg)
asyncio.exceptions.InvalidStateError: invalid state
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 211, in _onMessage
await self.handle_message(msg, hash)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 221, in handle_message
listener["func"](msg)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 362, in listener
logger.error("Failed to set result, received: " + rmsg)
TypeError: can only concatenate str (not "dict") to str
2023-01-31 20:37:33,420 - ERROR - fhempy.lib.fhem_pythonbinding: fhempy failed to handle message with hash: {'error': 0, 'awaitId': 87965765, 'result': None}
2023-01-31 20:37:33,421 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message: b'{"error":0,"awaitId":87965765,"result":null}'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 360, in listener
fut.set_result(rmsg)
asyncio.exceptions.InvalidStateError: invalid state
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 211, in _onMessage
await self.handle_message(msg, hash)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 221, in handle_message
listener["func"](msg)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 362, in listener
logger.error("Failed to set result, received: " + rmsg)
TypeError: can only concatenate str (not "dict") to str
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 180, in onMessage
await self._onMessage(payload)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 214, in _onMessage
await self.sendBackError(hash, "fhempy failed to handle message")
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 132, in sendBackError
duration = (time.time() - id_received_timestamp[retHash["id"]]) * 1000
KeyError: 'id'
2023-01-31 20:37:33,473 - ERROR - fhempy.lib.fhem: FHEM took 60869ms for readingsBeginUpdate($defs{'tuya_local_bfb7810a3e397c5fa4u7ud'});;readingsBulkUpdateIfChanged($defs{'tuya_local_bfb7810a3e397c5fa4u7ud'},'online','0');;readingsEndUpdate($defs{'tuya_local_bfb7810a3e397c5fa4u7ud'},1);;
2023-01-31 20:37:33,474 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 360, in listener
fut.set_result(rmsg)
asyncio.exceptions.InvalidStateError: invalid state
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 211, in _onMessage
await self.handle_message(msg, hash)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 221, in handle_message
listener["func"](msg)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 362, in listener
logger.error("Failed to set result, received: " + rmsg)
TypeError: can only concatenate str (not "dict") to str
2023-01-31 20:37:33,476 - ERROR - fhempy.lib.fhem_pythonbinding: fhempy failed to handle message with hash: {'error': 0, 'awaitId': 18804558, 'result': None}
2023-01-31 20:37:33,477 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message: b'{"error":0,"awaitId":18804558,"result":null}'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 360, in listener
fut.set_result(rmsg)
asyncio.exceptions.InvalidStateError: invalid state
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 211, in _onMessage
await self.handle_message(msg, hash)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 221, in handle_message
listener["func"](msg)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 362, in listener
logger.error("Failed to set result, received: " + rmsg)
TypeError: can only concatenate str (not "dict") to str
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 180, in onMessage
await self._onMessage(payload)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 214, in _onMessage
await self.sendBackError(hash, "fhempy failed to handle message")
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 132, in sendBackError
duration = (time.time() - id_received_timestamp[retHash["id"]]) * 1000
KeyError: 'id'
2023-01-31 20:37:33,520 - ERROR - fhempy.lib.fhem: FHEM took 60929ms for readingsBeginUpdate($defs{'tuya_local_bffa550a829a269630vhcn'});;readingsBulkUpdateIfChanged($defs{'tuya_local_bffa550a829a269630vhcn'},'online','0');;readingsEndUpdate($defs{'tuya_local_bffa550a829a269630vhcn'},1);;
2023-01-31 20:37:33,520 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 360, in listener
fut.set_result(rmsg)
asyncio.exceptions.InvalidStateError: invalid state
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 211, in _onMessage
await self.handle_message(msg, hash)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 221, in handle_message
listener["func"](msg)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 362, in listener
logger.error("Failed to set result, received: " + rmsg)
TypeError: can only concatenate str (not "dict") to str
2023-01-31 20:37:33,522 - ERROR - fhempy.lib.fhem_pythonbinding: fhempy failed to handle message with hash: {'result': None, 'awaitId': 86032985, 'error': 0}
2023-01-31 20:37:33,523 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message: b'{"result":null,"awaitId":86032985,"error":0}'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 360, in listener
fut.set_result(rmsg)
asyncio.exceptions.InvalidStateError: invalid state
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 211, in _onMessage
await self.handle_message(msg, hash)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 221, in handle_message
listener["func"](msg)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 362, in listener
logger.error("Failed to set result, received: " + rmsg)
TypeError: can only concatenate str (not "dict") to str
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 180, in onMessage
await self._onMessage(payload)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 214, in _onMessage
await self.sendBackError(hash, "fhempy failed to handle message")
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 132, in sendBackError
duration = (time.time() - id_received_timestamp[retHash["id"]]) * 1000
KeyError: 'id'
2023-01-31 20:37:33,571 - ERROR - fhempy.lib.fhem: FHEM took 60995ms for readingsSingleUpdate($defs{'tuya_system'},'state','ready',1)
2023-01-31 20:37:33,572 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 360, in listener
fut.set_result(rmsg)
asyncio.exceptions.InvalidStateError: invalid state
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 211, in _onMessage
await self.handle_message(msg, hash)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 221, in handle_message
listener["func"](msg)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 362, in listener
logger.error("Failed to set result, received: " + rmsg)
TypeError: can only concatenate str (not "dict") to str
2023-01-31 20:37:33,574 - ERROR - fhempy.lib.fhem_pythonbinding: fhempy failed to handle message with hash: {'awaitId': 82188327, 'error': 0, 'result': 'ready'}
2023-01-31 20:37:33,575 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message: b'{"awaitId":82188327,"error":0,"result":"ready"}'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 360, in listener
fut.set_result(rmsg)
asyncio.exceptions.InvalidStateError: invalid state
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 211, in _onMessage
await self.handle_message(msg, hash)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 221, in handle_message
listener["func"](msg)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 362, in listener
logger.error("Failed to set result, received: " + rmsg)
TypeError: can only concatenate str (not "dict") to str
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 180, in onMessage
await self._onMessage(payload)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 214, in _onMessage
await self.sendBackError(hash, "fhempy failed to handle message")
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 132, in sendBackError
duration = (time.time() - id_received_timestamp[retHash["id"]]) * 1000
KeyError: 'id'
2023-01-31 20:37:33,748 - ERROR - fhempy.lib.fhem: FHEM took 61188ms for readingsBeginUpdate($defs{'tuya_local_bf7bbcb9a4b03a2c97cqid'});;readingsBulkUpdateIfChanged($defs{'tuya_local_bf7bbcb9a4b03a2c97cqid'},'online','0');;readingsEndUpdate($defs{'tuya_local_bf7bbcb9a4b03a2c97cqid'},1);;
2023-01-31 20:37:33,749 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 360, in listener
fut.set_result(rmsg)
asyncio.exceptions.InvalidStateError: invalid state
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 211, in _onMessage
await self.handle_message(msg, hash)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 221, in handle_message
listener["func"](msg)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 362, in listener
logger.error("Failed to set result, received: " + rmsg)
TypeError: can only concatenate str (not "dict") to str
2023-01-31 20:37:33,751 - ERROR - fhempy.lib.fhem_pythonbinding: fhempy failed to handle message with hash: {'error': 0, 'awaitId': 78782641, 'result': None}
2023-01-31 20:37:33,751 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message: b'{"error":0,"awaitId":78782641,"result":null}'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 360, in listener
fut.set_result(rmsg)
asyncio.exceptions.InvalidStateError: invalid state
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 211, in _onMessage
await self.handle_message(msg, hash)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 221, in handle_message
listener["func"](msg)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 362, in listener
logger.error("Failed to set result, received: " + rmsg)
TypeError: can only concatenate str (not "dict") to str
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 180, in onMessage
await self._onMessage(payload)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 214, in _onMessage
await self.sendBackError(hash, "fhempy failed to handle message")
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 132, in sendBackError
duration = (time.time() - id_received_timestamp[retHash["id"]]) * 1000
KeyError: 'id'
2023-01-31 20:37:34,057 - ERROR - fhempy.lib.fhem: FHEM took 61510ms for readingsBeginUpdate($defs{'tuya_local_bf4f644bc7dd2fc71d9q52'});;readingsBulkUpdateIfChanged($defs{'tuya_local_bf4f644bc7dd2fc71d9q52'},'online','0');;readingsEndUpdate($defs{'tuya_local_bf4f644bc7dd2fc71d9q52'},1);;
2023-01-31 20:37:34,058 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 360, in listener
fut.set_result(rmsg)
asyncio.exceptions.InvalidStateError: invalid state
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 211, in _onMessage
await self.handle_message(msg, hash)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 221, in handle_message
listener["func"](msg)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 362, in listener
logger.error("Failed to set result, received: " + rmsg)
TypeError: can only concatenate str (not "dict") to str
2023-01-31 20:37:34,059 - ERROR - fhempy.lib.fhem_pythonbinding: fhempy failed to handle message with hash: {'awaitId': 14743269, 'error': 0, 'result': None}
2023-01-31 20:37:34,059 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message: b'{"awaitId":14743269,"error":0,"result":null}'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 360, in listener
fut.set_result(rmsg)
asyncio.exceptions.InvalidStateError: invalid state
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 211, in _onMessage
await self.handle_message(msg, hash)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 221, in handle_message
listener["func"](msg)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 362, in listener
logger.error("Failed to set result, received: " + rmsg)
TypeError: can only concatenate str (not "dict") to str
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 180, in onMessage
await self._onMessage(payload)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 214, in _onMessage
await self.sendBackError(hash, "fhempy failed to handle message")
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 132, in sendBackError
duration = (time.time() - id_received_timestamp[retHash["id"]]) * 1000
KeyError: 'id'
2023-01-31 20:37:34,138 - ERROR - fhempy.lib.fhem: FHEM took 61606ms for readingsBeginUpdate($defs{'tuya_local_bf68d9b41c16be3713vcc1'});;readingsBulkUpdateIfChanged($defs{'tuya_local_bf68d9b41c16be3713vcc1'},'online','0');;readingsEndUpdate($defs{'tuya_local_bf68d9b41c16be3713vcc1'},1);;
2023-01-31 20:37:34,138 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 360, in listener
fut.set_result(rmsg)
asyncio.exceptions.InvalidStateError: invalid state
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 211, in _onMessage
await self.handle_message(msg, hash)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 221, in handle_message
listener["func"](msg)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 362, in listener
logger.error("Failed to set result, received: " + rmsg)
TypeError: can only concatenate str (not "dict") to str
2023-01-31 20:37:34,140 - ERROR - fhempy.lib.fhem_pythonbinding: fhempy failed to handle message with hash: {'awaitId': 81706277, 'error': 0, 'result': None}
2023-01-31 20:37:34,140 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message: b'{"awaitId":81706277,"error":0,"result":null}'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 360, in listener
fut.set_result(rmsg)
asyncio.exceptions.InvalidStateError: invalid state
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 211, in _onMessage
await self.handle_message(msg, hash)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 221, in handle_message
listener["func"](msg)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 362, in listener
logger.error("Failed to set result, received: " + rmsg)
TypeError: can only concatenate str (not "dict") to str
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 180, in onMessage
await self._onMessage(payload)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 214, in _onMessage
await self.sendBackError(hash, "fhempy failed to handle message")
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 132, in sendBackError
duration = (time.time() - id_received_timestamp[retHash["id"]]) * 1000
KeyError: 'id'
2023-01-31 20:37:34,193 - ERROR - fhempy.lib.fhem: FHEM took 61676ms for readingsBeginUpdate($defs{'tuya_local_bf0572e0fb6ccbe356ykuh'});;readingsBulkUpdateIfChanged($defs{'tuya_local_bf0572e0fb6ccbe356ykuh'},'online','0');;readingsEndUpdate($defs{'tuya_local_bf0572e0fb6ccbe356ykuh'},1);;
2023-01-31 20:37:34,194 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 360, in listener
fut.set_result(rmsg)
asyncio.exceptions.InvalidStateError: invalid state
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 211, in _onMessage
await self.handle_message(msg, hash)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 221, in handle_message
listener["func"](msg)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 362, in listener
logger.error("Failed to set result, received: " + rmsg)
TypeError: can only concatenate str (not "dict") to str
2023-01-31 20:37:34,195 - ERROR - fhempy.lib.fhem_pythonbinding: fhempy failed to handle message with hash: {'awaitId': 12266838, 'error': 0, 'result': None}
2023-01-31 20:37:34,196 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message: b'{"awaitId":12266838,"error":0,"result":null}'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 360, in listener
fut.set_result(rmsg)
asyncio.exceptions.InvalidStateError: invalid state
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 211, in _onMessage
await self.handle_message(msg, hash)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 221, in handle_message
listener["func"](msg)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 362, in listener
logger.error("Failed to set result, received: " + rmsg)
TypeError: can only concatenate str (not "dict") to str
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 180, in onMessage
await self._onMessage(payload)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 214, in _onMessage
await self.sendBackError(hash, "fhempy failed to handle message")
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 132, in sendBackError
duration = (time.time() - id_received_timestamp[retHash["id"]]) * 1000
KeyError: 'id'
2023-01-31 20:37:36,655 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsSingleUpdate($defs{'tuya_cloud_connector'},'state','connected',1)
2023-01-31 20:37:37,360 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'tuya_cloud_bffa550a829a269630vhcn'});;
2023-01-31 20:37:37,445 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'Sybille_Tablet_bf68d9b41c16be3713vcc1'});;
2023-01-31 20:37:37,774 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'Stefan_Tablet_bf0572e0fb6ccbe356ykuh'});;
2023-01-31 20:44:45,374 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'Stefan_Tablet_bf0572e0fb6ccbe356ykuh'},'relay_status','last');;
Und das im fhem.log:
2023.01.31 20:37:37 1: readingsUpdate(tuya_cloud_bffa550a829a269630vhcn,active_time,1674825254) missed to call readingsBeginUpdate first.
2023.01.31 20:37:37 1: stacktrace:
2023.01.31 20:37:37 1: main::readingsBulkUpdate called by (eval 1748) (1)
2023.01.31 20:37:37 1: (eval) called by ./FHEM/10_BindingsIo.pm (570)
2023.01.31 20:37:37 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (682)
2023.01.31 20:37:37 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.01.31 20:37:37 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 20:37:37 1: main::CallFn called by fhem.pl (784)
2023.01.31 20:37:37 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,active_time,1638468323) missed to call readingsBeginUpdate first.
2023.01.31 20:37:37 1: stacktrace:
2023.01.31 20:37:37 1: main::readingsBulkUpdate called by (eval 1749) (1)
2023.01.31 20:37:37 1: (eval) called by ./FHEM/10_BindingsIo.pm (570)
2023.01.31 20:37:37 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (682)
2023.01.31 20:37:37 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.01.31 20:37:37 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 20:37:37 1: main::CallFn called by fhem.pl (784)
2023.01.31 20:37:37 1: readingsUpdate(tuya_cloud_bffa550a829a269630vhcn,biz_type,0) missed to call readingsBeginUpdate first.
2023.01.31 20:37:37 1: stacktrace:
2023.01.31 20:37:37 1: main::readingsBulkUpdate called by (eval 1819) (1)
2023.01.31 20:37:37 1: (eval) called by ./FHEM/10_BindingsIo.pm (570)
2023.01.31 20:37:37 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (682)
2023.01.31 20:37:37 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.01.31 20:37:37 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 20:37:37 1: main::CallFn called by fhem.pl (784)
2023.01.31 20:37:37 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,biz_type,0) missed to call readingsBeginUpdate first.
2023.01.31 20:37:37 1: stacktrace:
2023.01.31 20:37:37 1: main::readingsBulkUpdate called by (eval 1820) (1)
2023.01.31 20:37:37 1: (eval) called by ./FHEM/10_BindingsIo.pm (570)
2023.01.31 20:37:37 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (682)
2023.01.31 20:37:37 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.01.31 20:37:37 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 20:37:37 1: main::CallFn called by fhem.pl (784)
2023.01.31 20:37:37 1: readingsUpdate(Stefan_Tablet_bf0572e0fb6ccbe356ykuh,active_time,1638460188) missed to call readingsBeginUpdate first.
2023.01.31 20:37:37 1: stacktrace:
2023.01.31 20:37:37 1: main::readingsBulkUpdate called by (eval 1821) (1)
2023.01.31 20:37:37 1: (eval) called by ./FHEM/10_BindingsIo.pm (570)
2023.01.31 20:37:37 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (682)
2023.01.31 20:37:37 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.01.31 20:37:37 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 20:37:37 1: main::CallFn called by fhem.pl (784)
2023.01.31 20:37:38 1: readingsUpdate(tuya_cloud_bffa550a829a269630vhcn,category,wsdcg) missed to call readingsBeginUpdate first.
2023.01.31 20:37:38 1: stacktrace:
2023.01.31 20:37:38 1: main::readingsBulkUpdate called by (eval 1852) (1)
2023.01.31 20:37:38 1: (eval) called by ./FHEM/10_BindingsIo.pm (570)
2023.01.31 20:37:38 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (682)
2023.01.31 20:37:38 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.01.31 20:37:38 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 20:37:38 1: main::CallFn called by fhem.pl (784)
2023.01.31 20:37:38 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,category,cz) missed to call readingsBeginUpdate first.
2023.01.31 20:37:38 1: stacktrace:
2023.01.31 20:37:38 1: main::readingsBulkUpdate called by (eval 1853) (1)
2023.01.31 20:37:38 1: (eval) called by ./FHEM/10_BindingsIo.pm (570)
2023.01.31 20:37:38 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (682)
2023.01.31 20:37:38 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.01.31 20:37:38 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 20:37:38 1: main::CallFn called by fhem.pl (784)
2023.01.31 20:37:38 1: readingsUpdate(Stefan_Tablet_bf0572e0fb6ccbe356ykuh,biz_type,0) missed to call readingsBeginUpdate first.
2023.01.31 20:37:38 1: stacktrace:
2023.01.31 20:37:38 1: main::readingsBulkUpdate called by (eval 1854) (1)
2023.01.31 20:37:38 1: (eval) called by ./FHEM/10_BindingsIo.pm (570)
2023.01.31 20:37:38 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (682)
2023.01.31 20:37:38 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.01.31 20:37:38 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 20:37:38 1: main::CallFn called by fhem.pl (784)
2023.01.31 20:37:38 1: readingsUpdate(tuya_cloud_bffa550a829a269630vhcn,create_time,1674825254) missed to call readingsBeginUpdate first.
2023.01.31 20:37:38 1: stacktrace:
2023.01.31 20:37:38 1: main::readingsBulkUpdate called by (eval 1934) (1)
2023.01.31 20:37:38 1: (eval) called by ./FHEM/10_BindingsIo.pm (570)
2023.01.31 20:37:38 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (682)
2023.01.31 20:37:38 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.01.31 20:37:38 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 20:37:38 1: main::CallFn called by fhem.pl (784)
2023.01.31 20:37:38 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,create_time,1638468323) missed to call readingsBeginUpdate first.
2023.01.31 20:37:38 1: stacktrace:
2023.01.31 20:37:38 1: main::readingsBulkUpdate called by (eval 1935) (1)
2023.01.31 20:37:38 1: (eval) called by ./FHEM/10_BindingsIo.pm (570)
2023.01.31 20:37:38 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (682)
2023.01.31 20:37:38 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.01.31 20:37:38 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 20:37:38 1: main::CallFn called by fhem.pl (784)
2023.01.31 20:37:38 1: readingsUpdate(Stefan_Tablet_bf0572e0fb6ccbe356ykuh,category,cz) missed to call readingsBeginUpdate first.
2023.01.31 20:37:38 1: stacktrace:
2023.01.31 20:37:38 1: main::readingsBulkUpdate called by (eval 1936) (1)
2023.01.31 20:37:38 1: (eval) called by ./FHEM/10_BindingsIo.pm (570)
2023.01.31 20:37:38 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (682)
2023.01.31 20:37:38 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.01.31 20:37:38 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 20:37:38 1: main::CallFn called by fhem.pl (784)
2023.01.31 20:37:39 1: readingsUpdate(tuya_cloud_bffa550a829a269630vhcn,icon,https://images.tuyaeu.com/smart/icon/ay1525749833414yotNt/b3a94a9431b68373894805b4a19092e4.png) missed to call readingsBeginUpdate first.
2023.01.31 20:37:39 1: stacktrace:
2023.01.31 20:37:39 1: main::readingsBulkUpdate called by (eval 1954) (1)
2023.01.31 20:37:39 1: (eval) called by ./FHEM/10_BindingsIo.pm (570)
2023.01.31 20:37:39 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (682)
2023.01.31 20:37:39 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.01.31 20:37:39 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 20:37:39 1: main::CallFn called by fhem.pl (784)
2023.01.31 20:37:39 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,icon,https://images.tuyaeu.com/smart/icon/ay15148582002916nitB/c58a91c23c2e2b5309c7c5d776871390.png) missed to call readingsBeginUpdate first.
2023.01.31 20:37:39 1: stacktrace:
2023.01.31 20:37:39 1: main::readingsBulkUpdate called by (eval 1955) (1)
2023.01.31 20:37:39 1: (eval) called by ./FHEM/10_BindingsIo.pm (570)
2023.01.31 20:37:39 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (682)
2023.01.31 20:37:39 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.01.31 20:37:39 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 20:37:39 1: main::CallFn called by fhem.pl (784)
2023.01.31 20:37:39 1: readingsUpdate(Stefan_Tablet_bf0572e0fb6ccbe356ykuh,create_time,1638459915) missed to call readingsBeginUpdate first.
2023.01.31 20:37:39 1: stacktrace:
2023.01.31 20:37:39 1: main::readingsBulkUpdate called by (eval 1956) (1)
2023.01.31 20:37:39 1: (eval) called by ./FHEM/10_BindingsIo.pm (570)
2023.01.31 20:37:39 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (682)
2023.01.31 20:37:39 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.01.31 20:37:39 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 20:37:39 1: main::CallFn called by fhem.pl (784)
2023.01.31 20:37:39 1: readingsUpdate(tuya_cloud_bffa550a829a269630vhcn,id,bffa550a829a269630vhcn) missed to call readingsBeginUpdate first.
2023.01.31 20:37:39 1: stacktrace:
2023.01.31 20:37:39 1: main::readingsBulkUpdate called by (eval 1967) (1)
2023.01.31 20:37:39 1: (eval) called by ./FHEM/10_BindingsIo.pm (570)
2023.01.31 20:37:39 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (682)
2023.01.31 20:37:39 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.01.31 20:37:39 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 20:37:39 1: main::CallFn called by fhem.pl (784)
2023.01.31 20:37:39 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,id,bf68d9b41c16be3713vcc1) missed to call readingsBeginUpdate first.
2023.01.31 20:37:39 1: stacktrace:
2023.01.31 20:37:39 1: main::readingsBulkUpdate called by (eval 1968) (1)
2023.01.31 20:37:39 1: (eval) called by ./FHEM/10_BindingsIo.pm (570)
2023.01.31 20:37:39 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (682)
2023.01.31 20:37:39 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.01.31 20:37:39 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 20:37:39 1: main::CallFn called by fhem.pl (784)
2023.01.31 20:37:39 1: readingsUpdate(Stefan_Tablet_bf0572e0fb6ccbe356ykuh,icon,https://images.tuyaeu.com/smart/icon/ay15422864509092y6k8/94efe8972e318399f1a1ee3887c704e8.png) missed to call readingsBeginUpdate first.
2023.01.31 20:37:39 1: stacktrace:
2023.01.31 20:37:39 1: main::readingsBulkUpdate called by (eval 1969) (1)
2023.01.31 20:37:39 1: (eval) called by ./FHEM/10_BindingsIo.pm (570)
2023.01.31 20:37:39 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (682)
2023.01.31 20:37:39 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.01.31 20:37:39 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 20:37:39 1: main::CallFn called by fhem.pl (784)
2023.01.31 20:37:39 1: readingsUpdate(tuya_cloud_bffa550a829a269630vhcn,ip,84.188.243.243) missed to call readingsBeginUpdate first.
2023.01.31 20:37:39 1: stacktrace:
2023.01.31 20:37:39 1: main::readingsBulkUpdate called by (eval 1981) (1)
2023.01.31 20:37:39 1: (eval) called by ./FHEM/10_BindingsIo.pm (570)
2023.01.31 20:37:39 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (682)
2023.01.31 20:37:39 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.01.31 20:37:39 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 20:37:39 1: main::CallFn called by fhem.pl (784)
2023.01.31 20:37:39 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,ip,87.158.205.193) missed to call readingsBeginUpdate first.
2023.01.31 20:37:39 1: stacktrace:
2023.01.31 20:37:39 1: main::readingsBulkUpdate called by (eval 1982) (1)
2023.01.31 20:37:39 1: (eval) called by ./FHEM/10_BindingsIo.pm (570)
2023.01.31 20:37:39 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (682)
2023.01.31 20:37:39 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.01.31 20:37:39 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 20:37:39 1: main::CallFn called by fhem.pl (784)
2023.01.31 20:37:39 1: readingsUpdate(Stefan_Tablet_bf0572e0fb6ccbe356ykuh,id,bf0572e0fb6ccbe356ykuh) missed to call readingsBeginUpdate first.
2023.01.31 20:37:39 1: stacktrace:
2023.01.31 20:37:39 1: main::readingsBulkUpdate called by (eval 1983) (1)
2023.01.31 20:37:39 1: (eval) called by ./FHEM/10_BindingsIo.pm (570)
2023.01.31 20:37:39 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (682)
2023.01.31 20:37:39 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.01.31 20:37:39 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 20:37:39 1: main::CallFn called by fhem.pl (784)
2023.01.31 20:37:39 1: readingsUpdate(tuya_cloud_bffa550a829a269630vhcn,lat,49.6104) missed to call readingsBeginUpdate first.
2023.01.31 20:37:39 1: stacktrace:
2023.01.31 20:37:39 1: main::readingsBulkUpdate called by (eval 2021) (1)
2023.01.31 20:37:39 1: (eval) called by ./FHEM/10_BindingsIo.pm (570)
2023.01.31 20:37:39 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (682)
2023.01.31 20:37:39 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.01.31 20:37:39 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 20:37:39 1: main::CallFn called by fhem.pl (784)
2023.01.31 20:37:39 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,lat,49.6104) missed to call readingsBeginUpdate first.
2023.01.31 20:37:39 1: stacktrace:
2023.01.31 20:37:39 1: main::readingsBulkUpdate called by (eval 2022) (1)
2023.01.31 20:37:39 1: (eval) called by ./FHEM/10_BindingsIo.pm (570)
2023.01.31 20:37:39 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (682)
2023.01.31 20:37:39 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.01.31 20:37:39 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 20:37:39 1: main::CallFn called by fhem.pl (784)
2023.01.31 20:37:39 1: readingsUpdate(Stefan_Tablet_bf0572e0fb6ccbe356ykuh,ip,87.158.205.193) missed to call readingsBeginUpdate first.
2023.01.31 20:37:39 1: stacktrace:
2023.01.31 20:37:39 1: main::readingsBulkUpdate called by (eval 2023) (1)
2023.01.31 20:37:39 1: (eval) called by ./FHEM/10_BindingsIo.pm (570)
2023.01.31 20:37:39 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (682)
2023.01.31 20:37:39 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.01.31 20:37:39 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 20:37:39 1: main::CallFn called by fhem.pl (784)
2023.01.31 20:37:40 1: readingsUpdate(tuya_cloud_bffa550a829a269630vhcn,local_key,55db39dd00af9487) missed to call readingsBeginUpdate first.
2023.01.31 20:37:40 1: stacktrace:
2023.01.31 20:37:40 1: main::readingsBulkUpdate called by (eval 2061) (1)
2023.01.31 20:37:40 1: (eval) called by ./FHEM/10_BindingsIo.pm (570)
2023.01.31 20:37:40 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (682)
2023.01.31 20:37:40 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.01.31 20:37:40 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.01.31 20:37:40 1: main::CallFn called by fhem.pl (784)
2023.01.31 20:37:40 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,local_key,68c71bfc9491dabc) missed to call readingsBeginUpdate first.
Hab ich etwas falsch gemacht?
Gruß und Danke,
Stefan
Wie viele tuya Devices hast du in fhempy drin? Egal ob tuya oder tuya_cloud.
Ich glaube nicht dass ich es hier übertreibe ;)
Ich habe 6 Steckdosen und neu so einen sporadisch sendenden Temperatur und Luftfeuchte Sensor.
Die Geräte habe ich zur Zeit als Cloud und als Local drin.
Zitat von: dominik am 31 Januar 2023, 20:03:02
1. Doppelten löschen
2. set fhempy_local update
3. update
4. shutdown restart
beim update bekomme ich permission denied
sudo chown fhem:dialout 10_BindingsIo.pm geht nicht
Zitat von: stefanru am 31 Januar 2023, 21:02:03
Ich glaube nicht dass ich es hier übertreibe ;)
Ich habe 6 Steckdosen und neu so einen sporadisch sendenden Temperatur und Luftfeuchte Sensor.
Die Geräte habe ich zur Zeit als Cloud und als Local drin.
Das gibt es ja nicht. Ich habe ca. 20 Devices drin. Dein BindingsIo ist auch sicher aktuell?
Zitat von: thburkhart am 31 Januar 2023, 21:03:15
beim update bekomme ich permission denied
sudo chown fhem:dialout 10_BindingsIo.pm geht nicht
Dann löschen und ein FHEM Update machen.
Zitat von: dominik am 31 Januar 2023, 21:11:40
Dann löschen und ein FHEM Update machen.
schon versucht
geht auch nicht
permission denied
Zitat von: stefanru am 31 Januar 2023, 21:02:03
Ich glaube nicht dass ich es hier übertreibe ;)
Ich habe 6 Steckdosen und neu so einen sporadisch sendenden Temperatur und Luftfeuchte Sensor.
Die Geräte habe ich zur Zeit als Cloud und als Local drin.
Kann es sein, dass dein FHEM generell manchmal blockiert/hängt?
Zitat von: thburkhart am 31 Januar 2023, 21:17:05
schon versucht
geht auch nicht
permission denied
sudo rm? Mit root geht alles löschen.
löschen ging
aber beim update 2023.01.31 21:00:18 1:
2023.01.31 21:00:18 1: Downloading https://raw.githubusercontent.com/dominikkarall/fhempy/master/controls_pythonbinding.txt
2023.01.31 21:00:18 1: pythonbinding
2023.01.31 21:00:18 1: UPD FHEM/10_BindingsIo.pm
2023.01.31 21:00:18 1: UPD FHEM/10_fhempy.pm
2023.01.31 21:00:19 1: UPD FHEM/10_fhempyServer.pm
2023.01.31 21:00:19 1: open ./FHEM/10_fhempyServer.pm failed: Permission denied, trying to restore the previous version and aborting the update
2023.01.31 21:00:19 1:
2023.01.31 21:00:19 1: Downloading https://raw.githubusercontent.com/PatricSperling/FHEM_SST/master/controls_SST.txt
2023.01.31 21:00:19 1: SST
ok
dann lösche ich fhempy_server auch
Hmmm, seltsam.
Nein mein FHEM läuft eigentlich gut.
Und ich hatte ja auch ein Apptime gesendet.
Das einzige was lang lief war tuya.
Aber ich habe jetzt nochmal genau geschaut und scheinbar war mein Bindings nicht aktualisiert.
Habe nochmal update gemacht und diesmal kam:
2023.01.31 21:51:38 1: Downloading https://raw.githubusercontent.com/dominikkarall/fhempy/master/controls_pythonbinding.txt
2023.01.31 21:51:38 1: pythonbinding
2023.01.31 21:51:39 1: UPD FHEM/10_BindingsIo.pm
2023.01.31 21:51:39 1: UPD FHEM/10_fhempy.pm
2023.01.31 21:51:39 1: saving fhem.cfg
2023.01.31 21:51:39 1: saving ./log/fhem.save
2023.01.31 21:51:40 1: BindingsIo (local_pybinding): ==> FHEMPY UPDATE STARTED...CHECK FHEMPY STATE FOR STATUS <==
Nach dem Update und reapear von local_pybinding habe ich FHEM durchgestartet.
Danach sind die Versionen wie folgt:
Server:
Internals:
DEF 0
FD 35
FUUID 61a76073-f33f-0c45-3670-bd692e31096ebf98
LAST_START 2023-01-31 21:57:03
NAME fhempyserver_15733
NR 2013
NTFY_ORDER 50-fhempyserver_15733
PID 2902
STARTS 1
STATE ???
TYPE fhempyServer
currentlogfile ./log/fhempy-2023-01-31.log
eventCount 2
logfile ./log/fhempy-%Y-%m-%d.log
CoProcess:
cmdFn fhempyServer_getCmd
name fhempy
state running FHEM/bindings/python/bin/fhempy
READINGS:
2023-01-31 21:57:03 fhempy running FHEM/bindings/python/bin/fhempy
2023-01-31 21:57:03 python v3.9.2
Attributes:
devStateIcon { my $status_img = "10px-kreis-gruen";; my $status_txt = "running";; if (substr(ReadingsVal($name, "fhempy", "running"),0,7) ne "running") { $status_img = "10px-kreis-rot";; $status_txt = "stopped";; } "<div><a>".FW_makeImage($status_img, $status_txt)."</a><a href=\"/fhem?cmd.dummy=set $name restart&XHR=1\" title=\"Restart\">".FW_makeImage("audio_repeat")."</a></div>" }
group fhempy
icon python
logfile ./log/fhempy-%Y-%m-%d.log
nrarchive 10
room fhempy
local_pybinding
Internals:
BindingType fhempy
DEF fhempy
DeviceName ws:localhost:15733
FD 60
FUUID 61ebfd4f-f33f-0c45-6307-c6f25f4c826817c3
IP 127.0.0.1
NAME local_pybinding
NR 2079
NTFY_ORDER 50-local_pybinding
PARTIAL
PORT 15733
STATE opened
TYPE BindingsIo
WEBSOCKET 1
binary 1
connecttime 1675198633.01235
devioLoglevel 0
eventCount 3
installing 0
localBinding 1
nextOpenDelay 10
prev_error
READINGS:
2023-01-31 21:52:24 hostname raspberrypi
2023-01-31 21:52:24 os posix
2023-01-31 21:52:24 python 3.9.2
2023-01-31 21:52:24 release 5.15.84-v7+
2023-01-31 21:57:13 state opened
2023-01-31 21:52:24 system Linux
2023-01-31 21:52:24 version 0.1.585
2023-01-31 21:57:13 version_available 0.1.585
2023-01-31 21:57:13 version_release_notes <html><a href="https://github.com/fhempy/fhempy/releases" target="_blank">Release Notes</a></html>
args:
local_pybinding
BindingsIo
fhempy
Attributes:
devStateIcon { my $attr_ver = "1.1.0";; my $status_img = "10px-kreis-gruen";; my $status_txt = "connected";; my $ver = ReadingsVal($name, "version", "-");; my $ver_available = ReadingsVal($name, "version_available", $ver);; my $update_icon = "";; my $refresh_img = "refresh";; my $refresh_txt = "Update fhempy";; if ($ver_available ne $ver) { $refresh_img = "refresh\@orange";; $refresh_txt = "Version ".$ver_available." available for update";; } if (ReadingsVal($name, "state", "disconnected") eq "disconnected") { $status_img = "10px-kreis-rot";; $status_txt = "disconnected";; } $update_icon = "<a href=\"/fhem?cmd.dummy=set $name update&XHR=1\" title=\"Start ".$ver_available." update\">".FW_makeImage($refresh_img, $refresh_txt)."</a>";; my $restart_icon = "<a href=\"/fhem?cmd.dummy=set $name restart&XHR=1\" title=\"Restart fhempy\">".FW_makeImage("control_reboot")."</a>";; "<div><a>".FW_makeImage($status_img, $status_txt)."</a><a> ".$ver." </a>".$update_icon.$restart_icon."</div>" }
group fhempy
icon file_json-ld2
room fhempy
tuya_system (lokal)
Internals:
API_KEY XXX
API_SECRET XXX
DEF tuya setup XXX XXX
DEVICEID 0
FHEMPYTYPE tuya
FUUID 633eabdb-f33f-0c45-6cf9-6f79a14a1c27a922
IODev local_pybinding
NAME tuya_system
NR 2209
PYTHONTYPE tuya
REGION eu
STATE ready
TYPE fhempy
eventCount 1
READINGS:
2022-10-06 12:20:33 bf0572e0fb6ccbe356ykuh_icon https://images.tuyaeu.com/smart/icon/ay15422864509092y6k8/94efe8972e318399f1a1ee3887c704e8.png
2022-10-06 12:20:33 bf0572e0fb6ccbe356ykuh_id bf0572e0fb6ccbe356ykuh
2022-10-06 12:21:08 bf0572e0fb6ccbe356ykuh_ip 192.168.69.71
2022-10-06 12:20:33 bf0572e0fb6ccbe356ykuh_localkey b4ca4d3e6b518fd1
2022-10-06 12:20:33 bf0572e0fb6ccbe356ykuh_name Stefan Tablet
2022-10-06 12:20:33 bf0572e0fb6ccbe356ykuh_productid vxw1edwctjckt0zd
2022-10-06 12:21:08 bf0572e0fb6ccbe356ykuh_version 3.3
2022-10-06 12:20:33 bf4f644bc7dd2fc71d9q52_icon https://images.tuyaeu.com/smart/icon/ay15148582002916nitB/c58a91c23c2e2b5309c7c5d776871390.png
2022-10-06 12:20:33 bf4f644bc7dd2fc71d9q52_id bf4f644bc7dd2fc71d9q52
2022-10-06 12:21:08 bf4f644bc7dd2fc71d9q52_ip 192.168.69.76
2022-10-06 12:20:33 bf4f644bc7dd2fc71d9q52_localkey 8cf0099962d0ff3f
2022-10-06 12:20:33 bf4f644bc7dd2fc71d9q52_name Fernseher Schlafzimmer
2022-10-06 12:20:33 bf4f644bc7dd2fc71d9q52_productid apszn7k8yhgsin28
2022-10-06 12:21:08 bf4f644bc7dd2fc71d9q52_version 3.3
2022-10-06 12:20:33 bf68d9b41c16be3713vcc1_icon https://images.tuyaeu.com/smart/icon/ay15148582002916nitB/c58a91c23c2e2b5309c7c5d776871390.png
2022-10-06 12:20:33 bf68d9b41c16be3713vcc1_id bf68d9b41c16be3713vcc1
2022-10-06 12:21:08 bf68d9b41c16be3713vcc1_ip 192.168.69.78
2022-10-06 12:20:33 bf68d9b41c16be3713vcc1_localkey 68c71bfc9491dabc
2022-10-06 12:20:33 bf68d9b41c16be3713vcc1_name Sybille Tablet
2022-10-06 12:20:33 bf68d9b41c16be3713vcc1_productid apszn7k8yhgsin28
2022-10-06 12:21:09 bf68d9b41c16be3713vcc1_version 3.3
2022-10-06 12:20:31 bf7bbcb9a4b03a2c97cqid_icon https://images.tuyaeu.com/smart/icon/ay15148582002916nitB/c58a91c23c2e2b5309c7c5d776871390.png
2022-10-06 12:20:31 bf7bbcb9a4b03a2c97cqid_id bf7bbcb9a4b03a2c97cqid
2022-10-06 12:21:07 bf7bbcb9a4b03a2c97cqid_ip 192.168.69.77
2022-10-06 12:20:31 bf7bbcb9a4b03a2c97cqid_localkey ffb033dfca44e5e0
2022-10-06 12:20:31 bf7bbcb9a4b03a2c97cqid_name Fernseher Wohnzimmer
2022-10-06 12:20:31 bf7bbcb9a4b03a2c97cqid_productid apszn7k8yhgsin28
2022-10-06 12:21:08 bf7bbcb9a4b03a2c97cqid_version 3.3
2022-10-06 12:20:30 bf881b7977c814af88jmrc_icon https://images.tuyaeu.com/smart/icon/ay15148582002916nitB/c58a91c23c2e2b5309c7c5d776871390.png
2022-10-06 12:20:30 bf881b7977c814af88jmrc_id bf881b7977c814af88jmrc
2022-10-06 12:21:07 bf881b7977c814af88jmrc_ip 192.168.69.79
2022-10-06 12:20:30 bf881b7977c814af88jmrc_localkey d8256204db6848a7
2022-10-06 12:20:30 bf881b7977c814af88jmrc_name Computer
2022-10-06 12:20:30 bf881b7977c814af88jmrc_productid apszn7k8yhgsin28
2022-10-06 12:21:07 bf881b7977c814af88jmrc_version 3.3
2022-10-06 12:20:32 bfb7810a3e397c5fa4u7ud_icon https://images.tuyaeu.com/smart/icon/ay15422864509092y6k8/94efe8972e318399f1a1ee3887c704e8.png
2022-10-06 12:20:32 bfb7810a3e397c5fa4u7ud_id bfb7810a3e397c5fa4u7ud
2022-10-06 12:21:08 bfb7810a3e397c5fa4u7ud_ip 192.168.69.70
2022-10-06 12:20:32 bfb7810a3e397c5fa4u7ud_localkey 9f28f44af0417c83
2022-10-06 12:20:32 bfb7810a3e397c5fa4u7ud_name Fernseher
2022-10-06 12:20:32 bfb7810a3e397c5fa4u7ud_productid vxw1edwctjckt0zd
2022-10-06 12:21:08 bfb7810a3e397c5fa4u7ud_version 3.3
2023-01-27 14:47:53 bffa550a829a269630vhcn_icon https://images.tuyaeu.com/smart/icon/ay1525749833414yotNt/b3a94a9431b68373894805b4a19092e4.png
2023-01-27 14:47:53 bffa550a829a269630vhcn_id bffa550a829a269630vhcn
2023-01-27 15:37:37 bffa550a829a269630vhcn_ip 192.168.69.43
2023-01-27 14:47:53 bffa550a829a269630vhcn_localkey 55db39dd00af9487
2023-01-27 14:47:53 bffa550a829a269630vhcn_name T & H Sensor
2023-01-27 14:47:53 bffa550a829a269630vhcn_productid xlk3mtpjo1zkmdvh
2023-01-27 14:48:42 bffa550a829a269630vhcn_version 3.3
2023-01-31 21:57:24 state ready
args:
tuya_system
fhempy
tuya
setup
XXX
XXX
XXX
argsh:
Attributes:
group tuya
room fhempy
Leider immer noch das selbe in den Logs.
Kann die gerne nochmal senden.
Hier nochmal "Apptime" für das Verhalten meines FHEM Systems:
active-timers: 112; max-active timers: 121; max-timer-load: 11 min-tmrHandlingTm: 0.2ms; max-tmrHandlingTm: 1193.6ms; totAvgDly: 66.3ms
name function max count total average maxDly avgDly TS Max call param Max call
tmr-at_Exec HASH(0x79ffb18) 1193 2 1203.60 601.80 26.46 14.12 31.01. 22:07:01 HASH(haus.strom.at)
local_pybinding CODE(0x7e79a78) 983 700 29065.88 41.52 0.00 0.00 31.01. 22:06:23 HASH(local_pybinding)
WEB_192.168.69.94_41874 FW_Notify 593 1856 23939.53 12.90 0.00 0.00 31.01. 22:06:23 HASH(WEB_192.168.69.94_41874); HASH(tuya_local_bf4f644bc7dd2fc71d9q52)
tuya_local_bf4f644bc7dd2fc71d9q52 fhempy_Set 587 22 1265.23 57.51 0.00 0.00 31.01. 22:06:23 HASH(tuya_local_bf4f644bc7dd2fc71d9q52); ARRAY(0x88d2008); HASH(0x8a28aa0)
tuya_local_bf68d9b41c16be3713vcc1 fhempy_Set 508 50 4422.50 88.45 0.00 0.00 31.01. 22:08:13 HASH(tuya_local_bf68d9b41c16be3713vcc1); ARRAY(0x8a7b250); HASH(0x88c4f68)
WEB_192.168.69.69_42110 FW_Notify 484 1856 24898.78 13.42 0.00 0.00 31.01. 22:08:18 HASH(WEB_192.168.69.69_42110); HASH(tuya_local_bf68d9b41c16be3713vcc1)
Stefan_Tablet_bf0572e0fb6ccbe356ykuh fhempy_Set 405 68 4860.17 71.47 0.00 0.00 31.01. 22:06:23 HASH(Stefan_Tablet_bf0572e0fb6ccbe356ykuh); ARRAY(0x89ba680); HASH(0x8aa2be8)
tuya_local_bfb7810a3e397c5fa4u7ud fhempy_Set 372 54 4566.54 84.57 0.00 0.00 31.01. 22:06:57 HASH(tuya_local_bfb7810a3e397c5fa4u7ud); ARRAY(0x8cbd438); HASH(0x8036f88)
tuya_local_bf881b7977c814af88jmrc fhempy_Set 351 52 3643.89 70.07 0.00 0.00 31.01. 22:07:53 HASH(tuya_local_bf881b7977c814af88jmrc); ARRAY(0x87bfae8); HASH(0x8a69728)
tmr-WS3600_Read HASH(0x5315ff8) 341 1 341.45 341.45 1.26 1.26 31.01. 22:08:00 HASH(meineWetterstation)
tuya_local_bf7bbcb9a4b03a2c97cqid fhempy_Set 308 50 4266.99 85.34 0.00 0.00 31.01. 22:07:17 HASH(tuya_local_bf7bbcb9a4b03a2c97cqid); ARRAY(0x8a1f758); HASH(0x8d1e200)
Fernseher_Schlafzimmer_bf4f644bc7dd2fc71d9q52 fhempy_Set 268 44 2494.59 56.70 0.00 0.00 31.01. 22:07:53 HASH(Fernseher_Schlafzimmer_bf4f644bc7dd2fc71d9q52); ARRAY(0x8c11808); HASH(0x8ac2910)
fduino FHEMduino_Read 258 28 408.06 14.57 0.00 0.00 31.01. 22:07:34 HASH(fduino)
Fernseher_bfb7810a3e397c5fa4u7ud fhempy_Set 254 108 4093.26 37.90 0.00 0.00 31.01. 22:08:13 HASH(Fernseher_bfb7810a3e397c5fa4u7ud); ARRAY(0x8d6f1d0); HASH(0x8d21200)
Computer_Stefan_bf881b7977c814af88jmrc fhempy_Set 254 104 3878.54 37.29 0.00 0.00 31.01. 22:07:53 HASH(Computer_Stefan_bf881b7977c814af88jmrc); ARRAY(0x8cc15b8); HASH(0x8cb3578)
doTempAussen DOIF_Notify 239 6 358.24 59.71 0.00 0.00 31.01. 22:07:34 HASH(doTempAussen); HASH(WetterStefanAussen)
Sybille_Tablet_bf68d9b41c16be3713vcc1 fhempy_Set 204 100 3089.67 30.90 0.00 0.00 31.01. 22:07:53 HASH(Sybille_Tablet_bf68d9b41c16be3713vcc1); ARRAY(0x8a32130); HASH(0x8b71500)
Fernseher_Wohnzimmer_bf7bbcb9a4b03a2c97cqid fhempy_Set 166 100 3748.15 37.48 0.00 0.00 31.01. 22:07:13 HASH(Fernseher_Wohnzimmer_bf7bbcb9a4b03a2c97cqid); ARRAY(0x8ca8dd8); HASH(0x8adf538)
walter.stromzaehler OBIS_Read 138 180 8129.47 45.16 0.00 0.00 31.01. 22:07:31 HASH(walter.stromzaehler)
stefan.stromzaehler OBIS_Read 113 1027 7700.43 7.50 0.00 0.00 31.01. 22:07:49 HASH(stefan.stromzaehler)
Home HOMEMODE_Notify 86 21 157.99 7.52 0.00 0.00 31.01. 22:08:00 HASH(Home); HASH(meineWetterstation)
Die Meldungen sind halt sehr nervig, ansonnsten funktioniert ja alles die Daten kommen und meine Plots vonn den Tuya Geräten sehen sauber aus.
Ich habe halt jeden Tag ein fhem.log von über 5MB weil soviele der Meldungen drin stehen und mit verbose 0 ging es auch nicht weg.
Ich danke dir vielmals fürs reinschauen.
Ist irgendetwas mit den Versionen noch nicht in ordnung?
Gruß,
Stefan
nun hat das update geklappt :-)
und was die Doppelten betrifft: Teilerfolg
JL devices: doppelt nur offlines
SP devices: 4 von 16 doppelt, alle online 4 doppelte wohl Firmware
Temp devices: alle innerhalb _tuya doppelt, aber mit korrekter und aktuellen Daten (hier hatte ich die devices in TUYA_xx umbenannt (per rename), um die reading wie in _local zu haben
damit kann ich leben ;-)
in der FHEMPY.log
hagelt es immer noch:
23-01-31 22:18:41,696 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:18:43,356 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:18:46,225 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:18:46,286 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:18:46,709 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:18:51,298 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:18:51,721 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:18:53,369 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:18:56,237 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:18:56,311 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:18:56,732 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:01,323 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:01,744 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:03,382 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:04,163 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:06,250 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:06,335 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:06,756 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:11,347 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:11,768 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:13,394 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:16,262 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:16,360 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:16,779 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:21,373 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:21,791 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:23,405 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:26,274 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:26,385 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:26,802 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:31,397 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:31,814 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:33,418 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:36,287 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:36,409 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:36,826 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:39,770 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:41,422 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:41,838 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:43,430 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:46,299 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:46,434 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:46,850 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:51,447 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:51,862 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:53,442 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:56,312 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:56,458 - WARNING - asyncio: socket.send() raised exception.
2023-01-31 22:19:56,873 - WARNING - asyncio: socket.send() raised exception.
das nagelt aber wohl nur die log zu, an der Performace spüre ich nichts
was meinst du dazu?
update: bei den Temps steht jetzt in den readings tuya_local !! der richtige Wert :-)
Hi,
von mir auch noch eine Rückmeldung.
Habe auch keinen Performance Impakt mehr.
Die Auslastung des Raspberrys über nach sah auch gut aus.
Nach dem es beim Start gestern noch einige Fehler im Log gab, ist das Log von heute komplett leer.
Keine Fehler sowohl im fhempy.log noch im fhem.log.
Verstehe zwar nicht warum der gestern so gehustet hat beim starten aber jetzt hat es sich gefangen.
Gruß und Danke,
Stefan
meine Vermutung: am Anfang braucht es ewig
bei mir tauchen immer noch doppelte auf, die bei jedem Neustart beharrlich wieder findet
Hmm seltsam,
nach über 12 Stunden absolute Ruhe im Log hat er um 12:08:20 und dann nochmal um 12:18:15 und 12:18:16 das log voll gemüllt.
Danach wieder alles ok.
Er schreibt dann in einer Sekunde seitenweise raus.
Ich dachte schon, dass da vielleicht meine Zwangstrennung war, das war aber nicht der Fall.
Könnte es trotzdem sein dass wenn mal kurz keine Verbindung aufgebaut werden kann das er dann irgendwie in kürzester Zeit viele Fehler raus protokolliert.
Der Spuk dauert nur 1 bzw 2 Sekunden aber er schreibt Tonnenweise meldungen.
Könnte er bei einem Problem mit einem device nicht 5 sek warten und neu probieren?
Danke und Gruß,
Stefan
bei mir gab es im log um 13:00 wenige Meldungen im FHEM-Log u.a. zu meinem JL03 .
Dieser Stecker war zu der Zeit stromlos.
Im Fhempy.log steht ca. 34000 mal
2023-02-01 16:20:18,727 - WARNING - asyncio: socket.send() raised exception.
darf ich nochmals anregen, den devices ein Attribut "active" zu verpassen
0 = inaktiv
1 = aktiv
Solange der Attribut-Wert 0 ist, würde das Device beim fhempy restart zwar als "bekannt" erkannt werden; ein zig-tausendfaches Nachfragen, ob es tatsächlich da ist und Werte liefert, könnte dann entfallen.
Ein weiteres attr könnte "polling" sein;der Schwellwert, wielange/wieoft nach Werten des devices abgefragt werden soll.
Zitat von: thburkhart am 01 Februar 2023, 16:31:50
bei mir gab es im log um 13:00 wenige Meldungen im FHEM-Log u.a. zu meinem JL03 .
Dieser Stecker war zu der Zeit stromlos.
Im Fhempy.log steht ca. 34000 mal
2023-02-01 16:20:18,727 - WARNING - asyncio: socket.send() raised exception.
Kannst du das reproduzieren? Also Stecker stromlos machen und dann prüfen ob der Fehler kommt? Bitte zur gleichen Zeit schauen ob FHEM evtl. blockiert.
Ich habe das nochmals recherchiert und der Fehler (socket.send()...) dürfte kommen, wenn FHEM blockiert.
Zitat von: thburkhart am 01 Februar 2023, 17:11:39
darf ich nochmals anregen, den devices ein Attribut "active" zu verpassen
0 = inaktiv
1 = aktiv
Solange der Attribut-Wert 0 ist, würde das Device beim fhempy restart zwar als "bekannt" erkannt werden; ein zig-tausendfaches Nachfragen, ob es tatsächlich da ist und Werte liefert, könnte dann entfallen.
Ein weiteres attr könnte "polling" sein;der Schwellwert, wielange/wieoft nach Werten des devices abgefragt werden soll.
Es wird nix nachgefragt ob ein Wert da ist und es gibt auch kein pollen. Es wird einmalig eine Verbindung zur Tuya Cloud aufgebaut und wenn von dort ein Event kommt, wird dieser verarbeitet. Alles andere würde ja sonst dazu führen, dass an Drücken am Schalter nicht sofort in FHEM ankommt.
Zitat von: stefanru am 01 Februar 2023, 15:01:28
Hmm seltsam,
nach über 12 Stunden absolute Ruhe im Log hat er um 12:08:20 und dann nochmal um 12:18:15 und 12:18:16 das log voll gemüllt.
Danach wieder alles ok.
Er schreibt dann in einer Sekunde seitenweise raus.
Ich dachte schon, dass da vielleicht meine Zwangstrennung war, das war aber nicht der Fall.
Könnte es trotzdem sein dass wenn mal kurz keine Verbindung aufgebaut werden kann das er dann irgendwie in kürzester Zeit viele Fehler raus protokolliert.
Der Spuk dauert nur 1 bzw 2 Sekunden aber er schreibt Tonnenweise meldungen.
Könnte er bei einem Problem mit einem device nicht 5 sek warten und neu probieren?
Danke und Gruß,
Stefan
Mit was für Meldungen ist es voll? Nachdem du nur ein paar wenige Devices hast, kannst du bitte nur ein Device einrichten und mit diesen testen?
Zitat von: dominik am 01 Februar 2023, 20:50:43
Es wird nix nachgefragt ob ein Wert da ist und es gibt auch kein pollen. Es wird einmalig eine Verbindung zur Tuya Cloud aufgebaut und wenn von dort ein Event kommt, wird dieser verarbeitet. Alles andere würde ja sonst dazu führen, dass an Drücken am Schalter nicht sofort in FHEM ankommt.
laienhaft ausgedückt:/verstanden: dann wird ständig in die cloud gehorcht und ggf. werden neue devices in FHEM angelegt und dies ggf. doppelt zu del "locals". Dies könnte unterbleibeb bzw. vermmieden werden bei devices, die man sich mit attr "inactive" gemerkt hat
Zitat von: dominik am 01 Februar 2023, 20:48:40
Kannst du das reproduzieren? Also Stecker stromlos machen und dann prüfen ob der Fehler kommt? Bitte zur gleichen Zeit schauen ob FHEM evtl. blockiert.
Ich habe das nochmals recherchiert und der Fehler (socket.send()...) dürfte kommen, wenn FHEM blockiert.
wird gemacht
Ergebnis:
Stromlos machen: kein Fehler im FHEM-log
Shutdown restart: Temp ZigBees werden nochmals neu anlegt.
Das doppelt Anlegen liegt nicht an der Cloud oder Polling oder ähnlichen. Das liegt mit 99%iger Wahrscheinlichkeit an der fehlenden Rückmeldung von FHEM zur Abfrage ob ein Device mit der DEVICEID bereits existiert.
Bitte daher nach dem shutdown restart die beiden Logs posten.
Hi Dominik,
das Probiere ich.
Leider habe ich die nächsten 2 Tage keine Zeit aber ich schaue es mir an.
Werde auch nochmal alles neu Aufsetzen bekomme einen Raspberry PI 400.
Mal sehen ob das etwas ändert.
Heute wars im Log dann ab 12 Uhr ruhig.
Heute abend um 19:41, ich weiß da war ich nicht mal am System ein kleinen aussetzer.
Hier das Log dazu.
fhem.log
2023.02.01 19:40:03 1: BindingsIo (local_pybinding): ERROR: Timeout while waiting for function to finish (id: 95874632)
2023.02.01 19:40:03 1: function => Set
2023.02.01 19:40:03 1: NAME => Computer_Stefan_bf881b7977c814af88jmrc
2023.02.01 19:40:03 1: FHEMPYTYPE => tuya_cloud
2023.02.01 19:40:03 1: id => 95874632
2023.02.01 19:40:03 1: PYTHONTYPE => tuya_cloud
2023.02.01 19:40:03 1: defargs => ARRAY(0x7522bf0)
2023.02.01 19:40:03 1: msgtype => function
2023.02.01 19:40:03 1: argsh => HASH(0x8ac01a8)
2023.02.01 19:40:03 1: defargsh => HASH(0x75e31c8)
2023.02.01 19:40:03 1: args => ARRAY(0x920d420)
2023.02.01 19:41:01 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,cur_voltage,228.5) missed to call readingsBeginUpdate first.
2023.02.01 19:41:01 1: stacktrace:
2023.02.01 19:41:01 1: main::readingsBulkUpdate called by (eval 4948527) (1)
2023.02.01 19:41:01 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.01 19:41:01 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.01 19:41:01 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.01 19:41:01 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.01 19:41:01 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.01 19:41:01 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.01 19:41:01 1: main::CallFn called by fhem.pl (1954)
2023.02.01 19:41:01 1: main::DoSet called by fhem.pl (1996)
2023.02.01 19:41:01 1: main::CommandSet called by fhem.pl (2904)
2023.02.01 19:41:01 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.01 19:41:01 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.01 19:41:01 1: main::FW_Notify called by fhem.pl (3976)
2023.02.01 19:41:01 1: main::CallFn called by fhem.pl (3888)
2023.02.01 19:41:01 1: main::DoTrigger called by fhem.pl (4995)
2023.02.01 19:41:01 1: main::readingsEndUpdate called by (eval 4948526) (1)
2023.02.01 19:41:01 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.01 19:41:01 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.01 19:41:01 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.01 19:41:01 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.01 19:41:01 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.01 19:41:01 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.01 19:41:01 1: main::CallFn called by fhem.pl (1954)
2023.02.01 19:41:01 1: main::DoSet called by fhem.pl (1996)
2023.02.01 19:41:01 1: main::CommandSet called by fhem.pl (2904)
2023.02.01 19:41:01 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.01 19:41:01 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.01 19:41:01 1: main::FW_Notify called by fhem.pl (3976)
2023.02.01 19:41:01 1: main::CallFn called by fhem.pl (3888)
2023.02.01 19:41:01 1: main::DoTrigger called by fhem.pl (4995)
2023.02.01 19:41:01 1: main::readingsEndUpdate called by (eval 4948525) (1)
2023.02.01 19:41:01 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.01 19:41:01 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.01 19:41:01 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.01 19:41:01 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.01 19:41:01 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.01 19:41:01 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.01 19:41:01 1: main::CallFn called by fhem.pl (1954)
2023.02.01 19:41:01 1: main::DoSet called by fhem.pl (1996)
2023.02.01 19:41:01 1: main::CommandSet called by fhem.pl (2904)
2023.02.01 19:41:01 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.01 19:41:01 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.01 19:41:01 1: main::FW_Notify called by fhem.pl (3976)
2023.02.01 19:41:01 1: main::CallFn called by fhem.pl (3888)
2023.02.01 19:41:01 1: main::DoTrigger called by fhem.pl (4995)
2023.02.01 19:41:01 1: main::readingsEndUpdate called by (eval 4948523) (1)
2023.02.01 19:41:01 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.01 19:41:01 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
fhempy.log
2023-02-01 19:41:00,936 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'tuya_local_bfb7810a3e397c5fa4u7ud'},'add_ele','0.004');;
2023-02-01 19:41:00,941 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'tuya_local_bf881b7977c814af88jmrc'},'online','1');;
2023-02-01 19:41:00,948 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'tuya_local_bf68d9b41c16be3713vcc1'},'cur_voltage','228.5');;
2023-02-01 19:41:01,770 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'Sybille_Tablet_bf68d9b41c16be3713vcc1'});;
Im fhem py log hat es aber doch mit local zu tun und mit Cloud.
im fhem log sind 2 Cloud Devices genannt.
Das eine taucht auch im fhempy.log auf das andere aber nicht.
Gruß und vielen Dank,
Stefan
Danke dir für das Log! Das hat mir geholfen da nochmals auf genauere Fehlersuche zu gehen.
Ich habe eine Korrektur in der BindingsIo gemacht. Bitte daher ein FHEM update machen und prüfen ob die Fehler weiterhin auftreten.
Super, vielen Dank!
Mache ich sobald ich dazu komme, und melde mich.
Gruß,
Stefan
Zitat von: dominik am 01 Februar 2023, 22:09:05
Das doppelt Anlegen liegt nicht an der Cloud oder Polling oder ähnlichen. Das liegt mit 99%iger Wahrscheinlichkeit an der fehlenden Rückmeldung von FHEM zur Abfrage ob ein Device mit der DEVICEID bereits existiert.
Bitte daher nach dem shutdown restart die beiden Logs posten.
Guten Mogen,
habe erst das FHEM-Update gefahren und dann shutdown restart.
Log FHEM:
2023.02.02 09:30:29 1:
2023.02.02 09:30:29 1: Downloading https://fhem.de/fhemupdate/controls_fhem.txt
2023.02.02 09:30:29 2: Backup with command: tar czf ./backup/FHEM-20230202_093029.tar.gz "./db_create.sql" "./fhem.pl" "./fhem 2022-12-13-1.cfg" "./fhem 2022-12-14.cfg" "./db.conf" "./contrib" "./lib" "./README_DEMO.txt" "./www" "./GPL_V2.txt" "./fhem-demo.cfg" "./alexa-fhem.cfg" "./README" "./MAINTAINER.txt" "./fhem mit tuya 2023-01-20.cfg" "./restoreDir" "./fhem.cfg" "./demolog" "./configDB.db" "./fhem-2023-01-31.cfg" "./log" "./sqldump" "./configDB.conf" "./fhem tuya auskommentiert1 2023-01-20.cfg" "./configDB.pm" "./docs" "./CHANGED" "./fhem 2023-01-30.cfg" "./fhem 2023-01-21.cfg" "./fhem.cfg.demo" "./fhem 2023-01-24.cfg" "./FHEM"
2023.02.02 09:31:43 1: backup done: FHEM-20230202_093029.tar.gz (134610717 Bytes)
2023.02.02 09:31:43 1: fhem
2023.02.02 09:31:43 1: RMDIR: ./restoreDir/update/2023-01-28
2023.02.02 09:31:43 1: UPD ./CHANGED
2023.02.02 09:31:43 1: UPD FHEM/10_ZWave.pm
2023.02.02 09:31:43 1: UPD FHEM/72_FB_CALLMONITOR.pm
2023.02.02 09:31:43 1: UPD FHEM/74_AutomowerConnect.pm
2023.02.02 09:31:43 1: UPD FHEM/75_AutomowerConnectDevice.pm
2023.02.02 09:31:43 1: UPD FHEM/93_DbLog.pm
2023.02.02 09:31:43 1: UPD FHEM/93_DbRep.pm
2023.02.02 09:31:43 1: UPD FHEM/98_ComfoAir.pm
2023.02.02 09:31:44 1: UPD FHEM/98_Modbus.pm
2023.02.02 09:31:44 1: saving fhem.cfg
2023.02.02 09:31:44 1: saving ./log/fhem.save
2023.02.02 09:31:44 1:
2023.02.02 09:31:44 1: New entries in the CHANGED file:
2023.02.02 09:31:44 1: - feature: 74_AutomowerConnect: rework detail view
2023.02.02 09:31:44 1: getter for MowerData and StatisticsData
2023.02.02 09:31:44 1: - feature: 75_AutomowerConnectDevice: same as AutomowerConnect
2023.02.02 09:31:44 1: - feature: 93_DbLog: new Get menu for a selection of getters,
2023.02.02 09:31:44 1: send Log data back to parent process, Forum:#131790
2023.02.02 09:31:44 1: - change: 93_DbRep: ignore non-numeric values in diffValue and output
2023.02.02 09:31:44 1: the erroneous record in the log
2023.02.02 09:31:44 1:
2023.02.02 09:31:44 1:
2023.02.02 09:31:44 1: Downloading https://raw.githubusercontent.com/dominikkarall/fhempy/master/controls_pythonbinding.txt
2023.02.02 09:31:44 1: pythonbinding
2023.02.02 09:31:44 1: UPD FHEM/10_BindingsIo.pm
2023.02.02 09:31:44 1: saving fhem.cfg
2023.02.02 09:31:44 1: saving ./log/fhem.save
2023.02.02 09:31:44 1:
2023.02.02 09:31:44 1: New entries in the CHANGED file:
2023.02.02 09:31:44 1: See https://github.com/fhempy/fhempy/releases for details
2023.02.02 09:31:44 1:
2023.02.02 09:31:44 1:
2023.02.02 09:31:44 1: Downloading https://raw.githubusercontent.com/PatricSperling/FHEM_SST/master/controls_SST.txt
2023.02.02 09:31:44 1: SST
2023.02.02 09:31:45 1: nothing to do...
2023.02.02 09:31:45 1: Calling /usr/bin/perl ./contrib/commandref_modular.pl, this may take a while
2023.02.02 09:31:45 1:
2023.02.02 09:31:45 1: update finished, "shutdown restart" is needed to activate the changes.
2023.02.02 09:32:09 3: Pythonbinding_15733: read: end of file reached while sysread
2023.02.02 09:32:09 3: Pythonbinding_15733: stopped
2023.02.02 09:32:09 3: Pythonbinding_15733: starting
2023.02.02 09:32:10 2: Deleting fhempy-2023-01-23.log
2023.02.02 09:32:10 3: Pythonbinding_15733: using logfile: ./log/fhempy-2023-02-02.log
2023.02.02 09:32:23 3: Please define 0 first
2023.02.02 09:32:23 3: Please define 0 first
2023.02.02 09:32:23 3: attr 0 DbLogExclude .* ; attr 0 event-on-change-reading .* : Please define 0 first
Please define 0 first
2023.02.02 09:32:23 3: n_defined return value: Please define 0 first
Please define 0 first
2023.02.02 09:32:26 1: ERROR evaluating my $EVENT= $evalSpecials->{'%EVENT'};my $EVTPART0= $evalSpecials->{'%EVTPART0'};my $NAME= $evalSpecials->{'%NAME'};my $SELF= $evalSpecials->{'%SELF'};my $TYPE= $evalSpecials->{'%TYPE'};{ fhem("attr $EVTPART1 DbLogExclude .* ; attr $EVTPART1 event-on-change-reading .*");}: Global symbol "$EVTPART1" requires explicit package name (did you forget to declare "my $EVTPART1"?) at (eval 766349) line 1.
Global symbol "$EVTPART1" requires explicit package name (did you forget to declare "my $EVTPART1"?) at (eval 766349) line 1.
2023.02.02 09:32:26 3: n_defined return value: Global symbol "$EVTPART1" requires explicit package name (did you forget to declare "my $EVTPART1"?) at (eval 766349) line 1.
Global symbol "$EVTPART1" requires explicit package name (did you forget to declare "my $EVTPART1"?) at (eval 766349) line 1.
2023.02.02 09:33:49 3: Please define 1 first
2023.02.02 09:33:49 3: Please define 1 first
2023.02.02 09:33:49 3: attr 1 DbLogExclude .* ; attr 1 event-on-change-reading .* : Please define 1 first
Please define 1 first
2023.02.02 09:33:49 3: n_defined return value: Please define 1 first
Please define 1 first
2023.02.02 09:33:49 1: ERROR evaluating my $EVENT= $evalSpecials->{'%EVENT'};my $EVTPART0= $evalSpecials->{'%EVTPART0'};my $NAME= $evalSpecials->{'%NAME'};my $SELF= $evalSpecials->{'%SELF'};my $TYPE= $evalSpecials->{'%TYPE'};{ fhem("attr $EVTPART1 DbLogExclude .* ; attr $EVTPART1 event-on-change-reading .*");}: Global symbol "$EVTPART1" requires explicit package name (did you forget to declare "my $EVTPART1"?) at (eval 769034) line 1.
Global symbol "$EVTPART1" requires explicit package name (did you forget to declare "my $EVTPART1"?) at (eval 769034) line 1.
2023.02.02 09:33:49 3: n_defined return value: Global symbol "$EVTPART1" requires explicit package name (did you forget to declare "my $EVTPART1"?) at (eval 769034) line 1.
Global symbol "$EVTPART1" requires explicit package name (did you forget to declare "my $EVTPART1"?) at (eval 769034) line 1.
2023.02.02 09:34:16 1: PERL WARNING: Argument "14\0" isn't numeric in sprintf at ./FHEM/36_LaCrosse.pm line 212.
2023.02.02 09:34:16 1: PERL WARNING: Argument "\04" isn't numeric in multiplication (*) at ./FHEM/36_LaCrosse.pm line 219.
2023.02.02 09:34:17 1: PERL WARNING: Argument "140\0" isn't numeric in addition (+) at ./FHEM/36_LaCrosse.pm line 219.
2023.02.02 10:07:25 2: DbLog dblog_THB - Wait for last database cycle due to shutdown ...
2023.02.02 10:07:25 1: Server shutdown delayed due to dblog_THB,alexa for max 10 sec
2023.02.02 10:07:26 2: DbLog dblog_THB - Last database write cycle done
2023.02.02 10:07:27 3: alexa: read: end of file reached while sysread
2023.02.02 10:07:27 3: alexa: stopped
2023.02.02 10:07:27 0: Server shutdown
2023.02.02 10:07:27 2: DbLog dblog_THB - stopping SubProcess PID >16605< ...
2023.02.02 10:07:27 2: DbLog dblog_THB - SubProcess PID >16605< stopped
2023.02.02 10:07:29 1: Including fhem.cfg
2023.02.02 10:07:30 2: DbLog dblog_THB - Subprocess >23532< initialized ... ready for non-blocking operation
2023.02.02 10:07:31 3: telnetPort: port 7072 opened
2023.02.02 10:07:31 3: WEB: port 8083 opened
2023.02.02 10:07:31 3: WEBphone: port 8084 opened
2023.02.02 10:07:31 3: WEBtablet: port 8085 opened
2023.02.02 10:07:31 3: TelegramBot_Define TelegramBotTHB: called
2023.02.02 10:07:31 3: MQTT2: port 1883 opened
2023.02.02 10:07:31 3: BindingsIo v1.0.1
2023.02.02 10:07:31 3: found IP 127.0.0.1
2023.02.02 10:07:31 3: fhempyServer v1.0.0
2023.02.02 10:07:31 3: fhempy v1.0.0 (tuya_cloud: TUYA)
2023.02.02 10:07:32 3: fhempy v1.0.0 (tuya: tuya_system)
2023.02.02 10:07:32 3: Opening CUL_0 device /dev/ttyACM0
2023.02.02 10:07:32 3: Setting CUL_0 serial parameters to 9600,8,N,1
2023.02.02 10:07:32 3: CUL_0: Possible commands: BbCFiAZNkGMKUYRTVWXefmLltux
2023.02.02 10:07:32 3: CUL_0 device opened
2023.02.02 10:07:32 2: Switched CUL_0 rfmode to MAX
2023.02.02 10:07:32 3: Opening JLLaCR device /dev/ttyUSB0
2023.02.02 10:07:32 3: Setting JLLaCR serial parameters to 57600,8,N,1
2023.02.02 10:07:33 3: JLLaCR device opened
2023.02.02 10:07:33 1: PERL WARNING: Use of uninitialized value in numeric ge (>=) at ./FHEM/12_OilFox.pm line 387, <$fh> line 524.
2023.02.02 10:07:33 2: LOGIN TOKEN MISSING OR EXPIRED
2023.02.02 10:07:33 3: myOilFox - email set to bkt@gmx.net
2023.02.02 10:07:33 3: myOilFox - set interval: 36000
2023.02.02 10:07:33 3: myOilFox - password set to thbbkt25
2023.02.02 10:07:33 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.02 10:07:49 2: eventTypes: loaded 15849 lines from ./log/eventTypes.txt
2023.02.02 10:07:49 3: TX29_00: I/O device is JLLaCR
2023.02.02 10:07:49 3: TX29DTH_01: I/O device is JLLaCR
2023.02.02 10:07:49 3: TX29DTH_02: I/O device is JLLaCR
2023.02.02 10:07:49 3: TX29DTH_03: I/O device is JLLaCR
2023.02.02 10:07:49 3: TX29DTH_04: I/O device is JLLaCR
2023.02.02 10:07:49 3: TX29DTH_05: I/O device is JLLaCR
2023.02.02 10:07:49 3: TX29DTH_06: I/O device is JLLaCR
2023.02.02 10:07:49 3: TX29DTH_07: I/O device is JLLaCR
2023.02.02 10:07:49 3: TX29DTH_08: I/O device is JLLaCR
2023.02.02 10:07:49 3: TX29DTH_09: I/O device is JLLaCR
2023.02.02 10:07:49 3: TX29DTH_10: I/O device is JLLaCR
2023.02.02 10:07:49 3: TX29DTH_11: I/O device is JLLaCR
2023.02.02 10:07:49 3: TX29DTH_12: I/O device is JLLaCR
2023.02.02 10:07:49 3: TX25IT_13: I/O device is JLLaCR
2023.02.02 10:07:49 3: TX29DTH_14: I/O device is JLLaCR
2023.02.02 10:07:49 3: TX29DTH_15: I/O device is JLLaCR
2023.02.02 10:07:49 3: TX29DTH_16: I/O device is JLLaCR
2023.02.02 10:07:49 3: TX29DTH_17: I/O device is JLLaCR
2023.02.02 10:07:49 3: TX29DTH_18: I/O device is JLLaCR
2023.02.02 10:07:49 3: TX29DTH_19: I/O device is JLLaCR
2023.02.02 10:07:49 3: TX29DTH_20: I/O device is JLLaCR
2023.02.02 10:07:49 3: TX29DTH_21: I/O device is JLLaCR
2023.02.02 10:07:49 3: TX29DTH_22: I/O device is JLLaCR
2023.02.02 10:07:49 3: HUEDevice2: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice4: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice5: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice6: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice7: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice8: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice10: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice17: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice18: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice19: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice20: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice22: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice23: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice24: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice25: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice27: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice28: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice29: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice30: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice31: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice32: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice33: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice38: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice39: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice40: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice41: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup0: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup1: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup2: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup3: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup4: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup5: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup6: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup7: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup8: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup9: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup10: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup11: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup12: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup13: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup14: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup15: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup16: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup17: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup18: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup19: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup20: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup21: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup22: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup23: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup24: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup25: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup26: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup27: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup28: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup29: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup30: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice44: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEGroup31: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUESensor6: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUESensor8: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUESensor10: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUESensor13: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUESensor24: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUESensor27: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUESensor34: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUESensor37: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUESensor45: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice45: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice46: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice47: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice48: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice49: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice50: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice51: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUESensor91: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUESensor110: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUESensor1: I/O device is hueBridge1
2023.02.02 10:07:49 3: HUEDevice52: I/O device is hueBridge1
2023.02.02 10:07:49 1: MaxTemp: WT
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_BULB1)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_BULB2)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_BULB3)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_DIY1)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_DIY3)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_DIY4)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_EMYLO1)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_EMYLO2)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_EMYLOD2)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_EMYLO3)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_EMYLO4)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL02)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL03)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL04)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL05)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL06)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL07)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL08)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL09)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL10Z)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL11Z)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL12Z)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL13)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL14)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL15)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL16)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL17)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL18)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL19)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL20)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL21)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL22)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL23)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL24)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL25)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL26)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL27)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL28)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL29)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL30)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL31)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL32)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL33)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL34)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL35)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_JL36)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_PS1)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_PS2)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_PS3)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_PS4)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_PS5)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_PS7)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_SCHF1)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_SCHF2)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_SCHF3)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_SCHF4)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_SP01)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_SP02)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_SP03)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_SP04)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_SP05)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_SP06)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_SP07)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_SP08)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_SP09)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_SP10)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_SP11)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_SP12)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_SP13)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_SP14)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_SP15)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_SP16)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_STF1)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_STF2)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_STF3)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya: TUYA_MMG)
2023.02.02 10:07:50 3: SST (SamsungSmartThingsConnector): define - CONNECTOR defined as SamsungSmartThingsConnector
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp03)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp04)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp05)
2023.02.02 10:07:50 1: PERL WARNING: Useless use of anonymous hash ({}) in void context at (eval 127) line 1, <$fh> line 6335.
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp07)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_60381718807d3a04bbb4)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_60381718500291bade80)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_180025363c6105dcdcaf)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bfbeab33da30f5635ffj0r)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bfd99c63a8b65928a56hdb)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bf9e9fea71f3692d15gzrq)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bfffc31d13d14bca5dayj6)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp01)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_50880180cc50e30cbe91)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_52470320e09806c9a53f)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_60381718807d3a01eb63)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_67242256f4cfa2ce1662)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_045074212cf432ca0721)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_00673231e09806cb6fa5)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_260064612cf432ca55d8)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_07847240bcddc29b03e9)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_07847240dc4f225fdda0)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_06515140cc50e3d62490)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_00673231e09806cb188e)
2023.02.02 10:07:50 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bf3761a5af5f8d6361rmhh)
2023.02.02 10:07:51 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_47104178dc4f2236e437)
2023.02.02 10:07:51 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bf6b1900c331a78a2fkecw)
2023.02.02 10:07:51 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bffb7d9839e65fcdeciaqn)
2023.02.02 10:07:51 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_453005615002911dfe06)
2023.02.02 10:07:51 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bf16f1788a2fd6edd6pr1d)
2023.02.02 10:07:51 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_34602852ecfabc47cbe1)
2023.02.02 10:07:51 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bfefd42e199ea92ee3jbwh)
2023.02.02 10:07:51 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_4530056170039f4a87e5)
2023.02.02 10:07:51 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_720570712462ab27e625)
2023.02.02 10:07:51 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_720570712462ab280270)
2023.02.02 10:07:51 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_887800042cf4325f15ef)
2023.02.02 10:07:51 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_853556472cf4326e60da)
2023.02.02 10:07:51 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_743066432cf43267661d)
2023.02.02 10:07:51 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_627425735002915f502b)
2023.02.02 10:07:51 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_50880180840d8e87664b)
2023.02.02 10:07:51 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_50880180cc50e30c4c90)
2023.02.02 10:07:51 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_21410806cc50e37bdb15)
2023.02.02 10:07:51 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_104380002462ab30258d)
2023.02.02 10:07:51 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_0120018760019453b4b1)
2023.02.02 10:07:51 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp06)
2023.02.02 10:07:51 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_17710212600194dba99d)
2023.02.02 10:07:51 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp02)
2023.02.02 10:07:51 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bfc0750fc8af85f5d5vei7)
2023.02.02 10:07:51 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bfabd3dbaa5113764dzgkn)
2023.02.02 10:07:51 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bfe1b5bb54592232acz7dg)
2023.02.02 10:07:51 1: Including ./log/fhem.save
2023.02.02 10:07:51 1: Messages collected while initializing FHEM:SecurityCheck:
telnetPort is not password protected
WEBphone is not password protected
MQTT2 is not password protected
WEBtablet is not password protected
WEB 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.02 10:07:51 3: Pythonbinding_15733: starting
2023.02.02 10:07:51 3: Pythonbinding_15733: using logfile: ./log/fhempy-2023-02-02.log
2023.02.02 10:07:52 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2023.02.02 10:07:52 3: alexa: starting
2023.02.02 10:07:52 3: alexa: using logfile: ./log/alexa-2023-02-02.log
2023.02.02 10:07:52 2: hueBridge1: autocreate: created 0/0/0 devices (ignored 0/2/26)
2023.02.02 10:07:54 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2023.02.02 10:07:54 0: Featurelevel: 6.2
2023.02.02 10:07:54 0: Server started with 532 defined entities (fhem.pl:27110/2023-01-23 perl:5.032001 os:linux user:fhem pid:23531)
2023.02.02 10:07:54 3: DbLog dblog_THB - DB connection parameters are initialized in the SubProcess
2023.02.02 10:07:54 1: PERL WARNING: devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
2023.02.02 10:07:54 1: PERL WARNING: ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1310.
2023.02.02 10:07:55 3: DbLog dblog_THB - DB connection parameters are stored in SubProcess
2023.02.02 10:07:55 3: alexa: read: end of file reached while sysread
2023.02.02 10:07:55 3: alexa: stopped
2023.02.02 10:07:55 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2023.02.02 10:07:55 3: alexa: starting
2023.02.02 10:07:55 3: alexa: using logfile: ./log/alexa-2023-02-02.log
2023.02.02 10:07:56 2: AttrTemplates: got 258 entries
2023.02.02 10:08:01 3: Please define server first
2023.02.02 10:08:01 3: Please define server first
2023.02.02 10:08:01 3: attr server DbLogExclude .* ; attr server event-on-change-reading .* : Please define server first
Please define server first
2023.02.02 10:08:01 3: n_defined return value: Please define server first
Please define server first
2023.02.02 10:08:04 2: hueBridge1: http request failed: SSL connect attempt failed
2023.02.02 10:08:04 2: Buderus : km200_ParseHttpResponseInit - ERROR : /: No proper Communication with Gateway: read from http://192.168.9.114:80 timed out
2023.02.02 10:08:04 2: Buderus : km200_ParseHttpResponseInit - ERROR : Timer restarted to try again in 10s
2023.02.02 10:08:05 2: hueBridge1: http request failed: https://192.168.9.179/eventstream/clip/v2: empty answer received
2023.02.02 10:08:05 2: hueBridge1: EventStream: terminated; retrying later
2023.02.02 10:08:06 3: Please define server first
2023.02.02 10:08:06 3: Please define server first
2023.02.02 10:08:06 3: attr server DbLogExclude .* ; attr server event-on-change-reading .* : Please define server first
Please define server first
2023.02.02 10:08:06 3: n_defined return value: Please define server first
Please define server first
2023.02.02 10:08:08 1: PERL WARNING: Use of uninitialized value $value in string eq at ./FHEM/10_MAX.pm line 2057.
2023.02.02 10:08:08 1: PERL WARNING: Use of uninitialized value $value in string eq at ./FHEM/10_MAX.pm line 2058.
2023.02.02 10:08:10 3: Please define 0 first
2023.02.02 10:08:10 3: Please define 0 first
2023.02.02 10:08:10 3: attr 0 DbLogExclude .* ; attr 0 event-on-change-reading .* : Please define 0 first
Please define 0 first
2023.02.02 10:08:10 3: n_defined return value: Please define 0 first
Please define 0 first
2023.02.02 10:08:15 1: ERROR evaluating my $EVENT= $evalSpecials->{'%EVENT'};my $EVTPART0= $evalSpecials->{'%EVTPART0'};my $NAME= $evalSpecials->{'%NAME'};my $SELF= $evalSpecials->{'%SELF'};my $TYPE= $evalSpecials->{'%TYPE'};{ fhem("attr $EVTPART1 DbLogExclude .* ; attr $EVTPART1 event-on-change-reading .*");}: Global symbol "$EVTPART1" requires explicit package name (did you forget to declare "my $EVTPART1"?) at (eval 706) line 1.
Global symbol "$EVTPART1" requires explicit package name (did you forget to declare "my $EVTPART1"?) at (eval 706) line 1.
2023.02.02 10:08:15 3: n_defined return value: Global symbol "$EVTPART1" requires explicit package name (did you forget to declare "my $EVTPART1"?) at (eval 706) line 1.
Global symbol "$EVTPART1" requires explicit package name (did you forget to declare "my $EVTPART1"?) at (eval 706) line 1.
2023.02.02 10:08:38 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_63667231840d8e501cab)
2023.02.02 10:08:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bff304caecd1bfb52dahwu)
2023.02.02 10:08:47 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_2053863070039f179683)
2023.02.02 10:09:50 1: readingsUpdate(TUYA_JL04,cur_current,240.0) missed to call readingsBeginUpdate first.
2023.02.02 10:09:50 1: stacktrace:
2023.02.02 10:09:50 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.02.02 10:09:50 1: main::readingsBulkUpdateIfChanged called by (eval 3576) (1)
2023.02.02 10:09:50 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:09:50 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:09:50 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:09:50 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:09:50 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.02 10:09:50 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.02 10:09:50 1: main::CallFn called by fhem.pl (3198)
2023.02.02 10:09:50 1: main::CommandAttr called by (eval 3567) (1)
2023.02.02 10:09:50 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:09:50 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:09:50 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:09:50 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:09:50 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.02 10:09:50 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.02 10:09:50 1: main::CallFn called by fhem.pl (3198)
2023.02.02 10:09:50 1: main::CommandAttr called by (eval 3565) (1)
2023.02.02 10:09:50 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:09:50 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:09:50 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:09:50 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:09:50 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.02 10:09:50 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.02 10:09:50 1: main::CallFn called by fhem.pl (1954)
2023.02.02 10:09:50 1: main::DoSet called by fhem.pl (1996)
2023.02.02 10:09:50 1: main::CommandSet called by fhem.pl (2904)
2023.02.02 10:09:50 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.02 10:09:50 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.02 10:09:50 1: main::FW_Notify called by fhem.pl (3976)
2023.02.02 10:09:50 1: main::CallFn called by fhem.pl (3888)
2023.02.02 10:09:50 1: main::DoTrigger called by fhem.pl (4995)
2023.02.02 10:09:50 1: main::readingsEndUpdate called by fhem.pl (5178)
2023.02.02 10:09:50 1: main::readingsSingleUpdate called by (eval 3543) (1)
2023.02.02 10:09:50 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:09:50 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:09:50 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:09:50 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:09:50 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.02 10:09:50 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.02 10:09:50 1: main::CallFn called by fhem.pl (3198)
2023.02.02 10:09:50 1: main::CommandAttr called by (eval 3540) (1)
2023.02.02 10:09:50 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:09:50 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:09:50 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:09:50 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:09:50 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.02 10:09:50 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.02 10:09:51 1: readingsUpdate(TUYA_JL04,cur_power,34.1) missed to call readingsBeginUpdate first.
2023.02.02 10:09:51 1: stacktrace:
2023.02.02 10:09:51 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.02.02 10:09:51 1: main::readingsBulkUpdateIfChanged called by (eval 3669) (1)
2023.02.02 10:09:51 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:09:51 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:09:51 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:09:51 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:09:51 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.02 10:09:51 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.02 10:09:51 1: main::CallFn called by fhem.pl (1954)
2023.02.02 10:09:51 1: main::DoSet called by fhem.pl (1996)
2023.02.02 10:09:51 1: main::CommandSet called by fhem.pl (2904)
2023.02.02 10:09:51 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.02 10:09:51 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.02 10:09:51 1: main::FW_Notify called by fhem.pl (3976)
2023.02.02 10:09:51 1: main::CallFn called by fhem.pl (3888)
2023.02.02 10:09:51 1: main::DoTrigger called by fhem.pl (4995)
2023.02.02 10:09:51 1: main::readingsEndUpdate called by (eval 3664) (1)
2023.02.02 10:09:51 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:09:51 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:09:51 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:09:51 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:09:51 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.02 10:09:51 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.02 10:09:51 1: main::CallFn called by fhem.pl (1954)
2023.02.02 10:09:51 1: main::DoSet called by fhem.pl (1996)
2023.02.02 10:09:51 1: main::CommandSet called by fhem.pl (2904)
2023.02.02 10:09:51 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.02 10:09:51 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.02 10:09:51 1: main::FW_Notify called by fhem.pl (3976)
2023.02.02 10:09:51 1: main::CallFn called by fhem.pl (3888)
2023.02.02 10:09:51 1: main::DoTrigger called by fhem.pl (4995)
2023.02.02 10:09:51 1: main::readingsEndUpdate called by (eval 3636) (1)
2023.02.02 10:09:51 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:09:51 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:09:51 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:09:51 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:09:51 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.02 10:09:51 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.02 10:09:51 1: main::CallFn called by fhem.pl (1954)
2023.02.02 10:09:51 1: main::DoSet called by fhem.pl (1996)
2023.02.02 10:09:51 1: main::CommandSet called by fhem.pl (2904)
2023.02.02 10:09:51 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.02 10:09:51 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.02 10:09:51 1: main::FW_Notify called by fhem.pl (3976)
2023.02.02 10:09:51 1: main::CallFn called by fhem.pl (3888)
2023.02.02 10:09:51 1: main::DoTrigger called by fhem.pl (4995)
2023.02.02 10:09:51 1: main::readingsEndUpdate called by (eval 3635) (1)
2023.02.02 10:09:51 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:13:03 2: error while requesting https://api.oilfox.io/customer-api/v1/login - read from https://api.oilfox.io:443 timed out
2023.02.02 10:13:11 3: DbLog dblog_THB - SubProcess connected to fhem
2023.02.02 10:13:13 2: hueBridge1: http request failed: https://192.168.9.179/eventstream/clip/v2: empty answer received
2023.02.02 10:13:13 2: hueBridge1: EventStream: terminated; retrying later
2023.02.02 10:13:17 1: PERL WARNING: Argument "40\0" isn't numeric in sprintf at ./FHEM/36_LaCrosse.pm line 212.
2023.02.02 10:13:17 1: PERL WARNING: Argument "\01" isn't numeric in bitwise and (&) at ./FHEM/36_LaCrosse.pm line 213.
2023.02.02 10:13:17 1: PERL WARNING: Argument "\073" isn't numeric in addition (+) at ./FHEM/36_LaCrosse.pm line 219.
2023.02.02 10:13:18 1: RMDIR: ./restoreDir/save/2023-01-30
2023.02.02 10:13:19 2: hueBridge1: autocreate: created 0/0/0 devices (ignored 0/2/26)
2023.02.02 10:14:03 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_2053863070039f16cef8)
2023.02.02 10:14:05 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_3367036770039f60c576)
2023.02.02 10:14:07 1: readingsUpdate(tuya_cloud_52470320e09806c9a53f,state,on) missed to call readingsBeginUpdate first.
2023.02.02 10:14:07 1: stacktrace:
2023.02.02 10:14:07 1: main::readingsBulkUpdate called by (eval 4059) (1)
2023.02.02 10:14:07 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:14:07 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:14:07 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:14:07 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:14:07 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:14:07 1: readingsUpdate(tuya_cloud_00673231e09806cb6fa5,state,on) missed to call readingsBeginUpdate first.
2023.02.02 10:14:07 1: stacktrace:
2023.02.02 10:14:07 1: main::readingsBulkUpdate called by (eval 4060) (1)
2023.02.02 10:14:07 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:14:07 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:14:07 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:14:07 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:14:07 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:14:09 1: readingsUpdate(tuya_cloud_00673231e09806cb6fa5,state,on) missed to call readingsBeginUpdate first.
2023.02.02 10:14:09 1: stacktrace:
2023.02.02 10:14:09 1: main::readingsBulkUpdate called by (eval 4130) (1)
2023.02.02 10:14:09 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:14:09 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:14:09 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:14:09 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:14:09 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:14:09 1: readingsUpdate(tuya_cloud_00673231e09806cb6fa5,state,on) missed to call readingsBeginUpdate first.
2023.02.02 10:14:09 1: stacktrace:
2023.02.02 10:14:09 1: main::readingsBulkUpdate called by (eval 4131) (1)
2023.02.02 10:14:09 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:14:09 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:14:09 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:14:09 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:14:09 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:14:09 1: readingsUpdate(tuya_cloud_00673231e09806cb6fa5,state,on) missed to call readingsBeginUpdate first.
2023.02.02 10:14:09 1: stacktrace:
2023.02.02 10:14:09 1: main::readingsBulkUpdate called by (eval 4132) (1)
2023.02.02 10:14:09 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:14:09 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:14:09 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:14:09 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:14:09 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:14:09 1: readingsUpdate(tuya_cloud_00673231e09806cb6fa5,state,on) missed to call readingsBeginUpdate first.
2023.02.02 10:14:09 1: stacktrace:
2023.02.02 10:14:09 1: main::readingsBulkUpdate called by (eval 4135) (1)
2023.02.02 10:14:09 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:14:09 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:14:09 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:14:09 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:14:09 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:14:09 1: readingsUpdate(tuya_cloud_00673231e09806cb6fa5,state,on) missed to call readingsBeginUpdate first.
2023.02.02 10:14:09 1: stacktrace:
2023.02.02 10:14:09 1: main::readingsBulkUpdate called by (eval 4139) (1)
2023.02.02 10:14:09 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:14:09 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:14:09 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:14:09 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:14:09 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:14:09 1: readingsUpdate(tuya_cloud_00673231e09806cb6fa5,state,on) missed to call readingsBeginUpdate first.
2023.02.02 10:14:09 1: stacktrace:
2023.02.02 10:14:09 1: main::readingsBulkUpdate called by (eval 4148) (1)
2023.02.02 10:14:09 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:14:09 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:14:09 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:14:09 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:14:09 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.02 10:14:09 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.02 10:14:09 1: main::CallFn called by fhem.pl (1954)
2023.02.02 10:14:09 1: main::DoSet called by fhem.pl (1996)
2023.02.02 10:14:09 1: main::CommandSet called by fhem.pl (2904)
2023.02.02 10:14:09 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.02 10:14:09 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.02 10:14:09 1: main::FW_Notify called by fhem.pl (3976)
2023.02.02 10:14:09 1: main::CallFn called by fhem.pl (3888)
2023.02.02 10:14:09 1: main::DoTrigger called by fhem.pl (4995)
2023.02.02 10:14:09 1: main::readingsEndUpdate called by fhem.pl (5178)
2023.02.02 10:14:09 1: main::readingsSingleUpdate called by (eval 4145) (1)
2023.02.02 10:14:09 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:14:09 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:14:09 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:14:09 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:14:09 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:14:09 1: readingsUpdate(tuya_cloud_52470320e09806c9a53f,countdown_1,0.0) missed to call readingsBeginUpdate first.
2023.02.02 10:14:09 1: stacktrace:
2023.02.02 10:14:09 1: main::readingsBulkUpdate called by (eval 4161) (1)
2023.02.02 10:14:09 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:14:09 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:14:09 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:14:09 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:14:09 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.02 10:14:09 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.02 10:14:09 1: main::CallFn called by fhem.pl (1954)
2023.02.02 10:14:09 1: main::DoSet called by fhem.pl (1996)
2023.02.02 10:14:09 1: main::CommandSet called by fhem.pl (2904)
2023.02.02 10:14:09 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.02 10:14:09 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.02 10:14:09 1: main::FW_Notify called by fhem.pl (3976)
2023.02.02 10:14:09 1: main::CallFn called by fhem.pl (3888)
2023.02.02 10:14:09 1: main::DoTrigger called by fhem.pl (4995)
2023.02.02 10:14:09 1: main::readingsEndUpdate called by fhem.pl (5178)
2023.02.02 10:14:09 1: main::readingsSingleUpdate called by (eval 4145) (1)
2023.02.02 10:14:09 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:14:09 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:14:09 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:14:09 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:14:09 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:14:09 1: readingsUpdate(tuya_cloud_00673231e09806cb6fa5,countdown_1,0.0) missed to call readingsBeginUpdate first.
2023.02.02 10:14:09 1: stacktrace:
2023.02.02 10:14:09 1: main::readingsBulkUpdate called by (eval 4162) (1)
2023.02.02 10:14:09 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:14:09 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:14:09 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:14:09 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:14:09 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.02 10:14:09 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.02 10:14:09 1: main::CallFn called by fhem.pl (1954)
2023.02.02 10:14:09 1: main::DoSet called by fhem.pl (1996)
2023.02.02 10:14:09 1: main::CommandSet called by fhem.pl (2904)
2023.02.02 10:14:09 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.02 10:14:09 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.02 10:14:09 1: main::FW_Notify called by fhem.pl (3976)
2023.02.02 10:14:09 1: main::CallFn called by fhem.pl (3888)
2023.02.02 10:14:09 1: main::DoTrigger called by fhem.pl (4995)
2023.02.02 10:14:09 1: main::readingsEndUpdate called by fhem.pl (5178)
2023.02.02 10:14:09 1: main::readingsSingleUpdate called by (eval 4145) (1)
2023.02.02 10:14:09 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:14:09 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:14:09 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:14:09 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:14:09 1: main::CallFn called by fhem.pl (784)
Hi,
habe das Update auch gemacht und nun neue Fehler beim Neustart und auch alt bekannt.
Insgesammt nochmal einiges mehr an Fehlern.
Der fhempyserver stürzt nun regelmäßig ab :-(
Leider komme ich gerade nicht an das fhempy.log.
fhem.log
2023.02.02 10:37:39 1: BindingsIo (local_pybinding): ERROR: Timeout while waiting for function to finish (id: 92513506)
2023.02.02 10:37:39 1: function => Set
2023.02.02 10:37:39 1: FHEMPYTYPE => tuya_cloud
2023.02.02 10:37:39 1: defargs => ARRAY(0x68f8200)
2023.02.02 10:37:39 1: defargsh => HASH(0x68f8140)
2023.02.02 10:37:39 1: args => ARRAY(0x87d4998)
2023.02.02 10:37:39 1: PYTHONTYPE => tuya_cloud
2023.02.02 10:37:39 1: argsh => HASH(0x867c7e0)
2023.02.02 10:37:39 1: id => 92513506
2023.02.02 10:37:39 1: NAME => Fernseher_bfb7810a3e397c5fa4u7ud
2023.02.02 10:37:39 1: msgtype => function
2023.02.02 10:37:43 1: BindingsIo (local_pybinding): Use of uninitialized value in string eq at (eval 1519) line 1.
=> COMMAND: foreach my $fhem_dev (sort keys %main::defs) { return 1 if(defined($main::defs{$fhem_dev}{FHEMPYTYPE}) && $main::defs{$fhem_dev}{FHEMPYTYPE} eq 'tuya_cloud' && $main::defs{$fhem_dev}{DEVICEID} eq 'bffa550a829a269630vhcn');;}return 0;;
2023.02.02 10:37:43 1: BindingsIo (local_pybinding): Use of uninitialized value in string eq at (eval 1519) line 1.
=> COMMAND: foreach my $fhem_dev (sort keys %main::defs) { return 1 if(defined($main::defs{$fhem_dev}{FHEMPYTYPE}) && $main::defs{$fhem_dev}{FHEMPYTYPE} eq 'tuya_cloud' && $main::defs{$fhem_dev}{DEVICEID} eq 'bffa550a829a269630vhcn');;}return 0;;
2023.02.02 10:37:43 1: BindingsIo (local_pybinding): Use of uninitialized value in string eq at (eval 1519) line 1.
=> COMMAND: foreach my $fhem_dev (sort keys %main::defs) { return 1 if(defined($main::defs{$fhem_dev}{FHEMPYTYPE}) && $main::defs{$fhem_dev}{FHEMPYTYPE} eq 'tuya_cloud' && $main::defs{$fhem_dev}{DEVICEID} eq 'bffa550a829a269630vhcn');;}return 0;;
2023.02.02 10:37:43 1: BindingsIo (local_pybinding): Use of uninitialized value in string eq at (eval 1550) line 1.
=> COMMAND: foreach my $fhem_dev (sort keys %main::defs) { return 1 if(defined($main::defs{$fhem_dev}{FHEMPYTYPE}) && $main::defs{$fhem_dev}{FHEMPYTYPE} eq 'tuya_cloud' && $main::defs{$fhem_dev}{DEVICEID} eq 'bf881b7977c814af88jmrc');;}return 0;;
2023.02.02 10:37:43 1: BindingsIo (local_pybinding): Use of uninitialized value in string eq at (eval 1550) line 1.
=> COMMAND: foreach my $fhem_dev (sort keys %main::defs) { return 1 if(defined($main::defs{$fhem_dev}{FHEMPYTYPE}) && $main::defs{$fhem_dev}{FHEMPYTYPE} eq 'tuya_cloud' && $main::defs{$fhem_dev}{DEVICEID} eq 'bf881b7977c814af88jmrc');;}return 0;;
2023.02.02 10:37:43 1: BindingsIo (local_pybinding): Use of uninitialized value in string eq at (eval 1550) line 1.
=> COMMAND: foreach my $fhem_dev (sort keys %main::defs) { return 1 if(defined($main::defs{$fhem_dev}{FHEMPYTYPE}) && $main::defs{$fhem_dev}{FHEMPYTYPE} eq 'tuya_cloud' && $main::defs{$fhem_dev}{DEVICEID} eq 'bf881b7977c814af88jmrc');;}return 0;;
2023.02.02 10:37:43 1: BindingsIo (local_pybinding): Use of uninitialized value in string eq at (eval 1551) line 1.
=> COMMAND: foreach my $fhem_dev (sort keys %main::defs) { return 1 if(defined($main::defs{$fhem_dev}{FHEMPYTYPE}) && $main::defs{$fhem_dev}{FHEMPYTYPE} eq 'tuya' && $main::defs{$fhem_dev}{DEVICEID} eq 'bf881b7977c814af88jmrc');;}return 0;;
2023.02.02 10:37:43 1: BindingsIo (local_pybinding): Use of uninitialized value in string eq at (eval 1551) line 1.
=> COMMAND: foreach my $fhem_dev (sort keys %main::defs) { return 1 if(defined($main::defs{$fhem_dev}{FHEMPYTYPE}) && $main::defs{$fhem_dev}{FHEMPYTYPE} eq 'tuya' && $main::defs{$fhem_dev}{DEVICEID} eq 'bf881b7977c814af88jmrc');;}return 0;;
2023.02.02 10:37:43 1: BindingsIo (local_pybinding): Use of uninitialized value in string eq at (eval 1551) line 1.
=> COMMAND: foreach my $fhem_dev (sort keys %main::defs) { return 1 if(defined($main::defs{$fhem_dev}{FHEMPYTYPE}) && $main::defs{$fhem_dev}{FHEMPYTYPE} eq 'tuya' && $main::defs{$fhem_dev}{DEVICEID} eq 'bf881b7977c814af88jmrc');;}return 0;;
2023.02.02 10:37:43 1: BindingsIo (local_pybinding): Use of uninitialized value in string eq at (eval 1551) line 1.
=> COMMAND: foreach my $fhem_dev (sort keys %main::defs) { return 1 if(defined($main::defs{$fhem_dev}{FHEMPYTYPE}) && $main::defs{$fhem_dev}{FHEMPYTYPE} eq 'tuya' && $main::defs{$fhem_dev}{DEVICEID} eq 'bf881b7977c814af88jmrc');;}return 0;;
2023.02.02 10:37:43 1: BindingsIo (local_pybinding): Use of uninitialized value in string eq at (eval 1551) line 1.
=> COMMAND: foreach my $fhem_dev (sort keys %main::defs) { return 1 if(defined($main::defs{$fhem_dev}{FHEMPYTYPE}) && $main::defs{$fhem_dev}{FHEMPYTYPE} eq 'tuya' && $main::defs{$fhem_dev}{DEVICEID} eq 'bf881b7977c814af88jmrc');;}return 0;;
2023.02.02 10:37:43 1: BindingsIo (local_pybinding): Use of uninitialized value in string eq at (eval 1551) line 1.
=> COMMAND: foreach my $fhem_dev (sort keys %main::defs) { return 1 if(defined($main::defs{$fhem_dev}{FHEMPYTYPE}) && $main::defs{$fhem_dev}{FHEMPYTYPE} eq 'tuya' && $main::defs{$fhem_dev}{DEVICEID} eq 'bf881b7977c814af88jmrc');;}return 0;;
2023.02.02 10:37:43 1: BindingsIo (local_pybinding): Use of uninitialized value in string eq at (eval 1551) line 1.
=> COMMAND: foreach my $fhem_dev (sort keys %main::defs) { return 1 if(defined($main::defs{$fhem_dev}{FHEMPYTYPE}) && $main::defs{$fhem_dev}{FHEMPYTYPE} eq 'tuya' && $main::defs{$fhem_dev}{DEVICEID} eq 'bf881b7977c814af88jmrc');;}return 0;;
2023.02.02 10:37:43 1: BindingsIo (local_pybinding): Use of uninitialized value in string eq at (eval 1551) line 1.
=> COMMAND: foreach my $fhem_dev (sort keys %main::defs) { return 1 if(defined($main::defs{$fhem_dev}{FHEMPYTYPE}) && $main::defs{$fhem_dev}{FHEMPYTYPE} eq 'tuya' && $main::defs{$fhem_dev}{DEVICEID} eq 'bf881b7977c814af88jmrc');;}return 0;;
2023.02.02 10:37:44 1: readingsUpdate(Stefan_Tablet_bf0572e0fb6ccbe356ykuh,active_time,1638460188) missed to call readingsBeginUpdate first.
2023.02.02 10:37:44 1: stacktrace:
2023.02.02 10:37:44 1: main::readingsBulkUpdate called by (eval 1559) (1)
2023.02.02 10:37:44 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:44 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:44 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:37:44 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:37:44 1: main::IOWrite called by ./FHEM/10_fhempy.pm (65)
2023.02.02 10:37:44 1: main::fhempy_Define called by fhem.pl (3976)
2023.02.02 10:37:44 1: main::CallFn called by fhem.pl (2155)
2023.02.02 10:37:44 1: main::CommandDefine called by (eval 1558) (1)
2023.02.02 10:37:44 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:44 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:44 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:44 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:44 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:44 1: readingsUpdate(tuya_cloud_bffa550a829a269630vhcn,active_time,1674825254) missed to call readingsBeginUpdate first.
2023.02.02 10:37:44 1: stacktrace:
2023.02.02 10:37:44 1: main::readingsBulkUpdate called by (eval 1560) (1)
2023.02.02 10:37:44 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:44 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:44 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:37:44 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:37:44 1: main::IOWrite called by ./FHEM/10_fhempy.pm (65)
2023.02.02 10:37:44 1: main::fhempy_Define called by fhem.pl (3976)
2023.02.02 10:37:44 1: main::CallFn called by fhem.pl (2155)
2023.02.02 10:37:44 1: main::CommandDefine called by (eval 1558) (1)
2023.02.02 10:37:44 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:44 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:44 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:44 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:44 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:44 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,active_time,1638468323) missed to call readingsBeginUpdate first.
2023.02.02 10:37:44 1: stacktrace:
2023.02.02 10:37:44 1: main::readingsBulkUpdate called by (eval 1561) (1)
2023.02.02 10:37:44 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:44 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:44 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:37:44 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:37:44 1: main::IOWrite called by ./FHEM/10_fhempy.pm (65)
2023.02.02 10:37:44 1: main::fhempy_Define called by fhem.pl (3976)
2023.02.02 10:37:44 1: main::CallFn called by fhem.pl (2155)
2023.02.02 10:37:44 1: main::CommandDefine called by (eval 1558) (1)
2023.02.02 10:37:44 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:44 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:44 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:44 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:44 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:44 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE $/ at ./FHEM/33_readingsGroup.pm line 154.
=> COMMAND: CommandDefine(undef, "tuya_cloud_bf881b7977c814af88jmrc fhempy tuya_cloud tuya_cloud_connector bf881b7977c814af88jmrc")
2023.02.02 10:37:44 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE $/ at ./FHEM/33_readingsGroup.pm line 160.
=> COMMAND: CommandDefine(undef, "tuya_cloud_bf881b7977c814af88jmrc fhempy tuya_cloud tuya_cloud_connector bf881b7977c814af88jmrc")
2023.02.02 10:37:45 1: readingsUpdate(Stefan_Tablet_bf0572e0fb6ccbe356ykuh,biz_type,0) missed to call readingsBeginUpdate first.
2023.02.02 10:37:45 1: stacktrace:
2023.02.02 10:37:45 1: main::readingsBulkUpdate called by (eval 1591) (1)
2023.02.02 10:37:45 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:45 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:45 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:45 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:45 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:45 1: readingsUpdate(tuya_cloud_bffa550a829a269630vhcn,biz_type,0) missed to call readingsBeginUpdate first.
2023.02.02 10:37:45 1: stacktrace:
2023.02.02 10:37:45 1: main::readingsBulkUpdate called by (eval 1593) (1)
2023.02.02 10:37:45 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:45 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:45 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:45 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:45 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:45 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,biz_type,0) missed to call readingsBeginUpdate first.
2023.02.02 10:37:45 1: stacktrace:
2023.02.02 10:37:45 1: main::readingsBulkUpdate called by (eval 1594) (1)
2023.02.02 10:37:45 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:45 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:45 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:45 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:45 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:45 1: readingsUpdate(Stefan_Tablet_bf0572e0fb6ccbe356ykuh,category,cz) missed to call readingsBeginUpdate first.
2023.02.02 10:37:45 1: stacktrace:
2023.02.02 10:37:45 1: main::readingsBulkUpdate called by (eval 1600) (1)
2023.02.02 10:37:45 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:45 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:45 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:45 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:45 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:45 1: readingsUpdate(tuya_cloud_bffa550a829a269630vhcn,category,wsdcg) missed to call readingsBeginUpdate first.
2023.02.02 10:37:45 1: stacktrace:
2023.02.02 10:37:45 1: main::readingsBulkUpdate called by (eval 1602) (1)
2023.02.02 10:37:45 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:45 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:45 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:45 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:45 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:45 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,category,cz) missed to call readingsBeginUpdate first.
2023.02.02 10:37:45 1: stacktrace:
2023.02.02 10:37:45 1: main::readingsBulkUpdate called by (eval 1603) (1)
2023.02.02 10:37:45 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:45 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:45 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:45 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:45 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:45 1: readingsUpdate(Stefan_Tablet_bf0572e0fb6ccbe356ykuh,create_time,1638459915) missed to call readingsBeginUpdate first.
2023.02.02 10:37:45 1: stacktrace:
2023.02.02 10:37:45 1: main::readingsBulkUpdate called by (eval 1607) (1)
2023.02.02 10:37:45 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:45 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:45 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:37:45 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:37:45 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.02 10:37:45 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.02 10:37:45 1: main::CallFn called by fhem.pl (3198)
2023.02.02 10:37:45 1: main::CommandAttr called by (eval 1604) (1)
2023.02.02 10:37:45 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:45 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:45 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:45 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:45 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:45 1: readingsUpdate(tuya_cloud_bffa550a829a269630vhcn,create_time,1674825254) missed to call readingsBeginUpdate first.
2023.02.02 10:37:45 1: stacktrace:
2023.02.02 10:37:45 1: main::readingsBulkUpdate called by (eval 1608) (1)
2023.02.02 10:37:45 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:45 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:45 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:37:45 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:37:45 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.02 10:37:45 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.02 10:37:45 1: main::CallFn called by fhem.pl (3198)
2023.02.02 10:37:45 1: main::CommandAttr called by (eval 1604) (1)
2023.02.02 10:37:45 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:45 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:45 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:45 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:45 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:45 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,create_time,1638468323) missed to call readingsBeginUpdate first.
2023.02.02 10:37:45 1: stacktrace:
2023.02.02 10:37:45 1: main::readingsBulkUpdate called by (eval 1609) (1)
2023.02.02 10:37:45 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:45 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:45 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:37:45 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:37:45 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.02 10:37:45 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.02 10:37:45 1: main::CallFn called by fhem.pl (3198)
2023.02.02 10:37:45 1: main::CommandAttr called by (eval 1604) (1)
2023.02.02 10:37:45 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:45 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:45 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:45 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:45 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:45 1: readingsUpdate(Stefan_Tablet_bf0572e0fb6ccbe356ykuh,icon,https://images.tuyaeu.com/smart/icon/ay15422864509092y6k8/94efe8972e318399f1a1ee3887c704e8.png) missed to call readingsBeginUpdate first.
2023.02.02 10:37:45 1: stacktrace:
2023.02.02 10:37:45 1: main::readingsBulkUpdate called by (eval 1616) (1)
2023.02.02 10:37:45 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:45 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:45 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:37:45 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:37:45 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.02 10:37:45 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.02 10:37:45 1: main::CallFn called by fhem.pl (1954)
2023.02.02 10:37:45 1: main::DoSet called by fhem.pl (1996)
2023.02.02 10:37:45 1: main::CommandSet called by fhem.pl (2904)
2023.02.02 10:37:45 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.02 10:37:45 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.02 10:37:45 1: main::FW_Notify called by fhem.pl (3976)
2023.02.02 10:37:45 1: main::CallFn called by fhem.pl (3888)
2023.02.02 10:37:45 1: main::DoTrigger called by fhem.pl (4995)
2023.02.02 10:37:45 1: main::readingsEndUpdate called by (eval 1615) (1)
2023.02.02 10:37:45 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:45 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:45 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:37:45 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:37:45 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.02 10:37:45 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.02 10:37:45 1: main::CallFn called by fhem.pl (3198)
2023.02.02 10:37:45 1: main::CommandAttr called by (eval 1614) (1)
2023.02.02 10:37:45 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:45 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:45 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:45 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:45 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:45 1: readingsUpdate(tuya_cloud_bffa550a829a269630vhcn,icon,https://images.tuyaeu.com/smart/icon/ay1525749833414yotNt/b3a94a9431b68373894805b4a19092e4.png) missed to call readingsBeginUpdate first.
2023.02.02 10:37:45 1: stacktrace:
2023.02.02 10:37:45 1: main::readingsBulkUpdate called by (eval 1617) (1)
2023.02.02 10:37:45 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:45 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:45 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:37:45 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:37:45 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.02 10:37:45 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.02 10:37:45 1: main::CallFn called by fhem.pl (1954)
2023.02.02 10:37:45 1: main::DoSet called by fhem.pl (1996)
2023.02.02 10:37:45 1: main::CommandSet called by fhem.pl (2904)
2023.02.02 10:37:45 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.02 10:37:45 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.02 10:37:45 1: main::FW_Notify called by fhem.pl (3976)
2023.02.02 10:37:45 1: main::CallFn called by fhem.pl (3888)
2023.02.02 10:37:45 1: main::DoTrigger called by fhem.pl (4995)
2023.02.02 10:37:45 1: main::readingsEndUpdate called by (eval 1615) (1)
2023.02.02 10:37:45 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:45 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:45 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:37:45 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:37:45 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.02 10:37:45 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.02 10:37:45 1: main::CallFn called by fhem.pl (3198)
2023.02.02 10:37:45 1: main::CommandAttr called by (eval 1614) (1)
2023.02.02 10:37:45 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:45 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:45 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:45 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:45 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:45 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,icon,https://images.tuyaeu.com/smart/icon/ay15148582002916nitB/c58a91c23c2e2b5309c7c5d776871390.png) missed to call readingsBeginUpdate first.
2023.02.02 10:37:45 1: stacktrace:
2023.02.02 10:37:45 1: main::readingsBulkUpdate called by (eval 1618) (1)
2023.02.02 10:37:45 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:45 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:45 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:37:45 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:37:45 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.02 10:37:45 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.02 10:37:45 1: main::CallFn called by fhem.pl (1954)
2023.02.02 10:37:45 1: main::DoSet called by fhem.pl (1996)
2023.02.02 10:37:45 1: main::CommandSet called by fhem.pl (2904)
2023.02.02 10:37:45 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.02 10:37:45 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.02 10:37:45 1: main::FW_Notify called by fhem.pl (3976)
2023.02.02 10:37:45 1: main::CallFn called by fhem.pl (3888)
2023.02.02 10:37:45 1: main::DoTrigger called by fhem.pl (4995)
2023.02.02 10:37:45 1: main::readingsEndUpdate called by (eval 1615) (1)
2023.02.02 10:37:45 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:45 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:45 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:37:45 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:37:45 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.02 10:37:45 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.02 10:37:45 1: main::CallFn called by fhem.pl (3198)
2023.02.02 10:37:45 1: main::CommandAttr called by (eval 1614) (1)
2023.02.02 10:37:45 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:45 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:45 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:45 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:45 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:46 1: readingsUpdate(Stefan_Tablet_bf0572e0fb6ccbe356ykuh,id,bf0572e0fb6ccbe356ykuh) missed to call readingsBeginUpdate first.
2023.02.02 10:37:46 1: stacktrace:
2023.02.02 10:37:46 1: main::readingsBulkUpdate called by (eval 1624) (1)
2023.02.02 10:37:46 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:46 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:46 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:46 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:46 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:46 1: readingsUpdate(tuya_cloud_bffa550a829a269630vhcn,id,bffa550a829a269630vhcn) missed to call readingsBeginUpdate first.
2023.02.02 10:37:46 1: stacktrace:
2023.02.02 10:37:46 1: main::readingsBulkUpdate called by (eval 1625) (1)
2023.02.02 10:37:46 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:46 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:46 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:46 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:46 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:46 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,id,bf68d9b41c16be3713vcc1) missed to call readingsBeginUpdate first.
2023.02.02 10:37:46 1: stacktrace:
2023.02.02 10:37:46 1: main::readingsBulkUpdate called by (eval 1626) (1)
2023.02.02 10:37:46 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:46 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:46 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:46 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:46 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:46 1: readingsUpdate(Stefan_Tablet_bf0572e0fb6ccbe356ykuh,ip,87.158.205.193) missed to call readingsBeginUpdate first.
2023.02.02 10:37:46 1: stacktrace:
2023.02.02 10:37:46 1: main::readingsBulkUpdate called by (eval 1629) (1)
2023.02.02 10:37:46 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:46 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:46 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:37:46 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:37:46 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.02 10:37:46 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.02 10:37:46 1: main::CallFn called by fhem.pl (3198)
2023.02.02 10:37:46 1: main::CommandAttr called by (eval 1627) (1)
2023.02.02 10:37:46 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:46 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:46 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:46 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:46 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:46 1: readingsUpdate(tuya_cloud_bffa550a829a269630vhcn,ip,84.188.243.243) missed to call readingsBeginUpdate first.
2023.02.02 10:37:46 1: stacktrace:
2023.02.02 10:37:46 1: main::readingsBulkUpdate called by (eval 1630) (1)
2023.02.02 10:37:46 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:46 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:46 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:37:46 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:37:46 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.02 10:37:46 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.02 10:37:46 1: main::CallFn called by fhem.pl (3198)
2023.02.02 10:37:46 1: main::CommandAttr called by (eval 1627) (1)
2023.02.02 10:37:46 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:46 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:46 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:46 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:46 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:46 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,ip,87.158.205.193) missed to call readingsBeginUpdate first.
2023.02.02 10:37:46 1: stacktrace:
2023.02.02 10:37:46 1: main::readingsBulkUpdate called by (eval 1631) (1)
2023.02.02 10:37:46 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:46 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:46 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:37:46 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:37:46 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.02 10:37:46 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.02 10:37:46 1: main::CallFn called by fhem.pl (3198)
2023.02.02 10:37:46 1: main::CommandAttr called by (eval 1627) (1)
2023.02.02 10:37:46 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:46 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:46 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:46 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:46 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:46 1: readingsUpdate(Stefan_Tablet_bf0572e0fb6ccbe356ykuh,lat,49.6104) missed to call readingsBeginUpdate first.
2023.02.02 10:37:46 1: stacktrace:
2023.02.02 10:37:46 1: main::readingsBulkUpdate called by (eval 1632) (1)
2023.02.02 10:37:46 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:46 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:46 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:46 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:46 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:46 1: readingsUpdate(tuya_cloud_bffa550a829a269630vhcn,lat,49.6104) missed to call readingsBeginUpdate first.
2023.02.02 10:37:46 1: stacktrace:
2023.02.02 10:37:46 1: main::readingsBulkUpdate called by (eval 1633) (1)
2023.02.02 10:37:46 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:46 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:46 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:46 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:46 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:46 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,lat,49.6104) missed to call readingsBeginUpdate first.
2023.02.02 10:37:46 1: stacktrace:
2023.02.02 10:37:46 1: main::readingsBulkUpdate called by (eval 1665) (1)
2023.02.02 10:37:46 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:46 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:46 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:46 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:46 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:46 1: readingsUpdate(Stefan_Tablet_bf0572e0fb6ccbe356ykuh,local_key,b4ca4d3e6b518fd1) missed to call readingsBeginUpdate first.
2023.02.02 10:37:46 1: stacktrace:
2023.02.02 10:37:46 1: main::readingsBulkUpdate called by (eval 1668) (1)
2023.02.02 10:37:46 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:46 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:46 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:37:46 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:37:46 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.02 10:37:46 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.02 10:37:46 1: main::CallFn called by fhem.pl (3198)
2023.02.02 10:37:46 1: main::CommandAttr called by (eval 1666) (1)
2023.02.02 10:37:46 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:46 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:46 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:46 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:46 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:46 1: readingsUpdate(tuya_cloud_bffa550a829a269630vhcn,local_key,55db39dd00af9487) missed to call readingsBeginUpdate first.
2023.02.02 10:37:46 1: stacktrace:
2023.02.02 10:37:46 1: main::readingsBulkUpdate called by (eval 1669) (1)
2023.02.02 10:37:46 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:46 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:46 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:37:46 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:37:46 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.02 10:37:46 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.02 10:37:46 1: main::CallFn called by fhem.pl (3198)
2023.02.02 10:37:46 1: main::CommandAttr called by (eval 1666) (1)
2023.02.02 10:37:46 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:46 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:46 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:46 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:46 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:46 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,local_key,68c71bfc9491dabc) missed to call readingsBeginUpdate first.
2023.02.02 10:37:46 1: stacktrace:
2023.02.02 10:37:46 1: main::readingsBulkUpdate called by (eval 1670) (1)
2023.02.02 10:37:46 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:46 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:46 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:37:46 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:37:46 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.02 10:37:46 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.02 10:37:46 1: main::CallFn called by fhem.pl (3198)
2023.02.02 10:37:46 1: main::CommandAttr called by (eval 1666) (1)
2023.02.02 10:37:46 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:46 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:46 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:46 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:46 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:46 1: readingsUpdate(Stefan_Tablet_bf0572e0fb6ccbe356ykuh,lon,8.7262) missed to call readingsBeginUpdate first.
2023.02.02 10:37:46 1: stacktrace:
2023.02.02 10:37:46 1: main::readingsBulkUpdate called by (eval 1676) (1)
2023.02.02 10:37:46 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:46 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:46 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:46 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:46 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:46 1: readingsUpdate(tuya_cloud_bffa550a829a269630vhcn,lon,8.7263) missed to call readingsBeginUpdate first.
2023.02.02 10:37:46 1: stacktrace:
2023.02.02 10:37:46 1: main::readingsBulkUpdate called by (eval 1677) (1)
2023.02.02 10:37:46 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:46 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:46 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:46 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:46 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:46 1: readingsUpdate(Sybille_Tablet_bf68d9b41c16be3713vcc1,lon,8.7261) missed to call readingsBeginUpdate first.
2023.02.02 10:37:46 1: stacktrace:
2023.02.02 10:37:46 1: main::readingsBulkUpdate called by (eval 1678) (1)
2023.02.02 10:37:46 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:46 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:46 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:46 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:37:46 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:37:46 1: readingsUpdate(Stefan_Tablet_bf0572e0fb6ccbe356ykuh,model,0942 CB2S) missed to call readingsBeginUpdate first.
2023.02.02 10:37:46 1: stacktrace:
2023.02.02 10:37:46 1: main::readingsBulkUpdate called by (eval 1685) (1)
2023.02.02 10:37:46 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:37:46 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:37:46 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:37:46 1: main::BindingsIo_Read called by fhem.pl (3976)
Zitat von: stefanru am 02 Februar 2023, 10:45:42
Hi,
habe das Update auch gemacht und nun neue Fehler beim Neustart und auch alt bekannt.
Insgesammt nochmal einiges mehr an Fehlern.
Der fhempyserver stürzt nun regelmäßig ab :-(
Leider komme ich gerade nicht an das fhempy.log.
auch bei mir hat das log nicht in code gepasst
Letzte Zeile löschen und /code setzen.
PerformanceProbleme?
Der Start dauert eben 20 Minuten; seit 10:16 keine log einträge im fhemlog.
Der Raum fhempy ist immer noch nicht aufgebaut (nach 50 min) Darstellund ist nun Seitenbreit
Ok nach noch einem Neustart ist es jetzt ok.
Verstehe ncht warum ich 2 x starten musste ohne Änderung zwischen drin.
Diese Fehler sind nun verschwunden:
2023.02.02 10:37:43 1: BindingsIo (local_pybinding): Use of uninitialized value in string eq at (eval 1519) line 1.
=> COMMAND: foreach my $fhem_dev (sort keys %main::defs) { return 1 if(defined($main::defs{$fhem_dev}{FHEMPYTYPE}) && $main::defs{$fhem_dev}{FHEMPYTYPE} eq 'tuya_cloud' && $main::defs{$fhem_dev}{DEVICEID} eq 'bffa550a829a269630vhcn');;}return 0;;
Es läuft performant, Daten kommen.
Leider gibt es beim Start immer noch seitenweise diese Fehlermeldungen.
Es gibt 3 Arten die beim Start kommen, insgesamt unheimlich viele!
Zuerst diese:
2023.02.02 10:57:56 1: readingsUpdate(tuya_cloud_bffa550a829a269630vhcn,active_time,1674825254) missed to call readingsBeginUpdate first.
2023.02.02 10:57:56 1: stacktrace:
2023.02.02 10:57:56 1: main::readingsBulkUpdate called by (eval 1463) (1)
2023.02.02 10:57:56 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:57:56 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:57:56 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:57:56 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:57:56 1: main::CallFn called by fhem.pl (784)
2023.02.02 10:57:56 1: readingsUpdate(tuya_cloud_bf4f644bc7dd2fc71d9q52,active_time,1638458218) missed to call readingsBeginUpdate first.
Danach diese:
2023.02.02 10:58:03 1: readingsUpdate(tuya_cloud_bffa550a829a269630vhcn,time_zone,+01:00) missed to call readingsBeginUpdate first.
2023.02.02 10:58:03 1: stacktrace:
2023.02.02 10:58:03 1: main::readingsBulkUpdate called by (eval 2097) (1)
2023.02.02 10:58:03 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:58:03 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:58:03 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:58:03 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:58:03 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.02 10:58:03 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.02 10:58:03 1: main::CallFn called by fhem.pl (1954)
2023.02.02 10:58:03 1: main::DoSet called by fhem.pl (1996)
2023.02.02 10:58:03 1: main::CommandSet called by fhem.pl (2904)
2023.02.02 10:58:03 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.02 10:58:03 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.02 10:58:03 1: main::FW_Notify called by fhem.pl (3976)
2023.02.02 10:58:03 1: main::CallFn called by fhem.pl (3888)
2023.02.02 10:58:03 1: main::DoTrigger called by fhem.pl (4995)
2023.02.02 10:58:03 1: main::readingsEndUpdate called by (eval 2082) (1)
2023.02.02 10:58:03 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:58:03 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:58:03 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:58:03 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:58:03 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.02 10:58:03 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.02 10:58:03 1: main::CallFn called by fhem.pl (1954)
2023.02.02 10:58:03 1: main::DoSet called by fhem.pl (1996)
2023.02.02 10:58:03 1: main::CommandSet called by fhem.pl (2904)
2023.02.02 10:58:03 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.02 10:58:03 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.02 10:58:03 1: main::FW_Notify called by fhem.pl (3976)
2023.02.02 10:58:03 1: main::CallFn called by fhem.pl (3888)
2023.02.02 10:58:03 1: main::DoTrigger called by fhem.pl (4995)
2023.02.02 10:58:03 1: main::readingsEndUpdate called by (eval 2070) (1)
2023.02.02 10:58:03 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:58:03 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:58:03 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 10:58:03 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 10:58:03 1: main::CallFn called by fhem.pl (784)
Und dann noch mal ein Schwung von diesen:
2023.02.02 10:58:04 1: readingsUpdate(tuya_cloud_bffa550a829a269630vhcn,update_time_hr,27.01.2023, 14:14:17) missed to call readingsBeginUpdate first.
2023.02.02 10:58:04 1: stacktrace:
2023.02.02 10:58:04 1: main::readingsBulkUpdate called by fhem.pl (4980)
2023.02.02 10:58:04 1: main::readingsEndUpdate called by (eval 2176) (1)
2023.02.02 10:58:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:58:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:58:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:58:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:58:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.02 10:58:04 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.02 10:58:04 1: main::CallFn called by fhem.pl (1954)
2023.02.02 10:58:04 1: main::DoSet called by fhem.pl (1996)
2023.02.02 10:58:04 1: main::CommandSet called by fhem.pl (2904)
2023.02.02 10:58:04 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.02 10:58:04 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.02 10:58:04 1: main::FW_Notify called by fhem.pl (3976)
2023.02.02 10:58:04 1: main::CallFn called by fhem.pl (3888)
2023.02.02 10:58:04 1: main::DoTrigger called by fhem.pl (4995)
2023.02.02 10:58:04 1: main::readingsEndUpdate called by (eval 2173) (1)
2023.02.02 10:58:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:58:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:58:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:58:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:58:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.02 10:58:04 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.02 10:58:04 1: main::CallFn called by fhem.pl (1954)
2023.02.02 10:58:04 1: main::DoSet called by fhem.pl (1996)
2023.02.02 10:58:04 1: main::CommandSet called by fhem.pl (2904)
2023.02.02 10:58:04 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.02 10:58:04 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.02 10:58:04 1: main::FW_Notify called by fhem.pl (3976)
2023.02.02 10:58:04 1: main::CallFn called by fhem.pl (3888)
2023.02.02 10:58:04 1: main::DoTrigger called by fhem.pl (4995)
2023.02.02 10:58:04 1: main::readingsEndUpdate called by (eval 2169) (1)
2023.02.02 10:58:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 10:58:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 10:58:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 10:58:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 10:58:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.02 10:58:04 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.02 10:58:04 1: main::CallFn called by fhem.pl (1954)
2023.02.02 10:58:04 1: main::DoSet called by fhem.pl (1996)
2023.02.02 10:58:04 1: main::CommandSet called by fhem.pl (2904)
2023.02.02 10:58:04 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.02 10:58:04 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.02 10:58:04 1: main::FW_Notify called by fhem.pl (3976)
2023.02.02 10:58:04 1: main::CallFn called by fhem.pl (3888)
2023.02.02 10:58:04 1: main::DoTrigger called by fhem.pl (4995)
2023.02.02 10:58:04 1: main::readingsEndUpdate called by (eval 2167) (1)
2023.02.02 10:58:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
Danke und Gruß,
Stefan
nach zwei Stunden weitere Bewegungen in der FHEL-log:
2023.02.02 10:16:40 1: main::CallFn called by fhem.pl (784)
2023.02.02 12:10:05 3: Watchdog WDT_BAD_F2 triggered
2023.02.02 12:17:09 3: Watchdog WDT_HWR_F2 triggered
2023.02.02 12:20:53 1: readingsUpdate(tuya_cloud_260064612cf432ca55d8,state,on) missed to call readingsBeginUpdate first.
2023.02.02 12:20:53 1: stacktrace:
2023.02.02 12:20:53 1: main::readingsBulkUpdate called by (eval 211684) (1)
2023.02.02 12:20:53 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 12:20:53 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 12:20:53 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 12:20:53 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 12:20:53 1: main::CallFn called by fhem.pl (784)
2023.02.02 12:20:54 1: readingsUpdate(tuya_cloud_260064612cf432ca55d8,countdown_1,0.0) missed to call readingsBeginUpdate first.
2023.02.02 12:20:54 1: stacktrace:
2023.02.02 12:20:54 1: main::readingsBulkUpdate called by (eval 211689) (1)
2023.02.02 12:20:54 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 12:20:54 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 12:20:54 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 12:20:54 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 12:20:54 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.02 12:20:54 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.02 12:20:54 1: main::CallFn called by fhem.pl (1954)
2023.02.02 12:20:54 1: main::DoSet called by fhem.pl (1996)
2023.02.02 12:20:54 1: main::CommandSet called by fhem.pl (2904)
2023.02.02 12:20:54 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.02 12:20:54 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.02 12:20:54 1: main::FW_Notify called by fhem.pl (3976)
2023.02.02 12:20:54 1: main::CallFn called by fhem.pl (3888)
2023.02.02 12:20:54 1: main::DoTrigger called by fhem.pl (4995)
2023.02.02 12:20:54 1: main::readingsEndUpdate called by (eval 211687) (1)
2023.02.02 12:20:54 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 12:20:54 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 12:20:54 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 12:20:54 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 12:20:54 1: main::CallFn called by fhem.pl (784)
2023.02.02 12:20:54 1: readingsUpdate(tuya_cloud_260064612cf432ca55d8,add_ele,0.1) missed to call readingsBeginUpdate first.
2023.02.02 12:20:54 1: stacktrace:
2023.02.02 12:20:54 1: main::readingsBulkUpdate called by (eval 211693) (1)
2023.02.02 12:20:54 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 12:20:54 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 12:20:54 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 12:20:54 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 12:20:54 1: main::CallFn called by fhem.pl (784)
2023.02.02 12:20:54 1: readingsUpdate(tuya_cloud_260064612cf432ca55d8,cur_current,4278.0) missed to call readingsBeginUpdate first.
2023.02.02 12:20:54 1: stacktrace:
2023.02.02 12:20:54 1: main::readingsBulkUpdate called by (eval 211697) (1)
2023.02.02 12:20:54 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 12:20:54 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 12:20:54 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 12:20:54 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 12:20:54 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.02 12:20:54 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.02 12:20:54 1: main::CallFn called by fhem.pl (1954)
2023.02.02 12:20:54 1: main::DoSet called by fhem.pl (1996)
2023.02.02 12:20:54 1: main::CommandSet called by fhem.pl (2904)
2023.02.02 12:20:54 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.02 12:20:54 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.02 12:20:54 1: main::FW_Notify called by fhem.pl (3976)
2023.02.02 12:20:54 1: main::CallFn called by fhem.pl (3888)
2023.02.02 12:20:54 1: main::DoTrigger called by fhem.pl (4995)
2023.02.02 12:20:54 1: main::readingsEndUpdate called by (eval 211696) (1)
2023.02.02 12:20:54 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 12:20:54 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 12:20:54 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 12:20:54 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 12:20:54 1: main::CallFn called by fhem.pl (784)
2023.02.02 12:20:54 1: readingsUpdate(tuya_cloud_260064612cf432ca55d8,cur_power,288.4) missed to call readingsBeginUpdate first.
2023.02.02 12:20:54 1: stacktrace:
2023.02.02 12:20:54 1: main::readingsBulkUpdate called by (eval 211701) (1)
2023.02.02 12:20:54 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 12:20:54 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 12:20:54 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 12:20:54 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 12:20:54 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.02 12:20:54 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.02 12:20:54 1: main::CallFn called by fhem.pl (1954)
2023.02.02 12:20:54 1: main::DoSet called by fhem.pl (1996)
2023.02.02 12:20:54 1: main::CommandSet called by fhem.pl (2904)
2023.02.02 12:20:54 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.02 12:20:54 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.02 12:20:54 1: main::FW_Notify called by fhem.pl (3976)
2023.02.02 12:20:54 1: main::CallFn called by fhem.pl (3888)
2023.02.02 12:20:54 1: main::DoTrigger called by fhem.pl (4995)
2023.02.02 12:20:54 1: main::readingsEndUpdate called by (eval 211699) (1)
2023.02.02 12:20:54 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 12:20:54 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 12:20:54 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 12:20:54 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 12:20:54 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.02 12:20:54 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.02 12:20:54 1: main::CallFn called by fhem.pl (1954)
2023.02.02 12:20:54 1: main::DoSet called by fhem.pl (1996)
2023.02.02 12:20:54 1: main::CommandSet called by fhem.pl (2904)
2023.02.02 12:20:54 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.02 12:20:54 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.02 12:20:54 1: main::FW_Notify called by fhem.pl (3976)
2023.02.02 12:20:54 1: main::CallFn called by fhem.pl (3888)
2023.02.02 12:20:54 1: main::DoTrigger called by fhem.pl (4995)
2023.02.02 12:20:54 1: main::readingsEndUpdate called by (eval 211698) (1)
2023.02.02 12:20:54 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 12:20:54 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 12:20:54 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.02 12:20:54 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.02 12:20:54 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.02 12:20:54 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.02 12:20:54 1: main::CallFn called by fhem.pl (1954)
2023.02.02 12:20:54 1: main::DoSet called by fhem.pl (1996)
2023.02.02 12:20:54 1: main::CommandSet called by fhem.pl (2904)
2023.02.02 12:20:54 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.02 12:20:54 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.02 12:20:54 1: main::FW_Notify called by fhem.pl (3976)
2023.02.02 12:20:54 1: main::CallFn called by fhem.pl (3888)
2023.02.02 12:20:54 1: main::DoTrigger called by fhem.pl (4995)
2023.02.02 12:20:54 1: main::readingsEndUpdate called by (eval 211696) (1)
2023.02.02 12:20:54 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 12:20:54 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 12:20:54 1: readingsUpdate(tuya_cloud_260064612cf432ca55d8,cur_voltage,229.8) missed to call readingsBeginUpdate first.
2023.02.02 12:20:54 1: stacktrace:
2023.02.02 12:20:54 1: main::readingsBulkUpdate called by (eval 211703) (1)
2023.02.02 12:20:54 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.02 12:20:54 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (688)
2023.02.02 12:20:54 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.02 12:20:54 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.02 12:20:54 1: main::CallFn called by fhem.pl (784)
room FMEMPY brauch ca. 5 min zum Aufbau
in FHEMPY-Log hersch allerdings weitgehen Ruhe:
2023-02-02 10:15:32,296 - ERROR - root: tuya_cloud_00673231e09806cb6fa5: readingsBulkUpdate without readingsBeginUpdate: readingsBulkUpdate($defs{'tuya_cloud_00673231e09806cb6fa5'},'cur_voltage','230.3');;
2023-02-02 10:15:32,297 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_00673231e09806cb6fa5'},'add_ele','0.006');;
2023-02-02 10:15:32,297 - ERROR - root: tuya_cloud_00673231e09806cb6fa5: readingsBulkUpdate without readingsBeginUpdate: readingsBulkUpdate($defs{'tuya_cloud_00673231e09806cb6fa5'},'cur_current','116.0');;
2023-02-02 10:15:32,297 - ERROR - root: tuya_cloud_00673231e09806cb6fa5: readingsBulkUpdate without readingsBeginUpdate: readingsBulkUpdate($defs{'tuya_cloud_00673231e09806cb6fa5'},'cur_power','12.2');;
2023-02-02 10:15:32,298 - ERROR - root: tuya_cloud_00673231e09806cb6fa5: readingsBulkUpdate without readingsBeginUpdate: readingsBulkUpdate($defs{'tuya_cloud_00673231e09806cb6fa5'},'cur_voltage','230.3');;
2023-02-02 10:15:55,827 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_63667231dc4f22f329f1'},'sub','off');;
2023-02-02 10:16:09,601 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_2053863070039f16cebe'},'lat','48.5585');;
2023-02-02 10:16:09,601 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP11'},'dp_22','715');;
2023-02-02 10:16:09,601 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP15'},'dp_25','995');;
2023-02-02 10:16:09,602 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_50134218c4dd571b3390'},'countdown_3','0.0');;
2023-02-02 10:16:13,840 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_8877821724a160151069'},'model','欧è§,,，10A，带计ç"µé‡ï¼Œæ"¯æŒé...·å®¢RF产测');;
2023-02-02 10:16:13,953 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP10'},'dp_22','722');;
2023-02-02 10:16:13,954 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_00673231e09806cb188e'},'state','on');;
2023-02-02 10:16:20,831 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_8877821724a16014ef14'},'ip','149.172.226.177');;
2023-02-02 10:16:25,669 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_067327848cce4ec3fe13'},'create_time','1606310994');;
2023-02-02 10:16:25,669 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_04086463840d8e50124b'},'switch_3','on');;
2023-02-02 10:16:25,670 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL33'},'dp_07','0');;
2023-02-02 10:16:25,670 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_PS2'},'countdown_2','0.0');;
2023-02-02 10:16:25,671 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL27'},'dp_07','0');;
2023-02-02 10:16:25,672 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP05'},'cur_voltage','210.1');;
2023-02-02 10:16:25,675 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP02'},'cur_voltage','231.7');;
2023-02-02 10:16:25,676 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP03'},'cur_voltage','211.5');;
2023-02-02 10:16:25,678 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP07'},'cur_voltage','225.3');;
2023-02-02 10:16:25,682 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP09'},'cur_voltage','230.4');;
2023-02-02 10:16:38,865 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'TUYA_JL26'});;
2023-02-02 10:16:38,865 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL29'},'cur_voltage','230.4');;
2023-02-02 10:16:38,865 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL24'},'switch_1','on');;
2023-02-02 10:16:38,866 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_bfe1b5bb54592232acz7dg'},'va_humidity','78.0');;
2023-02-02 10:16:38,866 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_PS3', 'dp_104', '')
2023-02-02 10:16:38,866 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_MMG', 'dp_34', '')
2023-02-02 10:16:38,866 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_bffb7d9839e65fcdeciaqn'},'state','normal');;
2023-02-02 10:16:38,984 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP01'},'switch_1','on');;
2023-02-02 10:16:38,985 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_453005615002911e00b4'},'state','on');;
2023-02-02 10:16:38,985 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_00673231e09806cb188e'},'add_ele','0.002');;
2023-02-02 10:16:38,985 - ERROR - root: tuya_cloud_00673231e09806cb188e: readingsBulkUpdate without readingsBeginUpdate: readingsBulkUpdate($defs{'tuya_cloud_00673231e09806cb188e'},'cur_current','38.0');;
2023-02-02 10:16:38,986 - ERROR - root: tuya_cloud_00673231e09806cb188e: readingsBulkUpdate without readingsBeginUpdate: readingsBulkUpdate($defs{'tuya_cloud_00673231e09806cb188e'},'cur_power','4.3');;
2023-02-02 10:16:38,986 - ERROR - root: tuya_cloud_00673231e09806cb188e: readingsBulkUpdate without readingsBeginUpdate: readingsBulkUpdate($defs{'tuya_cloud_00673231e09806cb188e'},'cur_voltage','229.3');;
2023-02-02 10:16:38,986 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_bfefd42e199ea92ee3jbwh'},'bright_value_v2','1000.0');;
2023-02-02 10:54:23,185 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_8877821724a160151069'},'state','on');;
2023-02-02 10:54:23,185 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL33'},'cur_current','320.0');;
2023-02-02 10:54:23,186 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP15'},'online','1');;
2023-02-02 11:32:08,990 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP16'},'online','1');;
2023-02-02 11:32:08,990 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_3367036770039f60ce2b'},'countdown_1','0.0');;
2023-02-02 12:20:53,768 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'tuya_cloud_260064612cf432ca55d8'});;
2023-02-02 12:20:53,771 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL04'},'cur_current','236.0');;
2023-02-02 12:20:53,773 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_00673231e09806cb188e'},'add_ele','0.002');;
2023-02-02 13:24:27,927 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'tuya_cloud_3367036770039f613620'});;
2023-02-02 13:24:27,927 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_JL26'},'cur_voltage','228.0');;
2023-02-02 13:38:50,146 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'TUYA_JL08'});;
2023-02-02 13:38:50,147 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP15'},'online','1');;
2023-02-02 14:09:26,137 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_00673231e09806cb6fa5'},'cur_current','117.0');;
2023-02-02 14:09:26,137 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsEndUpdate($defs{'TUYA_STF2'},1);;
2023-02-02 14:09:26,138 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP14'},'dp_21','1');;
2023-02-02 14:09:26,139 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsEndUpdate($defs{'TUYA_STF1'},1);;
2023-02-02 14:09:26,139 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP16'},'cur_power','1.6');;
2023-02-02 14:09:26,263 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP15'},'cur_voltage','225.7');;
2023-02-02 14:09:26,263 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP12'},'cur_voltage','225.9');;
2023-02-02 14:09:26,264 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP13'},'dp_24','20333');;
2023-02-02 14:09:26,264 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsEndUpdate($defs{'TUYA_JL20'},1);;
Ok, hab mich auch zu früh gefreut.
Die Meldungen sind auch wieder da
2023.02.02 14:07:15 1: BindingsIo (local_pybinding): Use of uninitialized value $d in hash element at fhem.pl line 4766.
=> COMMAND: readingsEndUpdate($defs{'tuya_cloud_bf4f644bc7dd2fc71d9q52'},1);;
2023.02.02 14:07:15 1: BindingsIo (local_pybinding): Use of uninitialized value $dev in hash element at fhem.pl line 3839.
=> COMMAND: readingsEndUpdate($defs{'tuya_cloud_bf4f644bc7dd2fc71d9q52'},1);;
Außerdem die anderen auch die ganze Zeit.
Mein fhem.log file hat nach 2 Stunden über 50 MB!
Gruß,
Stefan
Nachtrag:
so nach ca. 6 Stunden nach dem Stutdown reset wird der room FHEMPY wieder quasi sofort angezeigt :-)
in fhempi log haben wir inzwischen 16000-mal
2023-02-02 16:35:38,461 - WARNING - asyncio: socket.send() raised exception.
2023-02-02 16:35:43,473 - WARNING - asyncio: socket.send() raised exception.
2023-02-02 16:35:45,872 - WARNING - asyncio: socket.send() raised exception.
2023-02-02 16:35:48,485 - WARNING - asyncio: socket.send() raised exception.
2023-02-02 16:35:53,497 - WARNING - asyncio: socket.send() raised exception.
2023-02-02 16:35:55,883 - WARNING - asyncio: socket.send() raised exception.
2023-02-02 16:35:57,802 - WARNING - asyncio: socket.send() raised exception.
2023-02-02 16:35:58,511 - WARNING - asyncio: socket.send() raised exception.
2023-02-02 16:36:03,522 - WARNING - asyncio: socket.send() raised exception.
2023-02-02 16:36:05,896 - WARNING - asyncio: socket.send() raised exception.
2023-02-02 16:36:08,534 - WARNING - asyncio: socket.send() raised exception.
2023-02-02 16:36:13,546 - WARNING - asyncio: socket.send() raised exception.
2023-02-02 16:36:15,908 - WARNING - asyncio: socket.send() raised exception.
2023-02-02 16:36:18,558 - WARNING - asyncio: socket.send() raised exception.
2023-02-02 16:36:23,570 - WARNING - asyncio: socket.send() raised exception.
2023-02-02 16:36:25,920 - WARNING - asyncio: socket.send() raised exception.
2023-02-02 16:36:28,582 - WARNING - asyncio: socket.send() raised exception.
2023-02-02 16:36:33,594 - WARNING - asyncio: socket.send() raised exception.
2023-02-02 16:36:35,932 - WARNING - asyncio: socket.send() raised exception.
Damit haben sich nun die socket.send() Fehler erklärt. Sie treten auf, wenn FHEM blockiert ist.
Ich kann diese Verhalten bei mir einfach nicht reproduzieren obwohl ich ca. 20 Tuya Devices eingebunden hab. Sowohl cloud, als auch local.
@thburkhart, nachdem du so viele Devices drin hast. Könntest du mir deine Credentials (=tuya_cloud setup Definition) per PN zukommen lassen und ich richte die mal bei mir ein? Ich kann die Fehler sonst bei mir leider nicht reproduzieren.
Zitat von: dominik am 02 Februar 2023, 17:35:57
Damit haben sich nun die socket.send() Fehler erklärt. Sie treten auf, wenn FHEM blockiert ist.
Ich kann diese Verhalten bei mir einfach nicht reproduzieren obwohl ich ca. 20 Tuya Devices eingebunden hab. Sowohl cloud, als auch local.
@thburkhart, nachdem du so viele Devices drin hast. Könntest du mir deine Credentials (=tuya_cloud setup Definition) per PN zukommen lassen und ich richte die mal bei mir ein? Ich kann die Fehler sonst bei mir leider nicht reproduzieren.
sehr gerne ....
funktioell ist es so, dass ich _local vs. _cloud viele devices doppelt habe und diese nur über _cloud bedienen kann
Danke für die Zusendung der Credentials! Das Gute, ich kann den Fehler nun bei mir nachstellen und bekomme diesen auch...ich mach mich auf die Suche.
super!!
danke!!!!!!
zum Thema shutdown restart
habe eben tuyaunabhängig in der fhem.cfg was geändert und gespeichert.
Folge: fhempy offline
dann tuya restart
fempy server immer noch offline
traue mich nicht, fhem neu starten
was tun?
einfach fhempyserver neu starten
@stefanru hattest Du nicht etwes über Wechsel zu Pi400 geschrieben? ich finde es nicht mehr
Ich habe nun in Version 0.1.588 ein paar Fehler behoben. Danke thburkhart für das sharen der Devices, mit so vielen Devices konnte ich noch nie testen :)
Testet bitte mit 0.1.588. Ich bekomme damit nur noch ein paar Warnings zu recursiven Calls. Die konnte ich noch nicht ausfindig machen. Es hängt dann beim Starten etwas, spielt sich aber nach 30s ein.
Hi,
@thburkhart
Habs jetzt geschafft und es läuft auf dem 400er. Ist schon um einiges flüssiger und die tempreraturen vom Raspberry sind ein Traum.
Den mehr Speed merkt man auch gewaltig.
@Dominik
Vielen Dank!
Habe gleich die neue Version drauf gemacht.
Hatte irgendwie Probleme beim starten der Server war schon belegt oder es gab wieder viele Log Einträge.
Habe den Raspberry dann durchgestartet, danach lief alles. fhempy.log direkt nach dem Start:
2023-02-03 02:23:18,706 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.588...
2023-02-03 02:23:18,709 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-02-03 02:23:18,751 - INFO - websockets.server: server listening on 0.0.0.0:15733
2023-02-03 02:23:24,111 - INFO - websockets.server: connection open
2023-02-03 02:23:24,111 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2023-02-03 02:24:25,766 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsSingleUpdate($defs{'Fernseher_Schlafzimmer_bf4f644bc7dd2fc71d9q52'},'state','ready',1)
2023-02-03 02:24:25,770 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsSingleUpdate($defs{'Computer_Stefan_bf881b7977c814af88jmrc'},'state','ready',1)
2023-02-03 02:24:25,774 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsSingleUpdate($defs{'Fernseher_Wohnzimmer_bf7bbcb9a4b03a2c97cqid'},'state','ready',1)
2023-02-03 02:24:25,787 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: setDevAttrList('tuya_cloud_bffa550a829a269630vhcn', ' IODev '.$readingFnAttributes)
2023-02-03 02:24:25,861 - ERROR - fhempy.lib.fhem: FHEM took 60091ms for readingsSingleUpdate($defs{'Computer_Stefan_bf881b7977c814af88jmrc'},'state','ready',1)
2023-02-03 02:24:25,861 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 364, in listener
fut.set_result(rmsg)
asyncio.exceptions.InvalidStateError: invalid state
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 217, in _onMessage
await self.handle_message(msg, hash)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 227, in handle_message
listener["func"](msg)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 366, in listener
logger.error("Failed to set result, received: " + rmsg)
TypeError: can only concatenate str (not "dict") to str
2023-02-03 02:24:25,864 - ERROR - fhempy.lib.fhem_pythonbinding: fhempy failed to handle message with hash: {'awaitId': 93784484, 'result': 'ready', 'error': 0}
2023-02-03 02:24:25,865 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message: b'{"awaitId":93784484,"result":"ready","error":0}'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 364, in listener
fut.set_result(rmsg)
asyncio.exceptions.InvalidStateError: invalid state
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 217, in _onMessage
await self.handle_message(msg, hash)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 227, in handle_message
listener["func"](msg)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 366, in listener
logger.error("Failed to set result, received: " + rmsg)
TypeError: can only concatenate str (not "dict") to str
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 186, in onMessage
await self._onMessage(payload)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 220, in _onMessage
await self.sendBackError(hash, "fhempy failed to handle message")
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 135, in sendBackError
duration = (time.time() - id_received_timestamp[retHash["id"]]) * 1000
KeyError: 'id'
2023-02-03 02:24:25,893 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsSingleUpdate($defs{'Sybille_Tablet_bf68d9b41c16be3713vcc1'},'state','ready',1)
2023-02-03 02:24:25,899 - ERROR - fhempy.lib.fhem: FHEM took 60135ms for readingsSingleUpdate($defs{'Fernseher_Schlafzimmer_bf4f644bc7dd2fc71d9q52'},'state','ready',1)
2023-02-03 02:24:25,899 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 364, in listener
fut.set_result(rmsg)
asyncio.exceptions.InvalidStateError: invalid state
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 217, in _onMessage
await self.handle_message(msg, hash)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 227, in handle_message
listener["func"](msg)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 366, in listener
logger.error("Failed to set result, received: " + rmsg)
TypeError: can only concatenate str (not "dict") to str
2023-02-03 02:24:25,900 - ERROR - fhempy.lib.fhem_pythonbinding: fhempy failed to handle message with hash: {'awaitId': 27526758, 'result': 'ready', 'error': 0}
2023-02-03 02:24:25,900 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message: b'{"awaitId":27526758,"result":"ready","error":0}'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 364, in listener
fut.set_result(rmsg)
asyncio.exceptions.InvalidStateError: invalid state
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 217, in _onMessage
await self.handle_message(msg, hash)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 227, in handle_message
listener["func"](msg)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 366, in listener
logger.error("Failed to set result, received: " + rmsg)
TypeError: can only concatenate str (not "dict") to str
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 186, in onMessage
await self._onMessage(payload)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 220, in _onMessage
await self.sendBackError(hash, "fhempy failed to handle message")
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 135, in sendBackError
duration = (time.time() - id_received_timestamp[retHash["id"]]) * 1000
KeyError: 'id'
2023-02-03 02:24:26,212 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsSingleUpdate($defs{'tuya_local_bfb7810a3e397c5fa4u7ud'},'state','Initializing...',1)
2023-02-03 02:24:26,221 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsSingleUpdate($defs{'tuya_local_bf68d9b41c16be3713vcc1'},'state','Initializing...',1)
2023-02-03 02:24:26,249 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsSingleUpdate($defs{'tuya_local_bf7bbcb9a4b03a2c97cqid'},'state','Initializing...',1)
2023-02-03 02:24:26,266 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsSingleUpdate($defs{'tuya_local_bf0572e0fb6ccbe356ykuh'},'state','Initializing...',1)
2023-02-03 02:24:26,281 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsSingleUpdate($defs{'tuya_local_bf881b7977c814af88jmrc'},'state','Initializing...',1)
2023-02-03 02:24:26,287 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsSingleUpdate($defs{'tuya_local_bf4f644bc7dd2fc71d9q52'},'state','Initializing...',1)
2023-02-03 02:24:26,309 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsSingleUpdate($defs{'tuya_local_bffa550a829a269630vhcn'},'state','Initializing...',1)
2023-02-03 02:24:29,018 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsSingleUpdate($defs{'tuya_cloud_connector'},'state','connected',1)
2023-02-03 02:24:30,052 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'Stefan_Tablet_bf0572e0fb6ccbe356ykuh'});;
Gruß,
Stefan
Stefan, hast du sicher auch BindingsIo aktualisiert? Also fhem update gemacht?
Poste bitte auch das FHEM Log.
Zitat von: stefanru am 03 Februar 2023, 02:27:14
Hi,
@thburkhart
Habs jetzt geschafft und es läuft auf dem 400er. Ist schon um einiges flüssiger und die tempreraturen vom Raspberry sind ein Traum.
Den mehr Speed merkt man auch gewaltig.
Hi Stefan, konntest du direkt von einem bestehenden PI migrieren. Ich boote meine PI4B von einer 250 GB SSD.
Kann ich von dieser SSSD wohl auch auf'm PI400 direkt booten ?
DEr PI4B hat ja immer noch Mondpreise. Wo hast deinen PI400 her?
Viele GRüße
Thomas
Zitat von: dominik am 02 Februar 2023, 23:59:04
Ich habe nun in Version 0.1.588 ein paar Fehler behoben. Danke thburkhart für das sharen der Devices, mit so vielen Devices konnte ich noch nie testen :)
Testet bitte mit 0.1.588. Ich bekomme damit nur noch ein paar Warnings zu recursiven Calls. Die konnte ich noch nicht ausfindig machen. Es hängt dann beim Starten etwas, spielt sich aber nach 30s ein.
Guten Morgen Dominik,
super !!! IN der fhempy-log ist nach wenigen Einträgen Ruhe :-) auch die FHM LOg ist frieflich
Bleiben nur och die Redundanzen, die aber fast kosmetisch sind, solange sie das Systemm nicht belasten.
a) die 36 JL devices sind ja alle in local vorhanden; in tuya_Cloud tauchen fast alle neueren (JL26 bis JL36) und solche, die noch keine IP haben
b) bei den 16 SPs kann ich keine Regelmäßigkeit erkennen.
Die Device-IDs sind jedenfalls eindeutig.
Nochmals vielen Dank.
Wie denkst du über die von mir und vlt. andern auch sehnlich gewünschte monatelich Kumulierung der Verbrauchswerte? ;-)
viele Grüße
Thomas
Hi,
@thburkhart: Ja habe von einem Raspberry PI3B auf den PI400 migriert.
Haben den PI400 auf ebay Kleinanzeigen geschossen.
@dominik: Ja BindingsIo ist aktuell.
2023.02.03 10:00:41 1: Downloading https://raw.githubusercontent.com/dominikkarall/fhempy/master/controls_pythonbinding.txt
2023.02.03 10:00:41 1: pythonbinding
2023.02.03 10:00:41 1: nothing to do...
Habe jetzt nochmal den Raspberry komplett neu gestertet um dir logs schicken zu können und diesmal ist ruhe.
Das verstehe ich nicht wirklich.
im fhempy.log ist:
2023-02-03 10:06:11,903 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.588...
2023-02-03 10:06:11,906 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-02-03 10:06:11,951 - INFO - websockets.server: server listening on 0.0.0.0:15733
2023-02-03 10:06:15,635 - INFO - websockets.server: connection open
2023-02-03 10:06:15,635 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2023-02-03 10:07:18,083 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: setDevAttrList('tuya_cloud_connector', ' IODev '.$readingFnAttributes)
2023-02-03 10:07:18,088 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsSingleUpdate($defs{'Fernseher_Schlafzimmer_bf4f644bc7dd2fc71d9q52'},'state','ready',1)
2023-02-03 10:10:30,965 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'tuya_local_bf4f644bc7dd2fc71d9q52'});;
Werde das beobachten.
Danke,
Stefan
@Stefan, bitte auch FHEM Log.
@thburkhart, bitte Logs, es sollte auch nix mehr doppelt angelegt werden.
Verbrauchswerte gibt es erst, wenn wir die Fehler weg haben. Zuerst Fehler beheben, dann weitere Features ;)
Zitat von: dominik am 03 Februar 2023, 10:16:25
@thburkhart, bitte Logs, es sollte auch nix mehr doppelt angelegt werden.
Verbrauchswerte gibt es erst, wenn wir die Fehler weg haben. Zuerst Fehler beheben, dann weitere Features ;)
ich sehe es nur im room fhempy , dass die gleichen devise in tuya und tuya_cloud gezeigt werden.
Ich müsste dies doppelten wohl händisch in tuya_cloud löschen und dann den fhempy-server neu starten?
Genau
nun haben wir nur noch eine Redundanz:
define TUYA_Temp06 fhempy tuya_cloud TUYA bfc0750fc8af85f5d5vei7
setuuid TUYA_Temp06 63d98f53-f33f-fd5f-94c9-2a0e3580220e1385
attr TUYA_Temp06 DbLogExclude .*
attr TUYA_Temp06 DbLogInclude va_humidity,va_temperature
attr TUYA_Temp06 alias TempHum06 Treppenhaus oben
attr TUYA_Temp06 event-min-interval va_humidity:300,va_temperature:300
attr TUYA_Temp06 event-on-change-reading .*
attr TUYA_Temp06 group Temperatur und Feuchtigkeit,Temperatur und Feuchtigkeit innen
attr TUYA_Temp06 room fhempy
define tuya_cloud_bfc0750fc8af85f5d5vei7 fhempy tuya_cloud TUYA bfc0750fc8af85f5d5vei7
setuuid tuya_cloud_bfc0750fc8af85f5d5vei7 63dcde0a-f33f-fd5f-f00c-ab2625824c146217
attr tuya_cloud_bfc0750fc8af85f5d5vei7 DbLogExclude .*
attr tuya_cloud_bfc0750fc8af85f5d5vei7 alias TempHum6 Treppenhaus oben
attr tuya_cloud_bfc0750fc8af85f5d5vei7 event-on-change-reading .*
attr tuya_cloud_bfc0750fc8af85f5d5vei7 group tuya_cloud
attr tuya_cloud_bfc0750fc8af85f5d5vei7 room fhempy
bei define tuya_cloud_bfc0750fc8af85f5d5vei7 fhempy tuya_cloud TUYA bfc0750fc8af85f5d5vei7
setuuid tuya_cloud_bfc0750fc8af85f5d5vei7 63dcde0a-f33f-fd5f-f00c-ab2625824c146217
attr tuya_cloud_bfc0750fc8af85f5d5vei7 DbLogExclude .*
attr tuya_cloud_bfc0750fc8af85f5d5vei7 alias TempHum6 Treppenhaus oben
attr tuya_cloud_bfc0750fc8af85f5d5vei7 event-on-change-reading .*
attr tuya_cloud_bfc0750fc8af85f5d5vei7 group tuya_cloud
attr tuya_cloud_bfc0750fc8af85f5d5vei7 room fhempy
vorher hatte ich alle schalter-Device in tuya_cloud gelöscht.
du kannst ja meinen TempHum6 nachvollziehen
lg
Thomas
Hi Dominik,
habe nun noch mehrmals neu gestartet, da ich noch am Raspberry bastel.
Hatte keine Fehler mehr beim starten.
Doppelte Devices bekomme ich auch nicht mehr angelegt.
Hatte das ab und zu mal.
Danke und Gruß,
Stefan
leider muss ich korrigieren:
Im hintergrund hat er doch wieder die Schalter hinzugefügt :
im log steht auszugsweise:
2023.02.03 11:15:24 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.03 11:15:24 1: main::CallFn called by fhem.pl (1954)
2023.02.03 11:15:24 1: main::DoSet called by fhem.pl (1996)
2023.02.03 11:15:24 1: main::CommandSet called by fhem.pl (2904)
2023.02.03 11:15:24 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.03 11:15:24 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.03 11:15:24 1: main::FW_Notify called by fhem.pl (3976)
2023.02.03 11:15:24 1: main::CallFn called by fhem.pl (3888)
2023.02.03 11:15:24 1: main::DoTrigger called by fhem.pl (4995)
2023.02.03 11:15:24 1: main::readingsEndUpdate called by (eval 7058) (1)
2023.02.03 11:15:24 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 11:15:24 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 11:15:24 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.03 11:15:24 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.03 11:15:24 1: main::CallFn called by fhem.pl (784)
2023.02.03 11:15:31 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_453005615002911dfe06)
2023.02.03 11:15:35 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bf16f1788a2fd6edd6pr1d)
2023.02.03 11:15:44 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_4530056170039f4a87e5)
2023.02.03 11:15:48 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_720570712462ab27e625)
2023.02.03 11:15:51 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_720570712462ab280270)
2023.02.03 11:15:56 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_887800042cf4325f15ef)
2023.02.03 11:16:05 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_21410806cc50e37bdb15)
2023.02.03 11:16:09 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_104380002462ab30258d)
2023.02.03 11:16:13 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_0120018760019453b4b1)
2023.02.03 11:16:36 1: readingsUpdate(tuya_cloud_453005615002911dfe06,state,off) missed to call readingsBeginUpdate first.
2023.02.03 11:16:36 1: stacktrace:
2023.02.03 11:16:36 1: main::readingsBulkUpdate called by (eval 8722) (1)
2023.02.03 11:16:36 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 11:16:36 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 11:16:36 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.03 11:16:36 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.03 11:16:36 1: main::CallFn called by fhem.pl (784)
2023.02.03 11:16:36 1: readingsUpdate(tuya_cloud_453005615002911dfe06,countdown_1,0.0) missed to call readingsBeginUpdate first.
2023.02.03 11:16:36 1: stacktrace:
2023.02.03 11:16:36 1: main::readingsBulkUpdate called by (eval 8727) (1)
2023.02.03 11:16:36 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 11:16:36 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 11:16:36 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 11:16:36 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 11:16:36 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.03 11:16:36 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.03 11:16:36 1: main::CallFn called by fhem.pl (1954)
2023.02.03 11:16:36 1: main::DoSet called by fhem.pl (1996)
2023.02.03 11:16:36 1: main::CommandSet called by fhem.pl (2904)
2023.02.03 11:16:36 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.03 11:16:36 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.03 11:16:36 1: main::FW_Notify called by fhem.pl (3976)
2023.02.03 11:16:36 1: main::CallFn called by fhem.pl (3888)
2023.02.03 11:16:36 1: main::DoTrigger called by fhem.pl (4995)
2023.02.03 11:16:36 1: main::readingsEndUpdate called by (eval 8726) (1)
2023.02.03 11:16:36 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 11:16:36 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 11:16:36 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.03 11:16:36 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.03 11:16:36 1: main::CallFn called by fhem.pl (784)
2023.02.03 11:16:36 1: readingsUpdate(tuya_cloud_453005615002911dfe06,add_ele,10.0) missed to call readingsBeginUpdate first.
Nachtrag:
ich habe inzwischen die doppelten in der fhem.conf gelöscht (dort standen sie ja ganz hinten)
vorher FHEM gestoppt
dann RASPI neu gestartet
30 min gewartet
nun habe ich als doppelte nur noch devices, die definitiv nicht am Stom sind.
Das ist eigentlich sinnhaftig.
aus meiner Sicht also alles gut :-)
Es darf gar keine doppelten Devices geben. Es wird immer anhand der DEVICEID (die haben auch offline Devices) geschaut ob welche existieren. Kommen Fehler in den beiden Logs?
Zitat von: dominik am 03 Februar 2023, 13:26:38
Es darf gar keine doppelten Devices geben. Es wird immer anhand der DEVICEID (die haben auch offline Devices) geschaut ob welche existieren. Kommen Fehler in den beiden Logs?
FHEM log:
2023.02.03 12:29:41 3: fhempy v1.0.0 (tuya: TUYA_BULB01)
2023.02.03 12:29:41 3: fhempy v1.0.0 (tuya: TUYA_BULB02)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_BULB03)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bf3761a5af5f8d6361rmhh)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bf9e9fea71f3692d15gzrq)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bfffc31d13d14bca5dayj6)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bf6b1900c331a78a2fkecw)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bfbeab33da30f5635ffj0r)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bfd99c63a8b65928a56hdb)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_DIY1)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_DIY3)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_DIY4)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_EMYLO1)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_EMYLO2)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_EMYLOD2)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_EMYLO3)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_EMYLO4)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL02)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL03)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL04)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL05)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL06)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL07)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL08)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL09)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL10Z)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL11Z)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL12Z)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL13)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL14)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL15)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL16)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL17)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL18)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL19)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL20)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL21)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL22)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL23)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL24)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL26)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL27)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL28)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL29)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL30)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL31)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL32)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL33)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL34)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL35)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_JL36)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_PS1)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_PS2)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_PS3)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_PS4)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_PS5)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_PS7)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_SCHF1)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_SCHF2)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_SCHF3)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_SCHF4)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_SP01)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_SP02)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_SP03)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_SP04)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_SP05)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_SP06)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_SP07)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_SP08)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_SP09)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_SP10)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_SP11)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_SP12)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_SP13)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_SP14)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_SP15)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_SP16)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_STF1)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_STF2)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_STF3)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya: TUYA_MMG)
2023.02.03 12:29:42 3: SST (SamsungSmartThingsConnector): define - CONNECTOR defined as SamsungSmartThingsConnector
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp01)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp02)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp03)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp04)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bf0982f08295070ae7tulb)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp05)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp06)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp07)
2023.02.03 12:29:42 1: PERL WARNING: Useless use of anonymous hash ({}) in void context at (eval 127) line 1, <$fh> line 6233.
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_60381718500291bade80)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_60381718807d3a04bbb4)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_60381718807d3a01eb63)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_67242256f4cfa2ce1662)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_34602852ecfabc47cbe1)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_50880180cc50e30cbe91)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_50880180840d8e87664b)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_50880180cc50e30c4c90)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_180025363c6105dcdcaf)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_07847240dc4f225fdda0)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_07847240bcddc29b03e9)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_06515140cc50e3d62490)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_47104178dc4f2236e437)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bffb7d9839e65fcdeciaqn)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_853556472cf4326e60da)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_627425735002915f502b)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_743066432cf43267661d)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bfc0750fc8af85f5d5vei7)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bfabd3dbaa5113764dzgkn)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_3367036770039f60ce2b)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_453005615002911dfe06)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bf16f1788a2fd6edd6pr1d)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_4530056170039f4a87e5)
2023.02.03 12:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_720570712462ab27e625)
2023.02.03 12:29:43 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_720570712462ab280270)
2023.02.03 12:29:43 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_887800042cf4325f15ef)
2023.02.03 12:29:43 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_21410806cc50e37bdb15)
2023.02.03 12:29:43 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_104380002462ab30258d)
2023.02.03 12:29:43 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_0120018760019453b4b1)Beispiel:
tuya_cloud_4530056170039f4a87e5
ist local TUYA_JL17
[code]define TUYA_JL17 fhempy tuya wifvoilfrqeo6hvu 4530056170039f4a87e5 offline 2204c23a9c30d10b 3.3 ea8453wdazquzfl08l0e 8a4b27dd759d4c6a9456aa8155d2a0ea
attr TUYA_JL17 DbLogExclude .*
attr TUYA_JL17 alias JL17 Heizdecke 1
attr TUYA_JL17 group Schalter (T),Schalter Heizgeräte
attr TUYA_JL17 room fhempy
# DEF tuya wifvoilfrqeo6hvu 4530056170039f4a87e5 offline 2204c23a9c30d10b 3.3 ea8453wdazquzfl08l0e 8a4b27dd759d4c6a9456aa8155d2a0ea
# FHEMPYTYPE tuya
# FUUID 63b30be0-f33f-fd5f-297f-f23e4ed51422a6db
# IODev local_pybinding
# NAME TUYA_JL17
# NR 1718
# PYTHONTYPE tuya
# STATE Change DEF and use IP instead of 'offline'
# TYPE fhempy
# eventCount 1
# READINGS:
# 2023-01-30 07:59:00 online 0
# 2023-02-03 12:29:56 state Change DEF and use IP instead of 'offline'
# args:
# TUYA_JL17
# fhempy
# tuya
# wifvoilfrqeo6hvu
# 4530056170039f4a87e5
# offline
# 2204c23a9c30d10b
# 3.3
# ea8453wdazquzfl08l0e
# 8a4b27dd759d4c6a9456aa8155d2a0ea
# argsh:
#
setstate TUYA_JL17 Change DEF and use IP instead of 'offline'
setstate TUYA_JL17 2023-01-30 07:59:00 online 0
setstate TUYA_JL17 2023-02-03 12:29:56 state Change DEF and use IP instead of 'offline'
[/code]
also identische DeviceID aber Ip nicht bekannt (Die Heizdecken samt Stecker sind irgendwo auf der Bühne; da war es mir zu kalt zum Suchen)
aber du hast Recht; an hand der DeviceID müsste es als bekannt gefunden werden.
Ich benenne mal die gewollten "cloud_only"-devices um, damit die doppelten zu _local gleich erkannt werden.
Oder kannst du es gleich nachvollziehen, dass NUR die Devices ohne IP gedoppelt werden?
Fehler gefunden :) Die offline Devices hatten kein Internal DEVICEID, da genau der Code nicht mehr durchlaufen wurde wg. offline state. Ist nun korrigiert.
Bitte mit 0.1.589 testen.
Falls du im FHEM oder fhempy Log noch Fehler hast, bitte posten! Ich möchte wirklich sicherstellen, dass da nix mehr falsch läuft.
ich nochmal nachgeschaut.
es ist eindeutig:
idoppelt vs. tuya-local sind genau die nicht angeschlossen
Stecker, Schalter,Cameras
Das würde mich nicht stören.
Es werden aber auch unsere berüchttigten "Schläfer" Temp03 bist Temp07 innerhalb tuya-cloud doppelt erfasst.
es werden vallerdings die Originale suber gelogt.
Es besteht der Verdacht , dass FHem mit dem Duplizieren intensiv beschäftigt ist. So wird der room fhempy est nach 2 bis 3 Stunden wieder flüssig angezeigt wird.
du warst vor mir
ich teste gleich mal
Das mit den fhempy Raum sollte auch nicht sein. Ich habe alle deine (ich glaube über 100) tuya Devices in einem Raum und der baut durchaus innerhalb von ein paar Sekunden auf.
Schau bitte ob du da was im Log siehst.
Zitat von: dominik am 03 Februar 2023, 22:28:04
Das mit den fhempy Raum sollte auch nicht sein. Ich habe alle deine (ich glaube über 100) tuya Devices in einem Raum und der baut durchaus innerhalb von ein paar Sekunden auf.
das war vor ner halben Stunde bei mir auch so.
Nun habe ich da Update gezogen und teste
2023-02-02 23:59:30,763 - WARNING - asyncio: socket.send() raised exception.
2023-02-02 23:59:34,395 - WARNING - asyncio: socket.send() raised exception.
2023-02-02 23:59:35,775 - WARNING - asyncio: socket.send() raised exception.
2023-02-02 23:59:40,787 - WARNING - asyncio: socket.send() raised exception.
2023-02-02 23:59:44,408 - WARNING - asyncio: socket.send() raised exception.
2023-02-02 23:59:45,799 - WARNING - asyncio: socket.send() raised exception.
2023-02-02 23:59:50,812 - WARNING - asyncio: socket.send() raised exception.
2023-02-02 23:59:53,943 - WARNING - asyncio: socket.send() raised exception.
2023-02-02 23:59:54,420 - WARNING - asyncio: socket.send() raised exception.
2023-02-02 23:59:55,825 - WARNING - asyncio: socket.send() raised exception.
setuuid tuya_cloud_bfc0750fc8af85f5d5vei7 63dd7c28-f33f-fd5f-e0dd-58ed086dbd27fc6a
attr tuya_cloud_bfc0750fc8af85f5d5vei7 alias TempHum6 Treppenhaus oben
attr tuya_cloud_bfc0750fc8af85f5d5vei7 group tuya_cloud
attr tuya_cloud_bfc0750fc8af85f5d5vei7 room fhempy
define tuya_cloud_bfabd3dbaa5113764dzgkn fhempy tuya_cloud TUYA bfabd3dbaa5113764dzgkn
setuuid tuya_cloud_bfabd3dbaa5113764dzgkn 63dd7c38-f33f-fd5f-d4cb-59d1135f51e2647e
attr tuya_cloud_bfabd3dbaa5113764dzgkn DbLogExclude .*
attr tuya_cloud_bfabd3dbaa5113764dzgkn alias TempHum7 Kueche
attr tuya_cloud_bfabd3dbaa5113764dzgkn event-on-change-reading .*
attr tuya_cloud_bfabd3dbaa5113764dzgkn group tuya_cloud
attr tuya_cloud_bfabd3dbaa5113764dzgkn room fhempy
define tuya_cloud_3367036770039f60ce2b fhempy tuya_cloud TUYA 3367036770039f60ce2b
setuuid tuya_cloud_3367036770039f60ce2b 63dd7c5c-f33f-fd5f-8c2b-0a01dbb7d9f9a5f0
attr tuya_cloud_3367036770039f60ce2b DbLogExclude .*
attr tuya_cloud_3367036770039f60ce2b alias USB Lader2 Thomas
attr tuya_cloud_3367036770039f60ce2b event-on-change-reading .*
attr tuya_cloud_3367036770039f60ce2b group tuya_cloud
attr tuya_cloud_3367036770039f60ce2b room fhempy
define tuya_cloud_00673231e09806cbeaa2 fhempy tuya_cloud TUYA 00673231e09806cbeaa2
setuuid tuya_cloud_00673231e09806cbeaa2 63dd7c6c-f33f-fd5f-ee7d-76778e1ba4f5c7aa
attr tuya_cloud_00673231e09806cbeaa2 DbLogExclude .*
attr tuya_cloud_00673231e09806cbeaa2 alias SP16 TH West
attr tuya_cloud_00673231e09806cbeaa2 event-on-change-reading .*
attr tuya_cloud_00673231e09806cbeaa2 group tuya_cloud
attr tuya_cloud_00673231e09806cbeaa2 room fhempy
define tuya_cloud_453005615002911dfe06 fhempy tuya_cloud TUYA 453005615002911dfe06
setuuid tuya_cloud_453005615002911dfe06 63dd7d27-f33f-fd5f-c837-68466fb7b41f235c
attr tuya_cloud_453005615002911dfe06 DbLogExclude .*
attr tuya_cloud_453005615002911dfe06 alias Heizkissen 2
attr tuya_cloud_453005615002911dfe06 event-on-change-reading .*
attr tuya_cloud_453005615002911dfe06 group tuya_cloud
attr tuya_cloud_453005615002911dfe06 room fhempy
define tuya_cloud_720570712462ab27e625 fhempy tuya_cloud TUYA 720570712462ab27e625
setuuid tuya_cloud_720570712462ab27e625 63dd7d30-f33f-fd5f-c814-b8edeacdfacb75ce
attr tuya_cloud_720570712462ab27e625 DbLogExclude .*
attr tuya_cloud_720570712462ab27e625 alias Steckdose 4
attr tuya_cloud_720570712462ab27e625 event-on-change-reading .*
attr tuya_cloud_720570712462ab27e625 group tuya_cloud
attr tuya_cloud_720570712462ab27e625 room fhempy
define tuya_cloud_887800042cf4325f15ef fhempy tuya_cloud TUYA 887800042cf4325f15ef
setuuid tuya_cloud_887800042cf4325f15ef 63dd7d37-f33f-fd5f-424a-5adc2683fa4e1614
attr tuya_cloud_887800042cf4325f15ef DbLogExclude .*
attr tuya_cloud_887800042cf4325f15ef alias Wohnzimmer 4
attr tuya_cloud_887800042cf4325f15ef event-on-change-reading .*
attr tuya_cloud_887800042cf4325f15ef group tuya_cloud
attr tuya_cloud_887800042cf4325f15ef room fhempy
Bitte auch das fhem Log
dein fhempy Log ist von gestern, bitte aktuelle Logs von Fehlern
nun die richtige:
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 217, in _onMessage
await self.handle_message(msg, hash)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 227, in handle_message
listener["func"](msg)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 366, in listener
logger.error("Failed to set result, received: " + rmsg)
TypeError: can only concatenate str (not "dict") to str
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 186, in onMessage
await self._onMessage(payload)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 220, in _onMessage
await self.sendBackError(hash, "fhempy failed to handle message")
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 135, in sendBackError
duration = (time.time() - id_received_timestamp[retHash["id"]]) * 1000
KeyError: 'id'
2023-02-03 22:28:50,324 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.589...
2023-02-03 22:28:50,329 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-02-03 22:28:50,370 - INFO - websockets.server: server listening on 0.0.0.0:15733
2023-02-03 22:28:57,141 - INFO - websockets.server: connection open
2023-02-03 22:28:57,142 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2023-02-03 22:29:04,058 - ERROR - TUYA: Please activate OpenPulsar: https://developer.tuya.com/en/docs/iot/subscribe-mq?id=Kavqcrvckbh9h
2023-02-03 22:29:14,253 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com
2023-02-03 22:29:14,255 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com
2023-02-03 22:29:14,270 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com
2023-02-03 22:29:14,282 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com
2023-02-03 22:29:14,284 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com
2023-02-03 22:29:14,296 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com
2023-02-03 22:29:14,306 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com
2023-02-03 22:29:14,320 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com
2023-02-03 22:30:26,319 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsEndUpdate($defs{'TUYA_JL33'},1);;
2023-02-03 22:30:26,319 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP11'},'dp_23','30264');;
2023-02-03 22:30:26,319 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_SP08', 'dp_09', '')
2023-02-03 22:30:26,320 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_SP04', 'dp_01', '')
2023-02-03 22:30:26,320 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_SP05', 'dp_01', '')
2023-02-03 22:30:26,320 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_SP07', 'dp_01', '')
2023-02-03 22:30:26,321 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_BULB03', 'dp_22', '')
2023-02-03 22:30:26,321 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_JL02', 'dp_05', '')
2023-02-03 22:30:26,447 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_JL10Z', 'dp_01', '')
2023-02-03 22:30:26,448 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_JL22', 'dp_03', '')
2023-02-03 22:30:26,448 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsEndUpdate($defs{'TUYA_JL31'},1);;
2023-02-03 22:30:26,448 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'TUYAC_Camera2'},'ptz_stop','on');;
2023-02-03 22:30:26,449 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_SP01', 'dp_24', '')
2023-02-03 22:30:26,449 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'TUYAC_Camera1'},'motion_timer_setting','07:00|19:00');;
2023-02-03 22:32:19,936 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP06'},'cur_current','695.0');;
2023-02-03 22:35:32,384 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsEndUpdate($defs{'TUYA_STF2'},1);;
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_BULB01)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_BULB02)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_BULB03)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Camera1)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Camera2)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Camera3)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya_cloud: Camera4tuya_cloud_bf6b1900c331a78a2fkecw)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya_cloud: Camera5tuya_cloud_bfbeab33da30f5635ffj0r)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Camera6)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_DIY1)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_DIY3)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_DIY4)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_EMYLO1)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_EMYLO2)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_EMYLOD2)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_EMYLO3)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_EMYLO4)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL02)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL03)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL04)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL05)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL06)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL07)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL08)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL09)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL10Z)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL11Z)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL12Z)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL13)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL14)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL15)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL16)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL17)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL18)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL19)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL20)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL21)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL22)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL23)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL24)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL26)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL27)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL28)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL29)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL30)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL31)
2023.02.03 22:28:47 3: fhempy v1.0.0 (tuya: TUYA_JL32)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_JL33)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_JL34)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_JL35)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_JL36)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_PS1)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_PS2)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_PS3)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_PS4)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_PS5)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_PS7)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_SCHF1)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_SCHF2)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_SCHF3)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_SCHF4)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_SP01)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_SP02)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_SP03)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_SP04)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_SP05)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_SP06)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_SP07)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_SP08)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_SP09)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_SP10)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_SP11)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_SP12)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_SP13)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_SP14)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_SP15)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_SP16)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: TUYAC_PIR01)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: TUYAC_PIR02)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: TUYAC_PIR03)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_STF1)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_STF2)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_STF3)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya: TUYA_MMG)
2023.02.03 22:28:48 3: SST (SamsungSmartThingsConnector): define - CONNECTOR defined as SamsungSmartThingsConnector
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp01)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp02)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp03)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp04)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp05)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp06)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp07)
2023.02.03 22:28:48 1: PERL WARNING: Useless use of anonymous hash ({}) in void context at (eval 127) line 1, <$fh> line 6238.
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorT01)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorT02)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorT03)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorT04)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorT05)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorW01)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorW02)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorW03)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorW04)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Sir01)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Sir02)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Sir03)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Relais01)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorSmoke01)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bf16f1788a2fd6edd6pr1d)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bfc0750fc8af85f5d5vei7)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bfabd3dbaa5113764dzgkn)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_3367036770039f60ce2b)
2023.02.03 22:28:48 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_00673231e09806cbeaa2)
2023.02.03 22:28:48 1: Including ./log/fhem.save
2023.02.03 22:28:49 1: Messages collected while initializing FHEM:SecurityCheck:
telnetPort is not password protected
WEBtablet is not password protected
MQTT2 is not password protected
WEBphone is not password protected
WEB 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.03 22:28:49 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2023.02.03 22:28:49 3: alexa: starting
2023.02.03 22:28:49 3: alexa: using logfile: ./log/alexa-2023-02-03.log
2023.02.03 22:28:50 2: hueBridge1: autocreate: created 0/0/0 devices (ignored 0/2/26)
2023.02.03 22:28:51 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2023.02.03 22:28:51 0: Featurelevel: 6.2
2023.02.03 22:28:51 0: Server started with 517 defined entities (fhem.pl:27110/2023-01-23 perl:5.032001 os:linux user:fhem pid:1705)
2023.02.03 22:28:51 3: DbLog dblog_THB - DB connection parameters are initialized in the SubProcess
2023.02.03 22:28:51 1: PERL WARNING: devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
2023.02.03 22:28:51 1: PERL WARNING: ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1310.
2023.02.03 22:28:53 3: DbLog dblog_THB - DB connection parameters are stored in SubProcess
2023.02.03 22:28:54 3: alexa: read: end of file reached while sysread
2023.02.03 22:28:54 3: alexa: stopped
2023.02.03 22:28:54 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2023.02.03 22:28:54 3: alexa: starting
2023.02.03 22:28:54 3: alexa: using logfile: ./log/alexa-2023-02-03.log
2023.02.03 22:28:54 2: AttrTemplates: got 258 entries
2023.02.03 22:28:57 2: {"token_type":"Bearer","access_token":"eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzUxMiJ9.eyJzdWIiOiJiNmU5ZDg5Ni1kMzMwLTRiMWYtODVhNS0wYjk4NGQyZWJiMDQiLCJhdWQiOiJVU0VSIiwic2NvcGUiOiJDVVNUT01FUl9BUEkiLCJpc3MiOiJvaWxmb3guaW8iLCJleHAiOjE2NzU0NjA2MzYsImp0aSI6IjY3ZDRmY2RkLTg0NzAtNDlmNC1hZmZmLTMxY2Y0MDZjYjgzOCIsImVtYWlsIjoiYmt0QGdteC5uZXQifQ.fChUExgoG7zyRC2kdsijTE-qYODAmCG3XELJqAnhcRuyLo2FrZRxRtvkI8qiPrRFOClErOKM1Ujo1bClVwgB4g","refresh_token":"eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzUxMiJ9.eyJzY29wZSI6IkNVU1RPTUVSX0FQSSIsImlzcyI6Im9pbGZveC5pbyIsImV4cCI6MTY3Njc1NTczNiwianRpIjoiMWQ5MTdjZDQtZDNkMS00NjBmLWI3MmUtNzdjYWViZWE3ODA5In0.RUgYNHK5bOf2bsY7Ov_8hDfhy7Ay9JznLTb3lE26PDtETeVgYtTQv5vSODDsWkOp_UNDS5GlpikGp3Tmqy2Nug"}
2023.02.03 22:29:35 2: hueBridge1: http request failed: SSL connect attempt failed
2023.02.03 22:29:35 2: Buderus : km200_ParseHttpResponseInit - ERROR : /application: No proper Communication with Gateway: read from http://192.168.9.114:80 timed out
2023.02.03 22:29:35 2: Buderus : km200_ParseHttpResponseInit - ERROR : Timer restarted to try again in 10s
2023.02.03 22:29:37 3: DbLog dblog_THB - SubProcess connected to fhem
2023.02.03 22:29:39 1: PERL WARNING: Argument "xxxx xxxx" isn't numeric in numeric eq (==) at ./FHEM/33_readingsGroup.pm line 1177.
2023.02.03 22:30:19 1: PERL WARNING: Use of uninitialized value $value in string eq at ./FHEM/10_MAX.pm line 2057.
2023.02.03 22:30:19 1: PERL WARNING: Use of uninitialized value $value in string eq at ./FHEM/10_MAX.pm line 2058.
2023.02.03 22:31:19 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_453005615002911dfe06)
2023.02.03 22:31:22 2: hueBridge1: EventStream: event for unknown device received, trying to refresh resouces
2023.02.03 22:31:23 2: hueBridge1: autocreate: created 0/0/0 devices (ignored 0/2/26)
2023.02.03 22:31:28 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_720570712462ab27e625)
2023.02.03 22:31:35 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_887800042cf4325f15ef)
2023.02.03 22:36:14 1: PERL WARNING: Argument "low" isn't numeric in numeric lt (<) at (eval 14380) line 1.
Da blockiert irgendwas dein FHEM
2023.02.03 22:30:19 1: PERL WARNING: Use of uninitialized value $value in string eq at ./FHEM/10_MAX.pm line 2058.
2023.02.03 22:31:19 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_453005615002911dfe06)
Hier vergeht genau 1 Minute und dann kommt in fhempy NO RESPONSE, weil ich max. 1 Minute warte. Kann es sein, dass MAX oder irgendwas anderes FHEM blockiert?
Kannst du das mit perfmon analysieren?
Zitat von: dominik am 03 Februar 2023, 22:57:00
Da blockiert irgendwas dein FHEM
2023.02.03 22:30:19 1: PERL WARNING: Use of uninitialized value $value in string eq at ./FHEM/10_MAX.pm line 2058.
2023.02.03 22:31:19 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_453005615002911dfe06)
Hier vergeht genau 1 Minute und dann kommt in fhempy NO RESPONSE, weil ich max. 1 Minute warte. Kann es sein, dass MAX oder irgendwas anderes FHEM blockiert?
Kannst du das mit perfmon analysieren?
wie geht das mit perfmon ? ;-)
room steht nun innerhalb 1 sekunde
eventlog von MAX:
2023-02-03 23:07:50 MAX MAX_Wohnzimmer_WT temperature: 21.3
2023-02-03 23:07:50 MAX MAX_Wohnzimmer_WT deviation: 0.8
2023-02-03 23:07:50 MAX MAX_Wohnzimmer_WT 20.5
2023-02-03 23:07:50 MAX MAX_Wohnzimmer_WT desiredTemperature: 20.5
2023-02-03 23:07:50 MAX MAX_Wohnzimmer_WT RSSI: -76
2023-02-03 23:07:50 MAX MAX_Wohnzimmer_WT peerList: Broadcast,MAX_Wohnzimmer_O,MAX_Wohnzimmer_SO,MAX_Wohnzimmer_SW
2023-02-03 23:07:50 MAX MAX_Wohnzimmer_WT peerIDs: 000000,08a373,08a8f2,16edc5
2023-02-03 23:07:50 CUL_MAX MaxSystem CUL_0:ok
2023-02-03 23:07:51 MAX MAX_Wohnzimmer_SW valveposition: 12
2023-02-03 23:07:51 MAX MAX_Wohnzimmer_SW 20.5
2023-02-03 23:07:51 MAX MAX_Wohnzimmer_SW desiredTemperature: 20.5
2023-02-03 23:07:51 MAX MAX_Wohnzimmer_SW RSSI: -49.5
2023-02-03 23:07:51 MAX MAX_Wohnzimmer_SW battery: ok
2023-02-03 23:07:51 MAX MAX_Wohnzimmer_SW batteryState: ok
2023-02-03 23:07:51 MAX MAX_Wohnzimmer_SW rferror: 0
2023-02-03 23:07:51 MAX MAX_Wohnzimmer_SW gateway: 1
2023-02-03 23:07:51 MAX MAX_Wohnzimmer_SW mode: auto
2023-02-03 23:07:51 MAX MAX_Wohnzimmer_SW panel: unlocked
2023-02-03 23:07:51 MAX MAX_Wohnzimmer_SW peerList: Broadcast,MAX_Wohnzimmer_WT
2023-02-03 23:07:51 MAX MAX_Wohnzimmer_SW peerIDs: 000000,0ccd87
2023-02-03 23:07:51 CUL_MAX MaxSystem CUL_0:ok
MAX schaltet 22:30 in der Tat ein paar Thermostate
blockiert MAX beim Schalten?
Sehe gerade es gibt auch freezemon
define freezemon freezemon
und dann im Log schauen nach dem restart.
neues log:
2023.02.03 22:55:22 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_52470320e09806c9a53f)
2023.02.03 22:55:26 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_00673231e09806cb13b0)
2023.02.03 22:55:43 1: readingsUpdate(TUYA_JL03,cur_current,385.0) missed to call readingsBeginUpdate first.
2023.02.03 22:55:43 1: stacktrace:
2023.02.03 22:55:43 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.02.03 22:55:43 1: main::readingsBulkUpdateIfChanged called by (eval 5656) (1)
2023.02.03 22:55:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 22:55:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 22:55:43 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 22:55:43 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 22:55:43 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.03 22:55:43 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.03 22:55:43 1: main::CallFn called by fhem.pl (1954)
2023.02.03 22:55:43 1: main::DoSet called by fhem.pl (1996)
2023.02.03 22:55:43 1: main::CommandSet called by fhem.pl (2904)
2023.02.03 22:55:43 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.03 22:55:43 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.03 22:55:43 1: main::FW_Notify called by fhem.pl (3976)
2023.02.03 22:55:43 1: main::CallFn called by fhem.pl (3888)
2023.02.03 22:55:43 1: main::DoTrigger called by fhem.pl (4995)
2023.02.03 22:55:43 1: main::readingsEndUpdate called by (eval 5655) (1)
2023.02.03 22:55:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 22:55:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 22:55:43 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 22:55:43 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 22:55:43 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.03 22:55:43 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.03 22:55:43 1: main::CallFn called by fhem.pl (1954)
2023.02.03 22:55:43 1: main::DoSet called by fhem.pl (1996)
2023.02.03 22:55:43 1: main::CommandSet called by fhem.pl (2904)
2023.02.03 22:55:43 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.03 22:55:43 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.03 22:55:43 1: main::FW_Notify called by fhem.pl (3976)
2023.02.03 22:55:43 1: main::CallFn called by fhem.pl (3888)
2023.02.03 22:55:43 1: main::DoTrigger called by fhem.pl (4995)
2023.02.03 22:55:43 1: main::readingsEndUpdate called by (eval 5652) (1)
2023.02.03 22:55:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 22:55:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 22:55:43 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 22:55:43 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 22:55:43 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.03 22:55:43 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.03 22:55:43 1: main::CallFn called by fhem.pl (1954)
2023.02.03 22:55:43 1: main::DoSet called by fhem.pl (1996)
2023.02.03 22:55:43 1: main::CommandSet called by fhem.pl (2904)
2023.02.03 22:55:43 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.03 22:55:43 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.03 22:55:43 1: main::FW_Notify called by fhem.pl (3976)
2023.02.03 22:55:43 1: main::CallFn called by fhem.pl (3888)
2023.02.03 22:55:43 1: main::DoTrigger called by fhem.pl (3222)
2023.02.03 22:55:43 1: main::CommandAttr called by (eval 5633) (1)
2023.02.03 22:55:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 22:55:43 1: readingsUpdate(TUYA_JL04,cur_current,216.0) missed to call readingsBeginUpdate first.
2023.02.03 22:55:43 1: stacktrace:
2023.02.03 22:55:43 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.02.03 22:55:43 1: main::readingsBulkUpdateIfChanged called by (eval 5657) (1)
2023.02.03 22:55:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 22:55:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 22:55:43 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 22:55:43 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 22:55:43 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.03 22:55:43 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.03 22:55:43 1: main::CallFn called by fhem.pl (1954)
2023.02.03 22:55:43 1: main::DoSet called by fhem.pl (1996)
2023.02.03 22:55:43 1: main::CommandSet called by fhem.pl (2904)
2023.02.03 22:55:43 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.03 22:55:43 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.03 22:55:43 1: main::FW_Notify called by fhem.pl (3976)
2023.02.03 22:55:43 1: main::CallFn called by fhem.pl (3888)
2023.02.03 22:55:43 1: main::DoTrigger called by fhem.pl (4995)
2023.02.03 22:55:43 1: main::readingsEndUpdate called by (eval 5655) (1)
2023.02.03 22:55:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 22:55:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 22:55:43 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 22:55:43 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 22:55:43 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.03 22:55:43 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.03 22:55:43 1: main::CallFn called by fhem.pl (1954)
2023.02.03 22:55:43 1: main::DoSet called by fhem.pl (1996)
2023.02.03 22:55:43 1: main::CommandSet called by fhem.pl (2904)
2023.02.03 22:55:43 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.03 22:55:43 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.03 22:55:43 1: main::FW_Notify called by fhem.pl (3976)
2023.02.03 22:55:43 1: main::CallFn called by fhem.pl (3888)
2023.02.03 22:55:43 1: main::DoTrigger called by fhem.pl (4995)
2023.02.03 22:55:43 1: main::readingsEndUpdate called by (eval 5652) (1)
2023.02.03 22:55:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 22:55:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 22:55:43 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 22:55:43 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 22:55:43 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.03 22:55:43 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.03 22:55:43 1: main::CallFn called by fhem.pl (1954)
2023.02.03 22:55:43 1: main::DoSet called by fhem.pl (1996)
2023.02.03 22:55:43 1: main::CommandSet called by fhem.pl (2904)
2023.02.03 22:55:43 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.03 22:55:43 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.03 22:55:43 1: main::FW_Notify called by fhem.pl (3976)
2023.02.03 22:55:43 1: main::CallFn called by fhem.pl (3888)
2023.02.03 22:55:43 1: main::DoTrigger called by fhem.pl (3222)
2023.02.03 22:55:43 1: main::CommandAttr called by (eval 5633) (1)
2023.02.03 22:55:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 22:55:43 1: readingsUpdate(TUYA_JL03,cur_power,80.2) missed to call readingsBeginUpdate first.
2023.02.03 22:55:43 1: stacktrace:
2023.02.03 22:55:43 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.02.03 22:55:43 1: main::readingsBulkUpdateIfChanged called by (eval 5675) (1)
2023.02.03 22:55:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 22:55:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 22:55:43 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 22:55:43 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 22:55:43 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.03 22:55:43 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.03 22:55:43 1: main::CallFn called by fhem.pl (1954)
2023.02.03 22:55:43 1: main::DoSet called by fhem.pl (1996)
2023.02.03 22:55:43 1: main::CommandSet called by fhem.pl (2904)
2023.02.03 22:55:43 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.03 22:55:43 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.03 22:55:43 1: main::FW_Notify called by fhem.pl (3976)
2023.02.03 22:55:43 1: main::CallFn called by fhem.pl (3888)
2023.02.03 22:55:43 1: main::DoTrigger called by fhem.pl (4995)
2023.02.03 22:55:43 1: main::readingsEndUpdate called by fhem.pl (5178)
2023.02.03 22:55:43 1: main::readingsSingleUpdate called by (eval 5673) (1)
2023.02.03 22:55:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 22:55:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 22:55:43 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 22:55:43 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 22:55:43 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.03 22:55:43 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.03 22:55:43 1: main::CallFn called by fhem.pl (1954)
2023.02.03 22:55:43 1: main::DoSet called by fhem.pl (1996)
2023.02.03 22:55:43 1: main::CommandSet called by fhem.pl (2904)
2023.02.03 22:55:43 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.03 22:55:43 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.03 22:55:43 1: main::FW_Notify called by fhem.pl (3976)
2023.02.03 22:55:43 1: main::CallFn called by fhem.pl (3888)
2023.02.03 22:55:43 1: main::DoTrigger called by fhem.pl (4995)
2023.02.03 22:55:43 1: main::readingsEndUpdate called by (eval 5660) (1)
2023.02.03 22:55:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 22:55:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 22:55:43 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 22:55:43 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 22:55:43 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.03 22:55:43 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.03 22:55:43 1: main::CallFn called by fhem.pl (1954)
2023.02.03 22:55:43 1: main::DoSet called by fhem.pl (1996)
2023.02.03 22:55:43 1: main::CommandSet called by fhem.pl (2904)
2023.02.03 22:55:43 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.03 22:55:43 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.03 22:55:43 1: main::FW_Notify called by fhem.pl (3976)
2023.02.03 22:55:43 1: main::CallFn called by fhem.pl (3888)
2023.02.03 22:55:43 1: main::DoTrigger called by fhem.pl (4995)
2023.02.03 22:55:43 1: main::readingsEndUpdate called by (eval 5655) (1)
2023.02.03 22:55:43 1: readingsUpdate(TUYA_JL04,cur_power,31.1) missed to call readingsBeginUpdate first.
2023.02.03 22:55:43 1: stacktrace:
2023.02.03 22:55:43 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.02.03 22:55:43 1: main::readingsBulkUpdateIfChanged called by (eval 5676) (1)
2023.02.03 22:55:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 22:55:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 22:55:43 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 22:55:43 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 22:55:43 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.03 22:55:43 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.03 22:55:43 1: main::CallFn called by fhem.pl (1954)
2023.02.03 22:55:43 1: main::DoSet called by fhem.pl (1996)
2023.02.03 22:55:43 1: main::CommandSet called by fhem.pl (2904)
2023.02.03 22:55:43 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.03 22:55:43 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.03 22:55:43 1: main::FW_Notify called by fhem.pl (3976)
2023.02.03 22:55:43 1: main::CallFn called by fhem.pl (3888)
2023.02.03 22:55:43 1: main::DoTrigger called by fhem.pl (4995)
2023.02.03 22:55:43 1: main::readingsEndUpdate called by fhem.pl (5178)
2023.02.03 22:55:43 1: main::readingsSingleUpdate called by (eval 5673) (1)
2023.02.03 22:55:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 22:55:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 22:55:43 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 22:55:43 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 22:55:43 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.03 22:55:43 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.03 22:55:43 1: main::CallFn called by fhem.pl (1954)
2023.02.03 22:55:43 1: main::DoSet called by fhem.pl (1996)
2023.02.03 22:55:43 1: main::CommandSet called by fhem.pl (2904)
2023.02.03 22:55:43 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.03 22:55:43 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.03 22:55:43 1: main::FW_Notify called by fhem.pl (3976)
2023.02.03 22:55:43 1: main::CallFn called by fhem.pl (3888)
2023.02.03 22:55:43 1: main::DoTrigger called by fhem.pl (4995)
2023.02.03 22:55:43 1: main::readingsEndUpdate called by (eval 5660) (1)
2023.02.03 22:55:43 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 22:55:43 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 22:55:43 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 22:55:43 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 22:55:43 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.03 22:55:43 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.03 22:55:43 1: main::CallFn called by fhem.pl (1954)
2023.02.03 22:55:43 1: main::DoSet called by fhem.pl (1996)
2023.02.03 22:55:43 1: main::CommandSet called by fhem.pl (2904)
2023.02.03 22:55:43 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.03 22:55:43 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.03 22:55:43 1: main::FW_Notify called by fhem.pl (3976)
2023.02.03 22:55:43 1: main::CallFn called by fhem.pl (3888)
2023.02.03 22:55:43 1: main::DoTrigger called by fhem.pl (4995)
2023.02.03 22:55:43 1: main::readingsEndUpdate called by (eval 5655) (1)
Nach Neustart, oder von wann? Bitte immer beide Logs, fhempy und FHEM
du hast wohl Recht:
2023.02.03 23:16:01 1: MaxTemp: WT
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_BULB01)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_BULB02)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_BULB03)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Camera1)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Camera2)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Camera3)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya_cloud: Camera4tuya_cloud_bf6b1900c331a78a2fkecw)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya_cloud: Camera5tuya_cloud_bfbeab33da30f5635ffj0r)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Camera6)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_DIY1)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_DIY3)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_DIY4)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_EMYLO1)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_EMYLO2)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_EMYLOD2)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_EMYLO3)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_EMYLO4)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL02)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL03)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL04)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL05)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL06)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL07)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL08)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL09)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL10Z)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL11Z)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL12Z)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL13)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL14)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL15)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL16)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL17)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL18)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL19)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL20)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL21)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL22)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL23)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL24)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL26)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL27)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL28)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL29)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL30)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL31)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL32)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL33)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL34)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL35)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_JL36)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_PS1)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_PS2)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_PS3)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_PS4)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_PS5)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_PS7)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_SCHF1)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_SCHF2)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_SCHF3)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_SCHF4)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_SP01)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_SP02)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_SP03)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_SP04)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_SP05)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_SP06)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_SP07)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_SP08)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_SP09)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_SP10)
2023.02.03 23:16:02 3: fhempy v1.0.0 (tuya: TUYA_SP11)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya: TUYA_SP12)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya: TUYA_SP13)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya: TUYA_SP14)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya: TUYA_SP15)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya: TUYA_SP16)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: TUYAC_PIR01)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: TUYAC_PIR02)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: TUYAC_PIR03)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya: TUYA_STF1)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya: TUYA_STF2)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya: TUYA_STF3)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya: TUYA_MMG)
2023.02.03 23:16:03 3: SST (SamsungSmartThingsConnector): define - CONNECTOR defined as SamsungSmartThingsConnector
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp01)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp02)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp03)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp04)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp05)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp06)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp07)
2023.02.03 23:16:03 1: PERL WARNING: Useless use of anonymous hash ({}) in void context at (eval 127) line 1, <$fh> line 6238.
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorT01)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorT02)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorT03)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorT04)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorT05)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorW01)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorW02)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorW03)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorW04)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Sir01)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Sir02)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Sir03)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Relais01)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorSmoke01)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bf16f1788a2fd6edd6pr1d)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bfc0750fc8af85f5d5vei7)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bfabd3dbaa5113764dzgkn)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_3367036770039f60ce2b)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_00673231e09806cbeaa2)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_453005615002911dfe06)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_720570712462ab27e625)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_887800042cf4325f15ef)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_52470320e09806c9a53f)
2023.02.03 23:16:03 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_00673231e09806cb13b0)
2023.02.03 23:16:03 3: freezemon defined freezemon freezemon
2023.02.03 23:16:03 1: Including ./log/fhem.save
2023.02.03 23:16:03 1: Messages collected while initializing FHEM:SecurityCheck:
WEB is not password protected
WEBtablet is not password protected
telnetPort is not password protected
MQTT2 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.03 23:16:04 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2023.02.03 23:16:04 3: alexa: starting
2023.02.03 23:16:04 3: alexa: using logfile: ./log/alexa-2023-02-03.log
2023.02.03 23:16:04 2: hueBridge1: autocreate: created 0/0/0 devices (ignored 0/2/26)
2023.02.03 23:16:06 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2023.02.03 23:16:06 2: [Freezemon] freezemon: ready to watch out for delays greater than 1 second(s)
2023.02.03 23:16:06 0: Featurelevel: 6.2
2023.02.03 23:16:06 0: Server started with 523 defined entities (fhem.pl:27110/2023-01-23 perl:5.032001 os:linux user:fhem pid:3262)
2023.02.03 23:16:06 3: DbLog dblog_THB - DB connection parameters are initialized in the SubProcess
2023.02.03 23:16:06 1: PERL WARNING: devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
2023.02.03 23:16:06 1: PERL WARNING: ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1310.
2023.02.03 23:16:07 3: alexa: read: end of file reached while sysread
2023.02.03 23:16:07 3: alexa: stopped
2023.02.03 23:16:07 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2023.02.03 23:16:07 3: alexa: starting
2023.02.03 23:16:07 3: alexa: using logfile: ./log/alexa-2023-02-03.log
2023.02.03 23:16:08 3: DbLog dblog_THB - DB connection parameters are stored in SubProcess
2023.02.03 23:16:09 2: AttrTemplates: got 258 entries
2023.02.03 23:16:10 2: {"token_type":"Bearer","access_token":"eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzUxMiJ9.eyJzdWIiOiJiNmU5ZDg5Ni1kMzMwLTRiMWYtODVhNS0wYjk4NGQyZWJiMDQiLCJhdWQiOiJVU0VSIiwic2NvcGUiOiJDVVNUT01FUl9BUEkiLCJpc3MiOiJvaWxmb3guaW8iLCJleHAiOjE2NzU0NjM0NjksImp0aSI6ImJiZWU2MWNiLWJhMDYtNDRhOC1iOTQ5LWQ4NTliY2RlMzQ4NCIsImVtYWlsIjoiYmt0QGdteC5uZXQifQ.bqm3zE5EGLDrwW-IivCYnDJBjjaXMna8WmOcu-QAOZpdJvUP4IvqwZQgRBfdEkzhMHOZ8HIOiEIw2lhmdBDVqQ","refresh_token":"eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzUxMiJ9.eyJzY29wZSI6IkNVU1RPTUVSX0FQSSIsImlzcyI6Im9pbGZveC5pbyIsImV4cCI6MTY3Njc1ODU2OSwianRpIjoiNTM0YmJiMDctNjAxOC00MzI1LWE3ZTUtOGEyYmU4NmVkOGQxIn0.bnRaHxs9-LoE1YvBuUURqAS3BoVRRcTpkfrjqWPJJPi5BVIweStH_HXkwfhJCFjzUlcQICgj_iufNMWOdpxfDQ"}
2023.02.03 23:16:46 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bfe1b5bb54592232acz7dg)
2023.02.03 23:16:49 1: [Freezemon] freezemon: possible freeze starting at 23:16:12, delay is 37.412 possibly caused by: tmr-BindingsIo_connectDev(local_pybinding)
2023.02.03 23:16:49 2: error while requesting https://api.oilfox.io/customer-api/v1/device - start_SSL https://api.oilfox.io:443 timed out
2023.02.03 23:16:49 2: hueBridge1: http request failed: read from https://192.168.9.179:443 timed out
2023.02.03 23:16:49 2: Buderus : km200_ParseHttpResponseInit - ERROR : /dhwCircuits: No proper Communication with Gateway: read from http://192.168.9.114:80 timed out
2023.02.03 23:16:49 2: Buderus : km200_ParseHttpResponseInit - ERROR : Timer restarted to try again in 10s
2023.02.03 23:16:50 1: PERL WARNING: Use of uninitialized value $value in string eq at ./FHEM/10_MAX.pm line 2057.
2023.02.03 23:16:50 1: PERL WARNING: Use of uninitialized value $value in string eq at ./FHEM/10_MAX.pm line 2058.
2023.02.03 23:16:51 3: DbLog dblog_THB - SubProcess connected to fhem
2023.02.03 23:16:51 1: [Freezemon] freezemon: possible freeze starting at 23:16:50, delay is 1.838 possibly caused by: tmr-TelegramBot_RestartPolling(TelegramBotTHB) tmr-HttpUtils_TimeoutErr(N/A) tmr-MQTT2_SERVER_keepaliveChecker(MQTT2) tmr-HttpUtils_TimeoutErr(N/A) tmr-DbRep_firstconnect(N/A) tmr-CODE(0x4c231f8)(GetUpdate) tmr-HttpUtils_TimeoutErr(N/A) tmr-CODE(0x4c231f8)(GetUpdate) tmr-DbLog_execMemCacheAsync(dblog_THB) tmr-CUL_MAX_BroadcastTime(MaxSystem) tmr-FW_closeInactiveClients(N/A)
2023.02.03 23:16:52 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bf0982f08295070ae7tulb)
2023.02.03 23:16:53 1: [Freezemon] freezemon: possible freeze starting at 23:16:52, delay is 1.907 possibly caused by: tmr-CUL_MAX_SQH(MaxSystem) tmr-CUL_HandleWriteQueue(CUL_0)
das könnte an den MAX-Credits liegen
könntest Du ein wenig länger warten
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 541, in create_device
await self._create_cloudmapping_dev()
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 434, in _create_cloudmapping_dev
await self.check_tuya_attributes()
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 346, in check_tuya_attributes
self.tuya_spec_functions = ast.literal_eval(self.tuya_spec_functions)
File "/usr/lib/python3.9/ast.py", line 62, in literal_eval
node_or_string = parse(node_or_string, mode='eval')
File "/usr/lib/python3.9/ast.py", line 50, in parse
return compile(source, filename, mode, flags,
File "<unknown>", line 0
SyntaxError: unexpected EOF while parsing
2023-02-03 22:55:43,392 - ERROR - TUYA_SP09: Failed create_device
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 541, in create_device
await self._create_cloudmapping_dev()
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 434, in _create_cloudmapping_dev
await self.check_tuya_attributes()
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 346, in check_tuya_attributes
self.tuya_spec_functions = ast.literal_eval(self.tuya_spec_functions)
File "/usr/lib/python3.9/ast.py", line 62, in literal_eval
node_or_string = parse(node_or_string, mode='eval')
File "/usr/lib/python3.9/ast.py", line 50, in parse
return compile(source, filename, mode, flags,
File "<unknown>", line 0
SyntaxError: unexpected EOF while parsing
2023-02-03 23:16:05,048 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.589...
2023-02-03 23:16:05,052 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-02-03 23:16:05,090 - INFO - websockets.server: server listening on 0.0.0.0:15733
2023-02-03 23:16:11,577 - INFO - websockets.server: connection open
2023-02-03 23:16:11,577 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2023-02-03 23:16:18,642 - ERROR - TUYA: Please activate OpenPulsar: https://developer.tuya.com/en/docs/iot/subscribe-mq?id=Kavqcrvckbh9h
2023-02-03 23:16:27,739 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com
2023-02-03 23:16:27,745 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com
2023-02-03 23:16:27,747 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com
2023-02-03 23:16:27,751 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com
2023-02-03 23:16:27,755 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com
2023-02-03 23:16:27,760 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com
2023-02-03 23:16:27,868 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com
2023-02-03 23:16:27,890 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com
2023-02-03 23:16:27,995 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com
2023-02-03 23:17:48,280 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_PS5', 'dp_104', '')
2023-02-03 23:17:48,280 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_SP11', 'dp_19', '')
2023-02-03 23:17:48,281 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_SP15', 'tuya_spec_functions', '')
2023-02-03 23:17:48,284 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_SP14', 'tuya_spec_functions', '')
2023-02-03 23:17:48,287 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_SP13', 'tuya_spec_functions', '')
2023-02-03 23:17:48,290 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'TUYA_BULB03'});;
2023-02-03 23:17:48,291 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'TUYA_SP07'});;
2023-02-03 23:17:48,293 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'TUYA_SP06'});;
2023-02-03 23:17:48,295 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP02'},'dp_24','21815');;
2023-02-03 23:17:48,299 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsSingleUpdate($defs{'TUYA_Temp04'},'state','ready',1)
2023-02-03 23:17:48,301 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP01'},'dp_24','21782');;
2023-02-03 23:17:48,303 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_PS1', 'dp_02', '')
2023-02-03 23:17:48,304 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP03'},'dp_24','0');;
2023-02-03 23:17:48,307 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_SP12', 'dp_20', '')
2023-02-03 23:17:48,309 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_SP09', 'dp_18', '')
2023-02-03 23:17:48,311 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP05'},'cur_voltage','213.7');;
2023-02-03 23:17:48,313 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_SP08', 'dp_18', '')
2023-02-03 23:17:48,314 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_PS7', 'dp_12', '')
2023-02-03 23:17:48,419 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'TUYA_Temp01'},'create_time','1644673048');;
2023-02-03 23:17:48,420 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_PS4', 'dp_07', '')
2023-02-03 23:17:48,421 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'TUYA_JL04'});;
2023-02-03 23:17:48,421 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'TUYA_SP14'});;
2023-02-03 23:17:48,422 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'TUYA_JL03'});;
2023-02-03 23:17:53,698 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_887800042cf4325f15ef'},'icon','https://images.tuyaeu.com/smart/icon/dj.png');;
2023-02-03 23:17:53,700 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_STF1', 'tuya_spec_status', '')
2023-02-03 23:17:53,701 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'TUYA_Temp03'},'id','bf14f376fe39bc2648iaeu');;
2023-02-03 23:17:53,706 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_bfe1b5bb54592232acz7dg'},'id','bfe1b5bb54592232acz7dg');;
2023-02-03 23:17:53,708 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'TUYA_Temp05'},'id','bfe1b5bb54592232acz7dg');;
2023-02-03 23:17:53,709 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'TUYA_Temp07'},'id','bfabd3dbaa5113764dzgkn');;
2023-02-03 23:17:53,711 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'TUYA_Temp06'},'id','bfc0750fc8af85f5d5vei7');;
2023-02-03 23:17:53,713 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_00673231e09806cb13b0'},'id','00673231e09806cb13b0');;
2023-02-03 23:17:53,715 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_00673231e09806cbeaa2'},'id','00673231e09806cbeaa2');;
2023-02-03 23:17:53,716 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_3367036770039f60ce2b'},'id','3367036770039f60ce2b');;
2023-02-03 23:17:53,718 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_SP16', 'dp_01', '')
2023-02-03 23:17:53,833 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_453005615002911dfe06'},'id','453005615002911dfe06');;
2023-02-03 23:17:53,833 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_52470320e09806c9a53f'},'id','52470320e09806c9a53f');;
2023-02-03 23:17:53,834 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'tuya_cloud_720570712462ab27e625'},'id','720570712462ab27e625');;
2023-02-03 23:17:53,718 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_SP16', 'dp_01', '')
ja das ein aktives Device; wenn ist nicht antwortet wird es wohl doppelt angelegt ;-)
2023.02.03 23:16:49 1: [Freezemon] freezemon: possible freeze starting at 23:16:12, delay is 37.412 possibly caused by: tmr-BindingsIo_connectDev(local_pybinding)
Die Zeile irritiert mich. Mach bitte nur einen fhempy Neustart (nicht FHEM!) und schau was dann in beiden Logs passiert.
erneuter Start:
2023-02-03 23:30:02,964 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_SP11', 'tuya_spec_status', '')
2023-02-03 23:30:02,966 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_SP16', 'tuya_spec_status', '[]')
2023-02-03 23:30:02,966 - ERROR - TUYA_SP16: Failed create_device
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 541, in create_device
await self._create_cloudmapping_dev()
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 434, in _create_cloudmapping_dev
await self.check_tuya_attributes()
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 347, in check_tuya_attributes
self.tuya_spec_status = ast.literal_eval(self.tuya_spec_status)
File "/usr/lib/python3.9/ast.py", line 62, in literal_eval
node_or_string = parse(node_or_string, mode='eval')
File "/usr/lib/python3.9/ast.py", line 50, in parse
return compile(source, filename, mode, flags,
File "<unknown>", line 0
SyntaxError: unexpected EOF while parsing
2023-02-03 23:30:02,969 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_SP13', 'tuya_spec_status', '[]')
2023-02-03 23:30:02,969 - ERROR - TUYA_SP13: Failed create_device
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 541, in create_device
await self._create_cloudmapping_dev()
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 434, in _create_cloudmapping_dev
await self.check_tuya_attributes()
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 347, in check_tuya_attributes
self.tuya_spec_status = ast.literal_eval(self.tuya_spec_status)
File "/usr/lib/python3.9/ast.py", line 62, in literal_eval
node_or_string = parse(node_or_string, mode='eval')
File "/usr/lib/python3.9/ast.py", line 50, in parse
return compile(source, filename, mode, flags,
File "<unknown>", line 0
SyntaxError: unexpected EOF while parsing
2023-02-03 23:30:02,970 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_JL32', 'dp_06', '')
2023-02-03 23:30:02,970 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_SP15', 'tuya_spec_status', '[]')
2023-02-03 23:30:02,971 - ERROR - TUYA_SP15: Failed create_device
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 541, in create_device
await self._create_cloudmapping_dev()
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 434, in _create_cloudmapping_dev
await self.check_tuya_attributes()
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 347, in check_tuya_attributes
self.tuya_spec_status = ast.literal_eval(self.tuya_spec_status)
File "/usr/lib/python3.9/ast.py", line 62, in literal_eval
node_or_string = parse(node_or_string, mode='eval')
File "/usr/lib/python3.9/ast.py", line 50, in parse
return compile(source, filename, mode, flags,
File "<unknown>", line 0
SyntaxError: unexpected EOF while parsing
2023-02-03 23:30:02,971 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_SP10', 'tuya_spec_functions', '')
2023-02-03 23:30:02,971 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_JL33', 'dp_01', '')
2023-02-03 23:30:02,972 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_SP12', 'tuya_spec_functions', '[]')
2023-02-03 23:30:02,973 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_STF1', 'tuya_spec_functions', '[]')
2023-02-03 23:30:02,974 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'TUYA_JL04'});;
2023-02-03 23:30:04,492 - ERROR - TUYA_SP14: Failed create_device
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 541, in create_device
await self._create_cloudmapping_dev()
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 434, in _create_cloudmapping_dev
await self.check_tuya_attributes()
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 346, in check_tuya_attributes
self.tuya_spec_functions = ast.literal_eval(self.tuya_spec_functions)
File "/usr/lib/python3.9/ast.py", line 62, in literal_eval
node_or_string = parse(node_or_string, mode='eval')
File "/usr/lib/python3.9/ast.py", line 50, in parse
return compile(source, filename, mode, flags,
File "<unknown>", line 0
SyntaxError: unexpected EOF while parsing
2023-02-03 23:30:05,068 - ERROR - TUYA_SP12: Failed create_device
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 541, in create_device
await self._create_cloudmapping_dev()
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 434, in _create_cloudmapping_dev
await self.check_tuya_attributes()
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 346, in check_tuya_attributes
self.tuya_spec_functions = ast.literal_eval(self.tuya_spec_functions)
File "/usr/lib/python3.9/ast.py", line 62, in literal_eval
node_or_string = parse(node_or_string, mode='eval')
File "/usr/lib/python3.9/ast.py", line 50, in parse
return compile(source, filename, mode, flags,
File "<unknown>", line 0
SyntaxError: unexpected EOF while parsing
2023-02-03 23:30:05,116 - ERROR - TUYA_STF1: Failed create_device
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 541, in create_device
await self._create_cloudmapping_dev()
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 434, in _create_cloudmapping_dev
await self.check_tuya_attributes()
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 346, in check_tuya_attributes
self.tuya_spec_functions = ast.literal_eval(self.tuya_spec_functions)
File "/usr/lib/python3.9/ast.py", line 62, in literal_eval
node_or_string = parse(node_or_string, mode='eval')
File "/usr/lib/python3.9/ast.py", line 50, in parse
return compile(source, filename, mode, flags,
File "<unknown>", line 0
SyntaxError: unexpected EOF while parsing
2023-02-03 23:30:08,025 - ERROR - fhempy.lib.fhem: FHEM took 5083ms for CommandAttr(undef, "TUYA_Temp01 room fhempy")
2023-02-03 23:30:08,259 - ERROR - fhempy.lib.fhem: FHEM took 5321ms for CommandAttr(undef, "TUYA_SP04 dp_01 switch_1")
2023-02-03 23:30:08,509 - ERROR - fhempy.lib.fhem: FHEM took 5588ms for CommandAttr(undef, "TUYA_JL35 dp_01 switch_1")
2023-02-03 23:30:08,635 - ERROR - fhempy.lib.fhem: FHEM took 5715ms for CommandAttr(undef, "TUYA_JL34 dp_01 switch_1")
2023-02-03 23:30:08,856 - ERROR - fhempy.lib.fhem: FHEM took 5937ms for CommandAttr(undef, "TUYA_JL26 dp_01 switch_1")
2023-02-03 23:30:09,220 - ERROR - fhempy.lib.fhem: FHEM took 6301ms for CommandAttr(undef, "TUYA_SCHF2 dp_02 switch_2")
2023-02-03 23:30:09,334 - ERROR - fhempy.lib.fhem: FHEM took 6416ms for CommandAttr(undef, "TUYA_SCHF1 dp_07 countdown_1")
2023-02-03 23:30:09,335 - ERROR - fhempy.lib.fhem: FHEM took 6418ms for readingsSingleUpdate($defs{'TUYA_STF3'},'state','Change DEF and use IP instead of \'offline\'',1)
2023-02-03 23:30:09,457 - ERROR - fhempy.lib.fhem: FHEM took 6540ms for CommandAttr(undef, "TUYA_JL04 dp_04 cur_current")
2023-02-03 23:30:09,712 - ERROR - fhempy.lib.fhem: FHEM took 6795ms for CommandAttr(undef, "TUYA_JL15 dp_02 countdown_1")
2023-02-03 23:30:09,841 - ERROR - fhempy.lib.fhem: FHEM took 6924ms for CommandAttr(undef, "TUYA_JL31 dp_04 cur_current")
2023-02-03 23:30:10,433 - ERROR - fhempy.lib.fhem: FHEM took 7517ms for CommandAttr(undef, "TUYA_JL13 dp_02 countdown_1")
[code]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.03 23:28:27 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2023.02.03 23:28:27 3: alexa: starting
2023.02.03 23:28:27 3: alexa: using logfile: ./log/alexa-2023-02-03.log
2023.02.03 23:28:27 2: hueBridge1: autocreate: created 0/0/0 devices (ignored 0/2/26)
2023.02.03 23:28:28 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2023.02.03 23:28:28 0: Featurelevel: 6.2
2023.02.03 23:28:28 0: Server started with 512 defined entities (fhem.pl:27110/2023-01-23 perl:5.032001 os:linux user:fhem pid:3990)
2023.02.03 23:28:28 3: DbLog dblog_THB - DB connection parameters are initialized in the SubProcess
2023.02.03 23:28:28 1: PERL WARNING: devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
2023.02.03 23:28:28 1: PERL WARNING: ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1310.
2023.02.03 23:28:29 3: alexa: read: end of file reached while sysread
2023.02.03 23:28:29 3: alexa: stopped
2023.02.03 23:28:29 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2023.02.03 23:28:29 3: alexa: starting
2023.02.03 23:28:29 3: alexa: using logfile: ./log/alexa-2023-02-03.log
2023.02.03 23:28:30 3: DbLog dblog_THB - DB connection parameters are stored in SubProcess
2023.02.03 23:28:30 2: AttrTemplates: got 258 entries
2023.02.03 23:28:37 2: error while requesting https://api.oilfox.io/customer-api/v1/login - start_SSL https://api.oilfox.io:443 timed out
2023.02.03 23:28:37 2: Buderus : km200_ParseHttpResponseInit - ERROR : /: No proper Communication with Gateway: read from http://192.168.9.114:80 timed out
2023.02.03 23:28:37 2: Buderus : km200_ParseHttpResponseInit - ERROR : Timer restarted to try again in 10s
2023.02.03 23:28:38 2: hueBridge1: http request failed: https://192.168.9.179/auth/v1: empty answer received
2023.02.03 23:28:40 2: hueBridge1: http request failed: https://192.168.9.179/eventstream/clip/v2: empty answer received
2023.02.03 23:28:40 2: hueBridge1: EventStream: terminated; retrying later
2023.02.03 23:29:02 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bf16f1788a2fd6edd6pr1d)
2023.02.03 23:29:04 3: DbLog dblog_THB - SubProcess connected to fhem
2023.02.03 23:29:06 1: PERL WARNING: Use of uninitialized value $value in string eq at ./FHEM/10_MAX.pm line 2057.
2023.02.03 23:29:06 1: PERL WARNING: Use of uninitialized value $value in string eq at ./FHEM/10_MAX.pm line 2058.
2023.02.03 23:29:07 2: hueBridge1: autocreate: created 0/0/0 devices (ignored 0/2/26)
2023.02.03 23:29:27 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_3367036770039f60ce2b)
2023.02.03 23:29:36 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bf4ae6b15fe239b42bxvpl)
2023.02.03 23:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_17710212600194dba99d)
2023.02.03 23:30:02 3: Untergeschoss_Rollo_2_down_Notify return value: OK
2023.02.03 23:30:04 3: Untergeschoss_Rollo_3_down_Notify return value: OK
2023.02.03 23:30:04 1: readingsUpdate(TUYA_JL04,cur_current,215.0) missed to call readingsBeginUpdate first.
2023.02.03 23:30:04 1: stacktrace:
2023.02.03 23:30:04 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.02.03 23:30:04 1: main::readingsBulkUpdateIfChanged called by (eval 3748) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (414)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3747) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3746) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3745) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3743) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.03 23:30:04 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (784)
2023.02.03 23:30:04 1: readingsUpdate(TUYA_DIY3,state,off) missed to call readingsBeginUpdate first.
2023.02.03 23:30:04 1: stacktrace:
2023.02.03 23:30:04 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.02.03 23:30:04 1: main::readingsBulkUpdateIfChanged called by (eval 3798) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3794) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3790) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3777) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3771) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3763) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: readingsUpdate(TUYA_DIY1,state,off) missed to call readingsBeginUpdate first.
2023.02.03 23:30:04 1: stacktrace:
2023.02.03 23:30:04 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.02.03 23:30:04 1: main::readingsBulkUpdateIfChanged called by (eval 3800) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3799) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3794) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3790) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3777) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3771) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: readingsUpdate(TUYA_DIY4,state,off) missed to call readingsBeginUpdate first.
2023.02.03 23:30:04 1: stacktrace:
2023.02.03 23:30:04 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.02.03 23:30:04 1: main::readingsBulkUpdateIfChanged called by (eval 3805) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3804) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3801) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3799) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3794) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3790) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: readingsUpdate(TUYA_JL09,state,off) missed to call readingsBeginUpdate first.
2023.02.03 23:30:04 1: stacktrace:
2023.02.03 23:30:04 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.02.03 23:30:04 1: main::readingsBulkUpdateIfChanged called by (eval 3812) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3811) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3810) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3809) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3808) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3807) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: readingsUpdate(TUYA_JL11Z,state,off) missed to call readingsBeginUpdate first.
2023.02.03 23:30:04 1: stacktrace:
2023.02.03 23:30:04 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.02.03 23:30:04 1: main::readingsBulkUpdateIfChanged called by (eval 3814) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3813) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3811) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3810) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3809) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3808) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: readingsUpdate(TUYA_JL12Z,online,1) missed to call readingsBeginUpdate first.
2023.02.03 23:30:04 1: stacktrace:
2023.02.03 23:30:04 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.02.03 23:30:04 1: main::readingsBulkUpdateIfChanged called by (eval 3816) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3813) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3811) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3810) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3809) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3808) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:05 1: readingsUpdate(TUYA_JL04,cur_power,31.7) missed to call readingsBeginUpdate first.
2023.02.03 23:30:05 1: stacktrace:
2023.02.03 23:30:05 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.02.03 23:30:05 1: main::readingsBulkUpdateIfChanged called by (eval 3836) (1)
2023.02.03 23:30:05 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:05 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:05 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:05 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:05 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:05 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:05 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:05 1: main::CommandAttr called by (eval 3828) (1)
2023.02.03 23:30:05 1: (eval) &n
Zitat von: dominik am 03 Februar 2023, 23:32:05
2023.02.03 23:16:49 1: [Freezemon] freezemon: possible freeze starting at 23:16:12, delay is 37.412 possibly caused by: tmr-BindingsIo_connectDev(local_pybinding)
Die Zeile irritiert mich. Mach bitte nur einen fhempy Neustart (nicht FHEM!) und schau was dann in beiden Logs passiert.
wird gemacht
fhem log:
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.03 23:28:27 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2023.02.03 23:28:27 3: alexa: starting
2023.02.03 23:28:27 3: alexa: using logfile: ./log/alexa-2023-02-03.log
2023.02.03 23:28:27 2: hueBridge1: autocreate: created 0/0/0 devices (ignored 0/2/26)
2023.02.03 23:28:28 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2023.02.03 23:28:28 0: Featurelevel: 6.2
2023.02.03 23:28:28 0: Server started with 512 defined entities (fhem.pl:27110/2023-01-23 perl:5.032001 os:linux user:fhem pid:3990)
2023.02.03 23:28:28 3: DbLog dblog_THB - DB connection parameters are initialized in the SubProcess
2023.02.03 23:28:28 1: PERL WARNING: devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
2023.02.03 23:28:28 1: PERL WARNING: ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1310.
2023.02.03 23:28:29 3: alexa: read: end of file reached while sysread
2023.02.03 23:28:29 3: alexa: stopped
2023.02.03 23:28:29 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2023.02.03 23:28:29 3: alexa: starting
2023.02.03 23:28:29 3: alexa: using logfile: ./log/alexa-2023-02-03.log
2023.02.03 23:28:30 3: DbLog dblog_THB - DB connection parameters are stored in SubProcess
2023.02.03 23:28:30 2: AttrTemplates: got 258 entries
2023.02.03 23:28:37 2: error while requesting https://api.oilfox.io/customer-api/v1/login - start_SSL https://api.oilfox.io:443 timed out
2023.02.03 23:28:37 2: Buderus : km200_ParseHttpResponseInit - ERROR : /: No proper Communication with Gateway: read from http://192.168.9.114:80 timed out
2023.02.03 23:28:37 2: Buderus : km200_ParseHttpResponseInit - ERROR : Timer restarted to try again in 10s
2023.02.03 23:28:38 2: hueBridge1: http request failed: https://192.168.9.179/auth/v1: empty answer received
2023.02.03 23:28:40 2: hueBridge1: http request failed: https://192.168.9.179/eventstream/clip/v2: empty answer received
2023.02.03 23:28:40 2: hueBridge1: EventStream: terminated; retrying later
2023.02.03 23:29:02 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bf16f1788a2fd6edd6pr1d)
2023.02.03 23:29:04 3: DbLog dblog_THB - SubProcess connected to fhem
2023.02.03 23:29:06 1: PERL WARNING: Use of uninitialized value $value in string eq at ./FHEM/10_MAX.pm line 2057.
2023.02.03 23:29:06 1: PERL WARNING: Use of uninitialized value $value in string eq at ./FHEM/10_MAX.pm line 2058.
2023.02.03 23:29:07 2: hueBridge1: autocreate: created 0/0/0 devices (ignored 0/2/26)
2023.02.03 23:29:27 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_3367036770039f60ce2b)
2023.02.03 23:29:36 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_bf4ae6b15fe239b42bxvpl)
2023.02.03 23:29:42 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_17710212600194dba99d)
2023.02.03 23:30:02 3: Untergeschoss_Rollo_2_down_Notify return value: OK
2023.02.03 23:30:04 3: Untergeschoss_Rollo_3_down_Notify return value: OK
2023.02.03 23:30:04 1: readingsUpdate(TUYA_JL04,cur_current,215.0) missed to call readingsBeginUpdate first.
2023.02.03 23:30:04 1: stacktrace:
2023.02.03 23:30:04 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.02.03 23:30:04 1: main::readingsBulkUpdateIfChanged called by (eval 3748) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (414)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3747) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3746) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3745) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3743) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.03 23:30:04 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (784)
2023.02.03 23:30:04 1: readingsUpdate(TUYA_DIY3,state,off) missed to call readingsBeginUpdate first.
2023.02.03 23:30:04 1: stacktrace:
2023.02.03 23:30:04 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.02.03 23:30:04 1: main::readingsBulkUpdateIfChanged called by (eval 3798) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3794) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3790) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3777) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3771) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3763) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: readingsUpdate(TUYA_DIY1,state,off) missed to call readingsBeginUpdate first.
2023.02.03 23:30:04 1: stacktrace:
2023.02.03 23:30:04 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.02.03 23:30:04 1: main::readingsBulkUpdateIfChanged called by (eval 3800) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3799) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3794) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3790) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3777) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3771) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: readingsUpdate(TUYA_DIY4,state,off) missed to call readingsBeginUpdate first.
2023.02.03 23:30:04 1: stacktrace:
2023.02.03 23:30:04 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.02.03 23:30:04 1: main::readingsBulkUpdateIfChanged called by (eval 3805) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3804) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3801) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3799) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3794) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3790) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: readingsUpdate(TUYA_JL09,state,off) missed to call readingsBeginUpdate first.
2023.02.03 23:30:04 1: stacktrace:
2023.02.03 23:30:04 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.02.03 23:30:04 1: main::readingsBulkUpdateIfChanged called by (eval 3812) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3811) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3810) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3809) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3808) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3807) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: readingsUpdate(TUYA_JL11Z,state,off) missed to call readingsBeginUpdate first.
2023.02.03 23:30:04 1: stacktrace:
2023.02.03 23:30:04 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.02.03 23:30:04 1: main::readingsBulkUpdateIfChanged called by (eval 3814) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3813) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3811) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3810) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3809) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3808) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: readingsUpdate(TUYA_JL12Z,online,1) missed to call readingsBeginUpdate first.
2023.02.03 23:30:04 1: stacktrace:
2023.02.03 23:30:04 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.02.03 23:30:04 1: main::readingsBulkUpdateIfChanged called by (eval 3816) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3813) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3811) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3810) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3809) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:04 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:04 1: main::CommandAttr called by (eval 3808) (1)
2023.02.03 23:30:04 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:04 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:04 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:04 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:04 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:04 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:05 1: readingsUpdate(TUYA_JL04,cur_power,31.7) missed to call readingsBeginUpdate first.
2023.02.03 23:30:05 1: stacktrace:
2023.02.03 23:30:05 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.02.03 23:30:05 1: main::readingsBulkUpdateIfChanged called by (eval 3836) (1)
2023.02.03 23:30:05 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:05 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:05 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:05 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:05 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:05 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:05 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:05 1: main::CommandAttr called by (eval 3828) (1)
2023.02.03 23:30:05 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:05 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:05 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:05 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:05 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:05 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:05 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:05 1: main::CommandAttr called by (eval 3826) (1)
2023.02.03 23:30:05 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:05 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:05 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:05 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:05 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:05 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:05 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:05 1: main::CommandAttr called by (eval 3820) (1)
2023.02.03 23:30:05 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:05 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:05 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:05 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:05 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:05 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:05 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:05 1: main::CommandAttr called by (eval 3818) (1)
2023.02.03 23:30:05 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:05 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:05 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:05 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:05 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:05 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:05 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:05 1: main::CommandAttr called by (eval 3813) (1)
2023.02.03 23:30:05 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:05 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:05 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:05 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:05 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:05 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:05 1: readingsUpdate(TUYA_JL12Z,state,ready) missed to call readingsBeginUpdate first.
2023.02.03 23:30:05 1: stacktrace:
2023.02.03 23:30:05 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.02.03 23:30:05 1: main::readingsBulkUpdateIfChanged called by (eval 3886) (1)
2023.02.03 23:30:05 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:05 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:05 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:05 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:05 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.03 23:30:05 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.03 23:30:05 1: main::CallFn called by fhem.pl (1954)
2023.02.03 23:30:05 1: main::DoSet called by fhem.pl (1996)
2023.02.03 23:30:05 1: main::CommandSet called by fhem.pl (2904)
2023.02.03 23:30:05 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.03 23:30:05 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.03 23:30:05 1: main::FW_Notify called by fhem.pl (3976)
2023.02.03 23:30:05 1: main::CallFn called by fhem.pl (3888)
2023.02.03 23:30:05 1: main::DoTrigger called by fhem.pl (4995)
2023.02.03 23:30:05 1: main::readingsEndUpdate called by (eval 3867) (1)
2023.02.03 23:30:05 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:05 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 23:30:05 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.03 23:30:05 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.03 23:30:05 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.03 23:30:05 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.03 23:30:05 1: main::CallFn called by fhem.pl (3198)
2023.02.03 23:30:05 1: main::CommandAttr called by (eval 3828) (1)
2023.02.03 23:30:05 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 23:30:05 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
SyntaxError: unexpected EOF while parsing
2023-02-03 23:32:06,394 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'TUYAC_SensorW01'},'product_id','SmFKLTOcGHbPQvmh');;
2023-02-03 23:32:06,394 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'Camera5tuya_cloud_bfbeab33da30f5635ffj0r'},'product_name','Smart Camera');;
2023-02-03 23:32:06,395 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'TUYAC_SensorT03'},'product_id','6l4vhjl3gttstgxj');;
2023-02-03 23:32:06,395 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'TUYAC_SensorT04'},'product_id','hx5ztlztij4yxxvg');;
2023-02-03 23:32:06,395 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'TUYAC_SensorT02'},'product_id','6l4vhjl3gttstgxj');;
2023-02-03 23:32:06,396 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'TUYAC_SensorSmoke01'},'product_id','powevvypruxyou2z');;
2023-02-03 23:32:06,396 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'TUYAC_SensorT01'},'product_id','6l4vhjl3gttstgxj');;
2023-02-03 23:32:06,407 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'TUYAC_Camera6'},'product_name','Smart Camera');;
2023-02-03 23:32:06,407 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'TUYAC_Camera1'},'product_id','jyqwiknzooocjhqc');;
2023-02-03 23:32:06,407 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'TUYAC_Camera3'},'product_id','v86uW5IC1RYLFN6q');;
2023-02-03 23:32:06,408 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'Camera4tuya_cloud_bf6b1900c331a78a2fkecw'},'product_id','jyqwiknzooocjhqc');;
2023-02-03 23:32:06,408 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: AttrVal('TUYA_SP11', 'dp_23', '')
2023-02-03 23:32:06,408 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: CommandAttr(undef, "TUYA_JL20 dp_06 cur_voltage")
2023-02-03 23:32:06,408 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: CommandAttr(undef, "TUYA_JL36 dp_06 cur_voltage")
2023-02-03 23:32:06,409 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'TUYAC_Sir01'},'online','off');;
2023-02-03 23:36:19,424 - INFO - fhempy.lib.fhem_pythonbinding: Restart initiated...
2023-02-03 23:36:19,546 - INFO - fhempy.lib.fhem_pythonbinding: All modules successfully undefined!
2023-02-03 23:36:19,548 - INFO - websockets.server: server closing
2023-02-03 23:36:19,548 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 364, in listener
fut.set_result(rmsg)
asyncio.exceptions.InvalidStateError: invalid state
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 217, in _onMessage
await self.handle_message(msg, hash)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 227, in handle_message
listener["func"](msg)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 366, in listener
logger.error("Failed to set result, received: " + rmsg)
TypeError: can only concatenate str (not "dict") to str
2023-02-03 23:36:19,550 - ERROR - fhempy.lib.fhem_pythonbinding: fhempy failed to handle message with hash: {'error': 0, 'awaitId': 43250103, 'result': None}
2023-02-03 23:36:19,550 - ERROR - fhempy.lib.fhem_pythonbinding: Failed to handle message: b'{"error":0,"awaitId":43250103,"result":null}'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 364, in listener
fut.set_result(rmsg)
asyncio.exceptions.InvalidStateError: invalid state
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 217, in _onMessage
await self.handle_message(msg, hash)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 227, in handle_message
listener["func"](msg)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py", line 366, in listener
logger.error("Failed to set result, received: " + rmsg)
TypeError: can only concatenate str (not "dict") to str
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 186, in onMessage
await self._onMessage(payload)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 220, in _onMessage
await self.sendBackError(hash, "fhempy failed to handle message")
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 135, in sendBackError
duration = (time.time() - id_received_timestamp[retHash["id"]]) * 1000
KeyError: 'id'
2023-02-03 23:36:29,554 - INFO - websockets.server: connection closed
2023-02-03 23:36:29,554 - INFO - websockets.server: server closed
2023-02-03 23:36:29,556 - INFO - fhempy.lib.fhem_pythonbinding: Exit 1
2023-02-03 23:36:30,870 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.589...
2023-02-03 23:36:30,874 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-02-03 23:36:30,907 - INFO - websockets.server: server listening on 0.0.0.0:15733
2023-02-03 23:36:39,828 - INFO - websockets.server: connection open
2023-02-03 23:36:39,829 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2023-02-03 23:36:42,922 - ERROR - TUYA: Please activate OpenPulsar: https://developer.tuya.com/en/docs/iot/subscribe-mq?id=Kavqcrvckbh9h
2023-02-03 23:36:52,015 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com
2023-02-03 23:36:52,048 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com
und FHEM Log? Bitte IMMER beide Logs
Noch ganz kurz von mir. Habe auch MAX :-) Habe da aber kein Problem mit Credits.
Bei mir war es im Log ruhig heute.
Das einzige war im fhempy.log aber nicht viel.
2023-02-03 11:31:56,379 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'Fernseher_bfb7810a3e397c5fa4u7ud'},'add_ele','0.005');;
2023-02-03 11:31:56,380 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'Sybille_Tablet_bf68d9b41c16be3713vcc1'},'cycle_time','');;
2023-02-03 11:31:56,381 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'Fernseher_Wohnzimmer_bf7bbcb9a4b03a2c97cqid'},'cur_power','0.0');;
2023-02-03 11:31:56,382 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'Stefan_Tablet_bf0572e0fb6ccbe356ykuh'},'cur_voltage','230.2');;
2023-02-03 11:31:56,383 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'Computer_Stefan_bf881b7977c814af88jmrc'},'cur_current','407.0');;
2023-02-03 11:31:56,757 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'tuya_local_bf4f644bc7dd2fc71d9q52'});;
2023-02-03 19:58:09,540 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsEndUpdate($defs{'Fernseher_Schlafzimmer_bf4f644bc7dd2fc71d9q52'},1);;
2023-02-03 19:58:09,543 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'Fernseher_bfb7810a3e397c5fa4u7ud'},'random_time','');;
2023-02-03 19:58:09,544 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsEndUpdate($defs{'Fernseher_Wohnzimmer_bf7bbcb9a4b03a2c97cqid'},1);;
Im fhem.log nur einmal etwas nämlich zu dem um 11:31:56, zu den anderen ist nichts da.
Auch sonst sehe ich nichts auffälliges im Log.
2023.02.03 11:31:56 1: readingsUpdate(tuya_local_bf4f644bc7dd2fc71d9q52,state,off) missed to call readingsBeginUpdate first.
2023.02.03 11:31:56 1: stacktrace:
2023.02.03 11:31:56 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.02.03 11:31:56 1: main::readingsBulkUpdateIfChanged called by (eval 97520) (1)
2023.02.03 11:31:56 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 11:31:56 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 11:31:56 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.03 11:31:56 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.03 11:31:56 1: main::CallFn called by fhem.pl (784)
Danke und Gruß,
Stefan
Zitat von: dominik am 03 Februar 2023, 23:47:07
und FHEM Log? Bitte IMMER beide Logs
siehe eins zuvor
habe inzwischen den room fhempy von doppelten durch delete einzeln bereinigt:
ya_cloud
Camera1 Hauseingang
ready
Camera2
ready
Camera3 Garage
ready
Camera4 Garten
ready
Camera5
ready
Camera6 Terrasse
ready
PIR Sensor 1
nomotion
PIR Sensor 2
nomotion
PIR Sensor 3
nomotion
RELAIS01 Emylo Garagentor
on
off
SensorT01 Haustüre
ready
SensorT02
ready
SensorT03
ready
SensorT04
open
SensorT05 Rolltor Garage
closed
Sirene 1 Temp
not support this device
Sirene 2 Temp
not support this device
Sirene 3 Temp
ready
Smoke Alarm
normal
Wassersensor 1 Küche
2
Wassersensor 2 Heizraum
2
Wassersensor 3 Waschmaschine
2
Wassersensor 4 Terrasse
normaldas sind nun nur noch die erwünschten
room baut nach ca. 2 sek auf
fhempy ist wohl im Hintergrund auf der Suche und verharrt so:
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 186, in onMessage
await self._onMessage(payload)
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 220, in _onMessage
await self.sendBackError(hash, "fhempy failed to handle message")
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem_pythonbinding.py", line 135, in sendBackError
duration = (time.time() - id_received_timestamp[retHash["id"]]) * 1000
KeyError: 'id'
2023-02-03 23:36:29,554 - INFO - websockets.server: connection closed
2023-02-03 23:36:29,554 - INFO - websockets.server: server closed
2023-02-03 23:36:29,556 - INFO - fhempy.lib.fhem_pythonbinding: Exit 1
2023-02-03 23:36:30,870 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.589...
2023-02-03 23:36:30,874 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-02-03 23:36:30,907 - INFO - websockets.server: server listening on 0.0.0.0:15733
2023-02-03 23:36:39,828 - INFO - websockets.server: connection open
2023-02-03 23:36:39,829 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2023-02-03 23:36:42,922 - ERROR - TUYA: Please activate OpenPulsar: https://developer.tuya.com/en/docs/iot/subscribe-mq?id=Kavqcrvckbh9h
2023-02-03 23:36:52,015 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com
2023-02-03 23:36:52,048 - WARNING - urllib3.connectionpool: Connection pool is full, discarding connection: openapi.tuyaeu.com
2023-02-03 23:44:48,370 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdateIfChanged($defs{'TUYA_SP16'},'cur_current','15.0');;
2023-02-03 23:52:44,068 - WARNING - asyncio: socket.send() raised exception.
2023-02-03 23:52:49,080 - WARNING - asyncio: socket.send() raised exception.
2023-02-03 23:52:53,698 - WARNING - asyncio: socket.send() raised exception.
2023-02-03 23:52:54,093 - WARNING - asyncio: socket.send() raised exception.
2023-02-03 23:52:58,221 - WARNING - asyncio: socket.send() raised exception.
2023-02-03 23:52:59,106 - WARNING - asyncio: socket.send() raised exception.
2023-02-03 23:53:03,710 - WARNING - asyncio: socket.send() raised exception.
2023-02-03 23:53:04,119 - WARNING - asyncio: socket.send() raised exception.
2023-02-03 23:53:09,131 - WARNING - asyncio: socket.send() raised exception.
2023-02-03 23:53:13,722 - WARNING - asyncio: socket.send() raised exception.
2023-02-03 23:53:14,144 - WARNING - asyncio: socket.send() raised exception.
2023-02-03 23:53:19,158 - WARNING - asyncio: socket.send() raised exception.
2023-02-03 23:53:23,733 - WARNING - asyncio: socket.send() raised exception.
2023-02-03 23:53:24,170 - WARNING - asyncio: socket.send() raised exception.
2023-02-03 23:53:29,183 - WARNING - asyncio: socket.send() raised exception.
2023-02-03 23:53:33,745 - WARNING - asyncio: socket.send() raised exception.
2023-02-03 23:53:34,198 - WARNING - asyncio: socket.send() raised exception.
2023-02-03 23:53:39,209 - WARNING - asyncio: socket.send() raised exception.
2023-02-03 23:53:43,757 - WARNING - asyncio: socket.send() raised exception.
2023-02-03 23:53:44,221 - WARNING - asyncio: socket.send() raised exception.
2023-02-03 23:53:49,232 - WARNING - asyncio: socket.send() raised exception.
2023-02-03 23:53:53,769 - WARNING - asyncio: socket.send() raised exception.
2023-02-03 23:53:54,244 - WARNING - asyncio: socket.send() raised exception.
2023-02-03 23:53:58,233 - WARNING - asyncio: socket.send() raised exception.
2023-02-03 23:53:59,257 - WARNING - asyncio: socket.send() raised exception.
2023-02-03 23:54:03,781 - WARNING - asyncio: socket.send() raised exception.
im fhm-log nur normales:
2023.02.03 23:32:06 3: Please define tuya_cloud_22230808bcddc213f838 first
2023.02.03 23:32:59 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_453005615002911dfe06)
2023.02.03 23:33:07 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_720570712462ab27e625)
2023.02.03 23:33:13 3: fhempy v1.0.0 (tuya_cloud: tuya_cloud_887800042cf4325f15ef)
2023.02.03 23:55:02 3: Wohnzimmer_Rollo_Alle_down_Notify return value: OK
2023.02.03 23:55:04 3: Untergeschoss_Rollo_Alle_down_Notify return value: OK
2023.02.03 23:55:07 3: Wohnzimmer_Rollo_2_down_Notify return value: OK
nur die Rolläden sind runter ;-)
nun scheint endlich Ruhe eingekehrt
nur wielange noch..
in der Ruhe nach dem Sturm ist fhempy wieder zack da ;-)
und funktionell alles prima
Ok, ich halte fest:
Nach fhempy Neustart ohne fhem Neustart kommt kein Fehler, nicht im fhempy Log und nicht im Fhem Log. Korrekt?
Bitte teste das nochmals um sicherzustellen, dass dem so ist.
Zitat von: stefanru am 03 Februar 2023, 23:57:20
Noch ganz kurz von mir. Habe auch MAX :-) Habe da aber kein Problem mit Credits.
Bei mir war es im Log ruhig heute.
Das einzige war im fhempy.log aber nicht viel.
2023-02-03 11:31:56,379 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'Fernseher_bfb7810a3e397c5fa4u7ud'},'add_ele','0.005');;
2023-02-03 11:31:56,380 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'Sybille_Tablet_bf68d9b41c16be3713vcc1'},'cycle_time','');;
2023-02-03 11:31:56,381 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'Fernseher_Wohnzimmer_bf7bbcb9a4b03a2c97cqid'},'cur_power','0.0');;
2023-02-03 11:31:56,382 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'Stefan_Tablet_bf0572e0fb6ccbe356ykuh'},'cur_voltage','230.2');;
2023-02-03 11:31:56,383 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'Computer_Stefan_bf881b7977c814af88jmrc'},'cur_current','407.0');;
2023-02-03 11:31:56,757 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'tuya_local_bf4f644bc7dd2fc71d9q52'});;
2023-02-03 19:58:09,540 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsEndUpdate($defs{'Fernseher_Schlafzimmer_bf4f644bc7dd2fc71d9q52'},1);;
2023-02-03 19:58:09,543 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBulkUpdate($defs{'Fernseher_bfb7810a3e397c5fa4u7ud'},'random_time','');;
2023-02-03 19:58:09,544 - ERROR - fhempy.lib.fhem: NO RESPONSE since 60s: readingsEndUpdate($defs{'Fernseher_Wohnzimmer_bf7bbcb9a4b03a2c97cqid'},1);;
Im fhem.log nur einmal etwas nämlich zu dem um 11:31:56, zu den anderen ist nichts da.
Auch sonst sehe ich nichts auffälliges im Log.
2023.02.03 11:31:56 1: readingsUpdate(tuya_local_bf4f644bc7dd2fc71d9q52,state,off) missed to call readingsBeginUpdate first.
2023.02.03 11:31:56 1: stacktrace:
2023.02.03 11:31:56 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.02.03 11:31:56 1: main::readingsBulkUpdateIfChanged called by (eval 97520) (1)
2023.02.03 11:31:56 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.03 11:31:56 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.03 11:31:56 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.03 11:31:56 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.03 11:31:56 1: main::CallFn called by fhem.pl (784)
Danke und Gruß,
Stefan
Kann es sein, dass fhem in der Zeit blockiert hat? Vielleicht auch freezemon parallel laufen lassen.
Ich werde morgen den Timeout auf 3 Minuten hochdrehen, damit auch ein blockiertes Fhem 3 Minuten Zeit für die Antwort hat.
Generell sollte FHEM aber nie blockieren, da sollte man nachgehen.
Zitat von: dominik am 04 Februar 2023, 00:08:05
Ich werde morgen den Timeout auf 3 Minuten hochdrehen, damit auch ein blockiertes Fhem 3 Minuten Zeit für die Antwort hat.
Generell sollte FHEM aber nie blockieren, da sollte man nachgehen.
mache ich bzgl. MAX morgen mit Wzut
und stelle Max im verbose höher
Gute Nacht und vielen Dank!
Thomas
Zitat von: dominik am 04 Februar 2023, 00:08:05
Ich werde morgen den Timeout auf 3 Minuten hochdrehen, damit auch ein blockiertes Fhem 3 Minuten Zeit für die Antwort hat.
Generell sollte FHEM aber nie blockieren, da sollte man nachgehen.
ich habe kurz nach Mitternacht Apptime gestartet; aktuelle Werte:
active-timers: 83; max-active timers: 85; max-timer-load: 36 min-tmrHandlingTm: 0.0ms; max-tmrHandlingTm: 11512.2ms; totAvgDly: 22.1ms
name function max count total average maxDly avgDly TS Max call param Max call
tmr-at_Exec HASH(0x4050738) 3310 1 3310.78 3310.78 0.74 0.74 04.02. 08:06:09 HASH(Kueche_Rollo_3_bei_Sonnenaufgang_hoch_AT)
Kueche_Rollo_3 dummy_Set 3259 2 3259.19 1629.59 0.00 0.00 04.02. 08:06:09 HASH(Kueche_Rollo_3); Kueche_Rollo_3; up
Kueche_Rollo_3_up_Notify notify_Exec 3093 1 3093.26 3093.26 0.00 0.00 04.02. 08:06:09 HASH(Kueche_Rollo_3_up_Notify); HASH(Kueche_Rollo_3)
tmr-at_Exec HASH(0x4049348) 2512 1 2512.38 2512.38 1.00 1.00 04.02. 07:46:08 HASH(Untergeschoss_Rollos_bei_Sonnenaufgang_hoch_AT)
tmr-at_Exec HASH(0x401c400) 2494 1 2494.51 2494.51 1.12 1.12 04.02. 08:30:02 HASH(Wohnzimmer_Rollos_bei_Sonnenaufgang_hoch_AT)
Wohnzimmer_Rollo_Alle dummy_Set 2492 2 2492.09 1246.05 0.00 0.00 04.02. 08:30:02 HASH(Wohnzimmer_Rollo_Alle); Wohnzimmer_Rollo_Alle; up
Untergeschoss_Rollo_Alle dummy_Set 2459 2 2459.80 1229.90 0.00 0.00 04.02. 07:46:08 HASH(Untergeschoss_Rollo_Alle); Untergeschoss_Rollo_Alle; up
Wohnzimmer_Rollo_Alle_up_Notify notify_Exec 2384 1 2384.53 2384.53 0.00 0.00 04.02. 08:30:02 HASH(Wohnzimmer_Rollo_Alle_up_Notify); HASH(Wohnzimmer_Rollo_Alle)
Untergeschoss_Rollo_Alle_up_Notify notify_Exec 2351 1 2351.91 2351.91 0.00 0.00 04.02. 07:46:08 HASH(Untergeschoss_Rollo_Alle_up_Notify); HASH(Untergeschoss_Rollo_Alle)
tmr-at_Exec HASH(0x4055088) 2289 1 2289.99 2289.99 9223.02 9223.02 04.02. 07:46:17 HASH(Wohnzimmer_Rollo_3_bei_Sonnenaufgang_hoch_AT)
tmr-at_Exec HASH(0x4052ff0) 2240 1 2240.61 2240.61 4748.97 4748.97 04.02. 07:46:12 HASH(Wohnzimmer_Rollo_1_bei_Sonnenaufgang_hoch_AT)
Wohnzimmer_Rollo_3 dummy_Set 2238 4 2337.02 584.25 0.00 0.00 04.02. 07:46:17 HASH(Wohnzimmer_Rollo_3); Wohnzimmer_Rollo_3; up
tmr-at_Exec HASH(0x4049a50) 2235 1 2235.40 2235.40 2513.47 2513.47 04.02. 07:46:10 HASH(Untergeschoss_Rollo_2_bei_Sonnenaufgang_hoch_AT)
tmr-at_Exec HASH(0x4053860) 2233 1 2233.21 2233.21 6989.71 6989.71 04.02. 07:46:15 HASH(Wohnzimmer_Rollo_2_bei_Sonnenaufgang_hoch_AT)
tmr-at_Exec HASH(0x4049258) 2199 1 2199.03 2199.03 72.11 72.11 04.02. 07:49:28 HASH(Untergeschoss_Rollo_1_bei_Sonnenaufgang_hoch_AT)
tmr-at_Exec HASH(0x404c708) 2190 1 2190.38 2190.38 35.88 35.88 04.02. 09:30:02 HASH(Obergeschoss_Rollo_1_bei_Sonnenaufgang_hoch_AT)
Obergeschoss_Rollo_1 dummy_Set 2188 2 2188.40 1094.20 0.00 0.00 04.02. 09:30:02 HASH(Obergeschoss_Rollo_1); Obergeschoss_Rollo_1; up
Wohnzimmer_Rollo_1 dummy_Set 2188 4 2348.09 587.02 0.00 0.00 04.02. 07:46:12 HASH(Wohnzimmer_Rollo_1); Wohnzimmer_Rollo_1; up
Untergeschoss_Rollo_2 dummy_Set 2183 4 2283.91 570.98 0.00 0.00 04.02. 07:46:10 HASH(Untergeschoss_Rollo_2); Untergeschoss_Rollo_2; up
Wohnzimmer_Rollo_2 dummy_Set 2180 4 2278.67 569.67 0.00 0.00 04.02. 07:46:15 HASH(Wohnzimmer_Rollo_2); Wohnzimmer_Rollo_2; up
Untergeschoss_Rollo_1 dummy_Set 2147 4 2273.58 568.39 0.00 0.00 04.02. 07:49:28 HASH(Untergeschoss_Rollo_1); Untergeschoss_Rollo_1; up
tmr-at_Exec HASH(0x404be98) 2146 1 2146.51 2146.51 2495.73 2495.73 04.02. 08:30:04 HASH(Untergeschoss_Rollo_3_bei_Sonnenaufgang_hoch_AT)
Untergeschoss_Rollo_3 dummy_Set 2144 4 2244.05 561.01 0.00 0.00 04.02. 08:30:04 HASH(Untergeschoss_Rollo_3); Untergeschoss_Rollo_3; up
Wohnzimmer_Rollo_3_up_Notify notify_Exec 2079 2 2079.67 1039.83 0.00 0.00 04.02. 07:46:17 HASH(Wohnzimmer_Rollo_3_up_Notify); HASH(Wohnzimmer_Rollo_3)
Obergeschoss_Rollo_1_up_Notify notify_Exec 2051 1 2051.12 2051.12 0.00 0.00 04.02. 09:30:02 HASH(Obergeschoss_Rollo_1_up_Notify); HASH(Obergeschoss_Rollo_1)
Wohnzimmer_Rollo_1_up_Notify notify_Exec 2028 2 2028.71 1014.36 0.00 0.00 04.02. 07:46:12 HASH(Wohnzimmer_Rollo_1_up_Notify); HASH(Wohnzimmer_Rollo_1)
Untergeschoss_Rollo_2_up_Notify notify_Exec 2023 2 2023.74 1011.87 0.00 0.00 04.02. 07:46:10 HASH(Untergeschoss_Rollo_2_up_Notify); HASH(Untergeschoss_Rollo_2)
Untergeschoss_Rollo_3_up_Notify notify_Exec 2023 2 2023.27 1011.64 0.00 0.00 04.02. 08:30:04 HASH(Untergeschoss_Rollo_3_up_Notify); HASH(Untergeschoss_Rollo_3)
Wohnzimmer_Rollo_2_up_Notify notify_Exec 2022 2 2022.89 1011.45 0.00 0.00 04.02. 07:46:15 HASH(Wohnzimmer_Rollo_2_up_Notify); HASH(Wohnzimmer_Rollo_2)
Untergeschoss_Rollo_1_up_Notify notify_Exec 2020 2 2020.68 1010.34 0.00 0.00 04.02. 07:49:28 HASH(Untergeschoss_Rollo_1_up_Notify); HASH(Untergeschoss_Rollo_1)
CUL_0 CUL_Read 1322 4160 938172.37 225.52 0.00 0.00 04.02. 12:22:11 HASH(CUL_0)
dblog_THB DbLog_Log 893 97273 6635585.25 68.22 0.00 0.00 04.02. 11:29:45 HASH(dblog_THB); HASH(WU_IPLIEZ_3)
local_pybinding CODE(0x2fc7ef0) 867 490175 5527962.98 11.28 0.00 0.00 04.02. 07:46:18 HASH(local_pybinding)
WEB_127.0.0.1_42872 FW_Notify 801 97273 400898.83 4.12 0.00 0.00 04.02. 07:46:18 HASH(WEB_127.0.0.1_42872); HASH(TUYA_JL27)
TUYA_JL27 fhempy_Set 799 1058 7777.51 7.35 0.00 0.00 04.02. 07:46:18 HASH(TUYA_JL27); ARRAY(0x4e64b00); HASH(0x43eb128)
TUYA_JL06 fhempy_Set 738 1826 9038.39 4.95 0.00 0.00 04.02. 07:46:18 HASH(TUYA_JL06); ARRAY(0x4eb4d98); HASH(0x514e3e8)
TUYA_JL15 fhempy_Set 679 5048 25678.02 5.09 0.00 0.00 04.02. 07:46:18 HASH(TUYA_JL15); ARRAY(0x508b360); HASH(0x5043300)
TUYA_JL31 fhempy_Set 617 5073 23350.83 4.60 0.00 0.00 04.02. 07:46:18 HASH(TUYA_JL31); ARRAY(0x4e600d8); HASH(0x4e5ccb8)
TUYA_JL13 fhempy_Set 553 2877 15014.83 5.22 0.00 0.00 04.02. 07:46:18 HASH(TUYA_JL13); ARRAY(0x460a018); HASH(0x513b260)
TUYA_JL29 fhempy_Set 463 5130 26481.28 5.16 0.00 0.00 04.02. 07:46:18 HASH(TUYA_JL29); ARRAY(0x4f3e4e8); HASH(0x4f8a9c8)
tmr-HUEBridge_GetUpdate HASH(0x2b45038) 444 721 190054.52 263.60 557.76 11.25 04.02. 12:19:37 HASH(hueBridge1)
dblog ist gut dabei; das hat ach heute Nacht automatische dumps und dblogreduces gefahren
fhempy hat sehr hohe Werte entsprechend log:
2023-02-04 12:53:32,572 - WARNING - asyncio: socket.send() raised exception.
2023-02-04 12:53:34,077 - WARNING - asyncio: socket.send() raised exception.
2023-02-04 12:53:34,079 - WARNING - asyncio: socket.send() raised exception.
2023-02-04 12:53:38,563 - WARNING - asyncio: socket.send() raised exception.
2023-02-04 12:53:39,094 - WARNING - asyncio: socket.send() raised exception.
2023-02-04 12:53:39,096 - WARNING - asyncio: socket.send() raised exception.
WEB_127.0.0.1_42872 FW_Notify 801 97273 400898.83 4.12 0.00 0.00 04.02. 07:46:18 HASH(WEB_127.0.0.1_42872); HASH(TUYA_JL27) ist auffällig.
JL27 ist eine Steckdose direkt an meinem Schreibtisch und ist an.
ist da noch was Bedenkliches?
die fhemlog ist unauffällig
ehm...deine apptime Ausgaben sind ziemlich schlecht. Überall Laufzeiten (avg!) von über 1s!
Wenn ich apptime richtig verstehe, sollte in avg nie ein hoher Wert drin stehen. Ich bin dort im Normalfall überall im ms Bereich, du hast 3310.78 stehen, das sind 3,3s! Freezemon meldet sich da garnicht zu Wort?
Zitat von: dominik am 04 Februar 2023, 14:47:11
ehm...deine apptime Ausgaben sind ziemlich schlecht. Überall Laufzeiten (avg!) von über 1s!
Wenn ich apptime richtig verstehe, sollte in avg nie ein hoher Wert drin stehen. Ich bin dort im Normalfall überall im ms Bereich, du hast 3310.78 stehen, das sind 3,3s! Freezemon meldet sich da garnicht zu Wort?
active-timers: 80; max-active timers: 80; max-timer-load: 1 min-tmrHandlingTm: 0.2ms; max-tmrHandlingTm: 60.1ms; totAvgDly: 35.4ms
name function max count total average maxDly avgDly TS Max call param Max call
CUL_0 CUL_Read 341 5 798.55 159.71 0.00 0.00 04.02. 14:54:03 HASH(CUL_0)
local_pybinding CODE(0x42ed668) 287 305 3383.83 11.09 0.00 0.00 04.02. 14:53:59 HASH(local_pybinding)
dblog_THB DbLog_Log 277 38 2954.70 77.76 0.00 0.00 04.02. 14:54:03 HASH(dblog_THB); HASH(MAX_THOMAS_HT2)
WEB_127.0.0.1_36872 FW_Notify 125 38 281.31 7.40 0.00 0.00 04.02. 14:53:59 HASH(WEB_127.0.0.1_36872); HASH(TUYA_JL04)
TUYA_JL04 fhempy_Set 124 14 209.24 14.95 0.00 0.00 04.02. 14:53:59 HASH(TUYA_JL04); ARRAY(0x6038b50); HASH(0x6166088)
tmr-DbLog_execMemCacheAsync HASH(0x1ae2620) 60 1 60.01 60.01 70.50 70.50 04.02. 14:53:59 HASH(dblog_THB)
JLLaCR JeeLink_Read 52 32 143.27 4.48 0.00 0.00 04.02. 14:54:03 HASH(JLLaCR)
WEB_192.168.9.103_1111 FW_Notify 50 38 180.19 4.74 0.00 0.00 04.02. 14:53:59 HASH(WEB_192.168.9.103_1111); HASH(TUYA_JL04)
TUYA_JL31 fhempy_Set 10 4 25.30 6.32 0.00 0.00 04.02. 14:53:58 HASH(TUYA_JL31); ARRAY(0x60a67e8); HASH(0x5d4e578)
WEB_192.168.9.103_1070 FW_Read 6 1 6.30 6.30 0.00 0.00 04.02. 14:53:48 HASH(WEB_192.168.9.103_1070)
TUYA_JL30 fhempy_Set 6 6 26.67 4.45 0.00 0.00 04.02. 14:53:50 HASH(TUYA_JL30); ARRAY(0x5c9cd70); HASH(0x6170c88)
TUYA_JL26 fhempy_Set 5 2 10.26 5.13 0.00 0.00 04.02. 14:53:54 HASH(TUYA_JL26); ARRAY(0x5fb6918); HASH(0x6233988)
MAX_THOMAS_HT2 CODE(0x506de60) 5 1 5.36 5.36 0.00 0.00 04.02. 14:54:03 HASH(MAX_THOMAS_HT2); MAX_THOMAS_HT2; ?
MAX_PETRA_HT1 CODE(0x506de60) 5 1 5.32 5.32 0.00 0.00 04.02. 14:54:01 HASH(MAX_PETRA_HT1); MAX_PETRA_HT1; ?
MAX_PETRA_WT CODE(0x506de60) 5 1 5.29 5.29 0.00 0.00 04.02. 14:54:01 HASH(MAX_PETRA_WT); MAX_PETRA_WT; ?
TUYA_SP15 fhempy_Set 4 2 9.18 4.59 0.00 0.00 04.02. 14:53:59 HASH(TUYA_SP15); ARRAY(0x616a1f8); HASH(0x5d26e80)
TUYA_JL33 fhempy_Set 4 6 18.38 3.06 0.00 0.00 04.02. 14:54:02 HASH(TUYA_JL33); ARRAY(0x573b6b8); HASH(0x62cb388)
TUYA_JL29 fhempy_Set 3 6 16.31 2.72 0.00 0.00 04.02. 14:53:58 HASH(TUYA_JL29); ARRAY(0x5d34d80); HASH(0x5ce3748)
TUYA_JL06 fhempy_Set 3 2 6.46 3.23 0.00 0.00 04.02. 14:54:03 HASH(TUYA_JL06); ARRAY(0x5fc87d8); HASH(0x60b8db0)
TUYA_JL27 fhempy_Set 2 2 4.89 2.45 0.00 0.00 04.02. 14:54:02 HASH(TUYA_JL27); ARRAY(0x393b018); HASH(0x6011d20)
tuya_cloud_453005615002911dfe06 fhempy_Set 2 1 2.43 2.43 0.00 0.00 04.02. 14:54:02 HASH(tuya_cloud_453005615002911dfe06); ARRAY(0x5341fd0); HASH(0x5d12bf8)
TUYA_JL13 fhempy_Set 2 2 4.75 2.38 0.00 0.00 04.02. 14:53:56 HASH(TUYA_JL13); ARRAY(0x6157bb8); HASH(0x5cf2780)
TUYA_JL15 fhempy_Set 2 4 9.35 2.34 0.00 0.00 04.02. 14:54:01 HASH(TUYA_JL15); ARRAY(0x5ccfae8); HASH(0x62c29a8)
TUYA_JL24 fhempy_Set 2 2 4.69 2.34 0.00 0.00 04.02. 14:54:02 HASH(TUYA_JL24); ARRAY(0x5746c98); HASH(0x61db738)
dblog_THB DbLog_Set 1 1 1.27 1.27 0.00 0.00 04.02. 14:53:59 HASH(dblog_THB); dblog_THB; ?
Pythonbinding_15733 fhempyServer_Read 1 6 3.19 0.53 0.00 0.00 04.02. 14:54:03 HASH(Pythonbinding_15733)
WEB FW_Read 0 1 0.67 0.67 0.00 0.00 04.02. 14:53:48 HASH(WEB)
dblog_THB DbLog_SBP_Read 0 1 0.42 0.42 0.00 0.00 04.02. 14:53:59 HASH(dblog_THB)
EcoTaster_2_notify_auto notify_Exec 0 38 4.15 0.11 0.00 0.00 04.02. 14:53:54 HASH(EcoTaster_2_notify_auto); HASH(TUYA_JL26)
EcoTaster_1_notify_auto notify_Exec 0 38 6.23 0.16 0.00 0.00 04.02. 14:53:58 HASH(EcoTaster_1_notify_auto); HASH(TUYA_JL29)
EcoTaster_5_notify_auto notify_Exec 0 38 3.89 0.10 0.00 0.00 04.02. 14:53:50 HASH(EcoTaster_5_notify_auto); HASH(TUYA_JL30)
alexa alexa_Read 0 1 0.26 0.26 0.00 0.00 04.02. 14:54:01 HASH(alexa)
EcoTaster_3_notify_eco notify_Exec 0 38 3.75 0.10 0.00 0.00 04.02. 14:53:56 HASH(EcoTaster_3_notify_eco); HASH(TUYA_JL04)
n_defined notify_Exec 0 38 5.45 0.14 0.00 0.00 04.02. 14:53:54 HASH(n_defined); HASH(TUYA_JL26)
EcoTaster_1_notify_eco notify_Exec 0 38 4.08 0.11 0.00 0.00 04.02. 14:53:56 HASH(EcoTaster_1_notify_eco); HASH(TUYA_JL04)
EcoTaster_4_notify_auto notify_Exec 0 38 3.72 0.10 0.00 0.00 04.02. 14:53:56 HASH(EcoTaster_4_notify_auto); HASH(TUYA_JL04)
EcoTaster_3_notify_auto notify_Exec 0 38 3.72 0.10 0.00 0.00 04.02. 14:53:56 HASH(EcoTaster_3_notify_auto); HASH(TUYA_JL04)
EcoTaster_4_notify_eco notify_Exec 0 38 3.60 0.09 0.00 0.00 04.02. 14:53:56 HASH(EcoTaster_4_notify_eco); HASH(TUYA_JL04)
EcoTaster_2_notify_eco notify_Exec 0 38 3.74 0.10 0.00 0.00 04.02. 14:53:56 HASH(EcoTaster_2_notify_eco); HASH(TUYA_JL04)
EcoTaster_5_notify_eco notify_Exec 0 38 3.58 0.09 0.00 0.00 04.02. 14:53:56 HASH(EcoTaster_5_notify_eco); HASH(TUYA_JL04)
EcoTaster_6_notify_eco notify_Exec 0 38 3.48 0.09 0.00 0.00 04.02. 14:53:50 HASH(EcoTaster_6_notify_eco); HASH(TUYA_JL30)ich hatte FHEM neu gestartet; also neues bild:
local_pybinding CODE(0x42ed668) 287 305 3383.83 11.09 0.00 0.00 04.02. 14:53:59 HASH(local_pybinding)hat den höchsten average Wert.
es wurden 3 doppelte "erkannt"
fhem-log:
2023.02.04 13:05:28 1: stacktrace:
2023.02.04 13:05:28 1: main::readingsBulkUpdate called by (eval 6528) (1)
2023.02.04 13:05:28 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:28 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:28 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.04 13:05:28 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.04 13:05:28 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.04 13:05:28 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.04 13:05:28 1: main::CallFn called by fhem.pl (3198)
2023.02.04 13:05:28 1: main::CommandAttr called by (eval 6524) (1)
2023.02.04 13:05:28 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:28 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:28 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.04 13:05:28 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.04 13:05:28 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.04 13:05:28 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.04 13:05:28 1: main::CallFn called by fhem.pl (3198)
2023.02.04 13:05:28 1: main::CommandAttr called by (eval 6520) (1)
2023.02.04 13:05:28 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:28 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:28 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.04 13:05:28 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.04 13:05:28 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.04 13:05:28 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.04 13:05:28 1: main::CallFn called by fhem.pl (1954)
2023.02.04 13:05:28 1: main::DoSet called by fhem.pl (1996)
2023.02.04 13:05:28 1: main::CommandSet called by fhem.pl (2904)
2023.02.04 13:05:28 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.04 13:05:28 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.04 13:05:28 1: main::FW_Notify called by fhem.pl (3976)
2023.02.04 13:05:28 1: main::CallFn called by fhem.pl (3888)
2023.02.04 13:05:28 1: main::DoTrigger called by fhem.pl (4995)
2023.02.04 13:05:28 1: main::readingsEndUpdate called by (eval 6518) (1)
2023.02.04 13:05:28 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:28 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:28 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.04 13:05:28 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.04 13:05:28 1: main::CallFn called by fhem.pl (784)
2023.02.04 13:05:28 1: readingsUpdate(TUYA_Temp02,va_temperature,19.9) missed to call readingsBeginUpdate first.
2023.02.04 13:05:28 1: stacktrace:
2023.02.04 13:05:28 1: main::readingsBulkUpdate called by (eval 6529) (1)
2023.02.04 13:05:28 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:28 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:28 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.04 13:05:28 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.04 13:05:28 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.04 13:05:28 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.04 13:05:28 1: main::CallFn called by fhem.pl (3198)
2023.02.04 13:05:28 1: main::CommandAttr called by (eval 6524) (1)
2023.02.04 13:05:28 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:28 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:28 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.04 13:05:28 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.04 13:05:28 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.04 13:05:28 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.04 13:05:28 1: main::CallFn called by fhem.pl (3198)
2023.02.04 13:05:28 1: main::CommandAttr called by (eval 6520) (1)
2023.02.04 13:05:28 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:28 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:28 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.04 13:05:28 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.04 13:05:28 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.04 13:05:28 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.04 13:05:28 1: main::CallFn called by fhem.pl (1954)
2023.02.04 13:05:28 1: main::DoSet called by fhem.pl (1996)
2023.02.04 13:05:28 1: main::CommandSet called by fhem.pl (2904)
2023.02.04 13:05:28 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.04 13:05:28 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.04 13:05:28 1: main::FW_Notify called by fhem.pl (3976)
2023.02.04 13:05:28 1: main::CallFn called by fhem.pl (3888)
2023.02.04 13:05:28 1: main::DoTrigger called by fhem.pl (4995)
2023.02.04 13:05:28 1: main::readingsEndUpdate called by (eval 6518) (1)
2023.02.04 13:05:28 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:28 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:28 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.04 13:05:28 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.04 13:05:28 1: main::CallFn called by fhem.pl (784)
2023.02.04 13:05:29 1: readingsUpdate(TUYA_Temp07,va_humidity,34.9) missed to call readingsBeginUpdate first.
2023.02.04 13:05:29 1: stacktrace:
2023.02.04 13:05:29 1: main::readingsBulkUpdate called by (eval 6543) (1)
2023.02.04 13:05:29 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:29 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:29 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.04 13:05:29 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.04 13:05:29 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.04 13:05:29 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (1954)
2023.02.04 13:05:29 1: main::DoSet called by fhem.pl (1996)
2023.02.04 13:05:29 1: main::CommandSet called by fhem.pl (2904)
2023.02.04 13:05:29 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.04 13:05:29 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.04 13:05:29 1: main::FW_Notify called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (3888)
2023.02.04 13:05:29 1: main::DoTrigger called by fhem.pl (3222)
2023.02.04 13:05:29 1: main::CommandAttr called by (eval 6524) (1)
2023.02.04 13:05:29 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:29 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:29 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.04 13:05:29 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.04 13:05:29 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.04 13:05:29 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (3198)
2023.02.04 13:05:29 1: main::CommandAttr called by (eval 6520) (1)
2023.02.04 13:05:29 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:29 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:29 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.04 13:05:29 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.04 13:05:29 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.04 13:05:29 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (1954)
2023.02.04 13:05:29 1: main::DoSet called by fhem.pl (1996)
2023.02.04 13:05:29 1: main::CommandSet called by fhem.pl (2904)
2023.02.04 13:05:29 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.04 13:05:29 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.04 13:05:29 1: main::FW_Notify called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (3888)
2023.02.04 13:05:29 1: main::DoTrigger called by fhem.pl (4995)
2023.02.04 13:05:29 1: main::readingsEndUpdate called by (eval 6518) (1)
2023.02.04 13:05:29 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:29 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:29 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.04 13:05:29 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (784)
2023.02.04 13:05:29 1: readingsUpdate(TUYA_Temp02,humidity_value,42.0) missed to call readingsBeginUpdate first.
2023.02.04 13:05:29 1: stacktrace:
2023.02.04 13:05:29 1: main::readingsBulkUpdate called by (eval 6546) (1)
2023.02.04 13:05:29 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:29 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:29 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.04 13:05:29 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.04 13:05:29 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.04 13:05:29 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (1954)
2023.02.04 13:05:29 1: main::DoSet called by fhem.pl (1996)
2023.02.04 13:05:29 1: main::CommandSet called by fhem.pl (2904)
2023.02.04 13:05:29 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.04 13:05:29 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.04 13:05:29 1: main::FW_Notify called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (3888)
2023.02.04 13:05:29 1: main::DoTrigger called by fhem.pl (3222)
2023.02.04 13:05:29 1: main::CommandAttr called by (eval 6524) (1)
2023.02.04 13:05:29 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:29 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:29 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.04 13:05:29 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.04 13:05:29 1: main::IOWrite called by ./FHEM/10_fhempy.pm (103)
2023.02.04 13:05:29 1: main::fhempy_Attr called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (3198)
2023.02.04 13:05:29 1: main::CommandAttr called by (eval 6520) (1)
2023.02.04 13:05:29 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:29 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:29 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.04 13:05:29 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.04 13:05:29 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.04 13:05:29 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (1954)
2023.02.04 13:05:29 1: main::DoSet called by fhem.pl (1996)
2023.02.04 13:05:29 1: main::CommandSet called by fhem.pl (2904)
2023.02.04 13:05:29 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.04 13:05:29 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.04 13:05:29 1: main::FW_Notify called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (3888)
2023.02.04 13:05:29 1: main::DoTrigger called by fhem.pl (4995)
2023.02.04 13:05:29 1: main::readingsEndUpdate called by (eval 6518) (1)
2023.02.04 13:05:29 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:29 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:29 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.04 13:05:29 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (784)
2023.02.04 13:05:29 1: readingsUpdate(TUYA_SP13,cur_current,934.0) missed to call readingsBeginUpdate first.
2023.02.04 13:05:29 1: stacktrace:
2023.02.04 13:05:29 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.02.04 13:05:29 1: main::readingsBulkUpdateIfChanged called by (eval 6554) (1)
2023.02.04 13:05:29 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:29 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:29 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.04 13:05:29 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.04 13:05:29 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.04 13:05:29 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (1954)
2023.02.04 13:05:29 1: main::DoSet called by fhem.pl (1996)
2023.02.04 13:05:29 1: main::CommandSet called by fhem.pl (2904)
2023.02.04 13:05:29 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.04 13:05:29 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.04 13:05:29 1: main::FW_Notify called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (3888)
2023.02.04 13:05:29 1: main::DoTrigger called by fhem.pl (3222)
2023.02.04 13:05:29 1: main::CommandAttr called by (eval 6520) (1)
2023.02.04 13:05:29 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:29 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:29 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.04 13:05:29 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.04 13:05:29 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.04 13:05:29 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (1954)
2023.02.04 13:05:29 1: main::DoSet called by fhem.pl (1996)
2023.02.04 13:05:29 1: main::CommandSet called by fhem.pl (2904)
2023.02.04 13:05:29 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.04 13:05:29 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.04 13:05:29 1: main::FW_Notify called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (3888)
2023.02.04 13:05:29 1: main::DoTrigger called by fhem.pl (4995)
2023.02.04 13:05:29 1: main::readingsEndUpdate called by (eval 6518) (1)
2023.02.04 13:05:29 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:29 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:29 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.04 13:05:29 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (784)
2023.02.04 13:05:29 1: readingsUpdate(TUYA_Temp07,battery_percentage,34.0) missed to call readingsBeginUpdate first.
2023.02.04 13:05:29 1: stacktrace:
2023.02.04 13:05:29 1: main::readingsBulkUpdate called by (eval 6555) (1)
2023.02.04 13:05:29 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:29 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:29 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.04 13:05:29 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.04 13:05:29 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.04 13:05:29 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (1954)
2023.02.04 13:05:29 1: main::DoSet called by fhem.pl (1996)
2023.02.04 13:05:29 1: main::CommandSet called by fhem.pl (2904)
2023.02.04 13:05:29 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.04 13:05:29 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.04 13:05:29 1: main::FW_Notify called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (3888)
2023.02.04 13:05:29 1: main::DoTrigger called by fhem.pl (3222)
2023.02.04 13:05:29 1: main::CommandAttr called by (eval 6520) (1)
2023.02.04 13:05:29 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:29 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:29 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.04 13:05:29 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.04 13:05:29 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.04 13:05:29 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (1954)
2023.02.04 13:05:29 1: main::DoSet called by fhem.pl (1996)
2023.02.04 13:05:29 1: main::CommandSet called by fhem.pl (2904)
2023.02.04 13:05:29 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.04 13:05:29 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.04 13:05:29 1: main::FW_Notify called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (3888)
2023.02.04 13:05:29 1: main::DoTrigger called by fhem.pl (4995)
2023.02.04 13:05:29 1: main::readingsEndUpdate called by (eval 6518) (1)
2023.02.04 13:05:29 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:29 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:29 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.04 13:05:29 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (784)
2023.02.04 13:05:29 1: readingsUpdate(TUYA_Temp02,temp_unit_convert,c) missed to call readingsBeginUpdate first.
2023.02.04 13:05:29 1: stacktrace:
2023.02.04 13:05:29 1: main::readingsBulkUpdate called by (eval 6562) (1)
2023.02.04 13:05:29 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:29 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:29 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.04 13:05:29 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.04 13:05:29 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.04 13:05:29 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (1954)
2023.02.04 13:05:29 1: main::DoSet called by fhem.pl (1996)
2023.02.04 13:05:29 1: main::CommandSet called by fhem.pl (2904)
2023.02.04 13:05:29 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.04 13:05:29 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.04 13:05:29 1: main::FW_Notify called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (3888)
2023.02.04 13:05:29 1: main::DoTrigger called by fhem.pl (3222)
2023.02.04 13:05:29 1: main::CommandAttr called by (eval 6520) (1)
2023.02.04 13:05:29 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:29 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:29 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.04 13:05:29 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.04 13:05:29 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.04 13:05:29 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (1954)
2023.02.04 13:05:29 1: main::DoSet called by fhem.pl (1996)
2023.02.04 13:05:29 1: main::CommandSet called by fhem.pl (2904)
2023.02.04 13:05:29 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.04 13:05:29 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.04 13:05:29 1: main::FW_Notify called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (3888)
2023.02.04 13:05:29 1: main::DoTrigger called by fhem.pl (4995)
2023.02.04 13:05:29 1: main::readingsEndUpdate called by (eval 6518) (1)
2023.02.04 13:05:29 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:29 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:29 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (301)
2023.02.04 13:05:29 1: main::BindingsIo_Read called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (784)
2023.02.04 13:05:29 1: readingsUpdate(TUYA_SP13,cur_power,155.9) missed to call readingsBeginUpdate first.
2023.02.04 13:05:29 1: stacktrace:
2023.02.04 13:05:29 1: main::readingsBulkUpdate called by fhem.pl (5012)
2023.02.04 13:05:29 1: main::readingsBulkUpdateIfChanged called by (eval 6571) (1)
2023.02.04 13:05:29 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:29 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:29 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.04 13:05:29 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.04 13:05:29 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.04 13:05:29 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (1954)
2023.02.04 13:05:29 1: main::DoSet called by fhem.pl (1996)
2023.02.04 13:05:29 1: main::CommandSet called by fhem.pl (2904)
2023.02.04 13:05:29 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.04 13:05:29 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.04 13:05:29 1: main::FW_Notify called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (3888)
2023.02.04 13:05:29 1: main::DoTrigger called by fhem.pl (4995)
2023.02.04 13:05:29 1: main::readingsEndUpdate called by (eval 6564) (1)
2023.02.04 13:05:29 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:29 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:29 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.04 13:05:29 1: main::BindingsIo_Write called by fhem.pl (1064)
2023.02.04 13:05:29 1: main::IOWrite called by ./FHEM/10_fhempy.pm (91)
2023.02.04 13:05:29 1: main::fhempy_Set called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (1954)
2023.02.04 13:05:29 1: main::DoSet called by fhem.pl (1996)
2023.02.04 13:05:29 1: main::CommandSet called by fhem.pl (2904)
2023.02.04 13:05:29 1: main::getAllSets called by ./FHEM/01_FHEMWEB.pm (3331)
2023.02.04 13:05:29 1: main::FW_devState called by ./FHEM/01_FHEMWEB.pm (3223)
2023.02.04 13:05:29 1: main::FW_Notify called by fhem.pl (3976)
2023.02.04 13:05:29 1: main::CallFn called by fhem.pl (3888)
2023.02.04 13:05:29 1: main::DoTrigger called by fhem.pl (3222)
2023.02.04 13:05:29 1: main::CommandAttr called by (eval 6520) (1)
2023.02.04 13:05:29 1: (eval) called by ./FHEM/10_BindingsIo.pm (576)
2023.02.04 13:05:29 1: main::BindingsIo_processMessage called by ./FHEM/10_BindingsIo.pm (686)
2023.02.04 13:05:29 1: main::BindingsIo_readWebsocketMessage called by ./FHEM/10_BindingsIo.pm (430)
2023.02.04 13:05:29 1: main::BindingsIo_Write called by fhem.pl (1064)
[code]- asyn
wie kann ich denn die Ergebnisse von perfmon sehen?
wie kann ich fhempy temporär deaktivieren, um die Systenlast ohne fhempy zu ermitteln?
Nicht auf total schauen. Avg ist der Wert der wichtig ist. Bzw. max natürlich auch.
Lass mal paar Stunden laufen und mach dann wieder apptime. Und lass freezemon laufen.
Ich denke irgendwas blockiert fhem beim Start.
Zitat von: dominik am 04 Februar 2023, 16:00:41
Nicht auf total schauen. Avg ist der Wert der wichtig ist. Bzw. max natürlich auch.
Lass mal paar Stunden laufen und mach dann wieder apptime. Und lass freezemon laufen.
so nun kommt mein Morgen-Bericht:
fhempy-log
2023-02-05 04:21:42,123 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 04:21:44,220 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 04:21:49,285 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 04:21:52,213 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 04:21:52,906 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 04:21:54,482 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 06:01:31,837 - ERROR - fhempy.lib.fhem: FHEM took 5290ms for readingsBulkUpdate($defs{'tuya_cloud_3367036770039f60ce2b'},'cur_power','64.0');;
2023-02-05 06:01:31,838 - ERROR - fhempy.lib.fhem: FHEM took 5175ms for readingsBeginUpdate($defs{'TUYA_JL31'});;
2023-02-05 07:44:58,000 - ERROR - fhempy.lib.fhem: FHEM took 11985ms for readingsBeginUpdate($defs{'TUYA_SP16'});;
2023-02-05 07:44:58,000 - ERROR - fhempy.lib.fhem: FHEM took 11272ms for readingsBeginUpdate($defs{'TUYA_SP11'});;
2023-02-05 07:44:58,001 - ERROR - fhempy.lib.fhem: FHEM took 11035ms for readingsBeginUpdate($defs{'TUYA_JL06'});;
2023-02-05 07:44:58,001 - ERROR - fhempy.lib.fhem: FHEM took 10085ms for readingsBeginUpdate($defs{'TUYA_SP15'});;
2023-02-05 07:44:58,003 - ERROR - fhempy.lib.fhem: FHEM took 9622ms for readingsBeginUpdate($defs{'TUYA_JL30'});;
2023-02-05 07:44:58,004 - ERROR - fhempy.lib.fhem: FHEM took 9511ms for readingsBeginUpdate($defs{'TUYA_JL18'});;
2023-02-05 07:44:58,005 - ERROR - fhempy.lib.fhem: FHEM took 9159ms for readingsBeginUpdate($defs{'tuya_cloud_3367036770039f60ce2b'});;
2023-02-05 07:44:58,006 - ERROR - fhempy.lib.fhem: FHEM took 9036ms for readingsBeginUpdate($defs{'TUYA_JL29'});;
2023-02-05 07:44:58,007 - ERROR - fhempy.lib.fhem: FHEM took 8925ms for readingsBeginUpdate($defs{'TUYA_JL27'});;
2023-02-05 07:44:58,009 - ERROR - fhempy.lib.fhem: FHEM took 8699ms for readingsBeginUpdate($defs{'TUYA_SP13'});;
2023-02-05 07:44:58,010 - ERROR - fhempy.lib.fhem: FHEM took 8699ms for readingsBeginUpdate($defs{'TUYA_SP14'});;
2023-02-05 07:44:58,011 - ERROR - fhempy.lib.fhem: FHEM took 8347ms for readingsBeginUpdate($defs{'TUYA_JL04'});;
2023-02-05 07:44:58,012 - ERROR - fhempy.lib.fhem: FHEM took 8348ms for readingsBeginUpdate($defs{'TUYA_JL33'});;
2023-02-05 07:44:58,014 - ERROR - fhempy.lib.fhem: FHEM took 7541ms for readingsBeginUpdate($defs{'TUYA_JL31'});;
2023-02-05 07:44:58,115 - ERROR - fhempy.lib.fhem: FHEM took 6094ms for readingsBeginUpdate($defs{'TUYA_JL15'});;
2023-02-05 07:44:58,117 - ERROR - fhempy.lib.fhem: FHEM took 5983ms for readingsBeginUpdate($defs{'TUYA_JL07'});;
2023-02-05 08:30:05,156 - ERROR - fhempy.lib.fhem: FHEM took 5121ms for readingsBeginUpdate($defs{'TUYA_JL30'});;
fhem.log
2023.02.05 00:00:31 3: alexa: using logfile: ./log/alexa-2023-02-05.log
2023.02.05 00:00:50 3: TelegramBot_Callback TelegramBotTHB: Digest: Number of poll failures on 2023-02-04 is :1:
2023.02.05 00:01:41 1: PERL WARNING: Subroutine HandleTimeout redefined at ./FHEM/98_apptime.pm line 45.
2023.02.05 00:01:41 1: PERL WARNING: Subroutine CallFn redefined at ./FHEM/98_apptime.pm line 122.
2023.02.05 00:04:41 1: [Freezemon] myFreezemon: possible freeze starting at 00:04:40, delay is 1.103 possibly caused by: tmr-MQTT2_SERVER_keepaliveChecker(MQTT2)
2023.02.05 00:07:34 1: [Freezemon] myFreezemon: possible freeze starting at 00:07:26, delay is 8.084 possibly caused by: no bad guy found :-(
2023.02.05 00:10:00 3: DbRep ReportDbLog_THB - ################################################################
2023.02.05 00:10:00 3: DbRep ReportDbLog_THB - ### New database clientSide dump ###
2023.02.05 00:10:00 3: DbRep ReportDbLog_THB - ################################################################
2023.02.05 00:10:00 3: DbRep ReportDbLog_THB - Starting dump of database 'fhem'
2023.02.05 00:10:00 4: DbRep ReportDbLog_THB - Database connect - user: fhemuser, UTF-8 option set: yes
2023.02.05 00:10:00 4: DbRep ReportDbLog_THB - SQL execute: SELECT VERSION()
2023.02.05 00:10:00 4: DbRep ReportDbLog_THB - SQL execute: SET NAMES 'utf8'
2023.02.05 00:10:00 4: DbRep ReportDbLog_THB - SQL execute: SHOW VARIABLES LIKE 'character_set_connection'
2023.02.05 00:10:00 3: DbRep ReportDbLog_THB - Characterset of collection set to utf8.
2023.02.05 00:10:00 3: DbRep ReportDbLog_THB - Searching for tables inside database fhem....
2023.02.05 00:10:00 4: DbRep ReportDbLog_THB - SQL execute: SHOW TABLE STATUS FROM `fhem`
2023.02.05 00:10:00 4: DbRep ReportDbLog_THB - SQL execute: SELECT count(*) FROM `current`
2023.02.05 00:10:00 4: DbRep ReportDbLog_THB - SQL execute: SELECT count(*) FROM `history`
2023.02.05 00:10:04 3: DbRep ReportDbLog_THB - Found 2 tables with 1939011 records.
2023.02.05 00:10:04 3: DbRep ReportDbLog_THB - Dumping table current (Type InnoDB):
2023.02.05 00:10:04 4: DbRep ReportDbLog_THB - SQL execute: SHOW CREATE TABLE `current`
2023.02.05 00:10:04 4: DbRep ReportDbLog_THB - SQL execute: SHOW FIELDS FROM `current`
2023.02.05 00:10:04 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `current` LIMIT 0,10000;
2023.02.05 00:10:04 3: DbRep ReportDbLog_THB - 1146 records inserted (size of backupfile: 233.65 KB)
2023.02.05 00:10:04 3: DbRep ReportDbLog_THB - Dumping table history (Type InnoDB):
2023.02.05 00:10:04 4: DbRep ReportDbLog_THB - SQL execute: SHOW CREATE TABLE `history`
2023.02.05 00:10:04 4: DbRep ReportDbLog_THB - SQL execute: SHOW FIELDS FROM `history`
2023.02.05 00:10:04 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 0,10000;
2023.02.05 00:10:04 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 10000,10000;
2023.02.05 00:10:05 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 20000,10000;
2023.02.05 00:10:05 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 30000,10000;
2023.02.05 00:10:05 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 40000,10000;
2023.02.05 00:10:06 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 50000,10000;
2023.02.05 00:10:06 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 60000,10000;
2023.02.05 00:10:06 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 70000,10000;
2023.02.05 00:10:07 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 80000,10000;
2023.02.05 00:10:07 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 90000,10000;
2023.02.05 00:10:07 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 100000,10000;
2023.02.05 00:10:08 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 110000,10000;
2023.02.05 00:10:08 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 120000,10000;
2023.02.05 00:10:09 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 130000,10000;
2023.02.05 00:10:09 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 140000,10000;
2023.02.05 00:10:10 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 150000,10000;
2023.02.05 00:10:10 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 160000,10000;
2023.02.05 00:10:11 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 170000,10000;
2023.02.05 00:10:11 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 180000,10000;
2023.02.05 00:10:12 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 190000,10000;
2023.02.05 00:10:12 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 200000,10000;
2023.02.05 00:10:13 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 210000,10000;
2023.02.05 00:10:13 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 220000,10000;
2023.02.05 00:10:14 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 230000,10000;
2023.02.05 00:10:15 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 240000,10000;
2023.02.05 00:10:15 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 250000,10000;
2023.02.05 00:10:16 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 260000,10000;
2023.02.05 00:10:17 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 270000,10000;
2023.02.05 00:10:17 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 280000,10000;
2023.02.05 00:10:18 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 290000,10000;
2023.02.05 00:10:19 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 300000,10000;
2023.02.05 00:10:20 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 310000,10000;
2023.02.05 00:10:20 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 320000,10000;
2023.02.05 00:10:21 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 330000,10000;
2023.02.05 00:10:22 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 340000,10000;
2023.02.05 00:10:23 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 350000,10000;
2023.02.05 00:10:23 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 360000,10000;
2023.02.05 00:10:24 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 370000,10000;
2023.02.05 00:10:25 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 380000,10000;
2023.02.05 00:10:26 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 390000,10000;
2023.02.05 00:10:27 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 400000,10000;
2023.02.05 00:10:28 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 410000,10000;
2023.02.05 00:10:29 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 420000,10000;
2023.02.05 00:10:30 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 430000,10000;
2023.02.05 00:10:31 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 440000,10000;
2023.02.05 00:10:31 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 450000,10000;
2023.02.05 00:10:32 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 460000,10000;
2023.02.05 00:10:33 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 470000,10000;
2023.02.05 00:10:34 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 480000,10000;
2023.02.05 00:10:35 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 490000,10000;
2023.02.05 00:10:36 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 500000,10000;
2023.02.05 00:10:38 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 510000,10000;
2023.02.05 00:10:39 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 520000,10000;
2023.02.05 00:10:40 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 530000,10000;
2023.02.05 00:10:41 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 540000,10000;
2023.02.05 00:10:42 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 550000,10000;
2023.02.05 00:10:43 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 560000,10000;
2023.02.05 00:10:44 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 570000,10000;
2023.02.05 00:10:45 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 580000,10000;
2023.02.05 00:10:46 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 590000,10000;
2023.02.05 00:10:48 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 600000,10000;
2023.02.05 00:10:49 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 610000,10000;
2023.02.05 00:10:50 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 620000,10000;
2023.02.05 00:10:51 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 630000,10000;
2023.02.05 00:10:53 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 640000,10000;
2023.02.05 00:10:54 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 650000,10000;
2023.02.05 00:10:55 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 660000,10000;
2023.02.05 00:10:56 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 670000,10000;
2023.02.05 00:10:58 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 680000,10000;
2023.02.05 00:10:59 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 690000,10000;
2023.02.05 00:11:00 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 700000,10000;
2023.02.05 00:11:02 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 710000,10000;
2023.02.05 00:11:03 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 720000,10000;
2023.02.05 00:11:05 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 730000,10000;
2023.02.05 00:11:06 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 740000,10000;
2023.02.05 00:11:07 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 750000,10000;
2023.02.05 00:11:09 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 760000,10000;
2023.02.05 00:11:10 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 770000,10000;
2023.02.05 00:11:12 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 780000,10000;
2023.02.05 00:11:13 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 790000,10000;
2023.02.05 00:11:15 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 800000,10000;
2023.02.05 00:11:16 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 810000,10000;
2023.02.05 00:11:18 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 820000,10000;
2023.02.05 00:11:20 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 830000,10000;
2023.02.05 00:11:21 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 840000,10000;
2023.02.05 00:11:23 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 850000,10000;
2023.02.05 00:11:24 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 860000,10000;
2023.02.05 00:11:26 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 870000,10000;
2023.02.05 00:11:28 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 880000,10000;
2023.02.05 00:11:29 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 890000,10000;
2023.02.05 00:11:31 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 900000,10000;
2023.02.05 00:11:33 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 910000,10000;
2023.02.05 00:11:34 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 920000,10000;
2023.02.05 00:11:36 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 930000,10000;
2023.02.05 00:11:38 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 940000,10000;
2023.02.05 00:11:39 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 950000,10000;
2023.02.05 00:11:41 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 960000,10000;
2023.02.05 00:11:43 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 970000,10000;
2023.02.05 00:11:45 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 980000,10000;
2023.02.05 00:11:47 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 990000,10000;
2023.02.05 00:11:49 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1000000,10000;
2023.02.05 00:11:52 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1010000,10000;
2023.02.05 00:11:54 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1020000,10000;
2023.02.05 00:11:57 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1030000,10000;
2023.02.05 00:11:59 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1040000,10000;
2023.02.05 00:12:01 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1050000,10000;
2023.02.05 00:12:04 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1060000,10000;
2023.02.05 00:12:06 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1070000,10000;
2023.02.05 00:12:09 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1080000,10000;
2023.02.05 00:12:12 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1090000,10000;
2023.02.05 00:12:14 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1100000,10000;
2023.02.05 00:12:17 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1110000,10000;
2023.02.05 00:12:19 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1120000,10000;
2023.02.05 00:12:22 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1130000,10000;
2023.02.05 00:12:25 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1140000,10000;
2023.02.05 00:12:27 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1150000,10000;
2023.02.05 00:12:30 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1160000,10000;
2023.02.05 00:12:33 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1170000,10000;
2023.02.05 00:12:36 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1180000,10000;
2023.02.05 00:12:39 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1190000,10000;
2023.02.05 00:12:41 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1200000,10000;
2023.02.05 00:12:44 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1210000,10000;
2023.02.05 00:12:47 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1220000,10000;
2023.02.05 00:12:50 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1230000,10000;
2023.02.05 00:12:53 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1240000,10000;
2023.02.05 00:12:56 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1250000,10000;
2023.02.05 00:12:59 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1260000,10000;
2023.02.05 00:13:02 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1270000,10000;
2023.02.05 00:13:05 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1280000,10000;
2023.02.05 00:13:08 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1290000,10000;
2023.02.05 00:13:11 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1300000,10000;
2023.02.05 00:13:14 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1310000,10000;
2023.02.05 00:13:18 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1320000,10000;
2023.02.05 00:13:21 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1330000,10000;
2023.02.05 00:13:24 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1340000,10000;
2023.02.05 00:13:27 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1350000,10000;
2023.02.05 00:13:30 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1360000,10000;
2023.02.05 00:13:34 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1370000,10000;
2023.02.05 00:13:37 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1380000,10000;
2023.02.05 00:13:40 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1390000,10000;
2023.02.05 00:13:44 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1400000,10000;
2023.02.05 00:13:47 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1410000,10000;
2023.02.05 00:13:50 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1420000,10000;
2023.02.05 00:13:54 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1430000,10000;
2023.02.05 00:13:57 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1440000,10000;
2023.02.05 00:14:01 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1450000,10000;
2023.02.05 00:14:04 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1460000,10000;
2023.02.05 00:14:08 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1470000,10000;
2023.02.05 00:14:12 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1480000,10000;
2023.02.05 00:14:15 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1490000,10000;
2023.02.05 00:14:19 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1500000,10000;
2023.02.05 00:14:22 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1510000,10000;
2023.02.05 00:14:26 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1520000,10000;
2023.02.05 00:14:30 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1530000,10000;
2023.02.05 00:14:34 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1540000,10000;
2023.02.05 00:14:37 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1550000,10000;
2023.02.05 00:14:41 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1560000,10000;
2023.02.05 00:14:45 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1570000,10000;
2023.02.05 00:14:49 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1580000,10000;
2023.02.05 00:14:53 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1590000,10000;
2023.02.05 00:14:57 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1600000,10000;
2023.02.05 00:15:01 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1610000,10000;
2023.02.05 00:15:05 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1620000,10000;
2023.02.05 00:15:09 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1630000,10000;
2023.02.05 00:15:13 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1640000,10000;
2023.02.05 00:15:17 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1650000,10000;
2023.02.05 00:15:21 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1660000,10000;
2023.02.05 00:15:25 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1670000,10000;
2023.02.05 00:15:29 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1680000,10000;
2023.02.05 00:15:33 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1690000,10000;
2023.02.05 00:15:37 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1700000,10000;
2023.02.05 00:15:42 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1710000,10000;
2023.02.05 00:15:46 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1720000,10000;
2023.02.05 00:15:50 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1730000,10000;
2023.02.05 00:15:55 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1740000,10000;
2023.02.05 00:15:59 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1750000,10000;
2023.02.05 00:16:03 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1760000,10000;
2023.02.05 00:16:08 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1770000,10000;
2023.02.05 00:16:12 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1780000,10000;
2023.02.05 00:16:16 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1790000,10000;
2023.02.05 00:16:21 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1800000,10000;
2023.02.05 00:16:25 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1810000,10000;
2023.02.05 00:16:30 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1820000,10000;
2023.02.05 00:16:34 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1830000,10000;
2023.02.05 00:16:39 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1840000,10000;
2023.02.05 00:16:44 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1850000,10000;
2023.02.05 00:16:48 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1860000,10000;
2023.02.05 00:16:53 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1870000,10000;
2023.02.05 00:16:57 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1880000,10000;
2023.02.05 00:17:02 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1890000,10000;
2023.02.05 00:17:07 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1900000,10000;
2023.02.05 00:17:12 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1910000,10000;
2023.02.05 00:17:17 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1920000,10000;
2023.02.05 00:17:21 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1930000,10000;
2023.02.05 00:17:26 3: DbRep ReportDbLog_THB - 1937865 records inserted (size of backupfile: 383.78 MB)
2023.02.05 00:17:26 3: DbRep ReportDbLog_THB - Deleting old dumpfile 'fhem_2023_02_02_00_10.sql'
2023.02.05 00:17:26 3: DbRep ReportDbLog_THB - Finished backup of database fhem - total time used (hh:mm:ss): 00:07:26
2023.02.05 00:17:27 3: DbRep ReportDbLog_THB - Database dump finished successfully.
2023.02.05 00:44:25 2: Buderus : ERROR: Service: /system/sensors/temperatures/supply_t1: No proper Communication with Gateway: read from http://192.168.9.114:80 timed out
2023.02.05 01:29:18 2: Buderus : ERROR: Service: /heatingCircuits/hc1/roomtemperature: No proper Communication with Gateway: read from http://192.168.9.114:80 timed out
2023.02.05 02:09:05 1: [Freezemon] myFreezemon: possible freeze starting at 02:09:04, delay is 1.031 possibly caused by: tmr-CODE(0x4bab278)(GetUpdate)
2023.02.05 02:20:53 3: MaxSystem, Send Queue missing ack from MAX_HCH_HT for TimeInformation, removing from queue
2023.02.05 03:00:00 2: DbLog dblog_THB - Connection closed until 03:00:00 (86400 seconds).
2023.02.05 03:00:00 3: DbLog dblog_THB - Database disconnected by request.
2023.02.05 03:01:07 3: DbLog dblog_THB - Reopen requested
2023.02.05 03:01:08 2: DbRep Reduce_Daily - command message after reduceLog: "Reopen executed."
2023.02.05 03:01:08 3: DbLog dblog_THB - Database disconnected by request.
2023.02.05 03:01:08 3: DbLog dblog_THB - SubProcess connected to fhem
2023.02.05 03:19:13 1: PERL WARNING: Use of uninitialized value in numeric ge (>=) at ./FHEM/12_OilFox.pm line 387.
2023.02.05 03:19:13 2: LOGIN TOKEN MISSING OR EXPIRED
2023.02.05 03:19:13 3: Reconnecting...
2023.02.05 03:19:13 2: {"token_type":"Bearer","access_token":"eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzUxMiJ9.eyJzdWIiOiJiNmU5ZDg5Ni1kMzMwLTRiMWYtODVhNS0wYjk4NGQyZWJiMDQiLCJhdWQiOiJVU0VSIiwic2NvcGUiOiJDVVNUT01FUl9BUEkiLCJpc3MiOiJvaWxmb3guaW8iLCJleHAiOjE2NzU1NjQ0NTMsImp0aSI6IjE2NTBkYjRmLTQ0MDQtNGE4Ny04YjMyLWE0MDEzNWQxYWQzMSIsImVtYWlsIjoiYmt0QGdteC5uZXQifQ.QLqU_qMrJrIbxJKI3Khimc2KdmsA2P9oBibc2R-1PZkn-m8UGhso1pHr9vG7zrCMBAtKng87C4ExxL2kt633Fg","refresh_token":"eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzUxMiJ9.eyJzY29wZSI6IkNVU1RPTUVSX0FQSSIsImlzcyI6Im9pbGZveC5pbyIsImV4cCI6MTY3Njg1OTU1MywianRpIjoiZWJiOTBjOWUtMmE0NC00OTBmLWE3M2YtY2I2MTlmODdkYjQxIn0.OunwjSz7ntnnJmBAb-QW587f-9BcRBF7GpL4YOscrcj9UC3baejq9Ht2IZDdseEsVdm5cP1ucbOVEBhAOEZBYA"}
2023.02.05 04:00:00 3: DbRep Reduce_Hourly - ################################################################
2023.02.05 04:00:00 3: DbRep Reduce_Hourly - ### new reduceLog run ###
2023.02.05 04:00:00 3: DbRep Reduce_Hourly - ################################################################
2023.02.05 04:00:00 3: DbRep Reduce_Hourly - get initial structure information of database "fhem", remaining attempts: 3
2023.02.05 04:00:00 3: DbRep Reduce_Hourly - Connectiontest to database mysql:database=fhem;host=localhost;port=3306 with user fhemuser
2023.02.05 04:00:00 3: DbRep Reduce_Hourly - Index Report_Idx exists. Check ok
2023.02.05 04:00:00 3: DbRep Reduce_Hourly - Initial data information retrieved - total time used: 0.0124 seconds
2023.02.05 04:00:00 3: DbRep Reduce_Hourly - Connectiontest to db mysql:database=fhem;host=localhost;port=3306 successful
2023.02.05 04:00:00 3: DbRep Reduce_Hourly - execute command before reduceLog: 'set dblog_THB reopen 86400'
2023.02.05 04:00:00 2: DbLog dblog_THB - Connection closed until 04:00:00 (86400 seconds).
2023.02.05 04:00:00 3: DbRep Reduce_Hourly - reduce data older than: 2023-01-29 23:59:59, newer than: 2023-01-27 00:00:00
2023.02.05 04:00:00 3: DbRep Reduce_Hourly - reduceLog requested with options:
average=day
INCLUDE -> Devs: % Readings: %
2023.02.05 04:00:00 3: DbLog dblog_THB - Database disconnected by request.
2023.02.05 04:00:03 3: DbRep Reduce_Hourly - reduceLog deleting 67327 records of day: 2023-01-29
2023.02.05 04:00:08 3: DbRep Reduce_Hourly - reduceLog deletion progress of day: 2023-01-29 is: 10000
2023.02.05 04:00:13 3: DbRep Reduce_Hourly - reduceLog deletion progress of day: 2023-01-29 is: 20000
2023.02.05 04:00:18 3: DbRep Reduce_Hourly - reduceLog deletion progress of day: 2023-01-29 is: 30000
2023.02.05 04:00:23 3: DbRep Reduce_Hourly - reduceLog deletion progress of day: 2023-01-29 is: 40000
2023.02.05 04:00:28 3: DbRep Reduce_Hourly - reduceLog deletion progress of day: 2023-01-29 is: 50000
2023.02.05 04:00:33 3: DbRep Reduce_Hourly - reduceLog deletion progress of day: 2023-01-29 is: 60000
2023.02.05 04:00:38 3: DbRep Reduce_Hourly - reduceLog (hourly-average) updating 2193 records of day: 2023-01-29
2023.02.05 04:00:39 3: DbRep Reduce_Hourly - reduceLog (hourly-average) updating progress of day: 2023-01-29 is: 1000
2023.02.05 04:00:40 3: DbRep Reduce_Hourly - reduceLog (hourly-average) updating progress of day: 2023-01-29 is: 2000
2023.02.05 04:00:40 3: DbRep Reduce_Hourly - reduceLog (daily-average) updating 236, deleting 3524 records of day: 2023-01-29
2023.02.05 04:00:41 3: DbRep Reduce_Hourly - reduceLog (daily-average) deleting progress of day: 2023-01-29 is: 1000
2023.02.05 04:00:41 3: DbRep Reduce_Hourly - reduceLog (daily-average) updating progress of day: 2023-01-29 is: 100
2023.02.05 04:00:42 3: DbRep Reduce_Hourly - reduceLog (daily-average) deleting progress of day: 2023-01-29 is: 2000
2023.02.05 04:00:42 3: DbRep Reduce_Hourly - reduceLog (daily-average) updating progress of day: 2023-01-29 is: 200
2023.02.05 04:00:42 3: DbRep Reduce_Hourly - reduceLog (daily-average) deleting progress of day: 2023-01-29 is: 3000
2023.02.05 04:00:43 3: DbRep Reduce_Hourly - reduceLog finished. Rows processed: 77661, deleted: 70851, updated: 2429
2023.02.05 04:00:43 3: DbLog dblog_THB - Reopen requested
2023.02.05 04:00:43 2: DbRep Reduce_Hourly - command message after reduceLog: "Reopen executed."
2023.02.05 04:00:43 3: DbLog dblog_THB - Database disconnected by request.
2023.02.05 04:00:43 3: DbLog dblog_THB - SubProcess connected to fhem
2023.02.05 05:00:00 2: DbLog dblog_THB - WARNING - "count" is outdated. Please consider use of DbRep "set <Name> countEntries" instead.
2023.02.05 06:00:00 3: DbLog dblog_THB - Reopen requested
2023.02.05 06:00:00 3: set dblog_THB reopen : Reopen executed.
2023.02.05 06:00:00 3: DbLog_reopen: Reopen executed.
2023.02.05 06:00:00 3: DbLog dblog_THB - Database disconnected by request.
2023.02.05 06:00:00 3: DbLog dblog_THB - SubProcess connected to fhem
2023.02.05 06:01:31 1: [Freezemon] myFreezemon: possible freeze starting at 06:01:27, delay is 4.516 possibly caused by: no bad guy found :-(
2023.02.05 06:31:51 2: Buderus : ERROR: Service: /heatSources/actualModulation: No proper Communication with Gateway: read from http://192.168.9.114:80 timed out
2023.02.05 06:44:07 1: [Freezemon] myFreezemon: possible freeze starting at 06:44:06, delay is 1.047 possibly caused by: no bad guy found :-(
2023.02.05 06:47:01 1: [Freezemon] myFreezemon: possible freeze starting at 06:47:00, delay is 1.003 possibly caused by: no bad guy found :-(
2023.02.05 07:04:11 1: [Freezemon] myFreezemon: possible freeze starting at 07:04:10, delay is 1.025 possibly caused by: no bad guy found :-(
2023.02.05 07:20:55 3: MaxSystem, Send Queue missing ack from MAX_Wohnzimmer_O for TimeInformation, removing from queue
2023.02.05 07:44:48 3: Untergeschoss_Rollo_Alle_up_Notify return value: OK
2023.02.05 07:44:50 3: Untergeschoss_Rollo_2_up_Notify return value: OK
2023.02.05 07:44:52 3: Wohnzimmer_Rollo_1_up_Notify return value: OK
2023.02.05 07:44:55 3: Wohnzimmer_Rollo_2_up_Notify return value: OK
2023.02.05 07:44:57 3: Wohnzimmer_Rollo_3_up_Notify return value: OK
2023.02.05 07:44:57 1: [Freezemon] myFreezemon: possible freeze starting at 07:44:46, delay is 11.456 possibly caused by: tmr-at_Exec(Untergeschoss_Rollos_bei_Sonnenaufgang_hoch_AT) tmr-at_Exec(Untergeschoss_Rollo_2_bei_Sonnenaufgang_hoch_AT) tmr-at_Exec(Wohnzimmer_Rollo_1_bei_Sonnenaufgang_hoch_AT) tmr-at_Exec(Wohnzimmer_Rollo_2_bei_Sonnenaufgang_hoch_AT) tmr-at_Exec(Wohnzimmer_Rollo_3_bei_Sonnenaufgang_hoch_AT)
2023.02.05 07:48:08 3: Untergeschoss_Rollo_1_up_Notify return value: OK
2023.02.05 07:48:08 1: [Freezemon] myFreezemon: possible freeze starting at 07:48:06, delay is 2.248 possibly caused by: tmr-at_Exec(Untergeschoss_Rollo_1_bei_Sonnenaufgang_hoch_AT)
2023.02.05 08:04:48 3: Kueche_Rollo_3_up_Notify return value: OK
2023.02.05 08:04:48 1: [Freezemon] myFreezemon: possible freeze starting at 08:04:46, delay is 2.352 possibly caused by: tmr-at_Exec(Kueche_Rollo_3_bei_Sonnenaufgang_hoch_AT)
2023.02.05 08:22:11 1: [Freezemon] myFreezemon: possible freeze starting at 08:22:10, delay is 1.394 possibly caused by: no bad guy found :-(
2023.02.05 08:27:19 1: [Freezemon] myFreezemon: possible freeze starting at 08:27:18, delay is 1.017 possibly caused by: tmr-HUEBridge_GetUpdate(hueBridge1)
2023.02.05 08:30:02 3: Wohnzimmer_Rollo_Alle_up_Notify return value: OK
2023.02.05 08:30:04 3: Untergeschoss_Rollo_3_up_Notify return value: OK
2023.02.05 08:30:04 1: [Freezemon] myFreezemon: possible freeze starting at 08:30:00, delay is 4.695 possibly caused by: tmr-at_Exec(Wohnzimmer_Rollos_bei_Sonnenaufgang_hoch_AT) tmr-at_Exec(Untergeschoss_Rollo_3_bei_Sonnenaufgang_hoch_AT)
2023.02.05 09:17:45 1: [Freezemon] myFreezemon: possible freeze starting at 09:17:39, delay is 6.668 possibly caused by: no bad guy found :-(
2023.02.05 09:18:56 1: [Freezemon] myFreezemon: possible freeze starting at 09:18:45, delay is 11.05 possibly caused by: no bad guy found :-(
2023.02.05 09:19:20 1: [Freezemon] myFreezemon: possible freeze starting at 09:19:19, delay is 1.004 possibly caused by: tmr-HUEBridge_GetUpdate(hueBridge1)
2023.02.05 09:30:02 3: Obergeschoss_Rollo_1_up_Notify return value: OK
2023.02.05 09:30:02 1: [Freezemon] myFreezemon: possible freeze starting at 09:30:00, delay is 2.188 possibly caused by: tmr-CUL_MAX_Alive(MaxSystem) tmr-MAX_Timer(MAX_BAD_WT) tmr-MAX_Timer(MAX_BAD_HT) tmr-MAX_Timer(MAX_DIELE_HT) tmr-MAX_Timer(MAX_HWR_HT) tmr-MAX_Timer(MAX_HCH_HT) tmr-MAX_Timer(MAX_PETRA_WT) tmr-MAX_Timer(MAX_PETRA_HT1) tmr-MAX_Timer(MAX_PETRA_HT2) tmr-MAX_Timer(MAX_PETRA_HT3) tmr-MAX_Timer(MAX_Schlafzimmer_WT) tmr-MAX_Timer(MAX_Schlafzimmer_HT) tmr-MAX_Timer(MAX_Treppenhaus_WT) tmr-MAX_Timer(MAX_Treppenhaus_HT) tmr-MAX_Timer(MAX_THOMAS_WT) tmr-MAX_Timer(MAX_THOMAS_HT1) tmr-MAX_Timer(MAX_THOMAS_HT2) tmr-MAX_Timer(MAX_TOILETTE_HT) tmr-MAX_Timer(MAX_Wohnzimmer_WT) tmr-MAX_Timer(MAX_Wohnzimmer_O) tmr-MAX_Timer(MAX_Wohnzimmer_SO) tmr-MAX_Timer(MAX_Wohnzimmer_SW) tmr-MAX_Timer(MAX_BAD_F1) tmr-MAX_Timer(MAX_HWR_F1) tmr-MAX_Timer(MAX_KCH_F1) tmr-MAX_Timer(MAX_PETRA_F2) tmr-MAX_Timer(MAX_Schlafzimmer_F1) tmr-MAX_Timer(MAX_THOMAS_F1) tmr-MAX_Timer(MAX_THOMAS_F3) tmr-MAX_Timer(MAX_TOILETTE_F1) tmr-MAX_Timer(MAX_Wohnzimmer_F1) tmr-at_Exec(Obergeschoss_Rollo_1_bei_Sonnenaufgang_hoch_AT)
um 09:15 hatte ich mich an den PC gesetzt und das WebFrontend von FHEM aufgerufen.
die tmr.MAX tauchen wohl nur alle mehrere Stunden mal auf.
AppTime:
active-timers: 83; max-active timers: 86; max-timer-load: 34 min-tmrHandlingTm: 0.0ms; max-tmrHandlingTm: 11701.7ms; totAvgDly: 39.8ms
name function max count total average maxDly avgDly TS Max call param Max call
tmr-at_Exec HASH(0x5836000) 2556 1 2556.71 2556.71 0.41 0.41 05.02. 07:44:48 HASH(Untergeschoss_Rollos_bei_Sonnenaufgang_hoch_AT)
tmr-at_Exec HASH(0x58086d0) 2504 1 2504.82 2504.82 0.76 0.76 05.02. 08:30:02 HASH(Wohnzimmer_Rollos_bei_Sonnenaufgang_hoch_AT)
Wohnzimmer_Rollo_Alle dummy_Set 2502 2 2502.47 1251.24 0.00 0.00 05.02. 08:30:02 HASH(Wohnzimmer_Rollo_Alle); Wohnzimmer_Rollo_Alle; up
Untergeschoss_Rollo_Alle dummy_Set 2501 2 2501.29 1250.65 0.00 0.00 05.02. 07:44:48 HASH(Untergeschoss_Rollo_Alle); Untergeschoss_Rollo_Alle; up
Wohnzimmer_Rollo_Alle_up_Notify notify_Exec 2397 1 2397.67 2397.67 0.00 0.00 05.02. 08:30:02 HASH(Wohnzimmer_Rollo_Alle_up_Notify); HASH(Wohnzimmer_Rollo_Alle)
Untergeschoss_Rollo_Alle_up_Notify notify_Exec 2397 1 2397.35 2397.35 0.00 0.00 05.02. 07:44:48 HASH(Untergeschoss_Rollo_Alle_up_Notify); HASH(Untergeschoss_Rollo_Alle)
tmr-at_Exec HASH(0x583ef60) 2352 1 2352.40 2352.40 0.29 0.29 05.02. 08:04:48 HASH(Kueche_Rollo_3_bei_Sonnenaufgang_hoch_AT)
Kueche_Rollo_3 dummy_Set 2298 2 2298.21 1149.11 0.00 0.00 05.02. 08:04:48 HASH(Kueche_Rollo_3); Kueche_Rollo_3; up
tmr-at_Exec HASH(0x583ff40) 2240 1 2240.14 2240.14 4775.45 4775.45 05.02. 07:44:53 HASH(Wohnzimmer_Rollo_1_bei_Sonnenaufgang_hoch_AT)
tmr-at_Exec HASH(0x5842288) 2225 1 2225.53 2225.53 7015.70 7015.70 05.02. 07:44:55 HASH(Wohnzimmer_Rollo_2_bei_Sonnenaufgang_hoch_AT)
tmr-at_Exec HASH(0x5835f10) 2220 1 2220.09 2220.09 28.56 28.56 05.02. 07:48:08 HASH(Untergeschoss_Rollo_1_bei_Sonnenaufgang_hoch_AT)
tmr-at_Exec HASH(0x5836fe0) 2218 1 2218.14 2218.14 2557.21 2557.21 05.02. 07:44:50 HASH(Untergeschoss_Rollo_2_bei_Sonnenaufgang_hoch_AT)
tmr-at_Exec HASH(0x5842ca8) 2214 1 2214.86 2214.86 9241.32 9241.32 05.02. 07:44:57 HASH(Wohnzimmer_Rollo_3_bei_Sonnenaufgang_hoch_AT)
tmr-at_Exec HASH(0x5837850) 2189 1 2189.67 2189.67 2505.69 2505.69 05.02. 08:30:04 HASH(Untergeschoss_Rollo_3_bei_Sonnenaufgang_hoch_AT)
Untergeschoss_Rollo_3 dummy_Set 2187 4 2292.84 573.21 0.00 0.00 05.02. 08:30:04 HASH(Untergeschoss_Rollo_3); Untergeschoss_Rollo_3; up
tmr-at_Exec HASH(0x583e6f0) 2187 1 2187.38 2187.38 0.51 0.51 05.02. 09:30:02 HASH(Obergeschoss_Rollo_1_bei_Sonnenaufgang_hoch_AT)
Obergeschoss_Rollo_1 dummy_Set 2185 2 2185.05 1092.52 0.00 0.00 05.02. 09:30:02 HASH(Obergeschoss_Rollo_1); Obergeschoss_Rollo_1; up
Wohnzimmer_Rollo_1 dummy_Set 2184 4 2349.38 587.35 0.00 0.00 05.02. 07:44:52 HASH(Wohnzimmer_Rollo_1); Wohnzimmer_Rollo_1; up
Wohnzimmer_Rollo_2 dummy_Set 2171 4 2275.96 568.99 0.00 0.00 05.02. 07:44:55 HASH(Wohnzimmer_Rollo_2); Wohnzimmer_Rollo_2; up
Untergeschoss_Rollo_1 dummy_Set 2164 4 2325.08 581.27 0.00 0.00 05.02. 07:48:08 HASH(Untergeschoss_Rollo_1); Untergeschoss_Rollo_1; up
Untergeschoss_Rollo_2 dummy_Set 2164 4 2268.92 567.23 0.00 0.00 05.02. 07:44:50 HASH(Untergeschoss_Rollo_2); Untergeschoss_Rollo_2; up
Wohnzimmer_Rollo_3 dummy_Set 2160 4 2265.04 566.26 0.00 0.00 05.02. 07:44:57 HASH(Wohnzimmer_Rollo_3); Wohnzimmer_Rollo_3; up
Kueche_Rollo_3_up_Notify notify_Exec 2156 1 2156.66 2156.66 0.00 0.00 05.02. 08:04:48 HASH(Kueche_Rollo_3_up_Notify); HASH(Kueche_Rollo_3)
Untergeschoss_Rollo_3_up_Notify notify_Exec 2037 2 2037.82 1018.91 0.00 0.00 05.02. 08:30:04 HASH(Untergeschoss_Rollo_3_up_Notify); HASH(Untergeschoss_Rollo_3)
Wohnzimmer_Rollo_3_up_Notify notify_Exec 2026 2 2026.59 1013.29 0.00 0.00 05.02. 07:44:57 HASH(Wohnzimmer_Rollo_3_up_Notify); HASH(Wohnzimmer_Rollo_3)
Wohnzimmer_Rollo_2_up_Notify notify_Exec 2026 2 2026.40 1013.20 0.00 0.00 05.02. 07:44:55 HASH(Wohnzimmer_Rollo_2_up_Notify); HASH(Wohnzimmer_Rollo_2)
Obergeschoss_Rollo_1_up_Notify notify_Exec 2023 1 2023.68 2023.68 0.00 0.00 05.02. 09:30:02 HASH(Obergeschoss_Rollo_1_up_Notify); HASH(Obergeschoss_Rollo_1)
Untergeschoss_Rollo_2_up_Notify notify_Exec 2022 2 2022.81 1011.41 0.00 0.00 05.02. 07:44:50 HASH(Untergeschoss_Rollo_2_up_Notify); HASH(Untergeschoss_Rollo_2)
Untergeschoss_Rollo_1_up_Notify notify_Exec 2022 2 2023.00 1011.50 0.00 0.00 05.02. 07:48:08 HASH(Untergeschoss_Rollo_1_up_Notify); HASH(Untergeschoss_Rollo_1)
Wohnzimmer_Rollo_1_up_Notify notify_Exec 2021 2 2022.50 1011.25 0.00 0.00 05.02. 07:44:52 HASH(Wohnzimmer_Rollo_1_up_Notify); HASH(Wohnzimmer_Rollo_1)
CUL_0 CUL_Read 1460 3130 779899.50 249.17 0.00 0.00 05.02. 09:22:11 HASH(CUL_0)
local_pybinding CODE(0x47b7310) 1230 376849 8850518.06 23.49 0.00 0.00 05.02. 07:44:59 HASH(local_pybinding)
WEB_127.0.0.1_49226 FW_Notify 1166 100638 3305708.51 32.85 0.00 0.00 05.02. 07:44:59 HASH(WEB_127.0.0.1_49226); HASH(TUYA_JL06)
TUYA_JL06 fhempy_Set 1164 1312 72362.01 55.15 0.00 0.00 05.02. 07:44:59 HASH(TUYA_JL06); ARRAY(0x5f540e0); HASH(0x79b5190)
TUYA_JL30 fhempy_Set 1050 4090 224349.78 54.85 0.00 0.00 05.02. 07:44:59 HASH(TUYA_JL30); ARRAY(0x6b2e880); HASH(0x7a4b9b8)
TUYA_JL18 fhempy_Set 940 1488 85734.12 57.62 0.00 0.00 05.02. 07:44:59 HASH(TUYA_JL18); ARRAY(0x78bbd20); HASH(0x85e72a0)
TUYA_JL31 fhempy_Set 871 3985 217384.02 54.55 0.00 0.00 05.02. 06:01:33 HASH(TUYA_JL31); ARRAY(0x79f42a0); HASH(0x5b91ce8)
TUYA_JL24 fhempy_Set 830 3722 189704.58 50.97 0.00 0.00 05.02. 00:44:38 HASH(TUYA_JL24); ARRAY(0x7a694a0); HASH(0x5a86cd8)
TUYA_JL29 fhempy_Set 808 3778 222937.95 59.01 0.00 0.00 05.02. 07:44:59 HASH(TUYA_JL29); ARRAY(0x75ba8d0); HASH(0x5d38ed0)
TUYA_JL15 fhempy_Set 779 3918 221111.62 56.43 0.00 0.00 05.02. 03:20:45 HASH(TUYA_JL15); ARRAY(0x888c5d0); HASH(0x703c738)
dblog_THB DbLog_Log 775 100638 7611640.05 75.63 0.00 0.00 05.02. 03:20:48 HASH(dblog_THB); HASH(WU_IPLIEZ_1)
das sind die üblichen Vorkommnisse per Timer oder eben TUYA
Solange Fhemy wohl nicht suchen muss ist auch Ruhehe.
Gestern Abend hatte ich gegen 23:00 noch mehrfach den room Fhempy aufgerufen (schnell) und ein paar Bezeichnungen und Plots angepasst. Da kam dann promt einiges forn FreezeMon...
hier das Log von FreezeMon der letzten Minuten:
2023.02.05 09:19:19.372 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2023.02.05 09:19:19.382 5: BindingsIo (local_pybinding): DevIo_SimpleRead WithTimeout
2023.02.05 09:19:19.382 5: BindingsIo (local_pybinding): QUEUE: start handling - 7
2023.02.05 09:19:19.382 5: processMessage: {"awaitId": 35196052, "NAME": "TUYA_SP03", "msgtype": "command", "command": "readingsEndUpdate($defs{'TUYA_SP03'},1);;"}
2023.02.05 09:19:19.383 5: processMessage: {"awaitId": 80839845, "NAME": "TUYA_SP09", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP09'},'dp_21','1');;"}
2023.02.05 09:19:19.383 5: processMessage: {"awaitId": 12653493, "NAME": "TUYA_SP11", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP11'},'dp_21','1');;"}
2023.02.05 09:19:19.383 5: processMessage: {"awaitId": 12158569, "NAME": "TUYA_SP08", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP08'},'dp_21','1');;"}
2023.02.05 09:19:19.383 5: processMessage: {"awaitId": 12653496, "NAME": "TUYA_SP12", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP12'},'dp_21','1');;"}
2023.02.05 09:19:19.383 5: processMessage: {"awaitId": 86201351, "NAME": "TUYA_JL33", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_JL33'},'cur_power','758.0');;"}
2023.02.05 09:19:19.383 5: processMessage: {"awaitId": 42537394, "NAME": "TUYA_JL30", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_JL30'},'online','1');;"}
2023.02.05 09:19:19.384 5: BindingsIo (local_pybinding): QUEUE: finished handling - 7
2023.02.05 09:19:19.384 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2023.02.05 09:19:19.394 5: BindingsIo (local_pybinding): DevIo_SimpleRead WithTimeout
2023.02.05 09:19:19.394 5: BindingsIo (local_pybinding): QUEUE: start handling - 7
2023.02.05 09:19:19.395 5: processMessage: {"awaitId": 35196052, "NAME": "TUYA_SP03", "msgtype": "command", "command": "readingsEndUpdate($defs{'TUYA_SP03'},1);;"}
2023.02.05 09:19:19.395 5: processMessage: {"awaitId": 80839845, "NAME": "TUYA_SP09", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP09'},'dp_21','1');;"}
2023.02.05 09:19:19.395 5: processMessage: {"awaitId": 12653493, "NAME": "TUYA_SP11", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP11'},'dp_21','1');;"}
2023.02.05 09:19:19.395 5: processMessage: {"awaitId": 12158569, "NAME": "TUYA_SP08", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP08'},'dp_21','1');;"}
2023.02.05 09:19:19.395 5: processMessage: {"awaitId": 12653496, "NAME": "TUYA_SP12", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP12'},'dp_21','1');;"}
2023.02.05 09:19:19.395 5: processMessage: {"awaitId": 86201351, "NAME": "TUYA_JL33", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_JL33'},'cur_power','758.0');;"}
2023.02.05 09:19:19.396 5: processMessage: {"awaitId": 42537394, "NAME": "TUYA_JL30", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_JL30'},'online','1');;"}
2023.02.05 09:19:19.396 5: BindingsIo (local_pybinding): QUEUE: finished handling - 7
2023.02.05 09:19:19.396 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2023.02.05 09:19:19.401 5: BindingsIo (local_pybinding): DevIo_SimpleRead WithTimeout
2023.02.05 09:19:19.401 4: BindingsIo (local_pybinding): >>> WS: {"awaitId": 92954678, "NAME": "TUYA_SP05", "msgtype": "command", "command": "readingsEndUpdate($defs{'TUYA_SP05'},1);;"}
2023.02.05 09:19:19.402 5: BindingsIo (local_pybinding): QUEUE: start handling - 8
2023.02.05 09:19:19.402 5: processMessage: {"awaitId": 35196052, "NAME": "TUYA_SP03", "msgtype": "command", "command": "readingsEndUpdate($defs{'TUYA_SP03'},1);;"}
2023.02.05 09:19:19.402 5: processMessage: {"awaitId": 80839845, "NAME": "TUYA_SP09", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP09'},'dp_21','1');;"}
2023.02.05 09:19:19.402 5: processMessage: {"awaitId": 12653493, "NAME": "TUYA_SP11", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP11'},'dp_21','1');;"}
2023.02.05 09:19:19.402 5: processMessage: {"awaitId": 12158569, "NAME": "TUYA_SP08", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP08'},'dp_21','1');;"}
2023.02.05 09:19:19.403 5: processMessage: {"awaitId": 12653496, "NAME": "TUYA_SP12", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP12'},'dp_21','1');;"}
2023.02.05 09:19:19.403 5: processMessage: {"awaitId": 86201351, "NAME": "TUYA_JL33", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_JL33'},'cur_power','758.0');;"}
2023.02.05 09:19:19.403 5: processMessage: {"awaitId": 42537394, "NAME": "TUYA_JL30", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_JL30'},'online','1');;"}
2023.02.05 09:19:19.403 5: processMessage: {"awaitId": 92954678, "NAME": "TUYA_SP05", "msgtype": "command", "command": "readingsEndUpdate($defs{'TUYA_SP05'},1);;"}
2023.02.05 09:19:19.404 5: BindingsIo (local_pybinding): QUEUE: finished handling - 8
2023.02.05 09:19:19.404 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2023.02.05 09:19:19.404 5: BindingsIo (local_pybinding): DevIo_SimpleRead WithTimeout
2023.02.05 09:19:19.404 4: BindingsIo (local_pybinding): >>> WS: {"awaitId": 12871118, "NAME": "TUYA_SP07", "msgtype": "command", "command": "readingsEndUpdate($defs{'TUYA_SP07'},1);;"}
2023.02.05 09:19:19.405 5: BindingsIo (local_pybinding): QUEUE: start handling - 9
2023.02.05 09:19:19.405 5: processMessage: {"awaitId": 35196052, "NAME": "TUYA_SP03", "msgtype": "command", "command": "readingsEndUpdate($defs{'TUYA_SP03'},1);;"}
2023.02.05 09:19:19.405 5: processMessage: {"awaitId": 80839845, "NAME": "TUYA_SP09", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP09'},'dp_21','1');;"}
2023.02.05 09:19:19.405 5: processMessage: {"awaitId": 12653493, "NAME": "TUYA_SP11", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP11'},'dp_21','1');;"}
2023.02.05 09:19:19.405 5: processMessage: {"awaitId": 12158569, "NAME": "TUYA_SP08", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP08'},'dp_21','1');;"}
2023.02.05 09:19:19.405 5: processMessage: {"awaitId": 12653496, "NAME": "TUYA_SP12", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP12'},'dp_21','1');;"}
2023.02.05 09:19:19.406 5: processMessage: {"awaitId": 86201351, "NAME": "TUYA_JL33", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_JL33'},'cur_power','758.0');;"}
2023.02.05 09:19:19.406 5: processMessage: {"awaitId": 42537394, "NAME": "TUYA_JL30", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_JL30'},'online','1');;"}
2023.02.05 09:19:19.406 5: processMessage: {"awaitId": 92954678, "NAME": "TUYA_SP05", "msgtype": "command", "command": "readingsEndUpdate($defs{'TUYA_SP05'},1);;"}
2023.02.05 09:19:19.406 5: processMessage: {"awaitId": 12871118, "NAME": "TUYA_SP07", "msgtype": "command", "command": "readingsEndUpdate($defs{'TUYA_SP07'},1);;"}
2023.02.05 09:19:19.407 5: BindingsIo (local_pybinding): QUEUE: finished handling - 9
2023.02.05 09:19:19.407 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2023.02.05 09:19:19.407 5: BindingsIo (local_pybinding): DevIo_SimpleRead WithTimeout
2023.02.05 09:19:19.407 4: BindingsIo (local_pybinding): >>> WS: {"awaitId": 69476713, "NAME": "TUYA_SP13", "msgtype": "command", "command": "readingsBeginUpdate($defs{'TUYA_SP13'});;"}
2023.02.05 09:19:19.408 4: BindingsIo (local_pybinding): >>> WS: {"FHEMPYTYPE": "tuya", "id": 27039214, "defargsh": {}, "defargs": ["TUYA_SP01", "fhempy", "tuya", "IGzCi97RpN2Lf9cu", "260064612cf432ca55d8", "192.168.9.31", "52a00c366067a6f7", "3.3", "ea8453wdazquzfl08l0e", "8a4b27dd759d4c6a9456aa8155d2a0ea"], "msgtype": "function", "argsh": {}, "function": "Set", "PYTHONTYPE": "tuya", "NAME": "TUYA_SP01", "args": ["TUYA_SP01", "?"], "finished": 1, "returnval": "Unknown argument ?, choose one of on:noArg off:noArg countdown_1:slider,0.0,1.0,86400.0"}
2023.02.05 09:19:19.408 5: BindingsIo (local_pybinding): QUEUE: start handling - 11
2023.02.05 09:19:19.408 5: processMessage: {"awaitId": 35196052, "NAME": "TUYA_SP03", "msgtype": "command", "command": "readingsEndUpdate($defs{'TUYA_SP03'},1);;"}
2023.02.05 09:19:19.408 5: processMessage: {"awaitId": 80839845, "NAME": "TUYA_SP09", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP09'},'dp_21','1');;"}
2023.02.05 09:19:19.408 5: processMessage: {"awaitId": 12653493, "NAME": "TUYA_SP11", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP11'},'dp_21','1');;"}
2023.02.05 09:19:19.409 5: processMessage: {"awaitId": 12158569, "NAME": "TUYA_SP08", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP08'},'dp_21','1');;"}
2023.02.05 09:19:19.409 5: processMessage: {"awaitId": 12653496, "NAME": "TUYA_SP12", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP12'},'dp_21','1');;"}
2023.02.05 09:19:19.409 5: processMessage: {"awaitId": 86201351, "NAME": "TUYA_JL33", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_JL33'},'cur_power','758.0');;"}
2023.02.05 09:19:19.409 5: processMessage: {"awaitId": 42537394, "NAME": "TUYA_JL30", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_JL30'},'online','1');;"}
2023.02.05 09:19:19.409 5: processMessage: {"awaitId": 92954678, "NAME": "TUYA_SP05", "msgtype": "command", "command": "readingsEndUpdate($defs{'TUYA_SP05'},1);;"}
2023.02.05 09:19:19.409 5: processMessage: {"awaitId": 12871118, "NAME": "TUYA_SP07", "msgtype": "command", "command": "readingsEndUpdate($defs{'TUYA_SP07'},1);;"}
2023.02.05 09:19:19.409 5: processMessage: {"awaitId": 69476713, "NAME": "TUYA_SP13", "msgtype": "command", "command": "readingsBeginUpdate($defs{'TUYA_SP13'});;"}
2023.02.05 09:19:19.410 5: processMessage: {"FHEMPYTYPE": "tuya", "id": 27039214, "defargsh": {}, "defargs": ["TUYA_SP01", "fhempy", "tuya", "IGzCi97RpN2Lf9cu", "260064612cf432ca55d8", "192.168.9.31", "52a00c366067a6f7", "3.3", "ea8453wdazquzfl08l0e", "8a4b27dd759d4c6a9456aa8155d2a0ea"], "msgtype": "function", "argsh": {}, "function": "Set", "PYTHONTYPE": "tuya", "NAME": "TUYA_SP01", "args": ["TUYA_SP01", "?"], "finished": 1, "returnval": "Unknown argument ?, choose one of on:noArg off:noArg countdown_1:slider,0.0,1.0,86400.0"}
2023.02.05 09:19:19.410 5: BindingsIo (local_pybinding): QUEUE: finished handling - 10
2023.02.05 09:19:19.410 4: BindingsIo (local_pybinding): end fhempyFunction: TUYA_SP01 => Set (27039214) - result: Unknown argument ?, choose one of on:noArg off:noArg countdown_1:slider,0.0,1.0,86400.0
2023.02.05 09:19:19.410 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2023.02.05 09:19:19.411 5: BindingsIo (local_pybinding): DevIo_SimpleRead NoTimeout
2023.02.05 09:19:19.411 5: BindingsIo (local_pybinding): QUEUE: start handling - 10
2023.02.05 09:19:19.411 5: processMessage: {"awaitId": 35196052, "NAME": "TUYA_SP03", "msgtype": "command", "command": "readingsEndUpdate($defs{'TUYA_SP03'},1);;"}
2023.02.05 09:19:19.411 4: BindingsIo (local_pybinding): <<< WS: {"awaitId":35196052,"result":null,"error":0}
2023.02.05 09:19:19.411 5: DevIo_SimpleWrite local_pybinding: 7b2261776169744964223a33353139363035322c22726573756c74223a6e756c6c2c226572726f72223a307d
2023.02.05 09:19:19.413 5: processMessage: {"awaitId": 80839845, "NAME": "TUYA_SP09", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP09'},'dp_21','1');;"}
2023.02.05 09:19:19.413 4: BindingsIo (local_pybinding): <<< WS: {"awaitId":80839845,"result":null,"error":0}
2023.02.05 09:19:19.413 5: DevIo_SimpleWrite local_pybinding: 7b2261776169744964223a38303833393834352c22726573756c74223a6e756c6c2c226572726f72223a307d
2023.02.05 09:19:19.415 5: processMessage: {"awaitId": 12653493, "NAME": "TUYA_SP11", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP11'},'dp_21','1');;"}
2023.02.05 09:19:19.415 4: BindingsIo (local_pybinding): <<< WS: {"error":0,"result":null,"awaitId":12653493}
2023.02.05 09:19:19.415 5: DevIo_SimpleWrite local_pybinding: 7b226572726f72223a302c22726573756c74223a6e756c6c2c2261776169744964223a31323635333439337d
2023.02.05 09:19:19.416 5: processMessage: {"awaitId": 12158569, "NAME": "TUYA_SP08", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP08'},'dp_21','1');;"}
2023.02.05 09:19:19.417 4: BindingsIo (local_pybinding): <<< WS: {"awaitId":12158569,"result":null,"error":0}
2023.02.05 09:19:19.417 5: DevIo_SimpleWrite local_pybinding: 7b2261776169744964223a31323135383536392c22726573756c74223a6e756c6c2c226572726f72223a307d
2023.02.05 09:19:19.419 5: processMessage: {"awaitId": 12653496, "NAME": "TUYA_SP12", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP12'},'dp_21','1');;"}
2023.02.05 09:19:19.419 4: BindingsIo (local_pybinding): <<< WS: {"awaitId":12653496,"result":null,"error":0}
2023.02.05 09:19:19.419 5: DevIo_SimpleWrite local_pybinding: 7b2261776169744964223a31323635333439362c22726573756c74223a6e756c6c2c226572726f72223a307d
2023.02.05 09:19:19.421 5: processMessage: {"awaitId": 86201351, "NAME": "TUYA_JL33", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_JL33'},'cur_power','758.0');;"}
2023.02.05 09:19:19.421 4: BindingsIo (local_pybinding): <<< WS: {"error":0,"result":null,"awaitId":86201351}
2023.02.05 09:19:19.421 5: DevIo_SimpleWrite local_pybinding: 7b226572726f72223a302c22726573756c74223a6e756c6c2c2261776169744964223a38363230313335317d
2023.02.05 09:19:19.422 5: processMessage: {"awaitId": 42537394, "NAME": "TUYA_JL30", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_JL30'},'online','1');;"}
2023.02.05 09:19:19.423 4: BindingsIo (local_pybinding): <<< WS: {"error":0,"awaitId":42537394,"result":null}
2023.02.05 09:19:19.423 5: DevIo_SimpleWrite local_pybinding: 7b226572726f72223a302c2261776169744964223a34323533373339342c22726573756c74223a6e756c6c7d
2023.02.05 09:19:19.424 5: processMessage: {"awaitId": 92954678, "NAME": "TUYA_SP05", "msgtype": "command", "command": "readingsEndUpdate($defs{'TUYA_SP05'},1);;"}
2023.02.05 09:19:19.425 4: BindingsIo (local_pybinding): <<< WS: {"error":0,"result":null,"awaitId":92954678}
2023.02.05 09:19:19.425 5: DevIo_SimpleWrite local_pybinding: 7b226572726f72223a302c22726573756c74223a6e756c6c2c2261776169744964223a39323935343637387d
2023.02.05 09:19:19.426 5: processMessage: {"awaitId": 12871118, "NAME": "TUYA_SP07", "msgtype": "command", "command": "readingsEndUpdate($defs{'TUYA_SP07'},1);;"}
2023.02.05 09:19:19.426 4: BindingsIo (local_pybinding): <<< WS: {"error":0,"result":null,"awaitId":12871118}
2023.02.05 09:19:19.426 5: DevIo_SimpleWrite local_pybinding: 7b226572726f72223a302c22726573756c74223a6e756c6c2c2261776169744964223a31323837313131387d
2023.02.05 09:19:19.428 5: processMessage: {"awaitId": 69476713, "NAME": "TUYA_SP13", "msgtype": "command", "command": "readingsBeginUpdate($defs{'TUYA_SP13'});;"}
2023.02.05 09:19:19.428 4: BindingsIo (local_pybinding): <<< WS: {"error":0,"awaitId":69476713,"result":"2023-02-05 09:19:19"}
2023.02.05 09:19:19.428 5: DevIo_SimpleWrite local_pybinding: 7b226572726f72223a302c2261776169744964223a36393437363731332c22726573756c74223a22323032332d30322d30352030393a31393a3139227d
2023.02.05 09:19:19.430 5: BindingsIo (local_pybinding): QUEUE: finished handling - 0
2023.02.05 09:19:19.432 5: End notify loop for TUYA_SP01
2023.02.05 09:19:19.432 4: BindingsIo (local_pybinding): <<< WS: {"awaitId":78651841,"result":null,"error":0}
2023.02.05 09:19:19.433 5: DevIo_SimpleWrite local_pybinding: 7b2261776169744964223a37383635313834312c22726573756c74223a6e756c6c2c226572726f72223a307d
2023.02.05 09:19:19.434 5: BindingsIo (local_pybinding): QUEUE: finished handling - 0
2023.02.05 09:19:19.437 4: BindingsIo (local_pybinding): start fhempyFunction: TUYA_JL15 => Set (75457611)
2023.02.05 09:19:19.437 4: BindingsIo (local_pybinding): <<< WS: {"argsh":{},"msgtype":"function","function":"Set","PYTHONTYPE":"tuya","NAME":"TUYA_JL15","args":["TUYA_JL15","?"],"FHEMPYTYPE":"tuya","id":75457611,"defargsh":{},"defargs":["TUYA_JL15","fhempy","tuya","37mnhia3pojleqfh","10438000d8f15ba4ccd3","192.168.9.44","8ef2d52a326d2259","3.3","ea8453wdazquzfl08l0e","8a4b27dd759d4c6a9456aa8155d2a0ea"]}
2023.02.05 09:19:19.437 5: DevIo_SimpleWrite local_pybinding: 7b226172677368223a7b7d2c226d736774797065223a2266756e6374696f6e222c2266756e6374696f6e223a22536574222c22505954484f4e54595045223a2274757961222c224e414d45223a22545559415f4a4c3135222c2261726773223a5b22545559415f4a4c3135222c223f225d2c224648454d505954595045223a2274757961222c226964223a37353435373631312c226465666172677368223a7b7d2c2264656661726773223a5b22545559415f4a4c3135222c226668656d7079222c2274757961222c2233376d6e68696133706f6a6c65716668222c223130343338303030643866313562613463636433222c223139322e3136382e392e3434222c2238656632643532613332366432323539222c22332e33222c226561383435337764617a71757a666c30386c3065222c223861346232376464373539643463366139343536616138313535643261306561225d7d
2023.02.05 09:19:19.439 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2023.02.05 09:19:19.449 5: BindingsIo (local_pybinding): DevIo_SimpleRead WithTimeout
2023.02.05 09:19:19.449 5: BindingsIo (local_pybinding): QUEUE: start handling - 0
2023.02.05 09:19:19.449 5: BindingsIo (local_pybinding): QUEUE: finished handling - 0
2023.02.05 09:19:19.449 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2023.02.05 09:19:19.459 5: BindingsIo (local_pybinding): DevIo_SimpleRead WithTimeout
2023.02.05 09:19:19.459 5: BindingsIo (local_pybinding): QUEUE: start handling - 0
2023.02.05 09:19:19.460 5: BindingsIo (local_pybinding): QUEUE: finished handling - 0
2023.02.05 09:19:19.460 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2023.02.05 09:19:19.470 5: BindingsIo (local_pybinding): DevIo_SimpleRead WithTimeout
2023.02.05 09:19:19.470 5: BindingsIo (local_pybinding): QUEUE: start handling - 0
2023.02.05 09:19:19.470 5: BindingsIo (local_pybinding): QUEUE: finished handling - 0
2023.02.05 09:19:19.470 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2023.02.05 09:19:19.480 5: BindingsIo (local_pybinding): DevIo_SimpleRead WithTimeout
2023.02.05 09:19:19.480 5: BindingsIo (local_pybinding): QUEUE: start handling - 0
2023.02.05 09:19:19.480 5: BindingsIo (local_pybinding): QUEUE: finished handling - 0
2023.02.05 09:19:19.480 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2023.02.05 09:19:19.490 5: BindingsIo (local_pybinding): DevIo_SimpleRead WithTimeout
2023.02.05 09:19:19.491 5: BindingsIo (local_pybinding): QUEUE: start handling - 0
2023.02.05 09:19:19.491 5: BindingsIo (local_pybinding): QUEUE: finished handling - 0
2023.02.05 09:19:19.491 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2023.02.05 09:19:19.501 5: BindingsIo (local_pybinding): DevIo_SimpleRead WithTimeout
2023.02.05 09:19:19.501 5: BindingsIo (local_pybinding): QUEUE: start handling - 0
2023.02.05 09:19:19.501 5: BindingsIo (local_pybinding): QUEUE: finished handling - 0
2023.02.05 09:19:19.501 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2023.02.05 09:19:19.511 5: BindingsIo (local_pybinding): DevIo_SimpleRead WithTimeout
2023.02.05 09:19:19.511 5: BindingsIo (local_pybinding): QUEUE: start handling - 0
2023.02.05 09:19:19.511 5: BindingsIo (local_pybinding): QUEUE: finished handling - 0
2023.02.05 09:19:19.512 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2023.02.05 09:19:19.514 5: BindingsIo (local_pybinding): DevIo_SimpleRead WithTimeout
2023.02.05 09:19:19.514 4: BindingsIo (local_pybinding): >>> WS: {"awaitId": 85297474, "NAME": "TUYA_JL24", "msgtype": "command", "command": "readingsBeginUpdate($defs{'TUYA_JL24'});;"}
2023.02.05 09:19:19.514 5: BindingsIo (local_pybinding): QUEUE: start handling - 1
2023.02.05 09:19:19.514 5: processMessage: {"awaitId": 85297474, "NAME": "TUYA_JL24", "msgtype": "command", "command": "readingsBeginUpdate($defs{'TUYA_JL24'});;"}
2023.02.05 09:19:19.515 5: BindingsIo (local_pybinding): QUEUE: finished handling - 1
2023.02.05 09:19:19.515 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2023.02.05 09:19:19.516 5: BindingsIo (local_pybinding): DevIo_SimpleRead WithTimeout
2023.02.05 09:19:19.516 4: BindingsIo (local_pybinding): >>> WS: {"awaitId": 14121363, "NAME": "TUYA_JL26", "msgtype": "command", "command": "readingsBeginUpdate($defs{'TUYA_JL26'});;"}
2023.02.05 09:19:19.517 5: BindingsIo (local_pybinding): QUEUE: start handling - 2
2023.02.05 09:19:19.517 5: processMessage: {"awaitId": 85297474, "NAME": "TUYA_JL24", "msgtype": "command", "command": "readingsBeginUpdate($defs{'TUYA_JL24'});;"}
2023.02.05 09:19:19.517 5: processMessage: {"awaitId": 14121363, "NAME": "TUYA_JL26", "msgtype": "command", "command": "readingsBeginUpdate($defs{'TUYA_JL26'});;"}
2023.02.05 09:19:19.517 5: BindingsIo (local_pybinding): QUEUE: finished handling - 2
2023.02.05 09:19:19.517 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2023.02.05 09:19:19.518 5: BindingsIo (local_pybinding): DevIo_SimpleRead WithTimeout
2023.02.05 09:19:19.518 4: BindingsIo (local_pybinding): >>> WS: {"awaitId": 64709140, "NAME": "TUYA_SP09", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP09'},'dp_22','729');;"}
2023.02.05 09:19:19.518 5: BindingsIo (local_pybinding): QUEUE: start handling - 3
2023.02.05 09:19:19.518 5: processMessage: {"awaitId": 85297474, "NAME": "TUYA_JL24", "msgtype": "command", "command": "readingsBeginUpdate($defs{'TUYA_JL24'});;"}
2023.02.05 09:19:19.518 5: processMessage: {"awaitId": 14121363, "NAME": "TUYA_JL26", "msgtype": "command", "command": "readingsBeginUpdate($defs{'TUYA_JL26'});;"}
2023.02.05 09:19:19.519 5: processMessage: {"awaitId": 64709140, "NAME": "TUYA_SP09", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP09'},'dp_22','729');;"}
2023.02.05 09:19:19.519 5: BindingsIo (local_pybinding): QUEUE: finished handling - 3
2023.02.05 09:19:19.519 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2023.02.05 09:19:19.519 5: BindingsIo (local_pybinding): DevIo_SimpleRead WithTimeout
2023.02.05 09:19:19.519 4: BindingsIo (local_pybinding): >>> WS: {"awaitId": 12748403, "NAME": "TUYA_SP11", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP11'},'dp_22','715');;"}
2023.02.05 09:19:19.520 5: BindingsIo (local_pybinding): QUEUE: start handling - 4
2023.02.05 09:19:19.520 5: processMessage: {"awaitId": 85297474, "NAME": "TUYA_JL24", "msgtype": "command", "command": "readingsBeginUpdate($defs{'TUYA_JL24'});;"}
2023.02.05 09:19:19.520 5: processMessage: {"awaitId": 14121363, "NAME": "TUYA_JL26", "msgtype": "command", "command": "readingsBeginUpdate($defs{'TUYA_JL26'});;"}
2023.02.05 09:19:19.520 5: processMessage: {"awaitId": 64709140, "NAME": "TUYA_SP09", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP09'},'dp_22','729');;"}
2023.02.05 09:19:19.520 5: processMessage: {"awaitId": 12748403, "NAME": "TUYA_SP11", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP11'},'dp_22','715');;"}
2023.02.05 09:19:19.521 5: BindingsIo (local_pybinding): QUEUE: finished handling - 4
2023.02.05 09:19:19.521 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2023.02.05 09:19:19.521 5: BindingsIo (local_pybinding): DevIo_SimpleRead WithTimeout
2023.02.05 09:19:19.521 4: BindingsIo (local_pybinding): >>> WS: {"awaitId": 88310421, "NAME": "TUYA_SP08", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP08'},'dp_22','724');;"}
2023.02.05 09:19:19.521 4: BindingsIo (local_pybinding): >>> WS: {"awaitId": 52988890, "NAME": "TUYA_SP12", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP12'},'dp_22','721');;"}
2023.02.05 09:19:19.522 5: BindingsIo (local_pybinding): QUEUE: start handling - 6
2023.02.05 09:19:19.522 5: processMessage: {"awaitId": 85297474, "NAME": "TUYA_JL24", "msgtype": "command", "command": "readingsBeginUpdate($defs{'TUYA_JL24'});;"}
2023.02.05 09:19:19.522 5: processMessage: {"awaitId": 14121363, "NAME": "TUYA_JL26", "msgtype": "command", "command": "readingsBeginUpdate($defs{'TUYA_JL26'});;"}
2023.02.05 09:19:19.522 5: processMessage: {"awaitId": 64709140, "NAME": "TUYA_SP09", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP09'},'dp_22','729');;"}
2023.02.05 09:19:19.522 5: processMessage: {"awaitId": 12748403, "NAME": "TUYA_SP11", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP11'},'dp_22','715');;"}
2023.02.05 09:19:19.522 5: processMessage: {"awaitId": 88310421, "NAME": "TUYA_SP08", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP08'},'dp_22','724');;"}
2023.02.05 09:19:19.522 5: processMessage: {"awaitId": 52988890, "NAME": "TUYA_SP12", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP12'},'dp_22','721');;"}
2023.02.05 09:19:19.523 5: BindingsIo (local_pybinding): QUEUE: finished handling - 6
2023.02.05 09:19:19.523 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2023.02.05 09:19:19.523 5: BindingsIo (local_pybinding): DevIo_SimpleRead WithTimeout
2023.02.05 09:19:19.524 4: BindingsIo (local_pybinding): >>> WS: {"awaitId": 51619211, "NAME": "TUYA_JL33", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_JL33'},'cur_voltage','229.3');;"}
2023.02.05 09:19:19.524 4: BindingsIo (local_pybinding): >>> WS: {"awaitId": 63472181, "NAME": "TUYA_JL30", "msgtype": "command", "command": "readingsEndUpdate($defs{'TUYA_JL30'},1);;"}
2023.02.05 09:19:19.524 5: BindingsIo (local_pybinding): QUEUE: start handling - 8
2023.02.05 09:19:19.524 5: processMessage: {"awaitId": 85297474, "NAME": "TUYA_JL24", "msgtype": "command", "command": "readingsBeginUpdate($defs{'TUYA_JL24'});;"}
2023.02.05 09:19:19.525 5: processMessage: {"awaitId": 14121363, "NAME": "TUYA_JL26", "msgtype": "command", "command": "readingsBeginUpdate($defs{'TUYA_JL26'});;"}
2023.02.05 09:19:19.525 5: processMessage: {"awaitId": 64709140, "NAME": "TUYA_SP09", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP09'},'dp_22','729');;"}
2023.02.05 09:19:19.525 5: processMessage: {"awaitId": 12748403, "NAME": "TUYA_SP11", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP11'},'dp_22','715');;"}
2023.02.05 09:19:19.525 5: processMessage: {"awaitId": 88310421, "NAME": "TUYA_SP08", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP08'},'dp_22','724');;"}
2023.02.05 09:19:19.525 5: processMessage: {"awaitId": 52988890, "NAME": "TUYA_SP12", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP12'},'dp_22','721');;"}
2023.02.05 09:19:19.525 5: processMessage: {"awaitId": 51619211, "NAME": "TUYA_JL33", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_JL33'},'cur_voltage','229.3');;"}
2023.02.05 09:19:19.525 5: processMessage: {"awaitId": 63472181, "NAME": "TUYA_JL30", "msgtype": "command", "command": "readingsEndUpdate($defs{'TUYA_JL30'},1);;"}
2023.02.05 09:19:19.526 5: BindingsIo (local_pybinding): QUEUE: finished handling - 8
2023.02.05 09:19:19.526 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2023.02.05 09:19:19.526 5: BindingsIo (local_pybinding): DevIo_SimpleRead WithTimeout
2023.02.05 09:19:19.526 4: BindingsIo (local_pybinding): >>> WS: {"argsh": {}, "msgtype": "function", "function": "Set", "PYTHONTYPE": "tuya", "NAME": "TUYA_JL15", "args": ["TUYA_JL15", "?"], "FHEMPYTYPE": "tuya", "id": 75457611, "defargsh": {}, "defargs": ["TUYA_JL15", "fhempy", "tuya", "37mnhia3pojleqfh", "10438000d8f15ba4ccd3", "192.168.9.44", "8ef2d52a326d2259", "3.3", "ea8453wdazquzfl08l0e", "8a4b27dd759d4c6a9456aa8155d2a0ea"], "finished": 1, "returnval": "Unknown argument ?, choose one of on:noArg off:noArg countdown_1:slider,0.0,1.0,86400.0"}
2023.02.05 09:19:19.527 5: BindingsIo (local_pybinding): QUEUE: start handling - 9
2023.02.05 09:19:19.527 5: processMessage: {"awaitId": 85297474, "NAME": "TUYA_JL24", "msgtype": "command", "command": "readingsBeginUpdate($defs{'TUYA_JL24'});;"}
2023.02.05 09:19:19.527 5: processMessage: {"awaitId": 14121363, "NAME": "TUYA_JL26", "msgtype": "command", "command": "readingsBeginUpdate($defs{'TUYA_JL26'});;"}
2023.02.05 09:19:19.527 5: processMessage: {"awaitId": 64709140, "NAME": "TUYA_SP09", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP09'},'dp_22','729');;"}
2023.02.05 09:19:19.527 5: processMessage: {"awaitId": 12748403, "NAME": "TUYA_SP11", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP11'},'dp_22','715');;"}
2023.02.05 09:19:19.527 5: processMessage: {"awaitId": 88310421, "NAME": "TUYA_SP08", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP08'},'dp_22','724');;"}
2023.02.05 09:19:19.527 5: processMessage: {"awaitId": 52988890, "NAME": "TUYA_SP12", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP12'},'dp_22','721');;"}
2023.02.05 09:19:19.528 5: processMessage: {"awaitId": 51619211, "NAME": "TUYA_JL33", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_JL33'},'cur_voltage','229.3');;"}
2023.02.05 09:19:19.528 5: processMessage: {"awaitId": 63472181, "NAME": "TUYA_JL30", "msgtype": "command", "command": "readingsEndUpdate($defs{'TUYA_JL30'},1);;"}
2023.02.05 09:19:19.528 5: processMessage: {"argsh": {}, "msgtype": "function", "function": "Set", "PYTHONTYPE": "tuya", "NAME": "TUYA_JL15", "args": ["TUYA_JL15", "?"], "FHEMPYTYPE": "tuya", "id": 75457611, "defargsh": {}, "defargs": ["TUYA_JL15", "fhempy", "tuya", "37mnhia3pojleqfh", "10438000d8f15ba4ccd3", "192.168.9.44", "8ef2d52a326d2259", "3.3", "ea8453wdazquzfl08l0e", "8a4b27dd759d4c6a9456aa8155d2a0ea"], "finished": 1, "returnval": "Unknown argument ?, choose one of on:noArg off:noArg countdown_1:slider,0.0,1.0,86400.0"}
2023.02.05 09:19:19.528 5: BindingsIo (local_pybinding): QUEUE: finished handling - 8
2023.02.05 09:19:19.528 4: BindingsIo (local_pybinding): end fhempyFunction: TUYA_JL15 => Set (75457611) - result: Unknown argument ?, choose one of on:noArg off:noArg countdown_1:slider,0.0,1.0,86400.0
2023.02.05 09:19:19.528 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2023.02.05 09:19:19.529 5: BindingsIo (local_pybinding): DevIo_SimpleRead NoTimeout
2023.02.05 09:19:19.529 5: BindingsIo (local_pybinding): QUEUE: start handling - 8
2023.02.05 09:19:19.529 5: processMessage: {"awaitId": 85297474, "NAME": "TUYA_JL24", "msgtype": "command", "command": "readingsBeginUpdate($defs{'TUYA_JL24'});;"}
2023.02.05 09:19:19.529 4: BindingsIo (local_pybinding): <<< WS: {"result":"2023-02-05 09:19:19","awaitId":85297474,"error":0}
2023.02.05 09:19:19.529 5: DevIo_SimpleWrite local_pybinding: 7b22726573756c74223a22323032332d30322d30352030393a31393a3139222c2261776169744964223a38353239373437342c226572726f72223a307d
2023.02.05 09:19:19.531 5: processMessage: {"awaitId": 14121363, "NAME": "TUYA_JL26", "msgtype": "command", "command": "readingsBeginUpdate($defs{'TUYA_JL26'});;"}
2023.02.05 09:19:19.531 4: BindingsIo (local_pybinding): <<< WS: {"error":0,"result":"2023-02-05 09:19:19","awaitId":14121363}
2023.02.05 09:19:19.531 5: DevIo_SimpleWrite local_pybinding: 7b226572726f72223a302c22726573756c74223a22323032332d30322d30352030393a31393a3139222c2261776169744964223a31343132313336337d
2023.02.05 09:19:19.533 5: processMessage: {"awaitId": 64709140, "NAME": "TUYA_SP09", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP09'},'dp_22','729');;"}
2023.02.05 09:19:19.534 4: BindingsIo (local_pybinding): <<< WS: {"result":null,"awaitId":64709140,"error":0}
2023.02.05 09:19:19.534 5: DevIo_SimpleWrite local_pybinding: 7b22726573756c74223a6e756c6c2c2261776169744964223a36343730393134302c226572726f72223a307d
2023.02.05 09:19:19.535 5: processMessage: {"awaitId": 12748403, "NAME": "TUYA_SP11", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP11'},'dp_22','715');;"}
2023.02.05 09:19:19.536 4: BindingsIo (local_pybinding): <<< WS: {"result":null,"awaitId":12748403,"error":0}
2023.02.05 09:19:19.536 5: DevIo_SimpleWrite local_pybinding: 7b22726573756c74223a6e756c6c2c2261776169744964223a31323734383430332c226572726f72223a307d
2023.02.05 09:19:19.537 5: processMessage: {"awaitId": 88310421, "NAME": "TUYA_SP08", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP08'},'dp_22','724');;"}
2023.02.05 09:19:19.537 4: BindingsIo (local_pybinding): <<< WS: {"error":0,"result":null,"awaitId":88310421}
2023.02.05 09:19:19.538 5: DevIo_SimpleWrite local_pybinding: 7b226572726f72223a302c22726573756c74223a6e756c6c2c2261776169744964223a38383331303432317d
2023.02.05 09:19:19.539 5: processMessage: {"awaitId": 52988890, "NAME": "TUYA_SP12", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP12'},'dp_22','721');;"}
2023.02.05 09:19:19.539 4: BindingsIo (local_pybinding): <<< WS: {"awaitId":52988890,"result":null,"error":0}
2023.02.05 09:19:19.540 5: DevIo_SimpleWrite local_pybinding: 7b2261776169744964223a35323938383839302c22726573756c74223a6e756c6c2c226572726f72223a307d
2023.02.05 09:19:19.541 5: processMessage: {"awaitId": 51619211, "NAME": "TUYA_JL33", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_JL33'},'cur_voltage','229.3');;"}
2023.02.05 09:19:19.541 4: BindingsIo (local_pybinding): <<< WS: {"error":0,"awaitId":51619211,"result":null}
2023.02.05 09:19:19.541 5: DevIo_SimpleWrite local_pybinding: 7b226572726f72223a302c2261776169744964223a35313631393231312c22726573756c74223a6e756c6c7d
2023.02.05 09:19:19.543 5: processMessage: {"awaitId": 63472181, "NAME": "TUYA_JL30", "msgtype": "command", "command": "readingsEndUpdate($defs{'TUYA_JL30'},1);;"}
2023.02.05 09:19:19.550 4: DbLog dblog_THB - check Device: TUYA_JL30 , Event: cur_current: 1060.0
2023.02.05 09:19:19.610 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL30'},1);;
2023.02.05 09:19:19.610 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1310.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL30'},1);;
2023.02.05 09:19:19.610 5: DbLog dblog_THB - parsed Event: TUYA_JL30 , Event: cur_current: 1060.0
2023.02.05 09:19:19.610 5: DbLog dblog_THB - DbLogExclude of "TUYA_JL30": .*
2023.02.05 09:19:19.610 4: DbLog dblog_THB - check Device: TUYA_JL30 , Event: cur_power: 2467.0
2023.02.05 09:19:19.659 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL30'},1);;
2023.02.05 09:19:19.659 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1310.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL30'},1);;
2023.02.05 09:19:19.660 5: DbLog dblog_THB - parsed Event: TUYA_JL30 , Event: cur_power: 2467.0
2023.02.05 09:19:19.660 5: DbLog dblog_THB - DbLogExclude of "TUYA_JL30": .*
2023.02.05 09:19:19.660 4: DbLog dblog_THB - check Device: TUYA_JL30 , Event: cur_voltage: 232.7
2023.02.05 09:19:19.708 1: BindingsIo (local_pybinding): devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL30'},1);;
2023.02.05 09:19:19.708 1: BindingsIo (local_pybinding): ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1310.
=> COMMAND: readingsEndUpdate($defs{'TUYA_JL30'},1);;
2023.02.05 09:19:19.708 5: DbLog dblog_THB - parsed Event: TUYA_JL30 , Event: cur_voltage: 232.7
2023.02.05 09:19:19.708 5: DbLog dblog_THB - DbLogExclude of "TUYA_JL30": .*
2023.02.05 09:19:19.709 5: rgBatterieStatus: not on any display, ignoring notify
2023.02.05 09:19:19.709 5: rgTUYA: not on any display, ignoring notify
2023.02.05 09:19:19.709 4: BindingsIo (local_pybinding): start fhempyFunction: TUYA_JL30 => Set (14990372)
2023.02.05 09:19:19.709 4: BindingsIo (local_pybinding): <<< WS: {"defargs":["TUYA_JL30","fhempy","tuya","37mnhia3pojleqfh","20538630c44f33f7b2b6","192.168.9.69","b2b021b05d25903e","3.3","ea8453wdazquzfl08l0e","8a4b27dd759d4c6a9456aa8155d2a0ea"],"defargsh":{},"id":14990372,"FHEMPYTYPE":"tuya","args":["TUYA_JL30","?"],"NAME":"TUYA_JL30","PYTHONTYPE":"tuya","function":"Set","msgtype":"function","argsh":{}}
2023.02.05 09:19:19.709 5: DevIo_SimpleWrite local_pybinding: 7b2264656661726773223a5b22545559415f4a4c3330222c226668656d7079222c2274757961222c2233376d6e68696133706f6a6c65716668222c223230353338363330633434663333663762326236222c223139322e3136382e392e3639222c2262326230323162303564323539303365222c22332e33222c226561383435337764617a71757a666c30386c3065222c223861346232376464373539643463366139343536616138313535643261306561225d2c226465666172677368223a7b7d2c226964223a31343939303337322c224648454d505954595045223a2274757961222c2261726773223a5b22545559415f4a4c3330222c223f225d2c224e414d45223a22545559415f4a4c3330222c22505954484f4e54595045223a2274757961222c2266756e6374696f6e223a22536574222c226d736774797065223a2266756e6374696f6e222c226172677368223a7b7d7d
2023.02.05 09:19:19.711 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2023.02.05 09:19:19.711 5: BindingsIo (local_pybinding): DevIo_SimpleRead WithTimeout
2023.02.05 09:19:19.711 4: BindingsIo (local_pybinding): >>> WS: {"awaitId": 64561166, "NAME": "TUYA_JL24", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_JL24'},'cur_voltage','229.3');;"}
2023.02.05 09:19:19.711 4: BindingsIo (local_pybinding): >>> WS: {"awaitId": 41685307, "NAME": "TUYA_JL26", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_JL26'},'cur_voltage','228.0');;"}
2023.02.05 09:19:19.711 4: BindingsIo (local_pybinding): >>> WS: {"awaitId": 63848462, "NAME": "TUYA_SP09", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP09'},'dp_23','31250');;"}
2023.02.05 09:19:19.712 4: BindingsIo (local_pybinding): >>> WS: {"awaitId": 81452013, "NAME": "TUYA_SP11", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP11'},'dp_23','30264');;"}
2023.02.05 09:19:19.712 4: BindingsIo (local_pybinding): >>> WS: {"awaitId": 62496518, "NAME": "TUYA_SP08", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP08'},'dp_23','31060');;"}
2023.02.05 09:19:19.712 4: BindingsIo (local_pybinding): >>> WS: {"awaitId": 74312766, "NAME": "TUYA_SP12", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP12'},'dp_23','30787');;"}
2023.02.05 09:19:19.712 4: BindingsIo (local_pybinding): >>> WS: {"awaitId": 14947482, "NAME": "TUYA_JL33", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_JL33'},'dp_07','0');;"}
2023.02.05 09:19:19.712 4: BindingsIo (local_pybinding): >>> WS: {"awaitId": 24107605, "NAME": "TUYA_SP15", "msgtype": "command", "command": "readingsBeginUpdate($defs{'TUYA_SP15'});;"}
2023.02.05 09:19:19.712 4: BindingsIo (local_pybinding): >>> WS: {"awaitId": 84529117, "NAME": "TUYA_SP13", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP13'},'state','on');;"}
2023.02.05 09:19:19.712 4: BindingsIo (local_pybinding): >>> WS: {"awaitId": 16464170, "NAME": "TUYA_JL04", "msgtype": "command", "command": "readingsBeginUpdate($defs{'TUYA_JL04'});;"}
2023.02.05 09:19:19.712 4: BindingsIo (local_pybinding): >>> WS: {"defargs": ["TUYA_JL30", "fhempy", "tuya", "37mnhia3pojleqfh", "20538630c44f33f7b2b6", "192.168.9.69", "b2b021b05d25903e", "3.3", "ea8453wdazquzfl08l0e", "8a4b27dd759d4c6a9456aa8155d2a0ea"], "defargsh": {}, "id": 14990372, "FHEMPYTYPE": "tuya", "args": ["TUYA_JL30", "?"], "NAME": "TUYA_JL30", "PYTHONTYPE": "tuya", "function": "Set", "msgtype": "function", "argsh": {}, "finished": 1, "returnval": "Unknown argument ?, choose one of on:noArg off:noArg countdown_1:slider,0.0,1.0,86400.0"}
2023.02.05 09:19:19.713 5: BindingsIo (local_pybinding): QUEUE: start handling - 11
2023.02.05 09:19:19.713 5: processMessage: {"awaitId": 64561166, "NAME": "TUYA_JL24", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_JL24'},'cur_voltage','229.3');;"}
2023.02.05 09:19:19.713 5: processMessage: {"awaitId": 41685307, "NAME": "TUYA_JL26", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_JL26'},'cur_voltage','228.0');;"}
2023.02.05 09:19:19.713 5: processMessage: {"awaitId": 63848462, "NAME": "TUYA_SP09", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP09'},'dp_23','31250');;"}
2023.02.05 09:19:19.713 5: processMessage: {"awaitId": 81452013, "NAME": "TUYA_SP11", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP11'},'dp_23','30264');;"}
2023.02.05 09:19:19.713 5: processMessage: {"awaitId": 62496518, "NAME": "TUYA_SP08", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP08'},'dp_23','31060');;"}
2023.02.05 09:19:19.713 5: processMessage: {"awaitId": 74312766, "NAME": "TUYA_SP12", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP12'},'dp_23','30787');;"}
2023.02.05 09:19:19.713 5: processMessage: {"awaitId": 14947482, "NAME": "TUYA_JL33", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_JL33'},'dp_07','0');;"}
2023.02.05 09:19:19.713 5: processMessage: {"awaitId": 24107605, "NAME": "TUYA_SP15", "msgtype": "command", "command": "readingsBeginUpdate($defs{'TUYA_SP15'});;"}
2023.02.05 09:19:19.713 5: processMessage: {"awaitId": 84529117, "NAME": "TUYA_SP13", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP13'},'state','on');;"}
2023.02.05 09:19:19.713 5: processMessage: {"awaitId": 16464170, "NAME": "TUYA_JL04", "msgtype": "command", "command": "readingsBeginUpdate($defs{'TUYA_JL04'});;"}
2023.02.05 09:19:19.713 5: processMessage: {"defargs": ["TUYA_JL30", "fhempy", "tuya", "37mnhia3pojleqfh", "20538630c44f33f7b2b6", "192.168.9.69", "b2b021b05d25903e", "3.3", "ea8453wdazquzfl08l0e", "8a4b27dd759d4c6a9456aa8155d2a0ea"], "defargsh": {}, "id": 14990372, "FHEMPYTYPE": "tuya", "args": ["TUYA_JL30", "?"], "NAME": "TUYA_JL30", "PYTHONTYPE": "tuya", "function": "Set", "msgtype": "function", "argsh": {}, "finished": 1, "returnval": "Unknown argument ?, choose one of on:noArg off:noArg countdown_1:slider,0.0,1.0,86400.0"}
2023.02.05 09:19:19.714 5: BindingsIo (local_pybinding): QUEUE: finished handling - 10
2023.02.05 09:19:19.714 4: BindingsIo (local_pybinding): end fhempyFunction: TUYA_JL30 => Set (14990372) - result: Unknown argument ?, choose one of on:noArg off:noArg countdown_1:slider,0.0,1.0,86400.0
2023.02.05 09:19:19.714 5: BindingsIo (local_pybinding): DevIo_SimpleRead
2023.02.05 09:19:19.714 5: BindingsIo (local_pybinding): DevIo_SimpleRead NoTimeout
2023.02.05 09:19:19.714 5: BindingsIo (local_pybinding): QUEUE: start handling - 10
2023.02.05 09:19:19.714 5: processMessage: {"awaitId": 64561166, "NAME": "TUYA_JL24", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_JL24'},'cur_voltage','229.3');;"}
2023.02.05 09:19:19.714 4: BindingsIo (local_pybinding): <<< WS: {"result":"cur_voltage: 229.3","awaitId":64561166,"error":0}
2023.02.05 09:19:19.714 5: DevIo_SimpleWrite local_pybinding: 7b22726573756c74223a226375725f766f6c746167653a203232392e33222c2261776169744964223a36343536313136362c226572726f72223a307d
2023.02.05 09:19:19.716 5: processMessage: {"awaitId": 41685307, "NAME": "TUYA_JL26", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_JL26'},'cur_voltage','228.0');;"}
2023.02.05 09:19:19.716 4: BindingsIo (local_pybinding): <<< WS: {"result":"cur_voltage: 228.0","awaitId":41685307,"error":0}
2023.02.05 09:19:19.716 5: DevIo_SimpleWrite local_pybinding: 7b22726573756c74223a226375725f766f6c746167653a203232382e30222c2261776169744964223a34313638353330372c226572726f72223a307d
2023.02.05 09:19:19.718 5: processMessage: {"awaitId": 63848462, "NAME": "TUYA_SP09", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP09'},'dp_23','31250');;"}
2023.02.05 09:19:19.718 4: BindingsIo (local_pybinding): <<< WS: {"error":0,"result":null,"awaitId":63848462}
2023.02.05 09:19:19.718 5: DevIo_SimpleWrite local_pybinding: 7b226572726f72223a302c22726573756c74223a6e756c6c2c2261776169744964223a36333834383436327d
2023.02.05 09:19:19.719 5: processMessage: {"awaitId": 81452013, "NAME": "TUYA_SP11", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP11'},'dp_23','30264');;"}
2023.02.05 09:19:19.720 4: BindingsIo (local_pybinding): <<< WS: {"error":0,"awaitId":81452013,"result":null}
2023.02.05 09:19:19.720 5: DevIo_SimpleWrite local_pybinding: 7b226572726f72223a302c2261776169744964223a38313435323031332c22726573756c74223a6e756c6c7d
2023.02.05 09:19:19.721 5: processMessage: {"awaitId": 62496518, "NAME": "TUYA_SP08", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP08'},'dp_23','31060');;"}
2023.02.05 09:19:19.721 4: BindingsIo (local_pybinding): <<< WS: {"result":null,"awaitId":62496518,"error":0}
2023.02.05 09:19:19.721 5: DevIo_SimpleWrite local_pybinding: 7b22726573756c74223a6e756c6c2c2261776169744964223a36323439363531382c226572726f72223a307d
2023.02.05 09:19:19.723 5: processMessage: {"awaitId": 74312766, "NAME": "TUYA_SP12", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP12'},'dp_23','30787');;"}
2023.02.05 09:19:19.723 4: BindingsIo (local_pybinding): <<< WS: {"error":0,"result":null,"awaitId":74312766}
2023.02.05 09:19:19.723 5: DevIo_SimpleWrite local_pybinding: 7b226572726f72223a302c22726573756c74223a6e756c6c2c2261776169744964223a37343331323736367d
2023.02.05 09:19:19.724 5: processMessage: {"awaitId": 14947482, "NAME": "TUYA_JL33", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_JL33'},'dp_07','0');;"}
2023.02.05 09:19:19.725 4: BindingsIo (local_pybinding): <<< WS: {"result":null,"awaitId":14947482,"error":0}
2023.02.05 09:19:19.725 5: DevIo_SimpleWrite local_pybinding: 7b22726573756c74223a6e756c6c2c2261776169744964223a31343934373438322c226572726f72223a307d
2023.02.05 09:19:19.726 5: processMessage: {"awaitId": 24107605, "NAME": "TUYA_SP15", "msgtype": "command", "command": "readingsBeginUpdate($defs{'TUYA_SP15'});;"}
2023.02.05 09:19:19.726 4: BindingsIo (local_pybinding): <<< WS: {"awaitId":24107605,"result":"2023-02-05 09:19:19","error":0}
2023.02.05 09:19:19.726 5: DevIo_SimpleWrite local_pybinding: 7b2261776169744964223a32343130373630352c22726573756c74223a22323032332d30322d30352030393a31393a3139222c226572726f72223a307d
2023.02.05 09:19:19.728 5: processMessage: {"awaitId": 84529117, "NAME": "TUYA_SP13", "msgtype": "command", "command": "readingsBulkUpdateIfChanged($defs{'TUYA_SP13'},'state','on');;"}
2023.02.05 09:19:19.728 4: BindingsIo (local_pybinding): <<< WS: {"awaitId":84529117,"result":null,"error":0}
2023.02.05 09:19:19.728 5: DevIo_SimpleWrite local_pybinding: 7b2261776169744964223a38343532393131372c22726573756c74223a6e756c6c2c226572726f72223a307d
2023.02.05 09:19:19.730 5: processMessage: {"awaitId": 16464170, "NAME": "TUYA_JL04", "msgtype": "command", "command": "readingsBeginUpdate($defs{'TUYA_JL04'});;"}
ich konnte bislang nicht nachvollziehen, warum fhempy neue devices fälschlich als doppelte anlegt, wenn sie nicht rechtzeitig antworten.
ich habe mal testweise autocreate für TYPE = fhempy ausgeschlossen.
in Apptime:
active-timers: 84; max-active timers: 162; max-timer-load: 82 min-tmrHandlingTm: 0.0ms; max-tmrHandlingTm: 11701.7ms; totAvgDly: 56.1ms
name function max count total average maxDly avgDly TS Max call param Max call
Buderus km200_Attr 15015 10 15016.31 1501.63 0.00 0.00 05.02. 10:50:46 set; Buderus; DoNotPoll; /dhwCircuits/dhw1/switchPrograms/
WEB_192.168.9.103_30328 FW_Read 8184 8 8189.53 1023.69 0.00 0.00 05.02. 10:55:50 HASH(WEB_192.168.9.103_30328)
JLLaCR JeeLink_Read 1206 878 18444.88 21.01 0.00 0.00 05.02. 10:50:52 HASH(JLLaCR)
JLLaCR JeeLink_Define 1025 1 1025.74 1025.74 0.00 0.00 05.02. 10:50:31 HASH(JLLaCR); JLLaCR JeeLink /dev/ttyUSB0@57600
SamsungSmartThingsConnector SST_Notify 567 659 577.33 0.88 0.00 0.00 05.02. 10:50:50 HASH(SamsungSmartThingsConnector); HASH(global)
dblog_THB DbLog_Log 456 660 44661.13 67.67 0.00 0.00 05.02. 10:51:17 HASH(dblog_THB); HASH(WU_IPLIEZ_1)
eventTypes eventTypes_Define 413 1 413.81 413.81 0.00 0.00 05.02. 10:50:46 HASH(eventTypes); eventTypes eventTypes ./log/eventTypes.txt
hueBridge1 HUEBridge_Notify 402 2 402.93 201.46 0.00 0.00 05.02. 10:50:50 HASH(hueBridge1); HASH(global)
tmr-HUEBridge_GetUpdate HASH(0x6b0efb8) 291 5 1366.06 273.21 415.92 84.02 05.02. 10:51:50 HASH(hueBridge1)
tmr-freezemon_ProcessTimer HASH(0x77a1220) 259 344 917.78 2.67 7612.83 42.08 05.02. 10:55:54 HASH(myFreezemon)
tmr-SYSSTAT_GetUpdate HASH(0x532c228) 215 3 570.14 190.05 195.42 65.91 05.02. 10:54:55 HASH(BBxM)
TelegramBotTHB TelegramBot_Define 168 1 168.23 168.23 0.00 0.00 05.02. 10:50:30 HASH(TelegramBotTHB); TelegramBotTHB TelegramBot
TUYA_SP01 fhempy_Set 159 2 160.53 80.27 0.00 0.00 05.02. 10:55:50 HASH(TUYA_SP01); ARRAY(0x80ded00); HASH(0x7c79a88)
WEB_192.168.9.103_30338 FW_Read 123 6 127.50 21.25 0.00 0.00 05.02. 10:56:22 HASH(WEB_192.168.9.103_30338)
tmr-CUL_MAX_SQH HASH(0x88688e8) 121 63 4867.08 77.26 4374.59 76.83 05.02. 10:56:05 HASH(MaxSystem)
CUL_0 CUL_Get 120 64 4885.57 76.34 0.00 0.00 05.02. 10:56:05 HASH(CUL_0); CUL_0; credit10ms
tmr-DbLog_execMemCacheAsync HASH(0x6ce6850) 118 11 935.24 85.02 365.20 35.54 05.02. 10:53:21 HASH(dblog_THB)
tmr-CUL_MAX_BroadcastTime HASH(0x88688e8) 117 1 117.07 117.07 33.81 33.81 05.02. 10:51:21 HASH(MaxSystem)
TUYA_JL30 fhempy_Set 65 3 123.92 41.31 0.00 0.00 05.02. 10:55:51 HASH(TUYA_JL30); ARRAY(0x88b4ac0); HASH(0x7fa4ee0)
TUYA_JL18 fhempy_Set 60 2 116.94 58.47 0.00 0.00 05.02. 10:55:45 HASH(TUYA_JL18); ARRAY(0x82cf680); HASH(0x833d010)
TUYA_JL22 fhempy_Set 60 4 172.04 43.01 0.00 0.00 05.02. 10:55:44 HASH(TUYA_JL22); ARRAY(0x7d5bc30); HASH(0x7c94df0)
TUYA_JL33 fhempy_Set 59 3 115.94 38.65 0.00 0.00 05.02. 10:55:49 HASH(TUYA_JL33); ARRAY(0x7f92518); HASH(0x8048418)
TUYA_JL02 fhempy_Set 59 4 172.52 43.13 0.00 0.00 05.02. 10:55:43 HASH(TUYA_JL02); ARRAY(0x7c9dbc0); HASH(0x8267b28)
TUYA_EMYLO4 fhempy_Set 59 4 169.81 42.45 0.00 0.00 05.02. 10:55:43 HASH(TUYA_EMYLO4); ARRAY(0x7cc9aa0); HASH(0x7050330)
TUYA_EMYLO3 fhempy_Set 59 4 170.66 42.67 0.00 0.00 05.02. 10:55:43 HASH(TUYA_EMYLO3); ARRAY(0x81cd380); HASH(0x718db98)
TUYAC_Sir01 fhempy_Set 59 3 59.46 19.82 0.00 0.00 05.02. 10:55:48 HASH(TUYAC_Sir01); ARRAY(0x7d9d4f8); HASH(0x8266ff8)
TUYA_JL31 fhempy_Set 58 3 115.10 38.37 0.00 0.00 05.02. 10:55:49 HASH(TUYA_JL31); ARRAY(0x8122cd8); HASH(0x7c37bf0)
TUYA_JL21 fhempy_Set 58 4 169.85 42.46 0.00 0.00 05.02. 10:55:44 HASH(TUYA_JL21); ARRAY(0x88f3238); HASH(0x7fdf7f8)
TUYAC_SensorSmoke01 fhempy_Set 58 4 171.75 42.94 0.00 0.00 05.02. 10:55:50 HASH(TUYAC_SensorSmoke01); ARRAY(0x88ef6f0); HASH(0x80ba9d0)
tuya_system fhempy_Set 58 3 114.86 38.29 0.00 0.00 05.02. 10:55:50 HASH(tuya_system); ARRAY(0x88fee00); HASH(0x81583f0)
TUYAC_Sir02 fhempy_Set 58 3 58.69 19.56 0.00 0.00 05.02. 10:55:48 HASH(TUYAC_Sir02); ARRAY(0x88df7d0); HASH(0x81d9408)
TUYA_JL32 fhempy_Set 57 3 114.15 38.05 0.00 0.00 05.02. 10:55:49 HASH(TUYA_JL32); ARRAY(0x82d8cd8); HASH(0x88ef9d8)
TUYA_JL23 fhempy_Set 57 2 113.76 56.88 0.00 0.00 05.02. 10:55:44 HASH(TUYA_JL23); ARRAY(0x81fdef0); HASH(0x588ef58)
TUYAC_SensorW03 fhempy_Set 57 3 58.04 19.35 0.00 0.00 05.02. 10:55:48 HASH(TUYAC_SensorW03); ARRAY(0x828aef8); HASH(0x88e07c8)
TUYA_Temp07 fhempy_Set 57 3 58.01 19.34 0.00 0.00 05.02. 10:55:48 HASH(TUYA_Temp07); ARRAY(0x7fc7200); HASH(0x8222e80)
TUYAC_Relais01 fhempy_Set 57 3 57.89 19.30 0.00 0.00 05.02. 10:55:46 HASH(TUYAC_Relais01); ARRAY(0x826bf58); HASH(0x78d3c60)
TUYAC_SensorT01 fhempy_Set 57 3 57.95 19.32 0.00 0.00 05.02. 10:55:47 HASH(TUYAC_SensorT01); ARRAY(0x7daa290); HASH(0x64768e8)
TUYA_Temp02 fhempy_Set 57 3 57.95 19.32 0.00 0.00 05.02. 10:55:48 HASH(TUYA_Temp02); ARRAY(0x8290140); HASH(0x8351168)
TUYAC_SensorW04 fhempy_Set 57 3 57.86 19.29 0.00 0.00 05.02. 10:55:48 HASH(TUYAC_SensorW04); ARRAY(0x8163ee0); HASH(0x8295400)
TUYA_PS3 fhempy_Set 57 3 113.66 37.89 0.00 0.00 05.02. 10:55:49 HASH(TUYA_PS3); ARRAY(0x78d49c8); HASH(0x7cb0580)
TUYA_Temp03 fhempy_Set 57 3 57.77 19.26 0.00 0.00 05.02. 10:55:48 HASH(TUYA_Temp03); ARRAY(0x88f44b8); HASH(0x80bf198)
ich habe keine doppelten Devices mehr
in tuya_local erzeuge ich doch auch durch eine "SET createdevices" Bentzeraktion neue und somit nur gewünschte devices ;
tuya_cloud könnte ja das doch auch so ermöglichen
sodele nach update auf fhempy 0.1.593
Phantom_devices aus den fhem.cfg:
define tuya_cloud_bf16f1788a2fd6edd6pr1d fhempy tuya_cloud TUYA bf16f1788a2fd6edd6pr1d
setuuid tuya_cloud_bf16f1788a2fd6edd6pr1d 63dfba2f-f33f-fd5f-8f45-4e400ef1f46ce1eb
attr tuya_cloud_bf16f1788a2fd6edd6pr1d DbLogExclude .*
attr tuya_cloud_bf16f1788a2fd6edd6pr1d alias Balkonstern BULB03
attr tuya_cloud_bf16f1788a2fd6edd6pr1d event-on-change-reading .*
attr tuya_cloud_bf16f1788a2fd6edd6pr1d group tuya_cloud
attr tuya_cloud_bf16f1788a2fd6edd6pr1d room fhempy
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>bereits Local vorhanden
define tuya_cloud_3367036770039f60ce2b fhempy tuya_cloud TUYA 3367036770039f60ce2b
setuuid tuya_cloud_3367036770039f60ce2b 63dfba55-f33f-fd5f-8d22-0c88c4ccfb4329b8
attr tuya_cloud_3367036770039f60ce2b DbLogExclude .*
attr tuya_cloud_3367036770039f60ce2b alias USB Lader2 Thomas
attr tuya_cloud_3367036770039f60ce2b event-on-change-reading .*
attr tuya_cloud_3367036770039f60ce2b group tuya_cloud
attr tuya_cloud_3367036770039f60ce2b room fhempy
>>>> aktiv >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>bereits Local vorhanden
define tuya_cloud_453005615002911dfe06 fhempy tuya_cloud TUYA 453005615002911dfe06
setuuid tuya_cloud_453005615002911dfe06 63dfbaa7-f33f-fd5f-77e2-78d57c6e3f7d09db
attr tuya_cloud_453005615002911dfe06 DbLogExclude .*
attr tuya_cloud_453005615002911dfe06 alias Heizkissen 2
attr tuya_cloud_453005615002911dfe06 event-on-change-reading .*
attr tuya_cloud_453005615002911dfe06 group tuya_cloud
attr tuya_cloud_453005615002911dfe06 room fhempy
>>>>> aktiv >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>bereits Local vorhanden
define tuya_cloud_720570712462ab27e625 fhempy tuya_cloud TUYA 720570712462ab27e625
setuuid tuya_cloud_720570712462ab27e625 63dfbab0-f33f-fd5f-39f8-d7bb6d72c54a3b42
attr tuya_cloud_720570712462ab27e625 DbLogExclude .*
attr tuya_cloud_720570712462ab27e625 alias Steckdose 4
attr tuya_cloud_720570712462ab27e625 event-on-change-reading .*
attr tuya_cloud_720570712462ab27e625 group tuya_cloud
attr tuya_cloud_720570712462ab27e625 room fhempy
>>>>nicht online und auch nicht mehr in TUYA_cloud >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>bereits Local vorhanden
[/code]
letzteres garnicht nicht mehr in der Cloud.
fhempY-Log:
2023-02-05 18:29:01,670 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 18:29:03,407 - ERROR - fhempy.lib.fhem: FHEM took 5006ms for readingsEndUpdate($defs{'TUYA_JL04'},1);;
2023-02-05 18:29:06,822 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 18:29:07,179 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 18:29:11,873 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 18:29:16,922 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 18:29:17,270 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 18:29:21,946 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 18:29:26,987 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 18:29:27,364 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 18:29:32,081 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 18:29:37,093 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 18:29:37,466 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 18:29:42,172 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 18:29:47,194 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 18:29:47,561 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 18:29:52,233 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 18:29:54,254 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 18:29:57,246 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 18:29:57,574 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 18:30:02,258 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 18:30:07,269 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 18:30:07,586 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 18:30:12,372 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 18:30:17,413 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 18:30:17,669 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 18:30:22,454 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 18:30:27,505 - WARNING - asyncio: socket.send() raised exception.
2023-02-05 18:30:27,761 - WARNING - asyncio: socket.send() raised exception.
JL04 ist online
fhem.log
2023.02.05 17:30:14 3: Kueche_Rollo_3_down_Notify return value: OK
2023.02.05 17:30:14 1: [Freezemon] myFreezemon: possible freeze starting at 17:30:12, delay is 2.229 possibly caused by: tmr-at_Exec(Kueche_Rollo_3_bei_Sonnenuntergang_runter_AT)
2023.02.05 17:43:59 1: [Freezemon] myFreezemon: possible freeze starting at 17:43:49, delay is 10.224 possibly caused by: no bad guy found :-(
2023.02.05 17:45:01 2: CM_Parse, unhandled message type 45 from MAX_002ad5 to MAX_26850e - ignoring !
2023.02.05 17:45:14 3: Untergeschoss_Rollo_1_down_Notify return value: OK
2023.02.05 17:45:16 3: Obergeschoss_Rollo_1_down_Notify return value: OK
2023.02.05 17:45:18 3: Wohnzimmer_Rollo_1_down_Notify return value: OK
2023.02.05 17:45:21 3: Wohnzimmer_Rollo_3_down_Notify return value: OK
2023.02.05 17:45:21 1: [Freezemon] myFreezemon: possible freeze starting at 17:45:12, delay is 9.415 possibly caused by: tmr-at_Exec(Untergeschoss_Rollo_1_bei_Sonnenuntergang_runter_AT) tmr-at_Exec(Obergeschoss_Rollo_1_bei_Sonnenuntergang_runter_AT) tmr-at_Exec(Wohnzimmer_Rollo_1_bei_Sonnenuntergang_runter_AT) tmr-at_Exec(Wohnzimmer_Rollo_3_bei_Sonnenuntergang_runter_AT)
2023.02.05 17:45:24 1: [Freezemon] myFreezemon: possible freeze starting at 17:45:23, delay is 1.88 possibly caused by: no bad guy found :-(
2023.02.05 17:45:27 2: CM_Parse, unhandled message type C0 from MAX_0018c9 to MAX_048989 - ignoring !
2023.02.05 17:45:27 2: CM_Parse, unhandled message type 07 from MAX_898a00 to MAX_015800 - ignoring !
2023.02.05 17:45:47 2: CM_Parse, unhandled message type 88 from MAX_0caa04 to MAX_420ccd - ignoring !
2023.02.05 17:45:47 3: CM_Parse, unhandled message PairPong from MAX_58232a to MAX_328a8a, groupid : 1 , payload : 880C7E04420CCD8716EDC5002AD308860E7E02 - ignoring !
2023.02.05 17:45:55 2: CM_Parse, unhandled message type CD from MAX_870158 to MAX_182a21 - ignoring !
2023.02.05 17:45:55 3: MaxSystem, device MAX_015823 want to be re-paired to MAX_2a328a, not to us [123456] - ignoring !
2023.02.05 17:46:35 1: [Freezemon] myFreezemon: possible freeze starting at 17:46:23, delay is 12.166 possibly caused by: tmr-MAX_Timer(MAX_PETRA_F3) tmr-DbLog_execMemCacheAsync(dblog_THB)
2023.02.05 17:48:21 1: [Freezemon] myFreezemon: possible freeze starting at 17:48:10, delay is 11.142 possibly caused by: no bad guy found :-(
2023.02.05 17:50:46 1: [Freezemon] myFreezemon: possible freeze starting at 17:50:45, delay is 1.739 possibly caused by: no bad guy found :-(
2023.02.05 17:50:52 1: [Freezemon] myFreezemon: possible freeze starting at 17:50:51, delay is 1.394 possibly caused by: no bad guy found :-(
2023.02.05 17:50:57 1: [Freezemon] myFreezemon: possible freeze starting at 17:50:55, delay is 2.455 possibly caused by: no bad guy found :-(
2023.02.05 17:51:23 1: [Freezemon] myFreezemon: possible freeze starting at 17:51:22, delay is 1.134 possibly caused by: no bad guy found :-(
2023.02.05 18:05:45 1: [Freezemon] myFreezemon: possible freeze starting at 18:05:31, delay is 14.187 possibly caused by: no bad guy found :-(
2023.02.05 18:05:56 1: [Freezemon] myFreezemon: possible freeze starting at 18:05:55, delay is 1.458 possibly caused by: no bad guy found :-(
2023.02.05 18:06:56 1: [Freezemon] myFreezemon: possible freeze starting at 18:06:54, delay is 2.229 possibly caused by: no bad guy found :-(
2023.02.05 18:07:56 1: [Freezemon] myFreezemon: possible freeze starting at 18:07:55, delay is 1.032 possibly caused by: no bad guy found :-(
2023.02.05 18:08:56 1: [Freezemon] myFreezemon: possible freeze starting at 18:08:55, delay is 1.136 possibly caused by: no bad guy found :-(
2023.02.05 18:12:17 1: [Freezemon] myFreezemon: possible freeze starting at 18:12:16, delay is 1.592 possibly caused by: no bad guy found :-(
2023.02.05 18:15:34 1: [Freezemon] myFreezemon: possible freeze starting at 18:15:33, delay is 1.055 possibly caused by: no bad guy found :-(
2023.02.05 18:15:36 1: [Freezemon] myFreezemon: possible freeze starting at 18:15:35, delay is 1.523 possibly caused by: no bad guy found :-(
2023.02.05 18:15:57 1: [Freezemon] myFreezemon: possible freeze starting at 18:15:56, delay is 1.698 possibly caused by: no bad guy found :-(
2023.02.05 18:16:22 1: [Freezemon] myFreezemon: possible freeze starting at 18:16:21, delay is 1.317 possibly caused by: tmr-MAX_Timer(MAX_THOMAS_F2)
2023.02.05 18:17:08 1: [Freezemon] myFreezemon: possible freeze starting at 18:17:06, delay is 2.049 possibly caused by: no bad guy found :-(
2023.02.05 18:17:15 1: [Freezemon] myFreezemon: possible freeze starting at 18:17:14, delay is 1.057 possibly caused by: no bad guy found :-(
2023.02.05 18:17:37 1: [Freezemon] myFreezemon: possible freeze starting at 18:17:36, delay is 1.392 possibly caused by: no bad guy found :-(
2023.02.05 18:17:57 1: [Freezemon] myFreezemon: possible freeze starting at 18:17:56, delay is 1.452 possibly caused by: no bad guy found :-(
2023.02.05 18:18:08 1: [Freezemon] myFreezemon: possible freeze starting at 18:18:06, delay is 2.767 possibly caused by: no bad guy found :-(
2023.02.05 18:18:12 1: [Freezemon] myFreezemon: possible freeze starting at 18:18:11, delay is 1.285 possibly caused by: no bad guy found :-(
2023.02.05 18:18:53 1: [Freezemon] myFreezemon: possible freeze starting at 18:18:52, delay is 1.871 possibly caused by: no bad guy found :-(
2023.02.05 18:19:37 3: Watchdog WDT_HWR_F2 triggered
2023.02.05 18:19:59 1: [Freezemon] myFreezemon: possible freeze starting at 18:19:58, delay is 1.254 possibly caused by: no bad guy found :-(
2023.02.05 18:20:01 1: [Freezemon] myFreezemon: possible freeze starting at 18:20:00, delay is 1.096 possibly caused by: tmr-DbLog_execMemCacheAsync(dblog_THB)
2023.02.05 18:20:09 1: [Freezemon] myFreezemon: possible freeze starting at 18:20:08, delay is 1.335 possibly caused by: no bad guy found :-(
2023.02.05 18:20:11 1: [Freezemon] myFreezemon: possible freeze starting at 18:20:10, delay is 1.381 possibly caused by: no bad guy found :-(
2023.02.05 18:20:13 1: [Freezemon] myFreezemon: possible freeze starting at 18:20:12, delay is 1.408 possibly caused by: no bad guy found :-(
2023.02.05 18:21:58 1: [Freezemon] myFreezemon: possible freeze starting at 18:21:57, delay is 1.021 possibly caused by: no bad guy found :-(
2023.02.05 18:22:01 1: [Freezemon] myFreezemon: possible freeze starting at 18:22:00, delay is 1.8 possibly caused by: tmr-DbLog_execMemCacheAsync(dblog_THB)
2023.02.05 18:22:12 1: [Freezemon] myFreezemon: possible freeze starting at 18:22:11, delay is 1.948 possibly caused by: no bad guy found :-(
2023.02.05 18:22:14 1: [Freezemon] myFreezemon: possible freeze starting at 18:22:13, delay is 1.505 possibly caused by: no bad guy found :-(
2023.02.05 18:25:10 1: [Freezemon] myFreezemon: possible freeze starting at 18:25:09, delay is 1.299 possibly caused by: no bad guy found :-(
2023.02.05 18:25:32 1: [Freezemon] myFreezemon: possible freeze starting at 18:25:31, delay is 1.171 possibly caused by: no bad guy found :-(
2023.02.05 18:25:56 1: [Freezemon] myFreezemon: possible freeze starting at 18:25:54, delay is 2.577 possibly caused by: no bad guy found :-(
2023.02.05 18:26:01 1: [Freezemon] myFreezemon: possible freeze starting at 18:25:59, delay is 2.153 possibly caused by: no bad guy found :-(
2023.02.05 18:27:41 1: [Freezemon] myFreezemon: possible freeze starting at 18:27:40, delay is 1.385 possibly caused by: no bad guy found :-(
2023.02.05 18:27:51 1: [Freezemon] myFreezemon: possible freeze starting at 18:27:50, delay is 1.126 possibly caused by: no bad guy found :-(
2023.02.05 18:28:21 1: [Freezemon] myFreezemon: possible freeze starting at 18:28:20, delay is 1.374 possibly caused by: no bad guy found :-(
2023.02.05 18:28:58 1: [Freezemon] myFreezemon: possible freeze starting at 18:28:57, delay is 1.406 possibly caused by: no bad guy found :-(
2023.02.05 18:29:03 1: [Freezemon] myFreezemon: possible freeze starting at 18:28:59, delay is 4.408 possibly caused by: no bad guy found :-(
2023.02.05 18:29:52 1: [Freezemon] myFreezemon: possible freeze starting at 18:29:51, delay is 1.639 possibly caused by: no bad guy found :-(
2023.02.05 18:30:36 1: [Freezemon] myFreezemon: possible freeze starting at 18:30:35, delay is 1.042 possibly caused by: no bad guy found :-(
2023.02.05 18:30:38 1: [Freezemon] myFreezemon: possible freeze starting at 18:30:37, delay is 1.161 possibly caused by: no bad guy found :-(
2023.02.05 18:30:47 1: [Freezemon] myFreezemon: possible freeze starting at 18:30:46, delay is 1.015 possibly caused by: no bad guy found :-(
2023.02.05 18:31:21 1: [Freezemon] myFreezemon: possible freeze starting at 18:31:20, delay is 1.12 possibly caused by: no bad guy found :-(
2023.02.05 18:32:16 1: [Freezemon] myFreezemon: possible freeze starting at 18:32:15, delay is 1.193 possibly caused by: no bad guy found :-(
2023.02.05 18:32:37 1: [Freezemon] myFreezemon: possible freeze starting at 18:32:35, delay is 2.565 possibly caused by: tmr-DbLog_execMemCacheAsync(dblog_THB)
ja da sind einige delays..
aver warum muss dann FHEMPY ein neues Device anlegen??
Die Daten kommen doch an.
Ich vermute, dass fhempy bei Schaltern Schaltvorgänge innerhalb einer Sekunde mitkriegen soll; deshalb wird häufig abgefragt.
Statt ein neues Device anzulegen, könnte fhempy sich fhempy doch merken, dass das Gerät aus welchem Grund auch immer nicht alive ist und es nach xxx Sekunden erst wieder versuchen.
Kann es nicht doch sein, dass fhempy selbst zu hohe Last erzeugt bei eben über 100 devices?
Von 0.1.589 auf 0.1.593 gab es keine Änderung, da ich alle Änderungen aus den Versionen dazwischen wieder entfernt hatte. 589 ist also gleich wie 593.
Nochmals zur Erklärung was passiert und warum Devices manchmal doppelt erstellt werden:
- fhempy schickt einen Befehl an FHEM um zu prüfen ob ein Device existiert
- wenn in der Zeit FHEM für längere Zeit blockiert, dann erhält FHEM diesen Befehl nicht und es kommt das WARNING asyncio.send() im fhempy Log
- Für fhempy bedeutet das, dass kein Device gefunden wurde und somit ein neues angelegt wird. Da ich in fhempy leider noch keine Möglichkeit gefunden habe zu erkennen wann ein Befehl in FHEM nicht ankommt, kann ich das noch nicht anders handhaben.
Dieses Verhalten kann bei ALLEN Befehlen auftreten. Mal ist es die Prüfung ob ein Device existiert, mal ist es ein Update der Readings und mal was ganz anderes. Das Verhalten ist also jedes mal anders.
Die Ursache liegt jedoch in FHEM bei dir, dass für lange Zeit blockiert. Du siehst es auch beim freezemon, welches in der Zeit um 18:29 herum, wo auch die Warnings in fhempy kommen, jede Menge Freezes hat.
Zu deiner Vermutung, dass fhempy die Devices häufig abfragt:
fhempy muss für die "Überwachung" der Devices wegen Schaltzustand nix machen außer eine Verbindung aufrecht halten. Das kostet also keine CPU. Wie schon öfter erwähnt, fhempy fragt nicht häufig ab, sondern erhält einen Event vom Device sobald geschalten wird.
Fazit:
- Ich schau in fhempy wie ich solche Fehler handhaben kann
- Du solltest in FHEM schauen wie du deine Freezes wegbekommst
Für mich sind deine Freezes natürlich sehr hilfreich um fhempy zu verbessern ;)
hi Dominik,
perfektes Fazit !! :-)
witzigerweise habe ich nach einem Stromausfall am Raspi zwar eine lange Wartezeit, bis room fhempy wieder flüssig anzeigt. Es gibt aktuell keine Doppelten mehr :-)
Im Vorfeld hatte ich die kritischen Devices in local neu scanen lassen.
Es würde mich riesig freuen, wenn Du das Thema "Kumulation Verbrauchswerte" bald mit auf Deine Agenda nimmst.
Ich teste dann auch fleißig ;-)
viele Grüße und Dank
von Thomas
Verbrauchswerte kommen erst wenn die Probleme hier behoben sind. Es macht keinen Sinn eine 2. Baustelle aufzumachen wenn die Basis nicht zuverlässig funktioniert.
Zitat von: McShire am 30 Januar 2023, 00:50:22
Jetzt funktioniert es, zumindest schon der Server und das BindingIo.
Das device zur Steuerung von Tuya (Ölradiator von Kesser) trage ich später ein.
Hallo Dominik,
leider funktioniert es doch nicht. Die Icons von fhempy_local und fhempyserver sind zwar grün,
aber fhem_local steht dauerhaft auf installing fhempy mit previous error Verbindungsaufbau abgelehnt
und der server ist running.
Ich habe auf dem Raspi3b+ ein Upgrade auf Bullseye durchgeführt und Python 3.9.16 installiert.
Aber leider immer das gleich Verhalten, sowohl bei Buster mit Python 3.9.2 und 3.9.16
als auch bei Bullseye mit 3.9.2 oder 3.9.16.
Hier die beiden lists:
fhempy_local:
Internals:
BindingType fhempy
DEF fhempy
DeviceName ws:localhost:15733
FUUID 63dfe147-f33f-f21b-158d-2320d4208add6a9c
IP 127.0.0.1
NAME fhempy_local
NEXT_OPEN 1675620943.39065
NR 1015
NTFY_ORDER 50-fhempy_local
PARTIAL
PORT 15733
STATE Installing fhempy (15min)...
TYPE BindingsIo
binary 1
devioLoglevel 0
eventCount 4681
installing 0
localBinding 1
nextOpenDelay 10
prev_error localhost: Verbindungsaufbau abgelehnt (111)
READINGS:
2023-02-05 21:52:58 state Installing fhempy (15min)...
args:
fhempy_local
BindingsIo
fhempy
Attributes:
devStateIcon { my $attr_ver = "1.1.0";; my $status_img = "10px-kreis-gruen";; my $status_txt = "connected";; my $ver = ReadingsVal($name, "version", "-");; my $ver_available = ReadingsVal($name, "version_available", $ver);; my $update_icon = "";; my $refresh_img = "refresh";; my $refresh_txt = "Update fhempy";; if ($ver_available ne $ver) { $refresh_img = "refresh\@orange";; $refresh_txt = "Version ".$ver_available." available for update";; } if (ReadingsVal($name, "state", "disconnected") eq "disconnected") { $status_img = "10px-kreis-rot";; $status_txt = "disconnected";; } $update_icon = "<a href=\"/fhem?cmd.dummy=set $name update&XHR=1\" title=\"Start ".$ver_available." update\">".FW_makeImage($refresh_img, $refresh_txt)."</a>";; my $restart_icon = "<a href=\"/fhem?cmd.dummy=set $name restart&XHR=1\" title=\"Restart fhempy\">".FW_makeImage("control_reboot")."</a>";; "<div><a>".FW_makeImage($status_img, $status_txt)."</a><a> ".$ver." </a>".$update_icon.$restart_icon."</div>" }
group fhempy
icon file_json-ld2
room fhempy
fhempyserver:
Internals:
DEF 0
FD 4
FUUID 63dfe147-f33f-f21b-5561-05bc61eeadb59101
LAST_START 2023-02-05 21:54:21
LAST_STOP 2023-02-05 21:54:21
NAME fhempyserver_15733
NR 1016
NTFY_ORDER 50-fhempyserver_15733
PID 2345
STARTS 66
STATE ???
TYPE fhempyServer
currentlogfile ./log/fhempy-2023-02-05.log
eventCount 132
logfile ./log/fhempy-%Y-%m-%d.log
CoProcess:
cmdFn fhempyServer_getCmd
name fhempy
state running FHEM/bindings/python/bin/fhempy
READINGS:
2023-02-05 21:54:21 fhempy running FHEM/bindings/python/bin/fhempy
2023-02-05 19:15:16 python v3.9.16
Attributes:
devStateIcon { my $status_img = "10px-kreis-gruen";; my $status_txt = "running";; if (substr(ReadingsVal($name, "fhempy", "running"),0,7) ne "running") { $status_img = "10px-kreis-rot";; $status_txt = "stopped";; } "<div><a>".FW_makeImage($status_img, $status_txt)."</a><a href=\"/fhem?cmd.dummy=set $name restart&XHR=1\" title=\"Kill and restart\">".FW_makeImage("audio_repeat")."</a></div>" }
group fhempy
icon python
logfile ./log/fhempy-%Y-%m-%d.log
nrarchive 10
room fhempy
Hast Du einen Lösungsansatz?
Viele Grüße
Werner
Bitte fhempy Log und fhem Log.
Noch im Nachtrag Einträge (immer wiederholend) im Logfile:
2023.02.05 22:01:35 3: fhempyserver_15733: read: end of file reached while sysread
2023.02.05 22:01:35 3: fhempyserver_15733: stopped
2023.02.05 22:01:35 3: fhempyserver_15733: starting
2023.02.05 22:01:35 3: fhempyserver_15733: using logfile: ./log/fhempy-2023-02-05.log
und dem fhempy-log:
WARNING: You are using pip version 22.0.4; however, version 23.0 is available.
You should consider upgrading via the '/usr/bin/python3 -m pip install --upgrade pip' command.
2023-02-05 18:17:16,600 - ERROR - __main__: Failed to install fhempy, exit now...
2023-02-05 18:18:17,108 - ERROR - __main__: Failed to load fhempy
Traceback (most recent call last):
File "/opt/fhem/FHEM/bindings/python/bin/fhempy", line 139, in <module>
import fhempy.lib.fhem_pythonbinding as fpb
ModuleNotFoundError: No module named 'fhempy'
2023-02-05 18:18:17,110 - INFO - __main__: Attempting install of fhempy>=0.1.462
2023-02-05 18:19:44,777 - ERROR - __main__: Unable to install package fhempy>=0.1.462: WARNING: The directory '/opt/fhem/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
ERROR: Could not install packages due to an OSError: [Errno 13] Keine Berechtigung: '/opt/fhem/.local'
Check the permissions.
die Verzeichnisse von /opt/fhem/.local und /opt/fhem/.cache gibt es im Verzeichnis /opt/fhem nicht nur /opt/fhem/cache, das scheint aber nicht das Richtige zu sein.
und das Ergebnis vom nicht funktionierendem pip Update im Anhang.
Die Berechtigung von /opt/fhem habe ich jetzt auf 777 gestellt
Du musst die Berechtigung von /opt/fhem/.local fixen.
chown -R fhem:dialout /opt/fhem
Dann sollte alles wieder richtig sein von den Berechtigungen.
jetzt hat sich etwas geändert, das logo ist gelb, mal 15 min auf installation warten
danke für den Tip mit der Berechtigung.
Es tut sich was
2023-02-05 22:40:45,502 - INFO - __main__: Attempting install of fhempy>=0.1.462
2023-02-05 22:42:44,281 - INFO - __main__: Successfully installed fhempy>=0.1.462
2023-02-05 22:42:44,283 - ERROR - __main__: Failed to import fhempy, exit now...
2023-02-05 22:43:48,270 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.593...
2023-02-05 22:43:48,378 - INFO - fhempy.lib.pkg_installer: Attempting install of async-upnp-client==0.31.2
2023-02-05 22:44:05,194 - INFO - fhempy.lib.pkg_installer: Successfully installed async-upnp-client==0.31.2 update!
2023-02-05 22:44:05,198 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-02-05 22:44:05,313 - INFO - websockets.server: server listening on 0.0.0.0:15733
2023-02-05 22:45:40,640 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.593...
2023-02-05 22:45:40,653 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-02-05 22:45:40,821 - INFO - websockets.server: server listening on 0.0.0.0:15733
2023-02-05 22:45:48,315 - INFO - websockets.server: connection open
2023-02-05 22:45:48,317 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
Zitat von: dominik am 05 Februar 2023, 22:45:10
Du musst die Berechtigung von /opt/fhem/.local fixen.
chown -R fhem:dialout /opt/fhem
Dann sollte alles wieder richtig sein von den Berechtigungen.
Eine Datei .local gibt es nicht im fhem-Verzeichnis
Zitat von: dominik am 05 Februar 2023, 22:45:10
Du musst die Berechtigung von /opt/fhem/.local fixen.
chown -R fhem:dialout /opt/fhem
Dann sollte alles wieder richtig sein von den Berechtigungen.
Ist das korrekt? Jetzt haben alle Dateien und Verzeichnisse unter /opt/fhem den Eigentümer dialout.
Hallo Dominik,
wenn ich es richtig sehe, ist jetzt alles ok. Siehe Logfile vom Server
2023-02-05 23:31:17,345 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.593...
2023-02-05 23:31:17,356 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-02-05 23:31:17,506 - INFO - websockets.server: server listening on 0.0.0.0:15733
2023-02-05 23:31:23,325 - INFO - websockets.server: connection open
2023-02-05 23:31:23,327 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
Vielen Dank für deine Hilfe.
Jetzt werde ich in den nächsten Tagen mein erstes Gerät über die Tuya Platform einbinden.
Viele Grüße
Werner
Hallo Dominik,
jetzt habe ich den tuya_cloud_connector definiert.
Hier das list
Internals:
DEF tuya_cloud setup 5xxxxxxxxfget e1ecxxxxxxxxxxxxebe12 werxxxxxxxxxxxxxxe Kixxxxxxx0 Tuya Smart Europe
DEVICEID 0
FHEMPYTYPE tuya_cloud
FUUID 63e0bad4-f33f-f21b-ccbc-281354202aeb0756
IODev fhempy_local
NAME tuya_cloud_connector
NR 1017
PYTHONTYPE tuya_cloud
STATE connecting
TYPE fhempy
eventCount 11
READINGS:
2023-02-06 15:50:00 state connecting
args:
tuya_cloud_connector
fhempy
tuya_cloud
setup
5xmxxxxxxxxxxxxxget
e1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxe12
wernxxxxxxxxxxxxxxxxxde
Kixxxxxxxxxxx0
Tuya
Smart
Europe
argsh:
Attributes:
group tuya_cloud
room fhempy
was mir auffällt:
- state ist connecting, nicht connected, die Login Daten stimmen sonst kommt eine
Fehlermeldung
- Es wird kein device gemäß meines Projektes in der tuya_development_Platform
angelegt
Das Projekt:
Kesser Oil Radiator
Kesser Oil Radiator
Integration of the Radiator into the smart home environment fhem
Industry : Smart Home
Creation Time : 2023-01-20 22:03:43
Data Center : Central Europe Data Center
Authorization Key
Access ID/Client ID: 5xxxxxxxxxget
Access Secret/Client Secret: exxxxxxxxxxxxxxxxxxxxxxxxxxbe12
Project Code: p16xxxxxxxxxxxxxxxxxxkv9
Cloud Authorization IP AllowlistConfigure
Central Europe Data Center：1 IP(s) addedView
Was kann ich tun, damit der Radiator angelegt wird?
Viele Grüße
Werner
Die letzten Einträge im Server log:
packages/fhempy/lib/generic.py:194> exception=TypeError("unsupported operand type(s) for +: 'NoneType' and 'str'")>
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/generic.py", line 202, in _handle_task_result
task.result()
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/generic.py", line 196, in _run_coro
await coro
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 58, in run_setup
if await self._init_tuya_sdk() is True:
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 106, in _init_tuya_sdk
else await utils.run_blocking(
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/utils.py", line 72, in run_blocking
return await asyncio.get_event_loop().run_in_executor(pool, function)
File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
File "/opt/fhem/.local/lib/python3.9/site-packages/tuya_iot/openapi.py", line 208, in connect
response = self.post(
File "/opt/fhem/.local/lib/python3.9/site-packages/tuya_iot/openapi.py", line 316, in post
return self.__request("POST", path, None, body)
File "/opt/fhem/.local/lib/python3.9/site-packages/tuya_iot/openapi.py", line 260, in __request
url = {self.endpoint + path},\
TypeError: unsupported operand type(s) for +: 'NoneType' and 'str'
und das Logfile nach shutdown restart:
2023-02-06 18:21:33,055 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.593...
2023-02-06 18:21:33,066 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-02-06 18:21:39,824 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2023-02-06 18:21:39,879 - DEBUG - fhempy.lib.fhem: <<< WS: {"msgtype": "version", "version": "0.1.593", "python": "3.9.16", "os": "posix", "system": "Linux", "release": "5.15.84-v7+", "hostname": "raspi3B"}
2023-02-06 18:21:39,978 - DEBUG - fhempy.lib.fhem_pythonbinding: >>> 60881822: {'PYTHONTYPE': 'tuya_cloud', 'function': 'Define', 'FHEMPYTYPE': 'tuya_cloud', 'defargsh': {}, 'NAME': 'tuya_cloud_connector', 'argsh': {}, 'id': '60881822', 'defargs': ['tuya_cloud_connector', 'fhempy', 'tuya_cloud', 'setup', '5xxxxxxxxxxget', 'e1xxxxxxxxxxxxxxxxxx2', 'werxxxxxxxxxx.de', 'Kixxxxxxx0', 'Tuya', 'Smart', 'Europe'], 'msgtype': 'function', 'args': ['tuya_cloud_connector', 'fhempy', 'tuya_cloud', 'setup', '5xxxxxxxxfget', 'e1xxxxxxxxxxxxxxxe12', 'werner.schwetje@t-online.de', 'Kixxxxxxxxx70', 'Tuya', 'Smart', 'Europe']}
2023-02-06 18:21:39,979 - DEBUG - fhempy.lib.fhem_pythonbinding: <<< 60881822 1.15ms: {'PYTHONTYPE': 'tuya_cloud', 'function': 'Define', 'FHEMPYTYPE': 'tuya_cloud', 'defargsh': {}, 'NAME': 'tuya_cloud_connector', 'argsh': {}, 'id': '60881822', 'defargs': ['tuya_cloud_connector', 'fhempy', 'tuya_cloud', 'setup', '5xmxxxxxxxxxxxfget', 'e1xxxxxxxxxxxxxe12', 'wernxxxxxxxxxxxxxxne.de', 'Kisxxxxxxxxxxxxxx0', 'Tuya', 'Smart', 'Europe'], 'msgtype': 'function', 'args': ['tuya_cloud_connector', 'fhempy', 'tuya_cloud', 'setup', '5xxxxxxxxxxxxxxxxxet', 'exxxxxxxxxxxxxxxxxxxxbe12', 'werxxxxxxxxxxxxxxxxxxxde', 'Kisxxxxxxxxxxxxxxx0', 'Tuya', 'Smart', 'Europe'], 'finished': 1, 'returnval': ''}
2023-02-06 18:21:40,375 - WARNING - asyncio: Executing <Task pending name='Task-11' coro=<send_latest_release() running at /opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/fhem.py:311> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x74f2d190>()] created at /usr/local/lib/python3.9/asyncio/base_events.py:429> created at /usr/local/lib/python3.9/asyncio/tasks.py:361> took 0.154 seconds
2023-02-06 18:21:40,401 - DEBUG - fhempy.lib.fhem_pythonbinding: >>> 50102601: {'args': ['tuya_cloud_connector', '?'], 'defargs': ['tuya_cloud_connector', 'fhempy', 'tuya_cloud', 'setup', '5xxxxxxxxxxxxxxt', 'exxxxxxxxxxxxxxxxxxe12', 'wexxxxxxxxxxxxxxxxxxxxe', 'Kixxxxxxxxxxxxxxxxx0', 'Tuya', 'Smart', 'Europe'], 'msgtype': 'function', 'NAME': 'tuya_cloud_connector', 'argsh': {}, 'id': '50102601', 'FHEMPYTYPE': 'tuya_cloud', 'function': 'Set', 'defargsh': {}, 'PYTHONTYPE': 'tuya_cloud'}
2023-02-06 18:21:40,404 - DEBUG - fhempy.lib.fhem_pythonbinding: <<< 50102601 3.54ms: {'args': ['tuya_cloud_connector', '?'], 'defargs': ['tuya_cloud_connector', 'fhempy', 'tuya_cloud', 'setup', '5xxxxxxxxxxxxxxxxget', 'e1xxxxxxxxxxxxxxxxxxxxxxxxxe12', 'werxxxxxxxxxxxxxxxxxxxxxxe', 'Kixxxxxxxxxxxxxxxx0', 'Tuya', 'Smart', 'Europe'], 'msgtype': 'function', 'NAME': 'tuya_cloud_connector', 'argsh': {}, 'id': '50102601', 'FHEMPYTYPE': 'tuya_cloud', 'function': 'Set', 'defargsh': {}, 'PYTHONTYPE': 'tuya_cloud', 'finished': 1, 'returnval': ''}
2023-02-06 18:21:40,469 - DEBUG - fhempy.lib.fhem: <<< WS: {"msgtype": "version", "version_available": "0.1.593", "version_release_notes": "<html><a href=\"https://github.com/fhempy/fhempy/releases\" target=\"_blank\">Release Notes</a></html>"}
2023-02-06 18:21:41,364 - DEBUG - fhempy.lib.core.discover_fhempy.discover_fhempy: Found service: _http._tcp.local. - Brother MFC-J5625DW._http._tcp.local.
2023-02-06 18:21:41,365 - DEBUG - fhempy.lib.core.discover_fhempy.discover_fhempy: Service Brother MFC-J5625DW._http._tcp.local. found, service info: AsyncServiceInfo(type='_http._tcp.local.', name='Brother MFC-J5625DW._http._tcp.local.', addresses=[b'\xc0\xa8\xb2 '], port=80, weight=0, priority=0, server='BRWB01041AE0F5D.local.', properties={}, interface_index=None)
2023-02-06 18:21:41,770 - DEBUG - fhempy.lib.fhem: <<< 88384148: {'awaitId': 88384148, 'NAME': 'tuya_cloud_connector', 'msgtype': 'command', 'command': "AttrVal('tuya_cloud_connector', 'verbose', '3')"}
2023-02-06 18:21:41,783 - DEBUG - fhempy.lib.fhem: >>> 88384148 12.70ms: {'error': 0, 'awaitId': 88384148, 'result': '3'}
2023-02-06 18:21:41,810 - DEBUG - fhempy.lib.fhem: <<< 34482423: {'awaitId': 34482423, 'NAME': 'tuya_cloud_connector', 'msgtype': 'command', 'command': '$init_done'}
2023-02-06 18:21:41,908 - DEBUG - fhempy.lib.fhem: >>> 34482423 98.66ms: {'error': 0, 'awaitId': 34482423, 'result': 1}
2023-02-06 18:21:41,919 - DEBUG - fhempy.lib.fhem: <<< 78437842: {'awaitId': 78437842, 'NAME': 'tuya_cloud_connector', 'msgtype': 'command', 'command': "AttrVal('tuya_cloud_connector', 'room', '')"}
2023-02-06 18:21:41,932 - DEBUG - fhempy.lib.fhem: >>> 78437842 13.07ms: {'result': 'fhempy', 'awaitId': 78437842, 'error': 0}
2023-02-06 18:21:41,943 - DEBUG - fhempy.lib.fhem: <<< 83773436: {'awaitId': 83773436, 'NAME': 'tuya_cloud_connector', 'msgtype': 'command', 'command': "AttrVal('tuya_cloud_connector', 'group', '')"}
2023-02-06 18:21:41,956 - DEBUG - fhempy.lib.fhem: >>> 83773436 13.13ms: {'error': 0, 'awaitId': 83773436, 'result': 'tuya_cloud'}
2023-02-06 18:21:42,103 - DEBUG - fhempy.lib.fhem: <<< 79257858: {'awaitId': 79257858, 'NAME': 'tuya_cloud_connector', 'msgtype': 'command', 'command': "setDevAttrList('tuya_cloud_connector', ' IODev '.$readingFnAttributes)"}
2023-02-06 18:21:42,460 - DEBUG - fhempy.lib.fhem: >>> 79257858 357.40ms: {'result': ' IODev:fhempy_local event-aggregator event-min-interval event-on-change-reading event-on-update-reading oldreadings stateFormat:textField-long timestamp-on-change-reading', 'awaitId': 79257858, 'error': 0}
2023-02-06 18:21:42,471 - DEBUG - fhempy.lib.fhem: <<< 79393227: {'awaitId': 79393227, 'NAME': 'tuya_cloud_connector', 'msgtype': 'command', 'command': "AttrVal('tuya_cloud_connector', 'verbose', '3')"}
2023-02-06 18:21:43,219 - DEBUG - fhempy.lib.fhem: >>> 79393227 748.61ms: {'result': '3', 'awaitId': 79393227, 'error': 0}
2023-02-06 18:21:43,235 - DEBUG - fhempy.lib.fhem: <<< 81640974: {'awaitId': 81640974, 'NAME': 'tuya_cloud_connector', 'msgtype': 'command', 'command': "readingsSingleUpdate($defs{'tuya_cloud_connector'},'state','connecting',1)"}
2023-02-06 18:21:43,238 - DEBUG - fhempy.lib.fhem_pythonbinding: <<< WS: {"PYTHONTYPE": "tuya_cloud", "function": "Define", "FHEMPYTYPE": "tuya_cloud", "defargsh": {}, "NAME": "tuya_cloud_connector", "argsh": {}, "defargs": ["tuya_cloud_connector", "fhempy", "tuya_cloud", "setup", "5xxxxxxxxxxxxxxxxxxxet", "e1xxxxxxxxxxxxxxxxxxxxxxxxxxx12", "werxxxxxxxxxxxxxxxxe", "Kixxxxxxxxxxxxxxxxxx70", "Tuya", "Smart", "Europe"], "msgtype": "update_hash", "args": ["tuya_cloud_connector", "fhempy", "tuya_cloud", "setup", "5xxxxxxxxxxxxxxxxxxet", "e1xxxxxxxxxxxxxxxxxxxxxxxxx12", "wxxxxxxxxxxxxxxxxe", "Kixxxxxxxxxxxxxxxxx0", "Tuya", "Smart", "Europe"], "DEVICEID": 0}
2023-02-06 18:21:43,420 - DEBUG - fhempy.lib.fhem_pythonbinding: >>> 14613249: {'FHEMPYTYPE': 'tuya_cloud', 'function': 'Set', 'defargsh': {}, 'PYTHONTYPE': 'tuya_cloud', 'args': ['tuya_cloud_connector', '?'], 'defargs': ['tuya_cloud_connector', 'fhempy', 'tuya_cloud', 'setup', '5xxxxxxxxxxxxxxxxxxt', 'e1xxxxxxxxxxxxxxxxx12', 'wxxxxxxxxxxxxxxxxxxxxxxe', 'Kixxxxxxxxxxxxxxxx0', 'Tuya', 'Smart', 'Europe'], 'msgtype': 'function', 'NAME': 'tuya_cloud_connector', 'argsh': {}, 'id': '14613249'}
2023-02-06 18:21:43,429 - DEBUG - fhempy.lib.fhem_pythonbinding: <<< 14613249 8.77ms: {'FHEMPYTYPE': 'tuya_cloud', 'function': 'Set', 'defargsh': {}, 'PYTHONTYPE': 'tuya_cloud', 'args': ['tuya_cloud_connector', '?'], 'defargs': ['tuya_cloud_connector', 'fhempy', 'tuya_cloud', 'setup', '5xxxxxxxxxxxxxxxxxxxxxet', 'exxxxxxxxxxxxxxxxxx12', 'wxxxxxxxxxxxxxxxxxxxxe', 'Kixxxxxxxxxxxxxxxxxx', 'Tuya', 'Smart', 'Europe'], 'msgtype': 'function', 'NAME': 'tuya_cloud_connector', 'argsh': {}, 'id': '14613249', 'finished': 1, 'returnval': 'Unknown argument ?, choose one of '}
2023-02-06 18:21:43,441 - DEBUG - fhempy.lib.fhem: >>> 81640974 206.01ms: {'error': 0, 'result': 'connecting', 'awaitId': 81640974}
2023-02-06 18:21:43,456 - ERROR - tuya_cloud_connector: Exception raised by task: <Task finished name='Task-30' coro=<FhemModule._run_coro() done, defined at /opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/generic.py:194> exception=TypeError("unsupported operand type(s) for +: 'NoneType' and 'str'") created at /usr/local/lib/python3.9/asyncio/tasks.py:361>
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/generic.py", line 202, in _handle_task_result
task.result()
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/generic.py", line 196, in _run_coro
await coro
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 58, in run_setup
if await self._init_tuya_sdk() is True:
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 106, in _init_tuya_sdk
else await utils.run_blocking(
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/utils.py", line 72, in run_blocking
return await asyncio.get_event_loop().run_in_executor(pool, function)
File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
File "/opt/fhem/.local/lib/python3.9/site-packages/tuya_iot/openapi.py", line 208, in connect
response = self.post(
File "/opt/fhem/.local/lib/python3.9/site-packages/tuya_iot/openapi.py", line 316, in post
return self.__request("POST", path, None, body)
File "/opt/fhem/.local/lib/python3.9/site-packages/tuya_iot/openapi.py", line 260, in __request
url = {self.endpoint + path},\
TypeError: unsupported operand type(s) for +: 'NoneType' and 'str'
Dein Define ist falsch:
define tuya_cloud_connector fhempy tuya_cloud setup <CLIENT_ID> <CLIENT_SECRET> <USERNAME> <PASSWORD> [<APPTYPE>] [<REGION>]
APPTYPE=tuyaSmart
tuyaSmart hat er nicht akzeptiert TuyaSmart und andere Variationen auch nicht nur Tuya Smart, so heißt die App auch
Hallo Dominik,
Das Ist das Ergebnis, wenn ich tuyaSmart oder die anderen Varianten einsetze.
tuya_cloud
tuya_cloud_connector
failed to login: {'code': 1106, 'msg': 'permission deny', 'success': False, 't': 1675711982082, 'tid': '11d23659a65511edae3d265fe02d1603'}
und das Ergebnis bei Tuya Smart:
Readings
state
connecting
2023-02-06 21:10:48
Ich habe jetzt ziemlich alles durchprobiert, nur bei Tuya Smart und (Tuya Smart) wird das Reading state connecting.
Dabei sieht der Server Tuya Smart oder (Tuya Smart) als 2 Parameter an, im Logfile steht dann xxx' , '(Tuya' , 'Smart) ', 'Europe
Wie kann ich dem Server beibringen das Tuya Smart ein Parameter/String ist, in Hochkomma setzen funktioniert leider auch nicht.
Oder wie kann man dem Tuya Server sagen, dass er tuyaSmart als den Namen der App versteht?
Das login und der state connecting funktionieren immer nur, wenn die Tuya und Smart getrennt sind, aber im Log werden sie dann immer als 2 Parameter aufgeführt.
Wenn ich "Tuya Smart" schreibe, steht im Log xxx0", "Tuya", "Smart", "Europe"] und im state failed to login
Bei allen anderen Zeichen ''Tuya Smart'' (2x Hochkomma) oder (Tuya Smart) usw steht im Log xxxxx0', 'Tuya', 'Smart', 'Europe']
oder xxxx0', '(Tuya', 'Smart)', 'Europe'] usw.
Bei 'Tuya Smart' wird im Log der Parameter richtig dargestellt xxxxx0', 'Tuya Smart', 'Europe'] , aber dann Fehlermeldung und kein login und kein conncting, weil es dann vermutlich so wie du es geschrieben hast tuyaSmart im log heißen muss.
Bei tuyaSmart steht imLogfile das Argument xxxxx0', 'tuyaSmart', 'Europe'], aber failed to login und kein connecting.
Da komme ich ohne deine Hilfe nicht mehr weiter.
Hier ist noch einmal der vollständige Log-Eintrag für tuyaSmart
2023-02-06 22:59:57,576 - DEBUG - fhempy.lib.fhem_pythonbinding: >>> 11008797: {'function': 'Define', 'msgtype': 'function', 'NAME': 'tuya_cloud_connector', 'args': ['tuya_cloud_connector', 'fhempy', 'tuya_cloud', 'setup', '5xxxxxxxxxxxxxet', 'exxxxxxxxxxxxxxx2', 'werner.schwetje@t-online.de', 'Kxxxxxxxxxxxxxxx0', 'tuyaSmart', 'Europe'], 'defargsh': {}, 'FHEMPYTYPE': 'tuya_cloud', 'PYTHONTYPE': 'tuya_cloud', 'argsh': {}, 'defargs': ['tuya_cloud_connector', 'fhempy', 'tuya_cloud', 'setup', '5xxxxxxxxxxxxxxt', 'exxxxxxxxxxxxxe12', 'wxxxxxxxxxxxxxde', 'Kxxxxxxxxxxxxx0', 'tuyaSmart', 'Europe'], 'id': '11008797'}
2023-02-06 22:59:57,585 - DEBUG - fhempy.lib.fhem_pythonbinding: <<< 11008797 8.76ms: {'function': 'Define', 'msgtype': 'function', 'NAME': 'tuya_cloud_connector', 'args': ['tuya_cloud_connector', 'fhempy', 'tuya_cloud', 'setup', '5xxxxxxxxxxxxxet', 'e1xxxxxxxxxxxxx12', 'werxxxxxxxxxxxxxe', 'Kxxxxxxxxxxxxx0', 'tuyaSmart', 'Europe'], 'defargsh': {}, 'FHEMPYTYPE': 'tuya_cloud', 'PYTHONTYPE': 'tuya_cloud', 'argsh': {}, 'defargs': ['tuya_cloud_connector', 'fhempy', 'tuya_cloud', 'setup', '5xxxxxxxxxxxxxeget', 'exxxxxxxxxxxxx12', 'wxxxxxxxxxxxxxee', 'Kxxxxxxxxxxxxxe0', 'tuyaSmart', 'Europe'], 'id': '11008797', 'finished': 1, 'returnval': ''}
2023-02-06 22:59:57,617 - DEBUG - fhempy.lib.fhem_pythonbinding: >>> 80410359: {'defargs': ['tuya_cloud_connector', 'fhempy', 'tuya_cloud', 'setup', '5xmvn7d9yt9crdfwfget', 'e1xxxxxxxxxxxxxee12', 'wxxxxxxxxxxxxxxee', 'Kxxxxxxxxxxxxxe70', 'tuyaSmart', 'Europe'], 'id': '80410359', 'argsh': {}, 'PYTHONTYPE': 'tuya_cloud', 'FHEMPYTYPE': 'tuya_cloud', 'defargsh': {}, 'args': ['tuya_cloud_connector', '?'], 'NAME': 'tuya_cloud_connector', 'function': 'Set', 'msgtype': 'function'}
2023-02-06 22:59:57,622 - DEBUG - fhempy.lib.fhem_pythonbinding: <<< 80410359 4.73ms: {'defargs': ['tuya_cloud_connector', 'fhempy', 'tuya_cloud', 'setup', '5xxxxxxxxxxxxxxeet', 'e1xxxxxxxxxxxxxe12', 'xxxxxxxxxxxxxee', 'xxxxxxxxxxxxxe0', 'tuyaSmart', 'Europe'], 'id': '80410359', 'argsh': {}, 'PYTHONTYPE': 'tuya_cloud', 'FHEMPYTYPE': 'tuya_cloud', 'defargsh': {}, 'args': ['tuya_cloud_connector', '?'], 'NAME': 'tuya_cloud_connector', 'function': 'Set', 'msgtype': 'function', 'finished': 1, 'returnval': ''}
2023-02-06 22:59:57,644 - DEBUG - fhempy.lib.fhem: <<< 89171413: {'awaitId': 89171413, 'NAME': 'tuya_cloud_connector', 'msgtype': 'command', 'command': "AttrVal('tuya_cloud_connector', 'verbose', '3')"}
2023-02-06 22:59:57,657 - DEBUG - fhempy.lib.fhem: >>> 89171413 13.42ms: {'error': 0, 'awaitId': 89171413, 'result': '3'}
2023-02-06 22:59:57,671 - DEBUG - fhempy.lib.fhem: <<< 80742028: {'awaitId': 80742028, 'NAME': 'tuya_cloud_connector', 'msgtype': 'command', 'command': '$init_done'}
2023-02-06 22:59:57,685 - DEBUG - fhempy.lib.fhem: >>> 80742028 13.15ms: {'awaitId': 80742028, 'error': 0, 'result': 1}
2023-02-06 22:59:57,695 - DEBUG - fhempy.lib.fhem: <<< 82745635: {'awaitId': 82745635, 'NAME': 'tuya_cloud_connector', 'msgtype': 'command', 'command': "AttrVal('tuya_cloud_connector', 'room', '')"}
2023-02-06 22:59:57,709 - DEBUG - fhempy.lib.fhem: >>> 82745635 13.35ms: {'result': 'fhempy', 'awaitId': 82745635, 'error': 0}
2023-02-06 22:59:57,719 - DEBUG - fhempy.lib.fhem: <<< 22455893: {'awaitId': 22455893, 'NAME': 'tuya_cloud_connector', 'msgtype': 'command', 'command': "AttrVal('tuya_cloud_connector', 'group', '')"}
2023-02-06 22:59:57,732 - DEBUG - fhempy.lib.fhem: >>> 22455893 13.35ms: {'awaitId': 22455893, 'error': 0, 'result': 'tuya_cloud'}
2023-02-06 22:59:57,804 - DEBUG - fhempy.lib.fhem: <<< 52560252: {'awaitId': 52560252, 'NAME': 'tuya_cloud_connector', 'msgtype': 'command', 'command': "setDevAttrList('tuya_cloud_connector', ' IODev '.$readingFnAttributes)"}
2023-02-06 22:59:57,821 - DEBUG - fhempy.lib.fhem: >>> 52560252 16.81ms: {'awaitId': 52560252, 'error': 0, 'result': ' IODev:fhempy_local event-aggregator event-min-interval event-on-change-reading event-on-update-reading oldreadings stateFormat:textField-long timestamp-on-change-reading'}
2023-02-06 22:59:57,831 - DEBUG - fhempy.lib.fhem: <<< 88782319: {'awaitId': 88782319, 'NAME': 'tuya_cloud_connector', 'msgtype': 'command', 'command': "AttrVal('tuya_cloud_connector', 'verbose', '3')"}
2023-02-06 22:59:57,844 - DEBUG - fhempy.lib.fhem: >>> 88782319 13.08ms: {'awaitId': 88782319, 'error': 0, 'result': '3'}
2023-02-06 22:59:57,859 - DEBUG - fhempy.lib.fhem: <<< 85258269: {'awaitId': 85258269, 'NAME': 'tuya_cloud_connector', 'msgtype': 'command', 'command': "readingsSingleUpdate($defs{'tuya_cloud_connector'},'state','connecting',1)"}
2023-02-06 22:59:57,861 - DEBUG - fhempy.lib.fhem_pythonbinding: <<< WS: {"function": "Define", "msgtype": "update_hash", "NAME": "tuya_cloud_connector", "args": ["tuya_cloud_connector", "fhempy", "tuya_cloud", "setup", "5xxxxxxxxxxxxxeget", "e1xxxxxxxxxxxxxe12", "wxxxxxxxxxxxxxee", "Kxxxxxxxxxxxxxe0", "tuyaSmart", "Europe"], "defargsh": {}, "FHEMPYTYPE": "tuya_cloud", "PYTHONTYPE": "tuya_cloud", "argsh": {}, "defargs": ["tuya_cloud_connector", "fhempy", "tuya_cloud", "setup", "5xxxxxxxxxxxxxeet", "e1xxxxxxxxxxxxxe12", "wxxxxxxxxxxxxxee", "Kixxxxxxxxxxxxxe0", "tuyaSmart", "Europe"], "DEVICEID": 0}
2023-02-06 22:59:57,880 - DEBUG - fhempy.lib.fhem_pythonbinding: >>> 49718475: {'PYTHONTYPE': 'tuya_cloud', 'FHEMPYTYPE': 'tuya_cloud', 'defargsh': {}, 'args': ['tuya_cloud_connector', '?'], 'id': '49718475', 'defargs': ['tuya_cloud_connector', 'fhempy', 'tuya_cloud', 'setup', '5xxxxxxxxxxxxxxet', 'exxxxxxxxxxxxxe2', 'wxxxxxxxxxxxxxee', 'Kixxxxxxxxxxxxxe', 'tuyaSmart', 'Europe'], 'argsh': {}, 'msgtype': 'function', 'function': 'Set', 'NAME': 'tuya_cloud_connector'}
2023-02-06 22:59:57,889 - DEBUG - fhempy.lib.fhem_pythonbinding: <<< 49718475 8.73ms: {'PYTHONTYPE': 'tuya_cloud', 'FHEMPYTYPE': 'tuya_cloud', 'defargsh': {}, 'args': ['tuya_cloud_connector', '?'], 'id': '49718475', 'defargs': ['tuya_cloud_connector', 'fhempy', 'tuya_cloud', 'setup', '5xmvn7d9yt9crdfwfget', 'e1eca018ed9a415caa693cbe305ebe12', 'werner.schwetje@t-online.de', 'Kis$IW$1970', 'tuyaSmart', 'Europe'], 'argsh': {}, 'msgtype': 'function', 'function': 'Set', 'NAME': 'tuya_cloud_connector', 'finished': 1, 'returnval': 'Unknown argument ?, choose one of '}
2023-02-06 22:59:57,902 - DEBUG - fhempy.lib.fhem: >>> 85258269 43.15ms: {'error': 0, 'awaitId': 85258269, 'result': 'connecting'}
2023-02-06 22:59:57,922 - DEBUG - urllib3.connectionpool: Starting new HTTPS connection (1): openapi.tuyaeu.com:443
2023-02-06 22:59:58,256 - DEBUG - urllib3.connectionpool: https://openapi.tuyaeu.com:443 "POST /v1.0/iot-01/associated-users/actions/authorized-login HTTP/1.1" 200 112
2023-02-06 22:59:58,268 - DEBUG - fhempy.lib.fhem: <<< 83822785: {'awaitId': 83822785, 'NAME': 'tuya_cloud_connector', 'msgtype': 'command', 'command': "readingsSingleUpdate($defs{'tuya_cloud_connector'},'state','failed to login: {\\'code\\': 1106, \\'msg\\': \\'permission deny\\', \\'success\\': False, \\'t\\': 1675720798234, \\'tid\\': \\'98af4d4ca66911ed97b7f276006a160b\\'}',1)"}
2023-02-06 22:59:58,288 - DEBUG - fhempy.lib.fhem_pythonbinding: >>> 50533045: {'args': ['tuya_cloud_connector', '?'], 'defargsh': {}, 'FHEMPYTYPE': 'tuya_cloud', 'PYTHONTYPE': 'tuya_cloud', 'argsh': {}, 'defargs': ['tuya_cloud_connector', 'fhempy', 'tuya_cloud', 'setup', '5xxxxxxxxxxxxxeet', 'exxxxxxxxxxxxxe2', 'wxxxxxxxxxxxxxee', 'Kxxxxxxxxxxxxxe0', 'tuyaSmart', 'Europe'], 'id': '50533045', 'function': 'Set', 'msgtype': 'function', 'NAME': 'tuya_cloud_connector'}
2023-02-06 22:59:58,296 - DEBUG - fhempy.lib.fhem_pythonbinding: <<< 50533045 8.59ms: {'args': ['tuya_cloud_connector', '?'], 'defargsh': {}, 'FHEMPYTYPE': 'tuya_cloud', 'PYTHONTYPE': 'tuya_cloud', 'argsh': {}, 'defargs': ['tuya_cloud_connector', 'fhempy', 'tuya_cloud', 'setup', '5xxxxxxxxxxxxxeet', 'e1xxxxxxxxxxxxxe12', 'wxxxxxxxxxxxxxe', 'Kxxxxxxxxxxxxxe0', 'tuyaSmart', 'Europe'], 'id': '50533045', 'function': 'Set', 'msgtype': 'function', 'NAME': 'tuya_cloud_connector', 'finished': 1, 'returnval': 'Unknown argument ?, choose one of '}
2023-02-06 22:59:58,310 - DEBUG - fhempy.lib.fhem: >>> 83822785 41.57ms: {'result': "failed to login: {'code': 1106, 'msg': 'permission deny', 'success': False, 't': 1675720798234, 'tid': '98af4d4ca66911ed97b7f276006a160b'}", 'awaitId': 83822785, 'error': 0}
2023-02-06 22:59:58,317 - ERROR - tuya_cloud_connector: Tuya login error response: {'code': 1106, 'msg': 'permission deny', 'success': False, 't': 1675720798234, 'tid': '98af4d4ca66911ed97b7f276006a160b'}
2023-02-06 23:00:21,342 - DEBUG - fhempy.lib.fhem_pythonbinding: >>> 28827027: {'args': ['tuya_cloud_connector', '?'], 'defargsh': {}, 'FHEMPYTYPE': 'tuya_cloud', 'PYTHONTYPE': 'tuya_cloud', 'argsh': {}, 'id': '28827027', 'defargs': ['tuya_cloud_connector', 'fhempy', 'tuya_cloud', 'setup', '5xxxxxxxxxxxxxet', 'exxxxxxxxxxxxxe2', 'wxxxxxxxxxxxxxede', 'Kixxxxxxxxxxxxxe70', 'tuyaSmart', 'Europe'], 'msgtype': 'function', 'function': 'Set', 'NAME': 'tuya_cloud_connector'}
2023-02-06 23:00:21,351 - DEBUG - fhempy.lib.fhem_pythonbinding: <<< 28827027 8.65ms: {'args': ['tuya_cloud_connector', '?'], 'defargsh': {}, 'FHEMPYTYPE': 'tuya_cloud', 'PYTHONTYPE': 'tuya_cloud', 'argsh': {}, 'id': '28827027', 'defargs': ['tuya_cloud_connector', 'fhempy', 'tuya_cloud', 'setup', '5xxxxxxxxxxxxxeet', 'exxxxxxxxxxxxxe12', 'wxxxxxxxxxxxxxee', 'Kixxxxxxxxxxxxxe0', 'tuyaSmart', 'Europe'], 'msgtype': 'function', 'function': 'Set', 'NAME': 'tuya_cloud_connector', 'finished': 1, 'returnval': 'Unknown argument ?, choose one of '}
Viele Grüße
Werner
versuche es mal mit SmartLife
Es muss tuyaSmart heißen:
https://developer.tuya.com/en/docs/cloud/c40fc05907?id=Kawfjj0r2m82l
Wenns damit nicht geht, liegt das Problem wo anders. Eventuell credentials falsch? NICHT die tuya Cloud Credentials verwenden, sondern die von der Tuya Smart App.
@thburkhart, wegen der Fehler bin ich noch dran...das wird noch paar Tage dauern, sind paar grundlegende Fehler in fhempy die ich da beheben muss. Zum Glück hast du die gefunden ;) Ich brauch bitte auch noch paar Tage den Zugriff auf die Devices, da ich mit dieser Menge super testen kann.
Zitat von: dominik am 06 Februar 2023, 22:48:33
Es muss tuyaSmart heißen:
https://developer.tuya.com/en/docs/cloud/c40fc05907?id=Kawfjj0r2m82l
Wenns damit nicht geht, liegt das Problem wo anders. Eventuell credentials falsch? NICHT die tuya Cloud Credentials verwenden, sondern die von der Tuya Smart App.
Wo stelle ich die Credentials ein ?
Ich habe den Begriff hier im Zusammenhang mit fhempy noch nirgendwo gesehen.
In anderen Anwendungen kommt dann der Hinweis bad credentials.
Muss vielleicht im Tuya Projekt noch etwas eingestellt werden, was für die Kommunikation wichtig ist?
Auf Seite 58 unten hab ich noch mal den komplette Log für tuyaSmart zugefügt.
Viele Grüße
Werner
Werner
Credentials -> Username / Passwort
Es muss das von der App verwendet werden. Anheben tust du es im Define.
Hallo Dominik,
Im Define habe ich Username und Passwort von der App angegeben, wie in der Anleitung beschrieben.
Ich habe eine Bitte.
Kann ich Dir per EMail mein Define senden und Du probierst es auf Deinem Rechner aus.
Dann ist zumindest geklärt, ob im Projekt bei Tuya etwas geändert werden muss oder ob es an meinem fhem liegt.
Viele Grüße
Werner
Ja, kannst mir gern per PN schicken
Nachdem meine TUYA-Device wieder funktionieren wurde bei der Neuinstallation jetzt auf die Local-Variante umgestellt.
Zwar gibt es jetzt mehr Readings, dafür ist bei den Set-Befehlen nur noch on/off verfügbar. In der Cloud-Version hatte ich da zumindest noch Modus und Drehzahl oder Oszilation.
Kann man die Set-Befehle irgendwie erweitern, so dass die Readings auch wieder ausführbar sind?
Außerdem vermisse ich die Lüftergeschwindigkeit. Auf diese wird unten in den beiden Funktionen bei den Attributen verwiesen, aber unter den Readings nicht gelistet.
Außerdem hätte ich die Frage ob es irgendwie möglich ist, die Namen der Readings zu ändern. Im Moment lege ich die Readings mit UserReadings mit sprechendem Namen alle doppelt an. Schöner wäre es aber, wenn diese direkt einen sprechenden Namen hätten.
Zitat von: dominik am 07 Februar 2023, 08:23:40
Ja, kannst mir gern per PN schicken
Ich habe Dir eine Mitteilung geschrieben.
Viele Grüße
Werner
Zitat von: Superposchi am 07 Februar 2023, 11:31:52
Nachdem meine TUYA-Device wieder funktionieren wurde bei der Neuinstallation jetzt auf die Local-Variante umgestellt.
Zwar gibt es jetzt mehr Readings, dafür ist bei den Set-Befehlen nur noch on/off verfügbar. In der Cloud-Version hatte ich da zumindest noch Modus und Drehzahl oder Oszilation.
Kann man die Set-Befehle irgendwie erweitern, so dass die Readings auch wieder ausführbar sind?
Außerdem vermisse ich die Lüftergeschwindigkeit. Auf diese wird unten in den beiden Funktionen bei den Attributen verwiesen, aber unter den Readings nicht gelistet.
Außerdem hätte ich die Frage ob es irgendwie möglich ist, die Namen der Readings zu ändern. Im Moment lege ich die Readings mit UserReadings mit sprechendem Namen alle doppelt an. Schöner wäre es aber, wenn diese direkt einen sprechenden Namen hätten.
Bitte im tuya local Thread die Frage stellen. Hier geht es nur um Tuya Cloud (=fhempy tuya_cloud).
@thburkhart, teste bitte deine Devices mit der Version 0.1.594. Poste mir dann bitte jegliche Fehler aus den Logs (fhem und fhempy).
Hallo dominik,
danke für Deine Mitteilung.
Da ich die App immer online habe, ist mir nicht aufgefallen, dass man sich dort nicht mehr einloggen kann, warum auch immer.
Das Passwort hatte ich nicht verändert, da muss sich wohl mit der Einrichtung des Projektes etwas verändert haben.
Ich habe jetzt das gleiche Passwort in der App noch einmal gesetzt, jetzt funktioniert alles.
Vielen Dank für Deine Unterstützung
Viele Grüße
Werner
Zitat von: dominik am 08 Februar 2023, 22:39:47
@thburkhart, teste bitte deine Devices mit der Version 0.1.594. Poste mir dann bitte jegliche Fehler aus den Logs (fhem und fhempy).
ok
FHEM
2023.02.09 16:59:37 1: Downloading https://raw.githubusercontent.com/dominikkarall/fhempy/master/controls_pythonbinding.txt
2023.02.09 16:59:37 1: pythonbinding
2023.02.09 16:59:37 1: UPD FHEM/10_BindingsIo.pm
2023.02.09 16:59:37 1: saving fhem.cfg
2023.02.09 16:59:37 1: saving ./log/fhem.save
2023.02.09 16:59:37 1:
2023.02.09 16:59:37 1: New entries in the CHANGED file:
2023.02.09 16:59:37 1: See https://github.com/fhempy/fhempy/releases for details
2023.02.09 16:59:37 1:
2023.02.09 16:59:37 1:
2023.02.09 16:59:37 1: Downloading https://raw.githubusercontent.com/PatricSperling/FHEM_SST/master/controls_SST.txt
2023.02.09 16:59:37 1: SST
2023.02.09 16:59:38 1: nothing to do...
2023.02.09 16:59:38 1: Calling /usr/bin/perl ./contrib/commandref_modular.pl, this may take a while
2023.02.09 16:59:38 1:
2023.02.09 16:59:38 1: update finished, "shutdown restart" is needed to activate the changes.
2023.02.09 17:00:02 2: Deleting fhempy-2023-01-30.log
2023.02.09 17:00:49 1: [Freezemon] myFreezemon: possible freeze starting at 17:00:14, delay is 35.259 possibly caused by: no bad guy found :-(
2023.02.09 17:00:55 1: PERL WARNING: Wide character in print at ./FHEM/98_freezemon.pm line 1522.
2023.02.09 17:02:06 1: [Freezemon] myFreezemon: possible freeze starting at 17:01:58, delay is 8.497 possibly caused by: no bad guy found :-(
2023.02.09 17:16:38 2: Buderus : ERROR: Service: /heatSources/gasAirPressure: No proper Communication with Gateway: read from http://192.168.9.114:80 timed out
2023.02.09 17:17:05 1: [Freezemon] myFreezemon: possible freeze starting at 17:17:04, delay is 1.005 possibly caused by: no bad guy found :-(
2023.02.09 17:18:24 3: Watchdog WDT_HWR_F2 triggered
FHEMPY
2023-02-09 16:59:33,632 - WARNING - asyncio: socket.send() raised exception.
2023-02-09 16:59:37,925 - WARNING - asyncio: socket.send() raised exception.
2023-02-09 16:59:37,931 - WARNING - asyncio: socket.send() raised exception.
2023-02-09 16:59:38,095 - WARNING - asyncio: socket.send() raised exception.
2023-02-09 16:59:38,452 - WARNING - asyncio: socket.send() raised exception.
2023-02-09 16:59:38,455 - WARNING - asyncio: socket.send() raised exception.
2023-02-09 16:59:38,458 - WARNING - asyncio: socket.send() raised exception.
2023-02-09 16:59:38,573 - INFO - fhempy.lib.fhem_pythonbinding: Start update...
2023-02-09 16:59:38,574 - INFO - fhempy.lib.pkg_installer: Attempting install of fhempy
2023-02-09 16:59:43,107 - WARNING - asyncio: socket.send() raised exception.
2023-02-09 16:59:43,464 - WARNING - asyncio: socket.send() raised exception.
2023-02-09 16:59:43,469 - WARNING - asyncio: socket.send() raised exception.
2023-02-09 16:59:43,473 - WARNING - asyncio: socket.send() raised exception.
2023-02-09 16:59:43,571 - WARNING - asyncio: socket.send() raised exception.
2023-02-09 16:59:43,574 - WARNING - asyncio: socket.send() raised exception.
2023-02-09 16:59:47,939 - WARNING - asyncio: socket.send() raised exception.
2023-02-09 16:59:47,943 - WARNING - asyncio: socket.send() raised exception.
2023-02-09 16:59:48,120 - WARNING - asyncio: socket.send() raised exception.
2023-02-09 16:59:48,479 - WARNING - asyncio: socket.send() raised exception.
2023-02-09 16:59:48,483 - WARNING - asyncio: socket.send() raised exception.
2023-02-09 16:59:48,487 - WARNING - asyncio: socket.send() raised exception.
2023-02-09 16:59:52,045 - INFO - fhempy.lib.pkg_installer: Successfully installed fhempy update!
2023-02-09 16:59:52,106 - INFO - fhempy.lib.fhem_pythonbinding: Restart initiated...
2023-02-09 16:59:52,311 - INFO - fhempy.lib.fhem_pythonbinding: All modules successfully undefined!
2023-02-09 16:59:52,312 - INFO - websockets.server: server closing
2023-02-09 17:00:02,315 - INFO - websockets.server: connection closed
2023-02-09 17:00:02,315 - INFO - websockets.server: server closed
2023-02-09 17:00:02,318 - INFO - fhempy.lib.fhem_pythonbinding: Exit 1
2023-02-09 17:00:03,587 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.595...
2023-02-09 17:00:03,591 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-02-09 17:00:03,620 - INFO - websockets.server: server listening on 0.0.0.0:15733
2023-02-09 17:00:13,015 - INFO - websockets.server: connection open
2023-02-09 17:00:13,016 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2023-02-09 17:00:16,396 - ERROR - TUYA: Please activate OpenPulsar: https://developer.tuya.com/en/docs/iot/subscribe-mq?id=Kavqcrvckbh9h
in den Logs ist also fast Ruhe
was ist Pulsar?
jetzt nach gut 30 min antwortetet room fhempy nach rund 40 sec
weiteres Testergebnis:
Device erst kürzlich über tuya_cloud eingelesen: (doppelt)
[code]define tuya_cloud_453005615002911dfe06 fhempy tuya_cloud TUYA 453005615002911dfe06
attr tuya_cloud_453005615002911dfe06 DbLogExclude .*
attr tuya_cloud_453005615002911dfe06 alias Heizdecke 2 (c)
attr tuya_cloud_453005615002911dfe06 event-on-change-reading .*
attr tuya_cloud_453005615002911dfe06 group Schalter (T),Schalter Heizgeräte
attr tuya_cloud_453005615002911dfe06 room fhempy
# DEF tuya_cloud TUYA 453005615002911dfe06
# DEVICEID 453005615002911dfe06
# FHEMPYTYPE tuya_cloud
# FUUID 63dfbaa7-f33f-fd5f-77e2-78d57c6e3f7d09db
# IODev local_pybinding
# NAME tuya_cloud_453005615002911dfe06
# NR 2334
# PYTHONTYPE tuya_cloud
# STATE on
# TYPE fhempy
# eventCount 7297
# READINGS:
# 2023-02-09 17:01:08 active_time 1606402887
# 2023-02-09 17:01:22 add_ele 10.0
# 2023-02-09 17:01:08 biz_type 18
# 2023-02-09 17:01:08 category cz
# 2023-02-09 17:01:22 countdown_1 0.0
# 2023-02-09 17:01:08 create_time 1606402887
# 2023-02-09 17:01:22 cur_current 0.0
# 2023-02-09 17:01:22 cur_power 0.0
# 2023-02-09 17:01:22 cur_voltage 2316.0
# 2023-02-09 17:01:08 icon https://images.tuyaeu.com/smart/device_icon/eu1548823829280mLHX1/453005615002911dfe06163417957708355.png
# 2023-02-09 17:01:08 id 453005615002911dfe06
# 2023-02-09 17:01:08 ip 46.5.205.127
# 2023-02-09 17:01:08 lat 48.5585
# 2023-02-09 17:01:08 local_key db41567569a265b4
# 2023-02-09 17:01:08 lon 9.2026
# 2023-02-09 17:01:08 name Heizkissen 2
# 2023-02-09 17:01:08 online on
# 2023-02-09 17:01:08 owner_id 3389434
# 2023-02-09 17:01:08 product_id wifvoilfrqeo6hvu
# 2023-02-09 17:01:08 product_name Smart Socket
# 2023-02-09 17:01:22 state on
# 2023-02-09 17:01:08 sub off
# 2023-02-05 17:03:22 switch_1 on
# 2023-02-09 17:01:08 time_zone +01:00
# 2023-02-09 17:01:08 uid eu1548823829280mLHX1
# 2023-02-09 17:01:08 update_time 1645653695
# 2023-02-09 17:01:08 uuid 453005615002911dfe06
# args:
# tuya_cloud_453005615002911dfe06
# fhempy
# tuya_cloud
# TUYA
# 453005615002911dfe06
# argsh:
# helper:
# bm:
# fhempy_Get:
# cnt 3
# dmx -1000
# dtot 0
# dtotcnt 0
# mTS 09.02. 17:42:22
# max 0.106812953948975
# tot 0.116453886032104
# mAr:
# HASH(0x5378758)
# ARRAY(0x64b44e0)
# HASH(0x6ee0d90)
# fhempy_Set:
# cnt 7336
# dmx -1000
# dtot 0
# dtotcnt 0
# mTS 08.02. 16:54:54
# max 1.18356585502625
# tot 315.876584768295
# mAr:
# HASH(0x5378758)
# ARRAY(0x55905e8)
# HASH(0x57ed298)
#
setstate tuya_cloud_453005615002911dfe06 on
setstate tuya_cloud_453005615002911dfe06 2023-02-09 17:01:08 active_time 1606402887
setstate tuya_cloud_453005615002911dfe06 2023-02-09 17:01:22 add_ele 10.0
setstate tuya_cloud_453005615002911dfe06 2023-02-09 17:01:08 biz_type 18
setstate tuya_cloud_453005615002911dfe06 2023-02-09 17:01:08 category cz
setstate tuya_cloud_453005615002911dfe06 2023-02-09 17:01:22 countdown_1 0.0
setstate tuya_cloud_453005615002911dfe06 2023-02-09 17:01:08 create_time 1606402887
setstate tuya_cloud_453005615002911dfe06 2023-02-09 17:01:22 cur_current 0.0
setstate tuya_cloud_453005615002911dfe06 2023-02-09 17:01:22 cur_power 0.0
setstate tuya_cloud_453005615002911dfe06 2023-02-09 17:01:22 cur_voltage 2316.0
setstate tuya_cloud_453005615002911dfe06 2023-02-09 17:01:08 icon https://images.tuyaeu.com/smart/device_icon/eu1548823829280mLHX1/453005615002911dfe06163417957708355.png
setstate tuya_cloud_453005615002911dfe06 2023-02-09 17:01:08 id 453005615002911dfe06
setstate tuya_cloud_453005615002911dfe06 2023-02-09 17:01:08 ip 46.5.205.127
setstate tuya_cloud_453005615002911dfe06 2023-02-09 17:01:08 lat 48.5585
setstate tuya_cloud_453005615002911dfe06 2023-02-09 17:01:08 local_key db41567569a265b4
setstate tuya_cloud_453005615002911dfe06 2023-02-09 17:01:08 lon 9.2026
setstate tuya_cloud_453005615002911dfe06 2023-02-09 17:01:08 name Heizkissen 2
setstate tuya_cloud_453005615002911dfe06 2023-02-09 17:01:08 online on
setstate tuya_cloud_453005615002911dfe06 2023-02-09 17:01:08 owner_id 3389434
setstate tuya_cloud_453005615002911dfe06 2023-02-09 17:01:08 product_id wifvoilfrqeo6hvu
setstate tuya_cloud_453005615002911dfe06 2023-02-09 17:01:08 product_name Smart Socket
setstate tuya_cloud_453005615002911dfe06 2023-02-09 17:01:22 state on
setstate tuya_cloud_453005615002911dfe06 2023-02-09 17:01:08 sub off
setstate tuya_cloud_453005615002911dfe06 2023-02-05 17:03:22 switch_1 on
setstate tuya_cloud_453005615002911dfe06 2023-02-09 17:01:08 time_zone +01:00
setstate tuya_cloud_453005615002911dfe06 2023-02-09 17:01:08 uid eu1548823829280mLHX1
setstate tuya_cloud_453005615002911dfe06 2023-02-09 17:01:08 update_time 1645653695
setstate tuya_cloud_453005615002911dfe06 2023-02-09 17:01:08 uuid 453005615002911dfe06
[/code]
entsprechend local: JL19
[code]define TUYA_JL19 fhempy tuya wifvoilfrqeo6hvu 5062137624a1600b6d62 192.168.9.54 d029f7f52f9fbec5 3.3 ea8453wdazquzfl08l0e 8a4b27dd759d4c6a9456aa8155d2a0ea
attr TUYA_JL19 DbLogExclude .*
attr TUYA_JL19 alias JL19 Heizkissen 2
attr TUYA_JL19 dp_01 switch_1
attr TUYA_JL19 dp_02 countdown_1
attr TUYA_JL19 dp_03 add_ele
attr TUYA_JL19 dp_04 cur_current
attr TUYA_JL19 dp_05 cur_power
attr TUYA_JL19 dp_06 cur_voltage
attr TUYA_JL19 group Schalter (T),Schalter Heizgeräte
attr TUYA_JL19 room fhempy
attr TUYA_JL19 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_JL19 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 5062137624a1600b6d62 192.168.9.54 d029f7f52f9fbec5 3.3 ea8453wdazquzfl08l0e 8a4b27dd759d4c6a9456aa8155d2a0ea
# DEVICEID 5062137624a1600b6d62
# FHEMPYTYPE tuya
# FUUID 63a4a46a-f33f-fd5f-4d1f-832bcfc39f19af8e
# IODev local_pybinding
# NAME TUYA_JL19
# NR 1732
# PYTHONTYPE tuya
# STATE ready
# TYPE fhempy
# eventCount 6
# READINGS:
# 2023-02-09 17:00:31 online 1
# 2023-02-09 17:00:31 state ready
# args:
# TUYA_JL19
# fhempy
# tuya
# wifvoilfrqeo6hvu
# 5062137624a1600b6d62
# 192.168.9.54
# d029f7f52f9fbec5
# 3.3
# ea8453wdazquzfl08l0e
# 8a4b27dd759d4c6a9456aa8155d2a0ea
# argsh:
# helper:
# bm:
# fhempy_Get:
# cnt 1
# dmx -1000
# dtot 0
# dtotcnt 0
# mTS 09.02. 17:49:33
# max 0.00241613388061523
# tot 0.00241613388061523
# mAr:
# HASH(0x525e148)
# ARRAY(0x7292978)
# HASH(0x6df25d0)
# fhempy_Set:
# cnt 44
# dmx -1000
# dtot 0
# dtotcnt 0
# mTS 09.02. 17:00:21
# max 0.855268955230713
# tot 3.79341268539429
# mAr:
# HASH(0x525e148)
# ARRAY(0x662ff40)
# HASH(0x6637c28)
#
setstate TUYA_JL19 ready
setstate TUYA_JL19 2023-02-09 17:00:31 online 1
setstate TUYA_JL19 2023-02-09 17:00:31 state ready
[/code]
device vor längerem per tuya_local eingelesen:
[code]define TUYA_JL02 fhempy tuya 1hxNMF9lRQL2xpEA 2223080884f3eb466414 192.168.9.75 824ea2c9d41a3ec1 3.1 ea8453wdazquzfl08l0e 8a4b27dd759d4c6a9456aa8155d2a0ea
attr TUYA_JL02 DbLogExclude .*
attr TUYA_JL02 alias JL02 Kaffeemaschine Saecco
attr TUYA_JL02 dp_01 switch
attr TUYA_JL02 dp_02 countdown_1
attr TUYA_JL02 dp_04 cur_current
attr TUYA_JL02 dp_05 cur_power
attr TUYA_JL02 dp_06 cur_voltage
attr TUYA_JL02 group Schalter (T),Schalter diverse
attr TUYA_JL02 room Küche,fhempy
attr TUYA_JL02 tuya_spec_functions [{'code': 'switch', 'dp_id': 1, 'type': 'Boolean', 'values': {}, 'desc': 'switch'}, {'code': 'countdown_1', 'dp_id': 2, 'type': 'Integer', 'values': {'unit': 's', 'min': 0, 'max': 86400, 'scale': 0, 'step': 1}, 'desc': 'countdown 1'}]
attr TUYA_JL02 tuya_spec_status [{'code': 'switch', 'dp_id': 1, 'type': 'Boolean', 'values': {}}, {'code': 'cur_current', 'dp_id': 4, 'type': 'Integer', 'values': {'unit': 'mA', 'min': 0, 'max': 30000, 'scale': 0, 'step': 1}}, {'code': 'cur_power', 'dp_id': 5, 'type': 'Integer', 'values': {'unit': 'W', 'min': 0, 'max': 50000, 'scale': 1, 'step': 1}}, {'code': 'cur_voltage', 'dp_id': 6, 'type': 'Integer', 'values': {'unit': 'V', 'min': 0, 'max': 5000, 'scale': 1, 'step': 1}}, {'code': 'countdown_1', 'dp_id': 2, 'type': 'Integer', 'values': {'unit': 's', 'min': 0, 'max': 86400, 'scale': 0, 'step': 1}}]
# DEF tuya 1hxNMF9lRQL2xpEA 2223080884f3eb466414 192.168.9.75 824ea2c9d41a3ec1 3.1 ea8453wdazquzfl08l0e 8a4b27dd759d4c6a9456aa8155d2a0ea
# DEVICEID 2223080884f3eb466414
# FHEMPYTYPE tuya
# FUUID 63a35f65-f33f-fd5f-5f31-dcf38dfd2d56f436
# IODev local_pybinding
# NAME TUYA_JL02
# NR 1698
# PYTHONTYPE tuya
# STATE off
# TYPE fhempy
# eventCount 7261
# READINGS:
# 2023-02-06 16:32:29 countdown_1 0.0
# 2023-02-09 16:35:30 cur_current 0.0
# 2023-02-09 16:35:30 cur_power 0.0
# 2023-02-09 17:39:26 cur_voltage 222.8
# 2023-02-09 17:00:18 online 1
# 2023-02-09 17:00:28 state off
# 2023-02-09 17:00:20 switch off
# args:
# TUYA_JL02
# fhempy
# tuya
# 1hxNMF9lRQL2xpEA
# 2223080884f3eb466414
# 192.168.9.75
# 824ea2c9d41a3ec1
# 3.1
# ea8453wdazquzfl08l0e
# 8a4b27dd759d4c6a9456aa8155d2a0ea
# argsh:
# helper:
# bm:
# fhempy_Get:
# cnt 2
# dmx -1000
# dtot 0
# dtotcnt 0
# mTS 09.02. 17:37:31
# max 0.101494073867798
# tot 0.104123115539551
# mAr:
# HASH(0x523ebb8)
# ARRAY(0x6c384c8)
# HASH(0x6f1a570)
# fhempy_Set:
# cnt 7316
# dmx -1000
# dtot 0
# dtotcnt 0
# mTS 08.02. 21:08:23
# max 0.917642116546631
# tot 379.338533878326
# mAr:
# HASH(0x523ebb8)
# ARRAY(0x67137d8)
# HASH(0x696dfe8)
#
setstate TUYA_JL02 off
setstate TUYA_JL02 2023-02-06 16:32:29 countdown_1 0.0
setstate TUYA_JL02 2023-02-09 16:35:30 cur_current 0.0
setstate TUYA_JL02 2023-02-09 16:35:30 cur_power 0.0
setstate TUYA_JL02 2023-02-09 17:39:26 cur_voltage 222.8
setstate TUYA_JL02 2023-02-09 17:00:18 online 1
setstate TUYA_JL02 2023-02-09 17:00:28 state off
setstate TUYA_JL02 2023-02-09 17:00:20 switch off
[/code]
7 readings
eine Stunde später:
JL31 tauch local nochmals auf..
2023.02.09 17:51:22 3: Untergeschoss_Rollo_1_down_Notify return value: OK
2023.02.09 17:51:24 3: Obergeschoss_Rollo_1_down_Notify return value: OK
2023.02.09 17:51:26 3: Wohnzimmer_Rollo_1_down_Notify return value: OK
2023.02.09 17:51:28 3: Wohnzimmer_Rollo_3_down_Notify return value: OK
2023.02.09 17:51:28 1: [Freezemon] myFreezemon: possible freeze starting at 17:51:20, delay is 8.969 possibly caused by: tmr-BlockingKill(N/A) tmr-at_Exec(Untergeschoss_Rollo_1_bei_Sonnenuntergang_runter_AT) tmr-at_Exec(Obergeschoss_Rollo_1_bei_Sonnenuntergang_runter_AT) tmr-at_Exec(Wohnzimmer_Rollo_1_bei_Sonnenuntergang_runter_AT) tmr-at_Exec(Wohnzimmer_Rollo_3_bei_Sonnenuntergang_runter_AT)
2023.02.09 17:57:22 1: [Freezemon] myFreezemon: possible freeze starting at 17:57:18, delay is 4.923 possibly caused by: no bad guy found :-(
passend zu JL31 doppelt:
2023-02-09 16:59:48,479 - WARNING - asyncio: socket.send() raised exception.
2023-02-09 16:59:48,483 - WARNING - asyncio: socket.send() raised exception.
2023-02-09 16:59:48,487 - WARNING - asyncio: socket.send() raised exception.
2023-02-09 16:59:52,045 - INFO - fhempy.lib.pkg_installer: Successfully installed fhempy update!
2023-02-09 16:59:52,106 - INFO - fhempy.lib.fhem_pythonbinding: Restart initiated...
2023-02-09 16:59:52,311 - INFO - fhempy.lib.fhem_pythonbinding: All modules successfully undefined!
2023-02-09 16:59:52,312 - INFO - websockets.server: server closing
2023-02-09 17:00:02,315 - INFO - websockets.server: connection closed
2023-02-09 17:00:02,315 - INFO - websockets.server: server closed
2023-02-09 17:00:02,318 - INFO - fhempy.lib.fhem_pythonbinding: Exit 1
2023-02-09 17:00:03,587 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.595...
2023-02-09 17:00:03,591 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-02-09 17:00:03,620 - INFO - websockets.server: server listening on 0.0.0.0:15733
2023-02-09 17:00:13,015 - INFO - websockets.server: connection open
2023-02-09 17:00:13,016 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2023-02-09 17:00:16,396 - ERROR - TUYA: Please activate OpenPulsar: https://developer.tuya.com/en/docs/iot/subscribe-mq?id=Kavqcrvckbh9h
2023-02-09 17:51:29,356 - ERROR - fhempy.lib.fhem: FHEM took 9205ms for readingsBeginUpdate($defs{'TUYA_SP13'});;
2023-02-09 17:51:29,357 - ERROR - fhempy.lib.fhem: FHEM took 9089ms for readingsBeginUpdate($defs{'TUYA_JL04'});;
2023-02-09 17:51:29,359 - ERROR - fhempy.lib.fhem: FHEM took 8830ms for readingsBeginUpdate($defs{'TUYA_EMYLO2'});;
2023-02-09 17:51:29,361 - ERROR - fhempy.lib.fhem: FHEM took 8722ms for readingsBeginUpdate($defs{'TUYA_SP16'});;
2023-02-09 17:51:29,364 - ERROR - fhempy.lib.fhem: FHEM took 8610ms for readingsBeginUpdate($defs{'TUYA_JL02'});;
2023-02-09 17:51:29,366 - ERROR - fhempy.lib.fhem: FHEM took 8491ms for readingsBeginUpdate($defs{'TUYA_EMYLO4'});;
2023-02-09 17:51:29,367 - ERROR - fhempy.lib.fhem: FHEM took 8353ms for readingsBeginUpdate($defs{'TUYA_JL33'});;
2023-02-09 17:51:29,370 - ERROR - fhempy.lib.fhem: FHEM took 7735ms for readingsBeginUpdate($defs{'TUYA_SP15'});;
2023-02-09 17:51:29,371 - ERROR - fhempy.lib.fhem: FHEM took 7732ms for readingsBeginUpdate($defs{'TUYA_EMYLO3'});;
2023-02-09 17:51:29,373 - ERROR - fhempy.lib.fhem: FHEM took 7732ms for readingsBeginUpdate($defs{'TUYA_EMYLO1'});;
2023-02-09 17:51:29,375 - ERROR - fhempy.lib.fhem: FHEM took 7623ms for readingsBeginUpdate($defs{'TUYA_DIY1'});;
2023-02-09 17:51:29,377 - ERROR - fhempy.lib.fhem: FHEM took 7624ms for readingsBeginUpdate($defs{'TUYA_DIY3'});;
2023-02-09 17:51:29,379 - ERROR - fhempy.lib.fhem: FHEM took 7625ms for readingsBeginUpdate($defs{'TUYA_DIY4'});;
2023-02-09 17:51:29,381 - ERROR - fhempy.lib.fhem: FHEM took 7627ms for readingsBeginUpdate($defs{'TUYA_BULB02'});;
2023-02-09 17:51:29,382 - ERROR - fhempy.lib.fhem: FHEM took 7629ms for readingsBeginUpdate($defs{'TUYA_JL31'});;
2023-02-09 17:51:29,383 - ERROR - fhempy.lib.fhem: FHEM took 7519ms for readingsBeginUpdate($defs{'TUYA_JL15'});;
2023-02-09 17:51:29,385 - ERROR - fhempy.lib.fhem: FHEM took 7520ms for readingsBeginUpdate($defs{'TUYA_SP11'});;
2023-02-09 17:51:29,386 - ERROR - fhempy.lib.fhem: FHEM took 7401ms for readingsBeginUpdate($defs{'TUYA_JL29'});;
2023-02-09 17:51:29,491 - ERROR - fhempy.lib.fhem: FHEM took 6906ms for readingsBeginUpdate($defs{'TUYA_SP05'});;
2023-02-09 17:51:29,492 - ERROR - fhempy.lib.fhem: FHEM took 6531ms for readingsBeginUpdate($defs{'TUYA_JL06'});;
2023-02-09 17:51:29,492 - ERROR - fhempy.lib.fhem: FHEM took 6529ms for readingsBeginUpdate($defs{'TUYA_JL07'});;
2023-02-09 17:51:29,493 - ERROR - fhempy.lib.fhem: FHEM took 5822ms for readingsBeginUpdate($defs{'TUYA_JL08'});;
2023-02-09 17:51:29,494 - ERROR - fhempy.lib.fhem: FHEM took 5805ms for readingsBeginUpdate($defs{'TUYA_JL09'});;
2023-02-09 17:51:29,495 - ERROR - fhempy.lib.fhem: FHEM took 5791ms for readingsBeginUpdate($defs{'TUYA_JL13'});;
2023-02-09 17:51:29,496 - ERROR - fhempy.lib.fhem: FHEM took 5543ms for readingsBeginUpdate($defs{'TUYA_JL11Z'});;
2023-02-09 17:51:29,498 - ERROR - fhempy.lib.fhem: FHEM took 5043ms for readingsBeginUpdate($defs{'TUYA_JL24'});;
2023-02-09 18:00:18,018 - ERROR - fhempy.lib.fhem: NO RESPONSE since 180s: readingsBulkUpdateIfChanged($defs{'TUYA_JL31'},'online','1');;
zusammenhang mit rollos?
Nachtrag:
JL31 war eingesteckt !!
Fehhlermeldung s.o.
2023-02-09 18:00:18,018 - ERROR - fhempy.lib.fhem: NO RESPONSE since 180s: readingsBulkUpdateIfChanged($defs{'TUYA_JL31'},'online','1');;
jedoch enthält das neue DEF alle readings aber natürlioch nich die alten groups und rooms
kann es sein, dass fhempy nun die bestehenden local-DEFs nicht komplett updated?? (falls es sie findet)
Hast du auch ein fhem update gemacht? Bitte das auch noch machen und restart.
Zitat von: dominik am 09 Februar 2023, 19:00:12
Hast du auch ein fhem update gemacht? Bitte das auch noch machen und restart.
hatte ich 17:58 gemacht
Ich seh um 17:58 aber keinen fhempy restart?
Lösche bitte nochmals die doppelten Devices manuell und dann mach einen shutdown restart. Poste dann wieder die Logs bitte.
ich habe nun die doppelten devices entfernt.
und ca 14:00 FEHM shutdown restart gemacht:
fhem-log:
2023.02.10 14:00:06 2: Buderus : ERROR: Service: /gateway/DateTime: No proper Communication with Gateway: read from http://192.168.9.114:80 timed out
2023.02.10 14:00:26 1: PERL WARNING: Argument "xxxx xxxx" isn't numeric in numeric eq (==) at ./FHEM/33_readingsGroup.pm line 1177.
2023.02.10 14:02:40 2: DbLog dblog_THB - Wait for last database cycle due to shutdown ...
2023.02.10 14:02:40 1: Server shutdown delayed due to dblog_THB,alexa for max 10 sec
2023.02.10 14:02:40 2: DbLog dblog_THB - Last database write cycle done
2023.02.10 14:02:42 3: alexa: read: end of file reached while sysread
2023.02.10 14:02:42 3: alexa: stopped
2023.02.10 14:02:42 0: Server shutdown
2023.02.10 14:02:42 2: DbLog dblog_THB - stopping SubProcess PID >16992< ...
2023.02.10 14:02:42 2: DbLog dblog_THB - SubProcess PID >16992< stopped
2023.02.10 14:02:44 1: Including fhem.cfg
2023.02.10 14:02:45 2: DbLog dblog_THB - Subprocess >17898< initialized ... ready for non-blocking operation
2023.02.10 14:02:46 3: telnetPort: port 7072 opened
2023.02.10 14:02:46 3: WEB: port 8083 opened
2023.02.10 14:02:46 3: WEBphone: port 8084 opened
2023.02.10 14:02:46 3: WEBtablet: port 8085 opened
2023.02.10 14:02:46 3: TelegramBot_Define TelegramBotTHB: called
2023.02.10 14:02:47 3: BindingsIo v1.0.1
2023.02.10 14:02:47 3: fhempyServer v1.0.0
2023.02.10 14:02:47 3: fhempy v1.0.0 (tuya_cloud: TUYA)
2023.02.10 14:02:47 3: fhempy v1.0.0 (tuya: tuya_system)
2023.02.10 14:02:47 3: Opening CUL_0 device /dev/ttyACM0
2023.02.10 14:02:47 3: Setting CUL_0 serial parameters to 9600,8,N,1
2023.02.10 14:02:47 3: CUL_0: Possible commands: BbCFiAZNkGMKUYRTVWXefmLltux
2023.02.10 14:02:47 3: CUL_0 device opened
2023.02.10 14:02:47 2: Switched CUL_0 rfmode to MAX
2023.02.10 14:02:47 3: Opening JLLaCR device /dev/ttyUSB0
2023.02.10 14:02:47 3: Setting JLLaCR serial parameters to 57600,8,N,1
2023.02.10 14:02:48 3: JLLaCR device opened
2023.02.10 14:02:48 1: PERL WARNING: Use of uninitialized value in numeric ge (>=) at ./FHEM/12_OilFox.pm line 387, <$fh> line 562.
2023.02.10 14:02:48 2: LOGIN TOKEN MISSING OR EXPIRED
2023.02.10 14:02:48 3: myOilFox - email set to bkt@gmx.net
2023.02.10 14:02:48 3: myOilFox - set interval: 36000
2023.02.10 14:02:48 3: myOilFox - password set to thbbkt25
2023.02.10 14:02:48 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.10 14:03:04 2: eventTypes: loaded 16333 lines from ./log/eventTypes.txt
2023.02.10 14:03:04 3: TX29_00: I/O device is JLLaCR
2023.02.10 14:03:04 3: TX29DTH_01: I/O device is JLLaCR
2023.02.10 14:03:04 3: TX29DTH_02: I/O device is JLLaCR
2023.02.10 14:03:04 3: TX29DTH_03: I/O device is JLLaCR
2023.02.10 14:03:04 3: TX29DTH_04: I/O device is JLLaCR
2023.02.10 14:03:04 3: TX29DTH_05: I/O device is JLLaCR
2023.02.10 14:03:04 3: TX29DTH_06: I/O device is JLLaCR
2023.02.10 14:03:04 3: TX29DTH_07: I/O device is JLLaCR
2023.02.10 14:03:04 3: TX29DTH_08: I/O device is JLLaCR
2023.02.10 14:03:04 3: TX29DTH_09: I/O device is JLLaCR
2023.02.10 14:03:04 3: TX29DTH_10: I/O device is JLLaCR
2023.02.10 14:03:04 3: TX29DTH_11: I/O device is JLLaCR
2023.02.10 14:03:04 3: TX29DTH_12: I/O device is JLLaCR
2023.02.10 14:03:04 3: TX25IT_13: I/O device is JLLaCR
2023.02.10 14:03:04 3: TX29DTH_14: I/O device is JLLaCR
2023.02.10 14:03:04 3: TX29DTH_15: I/O device is JLLaCR
2023.02.10 14:03:04 3: TX29DTH_16: I/O device is JLLaCR
2023.02.10 14:03:04 3: TX29DTH_17: I/O device is JLLaCR
2023.02.10 14:03:04 3: TX29DTH_18: I/O device is JLLaCR
2023.02.10 14:03:04 3: TX29DTH_19: I/O device is JLLaCR
2023.02.10 14:03:04 3: TX29DTH_20: I/O device is JLLaCR
2023.02.10 14:03:04 3: TX29DTH_21: I/O device is JLLaCR
2023.02.10 14:03:04 3: TX29DTH_22: I/O device is JLLaCR
2023.02.10 14:03:04 3: HUEDevice2: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice4: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice5: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice6: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice7: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice8: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice10: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice17: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice18: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice19: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice20: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice22: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice23: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice24: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice25: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice27: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice28: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice29: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice30: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice31: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice32: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice33: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice38: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice39: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice40: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice41: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup0: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup1: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup2: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup3: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup4: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup5: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup6: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup7: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup8: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup9: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup10: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup11: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup12: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup13: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup14: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup15: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup16: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup17: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup18: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup19: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup20: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup21: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup22: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup23: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup24: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup25: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup26: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup27: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup28: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup29: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup30: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice44: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEGroup31: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUESensor6: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUESensor8: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUESensor10: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUESensor13: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUESensor24: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUESensor27: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUESensor34: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUESensor37: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUESensor45: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice45: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice46: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice47: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice48: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice49: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice50: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice51: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUESensor91: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUESensor110: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUESensor1: I/O device is hueBridge1
2023.02.10 14:03:04 3: HUEDevice52: I/O device is hueBridge1
2023.02.10 14:03:04 1: MaxTemp: WT
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_BULB01)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_BULB02)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya_cloud: TUYA_BULB03)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Camera1)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Camera2)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Camera3)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya_cloud: Camera4tuya_cloud_bf6b1900c331a78a2fkecw)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya_cloud: Camera5tuya_cloud_bfbeab33da30f5635ffj0r)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Camera6)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_DIY1)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_DIY3)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_DIY4)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_EMYLO1)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_EMYLO2)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_EMYLOD2)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_EMYLO3)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_EMYLO4)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL02)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL03)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL04)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL05)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL06)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL07)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL08)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL09)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL10Z)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL11Z)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL12Z)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL13)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL14)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL15)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL16)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL17)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL18)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya_cloud: TUYAC_JL19)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL20)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL21)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL22)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL23)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL24)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya_cloud: TUYA_JL25)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL26)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL27)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL28)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL29)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL30)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL31)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL32)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL33)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL34)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL35)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_JL36)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_PS1)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_PS2)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_PS3)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_PS4)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_PS5)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_PS7)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_SCHF1)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_SCHF2)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_SCHF3)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_SP01)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_SP02)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_SP03)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_SP04)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_SP05)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_SP06)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_SP07)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_SP08)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_SP09)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_SP10)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_SP11)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_SP12)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_SP13)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_SP14)
2023.02.10 14:03:05 3: fhempy v1.0.0 (tuya: TUYA_SP15)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya: TUYA_SP16)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya_cloud: TUYAC_PIR01)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya_cloud: TUYAC_PIR02)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya_cloud: TUYAC_PIR03)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorT01)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorT02)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorT03)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorT04)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorT05)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorW01)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorW02)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorW03)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorW04)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Sir01)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Sir02)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Sir03)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Relais01)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorSmoke01)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya: TUYA_STF1)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya: TUYA_STF2)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya: TUYA_STF3)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya: TUYA_MMG)
2023.02.10 14:03:06 3: SST (SamsungSmartThingsConnector): define - CONNECTOR defined as SamsungSmartThingsConnector
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp01)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp02)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp03)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp04)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp05)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp06)
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp07)
2023.02.10 14:03:06 1: PERL WARNING: Useless use of anonymous hash ({}) in void context at (eval 128) line 1, <$fh> line 6381.
2023.02.10 14:03:06 3: fhempy v1.0.0 (tuya_cloud: TUYA_SCHFF4)
2023.02.10 14:03:06 1: Including ./log/fhem.save
2023.02.10 14:03:06 1: Messages collected while initializing FHEM:SecurityCheck:
WEB is not password protected
WEBphone is not password protected
telnetPort is not password protected
WEBtablet 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.10 14:03:07 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2023.02.10 14:03:07 3: alexa: starting
2023.02.10 14:03:07 3: alexa: using logfile: ./log/alexa-2023-02-10.log
2023.02.10 14:03:07 2: hueBridge1: autocreate: created 0/0/0 devices (ignored 0/2/26)
2023.02.10 14:03:09 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2023.02.10 14:03:09 0: Featurelevel: 6.2
2023.02.10 14:03:09 0: Server started with 512 defined entities (fhem.pl:27110/2023-01-23 perl:5.032001 os:linux user:fhem pid:17897)
2023.02.10 14:03:09 3: DbLog dblog_THB - DB connection parameters are initialized in the SubProcess
2023.02.10 14:03:09 1: PERL WARNING: devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
2023.02.10 14:03:09 1: PERL WARNING: ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1310.
2023.02.10 14:03:10 1: PERL WARNING: Use of uninitialized value $value in string eq at ./FHEM/10_MAX.pm line 2057.
2023.02.10 14:03:10 1: PERL WARNING: Use of uninitialized value $value in string eq at ./FHEM/10_MAX.pm line 2058.
2023.02.10 14:03:11 3: DbLog dblog_THB - DB connection parameters are stored in SubProcess
2023.02.10 14:03:11 3: alexa: read: end of file reached while sysread
2023.02.10 14:03:11 3: alexa: stopped
2023.02.10 14:03:11 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2023.02.10 14:03:11 3: alexa: starting
2023.02.10 14:03:11 3: alexa: using logfile: ./log/alexa-2023-02-10.log
2023.02.10 14:03:12 2: AttrTemplates: got 258 entries
2023.02.10 14:03:14 2: {"token_type":"Bearer","access_token":"eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzUxMiJ9.eyJzdWIiOiJiNmU5ZDg5Ni1kMzMwLTRiMWYtODVhNS0wYjk4NGQyZWJiMDQiLCJhdWQiOiJVU0VSIiwic2NvcGUiOiJDVVNUT01FUl9BUEkiLCJpc3MiOiJvaWxmb3guaW8iLCJleHAiOjE2NzYwMzUwOTMsImp0aSI6IjA2MWZjZGI5LTdiOTgtNDhlYy05MWE4LTE3ODIwMmM3YzY4MiIsImVtYWlsIjoiYmt0QGdteC5uZXQifQ.4ZrJfN9N6W86dC_4C90Wc6C-_6KPTMdUWUvl99vzAzeidbMzK-PsscLRgA0OUB2PSLnZinTVIUzTCzdo4tASTQ","refresh_token":"eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzUxMiJ9.eyJzY29wZSI6IkNVU1RPTUVSX0FQSSIsImlzcyI6Im9pbGZveC5pbyIsImV4cCI6MTY3NzMzMDE5MywianRpIjoiNGUwMWM0OTYtODFmOC00MDQwLTk4MTQtM2ZhZWRiYTYyODAzIn0.Gwrv-IillrmsAePfT2Iu08FJp66s0OQWNqh-2MlMDdV2vqqoXY_HrunQ-raOpxA6FcRRdUIwWx1GyvV-3iRS6Q"}
2023.02.10 14:03:23 2: hueBridge1: http request failed: read from https://192.168.9.179:443 timed out
2023.02.10 14:03:23 2: error while requesting https://api.oilfox.io/customer-api/v1/device - start_SSL https://api.oilfox.io:443 timed out
2023.02.10 14:03:39 3: DbLog dblog_THB - SubProcess connected to fhem
2023.02.10 14:03:53 2: hueBridge1: EventStream: event for unknown device received, trying to refresh resouces
2023.02.10 14:03:53 2: hueBridge1: autocreate: created 0/0/0 devices (ignored 0/2/26)
2023.02.10 14:04:03 3: MaxSystem, Send Queue missing ack from MAX_PETRA_HT1 for TimeInformation, removing from queue
und fhempy-log
2023-02-10 13:13:44,639 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.595...
2023-02-10 13:13:44,643 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-02-10 13:13:44,687 - INFO - websockets.server: server listening on 0.0.0.0:15733
2023-02-10 13:13:55,527 - INFO - websockets.server: connection open
2023-02-10 13:13:55,528 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2023-02-10 13:14:07,473 - ERROR - fhempy.lib.fhem: FHEM took 5042ms for readingsBeginUpdate($defs{'TUYA_SP11'});;readingsBulkUpdateIfChanged($defs{'TUYA_SP11'},'online','0');;readingsEndUpdate($defs{'TUYA_SP11'},1);;
2023-02-10 13:14:07,527 - ERROR - fhempy.lib.fhem: FHEM took 5094ms for readingsBeginUpdate($defs{'TUYA_SP15'});;readingsBulkUpdateIfChanged($defs{'TUYA_SP15'},'online','0');;readingsEndUpdate($defs{'TUYA_SP15'},1);;
2023-02-10 13:14:07,581 - ERROR - fhempy.lib.fhem: FHEM took 5145ms for readingsBeginUpdate($defs{'TUYA_STF1'});;readingsBulkUpdateIfChanged($defs{'TUYA_STF1'},'online','0');;readingsEndUpdate($defs{'TUYA_STF1'},1);;
2023-02-10 13:14:07,636 - ERROR - fhempy.lib.fhem: FHEM took 5196ms for readingsBeginUpdate($defs{'TUYA_SP16'});;readingsBulkUpdateIfChanged($defs{'TUYA_SP16'},'online','0');;readingsEndUpdate($defs{'TUYA_SP16'},1);;
2023-02-10 13:14:07,694 - ERROR - fhempy.lib.fhem: FHEM took 5251ms for readingsBeginUpdate($defs{'TUYA_STF2'});;readingsBulkUpdateIfChanged($defs{'TUYA_STF2'},'online','0');;readingsEndUpdate($defs{'TUYA_STF2'},1);;
2023-02-10 13:14:07,748 - ERROR - fhempy.lib.fhem: FHEM took 5302ms for readingsSingleUpdate($defs{'TUYA_Temp01'},'state','ready',1)
2023-02-10 13:14:07,802 - ERROR - fhempy.lib.fhem: FHEM took 5354ms for readingsSingleUpdate($defs{'TUYA_Temp02'},'state','ready',1)
2023-02-10 13:14:07,857 - ERROR - fhempy.lib.fhem: FHEM took 5405ms for readingsSingleUpdate($defs{'TUYA_Temp03'},'state','ready',1)
2023-02-10 13:14:07,911 - ERROR - fhempy.lib.fhem: FHEM took 5456ms for readingsSingleUpdate($defs{'TUYA_Temp04'},'state','ready',1)
2023-02-10 13:14:07,913 - ERROR - fhempy.lib.fhem: FHEM took 5385ms for readingsBeginUpdate($defs{'TUYA_STF3'});;readingsBulkUpdateIfChanged($defs{'TUYA_STF3'},'online','0');;readingsEndUpdate($defs{'TUYA_STF3'},1);;
2023-02-10 13:14:07,968 - ERROR - fhempy.lib.fhem: FHEM took 5436ms for readingsSingleUpdate($defs{'TUYA_Temp05'},'state','ready',1)
2023-02-10 13:14:08,020 - ERROR - fhempy.lib.fhem: FHEM took 5429ms for readingsSingleUpdate($defs{'TUYA'},'state','connecting',1)
2023-02-10 13:14:08,075 - ERROR - fhempy.lib.fhem: FHEM took 5482ms for readingsSingleUpdate($defs{'TUYA_Temp07'},'state','ready',1)
2023-02-10 13:14:08,131 - ERROR - fhempy.lib.fhem: FHEM took 5534ms for readingsSingleUpdate($defs{'TUYA_Temp06'},'state','ready',1)
2023-02-10 13:14:08,134 - ERROR - fhempy.lib.fhem: FHEM took 5377ms for setDevAttrList('TUYA_BULB01', 'tuya_spec_functions tuya_spec_status IODev '.$readingFnAttributes)
2023-02-10 13:14:08,137 - ERROR - fhempy.lib.fhem: FHEM took 5274ms for setDevAttrList('TUYA_DIY1', 'tuya_spec_functions tuya_spec_status IODev '.$readingFnAttributes)
2023-02-10 13:14:08,140 - ERROR - fhempy.lib.fhem: FHEM took 5159ms for setDevAttrList('TUYA_BULB02', 'tuya_spec_functions tuya_spec_status IODev '.$readingFnAttributes)
2023-02-10 13:14:08,143 - ERROR - fhempy.lib.fhem: FHEM took 5109ms for setDevAttrList('TUYA_DIY4', 'tuya_spec_functions tuya_spec_status IODev '.$readingFnAttributes)
2023-02-10 13:14:08,146 - ERROR - fhempy.lib.fhem: FHEM took 5059ms for setDevAttrList('TUYA_DIY3', 'tuya_spec_functions tuya_spec_status IODev '.$readingFnAttributes)
2023-02-10 13:14:10,704 - ERROR - TUYA: Please activate OpenPulsar: https://developer.tuya.com/en/docs/iot/subscribe-mq?id=Kavqcrvckbh9h
2023-02-10 13:15:59,634 - ERROR - fhempy.lib.fhem: FHEM took 5894ms for foreach my $fhem_dev (sort keys %main::defs) { return 1 if(defined($main::defs{$fhem_dev}{FHEMPYTYPE}) && $main::defs{$fhem_dev}{FHEMPYTYPE} eq 'tuya' && defined($main::defs{$fhem_dev}{DEVICEID}) && $main::defs{$fhem_dev}{DEVICEID} eq '8877821724a16014a898');;}return 0;;
2023-02-10 13:15:59,675 - ERROR - fhempy.lib.fhem: FHEM took 5562ms for readingsBeginUpdate($defs{'TUYA_SP11'});;
2023-02-10 14:03:07,874 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.595...
2023-02-10 14:03:07,877 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-02-10 14:03:07,912 - INFO - websockets.server: server listening on 0.0.0.0:15733
2023-02-10 14:03:14,659 - INFO - websockets.server: connection open
2023-02-10 14:03:14,660 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2023-02-10 14:03:25,736 - ERROR - TUYA: Please activate OpenPulsar: https://developer.tuya.com/en/docs/iot/subscribe-mq?id=Kavqcrvckbh9h
room fhempy steht innerhalb 5 min stramm :-)
keine fälschlichen Neuanlagen :-)
Sehr gut. Den Raum neu laden geht aber hoffentlich nach der anfänglichen Ladezeit dann wieder innerhalb von wenigen Sekunden? Ich hatte den fhempy Raum mit allen deinen tuya Devices (alles Cloud, nicht Lokal) in ca. 3-4s offen.
Zitat von: dominik am 10 Februar 2023, 14:16:09
Sehr gut. Den Raum neu laden geht aber hoffentlich nach der anfänglichen Ladezeit dann wieder innerhalb von wenigen Sekunden? Ich hatte den fhempy Raum mit allen deinen tuya Devices (alles Cloud, nicht Lokal) in ca. 3-4s offen.
hatte mich verschrieben ... "stramm" war max. 5 Sekunden ! :-)
aktuell 2 sek :-?
leider zickt es wieder in der fhempy-Log:
2023-02-10 13:14:07,473 - ERROR - fhempy.lib.fhem: FHEM took 5042ms for readingsBeginUpdate($defs{'TUYA_SP11'});;readingsBulkUpdateIfChanged($defs{'TUYA_SP11'},'online','0');;readingsEndUpdate($defs{'TUYA_SP11'},1);;
2023-02-10 13:14:07,527 - ERROR - fhempy.lib.fhem: FHEM took 5094ms for readingsBeginUpdate($defs{'TUYA_SP15'});;readingsBulkUpdateIfChanged($defs{'TUYA_SP15'},'online','0');;readingsEndUpdate($defs{'TUYA_SP15'},1);;
2023-02-10 13:14:07,581 - ERROR - fhempy.lib.fhem: FHEM took 5145ms for readingsBeginUpdate($defs{'TUYA_STF1'});;readingsBulkUpdateIfChanged($defs{'TUYA_STF1'},'online','0');;readingsEndUpdate($defs{'TUYA_STF1'},1);;
2023-02-10 13:14:07,636 - ERROR - fhempy.lib.fhem: FHEM took 5196ms for readingsBeginUpdate($defs{'TUYA_SP16'});;readingsBulkUpdateIfChanged($defs{'TUYA_SP16'},'online','0');;readingsEndUpdate($defs{'TUYA_SP16'},1);;
2023-02-10 13:14:07,694 - ERROR - fhempy.lib.fhem: FHEM took 5251ms for readingsBeginUpdate($defs{'TUYA_STF2'});;readingsBulkUpdateIfChanged($defs{'TUYA_STF2'},'online','0');;readingsEndUpdate($defs{'TUYA_STF2'},1);;
2023-02-10 13:14:07,748 - ERROR - fhempy.lib.fhem: FHEM took 5302ms for readingsSingleUpdate($defs{'TUYA_Temp01'},'state','ready',1)
2023-02-10 13:14:07,802 - ERROR - fhempy.lib.fhem: FHEM took 5354ms for readingsSingleUpdate($defs{'TUYA_Temp02'},'state','ready',1)
2023-02-10 13:14:07,857 - ERROR - fhempy.lib.fhem: FHEM took 5405ms for readingsSingleUpdate($defs{'TUYA_Temp03'},'state','ready',1)
2023-02-10 13:14:07,911 - ERROR - fhempy.lib.fhem: FHEM took 5456ms for readingsSingleUpdate($defs{'TUYA_Temp04'},'state','ready',1)
2023-02-10 13:14:07,913 - ERROR - fhempy.lib.fhem: FHEM took 5385ms for readingsBeginUpdate($defs{'TUYA_STF3'});;readingsBulkUpdateIfChanged($defs{'TUYA_STF3'},'online','0');;readingsEndUpdate($defs{'TUYA_STF3'},1);;
2023-02-10 13:14:07,968 - ERROR - fhempy.lib.fhem: FHEM took 5436ms for readingsSingleUpdate($defs{'TUYA_Temp05'},'state','ready',1)
2023-02-10 13:14:08,020 - ERROR - fhempy.lib.fhem: FHEM took 5429ms for readingsSingleUpdate($defs{'TUYA'},'state','connecting',1)
2023-02-10 13:14:08,075 - ERROR - fhempy.lib.fhem: FHEM took 5482ms for readingsSingleUpdate($defs{'TUYA_Temp07'},'state','ready',1)
2023-02-10 13:14:08,131 - ERROR - fhempy.lib.fhem: FHEM took 5534ms for readingsSingleUpdate($defs{'TUYA_Temp06'},'state','ready',1)
2023-02-10 13:14:08,134 - ERROR - fhempy.lib.fhem: FHEM took 5377ms for setDevAttrList('TUYA_BULB01', 'tuya_spec_functions tuya_spec_status IODev '.$readingFnAttributes)
2023-02-10 13:14:08,137 - ERROR - fhempy.lib.fhem: FHEM took 5274ms for setDevAttrList('TUYA_DIY1', 'tuya_spec_functions tuya_spec_status IODev '.$readingFnAttributes)
2023-02-10 13:14:08,140 - ERROR - fhempy.lib.fhem: FHEM took 5159ms for setDevAttrList('TUYA_BULB02', 'tuya_spec_functions tuya_spec_status IODev '.$readingFnAttributes)
2023-02-10 13:14:08,143 - ERROR - fhempy.lib.fhem: FHEM took 5109ms for setDevAttrList('TUYA_DIY4', 'tuya_spec_functions tuya_spec_status IODev '.$readingFnAttributes)
2023-02-10 13:14:08,146 - ERROR - fhempy.lib.fhem: FHEM took 5059ms for setDevAttrList('TUYA_DIY3', 'tuya_spec_functions tuya_spec_status IODev '.$readingFnAttributes)
2023-02-10 13:14:10,704 - ERROR - TUYA: Please activate OpenPulsar: https://developer.tuya.com/en/docs/iot/subscribe-mq?id=Kavqcrvckbh9h
2023-02-10 13:15:59,634 - ERROR - fhempy.lib.fhem: FHEM took 5894ms for foreach my $fhem_dev (sort keys %main::defs) { return 1 if(defined($main::defs{$fhem_dev}{FHEMPYTYPE}) && $main::defs{$fhem_dev}{FHEMPYTYPE} eq 'tuya' && defined($main::defs{$fhem_dev}{DEVICEID}) && $main::defs{$fhem_dev}{DEVICEID} eq '8877821724a16014a898');;}return 0;;
2023-02-10 13:15:59,675 - ERROR - fhempy.lib.fhem: FHEM took 5562ms for readingsBeginUpdate($defs{'TUYA_SP11'});;
2023-02-10 14:03:07,874 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.595...
2023-02-10 14:03:07,877 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-02-10 14:03:07,912 - INFO - websockets.server: server listening on 0.0.0.0:15733
2023-02-10 14:03:14,659 - INFO - websockets.server: connection open
2023-02-10 14:03:14,660 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2023-02-10 14:03:25,736 - ERROR - TUYA: Please activate OpenPulsar: https://developer.tuya.com/en/docs/iot/subscribe-mq?id=Kavqcrvckbh9h
2023-02-10 14:10:53,266 - ERROR - fhempy.lib.fhem: FHEM took 5969ms for readingsBulkUpdateIfChanged($defs{'TUYA_JL04'},'cur_current','145.0');;
2023-02-10 14:10:53,267 - ERROR - fhempy.lib.fhem: FHEM took 5472ms for readingsBeginUpdate($defs{'TUYA_JL06'});;
2023-02-10 14:10:53,268 - ERROR - fhempy.lib.fhem: FHEM took 5346ms for readingsBulkUpdateIfChanged($defs{'TUYA_JL18'},'cur_voltage','234.9');;
2023-02-10 14:10:53,269 - ERROR - fhempy.lib.fhem: FHEM took 5217ms for readingsBeginUpdate($defs{'TUYA_JL33'});;
2023-02-10 14:25:31,125 - WARNING - asyncio: socket.send() raised exception.
2023-02-10 14:25:31,127 - WARNING - asyncio: socket.send() raised exception.
2023-02-10 14:25:31,129 - WARNING - asyncio: socket.send() raised exception.
2023-02-10 14:25:35,217 - WARNING - asyncio: socket.send() raised exception.
2023-02-10 14:25:35,369 - WARNING - asyncio: socket.send() raised exception.
usw. usw
#
Fehler traten also nach der schon berichteten PULSAR-Meldung auf
die 4 JL's antworteten wohl nicht schnell genug?
Immerhin wurden sie NICHT neuangelegt :-) :-)
in der fhem. log
2023.02.10 15:39:45 3: Watchdog WDT_BAD_F2 triggered
2023.02.10 15:46:08 2: Buderus : ERROR: Service: /system/holidayModes/hm5/dhwMode: No proper Communication with Gateway: read from http://192.168.9.114:80 timed out
2023.02.10 16:30:10 3: Watchdog WDT_HWR_F2 triggered
das FHEM hatte keine von 14:15 an keine Konfigurationseingriffe mehr
Funktionell aber alles in Ordnung ; bis auf die fehlenden statischen readings wie "productid" etc.
Schau bitte ins fhem Log ob dort von freezemon eine Fehlermeldung um 14:10 und 14:25 drin ist. Die beiden Einträge im fhempy Log deuten darauf hin, dass FHEM zu der Zeit blockiert war. Mit Antworten von den Devices hat es nix zu tun, hat nur mit der Bearbeitungszeit in FHEM zu tun.
Zitat von: dominik am 10 Februar 2023, 17:45:45
Schau bitte ins fhem Log ob dort von freezemon eine Fehlermeldung um 14:10 und 14:25 drin ist. Die beiden Einträge im fhempy Log deuten darauf hin, dass FHEM zu der Zeit blockiert war. Mit Antworten von den Devices hat es nix zu tun, hat nur mit der Bearbeitungszeit in FHEM zu tun.
2023.02.10 14:04:03 3: MaxSystem, Send Queue missing ack from MAX_PETRA_HT1 for TimeInformation, removing from queue
2023.02.10 15:39:45 3: Watchdog WDT_BAD_F2 triggered
2023.02.10 15:46:08 2: Buderus : ERROR: Service: /system/holidayModes/hm5/dhwMode: No proper Communication with Gateway: read from http://192.168.9.114:80 timed out
2023.02.10 16:30:10 3: Watchdog WDT_HWR_F2 triggered
2023.02.10 16:40:15 3: Watchdog WDT_BAD_F2 triggered
nach Shutdown restart 18:19
fhem-log: erste freezemon Meldung:
2023.02.10 18:25:24 1: [Freezemon] myFreezemon: possible freeze starting at 18:25:18, delay is 6.174 possibly caused by: no bad guy found :-(
fhempy-log:
2023-02-10 18:19:42,963 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.595...
2023-02-10 18:19:42,968 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-02-10 18:19:43,010 - INFO - websockets.server: server listening on 0.0.0.0:15733
2023-02-10 18:19:54,535 - INFO - websockets.server: connection open
2023-02-10 18:19:54,536 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2023-02-10 18:20:02,998 - ERROR - TUYA: Please activate OpenPulsar: https://developer.tuya.com/en/docs/iot/subscribe-mq?id=Kavqcrvckbh9h
2023-02-10 18:25:24,263 - ERROR - fhempy.lib.fhem: FHEM took 5985ms for readingsBeginUpdate($defs{'TUYA_JL04'});;
der bad guy ist fhempy himself ?
nach weiteren 30 min per 18:41
keine weiteren Einträge in beiden logs
erweitert: fhem-log ab 18:20
2023.02.10 18:20:20 3: DbLog dblog_THB - SubProcess connected to fhem
2023.02.10 18:20:22 1: [Freezemon] myFreezemon: possible freeze starting at 18:20:21, delay is 1.168 possibly caused by: tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-DbLog_execMemCacheAsync(dblog_THB) tmr-CUL_MAX_BroadcastTime(MaxSystem) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding)
2023.02.10 18:20:25 1: [Freezemon] myFreezemon: possible freeze starting at 18:20:24, delay is 1.867 possibly caused by: tmr-CUL_MAX_SQH(MaxSystem) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding)
2023.02.10 18:20:26 2: hueBridge1: EventStream: event for unknown device received, trying to refresh resouces
2023.02.10 18:20:27 2: hueBridge1: autocreate: created 0/0/0 devices (ignored 0/2/26)
2023.02.10 18:20:27 1: [Freezemon] myFreezemon: possible freeze starting at 18:20:26, delay is 1.233 possibly caused by: tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-CUL_HandleWriteQueue(CUL_0) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-CUL_MAX_SQH(MaxSystem) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding)
2023.02.10 18:20:32 1: [Freezemon] myFreezemon: possible freeze starting at 18:20:28, delay is 4.22 possibly caused by: tmr-CUL_MAX_SQH(MaxSystem)
2023.02.10 18:20:35 1: [Freezemon] myFreezemon: possible freeze starting at 18:20:33, delay is 2.684 possibly caused by: tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding)
2023.02.10 18:20:42 1: [Freezemon] myFreezemon: possible freeze starting at 18:20:37, delay is 5.616 possibly caused by: tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding)
2023.02.10 18:20:45 1: [Freezemon] myFreezemon: possible freeze starting at 18:20:43, delay is 2.316 possibly caused by: tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-HUEBridge_GetUpdate(hueBridge1)
2023.02.10 18:21:02 1: PERL WARNING: Wide character in print at ./FHEM/98_freezemon.pm line 1522.
2023.02.10 18:21:17 1: PERL WARNING: Wide character in print at ./FHEM/98_freezemon.pm line 1522.
2023.02.10 18:21:22 1: PERL WARNING: Subroutine HandleTimeout redefined at ./FHEM/98_apptime.pm line 45.
2023.02.10 18:21:22 1: PERL WARNING: Subroutine CallFn redefined at ./FHEM/98_apptime.pm line 122.
2023.02.10 18:25:24 1: [Freezemon] myFreezemon: possible freeze starting at 18:25:18, delay is 6.174 possibly caused by: no bad guy found :-(
und hier noch Link zum Forum MAX wegen delays: https://forum.fhem.de/index.php/topic,132037.msg1263072.html#new (https://forum.fhem.de/index.php/topic,132037.msg1263072.html#new)
ich berichte, falls doch errors im fhempy auftauchen
Ok, das sieht schon ganz gut aus. Scheinbar liefern deine Devices so viele Updates, dass das BindingsIo_handleReceiverQueue zu lange dauert. Wundert mich dennoch, dass viele Reading Update es so stark blockieren. Ich kann das noch etwas optimieren, damit BindingsIo_handleReceiverQueue FHEM nicht so stark blockiert.
einen kleinen wermutgstropfen gibt es noch:
meine Temp4,Temp5, Temp6, Temp7 hatten gestern seit 14 Uhr nichts mehr geschrieben; gegen 21:30 hatte ich nochmals Fhem shutdown restart gemacht; dann wurden wenige Miuten wohl werte gelesen; aber seit 21:28 keine mehr:
Das heutige FHEM-log war unaufffällig 2023.02.11 10:22:08 1: [Freezemon] myFreezemon: possible freeze starting at 10:22:07, delay is 1.217 possibly caused by: no bad guy found :-(
2023.02.11 10:29:46 1: [Freezemon] myFreezemon: possible freeze starting at 10:29:44, delay is 2.299 possibly caused by: no bad guy found :-(
2023.02.11 10:30:40 1: [Freezemon] myFreezemon: possible freeze starting at 10:30:34, delay is 6.761 possibly caused by: no bad guy found :-(
2023.02.11 10:30:42 1: [Freezemon] myFreezemon: possible freeze starting at 10:30:41, delay is 1.468 possibly caused by: tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding)
um 10:20 hatte ich FHEM aufgerufen und die Tempdevices angeschaut (um obiges festzustellen)
ich habe eben nochmals shutdown restart gemacht:
2023.02.11 00:00:11 3: TelegramBot_Callback TelegramBotTHB: Digest: Number of poll failures on 2023-02-10 is :0:
2023.02.11 00:02:18 3: alexa: using logfile: ./log/alexa-2023-02-11.log
2023.02.11 00:10:00 3: DbRep ReportDbLog_THB - ################################################################
2023.02.11 00:10:00 3: DbRep ReportDbLog_THB - ### New database clientSide dump ###
2023.02.11 00:10:00 3: DbRep ReportDbLog_THB - ################################################################
2023.02.11 00:10:00 3: DbRep ReportDbLog_THB - Starting dump of database 'fhem'
2023.02.11 00:10:00 4: DbRep ReportDbLog_THB - Database connect - user: fhemuser, UTF-8 option set: yes
2023.02.11 00:10:00 4: DbRep ReportDbLog_THB - SQL execute: SELECT VERSION()
2023.02.11 00:10:00 4: DbRep ReportDbLog_THB - SQL execute: SET NAMES 'utf8'
2023.02.11 00:10:00 4: DbRep ReportDbLog_THB - SQL execute: SHOW VARIABLES LIKE 'character_set_connection'
2023.02.11 00:10:00 3: DbRep ReportDbLog_THB - Characterset of collection set to utf8.
2023.02.11 00:10:00 3: DbRep ReportDbLog_THB - Searching for tables inside database fhem....
2023.02.11 00:10:00 4: DbRep ReportDbLog_THB - SQL execute: SHOW TABLE STATUS FROM `fhem`
2023.02.11 00:10:00 4: DbRep ReportDbLog_THB - SQL execute: SELECT count(*) FROM `current`
2023.02.11 00:10:00 4: DbRep ReportDbLog_THB - SQL execute: SELECT count(*) FROM `history`
2023.02.11 00:10:02 3: DbRep ReportDbLog_THB - Found 2 tables with 1321176 records.
2023.02.11 00:10:02 3: DbRep ReportDbLog_THB - Dumping table current (Type InnoDB):
2023.02.11 00:10:02 4: DbRep ReportDbLog_THB - SQL execute: SHOW CREATE TABLE `current`
2023.02.11 00:10:02 4: DbRep ReportDbLog_THB - SQL execute: SHOW FIELDS FROM `current`
2023.02.11 00:10:02 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `current` LIMIT 0,10000;
2023.02.11 00:10:03 3: DbRep ReportDbLog_THB - 1243 records inserted (size of backupfile: 251.99 KB)
2023.02.11 00:10:03 3: DbRep ReportDbLog_THB - Dumping table history (Type InnoDB):
2023.02.11 00:10:03 4: DbRep ReportDbLog_THB - SQL execute: SHOW CREATE TABLE `history`
2023.02.11 00:10:03 4: DbRep ReportDbLog_THB - SQL execute: SHOW FIELDS FROM `history`
2023.02.11 00:10:03 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 0,10000;
2023.02.11 00:10:03 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 10000,10000;
2023.02.11 00:10:03 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 20000,10000;
2023.02.11 00:10:03 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 30000,10000;
2023.02.11 00:10:04 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 40000,10000;
2023.02.11 00:10:04 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 50000,10000;
2023.02.11 00:10:04 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 60000,10000;
2023.02.11 00:10:05 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 70000,10000;
2023.02.11 00:10:05 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 80000,10000;
2023.02.11 00:10:05 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 90000,10000;
2023.02.11 00:10:06 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 100000,10000;
2023.02.11 00:10:06 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 110000,10000;
2023.02.11 00:10:07 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 120000,10000;
2023.02.11 00:10:07 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 130000,10000;
2023.02.11 00:10:07 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 140000,10000;
2023.02.11 00:10:08 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 150000,10000;
2023.02.11 00:10:08 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 160000,10000;
2023.02.11 00:10:09 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 170000,10000;
2023.02.11 00:10:09 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 180000,10000;
2023.02.11 00:10:10 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 190000,10000;
2023.02.11 00:10:10 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 200000,10000;
2023.02.11 00:10:11 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 210000,10000;
2023.02.11 00:10:12 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 220000,10000;
2023.02.11 00:10:12 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 230000,10000;
2023.02.11 00:10:13 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 240000,10000;
2023.02.11 00:10:13 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 250000,10000;
2023.02.11 00:10:14 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 260000,10000;
2023.02.11 00:10:15 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 270000,10000;
2023.02.11 00:10:15 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 280000,10000;
2023.02.11 00:10:16 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 290000,10000;
2023.02.11 00:10:17 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 300000,10000;
2023.02.11 00:10:17 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 310000,10000;
2023.02.11 00:10:18 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 320000,10000;
2023.02.11 00:10:19 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 330000,10000;
2023.02.11 00:10:19 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 340000,10000;
2023.02.11 00:10:20 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 350000,10000;
2023.02.11 00:10:21 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 360000,10000;
2023.02.11 00:10:22 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 370000,10000;
2023.02.11 00:10:22 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 380000,10000;
2023.02.11 00:10:23 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 390000,10000;
2023.02.11 00:10:24 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 400000,10000;
2023.02.11 00:10:25 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 410000,10000;
2023.02.11 00:10:26 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 420000,10000;
2023.02.11 00:10:27 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 430000,10000;
2023.02.11 00:10:28 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 440000,10000;
2023.02.11 00:10:29 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 450000,10000;
2023.02.11 00:10:29 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 460000,10000;
2023.02.11 00:10:30 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 470000,10000;
2023.02.11 00:10:31 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 480000,10000;
2023.02.11 00:10:32 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 490000,10000;
2023.02.11 00:10:33 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 500000,10000;
2023.02.11 00:10:34 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 510000,10000;
2023.02.11 00:10:35 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 520000,10000;
2023.02.11 00:10:36 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 530000,10000;
2023.02.11 00:10:37 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 540000,10000;
2023.02.11 00:10:38 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 550000,10000;
2023.02.11 00:10:40 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 560000,10000;
2023.02.11 00:10:41 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 570000,10000;
2023.02.11 00:10:42 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 580000,10000;
2023.02.11 00:10:43 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 590000,10000;
2023.02.11 00:10:44 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 600000,10000;
2023.02.11 00:10:45 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 610000,10000;
2023.02.11 00:10:46 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 620000,10000;
2023.02.11 00:10:47 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 630000,10000;
2023.02.11 00:10:49 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 640000,10000;
2023.02.11 00:10:50 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 650000,10000;
2023.02.11 00:10:51 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 660000,10000;
2023.02.11 00:10:52 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 670000,10000;
2023.02.11 00:10:54 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 680000,10000;
2023.02.11 00:10:55 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 690000,10000;
2023.02.11 00:10:56 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 700000,10000;
2023.02.11 00:10:58 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 710000,10000;
2023.02.11 00:10:59 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 720000,10000;
2023.02.11 00:11:00 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 730000,10000;
2023.02.11 00:11:02 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 740000,10000;
2023.02.11 00:11:03 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 750000,10000;
2023.02.11 00:11:04 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 760000,10000;
2023.02.11 00:11:06 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 770000,10000;
2023.02.11 00:11:07 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 780000,10000;
2023.02.11 00:11:09 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 790000,10000;
2023.02.11 00:11:10 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 800000,10000;
2023.02.11 00:11:12 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 810000,10000;
2023.02.11 00:11:13 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 820000,10000;
2023.02.11 00:11:15 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 830000,10000;
2023.02.11 00:11:16 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 840000,10000;
2023.02.11 00:11:18 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 850000,10000;
2023.02.11 00:11:19 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 860000,10000;
2023.02.11 00:11:21 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 870000,10000;
2023.02.11 00:11:23 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 880000,10000;
2023.02.11 00:11:24 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 890000,10000;
2023.02.11 00:11:26 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 900000,10000;
2023.02.11 00:11:28 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 910000,10000;
2023.02.11 00:11:29 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 920000,10000;
2023.02.11 00:11:31 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 930000,10000;
2023.02.11 00:11:33 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 940000,10000;
2023.02.11 00:11:34 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 950000,10000;
2023.02.11 00:11:36 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 960000,10000;
2023.02.11 00:11:38 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 970000,10000;
2023.02.11 00:11:40 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 980000,10000;
2023.02.11 00:11:41 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 990000,10000;
2023.02.11 00:11:43 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1000000,10000;
2023.02.11 00:11:45 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1010000,10000;
2023.02.11 00:11:47 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1020000,10000;
2023.02.11 00:11:49 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1030000,10000;
2023.02.11 00:11:50 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1040000,10000;
2023.02.11 00:11:52 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1050000,10000;
2023.02.11 00:11:54 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1060000,10000;
2023.02.11 00:11:56 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1070000,10000;
2023.02.11 00:11:58 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1080000,10000;
2023.02.11 00:12:00 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1090000,10000;
2023.02.11 00:12:02 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1100000,10000;
2023.02.11 00:12:05 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1110000,10000;
2023.02.11 00:12:07 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1120000,10000;
2023.02.11 00:12:10 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1130000,10000;
2023.02.11 00:12:12 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1140000,10000;
2023.02.11 00:12:15 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1150000,10000;
2023.02.11 00:12:17 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1160000,10000;
2023.02.11 00:12:20 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1170000,10000;
2023.02.11 00:12:23 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1180000,10000;
2023.02.11 00:12:25 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1190000,10000;
2023.02.11 00:12:28 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1200000,10000;
2023.02.11 00:12:31 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1210000,10000;
2023.02.11 00:12:33 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1220000,10000;
2023.02.11 00:12:36 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1230000,10000;
2023.02.11 00:12:39 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1240000,10000;
2023.02.11 00:12:42 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1250000,10000;
2023.02.11 00:12:44 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1260000,10000;
2023.02.11 00:12:47 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1270000,10000;
2023.02.11 00:12:50 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1280000,10000;
2023.02.11 00:12:53 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1290000,10000;
2023.02.11 00:12:56 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1300000,10000;
2023.02.11 00:12:59 4: DbRep ReportDbLog_THB - SQL execute: SELECT * FROM `history` LIMIT 1310000,10000;
2023.02.11 00:13:02 3: DbRep ReportDbLog_THB - 1319933 records inserted (size of backupfile: 258.84 MB)
2023.02.11 00:13:02 3: DbRep ReportDbLog_THB - Deleting old dumpfile 'fhem_2023_02_08_00_10.sql'
2023.02.11 00:13:02 3: DbRep ReportDbLog_THB - Finished backup of database fhem - total time used (hh:mm:ss): 00:03:02
2023.02.11 00:13:02 3: DbRep ReportDbLog_THB - Database dump finished successfully.
2023.02.11 00:22:08 1: [Freezemon] myFreezemon: possible freeze starting at 00:22:07, delay is 1.356 possibly caused by: no bad guy found :-(
2023.02.11 00:50:36 1: [Freezemon] myFreezemon: possible freeze starting at 00:50:35, delay is 1.005 possibly caused by: tmr-BindingsIo_handleReceiverQueue(local_pybinding)
2023.02.11 00:53:24 1: [Freezemon] myFreezemon: possible freeze starting at 00:53:23, delay is 1.004 possibly caused by: no bad guy found :-(
2023.02.11 01:22:08 1: [Freezemon] myFreezemon: possible freeze starting at 01:22:07, delay is 1.406 possibly caused by: no bad guy found :-(
2023.02.11 01:55:30 2: Buderus : ERROR: Service: /recordings/system/heatSources/hs1/actualPower?interval=2023: No proper Communication with Gateway: read from http://192.168.9.114:80 timed out
2023.02.11 02:22:08 1: [Freezemon] myFreezemon: possible freeze starting at 02:22:07, delay is 1.343 possibly caused by: tmr-BindingsIo_handleReceiverQueue(local_pybinding)
2023.02.11 02:35:01 1: [Freezemon] myFreezemon: possible freeze starting at 02:34:58, delay is 3.778 possibly caused by: tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-CODE(0x4d79618)(GetUpdate)
2023.02.11 02:37:02 1: [Freezemon] myFreezemon: possible freeze starting at 02:36:58, delay is 4.652 possibly caused by: tmr-CODE(0x4d79618)(GetUpdate)
2023.02.11 03:00:00 2: DbLog dblog_THB - Connection closed until 03:00:00 (86400 seconds).
2023.02.11 03:00:00 3: DbLog dblog_THB - Database disconnected by request.
2023.02.11 03:01:00 3: DbLog dblog_THB - Reopen requested
2023.02.11 03:01:00 2: DbRep Reduce_Daily - command message after reduceLog: "Reopen executed."
2023.02.11 03:01:00 3: DbLog dblog_THB - Database disconnected by request.
2023.02.11 03:01:00 3: DbLog dblog_THB - SubProcess connected to fhem
2023.02.11 03:57:40 3: MaxSystem, Send Queue missing ack from MAX_KCH_HT for TimeInformation, removing from queue
2023.02.11 04:00:00 3: DbRep Reduce_Hourly - ################################################################
2023.02.11 04:00:00 3: DbRep Reduce_Hourly - ### new reduceLog run ###
2023.02.11 04:00:00 3: DbRep Reduce_Hourly - ################################################################
2023.02.11 04:00:00 3: DbRep Reduce_Hourly - get initial structure information of database "fhem", remaining attempts: 3
2023.02.11 04:00:00 3: DbRep Reduce_Hourly - Connectiontest to database mysql:database=fhem;host=localhost;port=3306 with user fhemuser
2023.02.11 04:00:00 3: DbRep Reduce_Hourly - Index Report_Idx exists. Check ok
2023.02.11 04:00:00 3: DbRep Reduce_Hourly - Initial data information retrieved - total time used: 0.0170 seconds
2023.02.11 04:00:00 3: DbRep Reduce_Hourly - Connectiontest to db mysql:database=fhem;host=localhost;port=3306 successful
2023.02.11 04:00:00 3: DbRep Reduce_Hourly - execute command before reduceLog: 'set dblog_THB reopen 86400'
2023.02.11 04:00:00 2: DbLog dblog_THB - Connection closed until 04:00:00 (86400 seconds).
2023.02.11 04:00:00 3: DbLog dblog_THB - Database disconnected by request.
2023.02.11 04:00:00 3: DbRep Reduce_Hourly - reduce data older than: 2023-02-04 23:59:59, newer than: 2023-02-02 00:00:00
2023.02.11 04:00:00 3: DbRep Reduce_Hourly - reduceLog requested with options:
average=day
INCLUDE -> Devs: % Readings: %
2023.02.11 04:00:03 3: DbRep Reduce_Hourly - reduceLog deleting 66041 records of day: 2023-02-04
2023.02.11 04:00:08 3: DbRep Reduce_Hourly - reduceLog deletion progress of day: 2023-02-04 is: 10000
2023.02.11 04:00:13 3: DbRep Reduce_Hourly - reduceLog deletion progress of day: 2023-02-04 is: 20000
2023.02.11 04:00:17 3: DbRep Reduce_Hourly - reduceLog deletion progress of day: 2023-02-04 is: 30000
2023.02.11 04:00:22 3: DbRep Reduce_Hourly - reduceLog deletion progress of day: 2023-02-04 is: 40000
2023.02.11 04:00:27 3: DbRep Reduce_Hourly - reduceLog deletion progress of day: 2023-02-04 is: 50000
2023.02.11 04:00:32 3: DbRep Reduce_Hourly - reduceLog deletion progress of day: 2023-02-04 is: 60000
2023.02.11 04:00:35 3: DbRep Reduce_Hourly - reduceLog (hourly-average) updating 2445 records of day: 2023-02-04
2023.02.11 04:00:36 3: DbRep Reduce_Hourly - reduceLog (hourly-average) updating progress of day: 2023-02-04 is: 1000
2023.02.11 04:00:37 3: DbRep Reduce_Hourly - reduceLog (hourly-average) updating progress of day: 2023-02-04 is: 2000
2023.02.11 04:00:37 3: DbRep Reduce_Hourly - reduceLog (daily-average) updating 258, deleting 3826 records of day: 2023-02-04
2023.02.11 04:00:38 3: DbRep Reduce_Hourly - reduceLog (daily-average) deleting progress of day: 2023-02-04 is: 1000
2023.02.11 04:00:38 3: DbRep Reduce_Hourly - reduceLog (daily-average) updating progress of day: 2023-02-04 is: 100
2023.02.11 04:00:39 3: DbRep Reduce_Hourly - reduceLog (daily-average) deleting progress of day: 2023-02-04 is: 2000
2023.02.11 04:00:39 3: DbRep Reduce_Hourly - reduceLog (daily-average) updating progress of day: 2023-02-04 is: 200
2023.02.11 04:00:39 3: DbRep Reduce_Hourly - reduceLog (daily-average) deleting progress of day: 2023-02-04 is: 3000
2023.02.11 04:00:39 3: DbRep Reduce_Hourly - reduceLog finished. Rows processed: 78104, deleted: 69867, updated: 2703
2023.02.11 04:00:39 3: DbLog dblog_THB - Reopen requested
2023.02.11 04:00:40 2: DbRep Reduce_Hourly - command message after reduceLog: "Reopen executed."
2023.02.11 04:00:40 3: DbLog dblog_THB - Database disconnected by request.
2023.02.11 04:00:40 3: DbLog dblog_THB - SubProcess connected to fhem
2023.02.11 04:36:39 1: [Freezemon] myFreezemon: possible freeze starting at 04:36:38, delay is 1.034 possibly caused by: no bad guy found :-(
2023.02.11 04:54:54 1: PERL WARNING: Argument "low" isn't numeric in numeric lt (<) at (eval 474969) line 1.
2023.02.11 05:00:00 2: DbLog dblog_THB - WARNING - "count" is outdated. Please consider use of DbRep "set <Name> countEntries" instead.
2023.02.11 05:33:59 1: [Freezemon] myFreezemon: possible freeze starting at 05:33:58, delay is 1.267 possibly caused by: tmr-HUEBridge_GetUpdate(hueBridge1)
2023.02.11 06:00:00 3: DbLog dblog_THB - Reopen requested
2023.02.11 06:00:00 3: set dblog_THB reopen : Reopen executed.
2023.02.11 06:00:00 3: DbLog_reopen: Reopen executed.
2023.02.11 06:00:00 3: DbLog dblog_THB - Database disconnected by request.
2023.02.11 06:00:00 3: DbLog dblog_THB - SubProcess connected to fhem
2023.02.11 06:56:25 2: LOGIN TOKEN MISSING OR EXPIRED
2023.02.11 06:56:25 3: Reconnecting...
2023.02.11 06:56:25 2: {"token_type":"Bearer","access_token":"eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzUxMiJ9.eyJzdWIiOiJiNmU5ZDg5Ni1kMzMwLTRiMWYtODVhNS0wYjk4NGQyZWJiMDQiLCJhdWQiOiJVU0VSIiwic2NvcGUiOiJDVVNUT01FUl9BUEkiLCJpc3MiOiJvaWxmb3guaW8iLCJleHAiOjE2NzYwOTU4ODUsImp0aSI6ImI5OTI4YmFiLTFhOTgtNGFmOS1iN2U0LWVhMTRiM2QyZmM2MyIsImVtYWlsIjoiYmt0QGdteC5uZXQifQ.hx-nZjAwmHXct7KdeyxQ54tKr8IPiOax353eaCLQIYdgX_PQEh98qQ6124Pq2-DEC8ywupiSBqpKYYLLbXVQmA","refresh_token":"eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzUxMiJ9.eyJzY29wZSI6IkNVU1RPTUVSX0FQSSIsImlzcyI6Im9pbGZveC5pbyIsImV4cCI6MTY3NzM5MDk4NSwianRpIjoiODMzMmQyMmYtYjJmNi00YjhkLTlhZWMtMzE5YjRjMzdmZTkyIn0.5XvLx-RCzeNJq1YQcs4tl5wOLZeVT8Pjle2Cefeh6v9Jtr6YteSeABNO-jm4v2cLWL5tKNHJ9Y7N913yH8jSYw"}
2023.02.11 06:57:21 1: [Freezemon] myFreezemon: possible freeze starting at 06:57:20, delay is 1.267 possibly caused by: tmr-CUL_HandleWriteQueue(CUL_0) tmr-CODE(0x59d8608)(GetUpdate) tmr-CUL_MAX_SQH(MaxSystem)
2023.02.11 06:57:44 3: MaxSystem, Send Queue missing ack from MAX_PETRA_WT for TimeInformation, removing from queue
2023.02.11 07:22:08 1: [Freezemon] myFreezemon: possible freeze starting at 07:22:07, delay is 1.481 possibly caused by: tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-HttpUtils_TimeoutErr(N/A)
2023.02.11 07:36:12 3: Untergeschoss_Rollo_Alle_up_Notify return value: OK
2023.02.11 07:36:14 3: Untergeschoss_Rollo_2_up_Notify return value: OK
2023.02.11 07:36:16 3: Wohnzimmer_Rollo_1_up_Notify return value: OK
2023.02.11 07:36:19 3: Wohnzimmer_Rollo_2_up_Notify return value: OK
2023.02.11 07:36:21 3: Wohnzimmer_Rollo_3_up_Notify return value: OK
2023.02.11 07:36:21 1: [Freezemon] myFreezemon: possible freeze starting at 07:36:10, delay is 11.468 possibly caused by: tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-at_Exec(Untergeschoss_Rollos_bei_Sonnenaufgang_hoch_AT) tmr-at_Exec(Untergeschoss_Rollo_2_bei_Sonnenaufgang_hoch_AT) tmr-at_Exec(Wohnzimmer_Rollo_1_bei_Sonnenaufgang_hoch_AT) tmr-at_Exec(Wohnzimmer_Rollo_2_bei_Sonnenaufgang_hoch_AT) tmr-at_Exec(Wohnzimmer_Rollo_3_bei_Sonnenaufgang_hoch_AT)
2023.02.11 07:39:32 3: Untergeschoss_Rollo_1_up_Notify return value: OK
2023.02.11 07:39:32 1: [Freezemon] myFreezemon: possible freeze starting at 07:39:30, delay is 2.245 possibly caused by: tmr-at_Exec(Untergeschoss_Rollo_1_bei_Sonnenaufgang_hoch_AT)
2023.02.11 07:56:12 3: Kueche_Rollo_3_up_Notify return value: OK
2023.02.11 07:56:12 1: [Freezemon] myFreezemon: possible freeze starting at 07:56:10, delay is 2.26 possibly caused by: tmr-at_Exec(Kueche_Rollo_3_bei_Sonnenaufgang_hoch_AT)
2023.02.11 08:30:02 3: Wohnzimmer_Rollo_Alle_up_Notify return value: OK
2023.02.11 08:30:04 3: Untergeschoss_Rollo_3_up_Notify return value: OK
2023.02.11 08:30:04 1: [Freezemon] myFreezemon: possible freeze starting at 08:30:00, delay is 4.697 possibly caused by: tmr-at_Exec(Wohnzimmer_Rollos_bei_Sonnenaufgang_hoch_AT) tmr-at_Exec(Untergeschoss_Rollo_3_bei_Sonnenaufgang_hoch_AT)
2023.02.11 08:57:43 3: MaxSystem, Send Queue missing ack from MAX_DIELE_HT for TimeInformation, removing from queue
2023.02.11 09:22:08 1: [Freezemon] myFreezemon: possible freeze starting at 09:22:07, delay is 1.421 possibly caused by: tmr-HUEBridge_GetUpdate(hueBridge1)
2023.02.11 09:30:02 3: Obergeschoss_Rollo_1_up_Notify return value: OK
2023.02.11 09:30:02 1: [Freezemon] myFreezemon: possible freeze starting at 09:30:00, delay is 2.177 possibly caused by: tmr-at_Exec(Obergeschoss_Rollo_1_bei_Sonnenaufgang_hoch_AT)
2023.02.11 09:31:43 1: [Freezemon] myFreezemon: possible freeze starting at 09:31:42, delay is 1.059 possibly caused by: no bad guy found :-(
2023.02.11 09:57:33 1: PERL WARNING: Argument "low" isn't numeric in numeric lt (<) at (eval 761933) line 1.
2023.02.11 09:57:34 2: CM_Parse, unhandled message type D0 from MAX_04420c to MAX_cdec0b - ignoring !
2023.02.11 09:57:41 3: MaxSystem, Send Queue missing ack from MAX_PETRA_HT3 for TimeInformation, removing from queue
2023.02.11 09:57:43 2: CM_Parse, unhandled message type D0 from MAX_02020b to MAX_12b70c - ignoring !
2023.02.11 10:22:08 1: [Freezemon] myFreezemon: possible freeze starting at 10:22:07, delay is 1.217 possibly caused by: no bad guy found :-(
2023.02.11 10:29:46 1: [Freezemon] myFreezemon: possible freeze starting at 10:29:44, delay is 2.299 possibly caused by: no bad guy found :-(
2023.02.11 10:30:40 1: [Freezemon] myFreezemon: possible freeze starting at 10:30:34, delay is 6.761 possibly caused by: no bad guy found :-(
2023.02.11 10:30:42 1: [Freezemon] myFreezemon: possible freeze starting at 10:30:41, delay is 1.468 possibly caused by: tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding) tmr-BindingsIo_handleReceiverQueue(local_pybinding)
2023.02.11 10:39:33 1: [Freezemon] myFreezemon: possible freeze starting at 10:39:32, delay is 1.185 possibly caused by: no bad guy found :-(
2023.02.11 10:41:11 2: DbLog dblog_THB - Wait for last database cycle due to shutdown ...
2023.02.11 10:41:11 1: Server shutdown delayed due to alexa,dblog_THB for max 10 sec
2023.02.11 10:41:11 2: DbLog dblog_THB - Last database write cycle done
2023.02.11 10:41:13 3: alexa: read: end of file reached while sysread
2023.02.11 10:41:13 3: alexa: stopped
2023.02.11 10:41:13 0: Server shutdown
2023.02.11 10:41:13 2: DbLog dblog_THB - stopping SubProcess PID >22004< ...
2023.02.11 10:41:13 2: DbLog dblog_THB - SubProcess PID >22004< stopped
2023.02.11 10:41:15 1: Including fhem.cfg
2023.02.11 10:41:16 2: DbLog dblog_THB - Subprocess >28869< initialized ... ready for non-blocking operation
2023.02.11 10:41:17 3: freezemon defined myFreezemon freezemon
2023.02.11 10:41:17 3: [Freezemon] myFreezemon: Wrapping Log3
2023.02.11 10:41:17 3: telnetPort: port 7072 opened
2023.02.11 10:41:17 3: WEB: port 8083 opened
2023.02.11 10:41:17 3: WEBphone: port 8084 opened
2023.02.11 10:41:17 3: WEBtablet: port 8085 opened
2023.02.11 10:41:17 3: TelegramBot_Define TelegramBotTHB: called
2023.02.11 10:41:18 3: BindingsIo v1.0.1
2023.02.11 10:41:18 3: fhempyServer v1.0.0
2023.02.11 10:41:18 3: fhempy v1.0.0 (tuya_cloud: TUYA)
2023.02.11 10:41:18 3: fhempy v1.0.0 (tuya: tuya_system)
2023.02.11 10:41:18 3: Opening CUL_0 device /dev/ttyACM0
2023.02.11 10:41:18 3: Setting CUL_0 serial parameters to 9600,8,N,1
2023.02.11 10:41:18 3: CUL_0: Possible commands: BbCFiAZNkGMKUYRTVWXefmLltux
2023.02.11 10:41:18 3: CUL_0 device opened
2023.02.11 10:41:18 2: Switched CUL_0 rfmode to MAX
2023.02.11 10:41:18 3: Opening JLLaCR device /dev/ttyUSB0
2023.02.11 10:41:18 3: Setting JLLaCR serial parameters to 57600,8,N,1
2023.02.11 10:41:19 3: JLLaCR device opened
2023.02.11 10:41:19 1: PERL WARNING: Use of uninitialized value in numeric ge (>=) at ./FHEM/12_OilFox.pm line 387, <$fh> line 562.
2023.02.11 10:41:19 2: LOGIN TOKEN MISSING OR EXPIRED
2023.02.11 10:41:19 3: myOilFox - email set to bkt@gmx.net
2023.02.11 10:41:19 3: myOilFox - set interval: 36000
2023.02.11 10:41:19 3: myOilFox - password set to thbbkt25
2023.02.11 10:41:19 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.11 10:41:35 2: eventTypes: loaded 16354 lines from ./log/eventTypes.txt
2023.02.11 10:41:35 3: TX29_00: I/O device is JLLaCR
2023.02.11 10:41:35 3: TX29DTH_01: I/O device is JLLaCR
2023.02.11 10:41:35 3: TX29DTH_02: I/O device is JLLaCR
2023.02.11 10:41:35 3: TX29DTH_03: I/O device is JLLaCR
2023.02.11 10:41:35 3: TX29DTH_04: I/O device is JLLaCR
2023.02.11 10:41:35 3: TX29DTH_05: I/O device is JLLaCR
2023.02.11 10:41:35 3: TX29DTH_06: I/O device is JLLaCR
2023.02.11 10:41:35 3: TX29DTH_07: I/O device is JLLaCR
2023.02.11 10:41:35 3: TX29DTH_08: I/O device is JLLaCR
2023.02.11 10:41:35 3: TX29DTH_09: I/O device is JLLaCR
2023.02.11 10:41:35 3: TX29DTH_10: I/O device is JLLaCR
2023.02.11 10:41:35 3: TX29DTH_11: I/O device is JLLaCR
2023.02.11 10:41:35 3: TX29DTH_12: I/O device is JLLaCR
2023.02.11 10:41:35 3: TX25IT_13: I/O device is JLLaCR
2023.02.11 10:41:35 3: TX29DTH_14: I/O device is JLLaCR
2023.02.11 10:41:35 3: TX29DTH_15: I/O device is JLLaCR
2023.02.11 10:41:35 3: TX29DTH_16: I/O device is JLLaCR
2023.02.11 10:41:35 3: TX29DTH_17: I/O device is JLLaCR
2023.02.11 10:41:35 3: TX29DTH_18: I/O device is JLLaCR
2023.02.11 10:41:35 3: TX29DTH_19: I/O device is JLLaCR
2023.02.11 10:41:35 3: TX29DTH_20: I/O device is JLLaCR
2023.02.11 10:41:35 3: TX29DTH_21: I/O device is JLLaCR
2023.02.11 10:41:35 3: TX29DTH_22: I/O device is JLLaCR
2023.02.11 10:41:35 3: HUEDevice2: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice4: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice5: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice6: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice7: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice8: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice10: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice17: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice18: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice19: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice20: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice22: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice23: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice24: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice25: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice27: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice28: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice29: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice30: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice31: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice32: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice33: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice38: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice39: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice40: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice41: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup0: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup1: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup2: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup3: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup4: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup5: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup6: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup7: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup8: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup9: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup10: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup11: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup12: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup13: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup14: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup15: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup16: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup17: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup18: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup19: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup20: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup21: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup22: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup23: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup24: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup25: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup26: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup27: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup28: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup29: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup30: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice44: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEGroup31: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUESensor6: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUESensor8: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUESensor10: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUESensor13: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUESensor24: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUESensor27: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUESensor34: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUESensor37: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUESensor45: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice45: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice46: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice47: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice48: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice49: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice50: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice51: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUESensor91: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUESensor110: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUESensor1: I/O device is hueBridge1
2023.02.11 10:41:35 3: HUEDevice52: I/O device is hueBridge1
2023.02.11 10:41:35 1: MaxTemp: WT
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_BULB01)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_BULB02)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya_cloud: TUYA_BULB03)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Camera1)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Camera2)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Camera3)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya_cloud: Camera4tuya_cloud_bf6b1900c331a78a2fkecw)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya_cloud: Camera5tuya_cloud_bfbeab33da30f5635ffj0r)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Camera6)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_DIY1)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_DIY3)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_DIY4)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_EMYLO1)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_EMYLO2)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_EMYLOD2)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_EMYLO3)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_EMYLO4)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL02)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL03)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL04)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL05)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL06)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL07)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL08)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL09)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL10Z)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL11Z)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL12Z)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL13)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL14)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL15)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL16)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL17)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL18)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya_cloud: TUYAC_JL19)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL20)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL21)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL22)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL23)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL24)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya_cloud: TUYA_JL25)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL26)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL27)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL28)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL29)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL30)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL31)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL32)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL33)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL34)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL35)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_JL36)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_PS1)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_PS2)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_PS3)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_PS4)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_PS5)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_PS7)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_SCHF1)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_SCHF2)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_SCHF3)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_SP01)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_SP02)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_SP03)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_SP04)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_SP05)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_SP06)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_SP07)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_SP08)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_SP09)
2023.02.11 10:41:36 3: fhempy v1.0.0 (tuya: TUYA_SP10)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya: TUYA_SP11)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya: TUYA_SP12)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya: TUYA_SP13)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya: TUYA_SP14)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya: TUYA_SP15)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya: TUYA_SP16)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya_cloud: TUYAC_PIR01)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya_cloud: TUYAC_PIR02)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya_cloud: TUYAC_PIR03)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorT01)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorT02)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorT03)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorT04)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorT05)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorW01)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorW02)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorW03)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorW04)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Sir01)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Sir02)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Sir03)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya_cloud: TUYAC_Relais01)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya_cloud: TUYAC_SensorSmoke01)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya: TUYA_STF1)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya: TUYA_STF2)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya: TUYA_STF3)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya: TUYA_MMG)
2023.02.11 10:41:37 3: SST (SamsungSmartThingsConnector): define - CONNECTOR defined as SamsungSmartThingsConnector
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp01)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp02)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp03)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp04)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp05)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp06)
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya_cloud: TUYA_Temp07)
2023.02.11 10:41:37 1: PERL WARNING: Useless use of anonymous hash ({}) in void context at (eval 128) line 1, <$fh> line 6381.
2023.02.11 10:41:37 3: fhempy v1.0.0 (tuya_cloud: TUYA_SCHFF4)
2023.02.11 10:41:37 1: Including ./log/fhem.save
2023.02.11 10:41:37 1: Messages collected while initializing FHEM:SecurityCheck:
telnetPort is not password protected
WEBphone is not password protected
WEB is not password protected
WEBtablet 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.11 10:41:37 2: Deleting fhempy-2023-02-01.log
2023.02.11 10:41:38 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2023.02.11 10:41:38 3: alexa: starting
2023.02.11 10:41:38 3: alexa: using logfile: ./log/alexa-2023-02-11.log
2023.02.11 10:41:38 2: hueBridge1: autocreate: created 0/0/0 devices (ignored 0/2/26)
2023.02.11 10:41:40 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2023.02.11 10:41:40 2: [Freezemon] myFreezemon: ready to watch out for delays greater than 1 second(s)
2023.02.11 10:41:40 0: Featurelevel: 6.2
2023.02.11 10:41:40 0: Server started with 513 defined entities (fhem.pl:27110/2023-01-23 perl:5.032001 os:linux user:fhem pid:28868)
2023.02.11 10:41:40 3: DbLog dblog_THB - DB connection parameters are initialized in the SubProcess
2023.02.11 10:41:40 1: PERL WARNING: devspec2array *: Unknown verb pattern '' in regex; marked by <-- HERE in m/^(*) <-- HERE $/ at fhem.pl line 1352.
2023.02.11 10:41:40 1: PERL WARNING: ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE :.*RSSI.*$/ at ./FHEM/93_DbLog.pm line 1310.
2023.02.11 10:41:41 3: DbLog dblog_THB - DB connection parameters are stored in SubProcess
2023.02.11 10:41:41 3: alexa: read: end of file reached while sysread
2023.02.11 10:41:41 3: alexa: stopped
vorheriges posting war abgeschnitten..
fhempy-log um den Zeitpunkt restart:
2023-02-11 10:30:30,469 - WARNING - asyncio: socket.send() raised exception.
2023-02-11 10:30:35,542 - WARNING - asyncio: socket.send() raised exception.
2023-02-11 10:30:39,882 - WARNING - asyncio: socket.send() raised exception.
2023-02-11 10:30:40,582 - WARNING - asyncio: socket.send() raised exception.
2023-02-11 10:30:40,816 - ERROR - fhempy.lib.fhem: FHEM took 7437ms for readingsBeginUpdate($defs{'TUYA_JL13'});;
2023-02-11 10:30:40,817 - ERROR - fhempy.lib.fhem: FHEM took 6461ms for readingsBeginUpdate($defs{'TUYA_JL33'});;
2023-02-11 10:30:40,818 - ERROR - fhempy.lib.fhem: FHEM took 6340ms for readingsBulkUpdateIfChanged($defs{'TUYA_JL30'},'cur_current','1571.0');;
2023-02-11 10:30:40,819 - ERROR - fhempy.lib.fhem: FHEM took 5619ms for readingsBeginUpdate($defs{'TUYA_JL18'});;
2023-02-11 10:30:45,731 - WARNING - asyncio: socket.send() raised exception.
2023-02-11 10:30:49,894 - WARNING - asyncio: socket.send() raised exception.
2023-02-11 10:30:50,844 - WARNING - asyncio: socket.send() raised exception.
2023-02-11 10:30:56,007 - WARNING - asyncio: socket.send() raised exception.
2023-02-11 10:30:59,906 - WARNING - asyncio: socket.send() raised exception.
nach raspi-restart wurden TempDevices ca. 30 min gelesen seitedem kein Eintrag mehr
das ist nicht gut
[code]define TUYA_Temp05 fhempy tuya_cloud TUYA bfe1b5bb54592232acz7dg
attr TUYA_Temp05 DbLogExclude .*
attr TUYA_Temp05 DbLogInclude va_temperature,va_humidity
attr TUYA_Temp05 alias TUYA TempHum05 Haustuere
attr TUYA_Temp05 event-min-interval va_temperature:300,va_humidity:300
attr TUYA_Temp05 event-on-change-reading .*
attr TUYA_Temp05 group Temperatur und Feuchtigkeit,Temperatur und Feuchtigkeit aussen
attr TUYA_Temp05 room fhempy,TUYA TempHum
# DEF tuya_cloud TUYA bfe1b5bb54592232acz7dg
# DEVICEID bfe1b5bb54592232acz7dg
# FHEMPYTYPE tuya_cloud
# FUUID 63d77196-f33f-fd5f-4eba-d73a26dc0c44ced2
# IODev local_pybinding
# NAME TUYA_Temp05
# NR 2145
# PYTHONTYPE tuya_cloud
# STATE ready
# TYPE fhempy
# eventCount 2
# Helper:
# DBLOG:
# va_humidity:
# dblog_THB:
# TIME 1676109890.78392
# VALUE 69.0
# va_temperature:
# dblog_THB:
# TIME 1676109890.78392
# VALUE 2.8
# READINGS:
# 2023-02-11 10:59:19 active_time 1672241324
# 2023-02-11 11:04:50 battery_state middle
# 2023-02-11 10:59:19 biz_type 18
# 2023-02-11 10:59:19 category wsdcg
# 2023-02-11 10:59:19 create_time 1672241324
# 2023-02-11 10:59:19 icon https://images.tuyaeu.com/smart/icon/ay1525749833414yotNt/d9d4ceec63cb81ff6e8c8d6c2fb4edb3.png
# 2023-02-11 10:59:19 id bfe1b5bb54592232acz7dg
# 2023-02-11 10:59:19 ip 78.43.212.60
# 2023-02-11 10:59:19 lat 48.5585
# 2023-02-11 10:59:19 local_key 53eb85e1736be53b
# 2023-02-11 10:59:19 lon 9.2025
# 2023-02-11 10:59:19 model TH01 CB3S
# 2023-02-11 10:59:19 name TempHum5 Haustuere
# 2023-02-11 10:59:19 online on
# 2023-02-11 10:59:19 owner_id 3389434
# 2023-02-11 10:59:19 product_id lf36y5nwb8jkxwgg
# 2023-02-11 10:59:19 product_name T & H Sensor
# 2023-02-11 10:58:57 state ready
# 2023-02-11 10:59:19 sub off
# 2023-02-11 11:04:50 temp_unit_convert c
# 2023-02-11 10:59:19 time_zone +01:00
# 2023-02-11 10:59:19 uid eu1548823829280mLHX1
# 2023-02-11 10:59:19 update_time 1674379937
# 2023-02-11 10:59:19 uuid 118ffd24280f8058
# 2023-02-11 11:04:50 va_humidity 69.0
# 2023-02-11 11:04:50 va_temperature 2.8
# args:
# TUYA_Temp05
# fhempy
# tuya_cloud
# TUYA
# bfe1b5bb54592232acz7dg
# argsh:
# helper:
# bm:
# fhempy_Get:
# cnt 1
# dmx -1000
# dtot 0
# dtotcnt 0
# mTS 11.02. 12:40:11
# max 0.00212597846984863
# tot 0.00212597846984863
# mAr:
# HASH(0x56f46f8)
# ARRAY(0x6a62140)
# HASH(0x6826b40)
# fhempy_Set:
# cnt 23
# dmx -1000
# dtot 0
# dtotcnt 0
# mTS 11.02. 11:16:57
# max 0.107030153274536
# tot 0.355092287063599
# mAr:
# HASH(0x56f46f8)
# ARRAY(0x78a8770)
# HASH(0x68674e8)
#
setstate TUYA_Temp05 ready
setstate TUYA_Temp05 2023-02-11 10:59:19 active_time 1672241324
setstate TUYA_Temp05 2023-02-11 11:04:50 battery_state middle
setstate TUYA_Temp05 2023-02-11 10:59:19 biz_type 18
setstate TUYA_Temp05 2023-02-11 10:59:19 category wsdcg
setstate TUYA_Temp05 2023-02-11 10:59:19 create_time 1672241324
setstate TUYA_Temp05 2023-02-11 10:59:19 icon https://images.tuyaeu.com/smart/icon/ay1525749833414yotNt/d9d4ceec63cb81ff6e8c8d6c2fb4edb3.png
setstate TUYA_Temp05 2023-02-11 10:59:19 id bfe1b5bb54592232acz7dg
setstate TUYA_Temp05 2023-02-11 10:59:19 ip 78.43.212.60
setstate TUYA_Temp05 2023-02-11 10:59:19 lat 48.5585
setstate TUYA_Temp05 2023-02-11 10:59:19 local_key 53eb85e1736be53b
setstate TUYA_Temp05 2023-02-11 10:59:19 lon 9.2025
setstate TUYA_Temp05 2023-02-11 10:59:19 model TH01 CB3S
setstate TUYA_Temp05 2023-02-11 10:59:19 name TempHum5 Haustuere
setstate TUYA_Temp05 2023-02-11 10:59:19 online on
setstate TUYA_Temp05 2023-02-11 10:59:19 owner_id 3389434
setstate TUYA_Temp05 2023-02-11 10:59:19 product_id lf36y5nwb8jkxwgg
setstate TUYA_Temp05 2023-02-11 10:59:19 product_name T & H Sensor
setstate TUYA_Temp05 2023-02-11 10:58:57 state ready
setstate TUYA_Temp05 2023-02-11 10:59:19 sub off
setstate TUYA_Temp05 2023-02-11 11:04:50 temp_unit_convert c
setstate TUYA_Temp05 2023-02-11 10:59:19 time_zone +01:00
setstate TUYA_Temp05 2023-02-11 10:59:19 uid eu1548823829280mLHX1
setstate TUYA_Temp05 2023-02-11 10:59:19 update_time 1674379937
setstate TUYA_Temp05 2023-02-11 10:59:19 uuid 118ffd24280f8058
setstate TUYA_Temp05 2023-02-11 11:04:50 va_humidity 69.0
setstate TUYA_Temp05 2023-02-11 11:04:50 va_temperature 2.8
[/code]
als zuletzt um 11:04 eingelesen ; nachdem um 10:40 restartet wurde
die Steckdosen liefern aktuelle werte
Heißt das, die passiven Devices, die du in tuya local verwendest liefern keine Werte? Oder die passiven Devices die du in tuya Cloud verwendest?
Zitat von: dominik am 11 Februar 2023, 13:34:28
Heißt das, die passiven Devices, die du in tuya local verwendest liefern keine Werte? Oder die passiven Devices die du in tuya Cloud verwendest?
es sind alle TempHum-Devices 01 bis 07
01 bis 03 sind stromversorgt, Intervall dynamisch
04 und 05 battery, Intervall 1h
06 und 07 ZigBee
alle sind auf PYTHONTYPE tuya_cloud
alle stehen auf letztes readingchange ca. 11:00
derselbe Effekt wir gestern nach fhem update
in der Vorversion ging das noch
nochmals fhempy update gefahren..
es bleibt dabei es wird wohl nur einmalig ausgelesen:
readingsgroup:
TUYA TempHum01 THOMAS
2023-02-11 18:29:15
T & H Sensor
7akwzwfwhukkdsib
ready
on
10
31.0
TUYA TempHum02 PETRA
2023-02-11 18:29:39
T & H Sensor
7akwzwfwhukkdsib
ready
on
10
39.0
TUYA TempHum03 Wohnzimmer
2023-02-11 18:29:13
Diivoo WiFi Thermometer Hygrometer
jy3ue7qz0zcmmizf
ready
on
10
35.0
TUYA TempHum04 Terrasse
2023-02-11 18:44:16
T & H Sensor
lf36y5nwb8jkxwgg
ready
on
10
61.0
TUYA TempHum05 Haustuere
2023-02-11 19:15:17
T & H Sensor
lf36y5nwb8jkxwgg
ready
on
10
64.0
TempHum06 Treppenhaus oben
2023-02-11 18:29:21
Temperature Humidity Sensor
fllyghyj
ready
on
10
28.1
TempHum07 Küche
2023-02-11 18:32:45
Temperature Humidity Sensor
fllyghyj
ready
on
10
29.1
tuya_system
ready
bei JLs: readingsgroup
JL02 Kaffeemaschine Saecco
2023-02-11 16:57:22
off
1
0.0
0.0
225.3
0.0
JL03 Fernseher Wohnzimmer
2023-02-10 23:56:11
ready
1
269.0
53.9
231.8
0.0
JL04 PC BKT3
2023-02-11 19:32:21
on
1
131.0
16.1
226.5
0.0
JL05 Schreibtisch Petra
ready
1
JL06 frei
2023-01-30 07:59:14
off
1
0.0
0.0
224.0
0.0
JL07 BKT2
2023-01-30 07:59:18
off
1
0.0
0.0
226.9
0.0
ich kriege das bei code leider nicht in Spalten
das alte "Schläferproblem" ?
Das ist seltsam, ich hab auch so einen offline Temperatur und Humidity Sensor.
In der Cloud tut er super, nur local kommt nichts.
Hab gerade nochmal geprüft, hab die neuste Version und der Sensor liefert regelmäßig Daten.
Gruß,
Stefan
Hi Stefan,
dann ist es bei dir genau umgekehrt.
Temp 3 hat sich übrigens gegen 19:48 gemeldet.
Temp01 bis Temp03 messen die Innentemperatur, die sich ja konstant war
Temp04 und Temp05 messen aussen, wo die Temp rapide gefallen ist
Hast du dieselbe productid wie einer von den meinen?
Hi Burkhart,
was genau meinst du mit Produktid?
Hier das list:
Internals:
DEF tuya_cloud tuya_cloud_connector bffa550a829a269630vhcn
DEVICEID bffa550a829a269630vhcn
FHEMPYTYPE tuya_cloud
FUUID 63d3d9cd-f33f-0c45-4616-9afe69334bfac8ce
IODev local_pybinding
NAME tuya_cloud_bffa550a829a269630vhcn
NR 2304
PYTHONTYPE tuya_cloud
STATE </br>Temp: 21.2 C° RF: 48.0 %
</br>Batterie: high
TYPE fhempy
eventCount 8
Helper:
DBLOG:
va_humidity:
logdb:
TIME 1676142622.7511
VALUE 48.0
va_temperature:
logdb:
TIME 1676142622.31355
VALUE 21.2
READINGS:
2023-02-11 19:45:21 active_time 1674825254
2023-02-11 20:10:23 battery_state high
2023-02-11 19:45:21 biz_type 0
2023-02-11 19:45:21 category wsdcg
2023-02-11 19:45:21 create_time 1674825254
2023-02-11 19:45:21 icon https://images.tuyaeu.com/smart/icon/ay1525749833414yotNt/b3a94a9431b68373894805b4a19092e4.png
2023-02-11 19:45:21 id bffa550a829a269630vhcn
2023-02-11 19:45:21 ip 84.188.243.243
2023-02-11 19:45:21 lat 49.6104
2023-02-11 19:45:21 local_key xxxxx
2023-02-11 19:45:21 lon 8.7263
2023-02-11 19:45:21 model TH08CBU
2023-02-11 19:45:21 name T & H Sensor
2023-02-11 19:45:21 online on
2023-02-11 19:45:21 owner_id 39691875
2023-02-11 19:45:21 product_id xlk3mtpjo1zkmdvh
2023-02-11 19:45:21 product_name T & H Sensor
2023-02-11 19:45:17 state ready
2023-02-11 19:45:21 sub off
2023-02-11 20:10:20 temp_unit_convert c
2023-02-11 19:45:21 time_zone +01:00
2023-02-11 19:45:21 uid eu1634560510538qIss1
2023-02-11 19:45:21 update_time 1674825257
2023-02-11 20:10:23 update_time_hr 27.01.2023, 14:14:17
2023-02-11 19:45:21 uuid 21d66a0f7e3333d0
2023-02-11 20:10:22 va_humidity 48.0
2023-02-11 20:10:22 va_temperature 21.2
args:
tuya_cloud_bffa550a829a269630vhcn
fhempy
tuya_cloud
tuya_cloud_connector
bffa550a829a269630vhcn
argsh:
Attributes:
DbLogInclude va_temperature,va_humidity
alias T & H Sensor
group Steckdosen_Tuya
room fhempy
stateFormat </br>Temp: va_temperature C° RF: va_humidity %
</br>Batterie: battery_state
userReadings update_time_hr { timestamp2date(ReadingsVal("tuya_cloud_bffa550a829a269630vhcn","update_time",0)) }
Zitat von: stefanru am 11 Februar 2023, 20:58:50
Hi Burkhart,
was genau meinst du mit Produktid?
Hier das list:
Internals:
DEF tuya_cloud tuya_cloud_connector bffa550a829a269630vhcn
DEVICEID bffa550a829a269630vhcn
FHEMPYTYPE tuya_cloud
FUUID 63d3d9cd-f33f-0c45-4616-9afe69334bfac8ce
IODev local_pybinding
NAME tuya_cloud_bffa550a829a269630vhcn
NR 2304
PYTHONTYPE tuya_cloud
STATE </br>Temp: 21.2 C° RF: 48.0 %
</br>Batterie: high
TYPE fhempy
eventCount 8
Helper:
DBLOG:
va_humidity:
logdb:
TIME 1676142622.7511
VALUE 48.0
va_temperature:
logdb:
TIME 1676142622.31355
VALUE 21.2
READINGS:
2023-02-11 19:45:21 active_time 1674825254
2023-02-11 20:10:23 battery_state high
2023-02-11 19:45:21 biz_type 0
2023-02-11 19:45:21 category wsdcg
2023-02-11 19:45:21 create_time 1674825254
2023-02-11 19:45:21 icon https://images.tuyaeu.com/smart/icon/ay1525749833414yotNt/b3a94a9431b68373894805b4a19092e4.png
2023-02-11 19:45:21 id bffa550a829a269630vhcn
2023-02-11 19:45:21 ip 84.188.243.243
2023-02-11 19:45:21 lat 49.6104
2023-02-11 19:45:21 local_key xxxxx
2023-02-11 19:45:21 lon 8.7263
2023-02-11 19:45:21 model TH08CBU
2023-02-11 19:45:21 name T & H Sensor
2023-02-11 19:45:21 online on
2023-02-11 19:45:21 owner_id 39691875
2023-02-11 19:45:21 product_id xlk3mtpjo1zkmdvh
2023-02-11 19:45:21 product_name T & H Sensor
2023-02-11 19:45:17 state ready
2023-02-11 19:45:21 sub off
2023-02-11 20:10:20 temp_unit_convert c
2023-02-11 19:45:21 time_zone +01:00
2023-02-11 19:45:21 uid eu1634560510538qIss1
2023-02-11 19:45:21 update_time 1674825257
2023-02-11 20:10:23 update_time_hr 27.01.2023, 14:14:17
2023-02-11 19:45:21 uuid 21d66a0f7e3333d0
2023-02-11 20:10:22 va_humidity 48.0
2023-02-11 20:10:22 va_temperature 21.2
args:
tuya_cloud_bffa550a829a269630vhcn
fhempy
tuya_cloud
tuya_cloud_connector
bffa550a829a269630vhcn
argsh:
Attributes:
DbLogInclude va_temperature,va_humidity
alias T & H Sensor
group Steckdosen_Tuya
room fhempy
stateFormat </br>Temp: va_temperature C° RF: va_humidity %
</br>Batterie: battery_state
userReadings update_time_hr { timestamp2date(ReadingsVal("tuya_cloud_bffa550a829a269630vhcn","update_time",0)) }
das hier:
2023-02-11 19:45:21 product_id xlk3mtpjo1zkmdvhist also bei dir ne andere Variante
hier ist übrigens meine readingsgroup DEF für die FHEMPY Devices:
<Device>,<TimeStampCurPower>,<TimeStampTemperatur>,<Produktname>,<ProduktID>,< State >,<online>,<XTime>,<cur_current>,<cur_power>,<cur_voltage>,<Countdown>,<Temperatur>,<Humidity>,<>,<>,<>,<>
TYPE=fhempy:<{ReadingsTimestamp($DEVICE,"cur_power","")}>,<{ReadingsTimestamp($DEVICE,"va_temperature","")}>,product_name,product_id,state,online,cur_current,cur_power,cur_voltage,countdown_1,temperature,va_temperature,va_humidity,humidity_valueist noch keineswegs perfekt..
ich weiß nicht, wie man leere Spalten darstellt
Für was brauchst du da eine Readings Group?
Bei mir sieht das so aus wie im Anhang.
Arbeite mit stateFormat.
Readingsgroup ist natürlich auch gut.
Readingsgroup formatieren kannst du mit cellStyle.
Gruß,
Stefan
Zitat von: stefanru am 12 Februar 2023, 00:15:30
Für was brauchst du da eine Readings Group?
Bei mir sieht das so aus wie im Anhang.
Arbeite mit stateFormat.
Readingsgroup ist natürlich auch gut.
Readingsgroup formatieren kannst du mit cellStyle.
Gruß,
Stefan
sieht gut aus ; ich möchte eben ProductID und weitere non StandardReadings in der Übersicht sehen.
hast du bitte deinen DEF-Code von deinen stateFormaten? besonders würde mich die Darstellung der letzten Update-Time interessieren
hg Thomas
Ah ok ich verstehe du willst da ne Tabelle mit allen möglichen Daten anzeigen.
Da ist readingsGroup vielleicht schon besser.
Hier trotzdem mal die Definition von stateFormat mit HTML:
state </br>
</br>cur_voltage V
</br>cur_power W
</br>cur_current mA
P.S:
@Dominik: Muss mal Danke sagen! Vielen Dank bei mir tut fhempy jetzt einwandfrei.
Keine Logmeldungen mehr. Auch scheint es das System nicht mehr so zu stressen.
Eine Sache ist mir aufgefallen.
Ich musste ein addLog für die Steckdosen einbauen da sie keine Events mehr lieferten wenn der Wert (in meinem Fall cur_power) sich nicht ändert.
Aber das ist ja gut. Unnötige Events belasten das System
Also nochmals vielen Dank für deine Mühe.
Gruß,
Stefan
@dominik
ich habe gegen 13:00 nochmals shutdown restart gemacht.
das sind die aktuellen states meiner TempHums:
Temperatur und Feuchtigkeit
TUYA TempHum01 THOMAS
Temp: 23.5 °C, Hum: 33.0 %, Update: 2023-02-12 13:15:20, PID: 7akwzwfwhukkdsib, PName: T & H Sensor
TUYA TempHum02 PETRA
Temp: 19.2 °C, Hum: 41.0 %, Update: 2023-02-12 13:14:40, PID: 7akwzwfwhukkdsib, PName: T & H Sensor
TUYA TempHum03 Wohnzimmer
Temp: 22.3 °C, Hum: 38.0 %, Update: 2023-02-12 14:21:05, PID: jy3ue7qz0zcmmizf, PName: Diivoo WiFi Thermometer Hygrometer
TempHum06 Treppenhaus oben
Temp: 20.8 °C, Hum: 30.2 %, Update: 2023-02-12 13:29:16, PID: fllyghyj, PName: Temperature Humidity Sensor
TempHum07 Küche
Temp: 21.1 °C, Hum: 33.0 %, Update: 2023-02-12 13:32:40, PID: fllyghyj, PName: Temperature Humidity Sensor
spätestens 14:21 und in der Mehrzahl spätestens 13:29 haben alle TempHums beschlossen, fhempy nicht mehr zu melden
also durchgängig dasselbe Bild seit der zu testenden neuen Version.
Steckdosen laufen super
beste Grüße und vielen Dank
Thomas
Kann es sein, dass sich die Temperatur nicht geändert hat? Weil die Readings werden nur mehr aktualisiert, wenn sich ein Wert geändert hat.
Ich hatte das eingebaut, da deine Devices ziemlich oft Updates aus der Cloud erhalten. Ich weiß nicht warum, aber das ist schon etwas eigenartig. Aktiviere bei dir mal PULSAR - Link dazu ist in der Fehlermeldung enthalten. Weil Pulsar ist der präferierte Weg von Tuya Events zu bekommen.
Zitat von: dominik am 13 Februar 2023, 18:39:15
Kann es sein, dass sich die Temperatur nicht geändert hat? Weil die Readings werden nur mehr aktualisiert, wenn sich ein Wert geändert hat.
Ich hatte das eingebaut, da deine Devices ziemlich oft Updates aus der Cloud erhalten. Ich weiß nicht warum, aber das ist schon etwas eigenartig. Aktiviere bei dir mal PULSAR - Link dazu ist in der Fehlermeldung enthalten. Weil Pulsar ist der präferierte Weg von Tuya Events zu bekommen.
bei TempHum04/05 handelt es sich um Außentenperaturen, die sich doch kräftig änderen:
ein Updaten erfolgt jedoch nur nach shutdown restart
Temperatur und Feuchtigkeit
TUYA TempHum01 THOMAS
Temp: 21.1 °C, Hum: 35.0 %, Update: 2023-02-13 19:52:32, PID: 7akwzwfwhukkdsib, PName: T & H Sensor
TUYA TempHum02 PETRA
Temp: 19.0 °C, Hum: 39.0 %, Update: 2023-02-13 19:52:38, PID: 7akwzwfwhukkdsib, PName: T & H Sensor
TUYA TempHum03 Wohnzimmer
Temp: 21.3 °C, Hum: 37.0 %, Update: 2023-02-13 19:52:31, PID: jy3ue7qz0zcmmizf, PName: Diivoo WiFi Thermometer Hygrometer
TUYA TempHum04 Terrasse
Temp: 3.2 °C, Hum: 71.0 %, Update: 2023-02-13 19:52:35, PID: lf36y5nwb8jkxwgg, PName: T & H Sensor
TUYA TempHum05 Haustuere
Temp: 3.4 °C, Hum: 72.0 %, Update: 2023-02-13 19:52:29, PID: lf36y5nwb8jkxwgg, PName: T & H Sensor
TempHum06 Treppenhaus oben
Temp: 20.5 °C, Hum: 29.4 %, Update: 2023-02-13 19:52:33, PID: fllyghyj, PName: Temperature Humidity Sensor
TempHum07 Küche
Temp: 20.6 °C, Hum: 31.4 %, Update: 2023-02-13 19:52:30, PID: fllyghyj, PName: Temperature Humidity Sensorich sehe das auch an den Gplots und in der SmartlifeApp
TempHum04 hatte gegen 14:00 frühlingshafte 14 Grad
Zitat von: dominik am 13 Februar 2023, 18:39:15
Kann es sein, dass sich die Temperatur nicht geändert hat? Weil die Readings werden nur mehr aktualisiert, wenn sich ein Wert geändert hat.
Ich hatte das eingebaut, da deine Devices ziemlich oft Updates aus der Cloud erhalten. Ich weiß nicht warum, aber das ist schon etwas eigenartig. Aktiviere bei dir mal PULSAR - Link dazu ist in der Fehlermeldung enthalten. Weil Pulsar ist der präferierte Weg von Tuya Events zu bekommen.
bei TempHum04/05 handelt es sich um Außentenperaturen, die sich doch kräftig änderen:
ein Updaten erfolgt jedoch nur nach shutdown restart
Temperatur und Feuchtigkeit
TUYA TempHum01 THOMAS
Temp: 21.1 °C, Hum: 35.0 %, Update: 2023-02-13 19:52:32, PID: 7akwzwfwhukkdsib, PName: T & H Sensor
TUYA TempHum02 PETRA
Temp: 19.0 °C, Hum: 39.0 %, Update: 2023-02-13 19:52:38, PID: 7akwzwfwhukkdsib, PName: T & H Sensor
TUYA TempHum03 Wohnzimmer
Temp: 21.3 °C, Hum: 37.0 %, Update: 2023-02-13 19:52:31, PID: jy3ue7qz0zcmmizf, PName: Diivoo WiFi Thermometer Hygrometer
TUYA TempHum04 Terrasse
Temp: 3.2 °C, Hum: 71.0 %, Update: 2023-02-13 19:52:35, PID: lf36y5nwb8jkxwgg, PName: T & H Sensor
TUYA TempHum05 Haustuere
Temp: 3.4 °C, Hum: 72.0 %, Update: 2023-02-13 19:52:29, PID: lf36y5nwb8jkxwgg, PName: T & H Sensor
TempHum06 Treppenhaus oben
Temp: 20.5 °C, Hum: 29.4 %, Update: 2023-02-13 19:52:33, PID: fllyghyj, PName: Temperature Humidity Sensor
TempHum07 Küche
Temp: 20.6 °C, Hum: 31.4 %, Update: 2023-02-13 19:52:30, PID: fllyghyj, PName: Temperature Humidity Sensorich sehe das auch an den Gplots und in der SmartlifeApp
TempHum04 hatte gegen 14:00 frühlingshafte 14 Grad
Zitat von: dominik am 13 Februar 2023, 18:39:15
Aktiviere bei dir mal PULSAR - Link dazu ist in der Fehlermeldung enthalten. Weil Pulsar ist der präferierte Weg von Tuya Events zu bekommen.
habe ich gemacht
Bin gerade dabei an der Basis von fhempy der Websocket Kommunikation - die der ursprüngliche Fehler bei dir war - ein paar Optimierungen zu machen. Ich melde mich sobald das fertig ist, dann kann ich mir das genauer mit den tuya Devices anschauen.
Zitat von: dominik am 14 Februar 2023, 00:20:22
Bin gerade dabei an der Basis von fhempy der Websocket Kommunikation - die der ursprüngliche Fehler bei dir war - ein paar Optimierungen zu machen. Ich melde mich sobald das fertig ist, dann kann ich mir das genauer mit den tuya Devices anschauen.
eben stelle ich fest, dass wie von Geisterhand auch die TempHums bei mir regelmäßig gelesen werden..
dies seit ca. 13 Uhr
da hatte ich meinen CUL und meinen JEELINK mit USB-Kabel verlängert und besser positioniert.
Vor wenigen Tagen hatte ich meinen RASPI im Hausflur positioniert
Dies könnte die Ursache sein für die InStabilität von FHEMPY sein.
Ich beobachte mal weiter
Hallo Seit heute Nacht werden keiner meiner States aktualisiert
Ich schalte eine Steckdose ein State geht auf on
Ich schalte diese wieder aus State bleibt auf on
Somit kann ich diese nicht mehr über den Schalter schalten nur mehr über set befehl aber da ändert sich der State auch nicht
Hat das auch jemand?
Hab das noch Gefunden
2023.02.17 17:31:05 1: BindingsIo (local_pybinding): ERROR JSON: malformed JSON string, neither tag, array, object, number, string or atom, at character offset 0 (before "\x{3}\x{ef}\x{bf}\x{bd}") at /usr/share/perl5/JSON.pm line 190.
2023.02.17 17:31:05 1: BindingsIo (local_pybinding): received JSON was: �
Hoffe es hilft weiter
Testet bitte mit der aktuellen Version: 0.1.598.
Wichtig: Auch ein fhem update machen! Danach shutdown restart.
Die Version sollte keinerlei NO RESPONSE Fehler mehr bringen und auch die Aufrufe der Seiten mit fhempy Device sollte spürbar schneller sein.
Zitat von: dominik am 17 Februar 2023, 21:20:39
Testet bitte mit der aktuellen Version: 0.1.598.
Wichtig: Auch ein fhem update machen! Danach shutdown restart.
Die Version sollte keinerlei NO RESPONSE Fehler mehr bringen und auch die Aufrufe der Seiten mit fhempy Device sollte spürbar schneller sein.
2023-02-17 21:33:05,650 - INFO - fhempy.lib.fhem_pythonbinding: Start update...
2023-02-17 21:33:05,651 - INFO - fhempy.lib.pkg_installer: Attempting install of fhempy
2023-02-17 21:33:18,744 - INFO - fhempy.lib.pkg_installer: Successfully installed fhempy update!
2023-02-17 21:33:18,944 - INFO - fhempy.lib.fhem_pythonbinding: Restart initiated...
2023-02-17 21:33:18,964 - INFO - fhempy.lib.fhem_pythonbinding: All modules successfully undefined!
2023-02-17 21:33:18,965 - INFO - websockets.server: server closing
2023-02-17 21:33:28,969 - INFO - websockets.server: connection closed
2023-02-17 21:33:28,969 - INFO - websockets.server: server closed
2023-02-17 21:33:28,971 - INFO - fhempy.lib.fhem_pythonbinding: Exit 1
2023-02-17 21:33:30,192 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.598...
2023-02-17 21:33:30,196 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-02-17 21:33:30,226 - INFO - websockets.server: server listening on 0.0.0.0:15733
2023-02-17 21:33:39,131 - INFO - websockets.server: connection open
2023-02-17 21:33:39,132 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2023-02-17 21:36:07,246 - INFO - fhempy.lib.fhem_pythonbinding: Start update...
2023-02-17 21:36:07,249 - INFO - fhempy.lib.pkg_installer: Attempting install of fhempy
2023-02-17 21:36:18,719 - INFO - fhempy.lib.pkg_installer: Successfully installed fhempy update!
2023-02-17 21:36:18,922 - INFO - fhempy.lib.fhem_pythonbinding: Restart initiated...
2023-02-17 21:36:18,942 - ERROR - fhempy.lib.fhem: Failed to set result, received: {'result': 1, 'awaitId': 23942669, 'error': 0}
2023-02-17 21:36:18,943 - INFO - fhempy.lib.fhem_pythonbinding: All modules successfully undefined!
2023-02-17 21:36:18,944 - INFO - websockets.server: server closing
2023-02-17 21:36:28,948 - INFO - websockets.server: connection closed
2023-02-17 21:36:28,948 - INFO - websockets.server: server closed
2023-02-17 21:36:28,950 - INFO - fhempy.lib.fhem_pythonbinding: Exit 1
2023-02-17 21:36:30,163 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.598...
2023-02-17 21:36:30,167 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-02-17 21:36:30,196 - INFO - websockets.server: server listening on 0.0.0.0:15733
2023-02-17 21:36:39,503 - INFO - websockets.server: connection open
2023-02-17 21:36:39,503 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2023-02-17 21:37:14,795 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.598...
2023-02-17 21:37:14,799 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-02-17 21:37:14,840 - INFO - websockets.server: server listening on 0.0.0.0:15733
2023-02-17 21:37:21,782 - INFO - websockets.server: connection open
2023-02-17 21:37:21,782 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
sieht gut aus :-)
keine Fehler im fhem.log
danke, Dominik
auch keine 10fachen Werte mehr bei den JLxx :-)
und die TEmps werden korrekt aktualisiert :-)
super !!
erkläre FMEMPY für stabil :-)
freue mich auf Kumulierung power
wenn's übers Wochenende stabil läuft, kann ich power angehen. Dieses Wochenende ist leider vollgeplant, da komm ich leider zu nix.
Merkst du schnellere Ladezeiten der Seiten im fhemweb, dort wo du ca. 100 Devices hast?
Zitat von: dominik am 17 Februar 2023, 22:34:31
wenn's übers Wochenende stabil läuft, kann ich power angehen. Dieses Wochenende ist leider vollgeplant, da komm ich leider zu nix.
Merkst du schnellere Ladezeiten der Seiten im fhemweb, dort wo du ca. 100 Devices hast?
es geht blitzartig :-)
begeisternd!
Hallo Dominik,
nun habe ich mein ganzes System nach dem Upgrade von Stretch auf Bullseye und dem Upgrade auf Python 3.9.16 wieder korrekt ans Laufen gebracht.
Ich hoffe, dass ich nun alle Prozesse korrekt getestet habe, inklusive Tuya Cloud und dem Kesser Radiator. Irgendetwas fällt ja später immer noch mal auf.
Jetzt möchte ich den Radiator ähnlich meiner Fußbodenheizung mit PWMR steuern.
Dabei musste ich leider feststellen, dass der Radiator alle Anweisungen entgegen nimmt und auch korrekt ausführt, aber keine Rückmeldung liefert. Die Readings werden nur einmal beim Starten des fhempyservers gesetzt, es gibt auch im Eventmonitor keine weiteren Events.
Da der Radiator 80 km entfernt steht, prüfe ich das mit der Tuya App auf dem Mobiltelefon. In der App gibt der Radiator die Statusänderungen korrekt an, Einschaltzustand, Solltemperatur, Isttemperatur usw.
Gibt es eine Möglichkeit den Radiator über fhempy zyklisch zu pollen, um immer den aktuellen Status zu bekommen?
Ich habe jetzt erst einmal eine "Hilfskrücke" eingeführt, in dem ich den Server mit einem at device alle 5 min restarte und dann immer aktuelle Werte bekomme.
Aber das ist sicher nicht die beste Lösung. Demnächst kommen auch Tuya Thermometer dazu.
Viele Grüße
Werner
Schau bitte ob im fhempy Log ein Fehler mit "Pulsar" drin steht. Wenn ja, bitte den Anweisungen dort folgen.
Hallo Dominik,
das steht im fhem-logfile:
2023.02.18 00:27:34 1: BindingsIo (fhempy_local): ERROR JSON: malformed JSON string, neither tag, array, object, number, string or atom, at character offset 0 (before "\x{3}\x{ef}\x{bf}\x{bd}") at /usr/share/perl5/JSON.pm line 190.
und das im fhempyserver-log
websocket: Handshake status 401 Unauthorized - goodbye
2023-02-18 00:32:54,362 - ERROR - tuya_cloud_connector: Please activate OpenPulsar: https://developer.tuya.com/en/docs/iot/subscribe-mq?id=Kavqcrvckbh9h
Ich werde morgen auf der tuya development platform nachschauen.
Danke für den Tip.
Viele Grüße
Werner
Hast du fhem heute aktualisiert? Wenn nicht, dann bitte fhem update machen. Ein JSON Fehler darf nicht mehr kommen.
Zitat von: dominik am 17 Februar 2023, 21:20:39
Testet bitte mit der aktuellen Version: 0.1.598.
Wichtig: Auch ein fhem update machen! Danach shutdown restart.
Die Version sollte keinerlei NO RESPONSE Fehler mehr bringen und auch die Aufrufe der Seiten mit fhempy Device sollte spürbar schneller sein.
meine TempHums zicken doch noch rum:
Temperatur und Feuchtigkeit
TUYA TempHum01 THOMAS
Temp: 20.9 °C, Hum: 36.0 %, Update: 2023-02-18 09:55:01, PID: 7akwzwfwhukkdsib, PName: T & H Sensor
TUYA TempHum02 PETRA
Temp: 19.6 °C, Hum: 48.0 %, Update: 2023-02-18 03:14:44, PID: 7akwzwfwhukkdsib, PName: T & H Sensor
TUYA TempHum03 Wohnzimmer
Temp: 22.5 °C, Hum: 47.0 %, Update: 2023-02-17 21:56:53, PID: jy3ue7qz0zcmmizf, PName: Diivoo WiFi Thermometer Hygrometer
!!!!!!!!!! TUYA TempHum04 Terrasse
Temp: 11.4 °C, Hum: 76.0 %, Update: 2023-02-17 22:03:17, PID: lf36y5nwb8jkxwgg, PName: T & H Sensor
!!!!!!!!!! TUYA TempHum05 Haustuere
Temp: 11.9 °C, Hum: 71.0 %, Update: 2023-02-17 21:54:31, PID: lf36y5nwb8jkxwgg, PName: T & H Sensor
TempHum06 Treppenhaus oben
Temp: 20.8 °C, Hum: 39.8 %, Update: 2023-02-18 09:28:34, PID: fllyghyj, PName: Temperature Humidity Sensor
!!!!!!!!!!! TempHum07 Küche
Temp: 21.1 °C, Hum: 38.4 %, Update: 2023-02-17 21:40:16, PID: fllyghyj, PName: Temperature Humidity Sensorgvielleicht haben sich die Daten doch nicht seit 22:00 geändert
Pulsar hast du schon aktiviert?
Zitat von: dominik am 18 Februar 2023, 00:05:09
Schau bitte ob im fhempy Log ein Fehler mit "Pulsar" drin steht. Wenn ja, bitte den Anweisungen dort folgen.
habe den Message Service aktiviert, jetzt funktionert es, habe das at-device wieder gelöscht.
Viele Grüße
Werner
Zitat
Hast du fhem heute aktualisiert? Wenn nicht, dann bitte fhem update machen. Ein JSON Fehler darf nicht mehr kommen.
habe ich jetzt getan, werde das Log beobachten.
Viele Grüße
Werner
Guten Abend Dominik,
seit dem Update ist kein ERROR JSON mehr vorgekommen.
Nach der Aktivierung des Message Services und dem fhem update scheint jetzt mit fhempy Tuya Cloud alles zu funktionieren.
Nun warte ich auf die weiteren Tuya-fähigen Elemente (Thermometer, Schalter und Geräte), die ich dann alle aus der Ferne steuern muss.
Vielen Dank für Deine Hilfe
Viele Grüße
Werner
Hi Dominik,
nach dem Update auf 0.1.598 und FHEM update sowie einem FHEM stop und start,
habe ich folgendes im fhempy.log gefunden, die genannte Steckdose arbeitet ohne Probleme.
2023-02-19 16:33:15,769 - INFO - websocket: Websocket connected
2023-02-19 16:33:21,535 - ERROR - Fernseher_Schlafzimmer_bf4f644bc7dd2fc71d9q52: 'tuya_cloud_device' object has no attribute '_t_specification'
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 294, in update_readings_arr
self._convert_value2fhem(status["code"], status["value"]),
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 244, in _convert_value2fhem
for code_def in self._t_specification["status"]:
AttributeError: 'tuya_cloud_device' object has no attribute '_t_specification'
Gruß,
Stefan
Kannst du mir bitte noch das Define des Devices posten?
Hi Dominik,
seltsam daran ist dass ich 4 Stück dieser Steckdosen mit Power Metering habe.
Alle genau gleich.
Nur die eine hat bei dem Startup den Fehler gezeigt.
Hier das List:
Internals:
DEF tuya_cloud tuya_cloud_connector bf4f644bc7dd2fc71d9q52
DEVICEID bf4f644bc7dd2fc71d9q52
FHEMPYTYPE tuya_cloud
FUUID 61a9066a-f33f-0c45-b078-df23495ef66d3ad5
IODev local_pybinding
NAME Fernseher_Schlafzimmer_bf4f644bc7dd2fc71d9q52
NR 2018
PYTHONTYPE tuya_cloud
STATE off </br>
</br>233.1 V
</br>0.0 W
</br>0.0 mA
TYPE fhempy
eventCount 3790
Helper:
DBLOG:
cur_power:
logdb:
TIME 1676888463.89334
VALUE 0.0
READINGS:
2023-02-20 00:36:56 active_time 1638458218
2023-02-20 11:25:07 add_ele 0.014
2023-02-20 00:36:56 biz_type 0
2023-02-20 00:36:56 category cz
2023-02-20 08:54:40 child_lock off
2023-02-20 08:54:40 countdown_1 0.0
2023-02-20 00:36:56 create_time 1638458218
2023-02-20 11:00:20 cur_current 0.0
2023-02-20 11:00:20 cur_power 0.0
2023-02-20 11:35:32 cur_voltage 233.1
2023-02-20 08:54:40 cycle_time
2023-02-20 00:36:56 icon https://images.tuyaeu.com/smart/icon/ay15148582002916nitB/c58a91c23c2e2b5309c7c5d776871390.png
2023-02-20 00:36:56 id bf4f644bc7dd2fc71d9q52
2023-02-20 00:36:56 ip 87.158.205.193
2023-02-20 00:36:56 lat 49.6104
2023-02-20 08:54:40 light_mode relay
2023-02-20 00:36:56 local_key 8cf0099962d0ff3f
2023-02-20 00:36:56 lon 8.7262
2023-02-20 00:36:56 model BSD34BP
2023-02-20 00:36:56 name Fernseher Schlafzimmer
2023-02-20 00:36:56 online on
2023-02-20 08:54:40 overcharge_switch off
2023-02-20 00:36:56 owner_id 39691875
2023-02-20 00:36:56 product_id apszn7k8yhgsin28
2023-02-20 00:36:56 product_name WIFI 插座
2023-02-20 08:54:40 random_time
2023-02-20 08:54:40 relay_status power_off
2023-02-20 11:00:14 state off
2023-02-20 00:36:56 sub off
2023-02-03 10:58:09 switch_1 on
2023-02-20 08:54:40 switch_inching
2023-02-20 00:36:56 time_zone +01:00
2023-02-20 00:36:56 uid eu1634560510538qIss1
2023-02-20 00:36:56 update_time 1640052277
2023-02-20 00:36:56 uuid 1b3479720033efbe
args:
Fernseher_Schlafzimmer_bf4f644bc7dd2fc71d9q52
fhempy
tuya_cloud
tuya_cloud_connector
bf4f644bc7dd2fc71d9q52
argsh:
Attributes:
DbLogInclude cur_power:60:force
alexaName Fernseher Schlafzimmer
alexaRoom OG
alias Fernseher Schlafzimmer
event-min-interval .*:300
event-on-change-reading .*
group Steckdosen_Tuya
room OG,fhempy
stateFormat state </br>
</br>cur_voltage V
</br>cur_power W
</br>cur_current mA
Gruß und Danke,
Stefan
Hallo Dominik,
von Tuya habe ich folgende Email bekommen, die Du sicher auch immer bekommst und Dir bekannt ist.
Zitat
Tuya IoT Platform Service Expiration Notice
Dear Tuya IoT Platform Account Manager,
The service IoT Core you subscribed to will expire on 2023-02-21,If you need to continue to use,please renew this service.
How to renew your contract:
Please check the services you subscribe to and select the corresponding expired / expiring services to renew:
www.tuya.com/vas/user/service
You have received this email because you are the account owner of the Tuya IoT platform and you have the right to know the changes of service information on the platform. If you do not use the above services in a business environment，you can ignore this email notification.
If the above instructions cannot conduct through the relevant operation, please contact your business manager or submit a help ticket on the Tuya IoT Platform.
This email is automatically sent by the system. Please do not reply. If you have any questions, please contact customer service.Contact: service@tuya.com
Sincerely,
Muss ich jetzt regelmäßig die Services erneuern, damit fhempy mit Tuya-Cloud weiter funktioniert?
Wenn ja, welche Services brauche ich wirklich und welche kann ich auslaufen lassen?
Viele Grüße
Werner
Mein Ablaufdatum war 2022-07-28 14:54:05 und ich hab nix gemacht. Es steht bei mir noch immer "In service" und dort dann "contract expired". Solange es funktioniert, mach ich daher nix :)
Alles klar,
Danke
Zitat von: dominik am 20 Februar 2023, 22:10:25
Mein Ablaufdatum war 2022-07-28 14:54:05 und ich hab nix gemacht. Es steht bei mir noch immer "In service" und dort dann "contract expired". Solange es funktioniert, mach ich daher nix :)
Bei mir funktioniert es so leider nicht.
Siehe Screenshot in der Anlage
Du solltest aber online verlängern können, denke ich.
Bei Änderung der Einstellungen in der App auf dem Mobiltelefon werden die Rückmeldungen von fhem noch entgegengenommen und in den Readings und im Logfile angezeigt. Aber etwas mit set ... einstellen geht nicht mehr.
Auch nach dem Restart vom Server und / oder fhempy_local die nach dem Verbinden und der Meldung ready beim Radiator anschließend die gleiche Meldung No permission. ...
Ich habe auch versucht in der Tuya PLatform alles wieder zu reaktivieren, aber erfolglos.
Hast Du einen Tip für mich
Viele Grüße
Werner
Zitat von: dominik am 21 Februar 2023, 22:18:12
Du solltest aber online verlängern können, denke ich.
Ist mir leider nicht gelungen. Der Trial-Mode geht offenbar nur einen Monat.
die Services neu kaufen, kostet enorm viel Geld.
Viele Grüße Werner
Ich schreibe Dir eine Mitteilung. Kannst ja mal versuchen.
Ich hoffe, die Mitteilung ist angekommen, ich kann sie im Ausgang nicht finden.
Ich hab mal extend trial period angefragt mit deinem Account. Ich glaube sowas habe ich auch mal gemacht.
Hallo dominik,
wo kann man das anfragen und welche Reaktion auf deine Anfrage erwartest du.
Eine Email dazu habe ich nicht bekommen.
Ich habe auch so ziemlich alles versucht und alle Help Informationen dazu durchsucht,
aber keine Möglichkeit gefunden die trial period von 1 month zu verlängern.
Mir fällt nichts weiter ein, als einen neuen Account einzurichten.
Aber ich kann doch nicht jeden Monat einen neuen Account mit neuer EMail Adresse einrichten.
Viele Grüße
Werner
Bei Service expired gibt es den Button Extend Trial Period, dort drückt man drauf.
Deswegen besser auf tuya local umsteigen bzw. mit den ZigBee Devices auf zigbee2mqtt.
Danke Dir, es geht wieder.
Wenn ich das richtig verstanden habe, geht local nur im gleichen WLAN.
Die devices, die ich steuern möchte, sind aber 80 km entfernt.
Bei local sehe ich dann nur eine Möglichkeit:
einen 2. Raspi dort im Wlan und dann über Teamviewer von hier bedienen.
Zigbee hilft mir leider nicht weiter. Bei den Geräten bin ich schon darauf angewiesen, was diese unterstützen,
der Radiator, den ich wegen der Features ausgesucht habe (Kesser), wird z.B. mit der Tuya App gesteuert.
Wegen der Entfernung und der dynamischen IP-Adresse muss ich schon über eine Cloud gehen.
Viele Grüße
Werner
Werner
Zitat von: dominik am 22 Februar 2023, 07:41:55
Bei Service expired gibt es den Button Extend Trial Period, dort drückt man drauf.
Deswegen besser auf tuya local umsteigen bzw. mit den ZigBee Devices auf zigbee2mqtt.
Ich habe alles durchgesucht, den Punkt Service expired habe ich in keinem Menuepunkt gefunden.
Falls ich den Button später noch mal drücken muss, sollte ich wissen wie es geht.
Wie kommt man zu diesem Punkt in der Tuya Platform?
Viele Grüße
Werner
Cloud - Development
Projekt auswählen
Service API
IoT Core - View Details
...und dort sieht man dann den Button
Hallo Dominik,
bei dem Punkt war ich vorher schon ein paar mal.
Da habe ich sicher irgendetwas falsch gemacht.
Ich habe jetzt noch einen expired service herausgesucht,
in der Anlage die Screencopy von View Details.
leider kein Button Extend Trial period.
Was ist falsch?
Viele Grüße
Werner
Meine Empfehlung, wenn es läuft und du keine Fehler hast, einfach nix angreifen :) Es bringt nix die ausgelaufenen Service - die funktionieren - jetzt nochmals bei tuya zu verlängern. Wer weiß auf welche Liste du sonst kommst....
IoT Core ist der Hauptservice den man braucht. Device Log Query braucht man imho nicht.
Hi Dominik,
habe eben auf 0.1.605 geupdatet und was soll ich sagen.
100% sauberer Start :-)
2023-02-22 22:06:23,154 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.605...
2023-02-22 22:06:23,158 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-02-22 22:06:23,185 - INFO - websockets.server: server listening on 0.0.0.0:15733
2023-02-22 22:06:27,436 - INFO - websockets.server: connection open
2023-02-22 22:06:27,437 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2023-02-22 22:06:29,862 - INFO - websocket: Websocket connected
Vielen Dank dafür!
Das energy Reading ist bei local vorhanden aber nicht bei cloud.
Denke das ist so gewollt?
Lege keinen großen Wert auf das reading und habe zur Zeit Cloud und Local parallel am laufen.
Nochmals vielen Dank und Gruß,
Stefan
Super, danke für das Feedback!
Für tuya_cloud hat noch niemand wegen energy nachgefragt ;) ich bau es später noch ein, kommt dann mit dem nächsten Update.
Hallo Dominik,
Deinen Rat werde ich befolgen. Never change the running system.
Es funktioniert jetzt alles einwandfrei.
Viele Grüße
Werner
Ich beiß gleich in die Tischplatte. Der fhempy server verabschiedet sich ständig leise, die Tuya-Geräte melden "fhempy server offline" aber fhempy local und server devices strahlen grün. im fhem log steht nichts sinnvolles (zB, "fhempy: bin dann mal weg") und im fhempy log auch nicht. Habe jetzt erfolgreich 21 Tuya-Geräte aus der China-Cloud befreit und hinter dem Firewall versteckt, aber wenn der fhempy server sich immer verabschiedet (ohne leise "servus" zu sagen 😕 ) dann macht das keinen Spass mehr. Behindert auch ungemein das Debugger, warum die Devices nicht mehr von Alexa gesteuert werden können (läuft jetzt der server noch, oder nicht?).
HELP
Ich habe 0.1.606 aktualisiert, der update Knopf geht übrigens bei mir auch nicht...
Wohin kann ich schauen, um zu sehen, was hier los ist? Wenn der Server nach "shutdown restart" wieder läuft, gehen die Devices mit on/off problemlos. Wie gesagt, trotz genericDeviceType switch sagt Alexa "<Device Name> unterstützt das nicht".
Zitat von: Nomo am 28 Februar 2023, 13:36:03
Ich beiß gleich in die Tischplatte. Der fhempy server verabschiedet sich ständig leise, die Tuya-Geräte melden "fhempy server offline" aber fhempy local und server devices strahlen grün. im fhem log steht nichts sinnvolles (zB, "fhempy: bin dann mal weg") und im fhempy log auch nicht. Habe jetzt erfolgreich 21 Tuya-Geräte aus der China-Cloud befreit und hinter dem Firewall versteckt, aber wenn der fhempy server sich immer verabschiedet (ohne leise "servus" zu sagen 😕 ) dann macht das keinen Spass mehr. Behindert auch ungemein das Debugger, warum die Devices nicht mehr von Alexa gesteuert werden können (läuft jetzt der server noch, oder nicht?).
HELP
Ich habe 0.1.606 aktualisiert, der update Knopf geht übrigens bei mir auch nicht...
Wohin kann ich schauen, um zu sehen, was hier los ist? Wenn der Server nach "shutdown restart" wieder läuft, gehen die Devices mit on/off problemlos. Wie gesagt, trotz genericDeviceType switch sagt Alexa "<Device Name> unterstützt das nicht".
verwendest Du nun tuya_cloud oder tuya_local ?
der ALEXA-Skill kann meines Wissens nur mit der TUYA-Cloud .
Würde mich jedoch sehr, sehr gerne eines Besseren belehren lassen
wie geht das ?
Ich verwende tuya, also nicht tuya_cloud
define tuya_system fhempy tuya setup xxxxx
Und ja, ich kann manche tuya devices manchmal steuern, über Alexa. Vielleicht liegt es daran, dass manche noch Zugang zum Internet hatten, das probiere ich gleich aus.
Und wieder leuchtet der fhempyserver grün und die Geräte melden alle offline 😥 und kill&restart geht natürlich nicht, also shutdown restart :-\
Zitat von: Nomo am 28 Februar 2023, 14:54:33
Ich verwende tuya, also nicht tuya_cloud
define tuya_system fhempy tuya setup xxxxx
Und ja, ich kann manche tuya devices manchmal steuern, über Alexa. Vielleicht liegt es daran, dass manche noch Zugang zum Internet hatten, das probiere ich gleich aus.
Und wieder leuchtet der fhempyserver grün und die Geräte melden alle offline 😥 und kill&restart geht natürlich nicht, also shutdown restart :-\
dann verwende doch auch den Thread zu tuya(local)https://forum.fhem.de/index.php/topic,127441.msg1265880.html#new (https://forum.fhem.de/index.php/topic,127441.msg1265880.html#new)
dort siehst du auch die neuesten Entwicklungen zu tuya_local
das Problem, dass nur mache Geräte von fhempy erkannt wurden; habe ich dadurch beheben können, die devices in der fhem.cfg mit ctrl-Q auszukommentieren (um indiv. Einstellungen wiederherstellen zu können)
Danach wurden nach FHEM shutdown restart und einiger Wartezeit die Devices neu eingelesen. Dann manuell "scandevices" und "create devices"
Voraussetzung ist natürlich die neueste Version ...10
Sorry, da hast Du natürlich recht. Habe den Thread genommen, den mir die Such-Funktion gefunden hat, als ich nach "fhempy server offline" gesucht habe. Ich schau mir mal den anderen thread an.
Hallo Dominik,
mein Temp04 bleibt beharrlich auf nur "ready"
[code]define TUYA_Temp04 fhempy tuya_cloud TUYA bf0982f08295070ae7tulb
attr TUYA_Temp04 DbLogExclude .*
attr TUYA_Temp04 DbLogInclude va_humidity,va_temperature
attr TUYA_Temp04 alias TUYA TempHum04 Terrasse
attr TUYA_Temp04 group Temperatur und Feuchtigkeit,tuya_cloud
attr TUYA_Temp04 room TUYA TempHum,fhempy
# DEF tuya_cloud TUYA bf0982f08295070ae7tulb
# DEVICEID bf0982f08295070ae7tulb
# FHEMPYTYPE tuya_cloud
# FUUID 6401fe6c-f33f-fd5f-61ee-0744a8a11cccca7e
# IODev local_pybinding
# NAME TUYA_Temp04
# NR 2594
# PYTHONTYPE tuya_cloud
# STATE ready
# TYPE fhempy
# eventCount 3
# Helper:
# DBLOG:
# va_humidity:
# dblog_THB:
# TIME 1677865385.46624
# VALUE 71.0
# va_temperature:
# dblog_THB:
# TIME 1677865385.46624
# VALUE 4.4
# READINGS:
# 2023-03-03 18:42:19 active_time 1671725935
# 2023-03-03 18:42:50 battery_state middle
# 2023-03-03 18:42:19 biz_type 18
# 2023-03-03 18:42:19 category wsdcg
# 2023-03-03 18:42:19 create_time 1671725935
# 2023-03-03 18:42:19 icon https://images.tuyaeu.com/smart/icon/ay1525749833414yotNt/d9d4ceec63cb81ff6e8c8d6c2fb4edb3.png
# 2023-03-03 18:42:19 id bf0982f08295070ae7tulb
# 2023-03-03 18:42:19 ip 78.43.212.60
# 2023-03-03 18:42:19 lat 48.5600
# 2023-03-03 18:42:19 local_key d81b4251f2f1ac46
# 2023-03-03 18:42:19 lon 9.2000
# 2023-03-03 18:42:19 model TH01 CB3S
# 2023-03-03 18:42:19 name TempHum4 Terrasse
# 2023-03-03 18:42:19 online off
# 2023-03-03 18:42:19 owner_id 3389434
# 2023-03-03 18:42:19 product_id lf36y5nwb8jkxwgg
# 2023-03-03 18:42:19 product_name T & H Sensor
# 2023-03-03 18:42:05 state ready
# 2023-03-03 18:42:19 sub off
# 2023-03-03 18:42:50 temp_unit_convert c
# 2023-03-03 18:42:19 time_zone +01:00
# 2023-03-03 18:42:19 uid eu1548823829280mLHX1
# 2023-03-03 18:42:19 update_time 1677311209
# 2023-03-03 18:42:19 uuid 1ff0620fa0c0d31a
# 2023-03-03 18:42:50 va_humidity 71.0
# 2023-03-03 18:42:50 va_temperature 4.4
# args:
# TUYA_Temp04
# fhempy
# tuya_cloud
# TUYA
# bf0982f08295070ae7tulb
# argsh:
#
setstate TUYA_Temp04 ready
setstate TUYA_Temp04 2023-03-03 18:42:19 active_time 1671725935
setstate TUYA_Temp04 2023-03-03 18:42:50 battery_state middle
setstate TUYA_Temp04 2023-03-03 18:42:19 biz_type 18
setstate TUYA_Temp04 2023-03-03 18:42:19 category wsdcg
setstate TUYA_Temp04 2023-03-03 18:42:19 create_time 1671725935
setstate TUYA_Temp04 2023-03-03 18:42:19 icon https://images.tuyaeu.com/smart/icon/ay1525749833414yotNt/d9d4ceec63cb81ff6e8c8d6c2fb4edb3.png
setstate TUYA_Temp04 2023-03-03 18:42:19 id bf0982f08295070ae7tulb
setstate TUYA_Temp04 2023-03-03 18:42:19 ip 78.43.212.60
setstate TUYA_Temp04 2023-03-03 18:42:19 lat 48.5600
setstate TUYA_Temp04 2023-03-03 18:42:19 local_key d81b4251f2f1ac46
setstate TUYA_Temp04 2023-03-03 18:42:19 lon 9.2000
setstate TUYA_Temp04 2023-03-03 18:42:19 model TH01 CB3S
setstate TUYA_Temp04 2023-03-03 18:42:19 name TempHum4 Terrasse
setstate TUYA_Temp04 2023-03-03 18:42:19 online off
setstate TUYA_Temp04 2023-03-03 18:42:19 owner_id 3389434
setstate TUYA_Temp04 2023-03-03 18:42:19 product_id lf36y5nwb8jkxwgg
setstate TUYA_Temp04 2023-03-03 18:42:19 product_name T & H Sensor
setstate TUYA_Temp04 2023-03-03 18:42:05 state ready
setstate TUYA_Temp04 2023-03-03 18:42:19 sub off
setstate TUYA_Temp04 2023-03-03 18:42:50 temp_unit_convert c
setstate TUYA_Temp04 2023-03-03 18:42:19 time_zone +01:00
setstate TUYA_Temp04 2023-03-03 18:42:19 uid eu1548823829280mLHX1
setstate TUYA_Temp04 2023-03-03 18:42:19 update_time 1677311209
setstate TUYA_Temp04 2023-03-03 18:42:19 uuid 1ff0620fa0c0d31a
setstate TUYA_Temp04 2023-03-03 18:42:50 va_humidity 71.0
setstate TUYA_Temp04 2023-03-03 18:42:50 va_temperature 4.4
[/code]
das sind die letzen Meldungen im fhempY.log:
2023-03-03 18:43:05,233 - ERROR - fhempy.lib.fhem: FHEM took 5123ms for AttrVal('TUYA_SP07', 'dp_21', '')
2023-03-03 18:43:05,234 - ERROR - fhempy.lib.fhem: FHEM took 5124ms for AttrVal('TUYA_SP08', 'dp_21', '')
2023-03-03 18:43:05,236 - ERROR - fhempy.lib.fhem: FHEM took 5124ms for AttrVal('TUYA_SP06', 'dp_21', '')
2023-03-03 18:43:05,237 - ERROR - fhempy.lib.fhem: FHEM took 5124ms for AttrVal('TUYA_SP11', 'dp_21', '')
2023-03-03 18:43:05,239 - ERROR - fhempy.lib.fhem: FHEM took 5124ms for AttrVal('TUYA_SP15', 'dp_21', '')
2023-03-03 18:43:05,240 - ERROR - fhempy.lib.fhem: FHEM took 5124ms for AttrVal('TUYA_SP09', 'dp_21', '')
2023-03-03 18:43:05,241 - ERROR - fhempy.lib.fhem: FHEM took 5123ms for AttrVal('TUYA_SP14', 'dp_21', '')
2023-03-03 18:43:05,243 - ERROR - fhempy.lib.fhem: FHEM took 5123ms for AttrVal('TUYA_SP16', 'dp_21', '')
2023-03-03 18:43:05,244 - ERROR - fhempy.lib.fhem: FHEM took 5123ms for AttrVal('TUYA_SP12', 'dp_21', '')
2023-03-03 18:43:05,246 - ERROR - fhempy.lib.fhem: FHEM took 5085ms for readingsBeginUpdate($defs{'TUYA_SP03'});;
2023-03-03 18:43:05,247 - ERROR - fhempy.lib.fhem: FHEM took 5020ms for AttrVal('TUYA_SP13', 'dp_21', '')
2023-03-03 18:43:05,396 - ERROR - fhempy.lib.fhem: FHEM took 5119ms for readingsEndUpdate($defs{'TUYA_JL32'},1);;
2023-03-03 18:43:05,398 - ERROR - fhempy.lib.fhem: FHEM took 5120ms for readingsEndUpdate($defs{'TUYAC_Sir01'},1);;
2023-03-03 18:43:05,447 - ERROR - fhempy.lib.fhem: FHEM took 5168ms for readingsBulkUpdate($defs{'TUYAC_Camera6'},'sd_format','on');;
2023-03-03 18:43:05,447 - ERROR - fhempy.lib.fhem: FHEM took 5168ms for readingsBulkUpdateIfChanged($defs{'TUYA_JL24'},'cur_voltage','226.5');;
2023-03-03 19:00:01,878 - ERROR - fhempy.lib.fhem: FHEM took 7011ms for readingsBeginUpdate($defs{'TUYA_JL30'});;
2023-03-03 19:00:01,879 - ERROR - fhempy.lib.fhem: FHEM took 6340ms for readingsBeginUpdate($defs{'TUYA_JL05'});;
2023-03-03 19:00:01,881 - ERROR - fhempy.lib.fhem: FHEM took 5972ms for readingsBeginUpdate($defs{'TUYA_SP11'});;
2023-03-03 19:00:01,883 - ERROR - fhempy.lib.fhem: FHEM took 5956ms for readingsBeginUpdate($defs{'TUYA_JL26'});;
2023-03-03 19:00:01,884 - ERROR - fhempy.lib.fhem: FHEM took 5756ms for readingsBeginUpdate($defs{'TUYA_JL33'});;
2023-03-03 19:00:01,886 - ERROR - fhempy.lib.fhem: FHEM took 5703ms for readingsBeginUpdate($defs{'TUYA_JL25'});;
2023-03-03 19:00:01,888 - ERROR - fhempy.lib.fhem: FHEM took 5701ms for readingsBeginUpdate($defs{'TUYA_JL27'});;
2023-03-03 19:00:01,889 - ERROR - fhempy.lib.fhem: FHEM took 5374ms for readingsBeginUpdate($defs{'TUYA_JL32'});;
2023-03-03 19:00:01,891 - ERROR - fhempy.lib.fhem: FHEM took 5364ms for readingsBeginUpdate($defs{'TUYA_JL35'});;
2023-03-03 19:00:01,893 - ERROR - fhempy.lib.fhem: FHEM took 5143ms for readingsBeginUpdate($defs{'TUYA_JL03'});;
im fhem.log nichts
der baugleiche Temp05 funktioniert.
Den Temp04 hatte ich durch auskommentieren herausgenommen und neu erkennen lassen.
Über ein "ready kommt er nicht hinaus
Der bleibt auch auf "ready" ;)
Stell stateFormat auf va_humidity / va_temperature, dann siehst du im state die korrekten Werte.
ok ; nun sehe ich zwar die Werte wieder ; aber es sind unverändert die von 18:48 (also kurz) nachdem shutdown restart ..
als das alte Phänomen update nur kurz restart
die Temeratur ist seitdem um 3 Grad gefallen
Pulsar hast du eh aktiviert, oder? Wenn ja, dann kann man da leider nicht mehr machen wenn die tuya Cloud keine Events liefert...das kam bei mir auch immer wieder vor, deshalb bin ich komplett auf local umgezogen, da es zuverlässiger ist. Ich habe aber auch keine passiven Devices.
Zitat von: dominik am 03 März 2023, 23:06:35
Pulsar hast du eh aktiviert, oder? Wenn ja, dann kann man da leider nicht mehr machen wenn die tuya Cloud keine Events liefert...das kam bei mir auch immer wieder vor, deshalb bin ich komplett auf local umgezogen, da es zuverlässiger ist. Ich habe aber auch keine passiven Devices.
hmm -- auch in _local will das Teil nicht aktualisieren
das ging aber schon mal
Ich habe mir jetzt mal einen tuya wifi Rauchmelder zugelegt, mit dem werde ich morgen mal testen.
Zitat von: dominik am 04 März 2023, 19:33:15
Ich habe mir jetzt mal einen tuya wifi Rauchmelder zugelegt, mit dem werde ich morgen mal testen.
bei mir ist ja auch einer dabei "SmokeAlarm" ; der hat über fempy noch keine Readings
Wenn er über tuya cloud noch keine Readings hat, poste bitte mal ein list davon hier.
Zitat von: dominik am 04 März 2023, 21:21:15
Wenn er über tuya cloud noch keine Readings hat, poste bitte mal ein list davon hier.
et voilà
[code]define TUYAC_SensorSmoke01 fhempy tuya_cloud TUYA bffb7d9839e65fcdeciaqn
attr TUYAC_SensorSmoke01 DbLogExclude .*
attr TUYAC_SensorSmoke01 alias Smoke Alarm
attr TUYAC_SensorSmoke01 group Sensor Smoke,Sensor (T)
attr TUYAC_SensorSmoke01 room -TUYA
# DEF tuya_cloud TUYA bffb7d9839e65fcdeciaqn
# DEVICEID bffb7d9839e65fcdeciaqn
# FHEMPYTYPE tuya_cloud
# FUUID 63dd2cfb-f33f-fd5f-9c8d-6cf99c5de4f44622
# IODev local_pybinding
# NAME TUYAC_SensorSmoke01
# NR 1808
# PYTHONTYPE tuya_cloud
# STATE normal
# TYPE fhempy
# eventCount 3
# READINGS:
# 2023-03-04 15:44:46 active_time 1651846315
# 2023-03-04 15:45:21 battery_state high
# 2023-03-04 15:44:46 biz_type 18
# 2023-03-04 15:44:46 category ywbj
# 2023-03-04 15:45:21 checking_result checking
# 2023-03-04 15:44:46 create_time 1651846315
# 2023-03-04 15:44:46 icon https://images.tuyaeu.com/smart/icon/ay1553762254781PxBGe/04ddc19b0ef593461acd0ce635147b92.jpg
# 2023-03-04 15:44:46 id bffb7d9839e65fcdeciaqn
# 2023-03-04 15:44:46 ip 78.43.212.39
# 2023-03-04 15:44:46 lat 48.5585
# 2023-03-04 15:45:21 link_alarm alarm
# 2023-03-04 15:44:46 local_key bf783bf4e72b936b
# 2023-03-04 15:44:46 lon 9.2026
# 2023-03-04 15:44:46 model SM11
# 2023-03-04 15:44:46 name Smoke Alarm
# 2023-03-04 15:44:46 online on
# 2023-03-04 15:44:46 owner_id 3389434
# 2023-03-04 15:44:46 product_id powevvypruxyou2z
# 2023-03-04 15:44:46 product_name Smoke Alarm
# 2023-02-27 21:34:11 statStateDay normal: 00:00:00 normal_Count: 1 (since: 2023-02-27_21:34:11)
# 2023-02-27 21:34:11 statStateMonth normal: 00:00:00 normal_Count: 1 (since: 2023-02-27_21:34:11)
# 2023-02-27 21:34:11 statStateYear normal: 00:00:00 normal_Count: 1 (since: 2023-02-27_21:34:11)
# 2023-03-04 15:45:21 state normal
# 2023-03-04 15:44:46 sub off
# 2023-03-04 15:44:46 time_zone +02:00
# 2023-03-04 15:44:46 uid eu1548823829280mLHX1
# 2023-03-04 15:44:46 update_time 1651846318
# 2023-03-04 15:44:46 uuid 4f81e895282e3558
# args:
# TUYAC_SensorSmoke01
# fhempy
# tuya_cloud
# TUYA
# bffb7d9839e65fcdeciaqn
# argsh:
#
setstate TUYAC_SensorSmoke01 normal
setstate TUYAC_SensorSmoke01 2023-03-04 15:44:46 active_time 1651846315
setstate TUYAC_SensorSmoke01 2023-03-04 15:45:21 battery_state high
setstate TUYAC_SensorSmoke01 2023-03-04 15:44:46 biz_type 18
setstate TUYAC_SensorSmoke01 2023-03-04 15:44:46 category ywbj
setstate TUYAC_SensorSmoke01 2023-03-04 15:45:21 checking_result checking
setstate TUYAC_SensorSmoke01 2023-03-04 15:44:46 create_time 1651846315
setstate TUYAC_SensorSmoke01 2023-03-04 15:44:46 icon https://images.tuyaeu.com/smart/icon/ay1553762254781PxBGe/04ddc19b0ef593461acd0ce635147b92.jpg
setstate TUYAC_SensorSmoke01 2023-03-04 15:44:46 id bffb7d9839e65fcdeciaqn
setstate TUYAC_SensorSmoke01 2023-03-04 15:44:46 ip 78.43.212.39
setstate TUYAC_SensorSmoke01 2023-03-04 15:44:46 lat 48.5585
setstate TUYAC_SensorSmoke01 2023-03-04 15:45:21 link_alarm alarm
setstate TUYAC_SensorSmoke01 2023-03-04 15:44:46 local_key bf783bf4e72b936b
setstate TUYAC_SensorSmoke01 2023-03-04 15:44:46 lon 9.2026
setstate TUYAC_SensorSmoke01 2023-03-04 15:44:46 model SM11
setstate TUYAC_SensorSmoke01 2023-03-04 15:44:46 name Smoke Alarm
setstate TUYAC_SensorSmoke01 2023-03-04 15:44:46 online on
setstate TUYAC_SensorSmoke01 2023-03-04 15:44:46 owner_id 3389434
setstate TUYAC_SensorSmoke01 2023-03-04 15:44:46 product_id powevvypruxyou2z
setstate TUYAC_SensorSmoke01 2023-03-04 15:44:46 product_name Smoke Alarm
setstate TUYAC_SensorSmoke01 2023-02-27 21:34:11 statStateDay normal: 00:00:00 normal_Count: 1 (since: 2023-02-27_21:34:11)
setstate TUYAC_SensorSmoke01 2023-02-27 21:34:11 statStateMonth normal: 00:00:00 normal_Count: 1 (since: 2023-02-27_21:34:11)
setstate TUYAC_SensorSmoke01 2023-02-27 21:34:11 statStateYear normal: 00:00:00 normal_Count: 1 (since: 2023-02-27_21:34:11)
setstate TUYAC_SensorSmoke01 2023-03-04 15:45:21 state normal
setstate TUYAC_SensorSmoke01 2023-03-04 15:44:46 sub off
setstate TUYAC_SensorSmoke01 2023-03-04 15:44:46 time_zone +02:00
setstate TUYAC_SensorSmoke01 2023-03-04 15:44:46 uid eu1548823829280mLHX1
setstate TUYAC_SensorSmoke01 2023-03-04 15:44:46 update_time 1651846318
setstate TUYAC_SensorSmoke01 2023-03-04 15:44:46 uuid 4f81e895282e3558
[/code]
schau mal bitte noch auf meine beiden TempHum04 und 05 mit der productid
lf36y5nwb8jkxwgg.
Komisch ist, dass der 05 funktioniert, der 04 aber nicht.
Beide haben frische Batterien, signifikante Termperaturänderungen und laut FING auch immer wieder
So, ich konnte jetzt mal kurz testen. Mein Rauchmelder liefert auch nur Batteriewert high aber keine Meldung. Ich schau mir das morgen Abend genauer an woran das liegt.
Wie ich sehe, hat deiner aber zumindest irgendwann "normal" geschickt.
seit neuesten werden readings nicht mehr aktualisiert. öfters auch tuya_lokal nicht, erst nach update von tuya und neu scan und anlegen. die cloud liest überhaupr nichts mehr ein. gibts bekannte probleme?
Zitat von: satprofi am 01 April 2023, 19:10:07seit neuesten werden readings nicht mehr aktualisiert. öfters auch tuya_lokal nicht, erst nach update von tuya und neu scan und anlegen. die cloud liest überhaupr nichts mehr ein. gibts bekannte probleme?
bei mir läuft alles (ca. 105) Devices wie geschmiert. Auch die neuen ZigBees TempHums.
Lediglich ein TempHum-Sensor wollte nicht mehr. Habe Ihn inzwischen ersetzt. Gibs bei Alixxxxx für knapp 5€.
Ich arbeite noch an der Visualisierung der Stromverbräuche.
Arbeitet jemand mit EXCEL Ex-Import aus der DbLog? (Dank Addlog habe ich nun die notwendigen Werte)
Zitat von: thburkhart am 02 April 2023, 10:15:41Zitat von: satprofi am 01 April 2023, 19:10:07seit neuesten werden readings nicht mehr aktualisiert. öfters auch tuya_lokal nicht, erst nach update von tuya und neu scan und anlegen. die cloud liest überhaupr nichts mehr ein. gibts bekannte probleme?
Ich arbeite noch an der Visualisierung der Stromverbräuche.
Arbeitet jemand mit EXCEL Ex-Import aus der DbLog? (Dank Addlog habe ich nun die notwendigen Werte)
Aha, danke.
Das mit den Stromverbräuchen ist interessant.
Zitat von: satprofi am 01 April 2023, 19:10:07seit neuesten werden readings nicht mehr aktualisiert. öfters auch tuya_lokal nicht, erst nach update von tuya und neu scan und anlegen. die cloud liest überhaupr nichts mehr ein. gibts bekannte probleme?
Hi,
ich habe ähnliches oder gleiches Problem, mein tuya Device (eine Wärmepumpe) kann ich über den tuya_cloud_connector und das darüber erzeugte device an- und ausschalten (Temperatureinstellung ist nicht möglich), aber ich erhalte keine Readings und keine Rückmeldung ob die Wärmepumpe an oder aus ist, lediglich die initial erzeugtem bleiben bestehen. Ich muss also immer noch in der App schauen, ob diese an oder aus ist.
Über fhempy_local kann ich die Wärmepumpe gar nicht steuern, das Device wird zwar angelegt, ist aber nicht steuerbar.
Jemand eine Idee woran es liegen kann? Punkt 6 in der Anleitung habe ich befolgt ;-)
Zitat von: GodVatter am 17 April 2023, 15:06:51Zitat von: satprofi am 01 April 2023, 19:10:07seit neuesten werden readings nicht mehr aktualisiert. öfters auch tuya_lokal nicht, erst nach update von tuya und neu scan und anlegen. die cloud liest überhaupr nichts mehr ein. gibts bekannte probleme?
Hi,
ich habe ähnliches oder gleiches Problem, mein tuya Device (eine Wärmepumpe) kann ich über den tuya_cloud_connector und das darüber erzeugte device an- und ausschalten (Temperatureinstellung ist nicht möglich), aber ich erhalte keine Readings und keine Rückmeldung ob die Wärmepumpe an oder aus ist, lediglich die initial erzeugtem bleiben bestehen. Ich muss also immer noch in der App schauen, ob diese an oder aus ist.
Über fhempy_local kann ich die Wärmepumpe gar nicht steuern, das Device wird zwar angelegt, ist aber nicht steuerbar.
Jemand eine Idee woran es liegen kann? Punkt 6 in der Anleitung habe ich befolgt ;-)
bei mir lag es daran, dass das Fritz OS 7.5 den Geräten trotz "die selbe IP verwenden" andere IPs zugewiesen hatte und auch nicht mehr zuweisen konnte.
So habe ich in diesem Zuge auf tuya_cloud umgestellt.
Die tuya_cloud Devices laufen seit Ende März zuverlässig.
Zitat von: thburkhart am 17 April 2023, 17:19:27bei mir lag es daran, dass das Fritz OS 7.5 den Geräten trotz "die selbe IP verwenden" andere IPs zugewiesen hatte und auch nicht mehr zuweisen konnte.
So habe ich in diesem Zuge auf tuya_cloud umgestellt.
Die tuya_cloud Devices laufen seit Ende März zuverlässig.
Deine readings werden auch aktualisiert?
2023-04-17 20:35:29,803 - ERROR - fhempy.lib.fhem: FHEM took 7216ms for setDevAttrList('tuya_cloud_XXX', ' IODev disable:0,1 '.$readingFnAttributes)
2023-04-17 20:35:29,811 - ERROR - fhempy.lib.fhem: FHEM took 7221ms for setDevAttrList('tuya_cloud_connector', ' IODev disable:0,1 '.$readingFnAttributes)
2023-04-17 20:35:29,820 - ERROR - fhempy.lib.fhem: FHEM took 7177ms for setDevAttrList('tuya_system', ' IODev disable:0,1 '.$readingFnAttributes)
2023-04-17 20:35:29,828 - ERROR - fhempy.lib.fhem: FHEM took 7177ms for setDevAttrList('tuya_local_XXX', ' IODev disable:0,1 '.$readingFnAttributes)
2023-04-17 20:35:32,450 - INFO - websocket: Websocket connected
2023-04-17 20:35:46,611 - ERROR - fhempy.lib.fhem: FHEM took 5932ms for readingsBulkUpdate($defs{'tuya_cloud_XXX'},'create_time','1611686843');;
2023-04-17 20:35:46,614 - ERROR - fhempy.lib.fhem: FHEM took 5932ms for AttrVal('tuya_local_XXX', 'tuya_spec_status', '[]')
im fhempy_log sind oben dargestellte Einträge zu sehen
kann mir jemand helfen, was hier das Problem ist?
product_id ist folgende
eeih95rmks0mjflz
Zitat von: satprofi am 01 April 2023, 19:10:07seit neuesten werden readings nicht mehr aktualisiert. öfters auch tuya_lokal nicht, erst nach update von tuya und neu scan und anlegen. die cloud liest überhaupr nichts mehr ein. gibts bekannte probleme?
hast du das Problem gelöst bekommen? ich stehe wie beschrieben vor genau dem gleichen...
tuya_cloud verursacht bei den Devices Updates manchmal Probleme. Das liegt an der tuya_cloud und wird auch bei HomeAssistant, die die gleiche Library verwenden, immer wieder bemängelt. Ich empfehle daher tuya (local) zu verwenden.
Zitat von: GodVatter am 18 April 2023, 08:42:132023-04-17 20:35:29,803 - ERROR - fhempy.lib.fhem: FHEM took 7216ms for setDevAttrList('tuya_cloud_XXX', ' IODev disable:0,1 '.$readingFnAttributes)
2023-04-17 20:35:29,811 - ERROR - fhempy.lib.fhem: FHEM took 7221ms for setDevAttrList('tuya_cloud_connector', ' IODev disable:0,1 '.$readingFnAttributes)
2023-04-17 20:35:29,820 - ERROR - fhempy.lib.fhem: FHEM took 7177ms for setDevAttrList('tuya_system', ' IODev disable:0,1 '.$readingFnAttributes)
2023-04-17 20:35:29,828 - ERROR - fhempy.lib.fhem: FHEM took 7177ms for setDevAttrList('tuya_local_XXX', ' IODev disable:0,1 '.$readingFnAttributes)
2023-04-17 20:35:32,450 - INFO - websocket: Websocket connected
2023-04-17 20:35:46,611 - ERROR - fhempy.lib.fhem: FHEM took 5932ms for readingsBulkUpdate($defs{'tuya_cloud_XXX'},'create_time','1611686843');;
2023-04-17 20:35:46,614 - ERROR - fhempy.lib.fhem: FHEM took 5932ms for AttrVal('tuya_local_XXX', 'tuya_spec_status', '[]')
im fhempy_log sind oben dargestellte Einträge zu sehen
kann mir jemand helfen, was hier das Problem ist?
product_id ist folgende
eeih95rmks0mjflz
Ist nicht weiter schlimm...deine FHEM Instanz war zu der Zeit sehr überlastet und hat bis zu 7s benötigt um eine Antwort zu liefern. Solange das nicht andauernd auftritt, sondern nur beim Start, kannst du das vernachlässigen.
Zitat von: GodVatter am 21 April 2023, 15:42:18Zitat von: satprofi am 01 April 2023, 19:10:07seit neuesten werden readings nicht mehr aktualisiert. öfters auch tuya_lokal nicht, erst nach update von tuya und neu scan und anlegen. die cloud liest überhaupr nichts mehr ein. gibts bekannte probleme?
hast du das Problem gelöst bekommen? ich stehe wie beschrieben vor genau dem gleichen...
ja, mit update von tuya_pibinding
Wie ist das gemeint mit dem Update von tuya_binding?
Ich habe auch das Problem, dass die Readings nur nach einem ,,shutdown restart" von FHEM erfolgen.
Zitat von: uwirt am 01 Mai 2023, 14:05:34Wie ist das gemeint mit dem Update von tuya_binding?
Ich habe auch das Problem, dass die Readings nur nach einem ,,shutdown restart" von FHEM erfolgen.
Hallo.
Wenn du auf Device "
local_pybinding" gehst siehst du update .
ich habe mir ein at angelegt dafür:
define tuya_pybinding_reset at *00:59:00 set local_pybinding update
Ich habe jetzt auf tuya local gewechselt und es funktioniert.
Hallo zusammen,
ich habe ein neuen Usecase und frage mich ob das jemand schon elegant gelöst hat.
Es betrifft Tuya Cloud und auch local.
Ich habe eine Pumpe für den Warmwasserboiler die über einen Temperatursensor geschaltet wird.
Nun ist es so dass die ganze Steckdose geschaltet wird.
Die Tuya Steckdose soll also nur den Stromverbrauch messen.
Das tut sie auch, nur gibt es nie cur_power Werte mit 0.
Da die Steckdose ja einfach ausgeschaltet wird.
In der Tuya App sehe ich "Offline" wenn der Strom weg ist.
Mein Fhem Graph zeigt immer den Verbrauch an der als letztes gemessen wurde, auch für die Zeit in der die Steckdose aus war und so keine Daten lieferte.
Auch die Anzeige im FHEM zeigt nur den letzten Zustand.
Also wenn die Steckdose Offline ist, wird angezeigt dass sie an ist und das Gerät 30 Watt braucht.
Ich müsste also mindestens einen 0 Wert in die DB schreiben wenn die Steckdose keine Daten mehr liefert.
Dachte nun es mit Readingsage > 60 sekunden zu realisieren.
Meine Frage ist ob hier jemand so etwas schonmal gemacht hat und vielleicht auch auf eine bessere Lösung gekommen ist?
Danke und Gruß,
Stefan
Hi,
zusätzlich zur Frage oben habe ich heute auch noch ein Problem im Logfile gefunden.
Es tritt auf seit dem Update auf 0.1.648.
Mein Temperatursensor hat ein Reading battery_state mit high, middle, low.
Im log kommen folgende Meldungen:
2023.05.14 10:48:59 1: BindingsIo (local_pybinding): Argument "middle" isn't numeric in numeric gt (>) at (eval 17242163) line 1.
=> COMMAND: readingsEndUpdate($defs{'tuya_cloud_bffa550a829a269630vhcn'},1);;
2023.05.14 10:48:59 1: BindingsIo (local_pybinding): command = readingsEndUpdate($defs{'tuya_cloud_bffa550a829a269630vhcn'},1);;
2023.05.14 10:48:59 1: BindingsIo (local_pybinding): NAME = tuya_cloud_bffa550a829a269630vhcn
2023.05.14 10:48:59 1: BindingsIo (local_pybinding): msgtype = command
2023.05.14 10:48:59 1: BindingsIo (local_pybinding): awaitId = 12710777
Ein List des Temperatur devices sieht so aus:
Internals:
DEF tuya_cloud tuya_cloud_connector bffa550a829a269630vhcn
DEVICEID bffa550a829a269630vhcn
FHEMPYTYPE tuya_cloud
FUUID 63d3d9cd-f33f-0c45-4616-9afe69334bfac8ce
IODev local_pybinding
NAME tuya_cloud_bffa550a829a269630vhcn
NR 2302
PYTHONTYPE tuya_cloud
STATE </br>Temp: 22.4 C° RF: 59.0 %
</br>Batterie: middle
TYPE fhempy
eventCount 260
Helper:
DBLOG:
va_humidity:
logdb:
TIME 1684060952.22546
VALUE 59.0
va_temperature:
logdb:
TIME 1684060951.98714
VALUE 22.4
READINGS:
2023-05-12 01:43:38 active_time 1674825254
2023-05-14 12:42:32 battery_state middle
2023-05-12 01:43:38 biz_type 0
2023-05-12 01:43:38 category wsdcg
2023-05-12 01:43:38 create_time 1674825254
2023-05-12 01:43:38 icon https://images.tuyaeu.com/smart/icon/ay1525749833414yotNt/b3a94a9431b68373894805b4a19092e4.png
2023-05-12 01:43:38 id bffa550a829a269630vhcn
2023-05-12 01:43:38 ip 84.188.243.243
2023-05-12 01:43:38 lat 49.6104
2023-05-12 01:43:38 local_key 55db39dd00af9487
2023-05-12 01:43:38 lon 8.7263
2023-05-12 01:43:38 model TH08CBU
2023-05-12 01:43:38 name T & H Sensor
2023-05-12 01:43:38 online on
2023-05-12 01:43:38 owner_id 39691875
2023-05-12 01:43:38 product_id xlk3mtpjo1zkmdvh
2023-05-12 01:43:38 product_name T & H Sensor
2023-05-12 01:43:26 state ready
2023-05-12 01:43:38 sub off
2023-05-12 03:54:13 temp_unit_convert c
2023-05-12 01:43:38 time_zone +01:00
2023-05-12 01:43:38 uid eu1634560510538qIss1
2023-05-12 01:43:38 update_time 1674825257
2023-05-14 12:42:32 update_time_hr 27.01.2023, 14:14:17
2023-05-12 01:43:38 uuid 21d66a0f7e3333d0
2023-05-14 12:42:32 va_humidity 59.0
2023-05-14 12:42:31 va_temperature 22.4
args:
tuya_cloud_bffa550a829a269630vhcn
fhempy
tuya_cloud
tuya_cloud_connector
bffa550a829a269630vhcn
argsh:
Attributes:
DbLogInclude va_temperature,va_humidity
alias T & H Sensor
group Steckdosen_Tuya
room fhempy
stateFormat </br>Temp: va_temperature C° RF: va_humidity %
</br>Batterie: battery_state
userReadings update_time_hr { timestamp2date(ReadingsVal("tuya_cloud_bffa550a829a269630vhcn","update_time",0)) }
Danke und Gruß,
Stefan
Hallo, ich will meine Tuya-WiFi-Steckdosen nicht nur schalten sondern auch einige Werte anzeigen. (siehe Bild 1) Allerdings stört mich die letzte Anzeige des Verbrauches in Wh. Da hätte ich am liebsten kWh. Nun probiere ich schon einige Zeit mit dem stateformat herum und komme auf keinen "grünen Zweig".
Wie muss ich das stateformat ändern, damit mir die letzte Anzeige in kWh angezeigt wird.
Hi Rainer,
bei der Solaranlage habe ich in StateFormat so etwas:
{
"Netz: ".sprintf("%.0f",ReadingsVal("$name","PowerFlow_Site_P_Grid", undef))." W <br/>
"Total Erzeugt: ".sprintf("%.3f",(ReadingsVal("$name","PowerFlow_Site_E_Total", undef)/1000))." kWh <br/>".
}
Sag mal das ist aber doch kein cloud sondern local oder?
Bei local habe ich energy, bei cloud nicht oder auf 0.
Gruß,
Stefan
Hallo Stefan, danke für die Antwort. Leider klappt das mit
{sprintf("%.3f",(ReadingsVal("tuya_local_251411404855195f16be","Waschmaschine","energy")/1000))." kWh"
}
auch nicht. In diesem Fall schreibt er immer nur 0.000 kWh. Der Wert von energy (aus dem reading 1.363) wird nicht übernommen. Ich habe es auch schon mit allen möglichen Formatierungen versucht. Leider ohne Erfolg.
Und natürlich ist das Local. Habe ich es dann im falschen Thread gepostet?
Zitat von: stefanru am 14 Mai 2023, 11:52:34Hallo zusammen,
ich habe ein neuen Usecase und frage mich ob das jemand schon elegant gelöst hat.
Es betrifft Tuya Cloud und auch local.
Ich habe eine Pumpe für den Warmwasserboiler die über einen Temperatursensor geschaltet wird.
Nun ist es so dass die ganze Steckdose geschaltet wird.
Die Tuya Steckdose soll also nur den Stromverbrauch messen.
Das tut sie auch, nur gibt es nie cur_power Werte mit 0.
Da die Steckdose ja einfach ausgeschaltet wird.
In der Tuya App sehe ich "Offline" wenn der Strom weg ist.
Danke und Gruß,
Stefan
warum schaltest du die pumpe nicht mit der tuya steckdose? dann ist sie immer online
Hi Rainer,
versuch es mal bitte genau so in stateFormat, nichts austauschen:
{sprintf("%.3f",(ReadingsVal("$name","energy",undef)/1000))." kWh"}
$name ist eine variable für das Device. Musst du nicht austauschen, funktioniert so.
Kannst du dann genau so in jedes Device kopieren in dem du das Reading brauchst.
"enregy" ist dein Reading
undef steht für undefined, falls kein Wert kommt. Kannst du auch z.B. 0 hinschreiben.
Aber undef geht gut.
Habe es gerade selbst probiert bei einem local Device.
Funktioniert genau so.
@satprofi:
Das ist ein uralter Temperatursensor, den müsste ich gegen etwas moderneres ersetzen um dann die Tuya Steckdose zu steuern.
Vielleicht mache ich das mal, aber so funktioniert es auch gut nur die Warning im Log ist halt blöd.
Gruß,
Stefan
Hi Stefan,
habe es jetzt genau so in das stateformat kopiert. Ergebnis siehe Bilder. Obwohl im Reading energy 1.363 steht wird jetzt 0.001 kWh angezeigt.
Es sind doch ganz normale Gosund WiFi-Steckdosen (https://www.amazon.de/gp/product/B09J8P9YFL/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1) . Die habe doch nicht nur ich, oder?
Trotzdem danke Stefan
Gruß
Rainer
Hi Rainer,
mist da habe ich nicht aufgepasst.
Ich dachte du brauchst ein geteilt durch 1000 um von Wh auf kWh zu kommen.
Aber das energy reading ist ja in kWh.
Durch das teilen durch tausend bekommst du jetzt 0.001 megaWh :-)
Also war dein state Format ja ok.
Ich denke ich verstehe dein Problem nicht ganz ;-)
Schreib doch einfach dein altes stateFormat vom ersten Post wieder hin, da power ja schon in kWh ist und die power Zeile dann mit der richtigen Einheit:
Also das alte state Format wieder nehmen und nur die Zeile für energy mit der richtigen Einheit hinschreiben:
energy kWh
Meinst du das?
Gruß,
Stefan
Hallo zusammen hatte bis jetzt nur eine Doppel Steckdose in Tuya und in Fhem. Diese funktioniert nach wie vor.
Jetzt habe ich in der App ein Bewässerungsventil hinzugefügt,das am Handy via BLE verbunden wird oder über den beigefügten WLAN zu BLE bride auch übers Internet angesprochen wird. Beides funktioniert in der App.
Aber in fhem bekomme ich es nicht hinzugefügt!
Wenn ich in Fhem im tuya_system Device auf scan_device klicke wird diese Fehlermeldung angezeigt im State.
2023-02-16 17:57:14
state
{'Error': 'Error Response from Tuya Cloud', 'Err': '913', 'Payload': "Error from Tuya Cloud: Code 28841002: 'No permissions. Your subscription to cloud development plan has expired.'"}
I'm Log steht das:
2023-06-11 14:00:44,954 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.652...
2023-06-11 14:00:44,966 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-06-11 14:00:45,098 - INFO - websockets.server: server listening on 0.0.0.0:15733
2023-06-11 14:00:50,667 - INFO - websockets.server: connection open
2023-06-11 14:00:50,669 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2023-06-11 14:01:32,139 - ERROR - tuya_system: getdevices: {'Error': 'Error Response from Tuya Cloud', 'Err': '913', 'Payload': "Error from Tuya Cloud: Code 28841002: 'No permissions. Your subscription to cloud development plan has expired.'"}
2023-06-11 14:02:46,849 - ERROR - tuya_system: getdevices: {'Error': 'Error Response from Tuya Cloud', 'Err': '913', 'Payload': "Error from Tuya Cloud: Code 28841002: 'No permissions. Your subscription to cloud development plan has expired.'"}
Was kann ich tun um wieder devices hinzuzufügen?
Danke euch und schönen Sonntag noch
Ich habe seit neuestem folgenden Fehler im log:
2023-06-16 15:38:11,331 - ERROR - __main__: Failed to install fhempy, exit now...
2023-06-16 15:39:31,159 - ERROR - __main__: Failed to load fhempy
Traceback (most recent call last):
File "/opt/fhem/FHEM/bindings/python/bin/fhempy", line 139, in
import fhempy.lib.fhem_pythonbinding as fpb
ModuleNotFoundError: No module named 'fhempy'
2023-06-16 15:39:31,161 - INFO - __main__: Attempting install of fhempy>=0.1.462
2023-06-16 15:39:31,419 - ERROR - __main__: Unable to install package fhempy>=0.1.462: error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.
If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.
If you wish to install a non-Debian packaged Python application,
it may be easiest to use pipx install xyz, which will manage a
virtual environment for you. Make sure you have pipx installed.
See /usr/share/doc/python3.11/README.venv for more information.
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
2023-06-16 15:39:31,419 - ERROR - __main__: Failed to install fhempy, exit now...
Habe ein Upgrade auf Debian 12 bookworm gemacht.
Keine Ahnung ob es damit zusammenhängt.
Auf jeden Fall funktioniert fhempy nicht mehr.
Habe auch wie im log beschrieben das mit dem virtual environment gemacht und dann per pip3 fhempy installiert, aber es funktioniert nicht.
Kann mir da bitte geholfen werden?
Gruß
Hubert
Hi,
ich habe das gleiche Problem nach dem debian 12 upgrade. Ich habe es auch noch noicht wieder ans Laufen bekommen.
LB Björn
Zitat von: baumeister am 22 Juni 2023, 08:14:08Hi,
ich habe das gleiche Problem nach dem debian 12 upgrade. Ich habe es auch noch noicht wieder ans Laufen bekommen.
LB Björn
ich habe es geschafft die Pakete unter dem FHEM user so zu installieren:
pip3 install websockets --break-system-packagesEinige gingen nicht z.B. aiotinytuya die musste ich von hand aus github holen.
Zumindest läuft jetzt fhempy wieder, jedoch senden meine Sensoren keine Daten mehr.
ja das hatte ich auch schon probiert, aber nur mit mäßigem Erfolg. Mein fhempy.service startet nicht
# journalctl -u fhempy.service -f
Jun 22 10:08:14 homecontrol-0001 systemd[1]: Started fhempy.service - fhempy.
Jun 22 10:08:14 homecontrol-0001 (fhempy)[8506]: fhempy.service: Failed to determine user credentials: No such process
Jun 22 10:08:14 homecontrol-0001 (fhempy)[8506]: fhempy.service: Failed at step USER spawning /home/pi/.local/bin/fhempy: No such process
Jun 22 10:08:14 homecontrol-0001 systemd[1]: fhempy.service: Main process exited, code=exited, status=217/USER
Jun 22 10:08:14 homecontrol-0001 systemd[1]: fhempy.service: Failed with result 'exit-code'.
Jun 22 10:08:14 homecontrol-0001 systemd[1]: fhempy.service: Scheduled restart job, restart counter is at 5.
Jun 22 10:08:14 homecontrol-0001 systemd[1]: Stopped fhempy.service - fhempy.
Jun 22 10:08:14 homecontrol-0001 systemd[1]: fhempy.service: Start request repeated too quickly.
Jun 22 10:08:14 homecontrol-0001 systemd[1]: fhempy.service: Failed with result 'exit-code'.
Jun 22 10:08:14 homecontrol-0001 systemd[1]: Failed to start fhempy.service - fhempy.
Das neue Einrichten in fhem mit
update add https://raw.githubusercontent.com/fhempy/fhempy/master/controls_pythonbinding.txt
update
shutdown restart
define fhempy_local BindingsIo fhempy
hat dagegen problemlos funktoniert. Hier bekomme ich auch im UI den lokalen connect status "grün" angezeigt.
Irgendwas scheint sich von debian 11 auf 12 mit dem python geändert zu haben. Hier komme ich nicht weiter.
Lg Björn
habe nun mit
define tuya_cloud_connector fhempy tuya_cloud setup <CLIENT_ID> <CLIENT_SECRET> <USERNAME> <PASSWORD> [<APPTYPE>] [<REGION>]
versucht die cloud anzubinden, aber das scheint nur teilweise zu funktionieren. Ein "fhempyserver_15733" wird zusätzlich angelegt, wlecher auch läuft. Aber der der cloud connect wirft nur Error Meldugen aus
Module failed to load: tuya_cloud Maybe you need to update fhempy on this or remote peer. Stacktrace: Traceback (most recent call last): File "/usr/local/lib/python3.11/dist-packages/fhempy/lib/fhem_pythonbinding.py", line 336, in handle_function module_object = await self.import_module(hash) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/dist-packages/fhempy/lib/fhem_pythonbinding.py", line 573, in import_module module_object = await utils.run_blocking( ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/dist-packages/fhempy/lib/utils.py", line 72, in run_blocking return await asyncio.get_event_loop().run_in_executor(pool, function) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/concurrent/futures/thread.py", line 58, in run result = self.fn(*self.args, **self.kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 1206, in _gcd_import File "", line 1178, in _find_and_load File "", line 1149, in _find_and_load_unlocked File "", line 690, in _load_unlocked File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "/usr/local/lib/python3.11/dist-packages/fhempy/lib/tuya_cloud/tuya_cloud.py", line 7, in import fhempy.lib.tuya_cloud.tuya_cloud_setup as tcs File "/usr/local/lib/python3.11/dist-packages/fhempy/lib/tuya_cloud/tuya_cloud_setup.py", line 7, in import tuya_iot ModuleNotFoundError: No module named 'tuya_iot'
im fhempy.log konnte ich erkennen, dass einige Pakete nicht nachinstaliert erden konnten:
2023-06-22 10:04:53,584 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.658...
2023-06-22 10:04:53,596 - INFO - fhempy.lib.pkg_installer: Attempting install of async-upnp-client==0.31.2
2023-06-22 10:04:54,105 - ERROR - fhempy.lib.pkg_installer: Unable to install package async-upnp-client==0.31.2: error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.
If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.
If you wish to install a non-Debian packaged Python application,
it may be easiest to use pipx install xyz, which will manage a
virtual environment for you. Make sure you have pipx installed.
See /usr/share/doc/python3.11/README.venv for more information.
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
Ich denke daran wird es liegen. ich kann nur noch sagen warum das nicht geht. Ich werde mal versichen diese Pakete vorher händlich zu installieren.
Lg Björn
das hat funktioniert
ich habe die pakete
async-upnp-client==0.31.2
tuya-iot-py-sdk==0.6.6
tuya-connector-python==0.1.2
für den user fhem händisch installiert
sudo -u fhem pip3 install --upgrade tuya-iot-py-sdk --break-system-packagesdenn den service via UI neu gestartet, jetzt kommen wieder alle Infos aus der cloud rein!
Lg Björn
Hallo zusammen,
ich habe gerade erst mit der Verwaltung von Tuya Devices begonnen und mir es noch einiges nicht ganz klar: Gibt es zB eine Möglichkeit, mit dem tuya_cloud Modul Automationen zu starten? Im Tuya API Explorer ist mir allerdings unklar, wie ich das ggf. triggern kann.
In der Tuya (Smart) App kann man diese anlegen und auch ausführen.
Danke und viele Grüße,
Andreas
hallo.
sehe gerade das der state vom fhempyServer "???" meldet, obwohl grüner punkt im icon.
start/stop/restart schein erfolglos zu sein, ändert sich nichts am state.
gabs da irgendein update? Devices werden aber erkannt aus cloud.
Hallo hat hier zufällig jemand die RGBWWKW LED Strips von Action eingebunden??
Ich habe 2 davon, das ein und ausschalten klappt die Farbtemperatur vom Weiß einstellen auch aber wenn ich auf Color Modus gehe kann ich keine Farben einstellen über den Colorpicker. Es wird nur die zuletzt über die App eingestellte Farbe eingeschaltet.
Kann mir jemand dabei helfen??
LG Holger
hallo.
habe gerade den stripe neu eingebunden, die dürften ein problem mit servern haben. weder tuya noch lsc app finden den stripe dauerhaft. und wenn dann geht nur rot zum schalten. mit fernbedienung klappt aber alles.
Hallo also Zuletzt, (vor 2 tagen) ging übder die Tuya App alles, über fhem könnte ich ein und ausschalten, die letzte Scene aktivieren, auf Musik Modus schalten und bei weiß die Farbtemperatur einstellen.
Was in FHEM nicht ging ist eine bestimmte Farbe im Color Modus einstellen.
LG holger
bekomme seit tagen keine readings mehr, schalten klappt aber noch.
tuya lokal, klappt gar nicht mehr. schade
Wie schon im lokal Thread geantwortet:
Hi satprofi,
bei mir funktioniert sowohl cloud als auch lokal mit Steckdosen mit Power Meter ohne Probleme.
Bekomme alle Werte und kann schalten.
Ich bin noch auf 0.1.665.
Hast du schon das letzte Update gemacht auf 0.1.670?
Gruß,
Stefan
hallo.
ja, habe letzte version. jetzt steht ready im state, statt on.
und schalten kann ich nur über cloud, bei lokal kommt immer zusatzfenster mit ok button.
readings kommen aber keine nach aktionen
Ok, bei mir funktioniert alles.
Kannst du schauen ob du Fehler im fhempy.log file hast?
Gruß,
Stefan
euje, sehr viele fehlermeldungen in etlichen lines.
2023-10-06 00:59:49,054 - INFO - fhempy.lib.pkg_installer: Successfully installed fhempy update!
2023-10-06 00:59:49,073 - INFO - fhempy.lib.fhem_pythonbinding: Restart initiated...
2023-10-06 00:59:49,106 - INFO - fhempy.lib.fhem_pythonbinding: All modules successfully undefined!
2023-10-06 00:59:49,108 - INFO - websockets.server: server closing
2023-10-06 00:59:59,119 - INFO - websockets.server: connection closed
2023-10-06 00:59:59,121 - INFO - websockets.server: server closed
2023-10-06 00:59:59,128 - INFO - fhempy.lib.fhem_pythonbinding: Exit 1
2023-10-06 01:00:03,967 - INFO - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.665...
2023-10-06 01:00:03,971 - INFO - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-10-06 01:00:04,128 - INFO - websockets.server: server listening on 0.0.0.0:15733
2023-10-06 01:00:09,556 - INFO - websockets.server: connection open
2023-10-06 01:00:09,557 - INFO - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2023-10-06 01:00:17,639 - ERROR - tuya_local_bf43718f426xxxxxxx: Failed to connect to device
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 563, in setup_connection
self._connected_device = await asyncio.wait_for(connect_fct, timeout=15)
File "/usr/lib/python3.9/asyncio/tasks.py", line 481, in wait_for
return fut.result()
File "/opt/fhem/.local/lib/python3.9/site-packages/aiotinytuya/__init__.py", line 206, in connect
await device.start_socket()
File "/opt/fhem/.local/lib/python3.9/site-packages/aiotinytuya/core.py", line 917, in start_socket
raise ex
File "/opt/fhem/.local/lib/python3.9/site-packages/aiotinytuya/core.py", line 894, in start_socket
self.reader, self.writer = await asyncio.open_connection(
File "/usr/lib/python3.9/asyncio/streams.py", line 52, in open_connection
transport, _ = await loop.create_connection(
File "/usr/lib/python3.9/asyncio/base_events.py", line 1056, in create_connection
raise exceptions[0]
File "/usr/lib/python3.9/asyncio/base_events.py", line 1041, in create_connection
sock = await self._connect_sock(
File "/usr/lib/python3.9/asyncio/base_events.py", line 955, in _connect_sock
await self.sock_connect(sock, address)
File "/usr/lib/python3.9/asyncio/selector_events.py", line 502, in sock_connect
return await fut
File "/usr/lib/python3.9/asyncio/selector_events.py", line 537, in _sock_connect_cb
raise OSError(err, f'Connect call failed {address}')
ConnectionRefusedError: [Errno 111] Connect call failed ('192.168.0.61', 6668)
2023-10-06 01:00:18,130 - ERROR - tuya_local_bffbc4082b5d59xxxxxxx: Failed to connect to device
Traceback (most recent call last):
File "/opt/fhem/.local/lib/python3.9/site-packages/fhempy/lib/tuya/tuya.py", line 563, in setup_connection
self._connected_device = await asyncio.wait_for(connect_fct, timeout=15)
File "/usr/lib/python3.9/asyncio/tasks.py", line 481, in wait_for
return fut.result()
File "/opt/fhem/.local/lib/python3.9/site-packages/aiotinytuya/__init__.py", line 206, in connect
await device.start_socket()
File "/opt/fhem/.local/lib/python3.9/site-packages/aiotinytuya/core.py", line 917, in start_socket
raise ex
File "/opt/fhem/.local/lib/python3.9/site-packages/aiotinytuya/core.py", line 894, in start_socket
self.reader, self.writer = await asyncio.open_connection(
File "/usr/lib/python3.9/asyncio/streams.py", line 52, in open_connection
transport, _ = await loop.create_connection(
File "/usr/lib/python3.9/asyncio/base_events.py", line 1056, in create_connection
raise exceptions[0]
File "/usr/lib/python3.9/asyncio/base_events.py", line 1041, in create_connection
sock = await self._connect_sock(
File "/usr/lib/python3.9/asyncio/base_events.py", line 955, in _connect_sock
kleiner auszug. ab 6.10. fehlermeldungen
Hmm,
ich bin da leider auch kein Experte.
Was ich meine sehen zu können dass Devices nicht erreicht werden.
In deinem Auszug sehe ich 2:
tuya_local_bf43718f426xxxxxxx
tuya_local_bffbc4082b5d59xxxxxxx
Die Devices sind aber in der Tuya/Smarthome App erreichbar?
Hast du etwas an deinem Hausnetzwerk geändert?
Irgendetwas muss ja am 2023-10-06 01:00:17,639 passiert sein.
Vom Log würde ich sagen du hast das update auf 0.1.665 eingespielt.
Das ist aber genau die Version die ich ohne Probleme benutze.
Hast du mal FHEM komplett gestoppt und wieder gestartet?
Nach dem stoppen von FHEM kannst du auch mal schauen ob noch ein prozess fhempy läuft.
Wenn er nach dem stoppen von FHEM noch läuft denn mal abschießen und FHEM wieder starten.
Gruß,
Stefan
ich resettiere täglich um 01:00 den fhempy connector, natürlich auch update wenn vorhanden. über tuyaapp normal steuerbar, auch readings der strommesserkommen an.
Hallo,
erstmal vielen Dank an Dominik für seine tolle Arbeit.
Ich habe eine Raspberry mit Raspbian 32Bit Lite neu aufgesetzt, FHEM neu installiert und unter TUYA IOT ein neues Konto und eine Projekt angelegt, alles wie in der Anleitung beschrieben. Es gibt in keinem Log Fehlermeldung und alle meine Tuya-Geräte werden sauber im FHEM angezeigt.
ABER ich erhalte nach Neustart des Raspberry immer nur Reading, danach keine mehr. Ich habe einen Türkontaktschalter als Beispiel. Der ist zum Zeitpunkt des Raspberry-Neustarts geschlossen. Nach ein paar Minuten öffne ich den Türkontaktschalter und ein paar Sekunden später zeigt dies auch FHEM an. Das war es dann mit den übertragenen Readings. Ich kann den Türkontaktschalter dann schließen und öffnen so oft ich will, es kommt bei FHEM nichts an.
Im Tuya IOT-Projekt kann ich die Devices debuggen und sehe dort auch die Readings zum Schließen und Öffnen des Türkontaktschalters. Sie werden scheinbar nicht an dem TUYA-Connector im FHEM geleitet.
Muss ich irgendeinen Port in der Fritzbox öffnen und zum Raspberry weiterleiten?
Ich habe im IOT-Projekt die Service APIs "IOT core" und "Device Status Notification" abonniert und der Message Service ist auch aktiviert. Wenn dieser deaktiviert ist, erhalte ich im fhempy-Log die Meldung "Polar aktivieren" (oder so ähnlich). Dann klappt auch das erste Reading nicht. Daher habe ich den Message Service aktiviert. Dort sehe ich unter "Subscription Management" --> "Production Environment" auch mein Projekt mit den Status "Good" und einen Consumer mit der Startzeit des Raspberry. Der Tuya Cloud Connector scheint sich also auch bei Tuya IoT zu verbinden.
Was muss ich noch einstellen, damit die Statusänderungen der Tuya-Geräte an den Cloud Connector übermittelt werden?
Ich habe auch zwei WiFi-Relais, deren Status bzw. Schaltzustände ich über FHEM steuern und ändern kann. Das kann ich in der SmartLife App und auf der Tuya IoT-Seite gut überwachen.
Aber auch bei diesen WiFi-Relais kommen die Änderungen der Schaltzustände nicht im FHEM an, auch nicht, wenn ich sie im FHEM schalte. Es scheint also an der Kommunikation von der Tuya IoT-Cloud zu meinem FHEM Tuya Cloud Connector zu scheitern. Vom Tuya Cloud Connector zu Tuya IoT klappt es ja.
Auf dem Raspberry läuft sonst nichts weiter. Ich habe eine neue SD-Karte verwendet.
Vielen Dank für Eure Antworten.
Holger Gläser
Hallo,
seit Februar liefen meine vielen Tuya-Schaltstecker wunderbar auch mit Doninic's energy-reading.
Seit ca. 10. Januar stehen bei manchen (älteren) Stecker in energy auf Null. Die ist auch in der Smartlife App plötzlich so. Bis 10. 1.24 wurden noch "electric"-Werte angezeigt. Timer können auch nicht mehr gesetzt werden.
In FHEMPY erscheinen immerhin noch der aktuelle Verbrauch.
Dominic, hast du nicht in das energy-reading den aktuellen Verbrauch multipliziert mit der Zeit aufsummiert geschrieben?
Hat sonst noch jemand Erfahrungen damit gemacht?
Hat jemand auch Erfahrungen mit der TUYA/Smartlife- Stromsparfunktion als Abo?
Immerhin wird FMEMPY und TUYA oberattraktiv, da z.B. LIDL kompatible Stromstecker mit Messfunktion demnächst für knapp 6 Euro anbietet.
Herzliche Grüße
Thomas Burkhart
Zitat von: hglaeser am 04 November 2023, 19:44:56Hallo,
erstmal vielen Dank an Dominik für seine tolle Arbeit.
Ich habe eine Raspberry mit Raspbian 32Bit Lite neu aufgesetzt, FHEM neu installiert und unter TUYA IOT ein neues Konto und eine Projekt angelegt, alles wie in der Anleitung beschrieben. Es gibt in keinem Log Fehlermeldung und alle meine Tuya-Geräte werden sauber im FHEM angezeigt.
ABER ich erhalte nach Neustart des Raspberry immer nur Reading, danach keine mehr. Ich habe einen Türkontaktschalter als Beispiel. Der ist zum Zeitpunkt des Raspberry-Neustarts geschlossen. Nach ein paar Minuten öffne ich den Türkontaktschalter und ein paar Sekunden später zeigt dies auch FHEM an. Das war es dann mit den übertragenen Readings. Ich kann den Türkontaktschalter dann schließen und öffnen so oft ich will, es kommt bei FHEM nichts an.
Im Tuya IOT-Projekt kann ich die Devices debuggen und sehe dort auch die Readings zum Schließen und Öffnen des Türkontaktschalters. Sie werden scheinbar nicht an dem TUYA-Connector im FHEM geleitet.
Muss ich irgendeinen Port in der Fritzbox öffnen und zum Raspberry weiterleiten?
Ich habe im IOT-Projekt die Service APIs "IOT core" und "Device Status Notification" abonniert und der Message Service ist auch aktiviert. Wenn dieser deaktiviert ist, erhalte ich im fhempy-Log die Meldung "Polar aktivieren" (oder so ähnlich). Dann klappt auch das erste Reading nicht. Daher habe ich den Message Service aktiviert. Dort sehe ich unter "Subscription Management" --> "Production Environment" auch mein Projekt mit den Status "Good" und einen Consumer mit der Startzeit des Raspberry. Der Tuya Cloud Connector scheint sich also auch bei Tuya IoT zu verbinden.
Was muss ich noch einstellen, damit die Statusänderungen der Tuya-Geräte an den Cloud Connector übermittelt werden?
Ich habe auch zwei WiFi-Relais, deren Status bzw. Schaltzustände ich über FHEM steuern und ändern kann. Das kann ich in der SmartLife App und auf der Tuya IoT-Seite gut überwachen.
Aber auch bei diesen WiFi-Relais kommen die Änderungen der Schaltzustände nicht im FHEM an, auch nicht, wenn ich sie im FHEM schalte. Es scheint also an der Kommunikation von der Tuya IoT-Cloud zu meinem FHEM Tuya Cloud Connector zu scheitern. Vom Tuya Cloud Connector zu Tuya IoT klappt es ja.
Auf dem Raspberry läuft sonst nichts weiter. Ich habe eine neue SD-Karte verwendet.
Vielen Dank für Eure Antworten.
Holger Gläser
Hallo Holger,
ich hatte auch das Problem, dass TUYA-Devices, die nicht ständig im WLAN aktiv sind, von FMEMPY schlechter erkannt werden. Das hat Dominic aber gefixt.
Kannst denn in Smartlife die aktuellen Zustände sehen?
Was für ein WIFi-Relais ist es denn?
In der Fritzbox kannst du auch sehen, wann ein Gerät neu hinzukommt. Noch besser sieht man es mit FING.
Beste Grüße
Thomas
Zitat von: thburkhart am 13 Januar 2024, 14:38:49Hallo,
seit Februar liefen meine vielen Tuya-Schaltstecker wunderbar auch mit Doninic's energy-reading.
Seit ca. 10. Januar stehen bei manchen (älteren) Stecker in energy auf Null. Die ist auch in der Smartlife App plötzlich so. Bis 10. 1.24 wurden noch "electric"-Werte angezeigt. Timer können auch nicht mehr gesetzt werden.
In FHEMPY erscheinen immerhin noch der aktuelle Verbrauch.
Dominic, hast du nicht in das energy-reading den aktuellen Verbrauch multipliziert mit der Zeit aufsummiert geschrieben?
Hat sonst noch jemand Erfahrungen damit gemacht?
Hat jemand auch Erfahrungen mit der TUYA/Smartlife- Stromsparfunktion als Abo?
Immerhin wird FMEMPY und TUYA oberattraktiv, da z.B. LIDL kompatible Stromstecker mit Messfunktion demnächst für knapp 6 Euro anbietet.
Herzliche Grüße
Thomas Burkhart
die Lidl Geräte sind nicht tuya tauglich, die brauchen extra hub
nach heutigem updateversuch auf 0.1.702 kommt es über "restart...please wait" nicht mehr hinaus. :o
Bei mir sieht's wie folgt aus:
# 2024-01-22 18:37:31 version restart...please waitdefine fhempy_local BindingsIo fhempy
attr fhempy_local devStateIcon { my $attr_ver = "1.1.0";;;; my $status_img = "10px-kreis-gruen";;;; my $status_txt = "connected";;;; my $ver = ReadingsVal($name, "version", "-");;;; my $ver_available = ReadingsVal($name, "version_available", $ver);;;; my $update_icon = "";;;; my $refresh_img = "refresh";;;; my $refresh_txt = "Update fhempy";;;; if ($ver_available ne $ver) { $refresh_img = "refresh\@orange";;;; $refresh_txt = "Version ".$ver_available." available for update";;;; } if (ReadingsVal($name, "state", "disconnected") eq "disconnected") { $status_img = "10px-kreis-rot";;;; $status_txt = "disconnected";;;; } $update_icon = "<a href=\"/fhem?cmd.dummy=set $name update&XHR=1\" title=\"Start ".$ver_available." update\">".FW_makeImage($refresh_img, $refresh_txt)."</a>";;;; my $restart_icon = "<a href=\"/fhem?cmd.dummy=set $name restart&XHR=1\" title=\"Restart fhempy\">".FW_makeImage("control_reboot")."</a>";;;; "<div><a>".FW_makeImage($status_img, $status_txt)."</a><a> ".$ver." </a>".$update_icon.$restart_icon."</div>" }
attr fhempy_local group fhempy
attr fhempy_local icon file_json-ld2
attr fhempy_local room fhempy
# BindingType fhempy
# CFGFN ./FHEM/myfhempy.cfg
# DEF fhempy
# DeviceName ws:127.0.0.1:15733
# FD 83
# FUUID 64996c5e-f33f-e986-e1e0-f38fc7c5b5d62104
# IP 127.0.0.1
# NAME fhempy_local
# NR 1146
# NTFY_ORDER 50-fhempy_local
# PARTIAL
# PORT 15733
# STATE opened
# TYPE BindingsIo
# WEBSOCKET 1
# binary 1
# connecttime 1705945072.09664
# devioLoglevel 0
# eventCount 63
# installing 0
# localBinding 1
# nextOpenDelay 10
# prev_error 127.0.0.1: Connection refused (111)
# READINGS:
# 2024-01-21 18:26:18 hostname Fhem
# 2024-01-21 18:26:18 os posix
# 2024-01-21 18:26:18 python 3.11.2
# 2024-01-21 18:26:18 release 6.1.0-17-amd64
# 2024-01-22 18:37:52 state opened
# 2024-01-21 18:26:18 system Linux
# 2024-01-22 18:37:31 version restart...please wait
# 2024-01-22 18:37:52 version_available 0.1.714
# 2024-01-22 18:37:52 version_release_notes <html><a href="https://github.com/fhempy/fhempy/releases" target="_blank">Release Notes</a></html>
# args:
# fhempy_local
# BindingsIo
# fhempy
# helper:
# bm:
# CODE(0x5637a911bfd8):
# cnt 2
# dmx -1000
# dtot 0
# dtotcnt 0
# mTS 22.01. 18:38:19
# max 1.50203704833984e-05
# tot 2.00271606445312e-05
# mAr:
# HASH(0x5637a8f8f998)
# ARRAY(0x5637bdc89c00)
# HASH(0x5637bde41a98)
# CODE(0x5637a911c0b0):
# cnt 73
# dmx -1000
# dtot 0
# dtotcnt 0
# mTS 22.01. 18:30:02
# max 0.00209808349609375
# tot 0.0118904113769531
# mAr:
# HASH(0x5637a8f8f998)
# ARRAY(0x5637bdb49e40)
# HASH(0x5637bdf47178)
# CODE(0x5637a91a06e0):
# cnt 2100376
# dmx -1000
# dtot 0
# dtotcnt 0
# mTS 22.01. 06:26:18
# max 0.253767967224121
# tot 6142.22558450699
# mAr:
# HASH(0x5637a8f8f998)
# CODE(0x5637a91a09c8):
# cnt 15
# dmx -1000
# dtot 0
# dtotcnt 0
# mTS 21.01. 18:26:17
# max 0.00243401527404785
# tot 0.0167138576507568
# mAr:
# HASH(0x5637a8f8f998)
# CODE(0x5637a91a72a0):
# cnt 542720
# dmx -1000
# dtot 0
# dtotcnt 0
# mTS 21.01. 21:52:30
# max 0.0121450424194336
# tot 16.2641866207123
# mAr:
# HASH(0x5637a8f8f998)
# HASH(0x5637ab0ca070)
# messages:
# 0:
# tuya_local_bf1f765162617dcd31ido7:
# tuya_local_bf25adc3b33d91441acnxr:
# tuya_local_bf40c31ece6575958bzage:
# tuya_system:
#
setstate fhempy_local opened
setstate fhempy_local 2024-01-21 18:26:18 hostname Fhem
setstate fhempy_local 2024-01-21 18:26:18 os posix
setstate fhempy_local 2024-01-21 18:26:18 python 3.11.2
setstate fhempy_local 2024-01-21 18:26:18 release 6.1.0-17-amd64
setstate fhempy_local 2024-01-22 18:37:52 state opened
setstate fhempy_local 2024-01-21 18:26:18 system Linux
setstate fhempy_local 2024-01-22 18:37:31 version restart...please wait
setstate fhempy_local 2024-01-22 18:37:52 version_available 0.1.714
setstate fhempy_local 2024-01-22 18:37:52 version_release_notes <html><a href="https://github.com/fhempy/fhempy/releases" target="_blank">Release Notes</a></html>
Ungeachtet dessen scheint das Device seinen Dienst zu tun.
Edit: Jetzt (zum Zeitpunkt dieser Änderung) sieht alles wie erwartet aus. Ich hab die Version 0.1.714.
Hallo zusammen,
bis gestern funktionierten meine tuya devices einwandfrei.
Heute habe ich bei den Geräte den Status: No permissions. Your subscription to cloud development plan has expired.
Wenn ich bei tuya in das Projekt nachschaue sehe ich folgendes unter my subscriptions:
Resource pack name Effective Date Expiration Date Status
oT Core - - 2023-01-20 22:10:01 2023-08-22 08:36:37 In service
Extend Trial Period
Das Expiration Date und der heutige Entzug der permission passen vom Datum nicht zusammen.
Daher vermute ich, dass der Grund für die Sperre vielleicht ein anderer ist zumal der Status In service ist.
Hat diese Meldung schon einmal jemand gehabt und was ist zu tun, damit der Service wieder funktioniert.
Der Zugang vom tuya cloud connector funktioniert, status ist connected.
Ansonsten finde ich bei tuya nur die Möglichkeit der Verlängerung indem man einen weitergehenden Service kauft.
Weiß jemand, wie ich meine Laufzeit verlängern kann ohne einen hohen Dollarbetrag zu bezahlen?
Viele Grüße
Werner
sooo, account jetzt eingeschränkt nutzbar. login klappt, sehe auch meine devices, aber man soll jetzt formular ausfüllen, bankdaten bekannt geben etc. das wars dann mit fhempy.
ja, mit 25.000$ weiteren service kaufen, kommt kaum in Frage, also fhempy canceln
Da meine Geräte 80km enfernt sind, geht auch nicht local.
mal sehen, ob ich da mit einer weiteren fhem Installation local etwas zum laufen bekomme.
Mit meiner UMTS Speedbox komme ich leider nicht von der Außenwelt rein. kein VPN, keine Port Weiterleitung
Hat jemand einen Tip?
mfg Werner
Zum Glück hatte ich nur wenige TUYA Geräte. Da fhempy bei mir nicht mehr laufen wollte, habe ich sie nun durch Zigbee-Geräte ersetzt. Schade, da fhempy meistens sehr gut funktionierte.
Zitat von: McShire am 07 Februar 2024, 19:23:13Mit meiner UMTS Speedbox komme ich leider nicht von der Außenwelt rein. kein VPN, keine Port Weiterleitung
Hat jemand einen Tip?
da ich dieses scenario auch im hinterkopf habe, hatte ich mir letztens diesen post zum thema gespeichert. keine ahnung was dahinter steckt.
ein post weiter gibt es noch ein paar infos dazu.
Zitat von: youngster am 01 September 2023, 15:32:08Bearbeite aktuell FHEM @home fuer externen Zugriff.
Scheint nur mit tailscale.com (https://tailscale.com/) zu funktionieren, habe ja keine
oeffentliche IP Adresse und will den Server anfunken.
"allowed" ein paar einzelne Tailscale IPs eintragen sollte reichen...
Hallo allerseits,
ich habe seit ein paar Tagen das Problem, dass meine Tuya T&H Sensoren keine Daten mehr liefern.
Das Problem, dass nur ein Reading funktionierte, hatte ich mit einem restart des FHEMPY Servers alle 15min gelöst, das reichte mir.
Aber seit 21.3. abends bekomme ich nun gar nix mehr.
Beim Restart des Servers kommen pro Device folgende Zeilen im fhempy.log.
(Der FHEMPY funktioniert aber einwandfrei mit meiner GREE Klimaanlage.)
Die Sensoren selbst (4 Stk) funktioniert ebenfalls einwandfrei mit der eigenen App.
In der Tuya Cloud scheint das Projekt "normal" zu funktionieren, sogar die "Device Status Notification" ist noch bis 5.4.2024 aktiv (testversion)
Ich wäre sehr dankbar über Hinweise, bin selbst kein Programmierer und hab dementsprechend null Plan warum das nicht mehr funktioniert :o
2024-03-26 18:06:56,498 - ERROR - tuya_cloud_bf75004b6ad7ed5ecf78rf: 'result'
Traceback (most recent call last):
File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 45, in _init_device
await self._setup_device()
File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/fhempy/lib/tuya_cloud/tuya_cloud_device.py", line 74, in _setup_device
self._t_info = await utils.run_blocking(
File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/fhempy/lib/utils.py", line 72, in run_blocking
return await asyncio.get_event_loop().run_in_executor(pool, function)
File "/usr/lib/python3.9/concurrent/futures/thread.py", line 52, in run
result = self.fn(*self.args, **self.kwargs)
File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/tuya_iot/device.py", line 332, in get_device_info
return self.device_manage.get_device_info(device_id)
File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/tuya_iot/device.py", line 580, in get_device_info
response["result"].pop("status")
KeyError: 'result'
Danke O:-) O:-)
LG Mario