That would really screwup the new multiple thermostat feature of Thermostat Controller - which I have on my to-do list to try out..... Could @bcopeland or @bravenel comment? Thanks.
That's why I'm using only RM for TRV controlling.
Tried with TS at first, but when picking single TRVs out of the TS group and put a delay between their activation in RM I found that that in case of 3 devices the entire TS instance would fire for 3 times.
At least it was like that in the first versions of TS.
Hope you understand what I am trying to say.
Thermostat Controller will only work as well as the controlled thermostats work. It is simply adding a level of control on top of that base.
Yes.
But what @Mr.Olsen is saying is that commands being sent at the same time (or close to same time) to multiple FLiRS thermostats (which Aeotec/Spirit/Eurotronic eTRV's are) causes issues on the network.
So if using RM and a 6 second delay is needed between sending commands to FLiRS thermostats then this supposedly means that the new multiple thermostat feature in TC is not going to work with these FLiRS eTRV thermostats?
If this is true, then Thermostat Controller will not work, as it does not have any delays in between sending commands.
@bcopeland any comment from a Z-Wave perspective on this????
@bravenel any chance we could have a user definable delay in seconds between sending commands to multiple thermostats in TC? I would love to be able to control all my eTRV's using TC.
1 Like
Honestly, I don't know. That could well introduce a whole other set of problems, since TC has no control over when temperature events are fired. There's the potential for a real mess with this.
Groundhog day has come and gone........
1 Like
I dunno why the TRV;s would be sending multiples of the same report - unless they were getting sent the command asking for the setpoint report over and over..........
That I can't answer but there is only one entry in the device event log
Meine Damen und Herren,
ich darf Ihnen auch mein Driver vorstellen.
Es werden in voller Maße Funktionen unterstützt, einschließlich manuelle Kontrolle von Valwe-Position in Modus "manufacturer specific". Es ist einiges zu beachten: Modi tragen andere Nahmen. "heat" ist "auto", "energy save heat" ist "cool", "heat" ist "manufacturer specific". Also, damit die Kontrolle über Valwe-Position genommen wird, muss Modus "heat" gewählt werden. Später wird es korrigiert.
[Release Eurotronic Spirit Z-Wave Plus TRV · Aelfot/Aelfot (github.com)]( Aelfot/EurotronicSpiritTRV.groovy at main · Aelfot/Aelfot (github.com))
2 Likes
Still experiencing setpiont issues even with staggered times. Even noticed my MCO HOME MH17 thermostat with the built in generic z-wave thermostat it goes bonkers on occasion. Something funky going on with my c-5.
Switched on logging for all my z-wave devices now. I'm getting duplicates everywhere, so yes, something is wrong with my network. Tweaked the energy monitoring plugs, binned the cheap z-wave plugs which I can't adjust the energy monitoring. It's much better now but still duplicates but much less. All TRV's are now polled only. Just ordered a C7 to test all my thermostats as debugging on the c5 is non-existent.
1 Like
I had nothing but problems with zigbee trvs.
I now use thermal actuators. Don't miss a beat.
Totally agree and I have started using them But these z-wave ones have flagged up some issues with my network. Thermal actuators are the way to go if you have a socket near by and bloody quiet too.
I actually just run a single socket, 2amp fuse, branched to every actuator via junction boxes around the house. Tiny current, small fuse. No worries.
1 Like
Well... That looks interesting.
Would you mind talking me through your setup please? The graph looks awesome... But more importantly, I seem to struggle a little with getting an accurate temp in the room. My DHT22's always feel as if they're recording a lower temp than it feels.
I assumed this was down to placement within the room. I have found that, for example, increasing the height of the sensor location can make a considerable difference to the reported temp. I've yet to try to calibrate against say, a 'dumb' source. But also, I assumes it may be down to air movement within the room (I. E it's hotter closer to the rads and takes a while to acclimatise).
Here's a visual. My graph really needs some work. Essentially, the solid reds show when the actuator/heating is on. It appears that when the rad kicks in, the temp (oddly) actually drops for a bit.
The mechanics are sound - everything functions. But the heating control could be better and I'd love to understand it.
Edit
The graph is rubbish - need to have a better look at at. Wondered why it was showing as being 'on' through the early hours. My events show that this isn't the case. So I've clearly messed my hubigraphs up! =p
I'm using this app and it's brilliant. Using the temperature from hue motion placed on the other side of room. Then the built in scheduler. Charting is the classic influxes and grafana combo.
