[rfxcom] The firmware type reported isn't known to the binding

[ajseesink]

Expected Behavior

I have firmware version 1045 and hardware version 3.1

Current Behavior

2022-06-26 21:59:29.564 [WARN ] [rnal.messages.RFXComInterfaceMessage] - The firmware type reported (19) isn't known to the RFXCom binding. Please raise an issue at https://github.com/openhab/openhab-addons/ to have it included.

2022-06-26 21:59:29.301 [ERROR] [internal.handler.RFXComBridgeHandler] - Connection to RFXCOM transceiver failed

org.openhab.binding.rfxcom.internal.exceptions.RFXComException: No serial port /dev/ttyUSB-rfxcom

at org.openhab.binding.rfxcom.internal.connector.RFXComSerialConnector.connect(RFXComSerialConnector.java:61) ~[?:?]

at org.openhab.binding.rfxcom.internal.handler.RFXComBridgeHandler.connect(RFXComBridgeHandler.java:211) ~[?:?]

at org.openhab.binding.rfxcom.internal.handler.RFXComBridgeHandler.lambda$0(RFXComBridgeHandler.java:184) ~[?:?]

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]

at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) [?:?]

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) [?:?]

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]

at java.lang.Thread.run(Thread.java:829) [?:?]

Possible Solution

Steps to Reproduce (for Bugs)

1. Start or restart openhab and the message will apear

Context

Your Environment

• Version used: (e.g., openHAB and add-on versions)
• Environment name and version (e.g. Chrome 76, Java 8, Node.js 12.9, ...):
• Operating System and version (desktop or mobile, Windows 10, Raspbian Buster, ...):

[lolodomo]

What model do you own and what firmware type did you install?

[lolodomo]

It may be the ProXL firmware?

[ajseesink]

I got the RFXtrx433XL with the current firmware version 1045. It's the latest firmware version. The message is that openhab sends is that it doesnt support the 1045 version (yet?) and asks me to raise an issue. So I did. My guess is that openhab rfxcom binding needs to be updated?

[lolodomo]

Yes this warning was to detect new firmware types, meaning those not officially supported by the binding. I do not know what is specific in this firmware and whether or not the API was updated. Unfortunately, the RFXCOM API is apparently no more public, at least I did not find any information on the RFXCOM website. Maybe the API changes are minor and the binding will work, difficult to say without any technical information. I would suggest you to test the binding anyway.

And someone having the specs should analyze them and update the binding if necessary.

PS: Your logs also show another problem, you setup apparently an invalid serial port.

[ajseesink]

Thanks for the reply. I've seen the serial part thing and managed that one. That problem is gone.

[Mickroz]

i got the same problem with the same model.

[lolodomo]

This would require a contribution to support this new model/firmware.

[Mickroz]

Firmware then, cause ive been using this since openhab 2.

[zygotic99]

I asked RFXCom about this, because I hope to buy a RFX433XL to control Somfy blinds but wondered whether this issue would me.

Their reply is below. Is this any help in resolving the issue and supporting newer firmware?

Ask the openhab developer to update the firmware types: msg10: Firmware type: 0x00 = Type1 RFXrec receive only firmware 0x01 = Type1 0x02 = Type2 0x03 = Ext 0x04 = Ext2 0x05 = Pro1 0x06 = Pro2 0x10 = ProXL1 0x11 = for internal use 0x13 = ProXL2 0x14 = RFX433 //RFX433XL 0x15 = RFX868 //RFX868XL 0x16 = ProXL95 //RFU 0x17 = RFU 0x18 = RFX310 //RFXusb with 310MHz receiver

Developers can ask for the latest RFXtrx SDK!

[lolodomo]

Nothing new. A contributor developing this enhancement is still required and he will have to contact RFXCOM to get the new API.

[wborn]

Maybe @martinvw or @paulianttila can have a look at this?