Receiving same event multiple times in a row

[robertinglin]

I have a couple Aeotec quad remotes in Homeseer which I'm using node-red to control
.

If I press scene 1 then run the report i get the last_change, however if I press scene 1 again and report again the last change value does not update.

I have the config set in homeseer to always update last change:


Homeseer does update when I press the same scene button but node-red doesn't receive/ignores that update so I'm not able to chain button actions.

Ideally I'd like to do things like "double click" or to enter custom codes to be able to expand the usefulness of the remote.

From what I see in the node-red-homeseer source code it looks like the webhook still only sends a devicechange event on status change even if the Last Change Time Updates on Status Change Only is unchecked.

Is this something that could be changed to always send a hook event?

[tenholde]

I'm using a device that when changes, triggers Alexa TTS to speak the status contents of that device. In order to get it to trigger everytime, the event I use first changes the status to "X" and then to the text I want to speak. This may trigger two node-red triggers, but I filter out the "X" trigger with a function node:

var status=msg.payload.status;
if (status==="x"){
return null;
}
else {
return msg;
}

[kenm]

robertinglin I ran into the same problem with the Aeotec Minimote. What I did to workaround it was to create an event in HS that fires on a device value change for the remote device and checks to see if the value is greater than zero. If it is, I reset the value to zero and set "last change" to FALSE to keep the zero change from going to NR. This insures that the next time a button is pressed, even the same button, the device value will change.

Let me know if you have any questions.
Ken

[robertinglin]

I ended up doing something similar. Created a counter and set the value to -count and checked if the value was greater than 0.

kenm would you mind sharing your node-red payload? I'd much rather clear the lastChanged flag

[kenm]

Hi robertinglin ,

Sorry for the late reply. I "disconnected" for a few days over the holidays. There isn't anything special in NR, since all the work is done with an HS event. The "False" in the script command keeps the reset to zero (Ready) from being sent to NR.

Let me know if you have any questions.
Ken