what I have managed to find now is that, if I enable USB 3.0 support for my VM running HSOS then the HGI80 has stayed up for over 24 hours. I have no idea if this is coincidence or something else has allowed this to stop failing.

I am using a udev rule too. Mine looks like this. SUBSYSTEM=="tty", SUBSYSTEMS=="usb", ATTRS{idVendor}=="10ac", ATTRS{serial}=="TUSB3410 ", ATTRS{idProduct}=="0102", ATTRS{manufacturer}=="Texas Instruments", ATTRS{product}=="TUSB3410 Boot Device", SYMLINK+="ttyUSB-HGI80" the result of "udevadm info ...

I realise that this is a very old thread. But I have suddenly hit the exact same problem and wondered if you ever found a solution to keep the HGI80 working.

What he said

Hence why a Long Lived Token makes sense. You can provide that and be reasonably assured that it's a valid request made, because you generated the token. Much better than a User/Password that could be a result of a brute force or passphrase attack..So sits in between User ID/Password and 2FA.

Is it too difficult to implement a Long Lived Token in Domoticz, especially as other lesser secure methods are also available any way I.e. user ID and password? That way the user gets choice of what to use.

Why is the Long Lived Token any more or less secure than a User ID and password. Surely if the Domoticz owner is in control of the Long Lived Token, then its almost as secure, but less likely to be brute forced.

The new "security" version of Domoticz broke my previously running version too. The issue was that the new version doesn't play nicely if you have a db created from an older version. The result is that you simply cannot log in. The admin and default password don't work, the -nopasswd option doesn't ...

I've set the debug flag to on and recompiled everything. However I cannot get the evoraw.log file created, like I used to be able to in the past. What's the trick to get this going again?

Mods, could we move this thread to the newly created Evohome subforum?

Thanks a ton. Now let's hope we get some developers to notice.

I'm trying to see if we can build an Evohome community. I have a pretty good idea of the Evohome protocol itself. But am often lost at implementing any changes to Domoticz beyond the Protocol parser. I have however noticed that there are people who know a lot more than me. Problem is that on github ...

I've only just realised that the inbuilt functionality of Notifications does not seem to work for the Evohome Devices. They work for other devices within my Domoticz installation just not the Evohome created ones. I've not checked if the Evohome Relay devices have the same issue or not.

My device is being updated within the Domoticz code (SendAlertSensor) and not via a json call.

I've seen that message notification processing was added whenever the AlertSensor is updated via a json call. So does that mean that notifications don't work for devices updated via code?

I realise this is an old topic but how do I get Notifications to work on an Alert Sensor? I'd like to get an email whenever a sensor has a value of more than 0 I.e. No alert. I can get notifications to work on a Custom Sensor based on the Value of the Custom Sensor. But that same technique isn't ...

Sorry the above is not correct and you can test this yourself. Move the setpoint of your DHW to any other temperature besides 60C and you will see the graphs still show it as 60C. Infact the code, just sets the setpoint to ON/OFF, so somewhere in the Domoticz spaghetti of code that ON is being ...

No one know where the graphs pick up the hardcoded value of 60C from? I now know the command to get the actual Hot Water setpoint stored on the Evohome controller. But I am struggling to figure out how to implement that change in Domoticz.

I just took it out. More problem that it was worth tbh. Now to just get my PR merged in. Some PRs have been piling up for a few weeks now.

I just removed a feature to print a Hex as a binary string and everything worked fine. The log message will now print things in decimal itself.

I had closed it to work out what I need to do to fix things. But I have reopened it now again. This is quite a strange situation.