Request Orcon functionality in Domoticz

[84dasilva]

RFXcom868xl is able to communicate with Orcon (MVS-15H) in the windows test program.

Please activate this functionality in Domoticz.

[waltervl]

I see references of Orcon in the source code (for Fans). I am no RF user so no idea how to select it in Domoticz.

[waltervl]

Do you see the Orcon Protocol when selecting Set Mode on your RFXCOM hardware gateway (menu Setup - Hardware)?

[84dasilva]

Hi, thanks for reply.

No the protocol selection functionality has been removed from domoticz. Also I don't see the required protocol as an option.

In the rfxmngr the orcon protocol is activated.

[waltervl]

Yes it seems this is the new way to not select it within Domoticz anymore. See also https://github.com/domoticz/domoticz/is ... 1518644890

So what is the issue? When you have set Orcon in RFXManager your receiver can work with that and should communicate with Domoticz.

[84dasilva]

Yes it seems this is the new way to not select it within Domoticz anymore. See also https://github.com/domoticz/domoticz/is ... 1518644890

So what is the issue? When you have set Orcon in RFXManager your receiver can work with that and should communicate with Domoticz.

The issue is that domoticz does not seem to work with the orcon protocol. It does not see any incomming devices. Devices which are seen in the rfxmngr tool.

I cannot find any other options to search or set any rfxcom868 device related settings in domoticz.

[waltervl]

Perhaps ask rfxcom directly how to do that.

[84dasilva]

Perhaps ask rfxcom directly how to do that.

He adviced to post the request here.

[opechunka]

Also tried with RFXtrx. Received "Invalid data received!....".
But even after I changed the source code and commented out check for type pTypeFan, Domoticz detected new buttons per every Orcon button (if you press it). But they were not functional at all. While looking into Domoticz source code for Orcon support, it looks like the imlementation is not finished.

[homeJLB]

I found that the respons from a Orcon device is

Code: Select all

pLen == 0x11

but the Fan device in domoticz has

Code: Select all

pLen == 0x08

so if I make a change in RFXBase.cpp to

Code: Select all

case pTypeFan:
return (pLen == 0x08 || pLen == 0x11);

Then the code works and gives me a on/off switch.

But sometimes it is detected as a second device.
So with 1 remote I have 2 devices discovered.

RFXcom 868.png (18.43 KiB) Viewed 7300 times

The Hardware remote 15RF has 6 buttons.

15RF.png (141.49 KiB) Viewed 7300 times

So has someone another remote and does we have to make a separate Fan Device for Orcon (FAN2)

Kind Regards

[homeJLB]

With my test setup I now have identified the different messages.

So based on this I propose a change from using RemoteID to using Destination ID as Hardware ID in Domoticz.

Leaves only the state off the device from the 6 buttons.

Happy Hollidays

[84dasilva]

I also have an honeywell hgi80 transeiver, which operates on the same frequency/protocol.

It also notices messages received from the orcon.

2025-12-27 21:15:41.601 Error: EvohomeHGI80: Unknown command 31d9
2025-12-27 21:15:58.464 Error: EvohomeHGI80: Unknown command 31e0
2025-12-27 21:17:41.073 Error: EvohomeHGI80: Unknown command 1298

These messages seem to be status info received from the orcon Unit.

Does anyone here have the skills to add these message ids for decoding?

[homeJLB]

if your Honeywell HGI80 is connected to the same hardare as the RFX.

you can add

Code: Select all

_log.Debug(DEBUG_HARDWARE, "CheckValidRFXData: pLen=0x%02X, pType=0x%02X (%s), pData=%s", pLen, pType, RFX_Type_Desc(pType, 1), ToHexString(pData, pLen + 1).c_str());

just like

CheckvalidRFXdata.png (36.19 KiB) Viewed 7259 times

then you can see the HEX-code transmitted and received

kind regards

[84dasilva]

Thanks for the quick response.

I need to find the time to look into this, this will be later in Januari.

Wil get back to it.

[homeJLB]

I have found that a FAN-device in domoticz is only correct displayed with a On/Off switch.
With a Selector Switch the Icon is empty.

Also when selecting the FAN as Favorite it is not shown on the Dashboard.

When I changed on the switch-page to selector-switch and add levels.

Orcon.png (68.56 KiB) Viewed 7242 times

And when I press a button on the selectorswitch there is a mismatch from the ID
It changed from 772473 to 732473
So I believe the Write to Hardware is also a Problem.

Fan.png (18.66 KiB) Viewed 7242 times

I have changed in hardware/RFXBase.cpp

Code: Select all

case pTypeFan:
		return (pLen == 0x08 || pLen == 0x11 || pLen == 0x31);

and in main/mainworker.cpp

Code: Select all

	//      Make a switch for Orcon Device based on Destination ID
	if (pResponse->ICMND.subtype == 0x0C)
	{
		_log.Debug(DEBUG_HARDWARE, "Subtype Orcon detected");
		sprintf(szTmp, "%02X%02X%02X", pResponse->FAN2.did1, pResponse->FAN2.did2, pResponse->FAN2.did3);
		//"CustomImage", 8 FAN
	}
	else
		sprintf(szTmp, "%02X%02X%02X", pResponse->FAN.id1, pResponse->FAN.id2, pResponse->FAN.id3);

This to have the received switch with Destination ID.

Happy Holidays

[homeJLB]

I have found that a FAN-device in domoticz is only correct displayed with a On/Off switch.
With a Selector Switch the Icon is empty.

Also when selecting the FAN as Favorite it is not shown on the Dashboard.

When I changed on the switch-page to selector-switch and add levels.

Orcon.png

And when I press a button on the selectorswitch there is a mismatch from the ID
It changed from 772473 to 732473
So I believe the Write to Hardware is also a Problem.

Fan.png


I have changed in hardware/RFXBase.cpp

Code: Select all

case pTypeFan:
		return (pLen == 0x08 || pLen == 0x11 || pLen == 0x31);

and in main/mainworker.cpp

Code: Select all

	//      Make a switch for Orcon Device based on Destination ID
	if (pResponse->ICMND.subtype == 0x0C)
	{
		_log.Debug(DEBUG_HARDWARE, "Subtype Orcon detected");
		sprintf(szTmp, "%02X%02X%02X", pResponse->FAN2.did1, pResponse->FAN2.did2, pResponse->FAN2.did3);
		//Write to Hardware has no DestinationID so using Normal ID
		if (pResponse->FAN2.did1 == 0)
			sprintf(szTmp, "%02X%02X%02X",pResponse->FAN2.id1, pResponse->FAN2.id2, pResponse->FAN2.id3);
		//"CustomImage", 8 FAN
	}
	else
		sprintf(szTmp, "%02X%02X%02X", pResponse->FAN.id1, pResponse->FAN.id2, pResponse->FAN.id3);

This to have the received switch with Destination ID.

Happy Holidays

[homeJLB]

I have found a solution for supporting the ORcon-FAN device.
I have made a Pull-Request on Git-hub.

Orcon Fan.png (26.82 KiB) Viewed 7208 times

FAN Options.png (77.44 KiB) Viewed 7208 times

Kind Regards

[homeJLB]

So in the latest Stable the Orcon Fan is fully supported.

For this to work with a RFXcom868 you must use the RFXmanager to set the mode to only Orcon.
The RFXcom can only receive 1 modus but transmit on multiple channels.

RFXmanager.jpg (99.46 KiB) Viewed 5640 times

The you can connect the RFXcom868 to Domoticz

RFXcom Hardware.png (68.48 KiB) Viewed 5640 times

When you then press on the original Orcon remote the Device is discovered by Domoticz and placed in the Devices "Not used" section.

After you set used the Device
You can name the Device instead off "Unknown"

The you can use the standard On/Off Fan with pop-up to select the modus.

Orcon Discovered.png (44.04 KiB) Viewed 5640 times

Or you can change the device to a selector for custom Level Names.
A seen in my previous post.


Maybe this can be added to the Wiki.

Kind Regards

[nfuse]

Nice work @homeJLB getting native Orcon support into Domoticz stable — that's great for RFXcom868 owners.

For anyone who doesn't have an RFXcom868 or HGI80 (or just wants full two‑way control on the cheap), I've open‑sourced a different route: a standalone ESP32 + CC1101 (~€10–12) that emulates the Orcon 15RF controller and talks to the HRC directly — no RFXcom/HGI80 needed.

It may be handy for the decoding side people hit earlier here — those Unknown command 31d9 / 31e0 / 1298 messages @84dasilva saw. It decodes those status frames into real values: indoor/outdoor/supply/exhaust temperatures, RH, CO₂, bypass position, and supply/exhaust fan %. And it sends: modes (Away/Auto/1/2/3/Boost), bypass, timed boost, and an unbalanced "AC" night‑cooling mode.

For Domoticz specifically it exposes everything over MQTT with auto‑discovery, and ships an embeddable /widget page (live airflow view) for the dashboard — so you get devices + a visual without patching Domoticz. There's also an on‑device RF log (RX/TX in ramses_rf notation) and a /debug page with 31DA byte‑rulers for calibrating decode offsets against your own model.

MIT‑licensed, built on the RAMSES‑II work from ramses_rf / evofw3 (credited):
https://github.com/me-processware/orcon-15rf-controller

Happy to help if anyone wants to try the ESP32 route.

[manjh]

I've found an Orcon RF15 remote control unit, and would like to interface that to Domoticz. Purpose is to switch my existing ventilation unit with it.
So all I need is a way to receive the signals sent by the remote control unit, and hand them to domoticz somehow. Node Red/MQTT sounds fine.

Would this be possible?