Open MRobi1 opened 4 years ago
Hi @MRobi1 Can you please give me more information about your flow. Are you using blindcontroller node or the multiblindcontroller one ? Are you using it in a subflow ?
To be sure everything is clean, you may have to delete the "blinds" global variable in NR.
With more info, I could take a look at this.
Yes it is still in development :)
Using blindcontroller node Not in a subflow
Just tried clearing the global variable and still getting the same "undefined%"
EDIT: Thinking out loud here... case "weather": sunPosition = msg.payload; weather = msg.payload; runCalc(node, send, msg, blinds, sunPosition, weather); break;
Sunposition is sent from the sunpos node directly to the blindcontroller node. For weather, I pull 2 current state nodes to get the temp and cloud conditions, run it through a join node and into a function node. This outputs msg.payload.clouds and msg.payload.maxtemp. The payload coming in with a weather topic doesn't have sunposition at all.
Ok to be honest, I only use the multiblindcontroller because I inject its config from Home Assistant data. I will test the simple one. I think there is a little bug in it. Can you say me if it is when it receives a Sun Position node?
This bug is still remain. Now it is a blocking issue to use this V2.
This bug is still remain. Now it is a blocking issue to use this V2. Probably not the best spot to suggest this, so I apologize in advance.
I started using node-red-contrib-sun-position. It's a little complicated to setup, has it's own build-in rules engine for over-riding blind position, and has been super reliable.
Hi. I´m also getting the "undefined" position error. Any clue on how to circumvent this?
I'm having the same error...
Same issue here...
Same error here. Any update or fix?
Giving your version a try since the original was giving me issues with inverting the 0/100 position. Even with "0 is closed" checked, it would set the blinds to 0 with a reason of "sun not in window".
This worked fine this morning, however with the update from an hour or 2 ago it now gives an "Undefined%" error.
I'm sure you're still under development but if you need some testing done let me know