Will you be able to update the drivers to accomodate the new scenes capabilities? In this thread I am having issues with the TP-Link bulb driver not providing the correct events and attributes. Reference this thread for the context:
Is that a custom driver you are using for TP-Link bulb?
It is DaveGut's TPLink he ported over from ST. I don't believe HE natively supports WiFi Color Bulbs like TP-Link.
Yes, we don't have that driver. Your problem is probably with that driver. I think @mike.maxwell addressed that issue in the other thread. This has nothing to do with Groups and Scenes, other than that this app expects color bulbs to conform to the standard Mike pointed to.
I agree completely. Asking developer @djgutheinz what he might be able to do to the driver to conform to HE standards.
What is the upgrade path from current driver/app scenario? Do I have to recreate devices?
Excellent job! Though the naming change of the app totally freaked me out as I am looking for TP-Link not Hubitat TP-Link lol!
Hi Dave (@djgutheinz)
Thanks for your fine work!!
I previously had a functional Node config running on a Pi with 2 TP-Link HS105 devices using TP-LinkHub_v2.js
- Updated the *_v2.js file to *_v3.js
- Updated TP-Link Plug-Switch (Hubitat).groovy
- Added TP-Link Hubitat Manager.groovy
Initially got this error in the Hubitat TP-Link/Kasa Manager log
Restarted the PI & then got this; ALL OK!!!
As both devices were already there & functional, I deleted 1 device.
I also updated the following in the remaining plug:
In theory the Hubitat TP-Link/Kasa Manager should now discover the plug I deleted from the system earlier... However, it just sits at this screen & never discovers anything:
I am also now getting this error:
I am sure this error is because the node server crashed and that a restart will fix it, but I am also sure the crash will happen again...
Edit:
Restarted the Pi, was OK for a short while & back to the error state:
Thanks
J
Had to update all my devices with installation type but all is working and migrated. Now to look at you local json implementation as I do have a dedicated Pi3 for the home.
Are the devices working? Indications from the last message is the node.js applet was not running at the time. For PCs, I use a bat file that restarts the node when it stops for an error; however, there may be an untrapped error that is causing the crash on the pi3.
Dave
Yup I am good
I have been using the local node server since @djgutheinz released it for hubitat It has been rock solid for me.
1 Like
HS107 and HS300 now supported
Added support to HS107 and HS300. One issue. For Hub (Node Applet) installation, the user must manually update the label after installation. A temporary label is created on initial installation. (I am working on this shortfall.)
Just updated the Node Applet to eliminate an error while polling for devices. It was crashing on a socket close. Added a "try" routine to preclude crash. Applet available on the new GitHub link.
Dave
@djgutheinz I am not good. The cloud doesn’t seem to work correctly and I had to revert to the deprecated cloud drivers. This was only for my colored bulbs. All switches worked without issues.
Issues by just changing code:
- lost all color control
- lost circadian
- lost level control
Devices would show ok and no error in logs. Just won’t work like expected. I did not try to delete the devices and re-add them (yet!). But if I go that route I am moving to local execution with your JSon script.
Any thoughts or suggestions?
Thanks for the heads-up. I checked this AM. Color has to be fixed since GitHub added a Color Selector in the device vice manual hue - saturation entry. Good feature. Just need to fix.
All the other are confirmed to work OK. (Hub or cloud should not make a difference.) Will fix driver and post back when done (hours or less, not days).
1 Like
Just did a full check using the Devices from the Devices Tab against my LB-130 with both Hub and Cloud installation. All worked OK. Note that the design sends the same command to the bulb either via the node applet or Kasa cloud.
I did update the color Driver on GitHub to set the default hue to low resolution. You might want to try that one instead - just in case something is weird.
Some items:
Color. When Hubitat implemented the Color selector, they use the LowRezHue mode. Go to preferences and set lowRezHue.
Color. The default display from GitHub showed an invalid hue/saturation. I had to select a color to update to valid(?????).
SetCircadian - it only sets circadian mode. To leave circadian, do any other function (off-on, level, colorTemp).
Color Temp. Range is 2500 to 9000 for the LB130.
What model bulb do you have. Would be nice to see logs - even if they do not show errors. The logs show the state returned from the bulb.
Dave
Very interesting results. After setting the LowRezHue to lowRezHue the color comes out correctly but now I see another bug with "color name." You will see below that the hue selector I used is green but the color name is orange?? Also the Set Level does nothing.
