Page 22 of 22 FirstFirst ... 12171819202122
Results 211 to 218 of 218

Thread: My HGI80 equivalent Domoticz setup without HGI80

  1. #211
    Automated Home Jr Member
    Join Date
    Nov 2018
    Posts
    10

    Default

    Tried various OSs and none work with the UartSBee and RFBee. I might try with an old windows laptop.
    As regards RPi, which models have other people used?

  2. #212
    Automated Home Legend
    Join Date
    Jul 2014
    Posts
    1,608

    Default

    Are you sure you have the FTDI drivers loaded on your RPi?

  3. #213
    Automated Home Jr Member
    Join Date
    Nov 2018
    Posts
    10

    Default

    Arghhh! smacks head, kicks cat, swears fiercly: there are drivers?

    I'll look for them tomorrow.

    I don't remember adding drivers back in February for the windows installation.

  4. #214
    Automated Home Jr Member
    Join Date
    Nov 2018
    Posts
    10

    Default

    Quote Originally Posted by bruce_miranda View Post
    Are you sure you have the FTDI drivers loaded on your RPi?

    I can't tell if I have the driver or how to install it.

    I have installed Raspery Pi OS from Raspbery Pi imager v1.2.

    I have installed domoitcz using the command:
    curl -L https://install.domoticz.com | bash

    I have installed TeamViewer for a headless operation.

    Are the FTDI drivers installed with the OS?

  5. #215
    Automated Home Sr Member
    Join Date
    Aug 2017
    Posts
    68

    Default

    Looks like some activity on the rtl_433 project to decode evohome.

    https://github.com/merbanan/rtl_433/pull/1336

  6. #216
    Automated Home Sr Member
    Join Date
    Aug 2017
    Posts
    68

    Default

    Quote Originally Posted by Jabes View Post
    Looks like some activity on the rtl_433 project to decode evohome.

    https://github.com/merbanan/rtl_433/pull/1336
    Out of interest, I have run this up and it is decoding data. It's not in HGI80 format of course, but probably wouldn't be hard to whip into shape.

  7. #217
    Automated Home Jr Member
    Join Date
    Jan 2019
    Posts
    12

    Default

    Just thought I'd stick some findings here from my fiddlings with evohome and a cc1101 module as I was hunting for them without success so it might be useful to someone.

    My setup is a slightly old condensing boiler (Rinnai/Atag E32S) - it claims to support OpenTherm but apparently it's an old version so when I tried the OpenTherm bridge it didn't work.

    I'm using a slightly modified version of smar's evohome-Listener gateway to separate out some of the messages that are combined on the original script ( https://github.com/thigger/evohome-Listener )
    I use OpenHAB to listen to the MQTT messages and have an ESP8266 sat next to the boiler controlling a digital potentiometer over SPI. That digital potentiometer emulates an outside temperature sensor. So when I want the boiler temperature to increase I "tell" the boiler it's cold outside, and when I want a low temperature I "tell" the boiler it's warming up.
    The OpenHAB script takes into account the OpenTherm messages (they're still broadcast if you tell it you have an opentherm module even if there isn't one there) and the boiler relay messages, to try to keep the heat demand at about 80% (if it doesn't turn off every now and again then my boiler starts to ramp up the temperature) - and it seems to work fairly successfully.
    Happy to share details of the setup, though I imagine most people are using more modern boilers that support opentherm properly! (though even then my system avoids the issue of it ramping up to high temperatures every morning).

    My other work has been playing around with changing hot water settings. We have stored hot water from the same boiler. I wanted to run the hot water at a relatively economical temperature, but my wife complained that her showers were running cold too quickly (she's one of those!)
    I've switched my nano to evofw3 and am able to control the DHW in two ways by using these commands (send to evohome/gateway/command via MQTT)

    Code:
    {"command":"dhw_temperature", "arguments" : {"dev1":"07:016202","dev2":"--:------","dev3":"01:067930","payload": "000FA0"},"wait_for_ack":false}
    Where dev1 is the DHW sensor, and dev3 is the controller - tells the controller that the hot water has dropped to 40C. This causes it to fire up and it will stay on until it reaches the set temperature. This is useful when the hysteresis (differential) has allowed the temperature to drop, as it will now carry on all the way back up to the top of the band. When it gets close to the set temperature, the DHW sensor seems to send out more temperature messages which will convince the controller to back off.

    Code:
    Sets to 65:
    {"command_code":"0x10A0", "send_mode":"W", "arguments" : {"payload": "001964000000"},"wait_for_ack":false}
    
    Sets to 55:
    {"command_code":"0x10A0", "send_mode":"W", "arguments" : {"payload": "00157C000000"},"wait_for_ack":false}
    Changes the set DHW temperature (you can't change the differential). The important bit is the 1964/157C which is the temperature you're after, in hex, multiplied by 100. 1770 is 60C.

    Thought it might be useful to someone so leaving it here! Thanks for everyone's work on this - it makes a good system even better.

  8. #218
    Automated Home Legend
    Join Date
    Jul 2014
    Posts
    1,608

    Default

    Things have moved on quite significantly in the last few months. Have a look at evohome_rf if you have an HGI80 or combine it with evofw3 if you have a DIY platform.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •