tapo-py: Properly export all handlers

Addresses #218.

CHANGELOG.md

@@ -14,6 +14,10 @@ file. This change log follows the conventions of
 
 ## [Python Unreleased][Unreleased]
 
+### Fixed
+
+- All handlers are now correctly exported and can be imported from the `tapo` module.
+
 ## [Rust v0.7.11][v0.7.11] - 2024-05-04
 
 ### Added
@@ -31,7 +35,7 @@ file. This change log follows the conventions of
 
 ### Added
 
-- Added partial support for the H100 hub and it's child devices. Currently, only the `get_device_info` function is supported for the child devices through the hub's `get_child_device_list` method.
+- 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's `get_child_device_list` method.
 
 ### Changed
 

tapo-py/src/lib.rs

@@ -5,7 +5,11 @@ mod handlers;
 use pyo3::prelude::*;
 
 use api_client::PyApiClient;
-use handlers::{PyColorLightSetDeviceInfoParams, PyEnergyDataInterval};
+use handlers::{
+    PyColorLightHandler, PyColorLightSetDeviceInfoParams, PyEnergyDataInterval,
+    PyGenericDeviceHandler, PyHubHandler, PyLightHandler, PyPlugEnergyMonitoringHandler,
+    PyPlugHandler,
+};
 use tapo::requests::Color;
 use tapo::responses::{
     ColorLightState, CurrentPowerResult, DefaultBrightnessState, DefaultColorLightState,
@@ -21,6 +25,12 @@ use tapo::responses::{
 #[pyo3(name = "tapo")]
 fn tapo_py(py: Python, module: &Bound<'_, PyModule>) -> PyResult<()> {
     module.add_class::<PyApiClient>()?;
+    module.add_class::<PyColorLightHandler>()?;
+    module.add_class::<PyGenericDeviceHandler>()?;
+    module.add_class::<PyHubHandler>()?;
+    module.add_class::<PyLightHandler>()?;
+    module.add_class::<PyPlugEnergyMonitoringHandler>()?;
+    module.add_class::<PyPlugHandler>()?;
 
     let requests = PyModule::new_bound(py, "tapo.requests")?;
     let responses = PyModule::new_bound(py, "tapo.responses")?;