iobroker tp-link hs100 intergration
License: MIT License
My name is Arthur Rupp. I'm a software developer for different languages, for more than 30 years.
💬 For the past 10 years, I have been working with Smart Home and Building automation. iobroker is here my preferred system
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
LB130 Bulbs are detected and Switching on/off does work, but no parameter for color is available.
It would be great if this would be implemented soon
thanks in advance
Hi, seit heute habe ich folgende Warnmeldung im log vom iobroker,
hs100.0 | 2021-02-09 17:07:20.140 | warn | at TCP._handle.close (net.js:607:12)
-- | -- | -- | --
hs100.0 | 2021-02-09 17:07:20.140 | warn | at Socket.emit (events.js:198:13)
hs100.0 | 2021-02-09 17:07:20.140 | warn | at Object.onceWrapper (events.js:286:20)
hs100.0 | 2021-02-09 17:07:20.140 | warn | at Socket.socket.once (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:104:31)
hs100.0 | 2021-02-09 17:07:20.140 | warn | (920) Info Message setDevice: Error: TCP Socket Closed. segment:0 hadError:false
hs100.0 | 2021-02-09 17:07:05.099 | warn | at TCP._handle.close (net.js:607:12)
hs100.0 | 2021-02-09 17:07:05.099 | warn | at Socket.emit (events.js:198:13)
hs100.0 | 2021-02-09 17:07:05.099 | warn | at Object.onceWrapper (events.js:286:20)
hs100.0 | 2021-02-09 17:07:05.099 | warn | at Socket.socket.once (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:104:31)
hs100.0 | 2021-02-09 17:07:05.099 | warn | (920) Info Message setDevice: Error: TCP Socket Closed. segment:0 hadError:false
hs100.0 | 2021-02-09 17:07:05.092 | warn | at TCP._handle.close (net.js:607:12)
hs100.0 | 2021-02-09 17:07:05.092 | warn | at Socket.emit (events.js:198:13)
hs100.0 | 2021-02-09 17:07:05.092 | warn | at Object.onceWrapper (events.js:286:20)
hs100.0 | 2021-02-09 17:07:05.092 | warn | at Socket.socket.once (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:104:31)
hs100.0 | 2021-02-09 17:07:05.092 | warn | (920) Info Message setDevice: Error: TCP Socket Closed. segment:0 hadError:false
hs100.0 | 2021-02-09 16:53:50.111 | warn | (920) LB setPowerState Socket connection Timeout : 192.168.***.**
-- | -- | -- | --
Node.js
v10.23.2
NPM
6.14.10
Läuft eigentlich seit 3 Monaten stabil und ohne Fehlermeldungen, bis auf heute.
Gruß
It worked just fine a week ago. But today i recognised that the values of my LB130 do not refresh. Found the following in the Log :
2019-12-17 16:49:08.334 - info: host.iobroker instance system.adapter.hs100.0 started with pid 11290
--
2019-12-17 16:49:08.553 - info: hs100.0 starting. Version 1.0.10 in /opt/iobroker/node_modules/iobroker.hs100, node: v10.17.0
2019-12-17 16:49:37.402 - info: host.iobroker object change system.adapter.hs100.0
2019-12-17 16:49:37.402 - info: host.iobroker stopInstance system.adapter.hs100.0
2019-12-17 16:49:37.402 - info: host.iobroker stopInstance system.adapter.hs100.0 killing pid 11290
2019-12-17 16:49:37.412 - error: Caught by controller[0]: TCP Timeout
2019-12-17 16:49:37.412 - error: Caught by controller[0]: (node:11290) UnhandledPromiseRejectionWarning: Error: TCP Timeout
2019-12-17 16:49:37.412 - error: Caught by controller[0]: at Timeout.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/iobroker.hs100/node_modules/tplink-smarthome-api/lib/client.js:226:20)
2019-12-17 16:49:37.412 - error: Caught by controller[0]: at ontimeout (timers.js:436:11)
2019-12-17 16:49:37.412 - error: Caught by controller[0]: at tryOnTimeout (timers.js:300:5)
2019-12-17 16:49:37.412 - error: Caught by controller[0]: at listOnTimeout (timers.js:263:5)
2019-12-17 16:49:37.412 - error: Caught by controller[0]: at Timer.processTimers (timers.js:223:10)
2019-12-17 16:49:37.413 - error: Caught by controller[0]: (node:11290) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
2019-12-17 16:49:37.413 - error: Caught by controller[0]: (node:11290) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
2019-12-17 16:49:37.413 - error: Caught by controller[1]: TCP Timeout
2019-12-17 16:49:37.413 - error: Caught by controller[2]: TCP Timeout
2019-12-17 16:49:37.413 - info: host.iobroker instance system.adapter.hs100.0 terminated with code 156 ()
The LB130 can be pinged from iobroker and controlled through the app.
A HS100 connected to the same instance works fine.
If you need any more log Files or so please reach out to me.
Version: stable=1.0.10 (370 days old) => latest=1.1.5 (18 days old)
Installs: stable=1082 (62.29%), latest=340 (19.57%), total=1737
Click to edit
Hi,
the new js-controller 2.0 will come into latest repository in the next days and we want to make sure that all adapters are working well. We already did a 2 weeks Beta test and so some adapter were aleady checked and some needed slight adjustments.
You can find more information in ioBroker/ioBroker.js-controller#482 and in the ioBroker Forum. If you have more technical questions please write in the referenced issue or in the Developer thread please. General questions are best in the genral thread.
Please update your systems to js-controller 2.0 and check your adapter.
Please close this issue once you have checked your adapter or received successfull reports from users.
Thank you very much for your support. Please contact us in the other Threads or Forum on any question.
2020-04-20 23:24:24.177 - error: host.Server Caught by controller[4]: [HasenLampe] device.send() Error: TCP Timeout
2020-04-20 23:24:24.177 - error: host.Server Caught by controller[4]: at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.hs100/node_modules/tplink-smarthome-api/lib/client.js:226:20)
2020-04-20 23:24:24.177 - error: host.Server Caught by controller[4]: at listOnTimeout (internal/timers.js:549:17)
2020-04-20 23:24:24.177 - error: host.Server Caught by controller[4]: at processTimers (internal/timers.js:492:7)
2020-04-20 23:24:24.177 - error: host.Server Caught by controller[5]: TCP Timeout
2020-04-20 23:24:24.177 - error: host.Server Caught by controller[5]: TCP Timeout
Probably related to js-controller 3 being more restrictive with uncaught errors / rejections.
I'm not 100% sure if that is not an issue with tplink-smarthome-api.
I tried updating the depencency to 2.0.0, which did not cause additional trouble but also did not solve the issue.
Error log then changed to this one:
2020-04-20 23:54:38.029 - error: hs100.0 (11031) uncaught exception: TCP Timeout
2020-04-20 23:54:38.030 - error: hs100.0 (11031) Error: TCP Timeout
at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
at listOnTimeout (internal/timers.js:549:17)
at processTimers (internal/timers.js:492:7)
2020-04-20 23:54:38.031 - info: hs100.0 (11031) terminating
2020-04-20 23:54:38.031 - info: hs100.0 (11031) Terminated (NO_ERROR): Without reason
2020-04-20 23:54:38.662 - error: host.Server Caught by controller[0]: TCP HS110-Deko3:9999 Error: connect EHOSTUNREACH 192.168.0.184:9999
2020-04-20 23:54:38.662 - error: host.Server Caught by controller[0]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16) {
2020-04-20 23:54:38.662 - error: host.Server Caught by controller[0]: errno: 'EHOSTUNREACH',
2020-04-20 23:54:38.662 - error: host.Server Caught by controller[0]: code: 'EHOSTUNREACH',
2020-04-20 23:54:38.662 - error: host.Server Caught by controller[0]: syscall: 'connect',
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[0]: address: '192.168.0.184',
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[0]: port: 9999
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[0]: }
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[1]: TCP HS110-Deko2:9999 Error: connect EHOSTUNREACH 192.168.0.183:9999
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[1]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16) {
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[1]: errno: 'EHOSTUNREACH',
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[1]: code: 'EHOSTUNREACH',
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[1]: syscall: 'connect',
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[1]: address: '192.168.0.183',
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[1]: port: 9999
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[1]: }
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[2]: TCP HS110-Deko1:9999 Error: connect EHOSTUNREACH 192.168.0.182:9999
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[2]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16) {
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[2]: errno: 'EHOSTUNREACH',
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[2]: code: 'EHOSTUNREACH',
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[2]: syscall: 'connect',
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[2]: address: '192.168.0.182',
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[2]: port: 9999
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[2]: }
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[3]: TCP WohnzimmerCouchLampe:9999 Error: TCP Timeout
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[3]: at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[3]: at listOnTimeout (internal/timers.js:549:17)
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[3]: at processTimers (internal/timers.js:492:7)
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[4]: TCP WohnzimmerHasenLampe:9999 Error: TCP Timeout
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[4]: at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[4]: at listOnTimeout (internal/timers.js:549:17)
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[4]: at processTimers (internal/timers.js:492:7)
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[5]: TCP WohnzimmerCouchLampe:9999 Error: TCP Timeout
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[5]: at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[5]: at listOnTimeout (internal/timers.js:549:17)
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[5]: at processTimers (internal/timers.js:492:7)
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[6]: TCP WohnzimmerHasenLampe:9999 Error: TCP Timeout
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[6]: at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[6]: at listOnTimeout (internal/timers.js:549:17)
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[6]: at processTimers (internal/timers.js:492:7)
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[7]: TCP WohnzimmerHasenLampe:9999 Error: TCP Timeout
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[7]: at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[7]: at listOnTimeout (internal/timers.js:549:17)
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[7]: at processTimers (internal/timers.js:492:7)
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[8]: TCP WohnzimmerHasenLampe:9999 Error: TCP Timeout
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[8]: at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[8]: at listOnTimeout (internal/timers.js:549:17)
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[8]: at processTimers (internal/timers.js:492:7)
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[9]: TCP WohnzimmerHasenLampe:9999 Error: TCP Timeout
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[9]: at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[9]: at listOnTimeout (internal/timers.js:549:17)
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[9]: at processTimers (internal/timers.js:492:7)
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[10]: TCP WohnzimmerHasenLampe:9999 Error: TCP Timeout
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[10]: at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[10]: at listOnTimeout (internal/timers.js:549:17)
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[10]: at processTimers (internal/timers.js:492:7)
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[11]: TCP WohnzimmerHasenLampe:9999 Error: TCP Timeout
2020-04-20 23:54:38.663 - error: host.Server Caught by controller[11]: at Timeout._onTimeout (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:62:22)
2020-04-20 23:54:38.664 - error: host.Server Caught by controller[11]: at listOnTimeout (internal/timers.js:549:17)
2020-04-20 23:54:38.664 - error: host.Server Caught by controller[11]: at processTimers (internal/timers.js:492:7)
2020-04-20 23:54:38.664 - info: host.Server instance system.adapter.hs100.0 terminated with code 0 (NO_ERROR)
Voltage wird bei HS110(EU) mit HW Version 1 nicht ausgelesen.
Bei Geräten mit HW Version 2 funktioniert es.
Fehlermeldung nach Update auf js-controller 3.2.4
hs100.0 | 2021-01-10 10:26:42.767 | warn | (520440) State "hs100.0.info.connection" has no existing object, this might lead to an error in future versions
Adapter working fine I can connect to the plug, but it spams my log with this error:
| hs100.0 | 2018-03-30 20:12:21.845 | info | Fehler Dose nicht erreichbar : 192.168.1.24 |
|---|
Describe the bug
Seit dem Update auf v2.0.0 sind zwar bisher keine TCP-Error mehr im Log aufgetaucht, allerdings stoppt jetzt das regelmäßige Update der Steckdosen nach ein paar Minuten. Im Log (auf debug) ist nichts weiter zu sehen, nur das einfach keine Updates mehr erfolgen. Das Intervall ist auf 5 Minuten in den Settings gestellt.
"Verbunden mit hs100" wechselt dann auch von grün auf gelb.
To Reproduce
Einfach Adapter laufen lassen und beobachten, dass 'last-update' nicht mehr aktualisiert wird. Im Log findet auch kein Aktualisierungsversuch mehr statt.
Expected behavior
Regelmäßiges Updaten mit eingestelltem Intervall (wie bei Versionen vor 2.0.0)
Screenshots & Logfiles
log.txt
Auf debug von Start des Adapters bis zum Stopp der Aktualisierung
Versions:
Eventuell liegt das Problem hier?
Line 170 in eff0510
Wenn eine Exception auftritt, wird die zwar nun gefangen, aber nie mehr setTimeout aufgerufen. Dadurch bricht das regelmäßige Updaten vermutlich ab, wobei allerdings kein error in meinem Log auftaucht.
Version: stable=2.0.0 (49 days old) => latest=2.0.1 (15 days old)
Installs: stable=789 (44.7%), latest=321 (18.19%), total=1765
Click to edit
Hi
Würde gerne meine KL60 hinzufügen doch das Feld für Helligkeit fehlt.
Was für Schritte muss ich ungefähr machen damit ich das zum Projekt hinzufügen kann?
Mit freundlichen Grüßen
Paul
Moin @ arteck
VERGISS ES, IST EIN HS100
seit Update auf 3.1.4 bekomm ich sehr oft (mal jede Minute, mal alle halbe Stunde, ...) diese Fehler.
Kommt vom HS100-Adapter.
Vor dem Update waren diese Fehler nicht da.
Liegt das am HS100 oder am JS-Controller?
Heute 12:06 error host.iobroker Caught by controller[0]: TCP 10.0.1.79:9999 Error: TCP Socket Closed. segment:0 hadError:false
Heute 12:06 error hs100.0 Error: TCP Socket Closed. segment:0 hadError:false at Socket.socket.once.hadError (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:113:19) at Object.onceWrapper (events.js:286:20) at Socket.emit (events.js:198:13) at TCP._handle.close (net.js:607:12)
Heute 12:06 error hs100.0 unhandled promise rejection: TCP Socket Closed. segment:0 hadError:false
Heute 12:06 error hs100.0 Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
Heute 12:04 error host.iobroker Caught by controller[1]: TCP 10.0.1.80:9999 Error: TCP Socket Closed. segment:0 hadError:false
Heute 12:04 error hs100.0 Error: TCP Socket Closed. segment:0 hadError:false at Socket.socket.once.hadError (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:113:19) at Object.onceWrapper (events.js:286:20) at Socket.emit (events.js:198:13) at TCP._handle.close (net.js:607:12)
Heute 12:04 error hs100.0 unhandled promise rejection: TCP Socket Closed. segment:0 hadError:false
Heute 12:04 error hs100.0 Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
Ich habe seit einem Jahr zwei hs110 eingebunden, die einwandfrei funktionieren.
Zwecks Erweiterung meines Smarthome habe ich mir eine neue Steckdose, allerdings eine HS100, zugelegt.
Beim Einbinden ins WLAN mittels KASA gab es auch prompt ein Update auf die Steckdose, sie läuft jetzt mit der Version 1.1.1 Build 191209 Rel.093031.
Die Steckdose kann allerdings in den Objekten lediglich geschaltet werden, es gibt keine Strommessungen.
Kann das jemand bestätigen?
The upcoming version 2.0.0 of js-controller will support a new mode for low memory devices. For this, a few minor adjustments to the adapter must be made. Please follow these instructions: https://forum.iobroker.net/viewtopic.php?f=24&t=20387#p213466
I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:
https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/arteck/ioBroker.hs100
I have also found warnings that may be fixed if possible.
Thanks,
your automatic adapter checker.
P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info
Describe the bug
I have a HS110 installed behind a fridge that sometimes loses its wifi connection to the router, which is okay for me actually.
However, the hs100 adapter doesn't like it at all. It detects the TCP timeout, but then crashes with an UNHANDLED_EXCEPTION (Code 6) because there is an unhandled promise rejection.
If the HS110 is unavailable for a few minutes, the adapter repeatedly crashes and is completely stopped by iobroker at some point.
To Reproduce
Steps to reproduce the behavior:
1.) Disconnect HS110 from Network/Power Socket
2.) Watch what happens in log console after some time
Expected behavior
The adapter should handle the TCP timeout exception and not crash.
Screenshots & Logfiles
2021-04-08 10:34:56.617 - info: host.raspi04 instance system.adapter.hs100.0 started with pid 20095
2021-04-08 10:34:58.167 - info: hs100.0 (20095) starting. Version 2.0.1 in /opt/iobroker/node_modules/iobroker.hs100, node: v14.16.1, js-controller: 3.2.16
2021-04-08 10:34:58.306 - info: hs100.0 (20095) Start with IP : 192.168.4.3
2021-04-08 10:34:58.449 - warn: hs100.0 (20095) State "hs100.0.info.connection" has no existing object, this might lead to an error in future versions
2021-04-08 10:34:58.603 - warn: hs100.0 (20095) State "hs100.0.info.connection" has no existing object, this might lead to an error in future versions
2021-04-08 10:35:09.290 - error: hs100.0 (20095) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2021-04-08 10:35:09.290 - error: hs100.0 (20095) unhandled promise rejection: TCP Timeout
2021-04-08 10:35:09.291 - error: hs100.0 (20095) Error: TCP Timeout
2021-04-08 10:35:09.292 - error: hs100.0 (20095) TCP Timeout
2021-04-08 10:35:09.329 - info: hs100.0 (20095) cleaned everything up...
2021-04-08 10:35:09.330 - info: hs100.0 (20095) terminating
2021-04-08 10:35:09.332 - warn: hs100.0 (20095) Terminated (UNCAUGHT_EXCEPTION): Without reason
2021-04-08 10:35:09.334 - warn: hs100.0 (20095) State "hs100.0.info.connection" has no existing object, this might lead to an error in future versions
2021-04-08 10:35:09.902 - error: host.raspi04 instance system.adapter.hs100.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
Versions:
Additional context
does not apply
Dear Adapter developer,
with js-controller 3.2 and js-controller 3.3 some additional checks were added to make sure that created objects match to the specifications and also written state values match to the object definition.
If something is not correct this is logged as 'warning' or 'info' log.
Please take the time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn log there from these checks please adjust the adapter and fix the relevant cases.
For questions please refer to ioBroker/ioBroker.js-controller#1301
Additionally we are preparing Admin 5 which will have a completely rewritten UI. Please install Admin 5, activate that new UI and verify that the configuration of you adapter works as expected also there.
More informations on Admin 5 can be found in Forum https://forum.iobroker.net/topic/44282/test-adapter-admin-5-0-x-alpha-der-neuen-ui
Please close the issue after you checked it.
Thank you very much for your support!
I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:
https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/arteck/ioBroker.hs100
Thanks,
your automatic adapter checker.
P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info
I am an automatic service from ioBroker that searches adapters and makes suggestions.
I noticed that your adapter is not integrated in the ioBroker.discovery. Using the Discovery adapter, ioBroker can automatically find devices or suggest services to the user for installation. If possible I would live to see your adapter added there.
Some adapters have already been added and you can use them as blueprints. See: https://github.com/ioBroker/ioBroker.discovery You need to fork this project and then create a PR for your adapter to be added.
Basically the plugins can do HTTP calls, UDP discovery, MDNS, UPNP and will iterate over all devices found by IP scan and check local serial ports. If you want you can also add new discovery methods but please try to do that with at least dependencies as possible.
Then create one file under lib/adapters for your adapter to implement the detection and proposal of an instance to the user.
On questions, the other developers will support in the forum or via GitHub issues too.
If no detection is possible, simply close this issue and I won't bother you again. ;-)
Thanks,
your automatic adapter checker.
P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info
Just moved and havent used ioBroker for a long time. Now that I set everything back, the adapter is unable to find the HS110 Ver 3.0 (or used to be shown as HW-Version 2.0 on the adapter).
Its only able to discover Version 2.0 (1.0 in the adapter).
Any ideas?
Cheers!
Version: stable=1.0.10 (287 days old) => latest=1.1.1 (17 days old)
Installs: stable=1052 (68.05%), latest=290 (18.76%), total=1546
Click to edit
Node.js v10.21.0
NPM 6.14.4
jsc 3.1.5
HS100 v2.0.0
instance delete, readd devices or reboot did not help
Log gets spammed with warnings (10 s interval) when device is offline
020-06-11 09:39:00.709 | warn | (1490) getDevice Socket connection Timeout : 192.xxx.xxx.57
after restarting the adapter for intervall change following error occurs for the unplugged device
| hs100.0 | 2020-06-11 09:44:48.069 | warn | (9639) getDevice Socket connection Timeout : 192xxx.57 |
|---|---|---|---|
| hs100.0 | 2020-06-11 09:44:44.956 | error | at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1107:14) |
| hs100.0 | 2020-06-11 09:44:44.956 | error | (9639) [create_state] : connect EHOSTUNREACH 192.xxx.57:9999, stack: Error: connect EHOSTUNREACH 192.xxx.57:9999 |
Dear Adapter develop,
Node.js 14 is now available for a year and Node.js 16 was release just some days ago and will become LTS by October 2021. We plan to update the ioBroker Node.js recommendation (currently 12.x) to 14.x later this year.
Please check your adapter with Node.js 14 especially, and ideally also directly with Node.js 16
Please add both versions to the adapter testing which is executed on commits.
If your adapter requires a certain minimum version of Node.js please set the 'engine' setting in package.json accordingly! Please also do this if the adapter is not able to work in certain Node.js versions, so that ioBroker can prevent users from installing te adapter if not compatible!
On questions please talk to us at ioBroker/ioBroker.js-controller#1138
Please close the issue after you checked it.
Thank you very much for your support!
Hallo Zusammen,
ich wollte endlich mal eine Szene erstellen, die zuerst meine Gartenpumpe einschaltet und anschließend nach 5 Sekunden mein Magnetventil ansteuert. Leider werden die Daten der HS110 in dem Szenen Adapter nicht angezeigt. Im Objekte Tree allerdings ja. Mache ich etwas falsch oder ist dies ein BUG?
Danke im Voraus
LG
Maurice
Wenn ich den Adapter auf die Version 1.0.8 update sind die Steckdosen nicht mehr ansprechbar.
Werden die Objekte und Adapter gelöscht und neu installiert werden auch keine Objekte mehr angelegt.
Die Version 1.0.6 funktioniert.
Diese Fehlermeldung konnt ich dazu finden:
2018-12-15 08:06:33.728 - �[32minfo�[39m: hs100.0 starting. Version 1.0.8 in C:/ioBroker/node_modules/iobroker.hs100, node: v6.15.1 2018-12-15 08:06:33.743 - �[31merror�[39m: hs100.0 uncaught exception: Cannot read property 'length' of undefined 2018-12-15 08:06:33.744 - �[31merror�[39m: hs100.0 TypeError: Cannot read property 'length' of undefined at main (C:\ioBroker\node_modules\iobroker.hs100\main.js:619:32) at Object.ready (C:\ioBroker\node_modules\iobroker.hs100\main.js:30:9) at initAdapter (C:\ioBroker\node_modules\iobroker.js-controller\lib\adapter.js:5289:62) at createInstancesObjects (C:\ioBroker\node_modules\iobroker.js-controller\lib\adapter.js:830:13) at Socket.that.getForeignObject (C:\ioBroker\node_modules\iobroker.js-controller\lib\adapter.js:869:25) at Socket.onack (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\lib\socket.js:312:9) at Socket.onpacket (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\lib\socket.js:236:12) at Manager.<anonymous> (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\component-bind\index.js:21:15) at Manager.Emitter.emit (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\node_modules\component-emitter\index.js:133:20) at Manager.ondecoded (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\lib\manager.js:332:8) 2018-12-15 08:06:34.252 - �[32minfo�[39m: hs100.0 terminating 2018-12-15 08:06:34.270 - �[31merror�[39m: Caught by controller[0]: TypeError: Cannot read property 'length' of undefined 2018-12-15 08:06:34.270 - �[31merror�[39m: Caught by controller[0]: at main (C:\ioBroker\node_modules\iobroker.hs100\main.js:619:32) 2018-12-15 08:06:34.271 - �[31merror�[39m: Caught by controller[0]: at Object.ready (C:\ioBroker\node_modules\iobroker.hs100\main.js:30:9) 2018-12-15 08:06:34.271 - �[31merror�[39m: Caught by controller[0]: at initAdapter (C:\ioBroker\node_modules\iobroker.js-controller\lib\adapter.js:5289:62) 2018-12-15 08:06:34.271 - �[31merror�[39m: Caught by controller[0]: at createInstancesObjects (C:\ioBroker\node_modules\iobroker.js-controller\lib\adapter.js:830:13) 2018-12-15 08:06:34.271 - �[31merror�[39m: Caught by controller[0]: at Socket.that.getForeignObject (C:\ioBroker\node_modules\iobroker.js-controller\lib\adapter.js:869:25) 2018-12-15 08:06:34.271 - �[31merror�[39m: Caught by controller[0]: at Socket.onack (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\lib\socket.js:312:9) 2018-12-15 08:06:34.271 - �[31merror�[39m: Caught by controller[0]: at Socket.onpacket (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\lib\socket.js:236:12) 2018-12-15 08:06:34.271 - �[31merror�[39m: Caught by controller[0]: at Manager.<anonymous> (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\component-bind\index.js:21:15) 2018-12-15 08:06:34.271 - �[31merror�[39m: Caught by controller[0]: at Manager.Emitter.emit (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\node_modules\component-emitter\index.js:133:20) 2018-12-15 08:06:34.271 - �[31merror�[39m: Caught by controller[0]: at Manager.ondecoded (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\lib\manager.js:332:8) 2018-12-15 08:06:34.271 - �[31merror�[39m: host.HP-ED800 instance system.adapter.hs100.0 terminated with code 0 (OK) 2018-12-15 08:06:34.271 - �[32minfo�[39m: host.HP-ED800 Restart adapter system.adapter.hs100.0 because enabled
Kannst du was damit anfangen oder brauchst du mehr Infos?
Version in io-package.json ( 0.0.15 ) doesn't match the current version ( 0.0.16 )
I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:
https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/arteck/ioBroker.hs100
Thanks,
your automatic adapter checker.
P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info
Fehlermeldung nach Update auf js-controller 3.2.4
hs100.0 | 2021-01-10 10:26:42.767 | warn | (520440) State "hs100.0.info.connection" has no existing object, this might lead to an error in future versions
Describe the bug
Seit dem Update auf V2.0.0 schalten die Steckdosen nicht mehr und zusätzlich bei den Hs110 werden die Daten nicht mehr aktualisiert.
To Reproduce
Beim restart der Instanz bleibt er auf gelb stehen und wechselt nicht mehr nach grün.
Expected behavior
Sollte wieder normal laufen, daten empfangen und schaltbar sein.
Screenshots & Logfiles
Restart Verhalten der Instanz...
Versions:
Adapter version: 2.0.0
JS-Controller version: 3.1.4
Node version: 12.18.0
NPM: 6.14.4
Operating system: Raspbian 9 (stretch)
Additional context
Muss wieder zurück auf V1.1.6, dann funktioniert wieder alles.
Version: stable=1.0.10 (308 days old) => latest=1.1.1 (38 days old)
Installs: stable=1057 (65.69%), latest=369 (22.93%), total=1609
Click to edit
Ich betreibe auf ioBroker am HS100 Adapter mehrere HS110 Plugs. Funktioniert soweit alles fein, außer in der folgenden Situation: Wenn die Änderung des Switch-Zustandes nur durch den internen Kalender des HS110 veranlasst wird, macht der Adapter kein update des entsprechenden Objekts im ioBroker. Ich kriege in ioBroker die Änderung also nicht mit. Läßt sich das ändern?
For Admin3 some changes are needed: see http://forum.iobroker.net/viewtopic.php?f=24&t=10268
Can not find any device after update to 0.1.3. Log is spamming every second and adapter is not working any more.
The used "tplink-smarthome-api" API already allows to switch the status LED on or off (e.g. HS110):
device.setLedState(state);
Could you implement a state in ioBroker for that purpose?
Thank You!
Der Adapter steuert ja die HS100/HS110.
Ist es eventuell möglich ihn auch für den TP-Link Tapo P100 zu erweitern? Dieser ist um einiges günstiger und kleiner.
Hi,
I was happy to find my lightbulb with this adapter. And so far it is working fine.
The light can be switched on and off. But as it is designed for a switch there is no way to set the brightness.
Can you add this?
The lightbulbs I use are LB120.
Upgrade auf 2.0.0 (auch 2.0.1): Power Anzeige im Statepoints des HS110 inaktiv
Hallo,
nach dem Upgrade auf 2.0.0 (auch 2.0.1) ist die Power Anzeige im Statepoints des HS110 inaktiv (eingefroren 0,00).
Muss bei einem Upgrade was besonderes beachtet werden, z.B. die Instance komplett gelöscht werden o.ä.?
Nach einem Downgrade auf 1.1.6 funktioniert die wieder, friert gelegentlich wieder ein (wie vorher auch).
MfG
Marian
I installed the Update from 1.0.10 to 1.1.00. Normaly vers. 1.0.10 should support the Compact Modus:
Changelog:
1.0.10 (2019-02-09)
(arteck) support for compact-mode added
But i got this Information as i tried to turn on the CM:
pi@ioBroker:~ $ iobroker compact hs100.0 status
This adapter does not support compact mode. The below settings will have no effect!
Compact mode enabled for instance: true
Compact group: 1
So is the CM now supported or not?
Hello,
the objects have the wrong types, so nothing can be calculated for energy.
What is the reason, that numbers have a string as type?
this.extendObjectAsync(`${ip_state}.power`, {
type: 'state',
common: {
name: hs_name || ip,
type: '**string**',
read: true,
write: false,
def: 0,
role: 'value',
desc: 'power value'
},
native: {},
});
The other objects have the same issue, so the Adapter e.g. SourceAnalytix can't calculated.
Best regards
Version: stable=2.0.1 (223 days old) => latest=2.0.3 (20 days old)
Installs: stable=1551 (67.52%), latest=361 (15.72%), total=2297
Click to edit
Heute einen neuen hs110 bekommen.
Der unterscheidet sich deutlich von den anderen.
Hardwareversion 2.0
Softwareversion 1.5.2 Build 180130 Rel.085820
Wird vom Adapter erkannt, aber zählt nicht.
Edit ON
Unten bei Realtime werden wohl die Werte anders ausgelesen als bei den älteren Steckern.
Edit OFF
Grüße Pocky :-)
Hallo,
nach einen Update des js-controllers auf V 3.3.1 kommen folgende Warnmeldungen:
`
| hs100.0 | 2021-04-30 06:49:45.021 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
|---|---|---|---|
| hs100.0 | 2021-04-30 06:49:44.622 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:49:14.830 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:49:14.438 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:48:44.614 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:48:44.215 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:48:14.426 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:48:14.040 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:47:44.210 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:47:43.811 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:47:14.021 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:47:13.627 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:46:43.828 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:46:43.435 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:46:13.617 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:46:13.189 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:45:43.400 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:45:43.008 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:45:13.186 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:45:12.802 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:44:42.994 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:44:42.595 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:44:12.792 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:44:12.394 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:43:42.592 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:43:42.205 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:43:12.403 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:43:12.016 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:42:42.215 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:42:41.817 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:42:11.999 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:42:11.597 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:41:41.809 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:41:41.423 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:41:11.584 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:41:11.197 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:40:41.371 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:40:40.966 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:40:11.189 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:40:10.786 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:39:40.971 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:39:40.570 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:39:10.782 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:39:10.390 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:38:40.582 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:38:40.191 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:38:10.378 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:38:09.977 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:37:40.185 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:37:39.794 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:37:09.974 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:37:09.583 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:36:39.763 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:36:39.355 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:36:09.571 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:36:09.179 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:35:39.367 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:35:38.974 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:35:09.178 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:35:08.776 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:34:38.977 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:34:38.573 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:34:08.787 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:34:08.398 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:33:38.589 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:33:38.189 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:33:08.372 | warn | (9752) State value to set for "hs100.0.192_168_178_23.ledState" has wrong type "boolean" but has to be "string" |
| hs100.0 | 2021-04-30 06:33:07.978 | warn | (9752) State value to set for "hs100.0.192_168_178_28.ledState" has wrong type "boolean" but has to be "string" |
`
Aktuell kann ich die Werte einer lb110 zwar auslesen, die Lampe aber nicht steuern (Werte werden nicht bestätigt).
Seit kurzem hängt sich der Adapter bei mir nach einer Weile immer wieder auf, sprich die werte von meinen HS110 werden nicht mehr aktualisiert. Es könnte evtl mit der aktualisierung auf version 2.0.0 zusammenhängen. Hat sonst noch jemand das gleiche Problem? Ich habe jetzt einen automatischen Adapterneustart alle 12 Std eingestellt und schaue mal ob das mein Problem löst. Das Issue hier erstelle ich in erster linie um zu erfahren ob das Problem noch bei anderen Leuten mit Version 2.0.0 auftritt.
Wenn es etwas gibt wie ich den Fehler genauer analysieren kann bitte Tipps geben. Danke!
Hello!
So I had a HS110 unit for more than a month and it worked perfectly, now I bought a new one and the new unit has a different hardware version (2.0) and runs with firmware version 1.5.2.
After adding the plug to the adapter the objects are created but the most important information is not relayed and stays as "0" such as (current, power, totalMonthNow, totalNow)
The rest of the information such as hw_ver, last_update, mac, model, state and sw_ver is shown normally.
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.