mirror of
https://github.com/python-kasa/python-kasa.git
synced 2024-12-23 03:33:35 +00:00
f6fd898faf
* Add DeviceConfig handling * Update post review * Further update post latest review * Update following latest review * Update docstrings and docs
73 lines
2.6 KiB
ReStructuredText
73 lines
2.6 KiB
ReStructuredText
.. py:module:: kasa.modules
|
|
|
|
.. _library_design:
|
|
|
|
Library Design & Modules
|
|
========================
|
|
|
|
This page aims to provide some details on the design and internals of this library.
|
|
You might be interested in this if you want to improve this library,
|
|
or if you are just looking to access some information that is not currently exposed.
|
|
|
|
.. contents:: Contents
|
|
:local:
|
|
|
|
.. _initialization:
|
|
|
|
Initialization
|
|
**************
|
|
|
|
Use :func:`~kasa.Discover.discover` to perform udp-based broadcast discovery on the network.
|
|
This will return you a list of device instances based on the discovery replies.
|
|
|
|
If the device's host is already known, you can use to construct a device instance with
|
|
:meth:`~kasa.SmartDevice.connect()`.
|
|
|
|
The :meth:`~kasa.SmartDevice.connect()` also enables support for connecting to new
|
|
KASA SMART protocol and TAPO devices directly using the parameter :class:`~kasa.DeviceConfig`.
|
|
Simply serialize the :attr:`~kasa.SmartDevice.config` property via :meth:`~kasa.DeviceConfig.to_dict()`
|
|
and then deserialize it later with :func:`~kasa.DeviceConfig.from_dict()`
|
|
and then pass it into :meth:`~kasa.SmartDevice.connect()`.
|
|
|
|
|
|
.. _update_cycle:
|
|
|
|
Update Cycle
|
|
************
|
|
|
|
When :meth:`~kasa.SmartDevice.update()` is called,
|
|
the library constructs a query to send to the device based on :ref:`supported modules <modules>`.
|
|
Internally, each module defines :meth:`~kasa.modules.Module.query()` to describe what they want query during the update.
|
|
|
|
The returned data is cached internally to avoid I/O on property accesses.
|
|
All properties defined both in the device class and in the module classes follow this principle.
|
|
|
|
While the properties are designed to provide a nice API to use for common use cases,
|
|
you may sometimes want to access the raw, cached data as returned by the device.
|
|
This can be done using the :attr:`~kasa.SmartDevice.internal_state` property.
|
|
|
|
.. _modules:
|
|
|
|
Modules
|
|
*******
|
|
|
|
The functionality provided by all :class:`~kasa.SmartDevice` instances is (mostly) done inside separate modules.
|
|
While the individual device-type specific classes provide an easy access for the most import features,
|
|
you can also access individual modules through :attr:`kasa.SmartDevice.modules`.
|
|
You can get the list of supported modules for a given device instance using :attr:`~kasa.SmartDevice.supported_modules`.
|
|
|
|
.. note::
|
|
|
|
If you only need some module-specific information,
|
|
you can call the wanted method on the module to avoid using :meth:`~kasa.SmartDevice.update`.
|
|
|
|
|
|
API documentation for modules
|
|
*****************************
|
|
|
|
.. automodule:: kasa.modules
|
|
:noindex:
|
|
:members:
|
|
:inherited-members:
|
|
:undoc-members:
|