Tomasz

I have a similar scenario and currently, I do that using RabbitMQ and NSQ. One can call a REST endpoint or the main app (the only one that is publically...

@davidfowl the requirement for using MQ was quite simple: some requests can take a long time to complete. For example, generating a report or doing a complex SQL query. So...

any updates on this? version 2.0.0 was released (https://github.com/microsoft/reverse-proxy/releases/tag/v2.0.0) but sadly tunneling isn't mentioned anywhere.

I've applied the change to my system (2024.1.2) and tested it with the below blueprint: ``` blueprint: name: Ikea Tradfri Dimmer as Shutter Remote (Zigbee2MQTT) description: | Control a shutter...

The action part can be optimized for sure, but feel free to use the blueprint in any way you want :) Thank you for adding the posibility to use templates,...

@jbouwh for my current use case (the blueprint) from above, I need just `discovery_id`. The rest is hard coded in triggers. Maybe a Jinja functuon that for a given device...

I'll check that tommorow. It should work for trigger_variables? Before I had to call template inside trigger. Or does that part stays the same?

I've described my potential use case here: https://community.home-assistant.io/t/wth-why-cant-i-use-mqtt-device-triggers-in-a-blueprint/482219/22?u=misiu the idea is to be able to build `discovery_id` from a variable in a blueprint. > A template can be added to...

According to https://community.home-assistant.io/t/wth-why-cant-i-use-mqtt-device-triggers-in-a-blueprint/482219/29?u=misiu the IEEE address is added to the identifiers attribute for the device, so in theory, one can use: ``` {{ (device_attr('d4bacfb73175d44ad4fdc88cbc3676b1', 'identifiers')|list)[0][1].split('_')[-1] }} ``` to get the...

> > the `device_attr` isn't supported in limited templates, so I guess this won't work in trigger_variables. > > Did you try it? It is just that the template is...