We had a powerloss yesterday and now all my dashboards are gone.
I managed to restore all flows from a backup file.
But where does Node-Red store data thats Dashoboard related, names, sizes etc
That’s weird… I’ve rebooted my NAS several times without any problems. Did you install Node-red using Docker? In docker you can export the complete image for backup.
Or you can export all nodes inside of Node-red in JSON format (Hamburger menu => Export => All nodes)
Rebooted the Ubuntu again, and now everything is back again ??!!
I have created an homey user for all members, but did not give them the app. And use smart present to switch the homey users home/away. Then also the cards last person left the house and first person to come home are functional.
Homey presence is send to mqtt (i thought I saw that)
Still getting errors (after replace the "), I think something went wrong in the split part
I entered on these positions and the import went wel, but no data (I changed the homewizard url) and getting the information in the debug screen
PROBLEM SOLVED: had to delete the . in the EDIT-JSONPATH NODE (on both cards)!!.. Thanks so far!
Hello Marc,
glad to hear it worked.
I just started with Node-Red, so troubleshooting is difficult.
Don’t know why you have to delete the . in the EDIT-JSONPATH node.
Awesome, I’ll look into that. How do you mean replace all flows of homey?
And btw, what do you do under teh “security” tab with all the locks. Cna you really lock the bathroom from there/ :O. Cool if yes, hahah. expensive as well?those locks?..
How do you mean replace all flows of homey?
With node red you can read en set devices trough MQTT. For example, turn the lights on when the light sensor gets below 20 lux. Almost everything you can create with flows, you can create with nodes in node red. You can create way more complicated structures if you want (which are not possible with flows). Going this route would make the Homey just a translator for every device to MQTT, and the node-red server the brains. I haven’t done this myself, I rather control my devices as directly as possible, but if I have a complicated task in the future, I might do this with node-red.
And btw, what do you do under teh “security” tab with all the locks. Cna you really lock the bathroom from there/ :O. Cool if yes, hahah. expensive as well?those locks?..
No, these are just window / door sensors. If I leave I can see all the open windows without physically need to go there to check.
Hi, my comment not adding value 
It looks absolutely stunning and sexy!
i’m unfortunately not talented enough for the manual / coding lines steps and will have to wait for a version for general audience 
i’m unfortunately not talented enough for the manual / coding lines steps and will have to wait for a version for general audience
Maybe the HomeyDash project will get a more widget style dashboard, but I don’t think node-red is going to get less complicated… although it’s not that complicated, if you managed to install the software on a server and go trough to the steps in my tutorial it shouldn’t be that hard.
How is everyone’s MQTT memory usage? It seems to be way less than I started this project.
The Client went from 38MB to 22 MB
The Hub went from 35 to 23,8 MB
(Don’t know about the Broker, I run this one on my NAS)
Dont know why, maybe the Homey 3.0 update.
I have a question, probably I do something wrong, but can’t see whats wrong:
If i toggle the switch from a lamp on the node-red dashboard, I see in MQTT Explorer that the topic is updated, but the lamp stay’s off. Like the MQTT client app in the Homey does not read that topic and/or react on it.
How does mqtt client know which topic to look in? I understand that the hub only sends the current status to mqtt and node-red is used to read these topics and set the values, but I don’t see how mqtt client then looks in the right topic and act on that.
What about LWT? Do I need to configure that in the MQTT client? And in the hub, should I enable that? And what topic paths should I use?
My config is Homey with MQTT client and hub apps. MQTT and Node-Red on a Pi3, and topics from Hub are published to mqtt and updated (including on the node read dashbard, when status is changed in Homey.
For control MQTT client looks in the topic used to report the status but with /set appended on the end.
So if the status topic is a/b/c/dim. The topic you update to change that value is a/b/c/dim/set
1 Like
Thanks, that was what I missed.
For users that are using the dashboard on an iPad or other tablet that want to lock / unlock (turn on and off) the tablet by Homey… For example controlled by a motion detector, or on during the day:
I’ve coded a firmware for a ESP 32 (cheap microcontroller). To emulate a Bluetooth keyboard. This way you can turn the tablet wireless on and off. A nice non intrusive solution. No need for soldering.
Playing with a Node-Red dashboard (Homey-Redboard?). My college is testing with node-red and I asked a homeydash a like background…
1 Like
Very Nice! This is my little project om Google nest
How do u arrange for a sensor to show, like water leak or movement?
Just use a simple Switch node, and change the on/of icon to a droplet or something. You can even change the on / off icon colour (see the locks in my dashboard)
Enable “Switch shows the state of the input” and attach the sensor MQTT signal to it (you might need to change the boolean string to a real boolean value. See the first (tutorial) post how to do that with a function node.)
I also have water alarms, I personally unhide a complete Group with a big warning if something like that happens.
3 Likes
oh, nice! how did you integrate a camera picture? can you share your node configuration?
Thank you very much, but I think there are some syntax errors in the code. Mabey you can use the “perfomattet Text”-function of the Forum?
