Just a quick question. Have you ever compiled Domoticz from the source code or do you always use the installer/updates? The reason that I ask is that it would be very helpful to actually have a log of all the messages picked up via the HGI80 from your system over a few days, but you have to ...

Hi, Thanks for all the detailed information it's really helpful, particularly as I don't have one of the HCE80 devices so my work on the Domoticz code for this device involves a lot of guesswork. I have some idea how the introduction of the controller ID might have caused the problem as this filters ...

Here's a post with an example of how to request the temperature log data from a device. It requests the daily values for the last month from device idx=9:

https://www.domoticz.com/forum/viewtopic.php?t=10027

Does this help?

Hi,

I think any value > 0 will trigger the boiler to fire for at least a few mins during each cycle. I think the BDR converts the demand into the appropriate on/off frequency of its relay.

Dan

Hi,

All the Evohome switch devices in Domoticz are read only and simply show their heat demand values (0-100%). The heat demand values do represent TPI (proportional control) and rather than the BDR showing a binary on/off value it reports these TPI values.

Hi, I'm developing some additional Evohome features as we've decoded more of its command structure, but not sure how best to integrate them into the Domoticz UI. An example is Backup/Restore functionality for the weekly schedule information via the controller. Evohome currently uses customised ...

Building on the information that Simon's shared I've now developed a couple of simple Python scripts to backup and restore the Evohome controller schedules via ASCII files. https://github.com/Evsdd/Evohome_Schedule_Backup https://github.com/Evsdd/Evohome_Schedule_Restore I'm not quite sure how best ...

Hi Phil,

Thanks for the update and I'm really pleased to hear that you've fixed your problem. It definitely seemed a strange one, I guess some weird part of the installation was corrupted, but very strange that it caused intermittent problems.

Regards,

Dan

Hi Phil,

I can't seem to reproduce this behaviour on my set-up (stable release 4.10717). JSON requests changing only the temporary until time (forwards or backwards) seem to be reliably accepted and the change is confirmed via the TCC app.

Regards,

Dan

Hi Phil, Thanks for explaining further. I'm pretty sure that the HGI80 just sends any correctly formatted message. The only exception to this is if you attempt to send far too many messages in succession, but this limit is something like a sustained 3-4 messages per second. This triggers the HGI80 ...

Hi Phil, Hmm, good question. I'm not 100% sure I understand though. You mentioned TCC in your last message, but any changes would only be visible here after they had already been confirmed by the controller. If you're sending commands via JSON to a specific device ID in Domoticz which is connected ...

Hi Bill, I believe that the time specified in your JSON query is sent directly to the Evohome controller, but I'm not 100% sure. If there's any difference between Domoticz & Evohome's time zones then it might cause problems. However, I wouldn't expect that this would cause a larger number of your ...

Hi Phil, I've done some testing sending regular JSON requests to make different temporary overrides to a zone setpoint separated by approx 30secs and confirmed successful result via the TCC app. I've tested this on the latest stable release 4.10717 and also my current development beta which is ...

Hi Phil, Just a couple of quick clarification questions: Does this appear to be a new problem in the current beta release ie. did these JSON commands work reliably in previous versions or did they also sometimes fail? Can you tell whether the setpoint change is actually sent by the HGI80 via ...

Hi, If it's more convenient to position your HGI80 remotely from your Domoticz server then a couple of linux options are ser2net or socat on the machine connected directly to the HGI80. The above examples show how to configure a ser2net port on the machine connected directly to the HGI80 and this ...

Hi Simon, Excellent detective work! I'll have a mess with the temperature field to see if there's any obvious meaning to the remaining bits. I'm still a little puzzled why some of my previous attempts at restoring using these messages might have upset the controller as they don't seem to contain ...

Hi Simon, Here's a bit more info. The following example is a 0x0404 message exchange which occurs shortly after startup between an RFG100 and a non-wifi controller 13/04/2017 18:55:06 045 RQ --- 30:060058 01:037519 --:------ 0404 007 00200008000100 13/04/2017 18:55:06 045 RP --- 01:037519 30:060058 ...

Hi Simon, The schedule information command is 0x0404. I need to update my EVOHOME_CONTROLLER.PY code in Github at some point as I did get a bit further with identifying and implementing more of the Evohome commands before I shelved this work. I was really using this program as a quick way to explore ...

Thanks Phil, I've had a look at the Domoticz Evohome code to try and understand why a permanent override might work, but a temporary one fail. There's actually no difference in the commands sent for these two types of override via the HGI80, just small tweaks in the parameters. So my first thought ...

Hi Phil, Do the temporary overrides constantly fail on your system or do they sometimes work? @akatar's problem does appear to be a total HGI80 message send failure based on the info posted to date, but some must work if permanent overrides work OK so it's going to take some time to fully understand ...