Control TP-Link Kasa smart outlets/plugs
- Quick Start
- Prerequisites
- Installation
- Configuration
- Commands
- Exceptions
- Supporting additional devices
- References
using Kasa;
using IKasaOutlet kasa = new KasaOutlet("192.168.1.100");
if (!await kasa.System.IsOutletOn()) {
await kasa.System.SetOutletOn(true);
}- A Kasa smart outlet
- Verified devices:
- Other similar devices may also work if they have the same API, such as the HS103, HS105, KP100, KP115, or EP25
- See Supporting additional devices if your device is not supported
- Any .NET runtime that supports .NET Standard 2.0 or later:
You can install this library into your project from NuGet Gallery:
dotnet add package KasaInstall-Package Kasa- Go to Project › Manage NuGet Packages in Visual Studio and search for
Kasa
- Connect your Kasa device to your wi-fi network.
- You can do this with the Kasa Smart app for Android or iOS.
- Get your device's hostname.
- You can find its IP address in your router's client or DHCP lists. The MAC address will match the one printed on the device and shown in Device Info in the Kasa Smart app.
- You can also scan for servers exposing TCP port 9999.
nmap --open -pT:9999 192.168.1.0/24
- You can also use its FQDN if you assigned one using a DNS A record.
- Construct a new
KasaOutletinstance in your project, passing the device's hostname as a constructor parameter.using IKasaOutlet kasa = new KasaOutlet(hostname: "192.168.1.100");
IKasaOutlet instances can be reused to send multiple commands over the lifetime of your application. You can add one to your dependency injection context and retain it for as long as you like. Remember to Dispose() it when you're done using it, so that it can tear down the TCP socket.
The KasaOutlet instance will try to transparently handle the TCP connection for you. It will automatically lazily ensure the TCP socket is connected to the Kasa device's server before sending any commands.
If the connection drops, for example if the device reboots, it will automatically attempt to reconnect multiple times before sending the next command, with a delay between attempts. The number of attempts and delay duration can be adjusted using the options below. If all reconnections fail, it will throw a NetworkException (see Exceptions below).
Optionally, you may manually eagerly connect before sending any commands, if you want to connect early to test the connection or ensure lower latency for the first command:
await kasa.Connect();You can customize the KasaOutlet instance by setting optional properties to control logging, timeouts, and retries.
using IKasaOutlet kasa = new KasaOutlet(hostname: "192.168.1.100", new Options {
LoggerFactory = loggerFactory,
MaxAttempts = 20,
RetryDelay = TimeSpan.FromSeconds(1),
SendTimeout = TimeSpan.FromSeconds(2),
ReceiveTimeout = TimeSpan.FromSeconds(2)
});This library will emit log messages at the Debug level when it connects and disconnects from the Kasa device's TCP server. It will also emit Trace messages with the raw, stringified JSON objects sent and received on the TCP socket.
Microsoft.Extensions.Logging.ILoggerFactory instances can be injected from an ASP.NET Core Builder or .NET Generic Host Builder, or created manually.
var builder = WebApplication.CreateBuilder(args);
builder.Services.AddSingleton<IKasaOutlet>(services => new KasaOutlet("192.168.1.100", new Options {
LoggerFactory = services.GetRequiredService<ILoggerFactory>()
}));{
"Logging": {
"LogLevel": {
"Default": "Information",
"Kasa": "Trace"
}
}
}Host.CreateDefaultBuilder(args).ConfigureServices(services => {
services.AddSingleton<IKasaOutlet>(s => new KasaOutlet("192.168.1.100", new Options {
LoggerFactory = s.GetRequiredService<ILoggerFactory>()
}));
});{
"Logging": {
"LogLevel": {
"Default": "Information",
"Kasa": "Trace"
}
}
}ILoggerFactory loggerFactory = LoggerFactory.Create(builder => builder
.AddFilter("Kasa", LogLevel.Trace)
.AddConsole());
using IKasaOutlet kasa = new KasaOutlet("192.168.1.100", new Options {
LoggerFactory = loggerFactory
});You can also adapt other logging providers, such as NLog, to consume the logs produced by Kasa.KasaOutlet.
ConsoleTarget consoleLog = new();
LoggingConfiguration nlogConfig = new();
nlogConfig.AddRule(NLog.LogLevel.Trace, NLog.LogLevel.Fatal, consoleLog);
LogManager.Configuration = nlogConfig;
ILoggerFactory loggerFactory = LoggerFactory.Create(builder => builder
.ClearProviders()
.AddNLog());
using IKasaOutlet kasa = new KasaOutlet("192.168.1.100", new Options {
LoggerFactory = loggerFactory,
});All commands are asynchronous, so you should await the returned Task to get the result.
More information about each command, including the parameters accepted and data returned, is available in their class and method comments.
Commands that get or set system properties, like status, name, and whether the outlet is on or off.
Get whether the outlet on the device is energized and can supply power to any connected electrical consumers or not.
This is unrelated to whether the entire Kasa device is running. If you can connect to it, it's running.
bool isOn = await kasa.System.IsOutletOn();
Console.WriteLine($"Is on: {isOn}");Is on: true
Turn on or off the device's outlet so it can supply power to any connected electrical consumers or not.
You can also toggle the outlet by pressing the physical button on the device.
This call is idempotent: if you try to turn the outlet on and it's already on, the call will have no effect.
The state is persisted across restarts. If the device loses power, it will restore the previous outlet power state when it turns on again.
This call is unrelated to turning the entire Kasa device on or off. To reboot the device, use Reboot.
await kasa.System.SetOutletOn(true);The name or alias of the device that you chose during setup.
string name = await kasa.System.GetName();
Console.WriteLine($"Name: {name}");Name: Washing Machine
Change the alias of this device. This will appear in the Kasa mobile app.
await kasa.System.SetName("My Outlet");Get data about the device, including hardware, software, configuration, and current state.
SystemInfo systemInfo = await kasa.System.GetInfo();
Console.WriteLine($"Operating mode: {systemInfo.OperatingMode}");
Console.WriteLine($"Model name: {systemInfo.ModelName}");
Console.WriteLine($"Model family: {systemInfo.ModelFamily}");
Console.WriteLine($"Signal strength: {systemInfo.SignalStrength} dBm");
Console.WriteLine($"Features: {string.Join(", ", systemInfo.Features)}");
Console.WriteLine($"MAC address: {systemInfo.MacAddress}");
Console.WriteLine($"Device ID: {systemInfo.DeviceId}");
Console.WriteLine($"Updating: {systemInfo.Updating}");
Console.WriteLine($"Software version: {systemInfo.SoftwareVersion}");
Console.WriteLine($"Hardware version: {systemInfo.HardwareVersion}");
Console.WriteLine($"Hardware ID: {systemInfo.HardwareId}");
Console.WriteLine($"OEM ID: {systemInfo.OemId}");Operating mode: Schedule
Model name: EP10(US)
Model family: Smart Wi-Fi Plug Mini
Signal strength: -49 dBm
Features: Timer
MAC address: 5CA6E64EF3EF
Device ID: 8006C153CFEBDE93CD3572549B5A47611F49F0D2
Updating: False
Software version: 1.0.2 Build 200915 Rel.085940
Hardware version: 1.0
Hardware ID: AE6865C67F6A54B756C0B5812472C825
OEM ID: 41372DE62C896B2C0E93C20D70B62DDB
Outlets have a physical status light (usually a blue LED) that shows whether they are supplying power to consumers or not.
This light can be disabled even when the outlet is on, for example if it's annoyingly bright in a room where you're trying to watch a movie or go to sleep.
By default, this returns true, and the light will turn on if and only if the outlet is supplying power.
bool isIndicatorLightOn = await kasa.System.IsIndicatorLightOn();
Console.WriteLine($"Is indicator light on: {isIndicatorLightOn}");Is indicator light on: true
Outlets have a physical status light that shows whether they are supplying power to consumers or not.
This light can be disabled even when the outlet is on, for example if it's annoyingly bright in a room where you're trying to watch a movie or go to sleep.
When you set this to true (the default value), the light will turn on if and only if the outlet is supplying power. When you set this to false, the light will never turn on, regardless of whether the outlet is supplying power. This setting is persistent, so if you want the light to always be off, you don't need to call SetIndicatorLightOn(false) every time you call SetOutletOn(true).
Even when you set this to false, the light will still blink for a few seconds while the outlet is booting up before turning the light off.
await kasa.System.SetIndicatorLightOn(true);Restart the device.
Rebooting will interrupt power to any connected consumers for roughly 108 milliseconds. It takes about 8 seconds for a KP125 to completely reboot and resume responding to API requests, and about 14 seconds for an EP10.
The existing outlet power state will be retained after rebooting, so if it was on before rebooting, it will turn on again after rebooting, and there is no need to explicitly call SetOutletOn to reestablish the previous state.
By default, this client will automatically reconnect to the outlet after it reboots, which can be tuned using the MaxAttempts and RetryDelay properties.
await kasa.System.Reboot(TimeSpan.FromSeconds(5));Commands that deal with the device's internal clock that keeps track of the current date and time.
This is unrelated to schedules and timers that control when the outlet turns on or off, see Timer.
Get the current local time from the device's internal clock.
DateTime time = await kasa.Time.GetTime();
Console.WriteLine($"Device time: {time:F}");Device time: Saturday, June 11, 2022 3:48:21 am
Get the current time and time zone from the device's internal clock.
DateTimeOffset dateTime = await kasa.Time.GetTimeWithZoneOffset();
Console.WriteLine($"Device time: {dateTime:O}");Device time: 2022-06-11T03:56:03.0000000-07:00
Get a list of possible time zones that the device is in.
This may return multiple possibilities instead of one time zone because, unfortunately, Kasa devices internally represent multiple time zones with non-unique identifiers.
For example, Central Standard Time is unambiguously stored as 13 on the Kasa device, so this method will only return that time zone.
However, Eastern Standard Time is stored as 18 on the Kasa device, which collides with 18 that it also uses to represent Eastern Standard Time (Mexico), Turks and Caicos Standard Time, Haiti Standard Time, and Easter Island Standard Time, so this method will return all five possibilities since they cannot be distinguished based on the information provided by the device.
IEnumerable<TimeZoneInfo> timeZones = await kasa.Time.GetTimeZones();
Console.WriteLine($"Device time zone may be {string.Join(" or ", timeZones.Select(zone => zone.Id))}");Device time zone may be Yukon Standard Time or Pacific Standard Time
Configure the device to use a specific time zone.
await kasa.Time.SetTimeZone(TimeZoneInfo.Local);Countdown timers allow you to schedule the outlet to turn on or off once after a delay of configurable duration.
Outlets can handle at most one timer at once.
This is unrelated to the current time of the device's internal clock, see Time.
Get the currently running countdown timer rule on the device, along with its updated RemainingDuration.
There can be either 0 or 1 timers on the device at once; multiple timers are not possible.
If no timer has ever been created, it already elapsed, or you deleted it with Clear, this method will return null.
if(await outlet.Timer.Get() is { } timer){
Console.WriteLine($"Outlet will turn {(timer.SetOutletOnWhenComplete ? "on" : "off")} in {timer.RemainingDuration.TotalSeconds:N1} seconds.");
} else {
Console.WriteLine("No timer running.");
}Outlet will turn on in 9.3 seconds.
Save a new, enabled countdown timer to the device.
There can be at most one timer on the device at once, so any existing timers will first be deleted, even if they had not elapsed yet.
The created timer will be returned, which is useful if you want to inspect the newly-populated RemainingDuration property.
Timer timer = await outlet.Timer.Start(TimeSpan.FromMinutes(30), true);
Console.WriteLine($"Outlet will turn {(timer.SetOutletOnWhenComplete ? "on" : "off")} in {timer.RemainingDuration.TotalSeconds:N1} seconds.");Outlet will turn on in 1,800.0 seconds.
Delete any existing timer rule from the device, cancelling its countdown.
This will cause Get to return null until you Start a new timer.
Idempotent: this will succeed even if there are no timers to delete.
await outlet.Timers.Clear();Commands that deal with schedules.
Schedules allow you to set the outlet to turn on or off once on a specific date and time, or on multiple days with a weekly recurrence pattern. Times can be relative to the start of the day, sunrise, or sunset.
Fetch all of the existing schedules from the outlet.
IEnumerable<Schedule> schedules = await outlet.Schedule.GetAll();
foreach (Schedule s in schedules) {
string time = s.TimeBasis switch {
Schedule.Basis.StartOfDay => TimeOnly.FromTimeSpan(s.Time).ToString(),
Schedule.Basis.Sunrise => $"{s.Time:%m} min {(s.Time < TimeSpan.Zero ? "before" : "after")} sunrise",
Schedule.Basis.Sunset => $"{s.Time:%m} min {(s.Time < TimeSpan.Zero ? "before" : "after")} sunset"
};
Console.WriteLine($"Turn {(s.WillSetOutletOn ? "on " : "off")} at {time} on {(s.IsRecurring ? string.Join(", ", s.DaysOfWeek) : s.Date)}{(s.IsEnabled ? "" : " (disabled)")}");
}Turn on at 19:45 on Tuesday, Wednesday, Thursday
Turn off at 23:45 on Monday, Tuesday, Wednesday, Thursday
Turn on at 18:45 on Monday
Persist a schedule to the outlet.
To insert a new schedule, construct a new Schedule instance, leaving its Schedule.Id property null. After saving it with this method, the returned instance will be a copy with the Schedule.Id value populated.
To update an existing schedule, retrieve it using GetAll, make any changes you like, then save it with this method.
Schedule schedule = new(true, new[] { DayOfWeek.Tuesday, DayOfWeek.Wednesday, DayOfWeek.Thursday }, new TimeOnly(12 + 7, 45));
schedule = await outlet.Schedule.Save(schedule);
Console.WriteLine($"Created schedule with ID {schedule.Id}");Created schedule with ID 0D3D1C778103039FEBCAB23C261AD821
Remove an existing schedule from the outlet.
You can pass an existing Schedule instance or just its Id.
Schedule schedule = (await outlet.Schedule.GetAll()).First();
await outlet.Schedule.Delete(schedule);await outlet.Schedule.Delete("0D3D1C778103039FEBCAB23C261AD821");Clear all existing schedules from the outlet.
await outlet.Schedule.DeleteAll();Commands that deal with the energy meter present in some Kasa devices, such as the EP25, KP125, and KP115.
To determine if your device has an energy meter, you can call:
bool hasEnergyMeter = (await kasaOutlet.System.GetInfo()).Features.Contains(Feature.EnergyMeter);Fetch a point-in-time measurement of the instantaneous electrical usage of the outlet.
The returned PowerUsage struct has Current (mA), Voltage (mV), Power (mW) fields. There is also a CumulativeEnergySinceBoot (W⋅h) field that shows how much total energy has been used since the Kasa device last booted, and which resets to 0 when the device reboots, loses power, or has DeleteHistoricalUsage called on it.
PowerUsage usage = await kasa.EnergyMeter.GetInstantaneousPowerUsage();
Console.WriteLine($"Attached consumer is currently using {usage.Current:N0} mA, {usage.Voltage / 1000.0:N3} V, and {usage.Power:N0} mW.");
Console.WriteLine($"It has used {usage.CumulativeEnergySinceBoot / 1000.0:N3} kWh since the Kasa device last booted.");Attached consumer is currently using 0 mA, 123.069 V, and 0 mW.
It has used 0.433 kWh since the Kasa device last booted.
For a given month and year, fetch a historical report of cumulative energy usage, grouped by day and aligned to the start of the day (midnight).
The returned array has one entry for each day in the given month, and the days are 0-indexed (the first day of the month is located at index 0). The array values are in watt-hours.
These data persist on the device across power loss and reboots; to reset them, call DeleteHistoricalUsage.
DateTimeOffset now = DateTimeOffset.Now;
if (await kasa.EnergyMeter.GetDailyEnergyUsage(now.Year, now.Month) is { } days) {
int monthStart = (int) new DateTime(now.Year, now.Month, 1).DayOfWeek;
Console.Write(string.Join(null, Enumerable.Repeat(" | ", monthStart)));
for (int day = 0; day < days.Count; day++) {
int usage = days[day];
DateTime date = new(now.Year, now.Month, day + 1);
Console.Write($"{date,2:%d}: {usage,3:N0} Wh{(day % 7 == monthStart ? "\n" : " | ")}");
}
Console.WriteLine();
} else {
Console.WriteLine("No energy data for the given month and year");
} | | | 1: 23 Wh | 2: 24 Wh | 3: 23 Wh | 4: 188 Wh
5: 481 Wh | 6: 8 Wh | 7: 7 Wh | 8: 8 Wh | 9: 8 Wh | 10: 12 Wh | 11: 22 Wh
12: 22 Wh | 13: 23 Wh | 14: 24 Wh | 15: 23 Wh | 16: 24 Wh | 17: 23 Wh | 18: 24 Wh
19: 181 Wh | 20: 7 Wh | 21: 8 Wh | 22: 7 Wh | 23: 2 Wh | 24: 0 Wh | 25: 0 Wh
26: 0 Wh | 27: 0 Wh | 28: 0 Wh | 29: 0 Wh | 30: 0 Wh | 31: 0 Wh |
For a given year, fetch a historical report of cumulative energy usage, grouped by month.
The returned array has 12 entries for each month in the given year, and the months are 0-indexed (January is located at index 0). The array values are in watt-hours.
These data persist on the device across power loss and reboots; to reset them, call DeleteHistoricalUsage.
DateTimeOffset now = DateTimeOffset.Now;
if (await kasa.EnergyMeter.GetMonthlyEnergyUsage(now.Year) is { } months) {
for (int month = 0; month < 12; month++) {
int usage = months[month];
DateTime date = new(now.Year, month + 1, 1);
Console.Write($"{date:MMM}: {usage,5:N0} Wh{(month % 3 == 2 ? "\n" : " | ")}");
}
} else {
Console.WriteLine("No energy data for the given year");
}Jan: 797 Wh | Feb: 1,020 Wh | Mar: 1,172 Wh
Apr: 0 Wh | May: 0 Wh | Jun: 0 Wh
Jul: 0 Wh | Aug: 0 Wh | Sep: 0 Wh
Oct: 0 Wh | Nov: 0 Wh | Dec: 0 Wh
Clear all energy usage data for all days, months, and years, and begin gathering new data from a fresh start.
After calling this method, subsequent calls to GetDailyEnergyUsage will return null for past months, and the current month's data will be reset to 0. Subsequent calls to GetMonthlyEnergyUsage will similarly return null for past years, and the current year's data will be reset to 0. Since these are not reset on power loss or reboot, this DeleteHistoricalUsage method is the only way to reset these.
In addition, subsequent calls to GetInstantaneousPowerUsage will return 0 for CumulativeEnergySinceBoot, just like a reboot, although it will not affect the point-in-time, non-historical measurements Current, Voltage, and Power.
await kasa.EnergyMeter.DeleteHistoricalUsage();All known exceptions thrown by this library are documented in the comments of each method.
Each command can throw two main exceptions:
NetworkExceptionif the TCP socket connection failed and could not be automatically recovered. Check the innerSocketExceptionorIOExceptionfor the cause.ResponseParsingExceptionif the TCP server returned JSON that could not be deserialized, possibly because the API changed or the device is unsupported.
If you try to run a command on an outlet that doesn't support it, it will throw a FeatureUnavailable exception, for example, if you try to retrieve the energy usage of an EP10 outlet which doesn't have an energy meter. You can check the RequiredFeature property of the exception to see which Feature was required, and you can call IKasaOutlet.System.GetInfo() and check the contents of the returned SystemInfo struct's Features set to see which features your outlet offers.
Some methods also throw other exceptions in specific cases, such as ArgumentOutOfRangeException or TimeZoneNotFoundException. Check the <exception> XML documentation comments for each method, or use an exception checker tool like Exception Analyzers 2022.
If you want this library to support more Kasa smart outlets, then you may help me buy the hardware to develop, test, and document those integrations with Amazon wishlist gifts or PayPal donations (you can specify a funding goal in the donation description).
| Image | Name | Outlets | Weatherproofing | Form factor | Cost |
|---|---|---|---|---|---|
 |
KP303 | 3 | Indoor | Strip | $23 USD |
 |
HS300 | 6 | Indoor | Strip | $43 USD |
- tplink-smarthome-commands.txt — Lubomir Stroetmann and Tobias Esser
- Reverse Engineering the TP-Link HS110 — Lubomir Stroetmann and Tobias Esser
- Controlling the TP-LINK HS100 Wi-Fi smart plug — George Georgovassilis, Thomas Baust
- python-kasa
- Pi Projects — Pablo Meier
- THLaundry — Ben Hutchison, Robert Mustacchi
- homebridge-tplink-smarthome#202 — the1maximus
- KasaLink — mguinness
- kasasock — Brian English
- Home Assistant
- tplink-smarthome-simulator — Patrick Seal