Results 1 to 10 of 10

Thread: Evohome / RAMSES-II protocol - device type 31?

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Automated Home Jr Member
    Join Date
    Jul 2016
    Posts
    17

    Default Evohome / RAMSES-II protocol - device type 31?

    Hi,

    This may be more of a question for @rameses but if anyone on here knows the answer I'd be grateful!

    I've been playing around with Home Assistant and a 3rd party integration to connect it directly with Evohome using an HGI80. It's all working just fine, but there's a curious device that's being picked up in the log. Device ID type '31':

    2021-02-25T08:17:07.775330 078 RQ --- 31:004811 13:077615 --:------ 3EF1 001 00
    2021-02-25T08:17:07.790084 072 RP --- 13:077615 31:004811 --:------ 3EF1 007 0000380038C8FF

    It only ever appears in RQ and RP messages talking to a '13' device, which is either a BDR91 or an HG60ng, not sure which... but seeing as I have two BDR91s and one HC60ng, and it only appears in connection with one of them then I can make a guess at the most likely device it's talking to is the HC60ng, but that is just a guess.

    Every single other component in my system has been accounted for in terms of what's been reported by the logs (touch controller, 10x HR92, 1x HW, 2xBDR91, 1xHC60, 2xY87RF).

    Any clues? This wiki page has most of the Device IDs recorded, but a 'Dunno' against 31!
    https://github.com/Evsdd/The-Evohome...lds#device-ids
    Last edited by oshingler; 25th February 2021 at 10:05 AM.

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

    Default

    It could a neighbour's device. Unless you saying that 13:077615 is definitely yours.
    According to me 31 is a wireless stat and might not even be called Honeywell.
    And in any case it can't be the HC60NG because that device cannot respond to any requests. It's a listen only radio device, which is why I think it was quickly replaced by the BDR91 that can perform 2 way radio communications.
    Last edited by bruce_miranda; 25th February 2021 at 08:52 AM.

  3. #3
    Automated Home Jr Member
    Join Date
    Jul 2016
    Posts
    17

    Default

    Perhaps it is a neighbour's device... I certainly can't rule that out! Maybe if I send some commands and then see which house the heating engineer turns up to in a couple of days?

  4. #4
    Automated Home Legend
    Join Date
    Jul 2014
    Posts
    1,567

    Default

    But surely you know if 13:077615 is yours or not.

  5. #5
    Automated Home Jr Member
    Join Date
    Jul 2016
    Posts
    17

    Default

    I *did* know what all of my IDs were, back when I first installed everything and I had a nice list of IDs for everything. But that was many years ago! I can of course go around and figure it out, I'm just being lazy - I have finally got it stable in Home Assistant so would have to move things around to do another discovery. Maybe I'll have a play this weekend and see what I find left over. The more I think about it though, the less I recognise that ID. It's not a problem anyway, I have a filter on because I only need to talk to my controller and none of the other devices directly. Most of them are out of range of the HGI80 so I end up with a lot of devices that don't update very often if I try that.

  6. #6
    Automated Home Legend
    Join Date
    Jul 2014
    Posts
    1,567

    Default

    Try sending this using your HGI80, replace the xxxx with your own ID. And post what comes back.
    Code:
    RQ --- 18:00xxxx 31:004811 --:------ 10E0 001 00

Posting Permissions

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