Node-RED nodes for hubitat

[fblackburn]

Thanks for sharing this example

I don't see how your flow will be better with msg.deviceId input. Can you simulate it and compare with a up-to-date version of hubitat nodes to show us difference?

Where do you plan to set your deviceId? In the presenceFaker node topic?

If you need to have all presenceFaker node, then adding a node for each device associated seems logical to me.

There are one node to manage presence and another to manager a device. If you mix deviceId in other nodes, it just complicate the flow (IMO)

If the command node will set the topic to its name, then it should simplify your flow? (no need to set topic on presenceFaker or using device node)

You can also merge all Date/Time Formatter

[cam.soper]

@fblackburn

Well, after some tests, it seems that Maker API does not decode URL for arguments, which cause you the space problem ( %20 )

As far as I can tell, they haven't made any changes since I ran into that issue. The problem would go away if they had a way to accept an HTTP POST, but since Maker API is limited to HTTP GET, we have to rely on URL encoding.

In my custom system, what I've done is I've created a really simple POST endpoint I can use for sending more complex messages to my speech devices.

[leeonestop]

I was using the Node-Red on the PI and decided to upgrade to the latest version of the Hubitat and when I did I get the following error and cannot do anything? Is there a way to fix this? Thanks

I get the following : Flows stopped due to missing node types.

hubitat config

[aaiyar]

@fblackburn @leeonestop

Confirmed - here's the startup error on Node-RED after updating to 0.0.19

1 Mar 11:38:09 - [info] Waiting for missing types to be registered:
1 Mar 11:38:09 - [info] - hubitat config
1 Mar 11:38:09 - [info] Server now running at http://127.0.0.1:1880/

[aaiyar]

@leeonestop

Is there a way to fix this?

The simplest way (for me) was to revert back to my last backup and then kill/restart node-red.

[Guffman]

Also experiencing problems with device event updates after upgrading to 0.0.19; looking at the "Edit habitat config node" properties panel, I see that an underscore is added to the Webhook configuration entry:

If I delete it, it returns automatically. Is this related to the flow no longer getting events from the device nodes?

[leeonestop]

Can you show me that Kill Command??

[aaiyar]

Sure. Get the PID for the node-red process using the command

ps ax | grep node-red | grep -v grep | cut -d' ' -f1

That will return something like this:

odroid@odroid:~$ ps ax | grep node-red | grep -v grep | cut -d' ' -f1
28415

where 28415 is the PID. Now run:

sudo kill -9 28415

That will kill node-red.

[aaiyar]

@leeonestop

Also - by last backup, I meant my last node-red backup. Not last hubitat backup.

[leeonestop]

I did as you suggested but it fail for me maybe I didn't a back up yet. Hopefully it will get fix or I will start over Thanks.

[aaiyar]

@leeonestop

I didn't a back up yet

Backups are not automatic. I have a cron script to backup my node-red configuration every night.

[leeonestop]

I just set this up today and saw an update to 0.19 and it started to act up. Once I get it back to working I will do a backup nightly thanks.

[aaiyar]

Here's the shell script I use - you'll have to edit the value of "backupdir" and "nodereddir" to match your installation ......

#!/bin/bash
#
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
backupdir=/mnt/backup/node-red-backup
backupfile=$backupdir/node-red-$(date +%d)-$(date +%m)-$(date +%Y).tar.gz
nodereddir=/home/odroid/.node-red/
#
find $backupdir/*.gz -mtime +30 -exec rm {} \;
tar czvf $backupfile $nodereddir

[fblackburn]

For those having issues with the new version:

From which version have you upgraded?
Can you export the hubitat config node?

@Guffman

, I see that an underscore is added to the Webhook configuration entry:

Have you multiple server configured?

[aaiyar]

@fblackburn

From which version have you upgraded?
Can you export the hubitat config node?

0.0.18

I don't know how to export just the config node?

[Guffman]

No just a single server.

[fblackburn]

I'm not able to reproduce your issues. Maybe is related to the Node-RED environment

@aaiyar

0.0.18

Which version and package (docker, etc...) of Node-RED do you use?

@Guffman

No just a single server.

If you try to remove these underscore, do it works or they come back?
If you cannot remove them, can you check if you have others configuration nodes: in the menu top right you have configuration nodes and you should see your config nodes

Do you have any output from the Node-RED server?

[aaiyar]

@fblackburn

Which version and package (docker, etc...) of Node-RED do you use?

v1.0.3 - no docker. Directly running on Ubuntu/Arm on an odroid xu4.

[fblackburn]

OK I've just installed a fresh debian with node-red via npm and I see one issue with dependencies

give me some minutes to test and fix

EDIT: version 0.0.20 published, should be available soon

[JasonJoel]

@Guffman

Also experiencing problems with device event updates after upgrading to 0.0.19; looking at the "Edit habitat config node" properties panel, I see that an underscore is added to the Webhook configuration entry:

If I delete it, it returns automatically. Is this related to the flow no longer getting events from the device nodes?

Same with me. Upgraded form 0.0.18 to 0.0.19. Every time I create a new webhook path, it appends a "_" at the end...

In my case, I'm still getting events, so the "_" may just be cosmetic...

However COMMANDS are not working. I see the msg going to the command block, and it spits out an output, but the end device in hubitat does nothing.

I'll wait for an updated version and try again.