Connecting my Intex SPA to openHAB

I own an Intex Spa (HB-20) since a bit more than one year. Tough thing with it, it that you’ve got to take care of it each and every day once filled if you want to be able to use it once the time has come.
Major issues being :

  • water temperature has to be anticipated long enough when you want to use it (IIRW it grows 2°C by hours)
  • water filtration has to be executed very frequently to keep it clean.

As it comes by default, with its local control panel, it is a real pain in the **ss to do on a frequent basis.
So started my searches on Internet.

So did I land on these two forum threads jeedom and domoticz with people having the same questions than me.

I got in touch with PaTiTan who provides modules based on this implementation.

A few days later, I received my module in the mailbox. Connections were really easy. The 3D printed connectors are really perfect and allows a completely removable installation on your SPA without any modification.

I must say that the module is really well packaged and built, and I am comfident it can face exterior conditions, temperatures and humidity.

Three minutes later, the module was online on my wifi network and fully working throught MQTT binding.

Configuration was quite easy with an MQTT thing, here is the YAML :

UID: mqtt:topic:localhost:spa
label: Intex PureSpa SB-H20
thingTypeUID: mqtt:topic
configuration: {}
bridgeUID: mqtt:broker:localhost
location: Terrasse
channels:
  - id: bubble
    channelTypeUID: mqtt:switch
    label: Bulles
    description: ""
    configuration:
      commandTopic: pool/command/bubble
      stateTopic: pool/bubble
      off: off
      on: on
  - id: filter
    channelTypeUID: mqtt:switch
    label: Filtration
    description: ""
    configuration:
      commandTopic: pool/command/filter
      stateTopic: pool/filter
      off: off
      on: on
  - id: heater
    channelTypeUID: mqtt:switch
    label: Chauffage
    description: ""
    configuration:
      commandTopic: pool/command/heater
      stateTopic: pool/heater
      off: off
      on: on
  - id: power
    channelTypeUID: mqtt:switch
    label: Power
    description: ""
    configuration:
      commandTopic: pool/command/power
      stateTopic: pool/power
      off: off
      on: on
  - id: currentTemp
    channelTypeUID: mqtt:number
    label: Température Actuelle
    description: ""
    configuration:
      stateTopic: pool/water/tempAct
      unit: °C
  - id: setpoint
    channelTypeUID: mqtt:number
    label: Température Cible
    description: ""
    configuration:
      commandTopic: pool/command/water/tempSet
      unit: °C
      min: 25
      stateTopic: pool/water/tempSet
      max: 40
  - id: error
    channelTypeUID: mqtt:string
    label: Erreur
    description: ""
    configuration:
      stateTopic: pool/error
  - id: rssi
    channelTypeUID: mqtt:number
    label: RSSI Wifi
    description: ""
    configuration:
      stateTopic: wifi/rssi
      unit: dBm
  - id: wifi_state
    channelTypeUID: mqtt:string
    label: Wifi Status
    description: ""
    configuration:
      stateTopic: wifi/state

In fact, the only thing to take care of was that commands must be emitted in lower case while by default OH pushes in uppercase. This is handled in the YAML configuration.

2 Likes