Is it possible to send radio telegrams?

[tzippy84]

I was wondering if its also possible to somehow send telegrams through an automation? How would I do that?
Thank you!

[mak-gitdev]

Hi,

I need more details to give you an accurate answer.
Which radio telegram do you want to send, or which EnOcean device do you want to control ?

[tzippy84]

sorry, here's some more details:
I have a TCM300 transceiver module connected to an arduino that controls a couple of LEDs. It runs a simple program that listens to all enocean radio packets. It only acts on a certain ID (simple byte compare) from one PTM210 rocker switch.
So I am pretty free in what I can do on the receiving side of the Arduino.
The most simple thing (for me ) would be to send the same F6-02-01 telegrams that the Arduino now listens to.

[mak-gitdev]

Ok I see.

You can do it, even if for the moment, it is not fully supported and not intended to work like that.
I mean, I made this work having in mind that F6 telegrams will always come to HA, I never had the use case to generate such telegrams in my applications.
But as this is of interest, especially for Eltako users, it will be fully supported in a future version I will start working on soon.

Please see this discussion for how to do it.
Note that if you use the dev version of the addon (I recommend to use this version), the base id is now easily available. See #17 for more details.

[mak-gitdev]

Do not hesitate if you have questions.

Also please report here if you have any success.
I am waiting for a confirmation that the described procedure works well before starting implementing it.

[tzippy84]

I tried following the steps from the topic you linked. But when you write "So, for the moment, please define 2 MQTT sensors like this:“ I’m not sure how to manually configure MQTT entities. Where would I put the yaml configuration? If I paste it into my configuration.yaml I get an error saying „Property button is not allowed“. I am new to MQTT broker. Thanks!

…

Am 29.11.2022 um 09:34 schrieb mak-gitdev ***@***.***>: Do not hesitate if you have questions. Also please report here if you have any success. I am waiting for a confirmation that the described procedure works well before starting implementing it. — Reply to this email directly, view it on GitHub <#22 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARU5K4FFDC6AXHQMUKHVN5DWKW5ZLANCNFSM6AAAAAASNGEJ7Y>. You are receiving this because you authored the thread.

[mak-gitdev]

Which version of HA are you using ?

[tzippy84]

2022.11.4 mak-gitdev ***@***.***> schrieb am Mi. 30. Nov. 2022 um 05:50:

…

Which version of HA are you using ? — Reply to this email directly, view it on GitHub <#22 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARU5K4GZQLFSLQJCUM6GGZDWK3MKHANCNFSM6AAAAAASNGEJ7Y> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[mak-gitdev]

I think it should be ok.

May I see your configuration.yaml ? Please mask all sensitive data before publishing it.

[tzippy84]

Sure. Here it is. Nothing too fancy going on I think: ```yaml # Loads default set of integrations. Do not remove. default_config: # Text to speech tts: - platform: google_translate powercalc: image_processing: - platform: doods url: http://192.168.0.136:8080 detector: default scan_interval: 1 source: - entity_id: camera.mobotix_i26 file_out: /config/www/doods_{{ camera_entity.split('.')[1] }}_latest.jpg confidence: 60 labels: - name: car confidence: 70 - name: person confidence: 70 - truck camera: - platform: generic name: doods_cam still_image_url: http://192.168.0.136:8123/local/doods.jpg sensor: - platform: command_line name: CPU Temperature command: "cat /sys/class/thermal/thermal_zone2/temp" unit_of_measurement: "°C" value_template: "{{ value | multiply(0.001) | round(1) }}" - platform: systemmonitor resources: - type: disk_use_percent arg: /config - type: memory_free - type: processor_use - type: disk_use_percent arg: "/" - type: disk_free arg: "/" - type: memory_use_percent - type: network_in arg: eth0 - type: throughput_network_in arg: eth0 - type: network_out arg: eth0 - type: throughput_network_out arg: eth0 - type: processor_temperature - type: last_boot automation: !include automations.yaml script: !include scripts.yaml scene: !include scenes.yaml homeassistant: allowlist_external_dirs: - /config/tmp - /config/www utility_meter: util_water_usage_hourly: source: sensor.water_total cycle: hourly util_water_usage_daily: source: sensor.water_total cycle: daily util_water_usage_monthly: source: sensor.water_total cycle: monthly util_water_usage_yearly: source: sensor.water_total cycle: yearly ```

…

On Wed, Nov 30, 2022 at 10:07 AM mak-gitdev ***@***.***> wrote: I think it should be ok. May I see your configuration.yaml ? Please mask all sensitive data before publishing it. — Reply to this email directly, view it on GitHub <#22 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARU5K4FB2ULCP4FHG6KMOOLWK4KLJANCNFSM6AAAAAASNGEJ7Y> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[mak-gitdev]

Sorry I meant with the MQTT section added.

[tzippy84]

I just paste the block from the topic you lik and I get from Visual Studio Code the error next to "button:" stating that "Property button is not allowed". Here's the entire configuration.yaml # Loads default set of integrations. Do not remove. default_config: # Text to speech tts: - platform: google_translate powercalc: image_processing: - platform: doods url: http://192.168.0.136:8080 detector: default scan_interval: 1 source: - entity_id: camera.mobotix_i26 file_out: /config/www/doods_{{ camera_entity.split('.')[1] }}_latest.jpg confidence: 60 labels: - name: car confidence: 70 - name: person confidence: 70 - truck camera: - platform: generic name: doods_cam still_image_url: http://192.168.0.136:8123/local/doods.jpg sensor: - platform: command_line name: CPU Temperature command: "cat /sys/class/thermal/thermal_zone2/temp" unit_of_measurement: "°C" value_template: "{{ value | multiply(0.001) | round(1) }}" - platform: systemmonitor resources: - type: disk_use_percent arg: /config - type: memory_free - type: processor_use - type: disk_use_percent arg: "/" - type: disk_free arg: "/" - type: memory_use_percent - type: network_in arg: eth0 - type: throughput_network_in arg: eth0 - type: network_out arg: eth0 - type: throughput_network_out arg: eth0 - type: processor_temperature - type: last_boot automation: !include automations.yaml script: !include scripts.yaml scene: !include scenes.yaml homeassistant: allowlist_external_dirs: - /config/tmp - /config/www utility_meter: util_water_usage_hourly: source: sensor.water_total cycle: hourly util_water_usage_daily: source: sensor.water_total cycle: daily util_water_usage_monthly: source: sensor.water_total cycle: monthly util_water_usage_yearly: source: sensor.water_total cycle: yearly mqtt: button: - name: "eltako_test_f60201_pressed_B0" unique_id: man_eltako_test_f60201_pressed_B0 command_topic: "enoceanmqtt/eltako/test/req" payload_press: >- {"R1":3,"EB":1,"R2":0,"SA":0,"T21":1,"NU":1,"send":"clear"} - name: "eltako_test_f60201_released_B0" unique_id: man_eltako_test_f60201_released_B0 command_topic: "enoceanmqtt/eltako/test/req" payload_press: >- {"R1":0,"EB":0,"R2":0,"SA":0,"T21":1,"NU":0,"send":"clear"}

…

On Wed, Nov 30, 2022 at 10:49 AM mak-gitdev ***@***.***> wrote: Sorry I meant with the MQTT section added. — Reply to this email directly, view it on GitHub <#22 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARU5K4BIJH5QG5FU3X24SJDWK4PJBANCNFSM6AAAAAASNGEJ7Y> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[mak-gitdev]

The error comes from VS Code ?
What happens when you check your configuration with HA ?

Image is from https://www.fordtransitusaforum.com/cdn-cgi/image/format=auto,onerror=redirect,width=1920,height=1920,fit=scale-down/https://www.fordtransitusaforum.com/attachments/1653152054593-png.172310/

[tzippy84]

Oh, I didn't even know that was an option. It worked and now I have the two entities for press and release. Now I just have to figure out which button my TCM300 listens to. Just a quick question concerning the payload: For "pressed B0" you have R1 = 3 (EB = 1), for "released B0" R1 is 0 (EB = 0). But when I look at the EnOcean Equipment Profile F6-02-01 a value R1 = "0" indicates Button A0. So shouldn't R1 be 3 in both cases? I'm referring to this document: https://www.enocean-alliance.org/wp-content/uploads/2017/05/EnOcean_Equipment_Profiles_EEP_v2.6.7_public.pdf

…

On Wed, Nov 30, 2022 at 11:31 AM mak-gitdev ***@***.***> wrote: The error comes from VS Code ? What happens when you check your configuration with HA ? [image: image] <https://user-images.githubusercontent.com/73297795/204772443-b970ea3f-ea85-414b-9fc0-465ac173779e.png> Image is from https://www.fordtransitusaforum.com/cdn-cgi/image/format=auto,onerror=redirect,width=1920,height=1920,fit=scale-down/https://www.fordtransitusaforum.com/attachments/1653152054593-png.172310/ — Reply to this email directly, view it on GitHub <#22 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARU5K4CGA6O7ABMV4I4ZRVLWK4UGLANCNFSM6AAAAAASNGEJ7Y> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[mak-gitdev]

Hi,

No need to have R1 != 0 when EB=0.

And just to confirm, for example, it is like that in telegrams generated by f6-02-01 devices

Press B0
2022-11-21 12:05:36,715 DEBUG: FE:E6:94:E8->FF:FF:FF:FF (-76 dBm): 0x01 ['0xf6', '0x70', '0xfe', '0xe6', '0x94', '0xe8', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x4c', '0x0'] OrderedDict() 2022-11-21 12:05:36,716 INFO: unknown sensor: FE:E6:94:E8

Release B0
2022-11-21 12:05:36,920 DEBUG: FE:E6:94:E8->FF:FF:FF:FF (-76 dBm): 0x01 ['0xf6', '0x0', '0xfe', '0xe6', '0x94', '0xe8', '0x20'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x4c', '0x0'] OrderedDict() 2022-11-21 12:05:36,921 INFO: unknown sensor: FE:E6:94:E8

Just a reminder that this is not supported yet. The proposed procedure is just a hack of the existing code.
For the moment you will only be able to emulate a single device in HA.
Do not try with more devices as it will corrupt the device database and you will have to uninstall then reinstall the addon.

[tzippy84]

Okay, thanks! So, Pres B0 is 0xF6 0x70 .... 0x30 While Release B0 is 0xF6 0x00 .... 0x20 How does the value 0x70 to be interpreted and what would it be Press A1/A0/B1 ? How do I go from R1 to this value?

…

On Thu, Dec 1, 2022 at 10:30 AM mak-gitdev ***@***.***> wrote: Hi, No need to have R1 != 0 when EB=0. And just to confirm, fox example, it is like that in telegrams generated by f6-02-01 devices Press B0 2022-11-21 12:05:36,715 DEBUG: FE:E6:94:E8->FF:FF:FF:FF (-76 dBm): 0x01 ['0xf6', '0x70', '0xfe', '0xe6', '0x94', '0xe8', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x4c', '0x0'] OrderedDict() 2022-11-21 12:05:36,716 INFO: unknown sensor: FE:E6:94:E8 Release B0 2022-11-21 12:05:36,920 DEBUG: FE:E6:94:E8->FF:FF:FF:FF (-76 dBm): 0x01 ['0xf6', '0x0', '0xfe', '0xe6', '0x94', '0xe8', '0x20'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x4c', '0x0'] OrderedDict() 2022-11-21 12:05:36,921 INFO: unknown sensor: FE:E6:94:E8 — Reply to this email directly, view it on GitHub <#22 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARU5K4FGYNIXJ2SNFMAB2XDWLBV47ANCNFSM6AAAAAASNGEJ7Y> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[mak-gitdev]

No better answer than the EEP doc for F6-02-01 😊

[tzippy84]

Thanks for the hint ;) So my "buttons" from home assistant are sending EnOcean telegrams now (I am sniffing with a seperate Pi and TCM320 module) . However the packets from Home Assistant have the USB300's ID and not the one I defined in the enoceanmqtt.devices file. Which looks like this: [sender1] address = 0xFFFFFFFF rorg = 0xF6 func = 0x02 type = 0x01 sender = 0x00129BA8 Here's what I logged. First two packets is pressing the actual button, the next two is the HA button: HW button 2022-12-02 13:39:55,371 - enocean.communicators.SerialCommunicator - DEBUG - 0x03 ['0xf6', '0x70', '0x0', '0x12', '0x9b', '0xa8', '0x30'] ['0x5', '0xff', '0xff', '0xff', '0xff', '0x46', '0x0', '0xd9', '0xd', '0x0', '0x46', '0x30', '0x4', '0x46', '0x30', '0x14', '0x47', '0x30', '0x17', '0x47', '0x30', '0x1a', '0x47', '0x30'] OrderedDict() 2022-12-02 13:39:55,811 - enocean.communicators.SerialCommunicator - DEBUG - 0x03 ['0xf6', '0x0', '0x0', '0x12', '0x9b', '0xa8', '0x20'] ['0x5', '0xff', '0xff', '0xff', '0xff', '0x46', '0x0', '0xda', '0xc5', '0x0', '0x46', '0x20', '0x4', '0x46', '0x20', '0xe', '0x46', '0x20', '0x11', '0x47', '0x20', '0x14', '0x47', '0x20'] OrderedDict() SW button 2022-12-02 13:40:01,146 - enocean.communicators.SerialCommunicator - DEBUG - 0x03 ['0xf6', '0x70', '0x0', '0x86', '0x3f', '0xa3', '0x0'] ['0x3', '0xff', '0xff', '0xff', '0xff', '0x5c', '0x0', '0xf0', '0x0', '0x0', '0x5e', '0x0', '0x5', '0x5e', '0x0', '0x16', '0x5c', '0x0'] OrderedDict() 2022-12-02 13:40:01,952 - enocean.communicators.SerialCommunicator - DEBUG - 0x03 ['0xf6', '0x0', '0x0', '0x86', '0x3f', '0xa3', '0x0'] ['0x3', '0xff', '0xff', '0xff', '0xff', '0x5e', '0x0', '0xf3', '0x26', '0x0', '0x5e', '0x0', '0x7', '0x5e', '0x0', '0x22', '0x5e', '0x0'] OrderedDict()

…

On Fri, Dec 2, 2022 at 2:22 PM mak-gitdev ***@***.***> wrote: No better answer than the EEP doc <http://tools.enocean-alliance.org/EEPViewer> for F6-02-01 <http://tools.enocean-alliance.org/EEPViewer/profiles/F6/02/01/F6-02-01.pdf> 😊 — Reply to this email directly, view it on GitHub <#22 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARU5K4B4UEPZ4N4S6Q2P5Y3WLHZ2XANCNFSM6AAAAAASNGEJ7Y> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[mak-gitdev]

0x00129BA8 is the EnOcean Unique Radio ID (EURID) of your hardware button. This address is unique to your HW button and it cannot be replicated by your EnOcean chip (either TCM or USB300).

sender can be either the EURID of your EnOcean chipset or one of its 128 alternative addresses (Base ID).
Please have a look to #1 starting from this message.

If using the dev version of the addon, you can now find your base ID as described in #17

[tzippy84]

Thank you, it's working now! I am sending radio telegrams.

…

On Fri, Dec 2, 2022 at 4:30 PM mak-gitdev ***@***.***> wrote: 0x00129BA8 is the EnOcean Unique Radio ID (EURID <https://www.enocean-alliance.org/EURID/>) of your hardware button. This address is unique to your HW button and it cannot be replicated by your EnOcean chip (either TCM or USB300). sender can be either the EURID <https://www.enocean-alliance.org/EURID/> of your EnOcean chipset or one of its 128 alternative addresses (Base ID). Please have a look to #1 <#1> starting from this message <#1 (comment)> . If using the dev version of the addon, you can now find your base ID as described in #17 <#17> — Reply to this email directly, view it on GitHub <#22 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARU5K4CYBD5J54OSTQHNKWDWLIIZZANCNFSM6AAAAAASNGEJ7Y> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[mak-gitdev]

Great !

Now that it is confirmed to work, I will add support for that so that you won't have to modify your configuration.yaml at all.

[tzippy84]

Awesome! Thanks for the great work! Much appreciated mak-gitdev ***@***.***> schrieb am Mo. 5. Dez. 2022 um 19:00:

…

Great ! Now that it is confirmed to work, I will add support for that so that you won't have to modify your configuration.yaml at all. — Reply to this email directly, view it on GitHub <#22 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARU5K4GRQ76JWIA66QP5JODWLYUS3ANCNFSM6AAAAAASNGEJ7Y> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[HotteX]

Hello, am I right in assuming that
"For the moment you will only be able to emulate a single device in HA.
Do not try with more devices as it will corrupt the device database and you will have to uninstall then reinstall the addon."
is still valid?

My next Project, now I have all my sensors running, would be sending temperature data into the EnOcean-World. And I would need more than one ;)