diff --git a/Readme.Md b/Readme.Md
index dc19cfb..f995d8a 100755
--- a/Readme.Md
+++ b/Readme.Md
@@ -475,4 +475,3 @@ Moving forward (post 1.9) there will be two primary branches, `master` and `dev`
     * Added ability to set temperature
     * Added ability to set room mode (auto,boost,manual)
 
-Copyright (c) Angelo Santagata
diff --git a/Recipes.md b/Recipes.md
index ddbff30..e169dd8 100755
--- a/Recipes.md
+++ b/Recipes.md
@@ -6,11 +6,14 @@ Thank you all
 
 * Collection of Sensors (@phixion)
 * Custom Lovelace Card (@phixion)
-* Renaming Element names in History Graphs (@DrJohnT & @msp1974)
+* Renaming History Graphs Element Names in  (@DrJohnT & @msp1974)
 * Interacting with custom schedules using the Lovelace UI (@nofuse)
+* Linking 3rd Party TRVs/Sensors to Wiser Heating  (@carloneb)
 
 ## Collection of Sensors ( **[phixion](https://github.com/phixion)**)
 
+------
+
 Following files assume you are separating out you configuration.yaml file into separate files (e.g. sensor.yaml,binary_sensor.yaml etc) as per https://www.home-assistant.io/docs/configuration/splitting_configuration/. if you want you can put these all in a single `configuration.yaml`.
 
 
@@ -96,6 +99,8 @@ sensor.yaml: history_stats spits out unitof measuerment in hours, so here is a s
 
 ## Custom Lovelace Card (https://gist.github.com/phixion)
 
+------
+
 
 
 ![](docs/phixion-card-graphic.png)
@@ -159,7 +164,9 @@ filter:
       state: <101
 type: 'custom:auto-entities'
 ```
-# Renaming Element names in History Graphs
+# Renaming History Graphs Element Names 
+
+------
 
 If you want to rename element names in the history graphs you can. There are two ways you can do this. 
 
@@ -213,6 +220,8 @@ if these are added to the  history graphs, elements will be named as per the fri
 
 # Interacting with custom schedules using the Lovelace UI
 
+------
+
 One question popped on the thread was how to switch between different schedules using the UI. This pattern shows how this can be implemented so that you have different schedules and can switch between them in an instant!
 
 Alas there is no way to view the schedules in HomeAssistant, a PR for this would be very welcome!
@@ -230,7 +239,80 @@ Alas there is no way to view the schedules in HomeAssistant, a PR for this would
 
    
 
+# Linking 3rd Party TRVs/Sensors to Wiser Heating
+
+------
+
+@carloneb had the following scenario
 
+He has a Drayton Wiser Basic Kit one thermostat in the kitchen but he doesnt have a Wiser TRV in the main room, he does however have a SONOFF Zibbee temperature sensor which is already integrated with Home Assistant. Can he get the heating to trigger the request for heat when the main room is cold? without purchasing a new TRV?
+
+YES YES YES!
+
+## How
+
+Definitions:
+
+In `Configuration.yaml`, defined a new generic thermostat entity for the kitchen: “cucina”. This thermostat is commanding a switch (defined later) which is then triggering the Wiser’s commands. Also, the generic thermostat is linked to the Sonoff Temperature sensor (sensor.t_cucina_temperature).
+
+```yaml
+climate:
+  - platform: generic_thermostat
+    name: cucina
+    heater: switch.switch_t_cucina
+    target_sensor: sensor.t_cucina_temperature
+    min_temp: 5
+    max_temp: 30
+    ac_mode: false
+    target_temp: 20
+    cold_tolerance: 0.3
+    hot_tolerance: 0
+    initial_hvac_mode: "heat"
+
+```
+
+The switch used by the above thermostat is as follows. It calls the wiser.boost_heating service when on (demanding heat) and sets the wiser to auto when triggered off (target T reached).
+
+```yaml
+switch:
+  - platform: template
+    switches:
+      switch_t_cucina:
+        turn_on:
+      service: wiser.boost_heating
+        data:
+        entity_id: climate.wiser_soggiorno
+        time_period: 30
+        temperature: 21
+        temperature_delta: 1
+        turn_off:
+      service: climate.set_hvac_mode
+        data:
+        entity_id: climate.wiser_soggiorno
+    hvac_mode: "auto"
+```
+
+Because the main temperature scheduling is owned by the wiser (it’s the master), I’ve created an automation that “copy” the scheduled temperature from the wiser to the Sonoff thermostat at any change.
+
+```yaml
+- alias: Set target T cucina
+  description: Setta la T target di climate.cucina quando la T schedulata wiser cambia, tranne se in boost
+  condition:
+    condition: numeric_state
+    entity_id: climate.wiser_soggiorno
+      attribute: boost_remaining
+    below: 1
+  trigger:
+  - platform: state
+    entity_id: sensor.target_t
+    action:
+  - service: climate.set_temperature
+    data:
+    entity_id: climate.cucina
+    temperature: "{{ (states('sensor.target_t') | float) }}"
+```
 
+In this way I can have both rooms heat following the scheduling set in the Wiser.
 
+![sensors](D:\My\Src\Home\HA Stuff\wiserHomeAssistantPlatform\docs\nonwisersensor_image.jpg)
 
diff --git a/docs/nonwisersensor_image.jpg b/docs/nonwisersensor_image.jpg
new file mode 100644
index 0000000..d796bfb
Binary files /dev/null and b/docs/nonwisersensor_image.jpg differ