AsWaM's home assistant configuration This is a work in progress, not a tutorial. Happy if it helps.
Using Hass.io (tried Jeedom, Hass OS, and dockered installation)
-
The full front end config can be found in the lovelace.yaml file.
-
The Picture Elements details overview floorplan and living room interactive are available as separate files
-
Automations: automations.yaml
-
Scripts: scripts.yaml
-
Configuration: configuration.yaml
-
Groups: groups.yaml
-
Sensors: sensors.yaml
-
Switches: switches.yaml
-
Customizations: customize.yaml
-
Booleans: input_boolean.yaml
-
Numbers: input_numbers.yaml
-
Dropdowns: input_select.yaml
Below a few screenshots of how it looks like (wip)
Except the furniture, everything is clickable or actionable
Live demo (YouTube)
Yaml configuration
All the lights and the tv are actionable
Live demo (YouTube)
Yaml configuration
- Add motors to the Rolle Shutters and integrate them
Add a Tado smart TRV in the bathroom--> Done
- Tado smart TRVs (x5) + Tado Gateway
- Template (for sensor batteries, average temperature, turned on lights etc...)
- History (Already cleaned today, Sonnzed notification, ect)
- Google Calendar
- Telegram
- Synology, custom python script to trigger home/away mode
- Foscam FI9821P
- Xiaomi dafang with EliasKotlyar Xiaomi-Dafang-Hacks custom Firmware
- Eufy Security cam V2 (not integrated yet)
- bluetooth device tracker
Tado GeoFenceDesactivated that, prevents you to remotely turn the heating on- Could not get the NUT ble tracker to work (ble_device_tracker)
- Xiaomi Gateway V2
- Xiaomi Temperature and Humidity Sensor (x9) both v1 and v2
- Xiaomi Window/Door Sensor (x6) both v1 and v2
- Xiaomi Motion Sensor (x5) both v1 and v2
- Xiaomi Bed Activity Sensor (currently unused)
- Xiaomi Smart Button (x3) both v1 and v2
- Xiaomi Magic Cube (x2)
- Xiaomi Smart Plug (x3)
- Sonoff T2 EU 1CH (x4) with arendst Tasmota Custom Firmware
- Sonoff T2 EU 2CH (x3) with arendst Tasmota Custom Firmware
- LG TV
- Mi flora (x2)
- YR.no
- DarkSky
- Yeelight RGB Bulb (x6) both v1 and v2
- YeeLight RGB Led Strip (x3) both v1 and v2
- Yeelight BedSide Lamp (v2)
- Xiaomi Philips BedSide Lamp
- Broadlink RM Plus
- Roborock S50 Vacuum cleaner
- Garadget
- Google cloud backup
- Tasmota Admin
- Mosquito Broker
- FritzBox 6190 Cable
- Xiaomi Mi Router 3G with OpenWRT LuCi
- Synology NAS DS218+
- Raspberry Pi 4B
Originally, (pre-lovelace) this was used for both display and use of multiple sensors/automations/lights etc together. Now, with lovelace, the display is useless, but still here for automations, sums, etc
All this can be found in the dedicated file groups.yaml
The magic about that, is that the group is 'home' if any of the trackers is 'home' and is 'not_home' if nobody is in the house. So the group is actually 'anyone home?' it switches to 'home' when the first person comes, and switches to 'not_home' when the last departs, which is just perfect for automations
tracked_devices:
name: Tracked devices
entities:
- device_tracker.qcombtd
- device_tracker.samsungsmg920f
- device_tracker.galaxy_s8
- device_tracker.lia
The magic about that, is that if any goes from 'off' to 'on' the the whole group goes from 'off' to 'on', so you can trigger an automation if any of them is triggered, and if you add a new one, just add it to the group and it is intergrated to automations automatically
The list here is not exhaustive, have a look a the groups.yaml file
Motion sensors inside the house
motion_sensors:
name: Mouvement intérieur
entities:
- binary_sensor.motion_sensor_158d0001e47f52
- binary_sensor.motion_sensor_158d0001e47d34
- binary_sensor.motion_sensor_158d0001ddca38
- binary_sensor.motion_sensor_158d0001b7542d
- binary_sensor.motion_sensor_158d0001d6675f
Open closed sensor on doors
door_sensors:
name: Ouvertures Portes
entities:
- binary_sensor.door_window_sensor_158d0001ab1b67
- binary_sensor.door_window_sensor_158d0001ab5aaa
- binary_sensor.door_window_sensor_158d0001d8526a
- binary_sensor.door_window_sensor_158d000272f13c
These groups help for the averages
room_humidity:
name: Humidité Maison
entities:
- sensor.humidity_158d0001b96127
- sensor.humidity_158d0001b92bcc
- sensor.humidity_158d0001b8f1b1
- sensor.humidity_158d00022734f8
room_temperature:
name: Température Maison
entities:
- sensor.temperature_158d0001b96127
- sensor.temperature_158d0001b92bcc
- sensor.temperature_158d0001b8f1b1
- sensor.temperature_158d00022734f8
These groups allow to control several lights simultaneously
light_salon:
name: Salon
entities:
- light.yeelight_color1_34ce008fcea8
- light.yeelight_color1_34ce00900013
- light.yeelight_color1_7811dc6aaca4
- light.yeelight_strip1_7811dca22953
And of course groups of groups
all_open_sensors:
name: Tous capteurs ouverture
entities:
- group.door_sensors
- group.window_sensors
Allows to deactivate the automations not "supported" by the wife when she is at home, and reactivate them the rest of the time
non_waf:
name: Non WAF scenarios
entities:
- automation.allumage_sdb_auto
- automation.extinction_sdb_auto
- automation.allumage_couloir_auto
- automation.extinction_couloir_auto
- automation.changement_lumieres_a_6h_et_20
- automation.changement_lumieres_a_7h_et_19h
- automation.changement_lumieres_a_9h_et_17h
- automation.changement_lumieres_a_22h
- automation.changement_lumieres_a_23
All the automations can be found in the dedicated file automations.yaml
The Kitchen button toggles the light of the worktop (smart plug + yeelight ledstrip), and turns off the night mode (usually, when I get up, I pour a cofee and need to light up the worktop for this)
# Toggle le led strip et la prise lors de l'appui du bouton cuisine + Exit night mode
- alias: Bouton Cuisine
id: switch.cuisine
trigger:
platform: event
event_type: xiaomi_aqara.click
event_data:
click_type: single
entity_id: binary_sensor.switch_158d0001e18d90
condition: []
action:
- service: light.toggle
entity_id: light.yeelight_strip1_7811dc66e549
- service: switch.toggle
entity_id: switch.plug_158d0001de56c2
- service: input_boolean.turn_off
entity_id: input_boolean.mode_nuit
Some other buttons, for example in the kids room allow to control the room lamp from the bed (main lamp, and desk led strip)
# Chambre Doudou
# Toggle la lampe principale lors de l'apuui du bouton
- alias: Bouton Doudou
id: switch.doudou
trigger:
platform: event
event_type: xiaomi_aqara.click
event_data:
click_type: single
entity_id: binary_sensor.switch_158d0001e18d16
condition: []
action:
- service: switch.toggle
entity_id: switch.chambredoud
## Toggle le lightstrip (double clic)
- alias: Bouton doudou double
id: switch.doudou.double
trigger:
platform: event
event_type: xiaomi_aqara.click
event_data:
click_type: double
entity_id: binary_sensor.switch_158d0001e18d16
condition: []
action:
- service: light.toggle
entity_id: light.yeelight_strip2_04cf8c7acfe8
Some buttons switch modes to on/off (Shower mode, Night mode etc.)
# Toggle le mode douche lors de l'appui du bouton sdb
- alias: Switch mode douche
id: switch.douche
trigger:
platform: event
event_type: xiaomi_aqara.click
event_data:
click_type: single
entity_id: binary_sensor.switch_158d0002134b92
condition: []
action:
service: input_boolean.toggle
data:
entity_id: input_boolean.mode_douche
The heating in the daughter's room is not necessary if she is at her mother's. So if her climate switches to auto (basically when a tracked person comes in), switch it back to manual if she is not home.
TODO: Override this behavior with some flag maybe
# Ne pas chauffer chez doudou si elle est chez sa mère
- alias: Mode absent doudou
id: override.doudou.heating
trigger:
platform: state
entity_id: climate.chambre_doudou
from: 'heat'
to: 'auto'
for:
minutes: 3
condition:
- condition: state
entity_id: calendar.calendar_doudou
state: 'off'
action:
service: climate.set_temperature
data:
entity_id: climate.chambre_doudou
hvac_mode: heat
temperature: 16
Telegram is my main way of interacting with HA, and same the main way of HA to notify me
Any good system has a good help :) So i have this command reminder. Note that the telegram command are case sensitive, and if you want tu support several, just add them to the trigger. Then these commands are clickable directly
- alias: Telegram commandes
id: telegrambot.help
trigger:
- platform: event
event_type: telegram_command
event_data:
command: '/Help'
- platform: event
event_type: telegram_command
event_data:
command: '/help'
- platform: event
event_type: telegram_command
event_data:
command: '/?'
condition: []
action:
service: notify.telegram
data_template:
title: '*Commandes implémentées*'
message: |
Résumé: /Status
Alarme: /StopAlarm /LaunchAlarm
Lumières: /LightsOff
Présence: /HomeMode /AwayMode
Caméras: /Cams /NoCams /Live
Notifications: /SnoozeNotifs /LaunchNotifs
Aspi: /LaunchAspi
Chauffage: /Heat /NoHeat
Garage: /OpenGarage /CloseGarage
It then looks like this
Summary
# commande /Status
- alias: Telegram etat
id: telegrambot.status
trigger:
- platform: event
event_type: telegram_command
event_data:
command: '/Status'
- platform: event
event_type: telegram_command
event_data:
command: '/status'
- platform: event
event_type: telegram_command
event_data:
command: '/s'
- platform: event
event_type: telegram_command
event_data:
command: '/!'
condition: []
action:
service: notify.telegram
data_template:
title: '*Statut de la maison*'
message: |
Mode présent: {% if is_state("input_boolean.mode_present", "on") -%} Activé {%- else -%} Désactivé {%- endif %}
Mode de chauffage: {% if is_state("input_boolean.heating", "on") -%} Auto {%- else -%} Absent {%- endif %}
Mode nuit: {% if is_state("input_boolean.mode_nuit", "on") -%} Activé {%- else -%} Désactivé {%- endif %}
Dernier mouvement: {{ states("sensor.last_motion") }}
Cameras : {% if is_state("switch.synology_home_mode", "on") -%} Desactivées {%- else -%} Activées {%- endif %}
Notifications: {% if is_state("input_boolean.snooze_notifs", "on") -%} Desactivées {%- else -%} Activées {%- endif %} (Desactivées {{ states("sensor.already_snoozed_notifs") }} fois ce jour)
Aspi: Passé pendant {{ states("sensor.cleaned_today") }} h
Conditions: {{ states("sensor.average_temperature") }} °C, {{ states("sensor.average_humidity") }} % hum
Portes ouvertes: {{ states("sensor.opened_doors") }}
Fenetres ouvertes: {{ states("sensor.opened_windows") }}
Lumières allumées: {{ states("sensor.active_lights") }}
Porte garage: {{ states("sensor.garage_summary") }}
It then looks like this
This automations run at given times of the day
All the scripts can be found in the dedicated file scripts.yaml
The tado application allows to set daily patterns for the heating, but if you use their geofencing mode, you cannot override the presence (you cannot start the heating in adavance for example). So the turn on heating is actually switching all the valves in auto mode (with a 3s delay not to stress the server) and the turn off sets them to manual on a low tempreature.
heating_on:
alias: Passe chauffage en mode Home
sequence:
- service: climate.set_hvac_mode
data:
entity_id: climate.salon
hvac_mode: auto
- delay:
seconds: 3
- service: climate.set_hvac_mode
data:
entity_id: climate.cuisine
hvac_mode: auto
- delay:
seconds: 3
- service: climate.set_hvac_mode
data:
entity_id: climate.chambre_alex
hvac_mode: auto
To turn the heating off, when nobody is home, the trick is to sitch them to manual mode with a low temperature. For readability, i did not put them all :)
#Passage de tous les radiateurs en mode manuel
heating_off:
alias: Eteint chauffage
sequence:
- service: climate.set_temperature
data:
entity_id: climate.salon
hvac_mode: heat
temperature: 16
- delay:
seconds: 3
- service: climate.set_temperature
data:
entity_id: climate.salle_de_bains
hvac_mode: heat
temperature: 14
The script allows to run multiple actions upon the detection of 'nobody home'
#Mode absent: Extinction de toutes les lumières, de la télé, activation des cams, desactivation du mode douche
away_mode:
alias: Passage mode absent
sequence:
- service: light.turn_off
data:
entity_id: group.light_devices, group.light_bulbs
- service: switch.turn_off
data:
entity_id: switch.synology_home_mode, switch.plug_158d0001de56c2, switch.chambre, switch.cuisine1, switch.cuisine2, switch.plug_158d0001a5d465, switch.chambredoud, switch.chiottelum, switch.chiotteventil, switch.plug_158d0001a5d465, switch.terasse, switch.lustresalon, switch.appliquesalon, switch.sdb
- service: media_player.turn_off
data:
entity_id: media_player.lg_tv_remote
- service: input_boolean.turn_off
data:
entity_id: input_boolean.mode_douche
The script is used to turn on (or off) the non WAF automations. For convenience/maintenance purposes, these automations are in a group
#waf mode: force l'allumage et fixe la couleur des lampes du couloir et du salon, desactive les allumages/changements de couleurs/extinctions automatiques des lampes du couloir et du salon
waf_mode:
alias: Stop non WAF Automations
sequence:
- service: light.turn_on
data:
entity_id: light.yeelight_color1_7811dc6a9651, light.yeelight_color2_7c49eb157ed5, light.yeelight_color2_7c49eb157a7e
color_name: ivory
brightness: 250
- service: automation.turn_off
data:
entity_id: group.non_waf
When there is movement and/or opened door when nobody is home, there are telegram notifications that are sent. Sometimes I don't want to receive them (like when the cleaning ladies are here, or when the dogs are active). The automation deactivates them for 1h, then if disable again for 3h, then 5, etc... In short it deactivates it, then delays the reactivation for 2 times the number of times it was already deactivated plus one.
# Snooze alerts. Finalement pour 1h, puis 3, puis 5, etc. Desactive les notifications d'intrusion temporairement
snooze_xh:
alias: Snooze an automation for x hour
sequence:
- service: automation.turn_off
data_template:
entity_id: '{{ automation }}'
- delay: '{{ states.sensor.already_snoozed_notifs.state | int * 2 +1 }}:00:00'
- service: automation.turn_on
data_template:
entity_id: '{{ automation }}'
- service: input_boolean.turn_off
data:
entity_id: input_boolean.snooze_notifs
This is used to receive a photo of the dafang cam directly in telegram
#Photo de la dafang en direct, envoyée via télégram
camera_snap_message:
alias: Send Camera snapshot
sequence:
- service: notify.telegram
data:
message: "Captures des caméras"
data:
photo:
- url: https://CAM-IP-HERE/cgi-bin/currentpic.cgi
username: root
password: !secret dafang_pass
verify_ssl: false
All this can be found in the dedicated file sensors.yaml
These ones are used to know historical things (did the vacuum cleaner work today, did we snooze notifcations already...)
- platform: history_stats
name: Cleaned Today
entity_id: vacuum.xiaomi_vacuum_cleaner
state: 'cleaning'
type: time
start: '{{ now().replace(hour=0).replace(minute=0).replace(second=0) }}'
end: '{{ now() }}'
- platform: history_stats
name: Already Snoozed Notifs
entity_id: input_boolean.snooze_notifs
state: 'on'
type: count
start: '{{ now().replace(hour=0).replace(minute=0).replace(second=0) }}'
end: '{{ now() }}'
- platform: mqtt
name: Garage Door Status
state_topic: "garadget/Garage/status"
value_template: '{{ value_json.status }}'
These ones are used to calculate things (battery level of a sensor with a custom icon, averages, last mouvement, opened windows, etc...)
N.B: Could maybe done recursively, atm i do the same calcultaion for all sensors
- platform: template
sensors:
bat_mvt_sdb:
friendly_name: Mouvement SDB
value_template: >
{% if is_state('binary_sensor.motion_sensor_158d0001e47f52', 'unknown') %}
110
{% else %}
{{ states.binary_sensor.motion_sensor_158d0001e47f52.attributes["battery_level"] | float}}
{% endif %}
icon_template: >
{% set battery_level_xod1 = states.binary_sensor.motion_sensor_158d0001e47f52.attributes.battery_level|default(0)|int %}
{% set battery_round_xod1 = (battery_level_xod1 / 10) |int * 10 %}
{% if battery_round_xod1 >= 100 or is_state('binary_sensor.motion_sensor_158d0001e47f52', 'unknown') %}
mdi:battery
{% elif battery_round_xod1 > 0 %}
mdi:battery-{{ battery_round_xod1 }}
{% else %}
mdi:battery-charging-wireless-outline
{% endif %}
unit_of_measurement: '%'
Gives back a text with the friendly name of the sensor and its last activation N.B: There is a little (acceptable) bug: The last changed can be change back to 'not-detected' state 1 min after last actual movement
- platform: template
sensors:
last_motion:
friendly_name: Dernier mouvement
value_template: >
{% set allmotion = states | selectattr('entity_id', 'in', state_attr('group.motion_sensors', 'entity_id')) | list %}
{% set open= allmotion | map(attribute='last_changed') | list |max %}
{{allmotion |selectattr('last_changed','eq', open)|map(attribute='name')|list|join}} le {{ as_timestamp(open) | timestamp_custom('%d/%m/%Y à %-Hh%M') }}
Gives back a comma separated list of friendly names of sensors with a given state (turned on lights, opened windows, visible trackers etc)
The second line forces the reread of the sensors value every minute, or the template sensor is never re-evaluated... Took me ages to figure that out
{% set forceupdate= strptime(states.sensor.date_time.state, '%Y-%m-%d, %H:%M')%}
Uses groups for dynamic integrations
- platform: template
sensors:
### Fenetres ouvertes
opened_windows:
friendly_name: Fenetres ouvertes
value_template: >
{% set allwindows = states | selectattr('entity_id', 'in', state_attr('group.window_sensors', 'entity_id')) | list %}
{% set forceupdate= strptime(states.sensor.date_time.state, '%Y-%m-%d, %H:%M')%}
{% set open= allwindows | selectattr('state', 'equalto', 'on') | list %}
{{ open| length}} / {{ allwindows | length}} ({{open | map(attribute='name') |list | join(', ') }})
### Lumières allumées
active_lights:
friendly_name: Lumières allumées
value_template: >
{% set alllights = states | selectattr('entity_id', 'in', state_attr('group.monitored_light', 'entity_id')) | list %}
{% set forceupdate= strptime(states.sensor.date_time.state, '%Y-%m-%d, %H:%M')%}
{% set turnedon= alllights | selectattr('state', 'equalto', 'on') | list %}
{{ turnedon| length}} / {{ alllights | length}} ({{turnedon | map(attribute='name') |list | join(', ') }})
### trackers visibles
home_trackers:
friendly_name: Trackers visibles
value_template: >
{% set alltrackers = states | selectattr('entity_id', 'in', state_attr('group.tracked_devices', 'entity_id')) | list %}
{% set forceupdate= strptime(states.sensor.date_time.state, '%Y-%m-%d, %H:%M')%}
{% set present= alltrackers | selectattr('state', 'equalto', 'home') | list %}
{{ present| length}} / {{ alltrackers| length}} ({{present | map(attribute='name') |list | join(', ') }})('%d/%m/%Y à %-Hh%M') }}
Gives back the value of the average of a group of sensors The second line forces the reread every minute of the sensors value, or the average is never recalculated... Took me ages to figure that out
{% set forceupdate= strptime(states.sensor.date_time.state, '%Y-%m-%d, %H:%M')%}
Forcing the unit allows to put them on the same graph as the actual sensors Uses groups for dynamic integrations
N.B: There is a little (not very acceptable) bug: if a sensor is unavailable, it will count as 0 and trick the average. Could be excluded in the first selection
- platform: template
sensors:
average_temperature:
friendly_name: Températe moyenne
unit_of_measurement: '°C'
value_template: >
{% set sensors = states | selectattr('entity_id', 'in', state_attr('group.room_temperature', 'entity_id')) | list %}
{% set forceupdate= strptime(states.sensor.date_time.state, '%Y-%m-%d, %H:%M')%}
{% set values = sensors | map(attribute='state')|map('float')|list%}
{{ (values |sum / values |length)|round(2) }}
average_humidity:
friendly_name: Humidité moyenne
unit_of_measurement: '%'
value_template: >
{% set sensors = states | selectattr('entity_id', 'in', state_attr('group.room_humidity', 'entity_id')) | list %}
{% set forceupdate= strptime(states.sensor.date_time.state, '%Y-%m-%d, %H:%M')%}
{% set values = sensors | map(attribute='state')|map('float')|list%}
{{ (values |sum / values |length)|round(2) }}
It was based on the monster card. You can find it on ciotlosm Github. Copy it to your /js folder
Edit: Migrated to Auto entities. You can find it on thomasloven Github. Copy it to your /js folder
Add code at the beigining of the lovelace file
resources:
- type: js
url: /local/js/auto-entities.js?v=1.1
You for example can the get all the turned on lights with the following code
- card:
title: Lumières Allumées
type: entities
filter:
include:
- entity_id: light.*
state: 'on'
type: 'custom:auto-entities'
Or the present device trackers
- card:
title: Personnes présentes
type: glance
filter:
include:
- entity_id: device_tracker.*
state: home
type: 'custom:auto-entities'
Or all the low batteries
- card:
title: Batteries inférieures a 33%
type: glance
filter:
include:
- entity_id: sensor.bat*
state: < 30
type: 'custom:auto-entities'
Last example with exclusions, all the turned on switches except the ones created by the dafang cam
- card:
title: Interrupteurs Allumées
type: entities
filter:
exclude:
- entity_id: switch.dafang*
include:
- entity_id: switch.*
state: 'on'
type: 'custom:auto-entities'
You need a background image, and if you like a different one for the switched (on or off) then another one. I used Paint.Net to darken/lighten the images then you just need to switch the image according to the status of a sensor (here a switch). You could also do the same with css transforms on the image.
- entity: switch.chambre
image: /local/images/chambre.png
state_image:
'off': /local/images/chambre_off.png
'on': /local/images/chambre.png
style:
left: 30%
top: 64.5%
width: 24.5%
tap_action:
action: none
type: image
You can also add a tap action on the image
- entity: input_boolean.mode_waf
state_image:
'off': /local/images/waf_off.png
'on': /local/images/waf.png
style:
left: 6%
top: 28%
width: 9%
tap_action:
action: toggle
title: mode waf
type: image
They are mostly used to force the icon in the lovelace ui and/or in the picture elements cards, and to give them a friendlier name All this can be found in the dedicated file customize.yaml
climate.salon:
icon: mdi:radiator
light.yeelight_strip2_04cf8c7acfe8:
friendly_name: LightStrip Doudou
icon: mdi:led-off
La maison fonctionne dans 2 modes. Présent et Absent. Le mode présent est activé dès qu'un téléphone tracké est détecté (bluetooth). Pour confirmer l'activation du mode présent, les lumières du salon (lampadaire, les 3 petites lampes et le ledstrip sous la télé s'allument). Lorsque le mode présent est activé, le chauffage se met en route, les caméras sont désactivées et les lumières du couloir et de la salle de bains s'allument sur notre passage et s'éteignent 1 min après qu'on aie quitté la pièce.
De même lorsque la maison ne voit plus aucun téléphone tracké pendant 5 min elle passe en mode absent (tout s'éteint (lumières, tv, chauffage), les caméras s'allument et je suis notifié si il y a un mouvement ou une ouverture de porte)
Sur l'interface, l'icone de la maison est coloré, pour signaler le mode présent, et grisé si il est désactivé
N.B: L'appui sur le bouton depuis l'interface change directement le mode présent/abesnt
Le petit Hic, c'est que la chambre est en limite de portée de bluetooth, donc il arrive qu'il perde la connectique, puis la retrouve. Pour éviter que les lumières du salon s'allument, il y a le mode nuit pour ca. Le mode nuit permet de ne pas allumer les lampes si on déconnecte/reconnecte, et de ne pas couper le chauffage non plus. Le mode nuit est activé en jettant en l'air le cube a coté de la tv, (idéalement en le rattrapant), ou a l'appui du mode nuit sur la tablette. Le mode nuit éteint toutes les lumières et la TV.
Le mode nuit se désactive automatiquement à 8h30 le matin, ou si on appuie sur l'interrupteur du plan de travail dans la cuisine.
Sur l'interface, l'icone de la nuit est coloré, pour signaler le mode nuit, et grisé si il est désactivé N.B: L'appui sur le bouton depuis l'interface change directement le mode nuit
La lumière de la salle de baisn s'éteint toute seule si elle ne détecte personne pendant 1 minute. Parfois, elle ne nous voit pas sous la douche.
Il y a le mode douche pour ca. Il désactive l'allumage/extinction automatique de la salle de bains, et met le chauffage de la salle de bains à fond
Pour l'activer, le bouton à l'entrée de la salle de bains allume le mode douche (et la lumière), et l'éteint (et la lumière)
Le mode douche se désactive automatiquement apres 45 minutes, ou si on passe en mode absent.
Sur l'interface, l'icone de la douche (dans la salle de bains) est coloré, pour signaler le mode douche, et grisé si il est désactivé N.B: L'appui sur le bouton depuis l'interface change directement le mode douche
L'écran principal est le résumé. Il permet de voir en un coup d'oeil l'état de la maison (lumières, modes, chauffages, etc). Tout les éléments sont cliquables
L'écran suivant est une photo interactive du salon. Il permet d'allumer éteindre toutes les lumières du salon en cliquant sur la photo. C'est plus un gadget qu'autre chose, je voulais juste voir comment ça rendait
L'écran important restant est le "dynamic" qui permet de voit toutes les lumieres allumées, interrupteurs enclenchés, portes ouvertes, personnes preésentes, etc... Pour les lumières et interrupteurs, on peut directement les éteindre (tous ou un par un).