I don’t think you have to reduce at all. My understanding is that you set the hours to run during the period between list_peak_hours_periods_start and list_peak_hours_periods_end in the configuration and the system will keep track throughout that period. You can change the hours in the middle of the period and the system will adjust for the remainder of time. That’s my understanding.
I do this:
So if the day starts sunny I set the hours depending on the season and that stays static throughout the day unless it clouds over, then I stop the pool pump altogether.
Hey Robert, I thought those variables related to energy cost from the grid, rather than time windows for when a deferrable load should operate. I supply a list of half hourly prices (based on my tariff) for how much energy will cost from the grid.
In theory it might completely roll over to the next day but in practice I find that it doesn’t. AEMO posts the next 24 hours pricing at 1230 AEST each day so I find I get consumption in the morning and then if the prices are really low the next day they will occasionally stop and roll over to the next day. Which for a pool filter pump isn’t that bad if it does 3 hours one day and then 6 hours the next.
The other thing I do is just schedule when the feed in price is extremely_low (negative) and the general price is less than 5¢/ kWh so basically nothing. As a consequence my pool is currently up at 34°C
Yesterday the pool sucked 51 kWh and it cost me 26¢.
I’m experiencing the same issue. I would like to have a certain def load be starting in the next x hours, while the rest will remain the max of 24 hours forecast.
Today for example my boiler will not heat today because the price for 02.00AM tomorrow is cheaper.
Only option right now is to adjust the prediction_horizon right?
If you’re using MPC, can you implement a template that increases the hours (def_total_hours) during the period of time that you want the boiler to operate then reduce the hours afterwards?
Not an expert in dedicated EMHASS containers but I enabled logging for RESTful and shell commands and I see something more in the log. Maybe helpful, maybe not, but something to start with:
Yep, I have this setup. When I get into the high CPU state I get timeouts on the naive-mpc-optim action. This is with the timeout on the rest_command increased to 30secs.
Just getting started with EMHass - loving this project so far. I’m just seeing some behaviour that I’m not sure is as a result of me doing something wrong.
My setup:
7.5kW rooftop solar
10kWh battery
Amber electricyt with wholesale dynamic prices
No deferrable loads at the moment (need to get a new switch for hot water system first)
I basically want to export excess electricity from my battery when feed-in tarrifs are favourable (usually around 7-8pm in the evening.
Today I noticed that in the morning my EMhass optimization was looking good. It was forecasting to export to the grid from the battery around 7pm. However as the day went by and I kept closer to this date it now no longer seems to suggest this and instead has a massive export spike in the middle of the day tomorrow when there’s negative feed-in tarrifs.
I run an automation every 10 minutes to update the latest amber prices via MPC.
Would love to understand why that is. I don’t understand the spike in the middle of the day at negative rates, and no export at 7-8pm when there’s good feed-in tarrifs.
Check the optimization status in the add-on logs: feasible/infeasible?
Setting the total number of operating hours for deferrable loads to zero can be sometimes problematic.
If you have an infeasible problem then set the operating hours to some vale but the nominal power to zero.
I have been very interested in being part of this project but unfortunately I have SMA inverters which is holding me back.
According to SMA I cannot take control of switching my inverters output levels. This sounds weird to me because if the grid connection goes down my inverters will switch off. I have argued that all I want to be able to do is exactly that at the time that I choose. Computer says no.
Any ideas?
Pat
Patrick, I assume you are specifically talking about controlling site export? This is normally of benefit when you are on a retail electricity plan that has wholesale market price exposure - like Amber.
My experience here has been that most inverters require “installer credentials” to change this part of the configuration. If you are in Australia part of the reason for this is too much export can have local grid voltage impacts.
