Intex brand is not involved in any way with this integration.
Please read the license file before use, and the manufacturer documentation.
This component relies on Intex Spa Python package.
It connects to your spa via your local network, and does not rely on the cloud.
This component will set up the following entities:
Platform | Entity | Description | Entity status |
---|---|---|---|
climate |
Spa | Climate controller for water heating | |
switch |
Power | Switch for toggling power state | |
switch |
Bubbles | Switch for toggling bubbles | |
switch |
Jets | Switch for toggling jets | To disable if your spa does not feature jets |
switch |
Filter | Switch for toggling water filtering | |
switch |
Sanitizer | Switch for toggling water electrolysis | To disable if your spa does not feature a sanitizer |
sensor |
Current Temperature | Sensor for current temperature (similar to climate entity 'current_temp' attribute) | Disabled by default |
sensor |
UID | Unique ID of the spa | Disabled by default |
sensor |
Error | Eventual error code and explanation | |
sensor |
Error description | Eventual action to take to solve the error | |
sensor |
Error code | Eventual uppercase error code | Disabled by default |
Installation is done using HACS:
- Go to your Home Assistant instance
- Go to "HACS" tab -> "Integrations" -> Click "+"
- Search for "Intex Spa" -> Select it -> Click "Download with HACS"
Configuration is done via Home Assistant interface.
- Go to your Home Assistant instance
- Go to "Settings" -> "Devices & Services" -> Click "+"
- Search for "Intex Spa" -> Select it
- Fill in the local IP or FQDN of your spa
This integration does not provide additional dashboard cards... Dashboard creation is up to you !
Contributions are welcome :
- If you face an issue
- If you want to translate the integration to your language
- If you want to contribute in any way
...please read the Contribution guidelines.
The versioning of this integration follows Semantic Versioning 2.0.0
Reminder: Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.