-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reduction node not turning off the heater causing grid tariff level to break 5 kwh level #145
Comments
I have an idea. You are sending the output from the However, since you are still having the Normally you would not use |
Thanks for pointing that out. I discovered that when I was copying the json, and changed it from Schedule merger to Lowest price, as I changed my setup earlier to Lowest price strategy node. So many things that are needed to change when changing strategy node :) So you are saying that I should only be using either override on the strategy node, or use the Perform action? Maybe this should be a bit more clear in the documentation? |
It is:) just didn't see it. But how is this explaining why reduction node did not send out anything on its outputs when it broke the 5kwh limit? This has worked fine in most cases, it turns off and on the device according to the limits set up. |
Sorry, I cannot tell 🙄 |
Maybe this is your problem too (issue #146). In the code for reduction action, the consumption is divided by 1000 ( Anyway, I recommend you use a sensor for the consumption, if you have one, or else it will think it is always using 3 kW, and will turn it off even if it is not using anything. |
I only have a sensor for the current consumption (in watt) being used, so when it's not using anything the sensor would return 0. Is this the sensor I can use? I don't have a problem that the actions nodes doesn't trigger at all, it's just that some some hours they don't trigger when they should. The variable called "actionTaken" is set to true when Reduction action node triggers, and reset again when Reset Action node is triggered. In the screenshot from my initial post we can see that the reduction action node was called at 00:05, and the reset action was not called until 04:18 UTC (very long time between these). This means the variable should be false and not prevent the action from being called between 4-5 GMT+1. reductionRecommended was also higher than 0. I don't have a sensor for alarmLevel so can't look into the history for this one. I will add one as this is the only one left that could prevent the action from turning off the device. |
Thanks for the tip for reset the reset action node :) We'll see next month if it works better or not:) |
My complete setup is earlier described on #128
This night from 04-05 I went from an average of the 3 highest days at 4,7 kwh to 5,2 kwh. I identified that the reduction node was not called.
First a screenshot of a graph showing that:
The screenshot below is showing the logs from reduction and reset actions. No reduction action was sent during this hour.
I'm also catching any errors thrown by the reduction and reset actions to file, but none was logged.
Is there anything that can explain why the device was not turned off when required power reduction was very high?
for reference, the reduction node "On Start " tab:
The text was updated successfully, but these errors were encountered: