Ok, at the beginning I was silly. I didn't get all the quirks with MQTT and msg.error. I think I have moved forward from there but "it" still doesn't seem to be working. Though the long way, I'll start with knowns and work towards the error. That way it may help you see how I am confused rather …

[image] Trying_to_learn: I know it is not as easy but I think of things that I move the first value to the second. I think of it as being the same as a standard line of code : msg.payload = msg.error but written vertically msg.payload = msg.error Simon

Seems I did that silly ting with the CHANGE node. Rather than setting the msg.payload to msg.error, I was setting msg.error to msg.payload. Reversed the names and it seems to be working a lot better. Sorry. I shall again say that how the CHANGE node is worded is confusing as it isn't (to me) i…

Yes, but when you go to other options (can't remember now exactly) the layout looks ok. But to me, when I see the layout I get which is which reversed. I just looked and now it kind of makes sense, but maybe because the threshold has been passed. I hope I don't keep falling into that problem. B…

[image] Trying_to_learn: I know it is not as easy but I think of things that I move the first value to the second. But it REALLY sets the first one to the second one. Are you saying that you expect [Screenshot-2018-09-02-08%3A02%3A11] to Move msg.error to msg.payload If so what you expect…

That's where I fall over. In the first example, I see it as setting msg.error to msg.payload. In the second one - which is "more intuitive" (cringing at that) is that msg.error gets MOVED to msg.payload. But in the second one the direction of what is moved is the other way. I think I am too conf…

[image] Trying_to_learn: I think that will really help me. :slight_smile: I sympathise with your confusion - I thought it was just me! :slight_smile: Quite a few times I've struggled to debug something and its because I've done it the wrong way around I only get it wrong when using msg pro…

[image] Trying_to_learn: But in the second one the direction of what is moved is the other way. That is because the first one does not Move it Sets. I do agree that it could be improved a little. If Set changed the word before the second field, currently "to" to "from" so the Set screen re…

The way to improve it would be to make the change always the same direction. So if you say: MOVE A -> B Then: B = A. (But B is negated, or what ever) If you say SET A -> B Then B = A. Same Direction. But that's just me. Keeping things the same.

Forget about the change node for the moment. What would you expect to happen if I said Set msg.payload to 7

Yes, I get it here, now. But "SET" throws me - when used with MOVE. SET msg.payload to 7 msg.payload = 7. But I am getting what/where you are going. Just if I am silly enough to fall for it, who else could? So when MOVE is used..... argh, I give up. (cheeky wink) But thanks. I am startin…

And again more confustion about error handling

General

Trying_to_learn 2 September 2018 07:28 8

What "annoys" (or confuses?) me is that with the MOVE, it makes sense.

I MOVE a to b.

b = a

But with SET.....

I parse it as SET a to b Or a = b, when it is setting b to a. (Or have I got that around the wrong way? The more I think about it the more it hurts.)

Topic		Replies	Views
CATCH node. Does it really help? General	12	3401	18 July 2018
Help tracking this error - oops General	17	1073	24 January 2020
MQTT SOM/EOM message formats. Problems General	61	2703	20 April 2019
MQTT messages and getting back the original message General	30	1367	3 September 2020
Error detecting really not "working" General	8	795	27 September 2019

And again more confustion about error handling

Related topics