Node Red Experiences

0rn0lf · November 30, 2018, 1:59pm

Thanks, this was the solution
Sometimes its so easy

dave-castle · October 18, 2019, 3:54pm

I am currently thinking of realizing my heat-automation and turn off heating if there is an open window via node-red, are there any examples you might share? Thanks in advance!

sergi.suarezj · October 18, 2019, 5:10pm

Hi.

See this example. It checks if heaters are on if window opens. Then switch’s on a binary switch and switch off heater. When window closes checks the binary switch and if on then switches on the heater.

The origin of window opening closing is through deconz but you can do it with an event node the same.

Hope it helps.

Sergi

dave-castle · October 18, 2019, 5:44pm

thanks for sharing!

capstan1 · October 29, 2019, 9:23pm

Hi,
I’m trying to use this but I have no idea how to get the state of my aqara switches connected by deconz. I only ever used events, which you explain in the flow are unsuitable. Can you give me any hint here?

matteos1 · March 31, 2020, 8:43am

since yesterday, the current node does not give numerical values.
if I pass a value from a sensor it gives Nan output. can it be solved in some way?
I believe i’ve update some palette in Node Red

gregg098 · March 31, 2020, 2:14pm

There is a bug with the 0.22.0 version of the Home Assistant websocket node. The author put out a patch yesterday afternoon (0.22.1) that should fix this, but I have not tested it yet. You should be able to update this in the pallete manager.

bikefright · March 31, 2020, 4:24pm

I had this problem - I run my own node-red in docker not under the control of HA.

The upgrade did not fix this for me. I have implemented a “fix”, which works for me, which is to create a new HA server with the same Base URL and Access Token (effectively an identical version of the not-working one) and go through my HA nodes in node-red (a real PITA!!!) and switch them to use the “new” Ha server node!

~~So far, so good.~~

Sorry. Forget that. Too hasty in posting. After a short time, the same nodes that had the problem revert from (for example) state “heat” or state “home” to “NaN” again.

So this was NOT a fix after all.

bikefright

bikefright · March 31, 2020, 6:52pm

I reverted to version 0.20.2 of the HA websocket module via the CLI in my docker container as follows:

docker container exec -u 0 -it nodered bash
cd /data
npm install [email protected]

I then restarted my node-red container via portainer and all is good in the world again…and has been for over an hour

bikefright.

Nutti85 · March 31, 2020, 7:13pm

Just got to say Node Red has been a revolution to me. As I tried to make more complex automations with multiple conditions I found YAML and the automation config extremely confusing. I have no idea where the contributors are going with the config GUI but I think the current direction is wrong. It needs to be more visual, which Node Red is.

gregg098 · March 31, 2020, 11:27pm

You can do this without even going into the Docker container. For me, I map everything to /srv/docker. So Node Red is in /srv/docker/nodered. Then I do exactly what you stated above

cd /srv/docker/nodered
npm install node-red-contrib-home-assistant-websocket@<version>

matteos1 · April 1, 2020, 9:28am

same problem. also there is the issue

matteos1 · April 1, 2020, 9:30am

are you in hassio?

bikefright · April 1, 2020, 9:43am

@matteos1 No.

I run my own node-red docker container, not the hassio add-on. I think that is what you are asking.

bikefright.

matteos1 · April 1, 2020, 9:47am

yes i installed hassio i’like to repair my insallation of current state returning on previous version but I don’t know how…

bikefright · April 1, 2020, 10:23am

I’m not 100% sure how to do this.

I would reach out to frenck again via the github issue (I see you already raised an issue there) and reference the open issue on the node-red-contrib-home-assistant-websocket github node-red-contrib-home-assistant-websocket

Ask the specific question: “Is it possible to downgrade the HA websocket module within my node-red container installed from the add-on store? If so, how?”

bikefright.

bikefright · April 1, 2020, 11:19am

Sorry Matteo, I meant for you to either reopen your closed issue on github here: hassio node-red addon where frenck had already responded to you, or better still, raise a new issue but be specific about the need to downgrade.

I know you can specify modules to install within the hassio plugin on it’s addon configuration page, under the “npm-packages:” section, but what I don’t know is if you can specify a specific version of a module (like you can when using the CLI with an “npm install x@y” command).

I’ve just seen Jason respond that he believes the node-red modules are built in on the fly whenever you start/restart the hassio addon, so perhaps you could try specifying a version of the module in the addon config?

Look for the “npm_packages:” section of the addon config and add the following line so it looks like this:


npm_packages:
  - node-red-admin
  - [email protected]
  - any other packages already in the list

Restart the addon and check the node red palette to see if a) node-red starts? b) if it does, did it observe the specified version?

I strongly suspect however that the HA websocket module is installed under the covers and don’t know how the above config would compete/interact with a list of user specified modules to include upon restart - which will win? System or user? I don’t know!

Worst case you: stop the addon, remove the line from the addon config and restart the addon. You should be no worse off than you are now.

bikefright

matteos1 · April 1, 2020, 2:01pm

I found that by updating from the manage palette to the latest version of node-red-contrib-home-assistant-websocket, the current state node does not give exact values. I was wondering if there was a way for a way to downgrade the node-red-contrib-home-assistant-websocket dLL version 0.22.1 to version 0.21.5, which is the latest working version.
Of course, node red is a hassio add-on

FunkyBoT · June 5, 2020, 2:12am

Many thanks to this code. Very helpful for something that I could not do by myself. It works nicely alone, but when I integrate it to my other nodes (single touch, double touch), it interfers.
I believe that this happens because your code reacts to a single touch and it is over my knowledge correct this behavior (I tryed many things). Can you give some direction in order to the code react only for long pressing?
Only using your code, a single and fast press is enough for turning the light on, when it should react only when long pressing.
Thanks!

chimpy · June 19, 2020, 11:43am

Glad you’re finding it helpful Sorry for the delay in answering.

Here is an updated export: https://hastebin.com/awojujayiv.json

The input to Format Msg should be the long press hold and long press release events:

You can see in the image above that I’m listening to deconz_event, then filtering on msg.payload.event.id = bathroom_switch (in this case) then sending that to a switch node containing the switch values:

The reason that it’s is important to send both the long hold/release values to the format msg and dimming subflows is because they are transformed into on/off values that control the gate that starts/stops the dimming.