docs updated

changes.md

@@ -1,7 +1,7 @@
 # Changes and Feature List
 
 ## Version 1.4.1 Support for sending arbritrary messages
-* Added Service for sending arbritrary ESP2 messages
+* Added Service for sending arbritrary EnOcean (ESP2) messages. Intended to be used in conjunction with [Home Assistant Automations](https://www.home-assistant.io/getting-started/automation/).
 * 🐞 Fix for TargetTemperatureSensor (EEP: A5-10-06 and A5-10-12)
 * 🐞 Fix for unknow cover positions and intermediate state + unit-tests added.
 * Unit-Tests added and improved for EEP A5-04-01, A5-04-02, A5-10-06, A5-10-12, A5-13-01, and F6-10-00.

docs/service-send-message/readme.md

@@ -8,7 +8,7 @@ This service is mainly inteded to combine none-EnOcean and EnOcean devices. Serv
 
 Create an [automation](https://www.home-assistant.io/getting-started/automation/) in Home Assistant. Use the upper sections to react on anything you like, dependent on you sensor/sender. 
 
-`Add Action` and search for `eltako`. It proposes a service to send messages for every available gateway. In addition you need to enter in the data section what to send. The fields `id` and `eep` must be specified. `id` stands for the sender address. (Keep in mind: bus gateways do not send in wireless network and wireless tranceivers do only have 128 hardcoded addresses to be used.) `eep` is the message format you what to use. Dependent on the eep specific information is put into the messages to be sent. You can either check in the [code](https://github.com/grimmpp/eltako14bus/blob/master/eltakobus/eep.py) or in this automatically generated [parameter list for EEPs](eep-params.md). In the logs you can see what parameters has been transferred and which will be set as default to 0.
+`Add Action` and search for `eltako`. It proposes a service to send messages for every available gateway. In addition you need to enter in the data section what to send. The fields `id` and `eep` must be specified. `id` stands for the sender address. (Keep in mind: bus gateways do not send in wireless network and wireless tranceivers do only have 128 hardcoded addresses to be used.) `eep` is the message format you what to use. Dependent on the eep specific information is put into the messages to be sent. You can either check in the [code](https://github.com/grimmpp/eltako14bus/blob/master/eltakobus/eep.py) or in this automatically generated [parameter list for EEPs](eep-params.md). In the logs you can see what parameters has been transferred and which will be set as default to 0. To fill the EEP paramters with values we use [templating of HA](https://www.home-assistant.io/docs/configuration/templating/). This gives us the posibility to read values from different sensors, modify them if required, and pass them to be sent.
 
 <img src="send_message_logs_screenshot.png" />
 
@@ -24,8 +24,12 @@ action:
     data:
       id: FF-DD-00-01
       eep: A5-10-06
-      current_temp: {{state_attr('climate.my_other_brands_smart_thermostat_1293127', 'current_temperature') }}
-      target_temp: {{state_attr('climate.my_other_brands_smart_thermostat_1293127', 'target_temperature') }}
+      current_temp: >-
+        {{state_attr('climate.my_other_brands_smart_thermostat_1293127', 'current_temperature') }}
+      target_temp: >-
+        {{state_attr('climate.my_other_brands_smart_thermostat_1293127', 'target_temperature') }}
+      #target_temp: >-
+      #  {{ states('sensor.eltako_gw1_ff_aa_00_81_temperature', rounded=True) }}  # alternative to get temperature value of a sensor
     enabled: true
 mode: single
 ```