How would I make the word Move bold in the change node below, with Jsonata expression?
I'm sending it to a dashboard, and I've just added in the battery percentage, but the non-bold is affecting my OCD. This is part of a flow that auto joins my Sonos speakers to be based on motion sensor movements in their respective rooms.
Hey guys, I've been playing around with this palette in node-red and it's really great. I'm converting some of my rule machine rules and came across one issue that hopefully someone can help me with:
I'm trying to send a notification to the hubitat app on my phone when my doors are unlocked (with the lock name and the name of the person who unlocked it), but the "Arguments" field in the command node for deviceNotification doesn't seem to parse variables. I tried using msg.payload.descriptionText, msg.payload and a global variable. What am I doing wrong?
I am not 100% sure I understand what you're trying to do but have you looked at the Template Node? It allows you to take a bunch of different payload items and combine them into one and then output as msg.arguments for example.
Correct, it does not (at least not as far as I remember, I would never do it that way so haven't ever tried). Expand the variables to strings in a change node before the command node. Stick them in msg.arguments.
@erktrek Thanks for those links. I had spent some time searching for a passthrough type of node to reduce the number of connecting lines...couldn't find one and wound up using a switch node with a single 'otherwise' case. On that second link you sent there's a node listed under must haves that does exactly what I was looking for
Has anyone here used the node-red-contrib-apcaccess pallet with with UPS's in their setups.
I am playing with it using UPS virtual driver and this seems to work ok..
It is a bit chatty though. My virtual driver creates a command for each attribute so it can be updated. Is there an easy way with Node-Red to Consolidate a set of messages and make one long comma delimited string. I know it is probably a simple answer, but i can't seem to figure it out.
I bit the bullet and updated to NR 2.0.1 yesterday, and it created an issue with my http request/web scraping (keeping an eye on certain prices/variables on the web, and even internally in my home network - solar etc). Anyway, I posted over at the Node Red forums and they fixed it within about 4 hours. There's a fix coming in 2.0.2, but the workaround was to delete an offending node built old dependancies.