Newbie to Node-Red, seasoned on Hubitat. Trying to tie them together. I went through the tutorial and built the 2 new floods and reviewed the User Guide, but I can't seem how to launch the Hubitat config node.
The hubitat config node is abstract, you cannot add it to your flow like other nodes. It's only a configuration shared between nodes. When you add a node (ex: device node) then you have a server field and this server is the config node. It is automatically deployed when it exists
You can view all configuration nodes with the following menu:
I am now completely off the alexa2 palette (in fact it's uninstalled). Used the Alexa Media Player integration in Home Assistant (HACS) instead and reworked my flows.
Of course this method says it uses the "experimental and unofficial Alexa API" so at some point this will break too lol
It breaks regularly, and requires regular updates which is why I Was just starting to look at the alexa2 palette when I saw your post. I have a flow that makes a random announcement based on who gets home. I'll get home, sit on the couch and start watching tv then it clues in that I didn't hear Alexa greet me. Hop on to HA and there's an update for the integration. Update it and all works again, it's just a little annoying. I'd say it's about 95% reliable which is around 4% too low for my likings.
Does anyone know of a method to backup the Hubitat nightly backup to a network share. I can backup to a directory on the Node Red device (pi/Odriod), but seem unable to backup to my NAS/network share.
While I'm not a fan of his actual javascript coding style, you could definitely apply what he talks about in his post using the flow you got off me
Lots of factors though, first and foremost: "what OS is the target for saving?". Obviously if it's Windows or Mac you'll need to set up the permissions differently. And secondly, what/where NR is running (inside Docker? out?) is a factor as well to set up the mount
This sounds like somebody should make an app to automatically send these backups to google drive. If the files are accessible on the hub then it shouldn't be too dificult.
A couple of months ago, I found someone that posted a flow that will backup files to a Dropbox folder. I don't know how it works in the Function Node. I can share the flow if anyone is interested. I would assume that someone smarter than me could figure out how to tweak it to upload to a Google Drive instead.
How are folks "running RM actions" via node-red? My thought was to make virtual switches for the actions and continue to have RM do the work but via a subscription to a virtual switch vs. being called from another RM action; perhaps I'm looking at it all wrong. Things I'm doing in actions that I can't do through MakerAPI (at least I don't think I can): running setFollowSchedule() for thermostats, also doing some custom HTTP calls to run the vacuum (with a charge action that cancels the clean action). I guess I could probably do the vacuum calls with http get nodes, but the cancelling actions would be new in node.
I am going to go out on a limb and say you can do anything in Node Red that you can do in RM; probably without adding virtual switches. If setFollowSchedule() is a command available to your thermostat, then you can do it in Node Red. Also, there is an HTTP Request Node in Node Red.
I am not sure what you mean by
Post one of your rules and one of us can probably help.