By JimboMarch 28, in Polyglot. If you have a SmartStrip give it a try. If you have other devices feel free to fork the repo and add it, or let me know and we can work on it as I have time. I have a few plugs I can help test with and integrate. I would but don't have any free time lately, hopefully silmplextech will have time. Sent from my Pixel 3 XL with Tapatalk.
Sorry I haven't even looked at this nodeserver in the last couple weeks. I've gotten busy at work recently and my development work is slacking. Thanks for the quick responses. So as to not hijack this thread, I'll include the details in a new post. Hi Jimbo, just saw you were the developer of the Kasa nodeserver, thank you very much!
I wanted to see if there's been any updates to working with the power plus? I noticed that the pyHS library has support for the following. So figured I'd ask. Right now the nodeserver is on, and a controller is set to True but it didn't find any of my plugs, so I'm going to assume those aren't working, which is fine, just wanted to ask.
Thank you! I installed the Node from Polyglot Cloud but the current status is Disconnected. If I press start it will say "Kasa is already Started". It currently only works for the power strip. Plug support was done by another member and I haven't had time to verify and release those changes.
But you should see it in the admin console so generate a log package from the Polyglot UI and PM that to me. Thanks Jimbo and sorry for the late reply. Looks like I do see the Kasa controller in the admin console so that's working, of course per your note the plug isn't showing up. Still have more device support to add, but I wanted to get the current version out there.
Subscribe to RSS
Please let me know what devices you need supported and I will add when possible. But, most devices should have basic functionality with this version.
Jimbo I installed the Kasa Nodeserver on my Polisy today. I don't see anything in the Read Me about configuration. I assume that discovery is supposed to take care of adding devices. Appreciate any direction you can give me. Ya, the admin console button needs to be fixed, not a big deal. Sorry, I forgot Kasa is not working on Polisy. FreeBSD doesn't allow broadcast of This was next on my list to work on anyway.
Well, I got the nodeserver working quickly in the RPi version and it found the bulb and seemed promising in Polyglot. Did you read the list of supported devices?
Looks like yours is not on of those, I've attempted to add support for ones I do not have, but obviously failed on that one. I have the KL Just posting this in case someone else might have the same problem. After serval minutes everything showed up in the ISY.January 30, Update to Version 2. Changes a. Commonized menus between Hub and Cloud versions. Changed naming conventions to support GitHub integration. Upgrade Recommendation: Do not recommend upgrade unless you need to add device models not in previous baseline.
HS - previous version verified by other users. HS - future product, same control as HS KP - assumed same control as HS HS - assumed same control as HS LB, LB - previous version verified by other users. NEW: HS - awaiting confirmation from user. Both provide control of the devices and energy monitor for capable devices. It was designed, integrated, and tested using what is now called the SmartThings Classic application. If you succeed in installation and running on the new app, Please add comments on this blog.
Old users - do not upgrade to the new SmartThings App until the SmartThings staff says that upgrades are ready. Detailed installation instructions are provided. Update Energy Monitor versions of the device handlers to accommodate devices that maintain more than 31 days of data. I bought it before I pulled the trigger and bought my ST hub.
I would love to give it a try. I have a node. I too purchased a few of these before I decided to go with Smartthings. I saw the limitations immediately after using them for five minutes.
Right now, they work fine with Alexa. I only have three of them. Those lights often get turned on by accident and I use them very rarely. Color Wheel - see if this changes the colors. At the bottom of the wheel page, there are circles. These scroll and provide about 10 pre-set colors.
After setting color, see if Color Temp changes back to non-color light. Brightness works as expected. Hi Dave, I have it set up per your instructions. Works fine for almost all functions. I get an error message and the node server exits when I trigger "off". Attached is the error log.GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together. If nothing happens, download GitHub Desktop and try again.
If nothing happens, download Xcode and try again. If nothing happens, download the GitHub extension for Visual Studio and try again. A significant update to version 4. No added device functionality, so upgrade is purely optional. Added a "upgrade installation" in the smart application to simplify the update process. This new version is designed to upgrade from Versions 1, 2, 3, 3. Kasa Account. Integration via the user's Kasa Account through the Cloud. This uses a Smart Application for installation, device communications, and device management.
Node Applet. Smart Application integration via a home wifi Node. JS bridge pc, fire tablet, android device, Raspberry Pi. The Smart Application is used with user entry of bridge IP to install and manage the devices. Especially useful in the new SmartThings phone app since it allows entry of user preferences via that app.
Launching Xcode If nothing happens, download Xcode and try again.Acknowldegement : To the many HubitatEnvironment, SmartThings, and gitHub users that have contributed to my knowledge and resolution of anomalies - Thanks now and forever. Problems or issues with this integration. If you have problems or issues with this integration, please use this thread to report same. The developers need information on.
Disclaimer: No association with Hubitat This integration is custom code developed by a Hubitat user. It is in no way certified by Hubitat. The developer has fully tested this code within a home environment using available TP-Link and other devices. No significant problems have been found that would impact other integrations; however, the complexity of the Hubitat system does not guarantee some level of adverse interaction in other installations. Hub performance issues : If you have problems or issues with your hub performance, the following steps are suggested, in the following order:.
Just want to post a thanks to Dave. First for being patient enough to deal with a total noobs questions and being very patient about it. Second for jumping on board and saving me any more suffering trying to figure this out.
I saw in the logs that devices this updated every 30 minutes. If someone manually activates it, the status will be synchronized within 30 minutes in Hubitat. However, the "refresh rate" command in the driver does not work. And if we change is parameter. The default 30 minutes refreshing will not work anymore.
Thanks for the feed-back. Actually, Hubitat does not have a Capability Refresh. I added the command in the metadata to keep the ability since the device can be controlled outside Hubitat and SmartThings. I just test. It works per spec after changing frequency. I did find that runEvery1Minute does not work in Hubitat. Poll is not there forgot need. I can add back in where poll does a refresh. Take about 5 minutes to add. Do you want it? The poll add may or may not help your RM functions.
Note that Hubitat does not have the Capability Poll. So if the app is looking for capabilities, it will not work.Now that TP Link Kasa devices have an official integration, let us know what your experiences have been. Note: as of Octoberthe official integration was updated to keep status is in synch, and now turning the device off with, say, echo should cause the status to update with SmartThings as well.
When you report your reviews, please be specific as to the model number you are using and the DTH if it is not just the official out-of-the-box integration. Dave Gutheinz Gutheinz has now deprecated his TP Link community — created integration, and has some more details in that thread. Make a smart lighting routine to control your switch. Make it turn off after power allowance of 1 minute. Edit: Exact same if you use the kasa app. Just the bulbs and the pocket sockets.
So I wonder if that makes a difference. What did smartthings identify it as? Official Integration. I deleted my integration, opened the new phone app. It discovered my TP-Link devices all. Control worked; however, the state did not update as-expected. It seemed to be similar to same problem we had at one time with the classic app. State would update when you went to the details page or back to the devices page.
My Integration. I could not install the app in the new phone app. After installing using the classic phone app, it can be run in the new app to add devices. One good thing - with the energy monitor plugs HS, HS, I was able to get the power and energy to display in the new app it does not in the "official Integration. This required a change in the vid parameter. Works great; including setting CT.Use the brightness channel on the HS with a Switch item can be used to switch the device on and off.
It will not change the brightness value. The default refresh for switch devices is set to 1 second. So it polls the switch for status changes. If you don't use the switch manually often, you can set it to a higher refresh.
The refresh is only relevant to detect manual using the switch. Switching via openHAB activates the switch directly. It is not possible to set the switch state on the Range Extender. This is because it is not known what command to send to the device to make this possible. This can be done using the TP-Link provided mobile app Kasa. Devices can be auto discovered in the same local network as the openHAB application.
It is possible to connect to devices on a different network, but these must be added manually by ipAddress. It is not possible to connect to devices on a different network using deviceId as configuration. The thingId is the product type in lower case. For example HS has thingId hs The thing can be configured by ipAddress or by deviceId. If the one of them is used the other is automatically set by the binding.
When manually configured it is preferred to set the deviceId because if the ip address of the device would change this will be automatically updated. The deviceId is the unique identifier each TP-Link device has.
The deviceId can be seen when using discovery in openHAB. Discovery will set the deviceId automatically. Using a configuration with deviceId depends on the discovery service of the binding.
The binding supports background discovery and this will update the ip address in case it changes within a minute. With background discovery disabled the ip address, which is needed to communicate with the device, needs to be set by starting a manual discovery. It will not update the ip address if background discovery is disabled and the ip address of the device changes. Manually starting a discovery can also be used to set the ip address directly instead of waiting for the 1 minute background discovery refresh period.
This means the channel is prefixed with the group id. The following group ids are available:. When the thing receives a RefreshType command the channel state is updated from an internal cache.Players will first gain access to contemporary technologies that have not been widely applied to real space programs such as nuclear reactors, electrical generators and thermal rockets. By continuing down the CTT tech tree and performing more research, these parts can be upgraded and later surpassed by novel new technologies such as fusion and even antimatter power.
We attempt to portray both the tremendous power of these technologies as well as their drawbacks, including the tremendous difficulty of obtaining resources like antimatter and the difficulties associated with storing it safely.
The goal being to reward players who develop advanced infrastructure on other planets with new, novel and powerful technologies capable of helping Kerbals explore planets in new and exciting ways. Added ignition limitation to Aluminium Hybrid Engine, ignitor can be reloaded at the surface by an engineer. Added Hybrid Wings credits to Charon Moloch which are wings that at the same time can also function as fixed radiator or as a thermal receiver.
Balance: Reduced Power output Dusty Plasma Reactor, which was too powerful compared with other reactors. Fixed Bug with Electric engines not correctly removing previous propellant when switching propellant. Export Downloads.
Whether my Network adapter is compatible with my computer
Export Followers. Export Referrals. Raw stats are from the beginning of time until now. Each follower and download entry represents one hour of data. Uneventful hours are omitted. You'll get emailed updates for this mod. KSP Interstellar Extended. Game Version: 1. Downloads:Author: FreeThinker. Mod Website: Forum Thread.