kpsuperplane / homebridge-wiz-lan

Control Wiz lights over LAN

homebridge-wiz-lan

Based off of kpsuperplane/homebridge-iotas

Currently supports

• Lightbulbs (RGB, Color Temp, and Single Color) (tested with Wiz 100W Color & Wiz 30W Filaments)
• Wiz Plugs/Outlets (ESP10_SOCKET_06, ESP25_SOCKET_01, ESP20_DHRGB_01)

Installation

Make sure your bulbs are already set up via the Wiz app and you have "Allow Local Communication" set to ON in your settings.

1. Install homebridge using: npm install -g homebridge
2. Install this plugin using: npm install -g homebridge-wiz-lan
3. Update your configuration file. See the sample below.

Configuration

Simple Configuration:

{
    "platform": "WizSmarthome",
    "name": "WizSmarthome",
}

Full configuration options:

{
    "platform": "WizSmarthome",
    "name": "Wiz",

    // [Optional] Port for bulbs to connect to your server
    // Default: 38900
    "port": 38900,

    // [Optional] Enable scenes support for your bulbs
    // Default: false
    "enableScenes": false,

    // [Optional] Lights turn on with the same settings they had when turned off (light configs in HomeKit are ignored).
    // Default: false
    "lastStatus": false,

    // [Optional] UDP Broadcast address for bulb discovery
    // Default: 255.255.255.255
    "broadcast": "255.255.255.255",

    // [Optional] Your server's IP address
    // Default: Autodiscovered
    "address": "192.168.0.1",

    // [Optional] Manual list of IP addresses of bulbs
    // Useful if UDP broadcast doesn't work for some reason
    // Default: None
    "devices": [
      { "host": "192.168.0.2" },
      { "host": "192.168.0.3" },
      { "host": "192.168.0.4" },
      // ...
    ],

    // [Optional] Refresh/ping every accessory to get their latest state on an interval. Specify in seconds, 0 = off
    // Default: 0
    "refreshInterval": 60,
  }

Some Notes

Color

The Wiz bulbs strongly distinguish between RGB color modes and Kelvin color modes, the latter being significantly brighter. Unfortunately, HomeKit is not very good at handling both at the same time, yielding weird errors if you try to add both characteristics.

Luckily, even if we only enable the color mode, we still get a nice temperature picker. Problem is, the color temperature is given in standard HSV. As such, this app will try to guess which one to best use given a color, and you will notice some significant brightness variance switching between a "temp" hue and a "color" hue.

In particular, since the Wiz bulbs only support up to 6500K, this means that only the top-ish half of the temperature picker is actually bright

Last Status (config setting)

If a "rhythm" is selected in the Wiz app and lastStatus is set to true, the lights will always turn on to the rhythm. When rhythms are disabled, lights turn on to whatever setting they had when last turned off.

Development

Ideas from http://blog.dammitly.net/2019/10/cheap-hackable-wifi-light-bulbs-or-iot.html?m=1

Credits

Thanks to:

@dotkrnl

#7 Remove obsolete/invalid parameters from setPilot to fix

@victori

#16 Support costco wiz lights that behave differently from philips wiz

@Supereg

#25 Fix: getter for Name Characteristic returned object instead of the value

@MoTechnicalities

#56 Update README.md

@xmanu

#57 transform the received dimming value to also fit the 10 to 100 range

@BMDan

#67 feat: Support durable custom names in config

@krystofcelba

#74 feat: implement dynamic scenes selector

@bwp91

#81 Add a config schema form

@AndrewSverdrup

#119 Add lastStatus setting so lights remember their setting when turned on

@pyrliu

#118 Added support for Wiz Smart Plug ESP25_SOCKET_01

Contributing

Mostly built for my own personal use, I'll probably reply to any created issues but probably will not actively support anything outside of the RGB bulbs. If you'd like to make a PR through, <3

Furthermore, feel free to create and modify it on your own per MIT License.

How bulbs are discovered

Make a UDP broadcast to port 38899 with the following content:

{"method":"registration","params":{"phoneMac":"<my_mac_address>","register":false,"phoneIp":"<my_ip_address>"}}

You will get a response on port 38900 with the following content:

{"method":"registration","env":"pro","result":{"mac":"<light_address>","success":true}}

License

See LICENSE file

homebridge-wiz-lan's Issues

Help !!

Hi,
I have never used Homebridge before and have installed it with docker on my NAS
I am trying to add around 30 Wiz bulbs but just cannot get this to work
I have added the plugin but get stuck at the sample code.
I pasted it into the config file, changed the port and IP address to mine then added all of the bulbs IP addresses.
When I go to Homekit I don't see anything. I have clicked add accessory but it asks for a qr code to be scanned.
Can you give easy instructions on how to use this with homier and detect my bulbs
Thanks

how do i make a udp broadcast to discover bulbs?

how do i make a udp broadcast to discover bulbs?

No Response from Wiz Recessed Color and Turnable White Light

I get erratic error messages and recessed lights not responding correctly either turning on or off. I don't seem to run into this issue with the Wiz light bulbs. Thoughts on if there is a difference between how the recessed lights and the normal light bulbs treated?

This is the light link i am having issues with https://www.homedepot.com/p/Philips-Color-and-Tunable-White-5-6-in-LED-65W-Equivalent-Dimmable-Smart-Wi-Fi-Wiz-Connected-Recessed-Downlight-Kit-555623/310289033

Let me know if you need me to gather logs to help troubleshoot.

No control in Homekit

I have several wiz lights that were working great. A few months ago, Homekit would not allow me to control the lights but it would show the correct status. Any recommendations?

New user troubles

Hello,
I realize this plugin may be deprecated, so I'm hoping that some of the users might be able to offer me some guidance.

I bought 4 LED RGB WIZ high hat downlights for my living room from HomeDepot. I set them up in the WIZ app, and I paired them to my google account. The google nest I have controls these lights fine. But I have an iPhone, then I got an Apple watch, and found that using Siri would be pretty useful, but WIZ isn't HomeKit approved. So, all new to me, I bought my first Raspberry Pi (Zero WH), and installed homebridge, then installed this homebridge-wiz-lan plugin. After that I was able to add the bridge to Homekit on my phone. However, in HomeKit when I go to "home settings" and select the pi homebridge, unlike my philips Hue bridge which has several lights connected to it, the pi homebridge has no lights attached to it. So nothing shows up in HomeKit. Also, when I go to http://homebridge.local/accessories there are no detected bulbs. I made sure that the lights were on, and set to cool white, and tried rechecking my steps, but I don't see why the bulbs aren't just 'there'.

I thought the bulbs would just be detected, either in homebridge, or in HomeKit when I add the homebridge. I'm wondering if I'm missing an obvious step or if this just requires higher-level troubleshooting? While I am happy to tinker to make things work, I don't have an abundance of patience, nor do I expect it from the community if the developer has already moved on. I would have been happy if WIZ lights would work, but perhaps I'll just have to stick with HUE.

If anyone has any tips or suggestions for me as a noob, please post, and thanks for your time.

Have to ask siri twice for the lights to turn on

The lights only turn on if I ask siri twice. The first time she says "sorry I did not get a response from your devices" Is this an issue can that be fixed? Thank you.

Issue controlling multiple lights

Rolled back to the previous version 2.0.5 to work

ST19 Bulbs work and reporting of bulbs powered off

I was gifted some Wiz RGB A19 bulbs recently and started using the plugin. Couldn’t be easier to get set up and running in Homebridge. Thank you!

Also picked up some ST19 soft white LED 40W (link below), not expecting them to work, but was pleasantly surprised that the plugin just discovered them and could control them out of the box. I know you said you will only be supporting the RGB bulbs but wanted to report in my experience for documentation:

With the ST19 bulb the following features work:

• Detection of brightness level
• Changing of brightness level
• Detection of bulb’s color temperature
• Detection and changing status of bulb on or off

What does not work:

• The plugin exposes the Homekit color picker and allows it to be changed in the Home app. However, this bulb’s color or color temperature is not actually changeable and the bulb seemingly just ignores the command.

https://www.homedepot.com/p/Philips-Soft-White-ST19-LED-40W-Equivalent-Dimmable-Smart-Wi-Fi-Wiz-Connected-Wireless-Light-Bulb-555557/310289025

One thought:
I’ve noticed with both the A19 and the ST19 bulb that if they are turned off at the power switch, Homekit will only report it’s last known status. I’ve seen other plugins report powered off bulbs as off in Homekit. Perhaps if the plugin does not receive the heartbeat from the bulb in XX seconds or if it is not responding to pings, the status of the bulb is reported as off to Homekit?

Adaptive Lighting

Hello,

Homebridge v1.3.0 aded support for adaptive lighting. Any chance we could see it in the plugin?

Removing bulb does not remove from plugin

I replaced a WIZ downlight with another WIZ downlight and the old bulb still shows up in both Homebridge and Homekit. Even if removed from Wiz app, it remains.

Apply for Unmaintained Plugin / Add New Developers

Hey @kpsuperplane and @dotkrnl it was mentioned by one of the Homebridge Developers in a previous issue I created which resulted in a PR that you can apply to Abandon Plug-in if you are not actively developing this plug-in any more. Or perhaps one of the users (@eutampieri) that recently created a PR that is sitting stale might like to take on the plug-in? I really wish I knew what I was doing to take this on myself, but I honestly have no idea where to start and maybe this could give someone else a chance to keep improving this plug-in in the meantime. I can already see with the new Homebridge v1.3.x that there are a number of things that might need fixing. What are your thoughts?

Bulbs

This plug in was working fine a month ago, now since some updates the bulbs are not appearing in accessories. I have uninstalled the plug-in multiple times.

Any advise on troubleshooting?

Thanks

-Mike

Possible to set CT values instead of RGB?

Hello,

I was wondering if there was a way to manually set color temperature (CT) values for Philips WIz bulbs using HomeKit. Another developer on the Hubitat side of things has created a device code for these bulbs here, which allows users to set the CT values (in addition to RGB/HSV). This lets us control the brighter light settings as well as the pre-installed scenes (CT values #6000-6032). I was wondering if there was any way to control these capabilities in Homebridge, as well.

TL;DR - If I could get Siri to turn any of these bulbs a true white (or activate any of their pre-installed scenes without Siri shortcuts) using my voice, I would be so happy.

Thanks!

Model Length Error message

I am fully updated on the plugin but on Homebridge I am getting this error message 3 or 4 times...

[homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Model': [Model] characteristic must have a length of more than 1 character otherwise HomeKit will reject this accessory, ignoring new value. See https://git.io/JtMGR for more info.

Thoughts on what could be causing this?

Feature Request: Add Change Logs to Config-UI-X

I was wondering if you can make your change logs appear in config-ui-x? Some plugins when updated on that UI have a pop-up box that lists the latest updates to the plug-in :) I believe all you need to do is move the Changelog from README.md to the CHANGELOG.md file. I am quoting the developer of the homebridge-xiaomi-roborock-vacuum for what he said he did when I raised the issue there. When I updated your plug-in today, I had no idea what the change was until I went to Github. Thanks :)

Bulbs not found for Homebridge

I installed v2.0.5.

Running Homebridge 1.1.1 (Node.js version 12.15.0) and I can't add my two Wiz bulbs to Homekit via this plugin. My config has this:
{ "platform": "WizSmarthome", "name": "WizSmarthome" },

Bulbs No Longer Found

Hey there - I know you've moved on to the Philips Hue ecosystem, but I'm trying to get my Wiz lights working with Homebridge. They were working fine in HOOBS, but after switching over to the official Homebridge Raspberry Pi OS, and installing your plugin, nothing is showing up. Could you possibly see if anything has changed with their API, or if something was broken in the more recent Homebridge updates? I appreciate your help.

[BUG] TW Light Reverts to RGBW Selector

I have a very curious one @kpsuperplane, originally these TW lights (model ESP56_SHTW3_01) showed only white selections and only the temperature wheel; once selecting from the temperature wheel the menu selection now displays colours and both a colour and temperature wheel. It seems to be stuck as an RGBW light now.

This has not broken anything, but definitely a bug.

Missing Bulbs in Child Bridge Mode

I switched the plugin to child mode, but now only 3 of my 6 bulbs are showing up in HomeKit. My log shows, "A platform configured a new accessory under the plugin name 'WizSmarthome'. However no loaded plugin could be found for the name!" on startup, but I believe that was being logged before the change to child bridge.

Bulbs reverting custom names in Home app upon HOOBS reboot

First I will say, all the bulbs are found & work fine. I do however have an issue upon rebooting HOOBS where the names & icons I have added in Apple Home app are lost & the tiles in Home app revert to the alphanumeric name the bulbs begins with as default. Even when I name in them with custom names in HOOBS. I have checked initially with HOOBS support & they believe this is a cache handling issue relative to the plugin.

Thoughts?

Randy M.

No loaded plugin could be found for the name

Using version 3.0.0 of this plugin installed via npm, I encounter the following message:

A platform configured a new accessory under the plugin name 'WizSmarthome'. However no loaded plugin could be found for the name!

I think Homebridge is expecting WizSmartHome to match homebridge-wiz-lan.

On/Off commands not working with dynamic settings

Hi,

Just setup the latest version of the plugin (v2.0.4) on latest version of home bridge (v0.4.53). Plugin works with lights if if they are set via the Wiz app to use the "white" bundle of settings (warm, day, cool, night) or a set custom color (via app or home bridge). If the bulbs are in any of the dynamic or simple setting bundles the lights will not respond to home bridge on/off commands but home bridge display the correct state (on/off). Weird thing is you can change the color of the bulb from one of the dynamic bundles to a fixed color via the home app, then the light will respond to on/off commands.

Is this a known feature gap?

Cannot read property 'state of undefined

Recently some of my wiz bulbs have stopped responding. Here is the console output:

This plugin threw an error from the characteristic 'Color Temperature': Unhandled error thrown inside write handler for characteristic: Cannot read property 'state' of undefined. See https://git.io/JtMGR for more info.
[5/10/2021, 09:14:32] [homebridge-wiz-lan] TypeError: Cannot read property 'state' of undefined
    at Object.setPilot (/usr/local/lib/node_modules/homebridge-wiz-lan/src/accessories/WizBulb/pilot.ts:140:21)
    at Characteristic.<anonymous> (/usr/local/lib/node_modules/homebridge-wiz-lan/src/accessories/WizBulb/characteristics/temperature.ts:39:9)
    at Characteristic.emit (events.js:327:22)
    at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1632:16
    at new Promise (<anonymous>)
    at Characteristic.<anonymous> (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1630:14)
    at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
    at Object.next (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:124:57)
    at /usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:117:75
    at new Promise (<anonymous>)

No changes on my end. 2 of my 3 wiz bulbs have stopped responding

Not working with HomeBridge 1.3.0 anymore

After upgrading HomeBridge to 1.3.0 the plugin is not working anymore

[22/02/2021, 10:36:52] [homebridge-wiz-lan] This plugin threw an error from the characteristic 'Model': Error: [Model] characteristic must have a length of more than 1 character otherwise HomeKit will reject this accessory. Ignoring new value. at Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1991:38) at Characteristic.<anonymous> (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1457:21) at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27) at Object.next (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:124:57) at /usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:117:75 at new Promise (<anonymous>) at Object.__awaiter (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:113:16) at Characteristic.handleGetRequest (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/dist/lib/Characteristic.js:632:24) at Characteristic.<anonymous> (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2127:22) at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27) See https://git.io/JtMGR for more info.

Brightness

Hi,
Any idea about this warning.??
This plugin generated a warning from the characteristic 'Brightness': characteristic was expected valid number and received NaN.

Versión de Node.js: v14.15.5
Versión de npm: v6.14.11
Bulbs: GU10 & A.E27

Regards, Ramon

Plugin stopping Hoobs Homebridge from restarting

Found wiz plugin stopping Homebridge from automatically restarting. This forces users to manually unplug the home bridge and could potentially result in SD card failure if system is hosted on SD card

Haven't yet investigated into the details. Will update later if more details found. Thanks

5/29/2021, 5:19:36 PM Got SIGINT, shutting down Bridge...
5/29/2021, 5:19:37 PM Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running
    at healthCheck (dgram.js:897:11)
    at Socket.close (dgram.js:719:3)
    at HomebridgeAPI.<anonymous> (/home/hoobs/.hoobs/node_modules/homebridge-wiz-lan/src/util/network.ts:141:12)
    at HomebridgeAPI.emit (events.js:315:20)
    at process.<anonymous> (/usr/local/lib/node_modules/@hoobs/hoobs/bridge/cli.js:77:28)
    at process.emit (events.js:315:20)
    at process.emit (/usr/local/lib/node_modules/@hoobs/hoobs/node_modules/source-map-support/source-map-support.js:495:21)

Homekit Automations with Wiz Plugin

I have been running into some weird HomeKit shortcut automations with button presses. I create a automation to check if the light is on or off and based on that it turns it on or off. The automations rarely have a issue with turning the wiz lights off but turning on they always time out. I can manually turn them on and off. I was wondering if you have run into this issue before?

Enhancement: Is it possible to reduce the wifi traffic of the plugin using any parameters?

Invalid JSON in an platform error message

Complete newbie here, basically a baby playing with scissors. Trying to get the wiz plugin to work using homebridge (HOOBS build). Using the "simple configuration" I get the following error:

"Unable to save. Please fix the following errors. Invalid JSON in an platform."

• Wiz Lan: Version 3.0.2 (3/11/21)
• HOOBS: Version 3.3.5

I'm pasting into configuration field:

"platforms": [{
"platform": "WizSmarthome",
"name": "WizSmarthome",
}]

Perhaps someone could assist in identifying what I'm doing wrong? Thanks in advance!

Scene Support

Is there a way to enable importing Wiz scenes into Homekit?

Still Reports as On When Unplugged

@kpsuperplane I noticed something after testing out a Filament style bulb that I didn’t turn off but instead just unscrewed it from the lamp. In HomeKit it was still reporting as ‘on’ until I pressed off in the Home app; this makes me suspect that feedback status or polling is not properly implemented. Have you noticed these issues before?

"This plugin slows down Homebridge" Reported by Homebridge 1.3.x

Noticed while testing #32 and wanted to bring forward since still unresolved.

This is occurring when a bulb goes off-line or powered off at the mains. The below messages are logged to the console for each bulb that is powered off at the switch. I have two Wiz bulbs controlled by a single switch, so I see the below message twice. After about 10 seconds, the bulb reports in Homekit as "No Response". However, during this 10 seconds or so, the other Wiz lights are stuck on "Updating" until the timeout occurs. I have all plug-ins isolated with to their own Child Bridge, so for me only affects the Wiz lights.

[2/24/2021, 8:51:44 AM] [homebridge-wiz-lan] This plugin slows down Homebridge. The read handler for the characteristic 'On' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.
[2/24/2021, 8:51:44 AM] [homebridge-wiz-lan] This plugin slows down Homebridge. The read handler for the characteristic 'Brightness' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.

Stats:

• running on the Homebridge-VM-Image Boot2Docker virtual machine
• OS: Ubuntu Bionic Beaver (18.04.5 LTS)
• Node.js Version: v14.15.5
• Npm Version: v6.14.11
• Homebridge: 1.3.1

Smart Plugs stopped working

For some reason my WiZ Smart Plugs stopped working after updating to the newest version. Any reason they would act out now?

Version 3.0.0 crashes Homebridge v1.3.1

When updating homebridge-wiz-lan to 3.0.0, homebridge crashes on restart. The following log appears:

Started Homebridge v1.3.1 with PID: 31751
Initializing HAP-NodeJS v0.9.2...
[26/02/2021, 15:42:44] Loaded config.json with 0 accessories and 2 platforms.
[26/02/2021, 15:42:44] Loaded 1 cached accessories from cachedAccessories.
[26/02/2021, 15:42:44] ---
[26/02/2021, 15:42:51] Loaded plugin: [email protected]
[26/02/2021, 15:42:51] Registering platform 'homebridge-config-ui-x.config'
[26/02/2021, 15:42:51] ---
[26/02/2021, 15:42:52] Loaded plugin: [email protected]
[26/02/2021, 15:42:53] Registering platform 'homebridge-rpi.Lib'
[26/02/2021, 15:42:53] Registering platform 'homebridge-rpi.RPi'
[26/02/2021, 15:42:53] ---
[26/02/2021, 15:42:53] Loaded plugin: [email protected]
[26/02/2021, 15:42:53] Registering platform 'homebridge-wiz-lan.WizSmarthome'
[26/02/2021, 15:42:53] ---
[26/02/2021, 15:42:53] Loading 2 platforms...
[26/02/2021, 15:42:53] [Config] Initializing config platform...
[26/02/2021, 15:42:53] [Config] Running in Service Mode
[26/02/2021, 15:42:54] [WizSmarthome] Initializing WizSmarthome platform...
[26/02/2021, 15:42:54] [WizSmarthome] Loading accessory from cache: a8bb50d63554
[26/02/2021, 15:42:56] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Model': characteristic value expected string and received undefined. See https://git.io/JtMGR for more info.
[26/02/2021, 15:42:56] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Model': [Model] characteristic must have a length of more than 1 character otherwise HomeKit will reject this accessory, ignoring new value. See https://git.io/JtMGR for more info.
[26/02/2021, 15:42:56] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Serial Number': characteristic value expected string and received undefined. See https://git.io/JtMGR for more info.
[26/02/2021, 15:42:56] TypeError: Cannot read property 'includes' of undefined
    at /usr/local/lib/node_modules/homebridge-wiz-lan/src/accessories/WizBulb/index.ts:19:57
    at Array.some (<anonymous>)
    at Object.is (/usr/local/lib/node_modules/homebridge-wiz-lan/src/accessories/WizBulb/index.ts:19:31)
    at /usr/local/lib/node_modules/homebridge-wiz-lan/src/wiz.ts:54:63
    at Array.find (<anonymous>)
    at HomebridgeWizLan.initAccessory (/usr/local/lib/node_modules/homebridge-wiz-lan/src/wiz.ts:54:35)
    at HomebridgeWizLan.configureAccessory (/usr/local/lib/node_modules/homebridge-wiz-lan/src/wiz.ts:72:10)
    at /usr/local/lib/node_modules/homebridge/src/bridgeService.ts:317:25
    at Array.filter (<anonymous>)
    at BridgeService.restoreCachedPlatformAccessories (/usr/local/lib/node_modules/homebridge/src/bridgeService.ts:277:69)
[26/02/2021, 15:42:56] Got SIGTERM, shutting down Homebridge...

Downgrading back to 2.2.0 fixes this.

Plugin Needs Polling to Determine Status

HomeKit does not update the bulb status unless you leave the room or app and come back.
My test:

• Go into HomeKit Room and turn on light using bulb icon.
• physically turn off power to bulb.

Result:
Icon never changes until I exit the HomeKit room then re-enter. Same if I start with a "no response" bulb and power it on. The status doesn't update until I exit the HomeKit room and re-enter.

Device Name

@kpsuperplane first of all thanks for a pretty awesome plugin! Since I’m pretty new to home bridge I may have missed something but is there a way for the plug-in to pull the name given in the Wiz app to then be reflected in HomeKit? Or some sort of way for the names to not drop out of HomeKit once I’ve set them. Problem being I have 19 of these wiz lights and whenever there is an update to the plug-in or even the confit-ui plug all the names drop out and so begins the tedious process of re-labeling them. If there is another solution somewhere I may have not seen either by a setting or another plug-in I’d love to know.

Takeovers of this work.

It seams that the founder of this valuable work has abandoned it.🥺 Isn't it possible for a person with interest in this repository to simply create a new branch, rename it and improve it, then simply let us know what the new branch is to follow?🤔 I really wish I could! But currently working up to 80 hours/ week! Just not enough time to devote! I really like these bulbs and LED strips! I hope someone can do it soon.🖖🏼

detected only one of 4 light bulbs in my house

not sure why - how can I detect the others?

NaN receieved for Hue and Saturation Characteristics

Since upgrading to Homebridge v1.3.x my Homebridge logs are being flooded with the following warnings every few seconds:

[23/02/2021, 13:05:54] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Saturation': characteristic was expected valid number and received NaN. See https://git.io/JtMGR for more info.
[23/02/2021, 13:05:55] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Hue': characteristic was expected valid number and received NaN. See https://git.io/JtMGR for more info.

I have the filament (non-rgb) bulbs and this plug-in was designed for rgb bulbs; so I imagine this is part of the issue.

Loading from cache funciton does not refresh for removed bulbs

When bulbs are removed physically, the plugin still tries to load bulb from cache leaving unresponsive bulbs

homebridge-wiz-lan/src/wiz.ts

Line 40 in c34da79

registerDiscoveryHandler(this, this.tryAddDevice.bind(this));

homebridge-wiz-lan/src/wiz.ts

Line 82 in c34da79

configureAccessory(accessory: PlatformAccessory) {

homebridge-wiz-lan/src/wiz.ts

Line 126 in c34da79

this.api.updatePlatformAccessories([existingAccessory]);

Filament Style Bulbs

Hi @kpsuperplane, I just installed your plug-in to see how I like these lights. I do notice you say this is mostly for RGB bulb support, but was wondering if at any stage you will be looking at making the plug-in to better accept dimmable white temperature changing bulbs?

As they currently show a colour palette in HomeKit and the colour temperature does not appear to actually work; it looks like you just use the colours.

Brightness Discrepancies Between Home App and Wiz App (Downlights)

Hi,

Thank you so much for creating this plug-in!

I know it hasn't been tested on anything other than the bulbs stated on the page but I've tried the plug-in with the Non-RGB Downlight (Model ID: 23041, Ver. 1.20.0) with success! I'm very excited to be able to control these downlights!

However, there's just one quirk, it seems that there's a discrepancy in brightness between what you set in Home app and what is being set when you open the Wiz app and go right back into Home app. Interestingly, the discrepancies seem to diminish as the brightness percentage set in Home app goes up. In other words, the higher you set the brightness in Home app, the lower the brightness discrepancies are when you go into the Wiz app and back.

I'm on Homebridge v1.3.4 and iOS 14.4.1 and I've turned on the "Last Status" option in the Power-on Behavior setting and it makes no difference at all.

Below are testing done by setting a brightness value in Home app then switch into the Wiz app and back to Home app. Here are my findings:

01% > 10%
10% > 18%
20% > 27%
30% > 36%
40% > 45%
50% > 55%
60% > 64%
70% > 73%
80% > 82%
90% > 91%

Is there anything that can be done about this?

Thank you again for this awesome plug-in!

Matt

Use of getCharacteristicValue creates infinite loop!

The method getCharacteristicValue calls .getValue() on the characteristic object.

See

homebridge-wiz-lan/lib/homekit-device/index.js

Lines 87 to 94 in 0253f46

	getCharacteristicValue(characteristic) {
	this.log.debug(
	'[%s] getCharacteristicValue',
	this.name,
	this.platform.getCharacteristicName(characteristic)
	);
	return this.getCharacteristic(characteristic).getValue();
	}

There are two issues with that

• getValue() doesn't return anything at all. Its a callback based method, where the resulting value is passed into the callback passed to the method
• getValue() is the function called when handling a request. It will query the the read handler of the plugin. e.g. what is set up for the GET request.

Thus, in the case of

homebridge-wiz-lan/lib/wiz-accessory.js

Lines 153 to 155 in 0253f46

	c.on('get', cb =>
	cb(null, this.hkDevice.getCharacteristicValue(characteristic))
	);

this will actually create an infinite loop, as the get event will fire a getValue() which again fires an get event an so on.

Instead of using .getValue() just use the property .value to retrieve the current value. But if your "get" handler just consist of return .value you can just omit registering a "get" handler, as returning .value is the default behavior.

A stack trace created with the latest beta

Name@Homebridge B03F] Unhandled error thrown inside read handler for characteristic: Error: characteristic value expected string and received object
    at Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1917:17)
    at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1428:24
    at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:9:18
    at Characteristic.<anonymous> (/usr/local/lib/node_modules/homebridge-wiz-lan/lib/wiz-accessory.js:154:11)
    at Characteristic.emit (events.js:315:20)
    at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1404:14
    at new Promise (<anonymous>)
    at Characteristic.<anonymous> (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1402:12)
    at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:140:27)
    at Object.next (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:121:57)

Light Strip manual toggle button

The HomeKit On/Off status of the WIZ light strips does not update when I toggle the state with the manual switch, unless I leave the HomeKit room and come back in or leave the Home app and come back in. The WIZ App does update with a manual toggle. So, the Homebridge/HOOBS plugin is not properly evaluating and updating the state of WIZ devices to HomeKit. The manual switch on the LED strip is only a state toggle. It does not cut overall power to the device.

Control RGB and White independently

I have a WIZ ceiling light which consists of a white (warm/cold) main light and an rgb led strip.
Both are meant to be controlled independently (rgb lighting the ceiling, white lighting the room).

Can you add an option to control these independently via HomeKit?
Having two devices would absolutely be an option, this does not have to be combined into one HomeKit/Homebridge device

This plugin threw an error from the characteristic 'Color Temperature': Unhandled error

[8/5/2021, 11:34:40 PM] [homebridge-wiz-lan] This plugin threw an error from the characteristic 'Color Temperature': Unhandled error thrown inside write handler for characteristic: Cannot read property 'state' of undefined. See https://git.io/JtMGR for more info.

Any ideas what this is about?

Enhancement request: Any chance that Dynamic modes could be added?

Thank you for your work on this plugin! Just curious if there's any feasibility that Dynamic lighting modes could be added? Is this feature something dependent on the Wiz app, and not accessible through local processes?

Hoobs 4

Looks like the new hoobs doesn't play well. Just keeps wanting to install and shows no configuration page to enter settings.

Plugin not loading

Fresh install of HomeBridge on Ubuntu Server 19.10

Trying to load the plugin gives the following error in logs:

[2/20/2020, 12:08:20 AM] ====================
[2/20/2020, 12:08:20 AM] ERROR LOADING PLUGIN homebridge-wiz-lan:
[2/20/2020, 12:08:20 AM] /usr/lib/node_modules/homebridge-wiz-lan/lib/client/index.js:256
setPilot = (host, state) => {
^

SyntaxError: Unexpected token =
at new Script (vm.js:79:7)
at createScript (vm.js:251:10)
at Object.runInThisContext (vm.js:303:10)
at Module._compile (internal/modules/cjs/loader.js:657:28)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (internal/modules/cjs/helpers.js:22:18)
[2/20/2020, 12:08:20 AM] ====================

I do have other plugins working so either I am missing a dependency or something is wrong? I'm new to HomeBridge.

Unable to control bulbs from Homekit

Starting on/about 14 July, about half of my bulbs (9ish) no longer respond to Homekit control via this plugin. Still working through the (new) Wiz app. Mix of A19 bulbs and recessed downlights, all RGB.

Updated npm/node.js.

All bulbs on same subnet.

I wonder if the app update changed something. I had to download a whole new one and migrate all of the configuration to it.

Anyone else having similar issue?