fhempy: tuya_cloud ZigBee

thburkhart · 21 Januar 2023, 14:12:48

hi Dominik,
ich mache mal ein neues Thema auf:

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?

und die readings kommen dann automatisch?

thburkhart · 21 Januar 2023, 14:21:22

Zitat
Übrigens, bei den ZigBee Devices würde ich die zigbee2mqtt empfehlen, dann bist die Cloud komplett los.

wie findet man dies zigbee2mqtt bei Amazon spezifischer?
habe es mit

Code Auswählen

zigbee2mqtt tuya versucht

gibt es Empfehlungen für Temperatur/humidity/Luftqualität ? dann würde ich meine Lacrosse ersetzen können

habe zuletzt https://www.amazon.de/gp/product/B0BHW2Y5QC/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 gekauft.
Sind die 2mqtt ?

man muss auch darauf achten, dass die Sensoren auch negative Temperaturen loggen können

Als Gateway verwende ich
https://www.amazon.de/gp/product/B09PQW3H85/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

und bin damit zufrieden.

dominik · 21 Januar 2023, 14:31:58

Hi,
du verwendest dann am einfachsten das fhempy zigbee2mqtt Modul. Damit wird z2m automatisch installiert und du kannst es auch über Fhem aktualisieren.
Du brauchst nur einmalig einen ZigBee USB Adapter (z.B. sonoff ZigBee USB plus). Danach kannst du alle ZigBee tuya Devices komplett ohne Cloud betreiben. Ich nutze das mit meinen Aqara Temperatur Sensoren und mit einen tuya Sensor. Einfach nach ZigBee Temperatur Sensor suchen, dann findest du was...Anbieter ist eigentlich egal, da z2m so gut wie alles unterstützt.

Die Devices werden dann in Fhem als MQTT Device angelegt. Du musst also in Fhem den MQTT Server laufen lassen.

MadMax-FHEM · 21 Januar 2023, 14:36:54

https://zigbee.blakadder.com/

Gruß, Joachim

thburkhart · 21 Januar 2023, 15:00:12

Zitat von: dominik am 21 Januar 2023, 14:31:58
Hi,
du verwendest dann am einfachsten das fhempy zigbee2mqtt Modul. Damit wird z2m automatisch installiert und du kannst es auch über Fhem aktualisieren.
Du brauchst nur einmalig einen ZigBee USB Adapter (z.B. sonoff ZigBee USB plus). Danach kannst du alle ZigBee tuya Devices komplett ohne Cloud betreiben. Ich nutze das mit meinen Aqara Temperatur Sensoren und mit einen tuya Sensor. Einfach nach ZigBee Temperatur Sensor suchen, dann findest du was...Anbieter ist eigentlich egal, da z2m so gut wie alles unterstützt.

Die Devices werden dann in Fhem als MQTT Device angelegt. Du musst also in Fhem den MQTT Server laufen lassen.

wie installiert ein Dummer das fhempy zigbee2mqtt Modul und den FHEM MQTT-Server ?

dominik · 21 Januar 2023, 15:08:13

https://github.com/fhempy/fhempy/blob/master/FHEM/bindings/python/fhempy/lib/zigbee2mqtt/README.md

Mqtt sever
define m2s MQTT2_SERVER 1883 global

thburkhart · 21 Januar 2023, 15:15:00

Zitat von: dominik am 21 Januar 2023, 15:08:13
https://github.com/fhempy/fhempy/blob/master/FHEM/bindings/python/fhempy/lib/zigbee2mqtt/README.md

Mqtt sever
define m2s MQTT2_SERVER 1883 global

super , muss ich gleich ausprobieren..

nur zum Verständnis: wenn ich Tuya_local habe, dann gibt es keinen Grund mehr tuya_cloud wieder zu aktivieren (nur um die ZigBees wieder zu haben)?

dominik · 21 Januar 2023, 15:18:17

Genau, speicher dir noch die localkeys ab, damit du die nicht wieder aus der Cloud holen musst. Achtung, die ändern sich wenn man WiFi neu verbindet.

thburkhart · 21 Januar 2023, 17:13:01

ok
m2s war "running" und verbleibt nun bei "stopping"

Code Auswählen

DeviceOverview
z2m
stopping

z2m
restart
Internals
CFGFN
DEF	
zigbee2mqtt
FHEMPYTYPE
zigbee2mqtt
FUUID
63cc0b86-f33f-fd5f-ca87-52a2b8bea6e261ae
IODev
local_pybinding
NAME
z2m
NR
2562
PYTHONTYPE
zigbee2mqtt
STATE
stopping
TYPE
fhempy
eventCount
10
Readings
installation
successful
2023-01-21 16:59:31
node
v12.22.12
2023-01-21 16:58:16
npm
7.5.2
2023-01-21 16:58:17
state
stopping
2023-01-21 17:00:01

dominik · 21 Januar 2023, 17:26:42

Wenn du z2m installiert hast, sollte es jetzt einen Menüpunkt Zigbee2mqtt geben und dort sollte das Webinterface angezeigt werden.

Wenn m2s nicht tut, dann bitte ins FHEM Log schauen, das ist ein Standard FHEM Modul.

thburkhart · 21 Januar 2023, 19:06:42

Zitat von: dominik am 21 Januar 2023, 17:26:42
Wenn du z2m installiert hast, sollte es jetzt einen Menüpunkt Zigbee2mqtt geben und dort sollte das Webinterface angezeigt werden.

Wenn m2s nicht tut, dann bitte ins FHEM Log schauen, das ist ein Standard FHEM Modul.

FHEM war mal wieder dauerbeschäfttigt ....

nun reagiert es wieder, nachdem ich die tuya_local devices bis auf die temperaturen entfernt habe.
Vielleicht war es nicht gut, diese wieder zu aktivieren und fast zeitgleich z2m zu installieren.

jedenfalls steht nun in z2m:

Code Auswählen

Zigbee2MQTT:info  2023-01-21 17:51:17: Logging to console and directory: '/opt/fhem/.fhempy/zigbee2mqtt/data/log/2023-01-21.17-51-17' filename: log.txt
Zigbee2MQTT:info  2023-01-21 17:51:17: Starting Zigbee2MQTT version 1.29.2 (commit #bb3e8f6d)
Zigbee2MQTT:info  2023-01-21 17:51:17: Starting zigbee-herdsman (0.14.83-hotfix.0)
Zigbee2MQTT:error 2023-01-21 17:51:38: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2023-01-21 17:51:38: Failed to start zigbee
Zigbee2MQTT:error 2023-01-21 17:51:38: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2023-01-21 17:51:38: Exiting...
Zigbee2MQTT:error 2023-01-21 17:51:38: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
    at ZStackAdapter.start (/opt/fhem/.fhempy/zigbee2mqtt/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:103:27)
		Zigbee2MQTT requires node version ^14 || ^16 || ^18 || ^19, you are running v12.22.12!

Zigbee2MQTT:info  2023-01-21 17:52:03: Logging to console and directory: '/opt/fhem/.fhempy/zigbee2mqtt/data/log/2023-01-21.17-52-03' filename: log.txt
Zigbee2MQTT:info  2023-01-21 17:52:03: Starting Zigbee2MQTT version 1.29.2 (commit #bb3e8f6d)
Zigbee2MQTT:info  2023-01-21 17:52:03: Starting zigbee-herdsman (0.14.83-hotfix.0)
2023-01-21 18:05:51,187 - INFO     - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.566...
2023-01-21 18:05:51,192 - INFO     - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-01-21 18:05:51,247 - INFO     - websockets.server: server listening on 0.0.0.0:15733
2023-01-21 18:06:11,645 - INFO     - websockets.server: connection open
2023-01-21 18:06:11,646 - INFO     - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2023-01-21 18:08:14,232 - ERROR    - fhempy.lib.fhem: NO RESPONSE since 60s: readingsEndUpdate($defs{'TUYA_JL07'},1);;
2023-01-21 18:08:14,232 - ERROR    - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'TUYA_JL27'});;

also Fehler

Code Auswählen

Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)

wie korrigiere ich das und wie werden dann die ZigBee-Devices erkannt?

das habe ich im fhempy-log

Code Auswählen

igbee2MQTT:info  2023-01-21 17:52:03: Logging to console and directory: '/opt/fhem/.fhempy/zigbee2mqtt/data/log/2023-01-21.17-52-03' filename: log.txt
Zigbee2MQTT:info  2023-01-21 17:52:03: Starting Zigbee2MQTT version 1.29.2 (commit #bb3e8f6d)
Zigbee2MQTT:info  2023-01-21 17:52:03: Starting zigbee-herdsman (0.14.83-hotfix.0)
2023-01-21 18:05:51,187 - INFO     - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.566...
2023-01-21 18:05:51,192 - INFO     - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-01-21 18:05:51,247 - INFO     - websockets.server: server listening on 0.0.0.0:15733
2023-01-21 18:06:11,645 - INFO     - websockets.server: connection open
2023-01-21 18:06:11,646 - INFO     - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2023-01-21 18:08:14,232 - ERROR    - fhempy.lib.fhem: NO RESPONSE since 60s: readingsEndUpdate($defs{'TUYA_JL07'},1);;
2023-01-21 18:08:14,232 - ERROR    - fhempy.lib.fhem: NO RESPONSE since 60s: readingsBeginUpdate($defs{'TUYA_JL27'});;
2023-01-21 19:22:04,848 - INFO     - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.566...
2023-01-21 19:22:04,852 - INFO     - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2023-01-21 19:22:04,888 - INFO     - websockets.server: server listening on 0.0.0.0:15733
2023-01-21 19:22:11,494 - INFO     - websockets.server: connection open
2023-01-21 19:22:11,494 - INFO     - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'zigbee2mqtt@1.29.2',
npm WARN EBADENGINE   required: { node: '^14 || ^16 || ^18 || ^19' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/console@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/core@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/environment@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/expect@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/expect-utils@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/fake-timers@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/globals@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/reporters@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/schemas@29.0.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/source-map@29.2.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/test-result@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/test-sequencer@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/transform@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@jest/types@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'babel-jest@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'babel-plugin-jest-hoist@29.2.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'babel-preset-jest@29.2.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'diff-sequences@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'eslint-plugin-jest@27.1.7',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'expect@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-changed-files@29.2.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-circus@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-cli@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-config@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-diff@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-docblock@29.2.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-each@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-environment-node@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-get-type@29.2.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-haste-map@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-leak-detector@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-matcher-utils@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-message-util@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-mock@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-regex-util@29.2.0',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-resolve@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-resolve-dependencies@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-runner@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-runtime@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-snapshot@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-util@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-validate@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-watcher@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'jest-worker@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'pretty-format@29.3.1',
npm WARN EBADENGINE   required: { node: '^14.15.0 || ^16.10.0 || >=18.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }

added 753 packages, and audited 754 packages in 28s

67 packages are looking for funding
  run `npm fund` for details

1 high severity vulnerability

To address all issues, run:
  npm audit fix

Run `npm audit` for details.
		Zigbee2MQTT requires node version ^14 || ^16 || ^18 || ^19, you are running v12.22.12!

Zigbee2MQTT:info  2023-01-21 19:22:48: Logging to console and directory: '/opt/fhem/.fhempy/zigbee2mqtt/data/log/2023-01-21.19-22-48' filename: log.txt
Zigbee2MQTT:info  2023-01-21 19:22:48: Starting Zigbee2MQTT version 1.29.2 (commit #bb3e8f6d)
Zigbee2MQTT:info  2023-01-21 19:22:48: Starting zigbee-herdsman (0.14.83-hotfix.0)

dominik · 21 Januar 2023, 20:45:24

Du musst nun zuerst den Zigbee USB Dongle anstecken. Ohne dem kannst sonst nix machen.

thburkhart · 21 Januar 2023, 21:24:53

Zitat von: dominik am 21 Januar 2023, 20:45:24
Du musst nun zuerst den Zigbee USB Dongle anstecken. Ohne dem kannst sonst nix machen.

ui ich habe keinen Dongle

nur das Gateway, das in tuya-Local vorhanden ist

ich habe den fehlermeldungen node.js auf die neueste Version 14.x gebracht.

FHEM war nach dem Start kurz ansprechbar und ging dann für 1h auf 100%

habe nun den Raspi neu gestartet und z2m aus der fhem.cfg raus genommen

FHEM läuft nun wieder normal

und das ist die Info zum Gateway:

Code Auswählen

[code]define TUYA_MMG fhempy tuya pj3gdjgpeqao7xk4 bff304caecd1bfb52dahwu 192.168.9.120 40e85de6c83f63e6 3.3 ea8453wdazquzfl08l0e 8a4b27dd759d4c6a9456aa8155d2a0ea
attr TUYA_MMG DbLogExclude .*
attr TUYA_MMG alias Mini Multi-Mode Gateway
attr TUYA_MMG dp_04 switch_alarm_sound
attr TUYA_MMG dp_32 master_state
attr TUYA_MMG dp_34 factory_reset
attr TUYA_MMG dp_45 alarm_active
attr TUYA_MMG event-on-change-reading .*
attr TUYA_MMG group tuya
attr TUYA_MMG room fhempy
attr TUYA_MMG tuya_spec_functions [{'code': 'switch_alarm_sound', 'dp_id': 4, 'type': 'Boolean', 'values': {}, 'desc': 'switch alarm sound'}, {'code': 'master_state', 'dp_id': 32, 'type': 'Enum', 'values': {'range': ['normal', 'alarm']}, 'desc': 'master state'}, {'code': 'factory_reset', 'dp_id': 34, 'type': 'Boolean', 'values': {}, 'desc': 'factory reset'}, {'code': 'alarm_active', 'dp_id': 45, 'type': 'String', 'values': {'maxlen': 255}, 'desc': 'alarm active'}]
attr TUYA_MMG tuya_spec_status [{'code': 'switch_alarm_sound', 'dp_id': 4, 'type': 'Boolean', 'values': {}}, {'code': 'master_state', 'dp_id': 32, 'type': 'Enum', 'values': {'range': ['normal', 'alarm']}}, {'code': 'factory_reset', 'dp_id': 34, 'type': 'Boolean', 'values': {}}, {'code': 'alarm_active', 'dp_id': 45, 'type': 'String', 'values': {'maxlen': 255}}]
#   DEF        tuya pj3gdjgpeqao7xk4 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
#   DEVICEID   bff304caecd1bfb52dahwu
#   FHEMPYTYPE tuya
#   FUUID      63bc6a73-f33f-fd5f-6f12-f9bd5b3479974128
#   IODev      local_pybinding
#   NAME       TUYA_MMG
#   NR         3034
#   PYTHONTYPE tuya
#   STATE      off
#   TYPE       fhempy
#   eventCount 5
#   READINGS:
#     2023-01-21 21:21:50   dp_01           181
#     2023-01-21 21:21:50   dp_02           34
#     2023-01-21 18:06:44   dp_05           65
#     2023-01-21 18:06:44   dp_06           2271
#     2023-01-21 16:20:38   dp_07           0
#     2023-01-21 11:40:08   dp_09           0
#     2023-01-21 16:20:38   dp_11           0
#     2023-01-21 18:06:44   dp_18           19
#     2023-01-21 18:06:44   dp_19           16
#     2023-01-21 18:06:44   dp_20           2283
#     2023-01-21 11:40:08   dp_21           1
#     2023-01-21 18:06:44   dp_22           710
#     2023-01-21 18:06:44   dp_23           30058
#     2023-01-21 18:06:44   dp_24           20343
#     2023-01-21 18:06:44   dp_25           1025
#     2023-01-20 21:12:07   dp_26           0
#     2023-01-20 20:58:26   master_state    normal
#     2023-01-21 21:21:44   online          1
#     2023-01-21 21:21:50   state           off
#     2023-01-20 20:58:26   switch_alarm_sound off
#   args:
#     TUYA_MMG
#     fhempy
#     tuya
#     pj3gdjgpeqao7xk4
#     bff304caecd1bfb52dahwu
#     192.168.9.120
#     40e85de6c83f63e6
#     3.3
#     ea8453wdazquzfl08l0e
#     8a4b27dd759d4c6a9456aa8155d2a0ea
#   argsh:
#
setstate TUYA_MMG off
setstate TUYA_MMG 2023-01-21 21:21:50 dp_01 181
setstate TUYA_MMG 2023-01-21 21:21:50 dp_02 34
setstate TUYA_MMG 2023-01-21 18:06:44 dp_05 65
setstate TUYA_MMG 2023-01-21 18:06:44 dp_06 2271
setstate TUYA_MMG 2023-01-21 16:20:38 dp_07 0
setstate TUYA_MMG 2023-01-21 11:40:08 dp_09 0
setstate TUYA_MMG 2023-01-21 16:20:38 dp_11 0
setstate TUYA_MMG 2023-01-21 18:06:44 dp_18 19
setstate TUYA_MMG 2023-01-21 18:06:44 dp_19 16
setstate TUYA_MMG 2023-01-21 18:06:44 dp_20 2283
setstate TUYA_MMG 2023-01-21 11:40:08 dp_21 1
setstate TUYA_MMG 2023-01-21 18:06:44 dp_22 710
setstate TUYA_MMG 2023-01-21 18:06:44 dp_23 30058
setstate TUYA_MMG 2023-01-21 18:06:44 dp_24 20343
setstate TUYA_MMG 2023-01-21 18:06:44 dp_25 1025
setstate TUYA_MMG 2023-01-20 21:12:07 dp_26 0
setstate TUYA_MMG 2023-01-20 20:58:26 master_state normal
setstate TUYA_MMG 2023-01-21 21:21:44 online 1
setstate TUYA_MMG 2023-01-21 21:21:50 state off
setstate TUYA_MMG 2023-01-20 20:58:26 switch_alarm_sound off

[/code]

thburkhart · 21 Januar 2023, 21:27:46

und das ist das letzte NpM-log:

Code Auswählen

0 verbose cli /usr/bin/node /usr/bin/npm
1 info using npm@9.3.1
2 info using node@v19.4.0
3 timing npm:load:whichnode Completed in 2ms
4 timing config:load:defaults Completed in 4ms
5 timing config:load:file:/usr/lib/node_modules/npm/npmrc Completed in 23ms
6 timing config:load:builtin Completed in 24ms
7 timing config:load:cli Completed in 6ms
8 timing config:load:env Completed in 1ms
9 timing config:load:project Completed in 2ms
10 timing config:load:file:/root/.npmrc Completed in 0ms
11 timing config:load:user Completed in 1ms
12 timing config:load:file:/usr/etc/npmrc Completed in 0ms
13 timing config:load:global Completed in 1ms
14 timing config:load:setEnvs Completed in 3ms
15 timing config:load Completed in 44ms
16 timing npm:load:configload Completed in 44ms
17 timing npm:load:mkdirpcache Completed in 0ms
18 timing npm:load:mkdirplogs Completed in 0ms
19 verbose title npm i
20 verbose argv "i" "--package-lock-only"
21 timing npm:load:setTitle Completed in 4ms
22 timing config:load:flatten Completed in 8ms
23 timing npm:load:display Completed in 10ms
24 verbose logfile logs-max:10 dir:/root/.npm/_logs/2023-01-21T19_06_51_407Z-
25 verbose logfile /root/.npm/_logs/2023-01-21T19_06_51_407Z-debug-0.log
26 timing npm:load:logFile Completed in 12ms
27 timing npm:load:timers Completed in 1ms
28 timing npm:load:configScope Completed in 0ms
29 timing npm:load Completed in 76ms
30 timing config:load:flatten Completed in 1ms
31 timing arborist:ctor Completed in 2ms
32 silly logfile done cleaning log files
33 timing arborist:ctor Completed in 0ms
34 timing idealTree:init Completed in 70ms
35 timing idealTree:userRequests Completed in 0ms
36 silly idealTree buildDeps
37 timing idealTree:#root Completed in 0ms
38 timing idealTree:buildDeps Completed in 3ms
39 timing idealTree:fixDepFlags Completed in 0ms
40 timing idealTree Completed in 77ms
41 timing reify:loadTrees Completed in 78ms
42 timing reify:save Completed in 5ms
43 timing reify Completed in 90ms
44 timing command:i Completed in 103ms
45 verbose stack Error: ENOENT: no such file or directory, open '/root/package.json'
46 verbose cwd /root
47 verbose Linux 5.15.84-v7l+
48 verbose node v19.4.0
49 verbose npm  v9.3.1
50 error code ENOENT
51 error syscall open
52 error path /root/package.json
53 error errno -2
54 error enoent ENOENT: no such file or directory, open '/root/package.json'
55 error enoent This is related to npm not being able to find a file.
55 error enoent
56 verbose exit -2
57 timing npm Completed in 225ms
58 verbose code -2
59 error A complete log of this run can be found in:
59 error     /root/.npm/_logs/2023-01-21T19_06_51_407Z-debug-0.log

dominik · 21 Januar 2023, 21:56:18

Bitte Schritt für Schritt...was hast du gemacht?

Bitte der Anleitung hier folgen...
https://github.com/fhempy/fhempy/blob/master/FHEM/bindings/python/fhempy/lib/zigbee2mqtt/README.md#usage

...und dann gerne melden bei welchem Befehl welcher Fehler kommt.

Mit dem Tuya Gateway hat das alle nix zu tun. Wie gesagt, du brauchst einen Zigbee Stick. Ich kann den Sonoff Zigbee USB Plus empfehlen.