Reply With QuoteWonder if it is something to do with the wifi Control Panel as it is only since installing that this problem has arisen although all was fine for the first few months. Since my last report on the problem it has not happened again.
Since getting the new wifi controller, I have had two Loss of Comms with the hot water sensor - about a month or so apart. The fault last night was in the quiet hours and the sensor is reading normally now. Batteries were changed a couple of months ago. My sensor is just over 2 years old.
Wonder if it is something to do with the wifi Control Panel as it is only since installing that this problem has arisen although all was fine for the first few months. Since my last report on the problem it has not happened again.
Mine is pretty random. It goes and comes back, all by itself.
I wonder what happens when the panel loses contact with a device, does it stay in the state it last was (on/off) or does it switch off as a fail safe.
With my boiler target temperature being set by Opentherm, i wouldn't want the HW to continue heating all the way to 90C just because the panel lost contact with the thermostat.
Good question. In my case when the Panel lost all contact the hot water was in off mode so can't answer it. Perhaps someone in the forum can.Originally Posted by bruce_miranda
Since moving to the new WiFi controller, I'm getting exactly the same. Random losses of connection to the Hot Water sensor. Nothing has changed.
Have to say my HW sensor over last few months has been erratic in it's reporting.
I capture all the data and store in a sql db so can see there is no regular reporting of HW temp. Sometimes it's small 5 min increments and other times only once an hour - and the temp moves a lot between 48 and 60C.
What is the 'official' reporting frequency of the HW sensor to the main Controller and then onto the Honeywell Servers ?
Mine reports every five minutes:
12/08/2016 08:25 53.6
12/08/2016 08:30 53.6
12/08/2016 08:35 53.6
12/08/2016 08:40 53.6
12/08/2016 08:45 53.6
12/08/2016 08:50 53.6
12/08/2016 08:55 53.6
12/08/2016 09:00 52.6
12/08/2016 09:05 52.6
12/08/2016 09:10 52.6
12/08/2016 09:15 52.6
12/08/2016 09:20 52.6
12/08/2016 09:25 52.6
12/08/2016 09:30 52.6
12/08/2016 09:35 50.8
12/08/2016 09:40 50.8
12/08/2016 09:45 50.8
12/08/2016 09:50 50.8
12/08/2016 09:55 50.8
12/08/2016 10:00 50.8
12/08/2016 10:05 50.8
12/08/2016 10:10 50.8
12/08/2016 10:15 50.8
12/08/2016 10:20 50.8
P.
Since my last posting here I have only had one reporting of failure to contact the HW sensor. It was after one o'clock in the morning and restored itself 58 minutes later. I have no explanation but it seems that with others having similar issues the current control panel may be the cause.
Done some more digging and debugging.
The DHW is always included in the data array coming from the Honeywell servers, but it's the temp that is 'odd'.
It sometimes will stay on the same temp for over an hour - to 2 decimal places. ie: 58.71
and will suddenly jump down/up several degrees to the correct temp (have other sensors available).
Considering it's 2 decimal places it should move on every 5 minute update.
Connectivity between the DHW sensor and wifi controller is good with only 2 lost contacts in last 3 months.
Anybody got comments or ideas as to what to have a look at next to get better reporting?
I have had a further loss of comms with the HW sensor. It has still not restored itself - 48 minutes later. Can any of the Honeywell Evohome team ( or Richard @ The EVShop) suggest what might be happening here? I replaced the sensor batteries and carried out a full re-set last time this happened.
Edit:
Self restored after 50 minutes.
Last edited by HenGus; 18th August 2016 at 02:48 PM.
Posting Permissions