# Human generated vs Machine generated events

**URL:** <https://discourse.nodered.org/t/human-generated-vs-machine-generated-events/102173>\
**Category:** General\
**Created:** [17 November 2026 09:58 UTC](https://discourse.nodered.org/t/human-generated-vs-machine-generated-events/102173 "2026-11-17T09:58:02Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![no\_mpimpi](https://avatars.discourse-cdn.com/v4/letter/n/f14d63/32.png) [@no\_mpimpi](https://discourse.nodered.org/u/no_mpimpi)\
**Post date:** [17 November 2026 09:58 UTC](https://discourse.nodered.org/t/human-generated-vs-machine-generated-events/102173/1 "2026-11-17T09:58:02Z")

</div>

Hello all,

I am exploring the idea of differentiating between system-generated events (eg turn on the lights at x time) versus human-generated events (eg someone reached out and touched a switch).

I feel like there's a use case where an automation is running, but a human interrupts it by interacting somehow. If the message came from a human, it should take priority over the running automation.

Since my system is based on MQTT, my current best idea is to include a value in the payload, eg: {"state": true; "source":"human"}.

Is there a better way of doing this? Have you tried this? What was your solution, and what else do you use it for?

Any ideas welcome.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [17 November 2026 10:28 UTC](https://discourse.nodered.org/t/human-generated-vs-machine-generated-events/102173/2 "2026-11-17T10:28:46Z")

</div>

I suggest using MQTT V5 User Properties for this. Add a user property {"source": "human"}, you can do that in the mqtt out node so it will not affect any existing flows as it will not change the payload value.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [17 November 2026 11:01 UTC](https://discourse.nodered.org/t/human-generated-vs-machine-generated-events/102173/3 "2026-11-17T11:01:22Z")

</div>

> [@no\_mpimpi](#):
>
> Since my system is based on MQTT, my current best idea is to include a value in the payload, eg: {"state": true; "source":"human"}.

Colin's approach is almost certainly the best. One thing to note about MQTT messages though. It is generally best to keep most of your messages as simple values rather than JSON. Use sub-topics instead.

```auto
sensors/dev001/temperature = 23
sensors/dev001/temperature/source = "human"
sensors/dev001/temperature/location = "Living Room"

```

It is also common to have multiple topics with the same data:

```auto
environment/temperature/living-room = 23
environment/temperature/bathroom = 20

```

These could also have the source sub-topic as well if needed though it might not be.

On the machine generated data, I often include where in my flows the updated data came from and when it was updated:

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/a/0/a094639a178ed2d6d9f9a4978f6acd2c1a0e7683.png)

---

<div class="post-metadata">

**Author:** ![ThingsTinkerer](https://avatars.discourse-cdn.com/v4/letter/t/91b2a8/32.png) [@ThingsTinkerer](https://discourse.nodered.org/u/ThingsTinkerer)\
**Post date:** [17 November 2026 11:29 UTC](https://discourse.nodered.org/t/human-generated-vs-machine-generated-events/102173/4 "2026-11-17T11:29:24Z")

</div>

Yes, we use node red to control over 100 ovens in a building. We have scheduled comfort temperature to apply for office hours, and lower temperature for evening and night. If someone manually adjusts an oven, they get one hour of grace period which will extend outside office hours if that makes sense. We don't use mqtt but http as the ovens are controlled via a cloud service. The main hassle with it is the oven producer doesn't set a flag for the source of the temperature change, so it got a bit complicated by storing latest automated commands in context and only changing temp immediately after reading status.This was to minimize overriding manual adjustments. They also have some lag up to 1-2 min which makes it imperfect, but all in all the risk and consequence of overriding manual inputs is minimal.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [17 November 2026 14:48 UTC](https://discourse.nodered.org/t/human-generated-vs-machine-generated-events/102173/5 "2026-11-17T14:48:58Z")

</div>

> [@ThingsTinkerer](#):
>
> the ovens are controlled via a cloud service

I do hope you have taken note of the recent Europe-wide fridge hacks? Many vendors who squeezed either cloud or local network controls into things have still not properly dealt with security.

> [@ThingsTinkerer](#):
>
> The main hassle with it is the oven producer doesn't set a flag for the source of the temperature change, so it got a bit complicated by storing latest automated commands in context and only changing temp immediately after reading status

Not sure that MQTT really helps in that situation anyway. You probably need the data in memory in any case if you need to track manual override times and reset to auto?

---

<div class="post-metadata">

**Author:** ![ThingsTinkerer](https://avatars.discourse-cdn.com/v4/letter/t/91b2a8/32.png) [@ThingsTinkerer](https://discourse.nodered.org/u/ThingsTinkerer)\
**Post date:** [17 November 2026 18:43 UTC](https://discourse.nodered.org/t/human-generated-vs-machine-generated-events/102173/6 "2026-11-17T18:43:37Z")

</div>

If the ovens are hacked, that would be a problem for the oven company who maintains their cloud service. For us, best we could do is shut it down by removing or replacing the access token. The damage is limited, by turning it down, people would come to work to a cold office (ovens are secondary heating for the building). If heated up, I don't know all ovens are a potential fire hazard regardless, but I think they're capped at max 30 Celsius.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [17 November 2026 19:13 UTC](https://discourse.nodered.org/t/human-generated-vs-machine-generated-events/102173/7 "2026-11-17T19:13:56Z")

</div>

> [@ThingsTinkerer](#):
>
> If the ovens are hacked, that would be a problem for the oven company who maintains their cloud service.

I think that your customers, landlords, insurers and more might just disagree. 😃 Depending on where the ovens are situated, there could be risk to life, surrounding buildings and more.

> [@ThingsTinkerer](#):
>
> The damage is limited, by turning it down, people would come to work to a cold office (ovens are secondary heating for the building).

Ah, I was thinking a bakery. 🤣

The worse case is overheated and overstressed buildings might cause fires. Certainly money would be wasted, from electricity if they are turned up, lost productivity if turned down. In fact, if forced off, depending on location and the contents of the building (anything temperature sensitive?), there could be permanent damage to other equipment or materials.

> [@ThingsTinkerer](#):
>
> I think they're capped at max 30 Celsius.

How? Is that a digital control or is it a physical one?

Unfortunately, it is the lack of people willing to think through the possibilities and to test them that causes incidents like the fridge failures across Europe. With that hack Millions of Euro's were lost, food went off and was unavailable. Also there was a loss of blood packs in France which might have cost lives.

These attacks used to be very few and far between but over the last year or 2, incidents have risen by several HUNDRED percent.

I will be amazed if we don't see loss-of-life and businesses going under and many law-suits before people finally take this more seriously and hold both themselves and their supply chains accountable.

Sorry, not getting at you personally, I don't know your circumstances. But Node-RED is often part of industrial IoT infrastructure and I personally feel quite strongly about it (having previously been involved with NHS national security). Getting the message out is more important than ever given the current state of the World.

---

<div class="post-metadata">

**Author:** ![ThingsTinkerer](https://avatars.discourse-cdn.com/v4/letter/t/91b2a8/32.png) [@ThingsTinkerer](https://discourse.nodered.org/u/ThingsTinkerer)\
**Post date:** [18 November 2026 09:12 UTC](https://discourse.nodered.org/t/human-generated-vs-machine-generated-events/102173/8 "2026-11-18T09:12:48Z")

</div>

These heaters are already sold to private and businesses alike, they are app controlled. A lot of home electronics are cloud controlled, from lights, heaters, heatpumps ++. We control electric panel heater / wall heater / convector heater. If it breaks, thousands will break, not just the 100 we got. They don't got our name on it, while we provide them and add functionality on top, I'm sure it can be communicated to our customer that the problem is with the manufacturer. If needed, we'd have to change brand and adapt code to new api. I think most if not all such heaters come with a max temp. The manual one I got at home won't go above 35. Perhaps biggest risk with electric heaters is if you cover them with clothes or something.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [18 November 2026 11:39 UTC](https://discourse.nodered.org/t/human-generated-vs-machine-generated-events/102173/9 "2026-11-18T11:39:33Z")

</div>

Just dealt with 2 more obvious AI posts.
