@BarryA
The driver installed with no issues. When I run scan nearby it finds the KP115 almost instantly, but it never finds the HS105.
The KP115 is a functioning smart plug, but there are broken clouds in the in the Energy Consumption & Power Meter fields.
I tired uninstalling and reinstalling both devices and the driver several times. The results are always the same.
When I look in the logs the the driver is polling the KP115 about every 2 seconds which seems excessive.
Any ideas on how to fix this? On the plus side I have have 1 more local device.
@Sylvain any thoughts.
BarryA Barry Andersen Developer
2d
I have an Edge driver for LIFX here: GitHub - bcandersen/lifx-st-edge: LIFX driver for the SmartThings Edge platform
It’s been a while since I’ve ran it. May require some updates if there’s been any breaking API changes.
Also, TP-Link driver here for those interested: GitHub - bcandersen/tplink-st-edge: TP-Link Driver For SmartThings Edge Platform
2 Likes
Logs for the above
2022-09-02T03:05:24.778563964+00:00 INFO TP-Link Initializing TP-Link Edge Driver
2022-09-02T03:05:24.799522547+00:00 TRACE TP-Link Setup driver tplink with lifecycle handlers:
DeviceLifecycleDispatcher: tplink
default_handlers:
removed:
init:
added:
driverSwitched:
child_dispatchers:
2022-09-02T03:05:24.803495589+00:00 TRACE TP-Link Setup driver tplink with Capability handlers:
CapabilityCommandDispatcher: tplink
default_handlers:
colorControl:
setColor
setSaturation
setHue
switchLevel:
setLevel
switch:
on
off
colorTemperature:
setColorTemperature
child_dispatchers:
2022-09-02T03:05:24.816270089+00:00 DEBUG TP-Link driver device thread event handled
2022-09-02T03:05:24.819363756+00:00 TRACE TP-Link Received event with handler environment_info
2022-09-02T03:05:24.823607422+00:00 TRACE TP-Link Received event with handler environment_info
2022-09-02T03:05:24.826559714+00:00 DEBUG TP-Link Z-Wave hub node ID environment changed.
2022-09-02T03:05:24.830746547+00:00 TRACE TP-Link Received event with handler discovery
2022-09-02T03:05:24.837353839+00:00 INFO TP-Link Starting TP-Link Discovery
2022-09-02T03:05:29.922691423+00:00 TRACE TP-Link received discovery response from from: 192.168.1.196:9999
2022-09-02T03:05:29.925883131+00:00 DEBUG TP-Link found TP-Link device (Phone Charger Plug) with IP: 192.168.1.196
2022-09-02T03:05:29.928815756+00:00 INFO TP-Link Discovered new TP-Link device - Name: Phone Charger Plug test DNI: 8006CDD34A6D9BE4EB1DD8D8AA0222061EC00051 IP: 192.168.1.196:9999 Type: IOT.SMARTPLUGSWITCH Model: KP115(US)
2022-09-02T03:05:30.484366256+00:00 TRACE TP-Link Received event with handler device_lifecycle
2022-09-02T03:05:30.493525131+00:00 INFO TP-Link <Device: 48b145f2-1afc-46f4-9cc9-0e7212249fa4 (Phone Charger Plug)> received lifecycle event: added
2022-09-02T03:05:30.501523381+00:00 TRACE TP-Link Received event with handler device_lifecycle
2022-09-02T03:05:30.506235673+00:00 INFO TP-Link <Device: 48b145f2-1afc-46f4-9cc9-0e7212249fa4 (Phone Charger Plug)> received lifecycle event: doConfigure
2022-09-02T03:05:30.525726298+00:00 TRACE TP-Link Found DeviceLifecycleDispatcher handler in tplink
2022-09-02T03:05:30.528603423+00:00 INFO TP-Link [48b145f2-1afc-46f4-9cc9-0e7212249fa4] Adding new TP-Link device: Phone Charger Plug
2022-09-02T03:05:30.538054381+00:00 INFO TP-Link [48b145f2-1afc-46f4-9cc9-0e7212249fa4] Initializing TP-Link device: Phone Charger Plug
2022-09-02T03:05:30.544724715+00:00 WARN TP-Link No TP-Link device object found for Phone Charger Plug. Starting discovery...
2022-09-02T03:05:30.868309631+00:00 TRACE TP-Link received discovery response from from: 192.168.1.196:9999
2022-09-02T03:05:30.871383631+00:00 DEBUG TP-Link found TP-Link device (Phone Charger Plug) with IP: 192.168.1.196
2022-09-02T03:05:35.150482382+00:00 TRACE TP-Link received discovery response from from: 192.168.1.196:9999
2022-09-02T03:05:35.153714257+00:00 DEBUG TP-Link found TP-Link device (Phone Charger Plug) with IP: 192.168.1.196
2022-09-02T03:05:35.883651132+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:05:35.888519299+00:00 TRACE TP-Link Found DeviceLifecycleDispatcher handler in tplink
2022-09-02T03:05:35.891499632+00:00 INFO TP-Link [48b145f2-1afc-46f4-9cc9-0e7212249fa4] Initializing TP-Link device: Phone Charger Plug
2022-09-02T03:05:35.894498799+00:00 WARN TP-Link Poll timer for Phone Charger Plug already started. Skipping...
2022-09-02T03:05:35.897501007+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:05:35.901290924+00:00 TRACE TP-Link <Device: 48b145f2-1afc-46f4-9cc9-0e7212249fa4 (Phone Charger Plug)> received unhandled lifecycle event: doConfigure
2022-09-02T03:05:35.904290215+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:05:35.913832882+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:05:35.918418049+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:05:37.887935424+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:05:37.891185966+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:05:37.920511382+00:00 INFO TP-Link [48b145f2-1afc-46f4-9cc9-0e7212249fa4] Marking TP-Link device online: Phone Charger Plug
2022-09-02T03:05:37.926885966+00:00 INFO TP-Link <Device: 48b145f2-1afc-46f4-9cc9-0e7212249fa4 (Phone Charger Plug)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"on"}}
2022-09-02T03:05:37.937274966+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:05:39.894488049+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:05:39.897645299+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:05:39.929263799+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:05:40.373150508+00:00 TRACE TP-Link received discovery response from from: 192.168.1.196:9999
2022-09-02T03:05:40.376185049+00:00 DEBUG TP-Link found TP-Link device (Phone Charger Plug) with IP: 192.168.1.196
2022-09-02T03:05:41.902095758+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:05:41.909174091+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:05:41.937793299+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:05:43.909301258+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:05:43.912726633+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:05:43.978928550+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:05:45.591174092+00:00 TRACE TP-Link received discovery response from from: 192.168.1.196:9999
2022-09-02T03:05:45.594207675+00:00 DEBUG TP-Link found TP-Link device (Phone Charger Plug) with IP: 192.168.1.196
2022-09-02T03:05:45.914260550+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:05:45.917263717+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:05:45.945897717+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:05:47.923209800+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:05:47.926297883+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:05:47.959459508+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:05:49.924920134+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:05:49.928077300+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:05:49.960671967+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:05:50.812564300+00:00 TRACE TP-Link received discovery response from from: 192.168.1.196:9999
2022-09-02T03:05:50.815914050+00:00 DEBUG TP-Link found TP-Link device (Phone Charger Plug) with IP: 192.168.1.196
2022-09-02T03:05:51.927149676+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:05:51.930529467+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:05:51.959191134+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:05:53.960092926+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:05:53.989559676+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:05:54.027734884+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:05:55.934562218+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:05:55.937567718+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:05:55.966552384+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:05:56.035453301+00:00 TRACE TP-Link received discovery response from from: 192.168.1.196:9999
2022-09-02T03:05:56.038835259+00:00 DEBUG TP-Link found TP-Link device (Phone Charger Plug) with IP: 192.168.1.196
2022-09-02T03:05:57.935821510+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:05:57.938862426+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:05:57.969087593+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:05:59.944892135+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:05:59.947996260+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:05:59.980150468+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:06:01.270278302+00:00 TRACE TP-Link received discovery response from from: 192.168.1.196:9999
2022-09-02T03:06:01.273451552+00:00 DEBUG TP-Link found TP-Link device (Phone Charger Plug) with IP: 192.168.1.196
2022-09-02T03:06:01.947287843+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:06:01.950444927+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:06:01.980230635+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:06:03.955251927+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:06:03.958299260+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:06:04.033443469+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:06:05.964834052+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:06:05.968017177+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:06:06.009144636+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:06:06.522800344+00:00 TRACE TP-Link received discovery response from from: 192.168.1.196:9999
2022-09-02T03:06:06.525843052+00:00 DEBUG TP-Link found TP-Link device (Phone Charger Plug) with IP: 192.168.1.196
2022-09-02T03:06:07.968229053+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:06:07.972556553+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:06:08.017941928+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:06:09.976161844+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:06:09.979245261+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:06:10.021229719+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:06:11.703548678+00:00 TRACE TP-Link received discovery response from from: 192.168.1.196:9999
2022-09-02T03:06:11.706776303+00:00 DEBUG TP-Link found TP-Link device (Phone Charger Plug) with IP: 192.168.1.196
2022-09-02T03:06:11.984698803+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:06:11.987876095+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:06:12.020384511+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:06:13.987737262+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:06:13.990823387+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:06:14.027451053+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:06:15.995770303+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:06:15.998727303+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:06:16.031622845+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:06:16.928374054+00:00 TRACE TP-Link received discovery response from from: 192.168.1.196:9999
2022-09-02T03:06:16.931993845+00:00 DEBUG TP-Link found TP-Link device (Phone Charger Plug) with IP: 192.168.1.196
2022-09-02T03:06:18.009426095+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:06:18.012874304+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:06:18.056911470+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:06:20.011555262+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:06:20.014909221+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:06:20.044633887+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:06:22.014761263+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:06:22.017752804+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:06:22.049560179+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:06:22.148182804+00:00 TRACE TP-Link received discovery response from from: 192.168.1.196:9999
2022-09-02T03:06:22.152138221+00:00 DEBUG TP-Link found TP-Link device (Phone Charger Plug) with IP: 192.168.1.196
2022-09-02T03:06:24.018902179+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:06:24.022112304+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:06:24.056060721+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:06:24.817949430+00:00 DEBUG TP-Link Performing periodic device health check
2022-09-02T03:06:24.821005471+00:00 DEBUG TP-Link driver device thread event handled
2022-09-02T03:06:26.024138930+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:06:26.027119846+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:06:26.059885805+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:06:27.411909638+00:00 TRACE TP-Link received discovery response from from: 192.168.1.196:9999
2022-09-02T03:06:27.414961346+00:00 DEBUG TP-Link found TP-Link device (Phone Charger Plug) with IP: 192.168.1.196
2022-09-02T03:06:28.025930680+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:06:28.040454138+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:06:28.087999930+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:06:30.034701638+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:06:30.037790763+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:06:30.067488180+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:06:32.040849305+00:00 TRACE TP-Link Polling device: Phone Charger Plug
2022-09-02T03:06:32.044013555+00:00 DEBUG TP-Link Sending command to 192.168.1.196 via udp: {"system":{"get_sysinfo":{}}, "emeter":{"get_realtime":{}}}
2022-09-02T03:06:32.089712305+00:00 DEBUG TP-Link Phone Charger Plug device thread event handled
2022-09-02T03:06:32.598022722+00:00 TRACE TP-Link received discovery response from from: 192.168.1.196:9999
2022-09-02T03:06:32.601243139+00:00 DEBUG TP-Link found TP-Link device (Phone Charger Plug) with IP: 192.168.1.196
2022-09-02T03:0
Sylvain
September 2, 2022, 2:25pm
3
@Paul_Oliver
1 Like
BarryA
September 2, 2022, 4:34pm
4
That’s odd. Looking at the logs it appears the driver never received a response from your HS105 during discovery. I onboarded an HS105 (HW: 1.0, FW: 1.5.6) to my hub this morning, was found right away. I would start by giving your plug a power cycle and verifying it’s on the same network as your hub. Discovery relies on IP broadcast, there’s also a possibility you have a switch or AP that may be dropping broadcast packets.
I do remember TP-Link had started disabling local control on some of their devices a couple years ago with a firmware update, but I believe they reversed that decision shortly after. Verify the FW is up to date.
Omg this is amazing…do these drivers work for the HS200/HS210 wifi switches ?
I assume i would have to remove each one and scan via wifi on my smartthings hub to add each one? @BarryA
I have hardware version 5.0 and firmware 1.0.2. when I run update firmware it says it “no updates available”
First I deleted the driver I got from GitHub last night and installed the driver from your new link.
Then I plugged and unplugged the HS105 while discover was running and it SUCCESSFULLY found the plug.
So the only remaining problem is no power reporting on KP115.
BarryA
September 2, 2022, 5:05pm
9
I have tested with a HS200, so they should both work.
If you are currently using the official TP-Link cloud integration, you’ll have to remove those devices first since there is no migration path to the Edge driver. Then enroll in the channel, install the driver to your hub, then you can discover them by doing a “Scan for nearby devices” in the app.
BarryA
September 2, 2022, 5:08pm
10
Sorry about that, I do not have a KP115 to test with at this time. If I can get my hands on one I can try to get it working. Since the TP-Link API is not documented, adding new devices/capabilities often requires manual inspection of the protocol from the device itself.
Thanks, I am happy to get the devices working locally, and the official integration does NOT include energy monitoring, so I didn’t lose any functionality.
Thanks again for sharing with the community.
Perfect, going to give this a try this weekend =) thank you so much for sharing this with the community. I know there are many of us that have TP-Link switches that would love to have them run locally
jkp
September 2, 2022, 6:23pm
13
I have the outdoor plug (KP400) with two outlets. I am able to find it but it only the master outlet that controls both plugs but there is no individual outlets found so I am unable to control each separately. Also, the status works the first time and then gets stuck in the off position.You can still control both (off/on) but status changes for a brief second and changes back to off.
1 Like
BarryA
September 2, 2022, 6:57pm
14
Yeah, unfortunately there is still some work to be done for the multi-component devices like the dual plug outlet and the power strip. At the time I wrote the driver multi-component devices were not yet supported for Edge drivers. If there is now support I will look into getting that fixed.
1 Like
RJGill84
September 2, 2022, 11:32pm
15
@BarryA thank you for providing the link to enroll in the channel. Typically after installing a particular driver I do a scan and the driver comes up as a new device but that is not happening here. How do we add bulbs? I assume we will need to create a new device but how is that done?
You just need to install the driver in the usual manner. Then do scan nearby and it should pick up any TP-Link Kasa devices that you already installed on your network using the Kasa app. I have 1 device that I had to unplug and plug in during the discover process.
RJGill84
September 3, 2022, 12:22am
17
I am referring to the LiFX driver. Scan nearby does not seem to work post driver install as nothing is found.
Sorry, I have no LiFX devices, do I don’t know.
koyfam
September 4, 2022, 12:22am
19
I installed the driver and it found all my LIFX bulbs right away. Odd that it didn’t find yours. Are the bulbs on the same WiFi network as the hub?
Sakari
September 4, 2022, 8:27am
20
What do you mean by that? If I purchase a product can I figure all that info out so you could add it to your dirver?
koyfam