You could use an openhab get node triggered by the change of your alarm clock item that gets you presence and than a switch node which evaluates only this. That way you would have two nodes less but any way that works reliably is good
Johannes
MDAR
(Stuart Hanlon, UK importer of Velbus hardware)
210
I know that Scheduling is the holy grail that we all seek, so imagine my delight in finding this node
Now we / I just need to create some kind of way to put it into a GUI
Does anyone have any ideas how we can put the scheduling variables into a UI like this?
Update
I’ve asked Niklas if it would be possible to expose the scheduling part to a NodeRed Dashboard.
Yes great Node , there is an option to set to minutely output , so some things that needs to stay on just get on command each min, if its already on so nothing… very good for some critical house stuff, and provided some good workarounds hhh
I ended up using a combination of Jsr233 rules written in Jython and Nodered but I’m still loving Nodered especially for quickly prototyping stuff and how many 3rd party things you can quickly integrate without much setup. You will definitely have fun along the way.
Johannes
A question came up along the way trying to migrate my rules to node RED:
Is there an option to send a debug node output to a logfile (e.g. openhab.log)?
I currently use the debug nodes heavily to learn, but they obviously just log with the web interface open.
So I don’t know how to check logs later on, if something is nor working properly.
MDAR
(Stuart Hanlon, UK importer of Velbus hardware)
222
Have you seen the “File” nodes in the storage section ?
MDAR
(Stuart Hanlon, UK importer of Velbus hardware)
223
Hi
This just popped up in an email, I thought you might like to review it.
I installed the node flogger, stopped node red and started it again.
All my flows are gone!
Is there any way to get them back?
EDIT:
Got them in home/.node-red/flows_Homer.json
1 Like
MDAR
(Stuart Hanlon, UK importer of Velbus hardware)
226
I’m glad you’ve found some files to restore.
I did a quick search and found this, if I’m reading it correctly, NodeRed saves a backup of the files each time flows are deployed.
Search for the word “deploy” to see what I saw.
flows_*.json & flows_*_cred.json
These define the flows and any credentials stored for the flows. The * indicates that the actual file is named after the machine name you are running on. If you have transferred from another machine name, you might have multiple files though only one set will be active. In addition, there are *.backup versions of these files. Node-RED copies the old active flow/cred files each time you deploy.
i was lucky enough to find node red before i started any rules on my setup, i was in the early stages of understanding OH, and then node-red came , and this got me real amped up
from controlling just some MQTT devices ,my entire house is node-red based
i use OH dont get me wrong OH is the best for
,DB, logging , cloud ,site map , for the great REST API, and it is so stable!
but my all logic is there and i love the simplicity
i can tell you i switched my setup many times but with Node somehow its fun! and worth it
if you need help i am here…
also dont forget if it dosent work in OH you can always try the Node red way, it provided me some flexibility, and allot of workarounds !