No, unfortunately it uses a cloud API.
Not sure how illegal it would be to hack the ESP8266 inside their product to connect directly (which would be awesome) but I don’t have these skills anyway.
You don’t use Zwave ?
I validate the heatzy that I already use to control floor heating / radiant panels (on the ceiling). When I bought the house there was a fairly old Delta Core energy manager with 3 zones. I kept only zone 1 (the two others, for radiators, were poorly distributed) by putting a heatzy in the place of the manager. It works just fine.
But for the radiators, if there are a lot of them, I find that the Shelly are more practical because 5 times cheaper and you can hide them in the wall boxes…
@Shaad I found on the forum a code to reverse the shelly command (not yet tried because I haven’t installed them yet) :
switch:
- platform: template
switches:
switch_state_revert:
value_template: "{{ is_state('switch.your_switch', 'off') }}"
turn_on:
service: switch.turn_off
data:
entity_id: switch.your_switch
turn_off:
service: switch.turn_on
data:
entity_id: switch.your_switch
Ahah, thanks. I’ve made a switch called ‘Mode ECO’, so I don’t need to swap status.
When I said I would prefer that it works in the reverse way, I meant that I would have prefered the heater to be in ‘Mode ECO’ when fil Pilote was not receiving any input, and switch to 'Mode CONFOR’T when it receive 230V because Shelly modules tend to be hot when they are ON.
Ah damn, not reassuring this story of heat. Were you able to take temperature readings?
Yes, all Shelly modules report their internal temperature, as well as an overheating alert and an overconsumption alert. They are really nice but sometimes get a little bit hot, always under the overheating alert threshold but still hot.
They’re known to get a little hot. At least it’s not as bad as the Sonoff’s, who are infamous due to their tendency to catch fire. Did you flash Tasmota onto the Shelly ? There’s a bug in certain versions of Tasmota that created essentially a short circuit in the Shelly MCU due to an incorrect pin assignment, making it heat up a lot more (and probably damaging it long term). See here. Make sure to update to the latest version. Or just use the original firmware over local MQTT.
By the way, regardless of what method you use to send the fil pilote orders, since the protocol is unidirectional and inherently multicast, you can use a single control module for multiple heaters. Just connect the fils pilotes of pretty much as many heaters as you want together on a single module, as long as they are on the same circuit breaker. I use a Qubino per zone, not per heater, with up to 3 heaters together on the same module.
Thanks, I’m using the original Shelly firmware and MQTT.