[ESPHome] Beta release

Malaus

@dutchman zurecht kommt man schon. Es gibt für jeden Wert einen extra Ordner.

Schöner fände ich selbst, wenn es so aufgebaut wäre:
Bildschirmfoto 2021-02-28 um 18.34.56.png

Aber vielleicht bin ich da auch einfach zu verwöhnt.

Dutchman

@malaus sagte in [ESPHome] Beta release:

@dutchman zurecht kommt man schon. Es gibt für jeden Wert einen extra Ordner.

Schöner fände ich selbst, wenn es so aufgebaut wäre:

Aber vielleicht bin ich da auch einfach zu verwöhnt.

Jup biste , kan ich hardcoded machen und Dan müsst ihr bei jeder Änderung warten bist der Entwickler mal Zeit hat.
Habe es jetzt so dynamisch gebaut das es immer passt und sehr einfach zu erweitern ist

Beachte hier das ein Gerät viele verschiedenen Sensoren haben kan, also die Struktur ist

Gerät | Type | senorID | werte

Und Dan willste die Struktur schließe mal 60 ds18b20 an Dan weißte warum

FredF

@Dutchman Ich hatte ja schon die 0.0.1 installiert gehabt, das update auf die 0.1.0 hat dann nicht geklappt. Deinstallieren und neu installieren ergab folgendes log. Adapter bleibt rot. Any idea?

2021-02-28 18:55:05.674 - info: host.ioBrokerVM iobroker url "https://github.com/iobroker-community-adapters/ioBroker.esphome.git"
2021-02-28 18:55:07.170 - info: host.ioBrokerVM iobroker install iobroker-community-adapters/ioBroker.esphome#7f27e520b9b4d4aff31e4007a0a22112b529d068
2021-02-28 18:55:07.362 - info: host.ioBrokerVM iobroker NPM version: 6.14.11npm install iobroker-community-adapters/ioBroker.esphome#7f27e520b9b4d4aff31e4007a0a22112b529d068 --loglevel error --prefix "/opt/iobroker" (System call)
2021-02-28 18:55:33.255 - info: host.ioBrokerVM iobroker upload [4] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/words.js words.js application/javascript
2021-02-28 18:55:33.345 - info: host.ioBrokerVM iobroker upload [3] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/style.css style.css text/css
2021-02-28 18:55:33.400 - info: host.ioBrokerVM iobroker upload [2] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/index_m.html index_m.html text/html
2021-02-28 18:55:33.454 - info: host.ioBrokerVM iobroker upload [1] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/esphome.png esphome.png image/png
2021-02-28 18:55:33.510 - info: host.ioBrokerVM iobroker upload [0] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/admin.d.ts admin.d.ts video/mp2t
2021-02-28 18:55:34.603 - info: host.ioBrokerVM iobroker exit 0
2021-02-28 18:55:35.450 - info: host.ioBrokerVM Updating repository "Stable (default)" under "http://download.iobroker.net/sources-dist.json"
2021-02-28 18:55:58.277 - info: host.ioBrokerVM iobroker add esphome --host ioBrokerVM
2021-02-28 18:55:59.364 - info: host.ioBrokerVM iobroker host.ioBrokerVM create instance esphome
2021-02-28 18:55:59.373 - info: host.ioBrokerVM iobroker host.ioBrokerVM object esphome.0.info.connection created
2021-02-28 18:55:59.401 - info: host.ioBrokerVM iobroker host.ioBrokerVM object esphome.0.info created
2021-02-28 18:55:59.433 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.logLevel created
2021-02-28 18:55:59.464 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.sigKill created
2021-02-28 18:55:59.493 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.eventLoopLag created
2021-02-28 18:55:59.522 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.outputCount created
2021-02-28 18:55:59.553 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.inputCount created
2021-02-28 18:55:59.585 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.uptime created
2021-02-28 18:55:59.614 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.memRss created
2021-02-28 18:55:59.643 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.memHeapTotal created
2021-02-28 18:55:59.680 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.memHeapUsed created
2021-02-28 18:55:59.713 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.cputime created
2021-02-28 18:55:59.746 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.cpu created
2021-02-28 18:55:59.776 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.compactMode created
2021-02-28 18:55:59.805 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.connected created
2021-02-28 18:55:59.835 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.alive created
2021-02-28 18:55:59.863 - info: host.ioBrokerVM iobroker host.ioBrokerVM Set default value of esphome.0.info.connection: false
2021-02-28 18:55:59.897 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0 created
2021-02-28 18:56:00.907 - info: host.ioBrokerVM iobroker exit 0
2021-02-28 18:56:02.971 - info: host.ioBrokerVM instance system.adapter.esphome.0 started with pid 24145
2021-02-28 18:56:03.746 - info: esphome.0 (24145) starting. Version 0.1.0 in /opt/iobroker/node_modules/iobroker.esphome, node: v12.21.0, js-controller: 3.2.16
2021-02-28 18:56:03.988 - error: esphome.0 (24145) uncaught exception: type rdhandoffF340B8D1-895A-47D4-BE75-0749071A6C85 has more than 20 characters
2021-02-28 18:56:03.988 - error: esphome.0 (24145) Error: type rdhandoffF340B8D1-895A-47D4-BE75-0749071A6C85 has more than 20 characters
at checkFormat (/opt/iobroker/node_modules/mdns-js/lib/service_type.js:244:11)
at exports.ServiceType.fromString (/opt/iobroker/node_modules/mdns-js/lib/service_type.js:118:5)
at new exports.ServiceType (/opt/iobroker/node_modules/mdns-js/lib/service_type.js:31:14)
at /opt/iobroker/node_modules/mdns-js/lib/decoder.js:40:27
at /opt/iobroker/node_modules/dns-js/lib/dnspacket.js:223:7
at Array.forEach ()
at module.exports.each (/opt/iobroker/node_modules/dns-js/lib/dnspacket.js:221:17)
at module.exports.decodeSection (/opt/iobroker/node_modules/mdns-js/lib/decoder.js:26:10)
at /opt/iobroker/node_modules/mdns-js/lib/decoder.js:111:5
at Array.forEach ()
2021-02-28 18:56:03.989 - error: esphome.0 (24145) type rdhandoffF340B8D1-895A-47D4-BE75-0749071A6C85 has more than 20 characters
2021-02-28 18:56:03.996 - info: esphome.0 (24145) terminating
2021-02-28 18:56:03.997 - warn: esphome.0 (24145) Terminated (UNCAUGHT_EXCEPTION): Without reason
2021-02-28 18:56:04.573 - error: host.ioBrokerVM instance system.adapter.esphome.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2021-02-28 18:56:04.573 - info: host.ioBrokerVM Restart adapter system.adapter.esphome.0 because enabled

Dutchman

@fredf sagte in [ESPHome] Beta release:

@Dutchman Ich hatte ja schon die 0.0.1 installiert gehabt, das update auf die 0.1.0 hat dann nicht geklappt. Deinstallieren und neu installieren ergab folgendes log. Adapter bleibt rot. Any idea?

2021-02-28 18:55:05.674 - info: host.ioBrokerVM iobroker url "https://github.com/iobroker-community-adapters/ioBroker.esphome.git"
2021-02-28 18:55:07.170 - info: host.ioBrokerVM iobroker install iobroker-community-adapters/ioBroker.esphome#7f27e520b9b4d4aff31e4007a0a22112b529d068
2021-02-28 18:55:07.362 - info: host.ioBrokerVM iobroker NPM version: 6.14.11npm install iobroker-community-adapters/ioBroker.esphome#7f27e520b9b4d4aff31e4007a0a22112b529d068 --loglevel error --prefix "/opt/iobroker" (System call)
2021-02-28 18:55:33.255 - info: host.ioBrokerVM iobroker upload [4] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/words.js words.js application/javascript
2021-02-28 18:55:33.345 - info: host.ioBrokerVM iobroker upload [3] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/style.css style.css text/css
2021-02-28 18:55:33.400 - info: host.ioBrokerVM iobroker upload [2] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/index_m.html index_m.html text/html
2021-02-28 18:55:33.454 - info: host.ioBrokerVM iobroker upload [1] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/esphome.png esphome.png image/png
2021-02-28 18:55:33.510 - info: host.ioBrokerVM iobroker upload [0] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/admin.d.ts admin.d.ts video/mp2t
2021-02-28 18:55:34.603 - info: host.ioBrokerVM iobroker exit 0
2021-02-28 18:55:35.450 - info: host.ioBrokerVM Updating repository "Stable (default)" under "http://download.iobroker.net/sources-dist.json"
2021-02-28 18:55:58.277 - info: host.ioBrokerVM iobroker add esphome --host ioBrokerVM
2021-02-28 18:55:59.364 - info: host.ioBrokerVM iobroker host.ioBrokerVM create instance esphome
2021-02-28 18:55:59.373 - info: host.ioBrokerVM iobroker host.ioBrokerVM object esphome.0.info.connection created
2021-02-28 18:55:59.401 - info: host.ioBrokerVM iobroker host.ioBrokerVM object esphome.0.info created
2021-02-28 18:55:59.433 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.logLevel created
2021-02-28 18:55:59.464 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.sigKill created
2021-02-28 18:55:59.493 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.eventLoopLag created
2021-02-28 18:55:59.522 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.outputCount created
2021-02-28 18:55:59.553 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.inputCount created
2021-02-28 18:55:59.585 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.uptime created
2021-02-28 18:55:59.614 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.memRss created
2021-02-28 18:55:59.643 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.memHeapTotal created
2021-02-28 18:55:59.680 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.memHeapUsed created
2021-02-28 18:55:59.713 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.cputime created
2021-02-28 18:55:59.746 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.cpu created
2021-02-28 18:55:59.776 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.compactMode created
2021-02-28 18:55:59.805 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.connected created
2021-02-28 18:55:59.835 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0.alive created
2021-02-28 18:55:59.863 - info: host.ioBrokerVM iobroker host.ioBrokerVM Set default value of esphome.0.info.connection: false
2021-02-28 18:55:59.897 - info: host.ioBrokerVM iobroker host.ioBrokerVM object system.adapter.esphome.0 created
2021-02-28 18:56:00.907 - info: host.ioBrokerVM iobroker exit 0
2021-02-28 18:56:02.971 - info: host.ioBrokerVM instance system.adapter.esphome.0 started with pid 24145
2021-02-28 18:56:03.746 - info: esphome.0 (24145) starting. Version 0.1.0 in /opt/iobroker/node_modules/iobroker.esphome, node: v12.21.0, js-controller: 3.2.16
2021-02-28 18:56:03.988 - error: esphome.0 (24145) uncaught exception: type rdhandoffF340B8D1-895A-47D4-BE75-0749071A6C85 has more than 20 characters
2021-02-28 18:56:03.988 - error: esphome.0 (24145) Error: type rdhandoffF340B8D1-895A-47D4-BE75-0749071A6C85 has more than 20 characters
at checkFormat (/opt/iobroker/node_modules/mdns-js/lib/service_type.js:244:11)
at exports.ServiceType.fromString (/opt/iobroker/node_modules/mdns-js/lib/service_type.js:118:5)
at new exports.ServiceType (/opt/iobroker/node_modules/mdns-js/lib/service_type.js:31:14)
at /opt/iobroker/node_modules/mdns-js/lib/decoder.js:40:27
at /opt/iobroker/node_modules/dns-js/lib/dnspacket.js:223:7
at Array.forEach ()
at module.exports.each (/opt/iobroker/node_modules/dns-js/lib/dnspacket.js:221:17)
at module.exports.decodeSection (/opt/iobroker/node_modules/mdns-js/lib/decoder.js:26:10)
at /opt/iobroker/node_modules/mdns-js/lib/decoder.js:111:5
at Array.forEach ()
2021-02-28 18:56:03.989 - error: esphome.0 (24145) type rdhandoffF340B8D1-895A-47D4-BE75-0749071A6C85 has more than 20 characters
2021-02-28 18:56:03.996 - info: esphome.0 (24145) terminating
2021-02-28 18:56:03.997 - warn: esphome.0 (24145) Terminated (UNCAUGHT_EXCEPTION): Without reason
2021-02-28 18:56:04.573 - error: host.ioBrokerVM instance system.adapter.esphome.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2021-02-28 18:56:04.573 - info: host.ioBrokerVM Restart adapter system.adapter.esphome.0 because enabled

Haste komplett deinstalliert oder nur die Instanzen gelöscht? Was für ein System ist das (Linux, Windows ? Und welche Node bzw npm Version)

FredF

@dutchman komplett Adapter deinstalliert, die vorherige Version aht ja geklappt.

fred@ioBrokerVM:~$ iob -v
3.2.16
fred@ioBrokerVM:~$ iob status
iobroker is running on this host.


Objects type: jsonl
States  type: jsonl
fred@ioBrokerVM:~$ which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs
/usr/bin/nodejs
v12.21.0
/usr/bin/node
v12.21.0
/usr/bin/npm
6.14.11
nodejs:
 Installiert:           12.21.0-1nodesource1
 Installationskandidat: 12.21.0-1nodesource1
 Versionstabelle:
*** 12.21.0-1nodesource1 500
       500 https://deb.nodesource.com/node_12.x buster/main amd64 Packages
       100 /var/lib/dpkg/status
    10.24.0~dfsg-1~deb10u1 500
       500 http://security.debian.org/debian-security buster/updates/main amd64 Packages
    10.21.0~dfsg-1~deb10u1 500
       500 http://deb.debian.org/debian buster/main amd64 Packages
fred@ioBrokerVM:~$

Dutchman

@fredf sagte in [ESPHome] Beta release:

@dutchman komplett Adapter deinstalliert, die vorherige Version aht ja geklappt.

fred@ioBrokerVM:~$ iob -v
3.2.16
fred@ioBrokerVM:~$ iob status
iobroker is running on this host.


Objects type: jsonl
States  type: jsonl
fred@ioBrokerVM:~$ which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs
/usr/bin/nodejs
v12.21.0
/usr/bin/node
v12.21.0
/usr/bin/npm
6.14.11
nodejs:
 Installiert:           12.21.0-1nodesource1
 Installationskandidat: 12.21.0-1nodesource1
 Versionstabelle:
*** 12.21.0-1nodesource1 500
       500 https://deb.nodesource.com/node_12.x buster/main amd64 Packages
       100 /var/lib/dpkg/status
    10.24.0~dfsg-1~deb10u1 500
       500 http://security.debian.org/debian-security buster/updates/main amd64 Packages
    10.21.0~dfsg-1~deb10u1 500
       500 http://deb.debian.org/debian buster/main amd64 Packages
fred@ioBrokerVM:~$

Hmm ja was ich dir mit Sicherheit sagen kan ist da es ein NPM Installations Fehler ist der nicht vom Adapter selber kommt aus irgend einem Grund kan er da was nicht Auflösen.

Würde empfehlen mal den fixer drüber laufen U lassen

FredF

@dutchman Nope, gleiches Verhalten/Fehlermeldung

Dutchman

@fredf sagte in [ESPHome] Beta release:

@dutchman Nope, gleiches Verhalten/Fehlermeldung

@apollon77 hast du eventuell ne idee ?

Markus_

@liv-in-sky @Dutchman
Ich kann das Problem Bestätigen. Bei mir werden auch 2 Amazon Geräte gefunden

esphome.0	2021-02-28 19:59:03.324	error	(21729) ESPHome client 192.168.0.229 Error: connect ECONNREFUSED 127.0.0.1:6053
esphome.0	2021-02-28 19:59:03.322	error	(21729) ESPHome client 192.168.0.166 Error: connect ECONNREFUSED 127.0.0.1:6053
esphome.0	2021-02-28 19:59:03.320	info	(21729) Initiate 192.168.0.229
esphome.0	2021-02-28 19:59:03.318	info	(21729) Initiate 192.168.0.166
esphome.0	2021-02-28 19:58:33.322	error	(21729) ESPHome client 192.168.0.229 Error: connect ECONNREFUSED 127.0.0.1:6053
esphome.0	2021-02-28 19:58:33.320	error	(21729) ESPHome client 192.168.0.166 Error: connect ECONNREFUSED 127.0.0.1:6053
esphome.0	2021-02-28 19:58:33.316	info	(21729) Initiate 192.168.0.229
esphome.0	2021-02-28 19:58:33.315	info	(21729) Initiate 192.168.0.166
esphome.0	2021-02-28 19:58:03.322	error	(21729) ESPHome client 192.168.0.229 Error: connect ECONNREFUSED 127.0.0.1:6053
esphome.0	2021-02-28 19:58:03.317	error	(21729) ESPHome client 192.168.0.166 Error: connect ECONNREFUSED 127.0.0.1:6053
esphome.0	2021-02-28 19:58:03.311	info	(21729) Initiate 192.168.0.229
esphome.0	2021-02-28 19:58:03.303	info	(21729) Initiate 192.168.0.166
esphome.0	2021-02-28 19:57:33.498	error	(21729) ESPHome client 192.168.0.229 Error: connect ECONNREFUSED 192.168.0.229:6053
esphome.0	2021-02-28 19:57:33.487	info	(21729) Initiate 192.168.0.229
esphome.0	2021-02-28 19:57:33.486	info	(21729) [AutoDiscovery] New ESPHome device found at IP 192.168.0.229
esphome.0	2021-02-28 19:57:33.480	info	(21729) ESPHome client test on ip 192.168.0.179 initialized
esphome.0	2021-02-28 19:57:33.398	info	(21729) ESPHome Device info received for test
esphome.0	2021-02-28 19:57:33.386	error	(21729) ESPHome client 192.168.0.166 Error: connect ECONNREFUSED 192.168.0.166:6053
esphome.0	2021-02-28 19:57:33.382	info	(21729) ESPHome client 192.168.0.179 connected
esphome.0	2021-02-28 19:57:33.375	info	(21729) Initiate 192.168.0.166
esphome.0	2021-02-28 19:57:33.373	info	(21729) [AutoDiscovery] New ESPHome device found at IP 192.168.0.166
esphome.0	2021-02-28 19:57:33.296	info	(21729) Initiate 192.168.0.179
esphome.0	2021-02-28 19:57:33.183	info	(21729) starting. Version 0.1.0 in /opt/iobroker/node_modules/iobroker.esphome, node: v12.20.2, js-controller: 3.2.16
esphome.0	2021-02-28 19:57:22.693	warn	(6761) ESPHome client 192.168.0.179 disconnected
esphome.0	2021-02-28 19:57:22.692	warn	(6761) ESPHome client 192.168.0.179 disconnected
esphome.0	2021-02-28 19:57:22.683	info	(6761) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
esphome.0	2021-02-28 19:57:22.681	info	(6761) terminating
esphome.0	2021-02-28 19:57:22.675	info	(6761) Got terminate signal TERMINATE_YOURSELF
esphome.0	2021-02-28 19:50:09.656	info	(6761) ESPHome client test on ip 192.168.0.179 initialized
esphome.0	2021-02-28 19:50:09.604	info	(6761) ESPHome Device info received for test
esphome.0	2021-02-28 19:50:09.586	info	(6761) ESPHome client 192.168.0.179 connected
esphome.0	2021-02-28 19:50:09.467	info	(6761) Initiate 192.168.0.179
esphome.0	2021-02-28 19:50:09.449	info	(6761) [AutoDiscovery] New ESPHome device found at IP 192.168.0.179

apollon77

@dutchman Was ist die Frage? Install läuft ja durch, dann crasht der Adapter ...

Dutchman

@apollon77 sagte in [ESPHome] Beta release:

@dutchman Was ist die Frage? Install läuft ja durch, dann crasht der Adapter ...

ging hierum :

@malaus sagte in [ESPHome] Beta release:

Bei mir kommt ebenfalls die Fehlermeldung 25:

$ ./iobroker url "https://github.com/iobroker-community-adapters/ioBroker.esphome"
Info: Can not get current GitHub commit, we remember master branch only. Status: 422 (No commit found for SHA: master)
install https://github.com/iobroker-community-adapters/ioBroker.esphome/tarball/master
NPM version: 6.14.11
npm install https://github.com/iobroker-community-adapters/ioBroker.esphome/tarball/master --loglevel error --prefix "/opt/iobroker" (System call)
npm
 ERR! code E404
npm
 ERR! 
404 Not Found - GET https://codeload.github.com/iobroker-community-adapters/ioBroker.esphome/legacy.tar.gz/master
npm ERR!
 404 
npm ERR!
 404  'https://github.com/iobroker-community-adapters/ioBroker.esphome/tarball/master' is not in the npm registry.
npm ERR!
 404 Your package name is not valid, because 
npm ERR!
 
404  1. name can only contain URL-friendly charactersnpm ERR! 404  2. name can no longer contain capital lettersnpm ERR! 404 npm ERR! 404 Note that you can also install from anpm ERR! 404 tarball, folder, http url, or git url.
npm ERR! A complete log of this run can be found in:npm ERR!     /home/iobroker/.npm/_logs/2021-02-28T11_14_11_035Z-debug.log
ERROR: host.raspberrypi Cannot install https://github.com/iobroker-community-adapters/ioBroker.esphome/tarball/master: 1
ERROR: process exited with code 25

Dutchman

@markus_ sagte in [ESPHome] Beta release:

Ich kann das Problem Bestätigen. Bei mir werden auch 2 Amazon Geräte gefunden

ok thanks kan es reproduzieren und beheben

apollon77

@dutchman js-controller 3.2??

FredF

@apollon77 Ja.
https://forum.iobroker.net/topic/42741/esphome-beta-release/28?_=1614580980648

apollon77

@fredf Dann bitte dafürmal js.controller issue anlegen. müssen wir da ansehen.

bigd-73

@dutchman Vielen Dank für die Integration. Ist geplant die "Light" Komponente mit einzubauen?

SG
Mario

Dutchman

@bigd-73 sagte in [ESPHome] Beta release:

@dutchman Vielen Dank für die Integration. Ist geplant die "Light" Komponente mit einzubauen?

SG
Mario

Kan ich einbauen sobald ich ein Beispiel dafür bekomme.
Der Adapter sollte ne Meldung geben “type Not supporters. Und Dan Informationen geben die dem Entwickler geschickt werden müssen

bigd-73

@dutchman Danke für die schnelle Antwort ...
Hier ein Link für einige Beispielkonfigurationen: QuinLED-Quad
Für mich persönlich wäre die "1x RGBW" Led Strip Variante aus diesen Beispielen interessant.

Log kann ich erst später analysieren ...

Danke

SG
Mario

bigd-73

@dutchman "Not supported" kann ich im Log leider nicht finden. Ist auf "debug" gestellt.
Die Config der Licht Komponente wird bereits richtig in den Objekten angezeigt.

SG
Mario

Dutchman

@bigd-73 sagte in [ESPHome] Beta release:

@dutchman "Not supported" kann ich im Log leider nicht finden. Ist auf "debug" gestellt.
Die Config der Licht Komponente wird bereits richtig in den Objekten angezeigt.

SG
Mario

jup config ja aber states fehlen
Starte mal bitte den adapter neu, es sollte dan eine warn melding kommen (debug nicht noetig, zuviel info !)

DeviceType >TypenName< not yet supported
Please submit git issue with all information from next line
DeviceType >TypenName< | State-Keys >ArrayOfKey< | [entityStateConfig] >informationen<

ich brauchte mal die komplette warn log Ausgabe was da kommt, bitte dafuer nicht aus dem admin kopieren (Zeile ist abgeschnitten) sondern log runterladen

Thanks !

NEWS

[ESPHome] Beta release

Support us

802
Online

30.3k
Users

76.4k
Topics

1.2m
Posts

NEWS

[ESPHome] Beta release

Support us

802Online

30.3kUsers

76.4kTopics

1.2mPosts

802
Online

30.3k
Users

76.4k
Topics

1.2m
Posts