If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
HGI80 hot water termperature no longer showing in domoticz
I think the message is 1260, and I see this in my log:
048 I --- 07:040114 --:------ 07:040114 1260 003 0016D1
Just spent a little while exploring the code on GitHub. I can see that these messages will be ignored. The code looks like it asks the controller to report the DHW temperature, which it isn't doing - or isn't getting a response.
I think my controller id is right - it is in the form 064e7d (01:151165) - I put 064e7d in the configuration. I assume if it was wrong I wouldn't see anything.
I think I need to get the domoticz debug messages... which look like they need a debug build.
Any ideas gratefully received but I've actually got work to do today so will leave it for now.
Well so much for work. Have spent a happy couple of hours this afternoon understanding the code. It seems that it ignores the temperature reports directly from the hot water sensor (which I can see, and copied above) - and instead makes a request of the controller to send an update.
However, I am not sure that any outbound messages from my HGI80 are being acted upon. I wonder if it is broken?
Talking directly to the device and sending a copy of the message I can see domoticz trying to send:
RQ - 18:730 1:151165 -:- 1260 001 00
...doesn't result in any particular response. Because I'm not sure in what format the other responses are meant to come I'm not sure if any of the outbound requests are being received... and that makes it difficult to know if they are not being sent or not being received :-)
I take it the HGI80 doesn't echo back? (when I send the command above I don't see anything)...?
Further investigation - connecting to the HGI80 directly, pulling the plug on it and putting it back in I now see echoes to my RQ responses! I guess the HGI80 had got itself into a funny state. Rebooting the raspberry pi didn't clear it, only dropping the power entirely.
So, I think we are up and running!
And I've learnt a lot about how to build domoticz, and how to talk to my evohome system - so that's a bonus!
Apologies for not responding sooner due to travel. The HGI80 can sometimes get into this state i.e. it rejects any message send requests if it gets too many requests within a short period of time. I'm not sure what the limit is, but I think it's part of the firmware and its wireless certification. As you found, interrupting the USB link and re-connecting seems to be the only way to fix it. Incidentally, I think a Domoticz bug a while ago which has now been fixed, caused a similar problem and it was only noticeable because temperature setpoint changes made within Domoticz were ignored.
Apologies for not responding sooner due to travel. The HGI80 can sometimes get into this state i.e. it rejects any message send requests if it gets too many requests within a short period of time. I'm not sure what the limit is, but I think it's part of the firmware and its wireless certification. As you found, interrupting the USB link and re-connecting seems to be the only way to fix it. Incidentally, I think a Domoticz bug a while ago which has now been fixed, caused a similar problem and it was only noticeable because temperature setpoint changes made within Domoticz were ignored.
Hi Dan,
Thanks for confirming my findings. Now I've found my way around the code I might be able to do some things with it! This situation looks like it is detectable - I now notice that when you send the 'RQ' it gets echoed back (in a slightly different format). It should be possible to check for this response and if not issued then give some assistance to the user.
I'm using the HGI80 remotely over a LAN, and there was no guidance about how to set it up in the wiki - not sure how to edit this but I used ser2net, currently set to logging. Can anyone just edit the wiki?
Are you using ser2net at the HGI80 end, and also at the Domoticz end to make a local PTY? If so, I committed some code to Domoticz about a year ago which may or may not be released yet (i.e. you might need to build from source if you're interested) which allows the Domoticz Evohome driver to connect directly to the ser2net TCP port, thereby eliminating the need for having another instance running locally. Doesn't directly help your situation, but allows the elimination of one more moving part! (And allows Domoticz to run inside Docker, which doesn't seem to allow the mounting of PTY devices, which was my actual use-case for developing this.)
Are you using ser2net at the HGI80 end, and also at the Domoticz end to make a local PTY? If so, I committed some code to Domoticz about a year ago which may or may not be released yet (i.e. you might need to build from source if you're interested) which allows the Domoticz Evohome driver to connect directly to the ser2net TCP port, thereby eliminating the need for having another instance running locally.
Yes, I am using the latest betas and these have an HGI80 over Lan option. I used this from day one as I have domoticz running on a virtual machine, and the HGI80 connected to an old Raspberry Pi in the centre of the house over powerline network. I didn't find any guidance for how to configure ser2net so had to take a guess which was why I was asking about how to update the wiki above - I assume it is either 'raw' or 'rawlp' (probably makes little odds now I've seen how the protocol worked - initially I was afraid it would require an 8-bit clean path)
I have noticed that too. Which is why I have abandoned this approach. I don't think a lot of people use it and so it hasn't been developed much. In my case I am lucky that my rack is built in the loft where my boiler is, so I don't need this.
Comment