The core is the Fibaro Smart Implant.
This is used to control the relays for the pool pump and the pump for the solar heating. Connections for three temperature sensors and two solar heating pumps are available and a socket for the pool pump. I also installed two buttons to switch the pumps manually.
What is still missing is the corresponding automation. I imagine the following:
The pool pump should run on a timer for a few hours a day. That shouldn’t be a problem.
The solar heating pump should only run when the temperature in the hose heating is higher than the water temperature in the pool:
For example:
If (temperature of solar hose heater) - (temperature of pool water) > 2°C then turn solar pump on
If (temperature of solar hose heater) - (temperature of pool water) < 0.5°C then turn solar pump off
In my opinion, this can still not be mapped using an Automation MeshBot at the moment. Maybe someone at Ezlo can tell me if I should wait for it. Otherwise, this would have to be done via a corresponding LUA script. Unfortunately, I haven’t seen an example of something like this for the Ezlo controllers.
Here is what you can do with the existing system to make it work:
We introduced expressions with references to device values.
You can create a new expression with a reference to pool water temp + 2 (difference you want) like this:
Next thing I’m trying is to create the corresponding dashboard. I’m thinking of the following elements showing at this page:
temperature of the pool water
temperature of the solar heating water
temperature of air
local weather (US only at the moment?)
switch for the pool pump
switch for the solar heating pump
a tile where the desired maximum temperature of the pool water can be changed
The first six points should be doable (although I am struggling a lot with setting up a dashboard or tiles). As for the last point, I imagine it as follows:
There is a kind of temperature wheel like the thermostats where you set the maximum temperature. This temperature will be taken over in a Variable that can be added in the previously created MeshBot Automatisations.
Hi @Odysee , we are updating our docs for dynamic dashboards. But will be happy to assist you on creating. I will DM you. For now we don’t support a value set via the dashboard to a variable.
I just had an idea about the pool project. The pool pump has to run about 4 hours per day to circulate the pool water twice. But this formula only applies at low water temperatures. The higher the water temperature, the longer the pump should run. I have now imagined the following process, which I would like to carry out with Meshbots:
Pool pump runs 2 hours in the morning and 2 hours in the evening when water temperature is lower than 20°C
Pool pump runs 2.5 hours in the morning and 2.5 hours in the evening when water temperature is between 20°C and 25°C
Pool pump runs 3 hours in the morning and 3 hours in the evening when water temperature is between 25°C and 30°C
Pool pump runs 3.5 hours in the morning and 3.5 hours in the evening when water temperature is higher than 35°C
So after 7:00 am when the temperature is between 20 and 25°C the pool pump runs for 2.5 hours. Although I’m not quite sure at this point what “between” means. Does it mean 20°C > x > 25°C or does it mean 20°C >= x >= 25°C? What expressions do I have to take so that I don’t trigger any action at exact temperatures like 20.00°C?
We are excited to see good use cases of our powerful meshbots !
the between operator in the comparison includes the min and max values so its like minvalue <= x <= maxvalue. You can design your comparisons according to this.
And for your use case, I can recommend another feature which we will be rolling out next monday, Exceptions.
With exceptions you will be able to create additional trigger blocks for each and every action. In your example ;
You will be able to create only one meshbot for all of your temperature comparison cases. That way it will be constructed properly in a single meshbot.
Exceptions wont be a trigger for the meshbot, they will only be conditions for that particular action item to execute.
So stay tuned and we will create a nice use case example together for your automation needs.
I’m excited to see what we’ll do with it next week. Would be really cool if we could summarize the many MeshBots.
Until then, however, the individual MeshBots would still have to run. Unfortunately I noticed this morning that the pump was not switched, although all conditions were met:
