RFXTRX Issue: wrong baudrate (38400) (VM Debian aarch64)

testeur999 commented 2 years ago

Feedback

On Debian 11 aarch64, all updated, running as VM on a Freebox Delta: when RFXTRX start, mys usb port baudrate lock to 38400. screen /dev/ttyACM0 38400 give hasardous characters.

when forcing to 57600 bauds, with stty, i got correct RFLink visual with screen /dev/ttyACM0 57600, but RFXTRX refuse to work.

have also tested from another RFLink, already used on a Domoticz server, via ser2net. same issue.

I don't know why RFXTRX force baudrate to 38400, as RFLink work at 57600.

Already tested on another VM, on HP DL380G7, on "pure" Home Assistant OS, same RFLink, no problems at all.

URL

https://www.home-assistant.io/integrations/rfxtrx/

Version

2021.12.5

Additional information

No response

probot-home-assistant[bot] commented 2 years ago

Hey there @danielhiversen, @elupus, @robbie1221, mind taking a look at this feedback as it has been labeled with an integration (rfxtrx) you are listed as a code owner for? Thanks! _{^{(message by CodeOwnersMention)}}

testeur999 commented 2 years ago

More than 24h awake....

why i don't understand RFLink is NOT RFXCOM...

connected as ser2net on my domoticz with configuration.yaml:

`rflink: host: 192.168.1.10 port: 6000 tcp_keepalive_idle_timer: 600

light:

platform: rflink automatic_add: true sensor:
platform: rflink automatic_add: true ` Work as a charm, only if i delete RFXTRX add-on.

All Work, i let this post as is, if anyone found the same brain-washed trap...

My miss

home-assistant / home-assistant.io