search

rdmtc / node-red-contrib-ccu

Node-RED Nodes for the Homematic CCU
https://flows.nodered.org/node/node-red-contrib-ccu
MIT License
71 stars 13 forks source link

CCU different / changing Nodes with "unknown Datapoint" #146

Open guny74 opened 3 years ago

guny74 commented 3 years ago

Hello,

I have the problem similar to (https://github.com/rdmtc/RedMatic/issues/428#issuecomment-751259303), that have more and more "Nodes" not working. Getting "unknown datapoint" or shown at the node "0 datapoint".

After Rebooting mostly some different Nodes are working or not working.... Also changing the "context" store does sometime help, but it also could be that the working nodes changes I did noct see the defect nodes.

So more and more, my complete "smart home" logic break....

Current version 3.4.0 ...Redmatic 7.1.3... BTW I had the same issues on CCU Nodes Version 3.2.1

Any idea ?

Regards

baxerus commented 3 years ago

possible dub of #140

guny74 commented 3 years ago

Hello,

after switching to RPI4 and to 3.4.1 at the moment it seems to be al little bit better... so far I clould see at the moment, I have only problems with the "set value" Node (nodes have shown "0 datapoints")

I found a strange behaviour... I found out that (some) of the "problem" nodes are directly or indirectly behind a "CCU Switch" node (and yes I proofed it via debug node the switch-condition matches).

A direct inject node also does not help.... alsways "0 datapoint", but if I add an other node e.g. debug-node out of the node before the "set value"-node it works.... "1 datapoint" it works and after deleting the extra node...it work also....

But after "cleaning" the contextdata (reboot if you use memory as context store) or switching from file to memory, the same problem appears and the same solution have to be done....

This is only a "snapshot" during my try&Error to find a solution....but may be this would help for finding the issue...

Regards

guny74 commented 2 years ago

Hello,

After a while (not using the flow with these problem), I now switched to new "clean" system and switched to a actual node red instance. But I have also/again these problems, that randomly the nodes say "0 datapoint", then after next deployment of the flow (no change)... it works again sometimes...

Any Idea ?

just-grizzle commented 2 years ago

@guny74 How did you install Node-RED? I switched from bare metal installation to Docker recently and I discovered similar behavior. After I set the "Init address" of the ccu-connection Node to the host IP which runs Docker, everything works as expected again.

image

guny74 commented 2 years ago

@just-grizzle When writing this issue I used redmatic (Note red as an Addon on Raspberrymatic). There wasn't this init Address field. Now I rebuild my smart home to an single engine with Docker container and User node red. Also I removed a lot of CUxD "virtual" devices. But when I have this problem again, I will try with the "Init Adress Field.

Thank you

Wastl2IT commented 2 years ago

Same here ... when I change some configuration of "set value", it will work for maybe one or two times. Then, it always shows "0 datapoints". There is no difference in behaviour setting values like "channelName" or "datapoint" in the node itself or in the input msg. I'm using: debmatic 3.65.6.94 (on the same host as node red) node red 3.0.1 node-red-contrib-ccu 3.4.2

shred commented 1 year ago

Unfortunately, setting the init address didn't work for me.

I'd like to set the ACTIVE_PROFILE on my thermostat depending on my presence at home. As mentioned by the original reporter, it's working a few couple of times. But then I'm only getting "0 datapoints" reported on the node, and the thermostat profile is kept unchanged.

I'm also using many value CCU nodes. They are perfectly working fine, and keep on working. The issue seems to be related to set value nodes only. Because of that, I don't think the issue is related to my network setup.

For the set value node, I have only set a minimum:

The msg.payload contains the numerical value of the desired thermostat profile.

CCU connection node config:

Thank you for your help.

andesse commented 1 year ago

@shred where does your geofencing position come from? I would do the Program in the ccu and not in Node-red.

If your geofencing location comes out of node red, just use virtual switches that trigger the program or set the thermostat in the ccu.

Would this work? Even I have node red i would not run my thermostats there

shred commented 1 year ago

The geofencing comes from checking if my mobile is connected to my home WiFi. But it's just an example. I might as well check the outside temperatures, or read an iCalendar, to decide what profile I would want to set.

Virtual switches is a good idea. I will check if they'll do as a workaround.

But the set value nodes should work as expected. Otherwise, what would they be good for if they just work randomly? :wink:

shred commented 1 year ago

I now use value nodes instead of set value nodes for changing the active profile of a thermostat. It seems to work reliable, so maybe this is a valid workaround for other people with the same problem.