Plugwise
This enables Plugwise
Platforms available - depending on your Smile and setup include:
-
climate(for the Anna, Jip and Lisa products, or a single Tom) -
button(for the Adam and the non-legacy Anna and P1 gateways) -
sensor(for all relevant products including the Smile P1) -
binary_sensor(for showing the status of e.g. domestic hot water heating or secondary heater) -
switch(for Plugs connected to Adam, or Circles and Stealths connected to a Stretch) -
select(for changing a thermostat schedule, a regulation mode (Adam only)) -
number(for changing a boiler setpoint, Circlesa temperature offset)
The password can be found on the bottom of your Smile or Stretch, the ID, it should consist of 8 characters. To find your IP address use the Plugwise App:
- Open the Plugwise App and choose the ‘Settings’-icon (☰) and choose ‘HTML-interface’.
- Go to the (lower) ‘Settings’-icon (☰) and choose ‘Preferences’.
- Choose ‘System’ then ‘Networking’ and your IP address will be shown.
Entities
This integration will show all Plugwise entities present in your Plugwise configuration. In addition, you will see a ‘Smile’ entity representing your central Plugwise gateway (i.e., the Smile Anna, Smile P1, Adam or Stretch).
For example, if you have an Adam setup with a Lisa named ‘Living’ and a Tom named ‘Bathroom’, these will show up as individual entities. The heating/cooling device connected to your Smile will be shown as ‘OpenTherm’ or ‘OnOff’, depending on how the Smile communicates with the device. If you have Plugs (as in, pluggable switches connecting to an Adam) those will be discovered as switches. Various other measurements of your setup will be available as sensors or as binary sensors.
Centralized measurements such as ‘power’ for a P1, ‘outdoor_temperature’ on Anna or Adam will be assigned to your gateway entity. Heating/cooling device measurements such as ‘boiler_temperature’ will be assigned to the OpenTherm/OnOff entity.
Configuration
The Plugwise Smile(s) present in your network will be automatically detected via Zeroconf discovery and will be shown on the Integrations-page. To set up an integration, click the “CONFIGURATION” button on the discovered integration and you will be presented with a dialog requesting your Smile password. After you click submit, you will have the opportunity to select the area(s) where individual Smile appliances are located. The username smile is shown as a default, when configuring your Stretch change this to stretch accordingly.
Repeat the above procedure for each Smile gateway (i.e., if you have an Adam setup and a P1 DSMR you’ll have to add two integrations).
Please note: when you have an Anna and an Adam, make sure to only configure the Adam integration. You can press the “IGNORE” button on the Anna integration to remove this integration. In case you need to rediscover the Anna integration, make sure to click the “STOP IGNORING” button on the Plugwise integration first, available via “show ignored integrations”.
For a thermostat, the active schedule can be deactivated or reactivated via the climate card. Please note, that when no schedule is active, one must first be activated in the Plugwise App. Once that has been done the Plugwise Integration can manage future operations.
Auto means the schedule is active, Heat means it’s not active. The active thermostat schedule can be changed via the connected thermostat select-entity. Please note: that only schedules that have two or more schedule points will be shown as select options.
Actions
Update Smile data
Forced update of data from your Smile can be triggered by calling the generic homeassistant.update_entity action with your Smile entity as the target.
# Example script change the temperature
script:
force_adam_update:
sequence:
- action: homeassistant.update_entity
target:
entity_id: climate.anna
Reboot the Plugwise gateway
action: button.press
# Example script change the thermostat schedule
script:
reboot_gateway:
sequence:
- action: button.press
target:
entity_id: button.adam_reboot
Set HVAC mode
action: climate.set_hvac_mode
Available options include off (Adam only) auto, cool, heat, and heat_cool (Anna with Elga only).
The meaning of off is that the Adam regulation is set to off. This means that the connected HVAC-system does not heat or cool, only the domestic hot water heating function, when available, is active.
The meaning of cool or heat is that there is no schedule active. For example, if the system is manually set to cooling- or heating-mode, the system will be active if the room temperature is above/below the thermostat setpoint.
The meaning of heat/cool is that there is no schedule active. For example, if the system is in automatic cooling- or heating-mode, the active preset or manually set temperature is used to control the HVAC system.
The meaning of auto is that a schedule is active and the thermostat will change presets/setpoints accordingly.
The last schedule that was active is determined the same way long-tapping the top of Anna works.
Example:
# Example script climate.set_hvac_mode to auto = schedule active
script:
lisa_reactivate_last_schedule:
sequence:
- action: climate.set_hvac_mode
target:
entity_id: climate.lisa_bios
data:
hvac_mode: auto
Turn on / turn off
action: climate.turn_off, climate.turn_on (Adam only)
These actions will switch the Adam regulation mode (= HVAC system mode) to off or on, affecting the operation of all connected thermostats.
climate.turn_on will activate the previously selected heating or cooling mode.
Example:
# Example script climate.turn_off
script:
turn_heating_on:
sequence:
- action: climate.turn_off
target:
entity_id: climate.lisa_bios
Change climate schedule
action: select.select_option
# Example script change the thermostat schedule
script:
lisa_change_schedule:
sequence:
- action: select.select_option
target:
entity_id: select.lisa_bios_thermostat_schedule
data:
option: "Regulier"
Change boiler setpoint
action: number.set_value
# Example script change the boiler setpoint
script:
change_max_boiler_tempeture_setpoint:
sequence:
- action: number.set_value
target:
entity_id: number.opentherm_max_boiler_temperature_setpoint
data:
value: 60
Set temperature
action: climate.set_temperature
Example:
# Example script change the temperature
script:
anna_set_predefined_temperature:
sequence:
- action: climate.set_temperature
target:
entity_id: climate.anna
data:
temperature: 19.5
Set preset mode
action: climate.set_preset_mode
Available options include: home, vacation (Anna only), no_frost, asleep & away.
Example:
# Example script changing the active (or currently set by schedule) preset
script:
anna_activate_preset_asleep:
sequence:
- action: climate.set_preset_mode
data:
preset_mode: asleep
Supported devices
The current implementation of the Python module (Plugwise-Smile) includes:
Adam (zone_control) with On/Off, OpenTherm, and Loria/Thermastage heating and cooling support:
-
v3.x
-
v2.3
-
Devices supported are Anna, Lisa, Jip, Floor, Tom, Plug, Aqara Smart Plug, and Koen (a Koen always comes with a Plug, the active part)
Anna (thermostat) with OnOff, OpenTherm heating, and Elga and Loria/Thermastage with heating and cooling support:
- v4.x
- v3.x
- v1.x
On the Elga, the cooling-mode can only be turned on, or off, via a switch present on the device, not via a toggle in the Plugwise App. Please make sure to reload the Plugwise integration after the cooling-mode-switch is turned off after being on, or the other way around. This will ensure that the Plugwise integration is being adapted to the change in function of the Elga.
Smile P1 (DSMR):
- v4.x
- v3.x
- v2.x
Stretch (power switches):
- v3.x
- v2.x