Coder Social home page Coder Social logo

iobroker.wifilight's Introduction

Logo

ioBroker.wifilight

Number of Installations Number of Installations NPM version

Test and Release Translation status Downloads

This adapter uses Sentry libraries to automatically report exceptions and code errors to the developers. For more details and for information how to disable the error reporting see Sentry-Plugin Documentation! Sentry reporting is used starting with js-controller 3.0.

Description

ioBroker Adapter for WiFi Light

Info

Supports LW12, LD382 and LD382A. Support for Mi-Light/LimitlessLED RGBW added.

Initial Creation

This adapter was initialy created by @soef at https://github.com/soef/ioBroker.wifilight but not maintained any more, so we moved it to iobroker-community so that bugs could be fixed. thanks @soef for his work.

How to use the command state:

  • Possible identifiers are: red, r, green, g, blue, b, bri, sat, transition, on, off
  • The string can be a JSON with or without parentheses.
  • You can also assign a value by =
  • Range of colors: 0..255
  • Range of bri: 0..100

Some Examples:

r = 100; g = 250, b = 100
r: 0, g: 0, b = 255
red: 200, green: 0, blue: 0
{r:100, b: 200, transition: 20}
off
on
{on:0}

To change the color you do not have to use all three vallues. For example, red = 0, blue and green will stay unchanged.

r, g, b, w States:

  • Values 0..255
  • #rrggbb[ww]

Installation

Use the Adapter panel in iobroker to add an instance.

If not exists execute the following command in the iobroker root directory (e.g. in /opt/iobroker).

npm install iobroker.wifilight 

Error fixing

In case of not working try to install the soef npm package

cd /opt/iobroker/node_modules/iobroker.wifilight 
sudo npm install soef 

Changelog

1.1.4 (2022-06-17)

  • (Apollon77) Prevent crash case reported by sentry

1.1.3 (2022-04-27)

  • (Apollon77) Prevent crash case reported by sentry

1.1.2 (2022-04-19)

  • (Apollon77) Prevent crashes when states are controlled with null as value

1.1.1 (2022-04-17)

  • (Apollon77) Prevent error logs with js-controller 3+
  • (Apollon77) Added sentry for error reporting

1.1.0 (2020-04-09)

  • (foxriver76) compatibility for js-c 3

1.0.0 (2019-10-18)

  • (ldittmar) first version for the community

License

The MIT License (MIT)

Copyright (c) 2020-2022 ioBroker Community Developers, 2019-2020 soef [email protected],

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

iobroker.wifilight's People

Contributors

apollon77 avatar dependabot-preview[bot] avatar dependabot[bot] avatar dutchmannl avatar fiiti avatar foxriver76 avatar germanbluefox avatar jogibear9988 avatar ldittmar81 avatar matze1708 avatar mcm1957 avatar soef avatar

Stargazers

 avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

iobroker.wifilight's Issues

Wifi Light Adapter im Docker Container

Hi, ich habe 2 Instanzen.
eine physikalische und ein Docker Container.
Leider bekomme ich den Adapter im Container zwar ans laufen, aber er findets keine Devices.
Ich vermute mal ich muss die entsprechenden Ports noch freischalten.
Leider kann ich nirgends finden auf welchem Port der Broadcast (Geräte finden) durchgeführt wird.
Es wäre nett, wenn du mir die verwendeten Ports nennen könntest.
Danke

Please check ioBroker.wifilight-community with js-controller 2.0

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.

Error using module

From @schliack on November 7, 2017 13:4

Hello,
after installing the module i got this error in logfile :

ost.raspberrypi 2017-11-07 13:01:45.231 info Restart adapter system.adapter.wifilight.0 because enabled
host.raspberrypi 2017-11-07 13:01:45.231 error instance system.adapter.wifilight.0 terminated with code 1 ()
Caught 2017-11-07 13:01:45.230 error by controller[0]: at startup (bootstrap_node.js:149:9)
Caught 2017-11-07 13:01:45.230 error by controller[0]: at run (bootstrap_node.js:383:7)
Caught 2017-11-07 13:01:45.230 error by controller[0]: at Module.runMain (module.js:604:10)
Caught 2017-11-07 13:01:45.229 error by controller[0]: at Function.Module._load (module.js:438:3)
Caught 2017-11-07 13:01:45.229 error by controller[0]: at tryModuleLoad (module.js:446:12)
Caught 2017-11-07 13:01:45.229 error by controller[0]: at Module.load (module.js:487:32)
Caught 2017-11-07 13:01:45.228 error by controller[0]: at Object.Module._extensions..js (module.js:579:10)
Caught 2017-11-07 13:01:45.228 error by controller[0]: at Module._compile (module.js:570:32)
Caught 2017-11-07 13:01:45.228 error by controller[0]: at Object. (/opt/iobroker/node_modules/iobroker.wifilight/wifilight.js:20:20)
Caught 2017-11-07 13:01:45.227 error by controller[0]: at Object.exports.Adapter (/opt/iobroker/node_modules/soef/soef.js:1141:23)
Caught 2017-11-07 13:01:45.227 error by controller[0]: TypeError: fns.adapter is not a function
Caught 2017-11-07 13:01:45.227 error by controller[0]: ^
Caught 2017-11-07 13:01:45.226 error by controller[0]: fns.adapter = fns.adapter(options);
Caught 2017-11-07 13:01:45.225 error by controller[0]: /opt/iobroker/node_modules/soef/soef.js:1141
host.raspberrypi 2017-11-07 13:01:44.283 info instance system.adapter.wifilight.0 started with pid 4843

The networkdevices will not be found (LD382)

Cheers
Andreas

Copied from original issue: soef/ioBroker.wifilight#12

state wrong - must be number is boolean..

with js-controller 5.x the error appears after every re-start of the adapter ( and I let it every hour restarting, because the adapter fall in deepsleep after a while and the states of the devices are not refreshed any more..

`

wifilight.0 | 2023-11-04 14:13:55.401 | info | State value to set for "wifilight.0.10_1_5_203.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.361 | info | State value to set for "wifilight.0.10_1_5_214.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.341 | info | State value to set for "wifilight.0.10_1_5_209.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.340 | info | State value to set for "wifilight.0.10_1_5_206.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.340 | info | State value to set for "wifilight.0.10_1_5_200.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.334 | info | State value to set for "wifilight.0.10_1_5_215.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.333 | info | State value to set for "wifilight.0.10_1_5_220.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.333 | info | State value to set for "wifilight.0.10_1_5_205.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.333 | info | State value to set for "wifilight.0.10_1_5_217.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.333 | info | State value to set for "wifilight.0.10_1_5_201.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.332 | info | State value to set for "wifilight.0.10_1_5_212.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.331 | info | State value to set for "wifilight.0.10_1_5_208.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.328 | info | State value to set for "wifilight.0.10_1_5_207.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.328 | info | State value to set for "wifilight.0.10_1_5_213.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.327 | info | State value to set for "wifilight.0.10_1_5_216.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.327 | info | State value to set for "wifilight.0.10_1_5_210.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.327 | info | State value to set for "wifilight.0.10_1_5_218.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.327 | info | State value to set for "wifilight.0.10_1_5_221.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.326 | info | State value to set for "wifilight.0.10_1_5_219.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.324 | info | State value to set for "wifilight.0.10_1_5_202.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.319 | info | State value to set for "wifilight.0.10_1_5_211.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.262 | info | State value to set for "wifilight.0.10_1_5_204.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.231 | info | State value to set for "wifilight.0.10_1_5_221.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.230 | info | State value to set for "wifilight.0.10_1_5_220.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.230 | info | State value to set for "wifilight.0.10_1_5_219.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.230 | info | State value to set for "wifilight.0.10_1_5_218.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.229 | info | State value to set for "wifilight.0.10_1_5_217.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.229 | info | State value to set for "wifilight.0.10_1_5_216.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.228 | info | State value to set for "wifilight.0.10_1_5_215.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.228 | info | State value to set for "wifilight.0.10_1_5_214.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.227 | info | State value to set for "wifilight.0.10_1_5_213.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.227 | info | State value to set for "wifilight.0.10_1_5_212.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.225 | info | State value to set for "wifilight.0.10_1_5_211.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.224 | info | State value to set for "wifilight.0.10_1_5_210.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.223 | info | State value to set for "wifilight.0.10_1_5_209.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.221 | info | State value to set for "wifilight.0.10_1_5_208.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.221 | info | State value to set for "wifilight.0.10_1_5_207.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.220 | info | State value to set for "wifilight.0.10_1_5_206.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.218 | info | State value to set for "wifilight.0.10_1_5_205.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.218 | info | State value to set for "wifilight.0.10_1_5_204.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.216 | info | State value to set for "wifilight.0.10_1_5_202.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.215 | info | State value to set for "wifilight.0.10_1_5_201.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:55.209 | info | State value to set for "wifilight.0.10_1_5_200.reachable" has to be type "number" but received type "boolean"
wifilight.0 | 2023-11-04 14:13:53.888 | info | starting. Version 1.1.4 in /opt/iobroker/node_modules/iobroker.wifilight, node: v18.18.2, js-controller: 5.0.16
host.iobroker | 2023-11-04 14:13:49.058 | info | instance system.adapter.wifilight.0 started with pid 15938
host.iobroker | 2023-11-04 14:13:46.502 | info | instance system.adapter.wifilight.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
wifilight.0 | 2023-11-04 14:13:46.314 | info | terminating
wifilight.0 | 2023-11-04 14:13:45.812 | info | Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
wifilight.0 | 2023-11-04 14:13:45.810 | info | terminating
wifilight.0 | 2023-11-04 14:13:45.807 | info | Got terminate signal TERMINATE_YOURSELF
host.iobroker | 2023-11-04 14:13:45.806 | info | stopInstance system.adapter.wifilight.0 send kill signal
host.iobroker | 2023-11-04 14:13:45.791 | info | stopInstance system.adapter.wifilight.0 (force=false, process=true)

`

Pollintervall - for what is this, because a polling is only on restart of the adapter happened...
image

Device Names?

From @psi-4ward on November 28, 2017 20:51

If I change the device name (Bezeichnung) in the adapter config I receive the errors:

wifilight.0 | | error | Known names are: HF-LPB100-ZJ200, HF-LPB100-ZJ002, HF-A11-ZJ002, Mi-Light, AK001-ZJ100
wifilight.0 | | error | config.device Kueche links is not a known device. Skipping this device!

So it's not possible to give the devices speaking names?

Disclaimer: I'm very very new to ioBroker

Copied from original issue: soef/ioBroker.wifilight#15

No reaction beside on/off

Describe the bug
It doesn't matter if LD686 or LD382A. I can only control on/off. All other attributes don't show any reaction.
Even on/off is only working 90% of the time. I have to use the magichome app on smartphone in that case. There the connection is stable.
As far as I know also other users have this problem.

To Reproduce
I can't give reproduction description besides changing values in this screenshot doesn't show any reaction.

image

Expected behavior
A change in every attribute that I change.

Versions:

  • Adapter version: 1.1.4

Compatibility check and testing for Node.js 14 and 16

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!

Adapter does not start

The actual Adapter does not Start. iObroker and everything else is the newest Version. Tried reinstall but didn't work.

ost.raspberrypi 2019-11-21 05:40:22.247 info Restart adapter system.adapter.wifilight-community.0 because enabled
host.raspberrypi 2019-11-21 05:40:22.246 error instance system.adapter.wifilight-community.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.raspberrypi 2019-11-21 05:40:22.246 error Caught by controller[0]: at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)
host.raspberrypi 2019-11-21 05:40:22.246 error Caught by controller[0]: at startup (internal/bootstrap/node.js:283:19)
host.raspberrypi 2019-11-21 05:40:22.245 error Caught by controller[0]: at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
host.raspberrypi 2019-11-21 05:40:22.245 error Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:585:3)
host.raspberrypi 2019-11-21 05:40:22.244 error Caught by controller[0]: at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
host.raspberrypi 2019-11-21 05:40:22.244 error Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:653:32)
host.raspberrypi 2019-11-21 05:40:22.243 error Caught by controller[0]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
host.raspberrypi 2019-11-21 05:40:22.243 error Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:778:30)
host.raspberrypi 2019-11-21 05:40:22.243 error Caught by controller[0]: at Object. (/opt/iobroker/node_modules/iobroker.wifilight-community/main.js:20:20)
host.raspberrypi 2019-11-21 05:40:22.242 error Caught by controller[0]: at Object.exports.Adapter (/opt/iobroker/node_modules/soef/soef.js:1383:23)
host.raspberrypi 2019-11-21 05:40:22.242 error Caught by controller[0]: TypeError: fns.adapter is not a function
host.raspberrypi 2019-11-21 05:40:22.241 error Caught by controller[0]: ^
host.raspberrypi 2019-11-21 05:40:22.240 error Caught by controller[0]: fns.adapter = fns.adapter(options);
host.raspberrypi 2019-11-21 05:40:22.240 error Caught by controller[0]: /opt/iobroker/node_modules/soef/soef.js:1383
host.raspberrypi 2019-11-21 05:40:21.435 info instance system.adapter.wifilight-community.0 started with pid 20807

Compatibility check to js-controller 4.0

Dear Adapter developer,

with js-controller 4.0 object definitions are now also checked that min/max in only provided for number/mixed objects and that the type of the default value matches to the object type.

If something is not correct this is logged as 'warning' or 'info' log.

Please also make sure to update to the lastest @iobroker/testing dependency 2.5.4 or to accept the PR from Apollon77 for legacy testing!

Please spent some 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 or info log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1749

Please close the issue after you checked it.

Thank you very much for your support to get the best experience for the growing numbers of ioBroker users!

Typ AK001-ZJ210 wird nicht unterstützt ?

From @Ridesa on November 7, 2018 16:5

Hab mir das Set hier gekauft https://www.amazon.de/gp/product/B07BLZCPPG/ref=oh_aui_detailpage_o04_s00?ie=UTF8&psc=1

bekomme da folgende Fehlermeldung

wifilight.0 2018-11-07 17:01:37.812 error wrong device type. not yet supported!
wifilight.0 2018-11-07 17:01:37.810 error config.device.type "" (AK001-ZJ210) is not a known device type. Skipping this device! Known types are: LW12, LD382A, LD382, UFO, MiLight, MiLightRGB, MiLightW

Copied from original issue: soef/ioBroker.wifilight#24

Adapter startet nicht sobald ein Typ eingetragen ist

From @nimit1001 on July 15, 2018 0:37

Ich hoffe ich bekomme hier noch einige Tipps: Mein Problem ist das der Adapter ohne ein Gerät problemlos läuft (grüner Status). Sobald ich ein Gerät suche findet er den "AK001-ZJ200" sowie eine IP, den Typ (LD382A) den Port 5577 sowie Pollintervall (30)

Im Anschluss ist der Adapter rot. Log kommt gleich noch. Nach einigem herumprobieren (Mehrfaches neuinstallieren des Adapter, Update der Komponente und manuelle Überprüfung der Datei (Soef-Version etc.)) habe ich dann herausgefunden das der Adapter läuft sobald ich den Typ des WIFI-Controllers entferne. Allerdings bekomme ich dann natürlich die Fehlermeldung dass der Typ unbekannt ist. (Logisch wenn kein Typ eingetragen ist)

Hier noch der Log wenn ein Controller eingetragen ist. Inklusive Typ:

host.raspberrypi 2018-07-15 02:34:23.534 info Restart adapter system.adapter.wifilight.0 because enabled
host.raspberrypi 2018-07-15 02:34:23.534 error instance system.adapter.wifilight.0 terminated with code 0 (OK)
Caught 2018-07-15 02:34:23.534 error by controller[0]: at Socket.onack (/root/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:312:9)
Caught 2018-07-15 02:34:23.534 error by controller[0]: at Socket. (/root/node_modules/iobroker.js-controller/lib/adapter.js:2281:25)
Caught 2018-07-15 02:34:23.534 error by controller[0]: at /root/node_modules/iobroker.wifilight/node_modules/soef/soef.js:848:21
Caught 2018-07-15 02:34:23.534 error by controller[0]: at safeCallback (/root/node_modules/iobroker.wifilight/node_modules/soef/soef.js:188:13)
Caught 2018-07-15 02:34:23.534 error by controller[0]: at /root/node_modules/iobroker.wifilight/node_modules/soef/soef.js:1297:9
Caught 2018-07-15 02:34:23.533 error by controller[0]: at main (/root/node_modules/iobroker.wifilight/wifilight.js:917:54)
Caught 2018-07-15 02:34:23.533 error by controller[0]: at WifiLight.run (/root/node_modules/iobroker.wifilight/wifilight.js:170:10)
Caught 2018-07-15 02:34:23.533 error by controller[0]: at WifiLight.createDevice (/root/node_modules/iobroker.wifilight/wifilight.js:197:19)
Caught 2018-07-15 02:34:23.533 error by controller[0]: at CDevice.getFullId (/root/node_modules/iobroker.wifilight/node_modules/soef/soef.js:1113:20)
Caught 2018-07-15 02:34:23.533 error by controller[0]: at dcs (/root/node_modules/iobroker.wifilight/node_modules/soef/soef.js:304:33)
Caught 2018-07-15 02:34:23.532 error by controller[0]: TypeError: Cannot read property '0' of undefined
wifilight.0 2018-07-15 02:34:23.503 error at Socket.onack (/root/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:312:9)
wifilight.0 2018-07-15 02:34:23.503 error at Socket. (/root/node_modules/iobroker.js-controller/lib/adapter.js:2281:25)
wifilight.0 2018-07-15 02:34:23.503 error at /root/node_modules/iobroker.wifilight/node_modules/soef/soef.js:848:21
wifilight.0 2018-07-15 02:34:23.503 error at safeCallback (/root/node_modules/iobroker.wifilight/node_modules/soef/soef.js:188:13)
wifilight.0 2018-07-15 02:34:23.503 error at /root/node_modules/iobroker.wifilight/node_modules/soef/soef.js:1297:9
wifilight.0 2018-07-15 02:34:23.503 error at main (/root/node_modules/iobroker.wifilight/wifilight.js:917:54)
wifilight.0 2018-07-15 02:34:23.503 error at WifiLight.run (/root/node_modules/iobroker.wifilight/wifilight.js:170:10)
wifilight.0 2018-07-15 02:34:23.503 error at WifiLight.createDevice (/root/node_modules/iobroker.wifilight/wifilight.js:197:19)
wifilight.0 2018-07-15 02:34:23.503 error at CDevice.getFullId (/root/node_modules/iobroker.wifilight/node_modules/soef/soef.js:1113:20)
wifilight.0 2018-07-15 02:34:23.503 error at dcs (/root/node_modules/iobroker.wifilight/node_modules/soef/soef.js:304:33)
wifilight.0 2018-07-15 02:34:23.503 error TypeError: Cannot read property '0' of undefined
wifilight.0 2018-07-15 02:34:23.502 error uncaught exception: Cannot read property '0' of undefined
wifilight.0 2018-07-15 02:34:23.427 info starting. Version 0.2.1 in /root/node_modules/iobroker.wifilight, node: v8.11.3

Ich hoffe das jemand eine Idee hat woran das liegen kann und bedanke mich im Voraus schonmal.

Copied from original issue: soef/ioBroker.wifilight#21

Transition from "white" to rgb, not from current color

From @psi-4ward on June 2, 2018 1:4

I've some trouble to understand the color transitions:

const ctrl = "wifilight.0.192_168_178_37";
function rand(min, max) {
    return Math.floor(Math.random() * (max - min + 1)) + min;
}
function setRand() {
    const cmd =  `r: ${rand(0,100)}, g: ${rand(0,100)}, b: ${rand(0,100)}, transition: 3`;
    setState(ctrl + '.command', cmd)
}
setInterval(setRand, 3*1000);

on every trigger the color switches to white and transitions to the rgb value. I would expect to have the transition from the current color.

Copied from original issue: soef/ioBroker.wifilight#20

Think about to fix the issues found by adapter checker

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/iobroker-community-adapters/ioBroker.wifilight

I have also found warnings that may be fixed if possible.

  • [W113] Adapter should support compact mode

Thanks,
your automatic adapter checker.

after Update js-controller 3.3.15 info messages

2021-09-01 00:30:05.893 - �[32minfo�[39m: wifilight.0 (15672) State value to set for "wifilight.0.192_168_178_32.reachable" has to be type "number" but received type "boolean" 2021-09-01 00:30:05.895 - �[32minfo�[39m: wifilight.0 (15672) State value to set for "wifilight.0.192_168_178_30.reachable" has to be type "number" but received type "boolean" 2021-09-01 00:30:05.896 - �[32minfo�[39m: wifilight.0 (15672) State value to set for "wifilight.0.192_168_178_62.reachable" has to be type "number" but received type "boolean"

Versions:

  • Adapter version: 1.1.0
  • JS-Controller version: 3.3.15
  • Node version: 12.22.6
  • Operating system: linux

Data Type of State is not supported

Data Type Number ist not supported at state
wifilight.0.x_x_x_x.reachable

Device Type is LD686

complite message is:
State value to set for "wifilight.0.192_168_178_211.reachable" has to be type "number" but received type "boolean"

Think about to fix the issues found by adapter checker

From @ioBrokerChecker on February 3, 2019 12:26

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/soef/ioBroker.wifilight

ERR:["E019","E114","E115","E201"]:ERR

Thanks,
your automatic adapter checker.

Copied from original issue: soef/ioBroker.wifilight#28

Adapter don t start..

actual Version on Git don t start:
`

host.Masterbroker 2019-08-06 14:09:43.195 error instance system.adapter.wifilight-community.0 terminated with code 0 (OK)
Caught 2019-08-06 14:09:43.195 error by controller[0]: at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9)
Caught 2019-08-06 14:09:43.195 error by controller[0]: at Socket.that.objects.getObjectView (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:2732:25)
Caught 2019-08-06 14:09:43.195 error by controller[0]: at /opt/iobroker/node_modules/iobroker.wifilight-community/node_modules/soef/soef.js:848:21
Caught 2019-08-06 14:09:43.195 error by controller[0]: at safeCallback (/opt/iobroker/node_modules/iobroker.wifilight-community/node_modules/soef/soef.js:188:13)
Caught 2019-08-06 14:09:43.195 error by controller[0]: at /opt/iobroker/node_modules/iobroker.wifilight-community/node_modules/soef/soef.js:1297:9
Caught 2019-08-06 14:09:43.195 error by controller[0]: at main (/opt/iobroker/node_modules/iobroker.wifilight-community/main.js:917:54)
Caught 2019-08-06 14:09:43.195 error by controller[0]: at WifiLight.run (/opt/iobroker/node_modules/iobroker.wifilight-community/main.js:170:10)
Caught 2019-08-06 14:09:43.195 error by controller[0]: at WifiLight.createDevice (/opt/iobroker/node_modules/iobroker.wifilight-community/main.js:197:19)
Caught 2019-08-06 14:09:43.195 error by controller[0]: at CDevice.getFullId (/opt/iobroker/node_modules/iobroker.wifilight-community/node_modules/soef/soef.js:1113:20)
Caught 2019-08-06 14:09:43.194 error by controller[0]: at dcs (/opt/iobroker/node_modules/iobroker.wifilight-community/node_modules/soef/soef.js:304:33)
Caught 2019-08-06 14:09:43.194 error by controller[0]: TypeError: Cannot read property '0' of undefined
wifilight-community.0 2019-08-06 14:09:43.186 info terminating
wifilight-community.0 2019-08-06 14:09:43.182 error at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9)
wifilight-community.0 2019-08-06 14:09:43.182 error at Socket.that.objects.getObjectView (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:2732:25)
wifilight-community.0 2019-08-06 14:09:43.182 error at /opt/iobroker/node_modules/iobroker.wifilight-community/node_modules/soef/soef.js:848:21
wifilight-community.0 2019-08-06 14:09:43.182 error at safeCallback (/opt/iobroker/node_modules/iobroker.wifilight-community/node_modules/soef/soef.js:188:13)
wifilight-community.0 2019-08-06 14:09:43.182 error at /opt/iobroker/node_modules/iobroker.wifilight-community/node_modules/soef/soef.js:1297:9
wifilight-community.0 2019-08-06 14:09:43.182 error at main (/opt/iobroker/node_modules/iobroker.wifilight-community/main.js:917:54)
wifilight-community.0 2019-08-06 14:09:43.182 error at WifiLight.run (/opt/iobroker/node_modules/iobroker.wifilight-community/main.js:170:10)
wifilight-community.0 2019-08-06 14:09:43.182 error at WifiLight.createDevice (/opt/iobroker/node_modules/iobroker.wifilight-community/main.js:197:19)
wifilight-community.0 2019-08-06 14:09:43.182 error at CDevice.getFullId (/opt/iobroker/node_modules/iobroker.wifilight-community/node_modules/soef/soef.js:1113:20)
wifilight-community.0 2019-08-06 14:09:43.182 error at dcs (/opt/iobroker/node_modules/iobroker.wifilight-community/node_modules/soef/soef.js:304:33)
wifilight-community.0 2019-08-06 14:09:43.182 error TypeError: Cannot read property '0' of undefined
wifilight-community.0 2019-08-06 14:09:43.181 error uncaught exception: Cannot read property '0' of undefined
wifilight-community.0 2019-08-06 14:09:43.099 info starting. Version 0.2.1 in /opt/iobroker/node_modules/iobroker.wifilight-community, node: v8.16.0
host.Masterbroker 2019-08-06 14:09:42.764 info instance system.adapter.wifilight-community.0 started with pid 30098
host.Masterbroker 2019-08-06 14:09:42.752 info object change system.adapter.wifilight-community.0

`

Compatibility check to js-controller 3.3 and Admin5 React UI

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!

HTTP Request des Adapter

From @ihavenonick on August 26, 2018 10:17

Hallo,
hat eigentlich nichts direkt mit dem Adapter zu tun, da Du aber hier definitiv der Mann mit mehr Wissen bist, erhoffe ich mir doch Hilfe.
Ich möchte einfach ein Controller der mit dem Adapter über IOBroker läuft, auch schnell und einfach über HTTP Request mit dem Handy aus und ein schalten. Dazu fehlt mir allerdings der besagte HTTP Request. Eigentlich läuft das im Adapter wohl genau so ab, oder Du weißt zumindest mal wie der Befehl hier aufgebaut sein müsste. Kannst Du mir hier weiterhelfen?

Copied from original issue: soef/ioBroker.wifilight#22

Adapter startet nicht.

From @matze1708 on November 26, 2017 10:50

Hallo,

der Adapter startet nicht und bringt Fehler ins log.
Forum Thread:
http://forum.iobroker.net/viewtopic.php?f=20&t=9270&p=99007#p99007

Fehler:

`node node_modules/iobroker.wifilight/wifilight.js --logs --force
/opt/iobroker/node_modules/soef/soef.js:1141
fns.adapter = fns.adapter(options);
^

TypeError: fns.adapter is not a function
at Object.exports.Adapter (/opt/iobroker/node_modules/soef/soef.js:1141:23)
at Object. (/opt/iobroker/node_modules/iobroker.wifilight/wifilight.js:20:20)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.runMain (module.js:604:10)
at run (bootstrap_node.js:383:7)
at startup (bootstrap_node.js:149:9)`

LOG:

host.ioBroker-RasPi 2017-11-26 11:42:42.830 error instance system.adapter.wifilight.0 terminated with code 1 ()
Caught 2017-11-26 11:42:42.830 error by controller[0]: at startup (bootstrap_node.js:149:9)
Caught 2017-11-26 11:42:42.830 error by controller[0]: at run (bootstrap_node.js:383:7)
Caught 2017-11-26 11:42:42.829 error by controller[0]: at Module.runMain (module.js:604:10)
Caught 2017-11-26 11:42:42.829 error by controller[0]: at Function.Module._load (module.js:438:3)
Caught 2017-11-26 11:42:42.829 error by controller[0]: at tryModuleLoad (module.js:446:12)
Caught 2017-11-26 11:42:42.829 error by controller[0]: at Module.load (module.js:487:32)
Caught 2017-11-26 11:42:42.829 error by controller[0]: at Object.Module._extensions..js (module.js:579:10)
Caught 2017-11-26 11:42:42.828 error by controller[0]: at Module._compile (module.js:570:32)
Caught 2017-11-26 11:42:42.828 error by controller[0]: at Object. (/opt/iobroker/node_modules/iobroker.wifilight/wifilight.js:20:20)
Caught 2017-11-26 11:42:42.828 error by controller[0]: at Object.exports.Adapter (/opt/iobroker/node_modules/soef/soef.js:1141:23)
Caught 2017-11-26 11:42:42.828 error by controller[0]: TypeError: fns.adapter is not a function
Caught 2017-11-26 11:42:42.827 error by controller[0]: ^
Caught 2017-11-26 11:42:42.827 error by controller[0]: fns.adapter = fns.adapter(options);
Caught 2017-11-26 11:42:42.824 error by controller[0]: /opt/iobroker/node_modules/soef/soef.js:1141

Copied from original issue: soef/ioBroker.wifilight#14

Think about to fix the issues found by adapter checker

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/iobroker-community-adapters/ioBroker.wifilight-community

I have also found warnings that may be fixed if possible.

  • [W113] Adapter should support compact mode
  • [W400] Cannot find "wifilight-community" in latest repository

Thanks,
your automatic adapter checker.

State ON wird nicht aktualisiert bei externen Befehlen

From @hyperbit00 on February 10, 2019 20:50

Mindestens bei TYP AK001-ZJ100 wird der State ON nur mit neustart der Instanz aktualisiert.
Wird das LED Modul per ALEXA oder Fernbedienung oder CLOUD gesteuert, bleibt der STATE ON auf dem Wert den er zuvor hatte.

Daher wird das Modul per Fernbedienung aktivert, wechselt der State ON nicht auf TRUE.
Startet wir den Adapter jedoch neu, wird nun korrekt TRUE angezeigt.

Wo ist der Fehler?

Copied from original issue: soef/ioBroker.wifilight#29

wifilight 0.2.0 don"t work with Admin V3.6.2

host.iobroker 2019-05-06 09:28:52.060 error instance system.adapter.wifilight.0 terminated with code 1 ()
Caught 2019-05-06 09:28:52.060 error by controller[0]: at bootstrap_node.js:625:3
Caught 2019-05-06 09:28:52.060 error by controller[0]: at startup (bootstrap_node.js:204:16)
Caught 2019-05-06 09:28:52.060 error by controller[0]: at Function.Module.runMain (module.js:694:10)
Caught 2019-05-06 09:28:52.060 error by controller[0]: at Function.Module._load (module.js:498:3)
Caught 2019-05-06 09:28:52.059 error by controller[0]: at tryModuleLoad (module.js:506:12)
Caught 2019-05-06 09:28:52.059 error by controller[0]: at Module.load (module.js:566:32)
Caught 2019-05-06 09:28:52.059 error by controller[0]: at Object.Module._extensions..js (module.js:664:10)
Caught 2019-05-06 09:28:52.059 error by controller[0]: at Module._compile (module.js:653:30)
Caught 2019-05-06 09:28:52.059 error by controller[0]: at Object. (/opt/iobroker/node_modules/iobroker.wifilight/wifilight.js:20:20)
Caught 2019-05-06 09:28:52.059 error by controller[0]: at Object.exports.Adapter (/opt/iobroker/node_modules/soef/soef.js:1148:23)
Caught 2019-05-06 09:28:52.059 error by controller[0]: TypeError: fns.adapter is not a function
Caught 2019-05-06 09:28:52.059 error by controller[0]: ^
Caught 2019-05-06 09:28:52.059 error by controller[0]: fns.adapter = fns.adapter(options);
Caught 2019-05-06 09:28:52.059 error by controller[0]: /opt/iobroker/node_modules/soef/soef.js:1148
host.iobroker 2019-05-06 09:28:51.698 info object change system.adapter.wifilight.0
host.iobroker 2019-05-06 09:28:50.892 info Restart adapter system.adapter.wifilight.0 because enabled

controller do not switch

From @fmsmuc on February 14, 2017 13:23

have three controllers - all controllers are detected as HF-LPB100-ZJ200
it seams that my HF-LPB100-ZJ200 is LD868 (five channels)
and the UFO HF-LPB100-ZJ100 (LD??? )

one Contoller is UFO with 4 channel RGBW (in MagicHome shown as version 3)

two Controllers are 5 channel with RGBWW (and same charge - in MagicHome shown as version 1)
(https://www.amazon.de/gp/product/B01J5A7ABW/ref=oh_aui_detailpage_o09_s00?ie=UTF8&psc=1)

in ioBroker you can see the status change but one of the four Controller do not switch or only sometimes - the other one does. Sometimes the four channel Controller UFO works - sometimes not.
the same with the four channel controller - one is working, the other works only sometimes even if status change is shown in ioBroker.
port (5577) has to be correct because sometimes it is working.
devicename: HF-LPB100-ZJ200' - port: 5577
Found that there is a possibility to switch between 4 and 5 channel controllers see here:
https://github.com/steve228uk/homebridge-magichome/blob/master/flux_led.py

1.) why does UFO do not switch or only sometimes? (found solution - see below)
2.) why does one five channel controller switch and the other only sometimes?
3.) would it be possible do create a datepoint for cold white so that we have w (warm white) and cw (cold white) if it is a 5 channel RGB warmwhite coldwhite controller ?
4.) "ct" Paramater does not work (have one Controller with warm/coldwhite LED)
5.) Status of Pramameters show wrong values in ioBroker

I did a capture of the TCP traffic - Magic home sends "81 8A 8B 96" gets response and then the "on" or "off command "71 23 0F A3"

i modified the flux_led.py script and then the script was working too.
But, did not test brightness and colors - if you need captures please tell me.
I have the manufacture original docs of all command - if you need this, please tell me.
"81 8A 8B 96" is a request of device status. I think in newer firmware it is a must that the device status has to be requested, before it can be switched on /off.

Could you please alter the Wifilight Adapter that it can handle controllers with newer software and the new 5 channel controllers.

by the way - with the magichome app its working all the time, so the controller hardware is ok
thank you

Copied from original issue: soef/ioBroker.wifilight#4

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.