Sorry folks, little information to give, but if I don't ask the problem won't go away.
I have a flow that uses the samsung node to control my Samsung TV.
At given times it controls the channel.
Alas recently one of them stopped working.
Base line:
I have a few of these events and the channels change at their given time.
Recently one of them have stopped working.
I have 2 others that are also regular and today they worked.
Observations:
I have a similar thing which is more a remote control duplication on ANOTHER machine.
The even happens, nothing happens on the TV.
If I use the other machine to adjust the volume it works.
Then I go back and test the event again and it works.
There are no ERRORS just a message (which sorry I've since deleted).
--
Ok, I will have to try and remember to capture the message that is given next time.
Alas it may be difficult as I have an error handling routine but it doesn't capture anything.
I just see these messages in the debug list (right side of screen).
It just seems strange that it works earlier on that day, but at this specific time / event: it doesn't work.
Yet it used to work daily without any problem.
Update:
Ok after a bit of testing I got the problematic message back.
So as you can see it isn't being seen as an error.
Again: (as I can't really resolve an answer from the other thread) how can I catch those messages and then make things happen.
Ok, the latter part is my problem and I am sure I can deal with that.
But catching that message....
HOW?
Thanks.
(I'm doing it here now as it just happened and is hard to make happen to test it)
The ideal solution is to submit an issue on the node to get it to trigger a catch-able error.
If the node is not supported then maybe you could fork it and fix it yourself.
In the meantime they should appear in the node red log, so potentially you could tail that. On a pi, for example, they should be in /var/log/syslog.
Your next suggestions are above my skills.
So there is no way to catch the message with an existing node?
Ideally I only need to catch one of the messages. Not from all nodes.
As basically the <enter> is pressed at the end of a each sequence and is in them all.
You don't say which node you are actually using... and checking the flows, I can see 7 'samsung' contrib nodes listed.
Have you tried any of the others?
All node code is loaded at node-red startup, so you will have to start node-red. I don't understand why you bothered to even ask, would it not have been easier just to restart?