Understanding the rbe node

I've programmed a flow for turning on and off the TV using node-red-contrib-bravia. Since those nodes don't return a status change and this is a device that often is switched from it's remote, I implemented an automated check every minute. I don't like filling the network bandwith with pollings, but I didn't found any other way.

So every minute, an api call with a request for status is sent. As I don't want to needlessly refresh the dashboard and other interfaces every minute, i've put an rbe node at this output.
But the rbe doesn't pass any message, and as simple as it seems, I can see what's wrong.

So starting from TV off, status off been sent trough the rbe node, I turn the TV on manually. Afer a minute there's the poll and this message it's injected:

topic = ""
msg.payload.status = "standby" (that was "active" a minute before)

But the rbe output debug node doesnt reply. Do I miss anything? Could be the topic being empty the cause?

Well, I've changed the topic of the response to "anything" and the rbe node has started to work.
Could this be considered a bug?

What mode did you use for the RBE ?

"block unless value changes"

i also did not find it work...
or did not understand its purpose for "block unless value changes"

Upon deploy of your flow, should it ignore the initial value ?

@aihysp - this node is used to block/let through of repeating messages based on the same values or values that are within a certain range (% based)

If you have a flow that constantly produces the same payload, it might not be interesting to have it pass through your flow, but only when the value changes.

Nope, it's supposed to take the initial into account.

This should work


If it doesn't, which version of node-red, nodejs and npm do you use ?