# Sending information from Node Red to Webcore

**URL:** <https://discourse.nodered.org/t/sending-information-from-node-red-to-webcore/62038>\
**Category:** General\
**Created:** [1 May 2022 19:42 UTC](https://discourse.nodered.org/t/sending-information-from-node-red-to-webcore/62038 "2022-05-01T19:42:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mebejedi](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@Mebejedi](https://discourse.nodered.org/u/Mebejedi)\
**Post date:** [1 May 2022 19:42 UTC](https://discourse.nodered.org/t/sending-information-from-node-red-to-webcore/62038/1 "2022-05-01T19:42:17Z")

</div>

Yes, I know....strange question.

I'm slowly learning Node Red, but one thing I really love about it is the ability to determine which Echo received a command. I've already created a flow that allows me to say "Turn on/off fan" in every room, and the fan associated with each Echo will turn the appropriate fan on/off.

I used to be able to do this with Hubitat/Webcore/EchoSpeaks and the _ **wasLastSpokenToDevice** _ setting, but Amazon disabled it. I have some complicated pistons that I'd like to route to the appropriate Echo, and I was just curious if there was a way to have Node Red determine the Echo spoken to, and somehow port this information back to WC...at least until I can recreate the pistons as flows. Is this a pipe dream?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [30 June 2022 19:42 UTC](https://discourse.nodered.org/t/sending-information-from-node-red-to-webcore/62038/2 "2022-06-30T19:42:48Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.