How to start? Looking for a Howto!

[mrqnapper]

Now I have Domotiga running I haven been looking around in the programm getting familiair with it. Now I am trying to get things starting. I have several devices from Homeasy, Klik aan Klik uit. Now I want to add an receiver to the devices list, so for first test I have the HE205EU Which is an light bulb device. My RFXLAn is connected (its mentioned at the bottum of the Domotiga window). So if I want to use this device do I have to add it first to the Modules list? And if so, where do I get the address format from? Because If I just choose the available Homeasy Eu Module from the devices list it gives an error message saying that selected interface does not support this kind of device?

So Now I am a bit lost here without a manual, or any examples how to get this going in combination with the RFXLAN. I thought I could set up any device from the Domotiga prog. Or do I also have to use the RFXLAN program to connect the devices I want to use? Anyone who has a clear Howto for me to get this a bit clear? Thanks a lot.

Wiechert.

[insomniux]

Hi Wiechert,
I kind of recognize your desperacy. For me it has been kind of a struggle to get it up and running. Once thought of writing a simple HowTo for dummies, but alas, no time.

I have KiKa devices alone, cannot say anything about HomeEasy, although the setup may be comparable. From memory I'll try to guide you through the first steps (in fact I'm still not far away from that ). Assumptions are that DomotiGa is well installed with a working database (the MySQL thing) and you can connect to the db). Also I assume your RFXlan is well connected to your network and you can connect to the webpage of the device (kind of proving that it works). One important feature of DomotiGa is that you can nearly debug everyting, and that debugging is the Nr One important key during installation.

Then:
1. Make sure DomotiGa connects to your RFXLan: go to setup/interfaces/RFXcom and configure both the receiver and transmitter (tcp/host address). If you have the xmitter check that box. Turn on Debug in both. This will enable you to check which KaKu uses which channel.
2. Go to the the Main/Log section. Here you get ALL logs (program, Debug, Devices, etc)
3. Go to Debug
4. Switch on any of your KaKu devices an check the debug window. You'll see something being printed like:

Code: Select all

2011/07/14 22:27:13 20708F609F2011/07/14 22:27:13 [Devices] Device 'X10' with address 'B05' and interface '' not found!
 B5-Off bits=32

The Address B05 indicates that you have a codewheel KaKu device with code B05 activated. It can also show something like 048B466, indicating the newer KaKu (single programming button) devices. This log-format also means that the device is not recognized
5. Lets say you have a KaKu remote plug (eg the KaKu YC 1000) which respond to channel B6. Go to menu Devices and select Add Device. Then:

• - Enter a suitable name
  - Choose KaKu Par 1000 as device (automatically the correct device options are selected)
  - Set the X10 (!) Add to B 6 (or the code given by the debug-logging; make sure you add a 1 or 2 at the end of the code for switch 1 or 2 in case of combined switches)
  - Go to the tab Options
  - Select device can be switched, log status and Display status changes
  - Select Save (it'll ask if the device should be enabled, answer yes)

If you know go to Section Main and select Control, you should see a button with the name you've given in the first field above. If you click the button the switch should turn on (or off). Check the log-section to see what the message looks like now.

If it does not work I advice to check (under windows ) if the RFXLan box actually does capture the signal from your KaKu or HE devices first.

If you've reached this point and you can switch your devices, you're at the beginning of a long adventure in controlling your house. The events/actions are extremely rewarding experimenting with, and GREAT FUN.

Succes
Insomniux

[RDNZL]

@Wiechert Did the nice howto from Insomniux help getting the light on? Or are you still in the dark?
If not, where did you get stuck? Maybe we can get it fixed...

[mrqnapper]

@Insomniux, @Ron,

Unfortunately I am still in the dark Although the explanation is great I get lost again. So following the steps, I went to the Main/log/debug part, then I switched on one of the HE devices and I got a line mentioning more or less the same thing as the example from Insomniux. So far so good: The code displayed for the device was: HE/KAKU 039A922
to make sure it really was working, I also switched it off again an yes it mentioned that in the debug log as well.
So I went over to the next part. And created a brand new Device using this settings:

• - Name Test device
  - KaKu Par 1000 as device
  - A 09 as the code ???
  - Options: Select device can be switched, log status and Display status changes
  - RFXCOM transmitter as the interface
  - Select Save (it'll ask if the device should be enabled, answer yes)

After that I went over to the control and the new Device showed up. Click on it and its status changed to on. But no light for me!

The log file:

Code: Select all

interface for device with name "test" is 12
address for device with name "test" is A09
Interface with name RFXCom Transmitter has id 12
Device with name A09 is test
RFXCom TX 20609F20DF
RFXCOM ACK=> 33
...And some queries for the database....

This did not work. After trying different settings it still does not work.
Than I thought let start over form the begin and try an other HE Device. But now, I even do not see that device mentioned in the log file?

Regards,
Wiechert

[RDNZL]

Can you copy/paste the exact logfile entries?
You should get something like 'Device '...' with address '...' when switching.
Whats in the address part?

[mrqnapper]

Ron thanks for your reply. This is from the log file:

Code: Select all

2011/07/30 17:03:45 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:03:45 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:03:45 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:03:45 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:03:45 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:03:45 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:03:45 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:05:08 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:05:08 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:05:08 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:05:08 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:05:08 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:05:08 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:05:08 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:05:18 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:05:18 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:05:18 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:05:18 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:05:18 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:05:18 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:05:19 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:08:35 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:08:35 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:08:36 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:08:36 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:08:36 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:08:36 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:08:36 [Devices] Device 'HE/KAKU' with address '039A922' and interface 'RFXCom Receiver' not found!
2011/07/30 17:32:26 [Devices] Address for device with name 'kamer_borre' is 'A09'
2011/07/30 17:32:26 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 17:32:26 [Devices] Device with address 'A09' and 'kamer_borre' is a new device
2011/07/30 17:32:27 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 17:32:27 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 17:32:33 [Devices] Address for device with name 'kamer_borre' is 'A09'
2011/07/30 17:32:33 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 17:32:34 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 17:32:34 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 17:33:31 [Devices] Address for device with name 'kamer_borre' is 'A09'
2011/07/30 17:33:31 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 17:33:32 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 17:33:32 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 17:34:56 [Devices] Address for device with name 'kamer_borre' is 'A09'
2011/07/30 17:34:56 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 17:34:58 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 17:34:58 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 17:36:19 [Devices] Address for device with name 'kamer_borre' is 'A09'
2011/07/30 17:36:19 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 17:36:20 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 17:36:20 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 17:36:23 [Devices] Address for device with name 'kamer_borre' is 'A09'
2011/07/30 17:36:23 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 17:36:24 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 17:36:24 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 17:40:30 [Devices] Address for device with name 'kamer_borre' is 'A09'
2011/07/30 17:40:30 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 17:40:31 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 17:40:31 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 17:40:34 [Devices] Address for device with name 'kamer_borre' is 'A09'
2011/07/30 17:40:34 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 17:40:35 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 17:40:35 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 21:46:12 [Devices] Address for device with name 'kamer_borre' is 'A09'
2011/07/30 21:46:12 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 21:46:13 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 21:46:13 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 21:56:55 [Devices] Address for device with name 'kamer_borre' is 'A09'
2011/07/30 21:56:55 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 21:56:56 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 21:56:56 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 21:59:57 [Devices] Address for device with name 'kamer_borre' is 'A09'
2011/07/30 21:59:57 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 21:59:58 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 21:59:58 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 22:02:19 [Devices] Address for device with name 'kamer_borre' is 'A09'
2011/07/30 22:02:19 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 22:02:20 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 22:02:20 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 22:19:42 [Devices] Address for device with name 'kamer_borre' is 'A09'
2011/07/30 22:19:42 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 22:19:43 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 22:19:43 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 22:19:47 [Devices] Address for device with name 'kamer_borre' is 'A09'
2011/07/30 22:19:47 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 22:19:48 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/30 22:19:48 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/31 20:37:50 [Devices] Address for device with name 'kamer_borre' is 'A09'
2011/07/31 20:37:50 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/31 20:37:51 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/31 20:37:51 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/31 20:38:56 [Devices] Address for device with name 'kamer_borre' is 'B09'
2011/07/31 20:38:56 [Devices] Device with address 'B09' is 'kamer_borre'
2011/07/31 20:38:57 [Devices] Device with address 'B09' is 'kamer_borre'
2011/07/31 20:38:57 [Devices] Device with address 'B09' is 'kamer_borre'
2011/07/31 20:39:01 [Devices] Address for device with name 'kamer_borre' is 'B09'
2011/07/31 20:39:01 [Devices] Device with address 'B09' is 'kamer_borre'
2011/07/31 20:39:02 [Devices] Device with address 'B09' is 'kamer_borre'
2011/07/31 20:39:02 [Devices] Device with address 'B09' is 'kamer_borre'
2011/07/31 20:40:30 [Devices] Address for device with name 'kamer_borre' is 'A09'
2011/07/31 20:40:30 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/31 20:40:31 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/31 20:40:31 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/31 20:40:35 [Devices] Address for device with name 'kamer_borre' is 'A09'
2011/07/31 20:40:35 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/31 20:40:36 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/31 20:40:36 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/31 20:46:51 [Devices] Address for device with name 'kamer_borre' is 'A09'
2011/07/31 20:46:51 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/31 20:46:52 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/31 20:46:52 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/31 20:46:57 [Devices] Address for device with name 'kamer_borre' is 'A09'
2011/07/31 20:46:57 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/31 20:46:58 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/31 20:46:58 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/31 20:57:18 [Devices] Address for device with name 'kamer_borre' is 'A09'
2011/07/31 20:57:18 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/31 20:57:19 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/31 20:57:19 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/31 21:18:57 [Devices] Address for device with name 'kamer_borre' is 'A09'
2011/07/31 21:18:57 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/31 21:18:58 [Devices] Device with address 'A09' is 'kamer_borre'
2011/07/31 21:18:58 [Devices] Device with address 'A09' is 'kamer_borre'

[RDNZL]

What happens when you define a device as type "KAKU AWST-8802" and use "039A922" as DevUnit address?

[mrqnapper]

I defined a device with these settings and have selectes RFXCOM transmitter as interface than I get: Selected interface does not support this kind of device.

Regards Wiechert

[mrqnapper]

Still did not succeed in getting things working. Now I try to understand how things are working, so hopefully I can get it right. My questions remarks here below.

Code: Select all

A question?: 
1. does Domotiga handle the paring with new devices for/ through RFXLAN? Or do I need to pair al devices first in RFXLAN first before I can use them in Domotiga? 

Code: Select all

2. The strange thing is, that after the first time switching on a device (as advised at point 4 of the instructions from Insomniux) and being able to read its device address, I could not do that any more, even not with any other device chosen. 
So trying a different device with an other address is no option now. 
So at this moment I am completely lost here. Might be the case that the RFXLAN settings are not correct? 

An other Question?

Code: Select all

3. Say I have a new device, which is not mentioned in the Device list, when creating a new device, Do I need to create a new "module" in the available device list or is this something thats part of the Domotiga software? So if I want to use per example the KaKuAPCR-2300 its not already in the "devices" list, also for the HomeEasy devices I tried to use (HE332EU), etc.

Thanks,

Wiechert

[insomniux]

Ehhh... shouldn't this device have 8 digits as identifier? With KaKu there are 7bits identifying the device and 1 (last) identifying switch 1 or 2 of the (sender)device. My receiver expects 8 hex codes, in my example: 048B4662 . The last '2' identifies the 2nd switch in the (sender)device. Don;t know, however, if this also applies to HomeEasy devices... So, you may need to add a 1 or a 2 at the end (just trial and error). Hope this helps, since, when you have it up and running, it may become addictive....

[insomniux]

Code: Select all

A question?: 
1. does Domotiga handle the paring with new devices for/ through RFXLAN? Or do I need to pair al devices first in RFXLAN first before I can use them in Domotiga? 

No you do not need to pair the devices in the RFXCom, at least not with the devices I use (KaKu and Elro). However, you can try to control the devices from the windows app which is provided by RFXCom to check if it works. I use a VirtualBox under Linux with WinXP, to run these apps. Have not tried Wine. Unfortunately RFXCom does not provide a Linux version of their applications.

Code: Select all

2. The strange thing is, that after the first time switching on a device (as advised at point 4 of the instructions from Insomniux) and being able to read its device address, I could not do that any more, even not with any other device chosen. 
So trying a different device with an other address is no option now. 
So at this moment I am completely lost here. Might be the case that the RFXLAN settings are not correct? 

I remember that while experimenting sometimes domotiga got stuck while sending the wrong codes to the devices (or listening to the wrong signals). Killing all gamba gbr2 processes did help. After I corrected all settings this did not happen anymore.

An other Question?

Code: Select all

3. Say I have a new device, which is not mentioned in the Device list, when creating a new device, Do I need to create a new "module" in the available device list or is this something thats part of the Domotiga software? So if I want to use per example the KaKuAPCR-2300 its not already in the "devices" list, also for the HomeEasy devices I tried to use (HE332EU), etc.

As far as I see, you do not need to create new modules, as long as the protocol used by the devices is identical. I use a mix of Elro and KaKu devices, partly using the HE protocol (7 x hex + 1/2) or ARC protocol (like A1). The fact that Ron provided actual models for each protocol is more a matter of courtesy and it helps by making a good choice rather than being actually necessary. I use the KaKu PAR 1000 for actually all (elro and kika) recievers. As long as they use the same protocol. I assume the APCR-2300 uses the HE protocol, just select a module with that protocol.

Insomniux

[mrqnapper]

Thanks for your reply. I will try again with your remarks. Still its not all very clear to me. Will start with the killing part first.
If there are other users with experiences regarding this subject please add them might be usefull for me and other users starting with Domotica. Thanks

Wiechert

[mrqnapper]

I tried several protocols and still did not get this working. If using HE in combination with the RFXCOM transmitter! it says that this kind of device is not supported by the interface?
After some unbuntu Killing I am again able to see some action in the debug log when I switch on or off a device. I even updated to the last version of Domotiga to be sure:)

So now I have the address format for the new device I use for testing (its the HE332EU remote control starter kit): 0579BA1 .
But still no lights here. Its driving me...
Apparently something is not working like it should or, I am missing the point? I don't know. So might need some more support on this:)

a part of the log file for reference:

Code: Select all

2011/08/05 21:56:23 22015E6E8000 HE Device=0579BA Unit=12011/08/05 21:56:23 [Devices] Interface with name 'RFXCom Receiver' has id '1'
2011/08/05 21:56:23 [Devices] Device 'HE/KAKU' with address '0579BA1' and interface 'RFXCom Receiver' not found!
 OFF bits=34
2011/08/05 21:56:23 22015E6E8000 HE Device=0579BA Unit=12011/08/05 21:56:23 [Devices] Interface with name 'RFXCom Receiver' has id '1'
2011/08/05 21:56:23 [Devices] Device 'HE/KAKU' with address '0579BA1' and interface 'RFXCom Receiver' not found!
 OFF bits=34
2011/08/05 21:56:23 22015E6E8000 HE Device=0579BA Unit=12011/08/05 21:56:23 [Devices] Interface with name 'RFXCom Receiver' has id '1'
2011/08/05 21:56:23 [Devices] Device 'HE/KAKU' with address '0579BA1' and interface 'RFXCom Receiver' not found!
 OFF bits=34
2011/08/05 21:56:23 22015E6E8000 HE Device=0579BA Unit=12011/08/05 21:56:23 [Devices] Interface with name 'RFXCom Receiver' has id '1'
2011/08/05 21:56:23 [Devices] Device 'HE/KAKU' with address '0579BA1' and interface 'RFXCom Receiver' not found!
 OFF bits=34
2011/08/05 21:57:00 [Events] 1a. Runn

[insomniux]

Wiechert,
The identification of your device is 0579ba UNIT=1. My guess is that you should enter the address as 0579ba1.
The problem I see is that this HE332EU set uses the new identification protocol (not the A1 type but the 0579ba1-type). I can catch these signals with the RFX-receiver (using the HE protocol (eg the AWST-8802)), but I have not found the way to transmit this code through the RFXmitter. All KAKU and HE receivers use the A1-type (ARC) identification.

The dirty solution I have (with KaKu, it may work for HE as well) is as follows. The appliance modules usually have a learning modus. KaKu has a button which you have to push. Then you push the button on the switch to handshake them. You can also use DomotiGa to do the handshaking (using e.g. the PAR 1000 / ARC protocol). Choose a code e.g. A2 or any unique code you like, don't forget to set the option "Device can be switched" in the options tab. Then go to the Control section in the Main group, where you will see the button of the device you've just created. Put the appliance in the programming mode and push the button of the device in the Control-screen. Make sure the device is absolutely in reach of the RFXmitter! This way I programmed all my KaKu appliances. Drawback is that you have only 256 different chanels, wheras the new programming protocol as 16^7 chanels.

@Ron: would you have another solution? Is there a way to make DomotiGa handshake with the HE receivers in another way?
Cheers,
Insomniux

[mrqnapper]

@Insomniux, thanks for your reply.

Your dirty solution works fine for the only KiKa device I have with learning button.
But for the HE EU devices its still not working. Since I have Mainly HE EU devices it would be nice if I get them working as well.

When I started with "domotica" I first tried to switch devices on and off through the RFXCOMLan I bought. Than I managed to get one of these HE devices working (as a test for use with HomeAutom8) using the instructions from RFXCOM. These settings for HE are in AC format. Tried to connect a device today but could not get that working, might be that RFXLan can only be used to pair up a device when Domotiga is not connected?

@Ron would be very pleased with some support from your side:)