Releases: mihai-dinculescu/tapo
Releases · mihai-dinculescu/tapo
Tapo Rust v.0.7.13
Changed
- To align with the latest API updates, the
overheated
field for plugs has been replaced by three enums:overcurrent_status
,overheat_status
, andpower_protection_status
(thanks to @padenot).
Tapo Python v0.3.2
Changed
- To align with the latest API updates, the
overheated
field for plugs has been replaced by three enums:overcurrent_status
,overheat_status
, andpower_protection_status
.
Tapo Rust v.0.7.12
Changed
- H100's create child device handler methods now take a
HubDevice
enum
instead of aString
and are nowasync
to allow for more flexibility. This enables the caller to find child devices by either device ID or nickname. PlugIdentifier
has been renamed toPlug
.Plug::ByDeviceId
now verifies that the provided device ID is found and returns anError::DeviceNotFound
error when it's not.HubDevice
variants now take aString
instead of a&str
to allow for more flexibility.Plug
variants now take aString
instead of a&str
to allow for more flexibility.
Fixed
ColorLightSetDeviceInfoParams
hue
field validation has been changed frombetween 1 and 360
tobetween 0 and 360
to match the device's expected range.- Fixed an issue where the
EnergyDataResult's
start_timestampand
end_timestamp` did not correctly adjust for timezone offsets. - The
chrono
dependency has been updated to0.4.34
to fix the minimum version requirement.
Removed
- The
overheated
property has been removed fromDeviceInfoGenericResult
because it's not present in the response of all devices.
Tapo Python v0.3.1
Fixed
ColorLightSetDeviceInfoParams
hue
field validation has been changed frombetween 1 and 360
tobetween 0 and 360
to match the device's expected range.- Fixed an issue where the
EnergyDataResult's
start_timestampand
end_timestamp` did not correctly adjust for timezone offsets. - All handlers are now correctly exported and can be imported from the
tapo
module.
Removed
- The
overheated
property has been removed fromDeviceInfoGenericResult
because it's not present in the response of all devices.
Tapo Rust v.0.7.11
Added
- Added support for the P300 power strip (thanks to @Michal-Szczepaniak).
RgbLightStripHandler
andDeviceInfoRgbLightStripResult
have been added to support the L900 devices separately from the L530 and L630 devices.
Changed
ChildDeviceResult
has been renamed toChildDeviceHubResult
to facilitate adding support for other devices with children.ColorLightStripHandler
has been renamed toRgbicLightStripHandler
to better reflect its purpose.DeviceInfoColorLightStripResult
has been renamed toDeviceInfoRgbicLightStripResult
to better reflect its purpose.
Tapo Python v0.3.0
Added
- Added partial support for the H100 hub and its child devices. Currently, only the
get_device_info
function is supported for the child devices through the hub'sget_child_device_list
method.
Changed
- A large number of types have been reorganized to me more in line with the Rust library. This includes moving many of them under the
requests
andresponses
sub modules.
Removed
l900
has been removed from theApiClient
until proper support is added.
Tapo Rust v.0.7.10
Changed
- The implementation of
ApiClient::new
has been improved to allow for the return ofApiClient
instead ofResult<ApiClient, Error>
. - The default timeout for all requests has been reduced to 30 seconds from 300 seconds.
ApiClient::with_timeout
has been added to allow for the setting of a custom timeout for all requests (thanks to @skoky).
Tapo Python v0.2.1
Changed
- The default timeout for all requests has been reduced to 30 seconds from 300 seconds.
- The
timeout_s
optional parameter has been added to theApiClient
constructor to allow for the setting of a custom timeout for all requests (thanks to @skoky).
Tapo Rust v.0.7.9
Changed
- The
send()
method of the.set()
API now takes a reference to the device handler in order to allow for better ergonomics.
Fixed
- The device info response for the L510, L520, and L610 devices has been fixed.
Tapo Python v0.2.0
Added
- Added support for the L530, L630, and L900 color light bulbs.
Fixed
- Fixed a misconfiguration that was preventing the sdist package from working properly.
- The device info response for the L510, L520, and L610 devices has been fixed.