search

zxdavb / ramses_rf

An interface for the RAMSES RF protocol, as used by Honeywell-compatible HVAC & CH/DHW systems.
MIT License
61 stars 16 forks source link

HGI80 incorrectly detected as an evofw3 #104

Closed zxdavb closed 7 months ago

zxdavb commented 8 months ago

From HA forum

Latest version, and I get this in the logs now:

/dev/serial/by-id/usb-FTDI_USB-RS232_Cable_FT5S4V48-if00-port0: the gateway type is not determinable, will assume evofw3, TIP: specify the serial port by-id (i.e. /dev/serial/by-id/usb-...)

As you can see, I’m already using /dev/serial/by-id…

It says treating as an evofw3 device, however, I actually have a serial HGI80 connected via USB adapter. It works fine but latest updates treat it as an evofw3.

Can we have a manual switch to tell it what it is?

Onl1ne1373 commented 8 months ago

Interesting, my HGI80 does not have a FTDI chipset, but a TUSB3410: /dev/serial/by-id/usb-Texas_Instruments_TUSB3410_Boot_Device_TUSB3410-if00-port0

zxdavb commented 8 months ago

Actually, this is a HGS80 attached via a Rs232-USB adapter. The /dev/serial/by-id/usb-FTDI_USB-RS232_Cable_FT5S4V48-if00-port0 is the adapter, not the HGS80.

zxdavb commented 7 months ago

This has been addressed with a less unhelpful error message

zxdavb commented 7 months ago 
    _LOGGER.warning(
        f"{serial_port}: the gateway type is not determinable, will assume evofw3"
        + (
            ", TIP: specify the serial port by-id (i.e. /dev/serial/by-id/usb-...)"
            if "by-id" not in serial_port
            else ""
        )
    )