You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's entirely possible that I am misunderstanding how the "Ability to control via simple topic commands" (as described in the README) is supposed to work. Here's what I expect to happen. Let me know if I've got it right: If I connect an injection node with the topic set to (for example) list-all-dynamic, the Command responses only output should spit out the information about entries in the dynamic schedule. However, either I'm incorrect about that, or there appears to be a bug? I tried with and without a setting for the payload in the injection.
I made a screen recording to demonstrate what I tried. Did I do something wrong or am I misunderstanding how it's intended to work? I updated to the latest version (from 1.4.0 to 1.4.2) and restarted node-red to try this before submitting this issue.
Hi again @Steve-Mcl,
It's entirely possible that I am misunderstanding how the "Ability to control via simple topic commands" (as described in the README) is supposed to work. Here's what I expect to happen. Let me know if I've got it right: If I connect an injection node with the topic set to (for example)
list-all-dynamic
, theCommand responses only
output should spit out the information about entries in the dynamic schedule. However, either I'm incorrect about that, or there appears to be a bug? I tried with and without a setting for the payload in the injection.I made a screen recording to demonstrate what I tried. Did I do something wrong or am I misunderstanding how it's intended to work? I updated to the latest version (from 1.4.0 to 1.4.2) and restarted node-red to try this before submitting this issue.
Here is what I see:
https://drive.google.com/open?id=1ifA3nP7oKxjfwuN8fer40pwGvzEMJIe5
The text was updated successfully, but these errors were encountered: