People who signed up early didn't get the PDF.
P.
People who signed up early didn't get the PDF.
P.
This like very similar behaviour to the post I made a few days ago....
Andy,
Through this thread in response to some of the issues found such as the manual zone override postponing hot water reheat you've stated "yes we're aware of this, it will be fixed in the public release" etc, can I ask in relation to this;
1) Is the public release finalised yet or is it still evolving and being tested internally in response to feedback and testing ?
2) Will there be another beta or perhaps a release candidate made available to all the testers here before the final release goes out to everyone ?
The reason I ask about number 2 is that last time we participated in a public beta a year or two ago some issues were found, reported, assurances were made that the problems reported were fixed and the final release then went out to all devices and still had some of the bugs that had been reported, and no "release candidate" of what was going to be pushed to everyone was provided for any public testing prior to it being sent out to all devices.
In this current round of testing there are many very significant and visible bugs in the current beta, (far more than the last public beta) and as someone who does quite a bit of debugging and testing on a couple of open source projects the thought of going straight from a beta with many known problem with the assurance that they will be fixed to a full public release with no further testing in between by the public testers who originally reported the problems makes me extremely nervous from a quality control perspective.
Given the various issues raised I would ideally hope to see a further beta version during this beta testing period which addresses some of the issues raised, (and the version number published so people know when they have received the newer beta version) and/or at the very least a release candidate of the proposed public release a few weeks ahead of the general rollout so that fixes to the various issues can be confirmed under the same test conditions that they were originally found and any last minute or missed bugs can be found and reported before going public.
So can you elaborate on how far along the internal builds are relative to our current beta version, roughly how much longer the public beta testing program is going to run for (given we're coming into warm weather soon so won't be able to do much testing when heating isn't needed) and whether testers will receive further beta versions and/or a release candidate during the public beta program significantly before any update goes live to the general public ?
As owners of Evohome systems we all have a vested interest in seeing the next general public release of the firmware being as solid and bug free as possible.
Last edited by DBMandrake; 17th April 2020 at 11:07 AM.
Interestinghave taken the advice and reduced all my rooms by 1C and enabled cold weather boost with a +1C - sort of now makes sense as I was trying to deal with a few days a year rather than the majority. here will still be a few days when I need to add a bit extra to the temp during winter but those are minor and could easily be solved with a (dare I say it) variable ECO/Boost mode
![]()
Am I missing something re CWB as have set for all zones and all zones have temp requirement of 18C and yet only have two zones that have temp set for 19C and 20C have invoked CWB. So after adjusting down all my zones by 1C this morning, the lounge could do with the extra 1C but hasn’t asked for it? Just re-read the original email guide but cant see any exceptions other than zones set to 16C and below which none of mine are. Slightly confused ??
Cold weather boost only applies when the outside temperature is 10C or more lower than the set point. So in my zones that are set to 21C CWB kicks in when the outside temperature drops to 11C or lower, but rooms at different set points will have a different threshold.
There also seems to be a considerable delay after the conditions change before it actually takes effect, a few times I've though it's not working as the criteria have been met but when I've looked again 10-20 minutes later it has taken effect. So it's not recalculated every minute.