Is there anything in the node-RED log when doing a deploy?
node-red-log
I set up my logging inside the settings.js... but where can I read those messages?
Depends on how you started node red and what operating system.
Just enter the above at the cmd prompt.
Alternatively, and maybe a better way would be to stop and restart node-RED, and watch the log.
node-red-stop & node-red-start
Search the forum. Lots and lots of questions and answers on this one
1 Like
I'm using node-red inside docker and did more than one restart on that 
So maybe the log files are located on a not persistant volume right now.
Aaah Docker!
I know nothing about docker installs, so I'll leave the discussion. Good luck!
hahaha 
Docker is fine so far.
What I tryed out right now. I exported my whole flow for backup and removed it.
Now I#m rebuilding it from the ground, maybe it was too much to handle for this one.
I'm having just 1 mqtt device now with one switch for the dashboard, that's it. Dashboard is loading instant now! Doesn't matter how often I hit the deploy button.
ok... It seems to be fixed!
Just recreation of the flow with multiple mqtt devices instead of 4 with following switches to get out 8 topics for everything... maybe that was what was not the best solution. now it is loading as fast as it should be and no flickering on the refreshbutton....
I know some of you won't like that way to debug... but was the easiest for me, just try and error
Thank you anyway! Will take a look at the timer thing now <3
When it was misbehaving was the editor window still responsive?
in firefox sometimes not!
then I opened Edge and Edge Chromium and the old Internet Explorer to verify that that was maybe a firefox problem. All of these later 3 browsers got a responsive editor but the same problem with the dashboard.
Sometimes my firefox started to block any interactions with the mouse, couldn't even close it without using the task manager.
Are you sure you did not have an mqtt loop or something that was hogging the processor. The change to the MQTT In architecture that you described should not have any noticable effect on anything, if it was functionally equivalent.
mhhh could be, that could be a reason why now it is working as intended.
but I'm relativly sure that I rebuild near everything (topics/switches) like I did before... just without all the switches to split my topics.
Obviously, if you wanted to, you could go back to your original flow and try disabling bits till at least the dashboard draws itself, even without data coming in. Having a look at the processor loading is worth while when there seems to be some sort of clog up to see if something is hogging it (run top in a terminal). If you suspect a possible mqtt loop then stopping the mqtt server will immediately stop the loop.
1 Like
my newly build flow looks bit cleaner now, so it wasn't that bad at all.
but I will keep it in mind for the future! Thank you all for the help right now and in the past!
Meanwhile there is also this node that may help with setting timers from the dashboard
(I've not tried it yet so can't comment as to how useable it is, or even if it does what you want...)
1 Like
hey guys, still stuck with my harmony right now.
I can get to a point where I'm pretty happy with switching on/off and doing those activities on my harmony but:
is it even possible to return a message with a payload = "on" and some objects? All in one message of course so I only need 1 function for that
f.e.
msg.payload = "on"
msg.payload.status = 1
msg.payload.activities = 123456789
?
No a payload canāt be both a string and an object at the same time
1 Like
wasn't the answer I wanna hear but now I know that I'm doing it right xD
But you could code things up like this
msg.payload = "on"
msg.status = 1
msg.activities = 123456789
1 Like
