Create KAKU output devices in HS3 / RFCcom

Forum about Rfxcom home automation Domotica devices.

Moderator: b_weijenberg

Post Reply
User avatar
Jeroen Bartels
Advanced Member
Advanced Member
Posts: 627
Joined: Sun Jul 20, 2008 1:23 pm
Location: Netherlands

Create KAKU output devices in HS3 / RFCcom

Post by Jeroen Bartels »

Hello all,

I recently upgraded to HS3 and I wanted to start clean (So I will create all devices by hand).
I have some questions about creating KAKU output devices in RFXcom plugin. (Both AC and ARC devices/dimmers)
The questions are probably more clear in the attached picture but here they are:

1: There is a code (house) code in the config tab like "H 1" but there is also a "device code" in the RFCcom tab. What is the difference, do they need to be the same?
2: The ID code can be randomly filled. but does this mean I can keep them the same for each device? Does it do anything?
3: In HS2 the location2 needed to stay empty. is there also some rule for the 2 lacations in HS3?

I checked the RFCcom manual but could not get clear answers on these points. As I will be creating many devices I just want to make sure I do it right the first time.

Remark: I had a though time finding which transmitter I have (old device) and what I needed to fill in for receiver/transmitter to get it to work. Maybe Bert can improve the documentation for this for future users. (e.g. pictures)
Attachments
HS3 RFXcom vragen.JPG
HS3 RFXcom vragen.JPG (124.99 KiB) Viewed 18856 times
**Jeroen**
User avatar
b_weijenberg
Forum Moderator
Forum Moderator
Posts: 1744
Joined: Sun May 14, 2006 4:32 pm
Location: Netherlands

Re: Create KAKU output devices in HS3 / RFCcom

Post by b_weijenberg »

1: There is a code (house) code in the config tab like "H 1" but there is also a "device code" in the RFCcom tab. What is the difference, do they need to be the same?
They can be different but it is preferred to use the same device code.

2: The ID code can be randomly filled. but does this mean I can keep them the same for each device? Does it do anything?
The ID + device code is used by the module. So ID's can be the same.
The ID is in fact the code of an AC remote.

3: In HS2 the location2 needed to stay empty. is there also some rule for the 2 lacations in HS3?
Location2 can be activated somewhere in the Homeseer configuration.
mrqnapper
Member
Member
Posts: 234
Joined: Sat Jun 25, 2011 1:08 pm

Re: Create KAKU output devices in HS3 / RFCcom

Post by mrqnapper »

After (again) problems with my HS3pro running in Windows10 on a Parallels VM on a MacMini I decided to try the Raspberry Pi2 with hS3 Linux.
Since I can not get into my old HS3 system any more :) I have to build most of the HS3 again in the Linux version. One thing that's giving me a headache is RFXCOM. I have a transceiver connected. And I think it is working since I am able receiving sensors and were able to create input devices form a remote (which I can see are working).

Now I also want to restore my OutputDevices. I thought this would be easy but seems not :)
As before in my Windows HS3 I created an AC Dimmer device which looks like the one in this topic. I have as a device code 9 and an ID code 0 03 9A 92 (the code I receive in RFXCOM input device from my remote for this dimmer is AC[0039A92-9]a )
Than when switching on or of the device nothing happens! So there could be a problem with the settings in the transmitter? Or is my code just wrong?

This is what I see in my log:
after an on:

Code: Select all

Jan-12 14:35:52 	  	RFXCOM 	29 (CheckTransmitters) xmitter #1 new state:Idle
Jan-12 14:35:52 	  	RFXCOM 	29 (XmitRxChar) Response xmitter#1 was 33
Jan-12 14:35:52 	  	RFXCOM 	29 (sockDataArrival) TCP 192.168.0.5,10002 data received: 33
Jan-12 14:35:51 	  	RFXCOM 	29 (CheckTransmitters) xmitter #1 new state:WaitAck
Jan-12 14:35:51 	  	RFXCOM 	29 (CheckTransmitters) xmit length:21
Jan-12 14:35:51 	  	RFXCOM 	29 (sockSendEnd) nbr of bytes send: 6
Jan-12 14:35:51 	  	RFXCOM 	29 (TxData) TCP 192.168.0.5,10002 data xmitted: 2100E6A49800
Jan-12 14:35:51 	  	RFXCOM 	29 (DeviceCmd) transmitter #1 packet: 2100E6A49800
Jan-12 14:35:51 	  	RFXCOM 	29 (DeviceCmd) called with:X_XMIT[1]Q:A:9:39A92:1:_On
Jan-12 14:35:51 	  	RFXCOM 	29 (DeviceCmd) called with dvref:96 cmd:_On
Jan-12 14:35:51 	  	RFXCOM 	29 (ODevXmit) called with:96:_On
Jan-12 14:35:51 	  	Device Control 	Device: Lamp Tafel to On (100) by/from: CAPI Control Handler 
This are my setting in the RFXcom tranmitter which seems ok to me?

Code: Select all

Transmitter 1	System	RFXCOM	RFXmitter	X_XMIT[1]Q	TCP/IP	192.168.0.5:10002
Who can help me getting the light on :)
User avatar
b_weijenberg
Forum Moderator
Forum Moderator
Posts: 1744
Joined: Sun May 14, 2006 4:32 pm
Location: Netherlands

Re: Create KAKU output devices in HS3 / RFCcom

Post by b_weijenberg »

Did you configure Device Code 9 on the Device RFXCOM tab?
mrqnapper
Member
Member
Posts: 234
Joined: Sat Jun 25, 2011 1:08 pm

Re: Create KAKU output devices in HS3 / RFCcom

Post by mrqnapper »

Yes I did.
User avatar
b_weijenberg
Forum Moderator
Forum Moderator
Posts: 1744
Joined: Sun May 14, 2006 4:32 pm
Location: Netherlands

Re: Create KAKU output devices in HS3 / RFCcom

Post by b_weijenberg »

What is received from the remote in the log with debug level 2 enabled for the receivers
mrqnapper
Member
Member
Posts: 234
Joined: Sat Jun 25, 2011 1:08 pm

Re: Create KAKU output devices in HS3 / RFCcom

Post by mrqnapper »

Code: Select all


Jan-12 16:17:45 	  	RFXCOM 	29 (RecRxChar) receiver #1 duplicate packet ignored: 2200E6A48800
Jan-12 16:17:45 	  	RFXCOM 	29 (RecRxChar) receiver #1 duplicate packet ignored: 2200E6A48800
Jan-12 16:17:45 	  	RFXCOM 	29 (sockDataArrival) TCP 192.168.0.5,10001 data received: 2200E6A48800
Jan-12 16:17:45 	  	RFXCOM 	29 (RecRxChar) receiver #1 duplicate packet ignored: 2200E6A48800
Jan-12 16:17:45 	  	RFXCOM 	29 (sockDataArrival) TCP 192.168.0.5,10001 data received: 2200E6A48800
Jan-12 16:17:45 	  	RFXCOM 	29 (RecRxChar) receiver #1 duplicate packet ignored: 2200E6A48800
Jan-12 16:17:45 	  	RFXCOM 	29 (sockDataArrival) TCP 192.168.0.5,10001 data received: 2200E6A48800
Jan-12 16:17:45 	  	RFXCOM 	29 (RecRxChar) receiver #1 duplicate packet ignored: 2200E6A48800
Jan-12 16:17:45 	  	RFXCOM 	29 (sockDataArrival) TCP 192.168.0.5,10001 data received: 2200E6A48800
Jan-12 16:17:45 	  	RFXCOM 	29 (RecRxChar) receiver #1 duplicate packet ignored: 2200E6A48800
Jan-12 16:17:45 	  	RFXCOM 	29 (sockDataArrival) TCP 192.168.0.5,10001 data received: 2200E6A48800
Jan-12 16:17:45 	  	RFXCOM 	29 (RecRxChar) receiver #1 packet: 2200E6A48800
Jan-12 16:17:45 	  	RFXCOM 	29 (display_E_a) Device:AC[0039A92-9]a Cmd:0
Jan-12 16:17:45 	  	RFXCOM 	29 (getHSdevice) input device 'AC[0039A92-9]a' found
Jan-12 16:17:45 	  	RFXCOM 	29 (sockDataArrival) TCP 192.168.0.5,10001 data received: 2200E6A48800
Jan-12 16:17:45 	  	RFXCOM 	AC received ID=0039A92 Unit=9
Jan-12 16:17:45 	  	RFXCOM 	29 (sockDataArrival) TCP 192.168.0.5,10001 data received: 2200E6A48800 
User avatar
b_weijenberg
Forum Moderator
Forum Moderator
Posts: 1744
Joined: Sun May 14, 2006 4:32 pm
Location: Netherlands

Re: Create KAKU output devices in HS3 / RFCcom

Post by b_weijenberg »

I suppose there is a bug in the plug-in, try the output device with device code 8
mrqnapper
Member
Member
Posts: 234
Joined: Sat Jun 25, 2011 1:08 pm

Re: Create KAKU output devices in HS3 / RFCcom

Post by mrqnapper »

Code: Select all

Jan-12 16:37:11 	  	RFXCOM 	29 (sockSendEnd) nbr of bytes send: 1
Jan-12 16:37:11 	  	RFXCOM 	29 (TxData) TCP 192.168.0.5,10001 data xmitted: 00
Jan-12 16:37:11 	  	RFXCOM 	Receiver #1 alive check on 192.168.0.5
Jan-12 16:36:59 	  	Device Control 	Device: Beneden Woonkamer Voor Lamp Tafel to On (100) by/from: CAPI Control Handler 
No result with device code 8

Code: Select all


Jan-12 16:40:32 	  	RFXCOM 	29 (HSEvent) parms4=62
Jan-12 16:40:32 	  	RFXCOM 	29 (HSEvent) parms3=255
Jan-12 16:40:32 	  	RFXCOM 	29 (HSEvent) parms2=0
Jan-12 16:40:32 	  	RFXCOM 	29 (HSEvent) parms1=014D02F4-024-Q37
Jan-12 16:40:32 	  	RFXCOM 	29 (HSEvent) parms0=1024
Jan-12 16:40:32 	  	Z-Wave 	Device: Beneden Woonkamer Voor Motion Sensor Set to Off/Closed/No Motion
Jan-12 16:40:21 	  	RFXCOM 	29 (CheckTransmitters) xmitter #1 new state:Idle
Jan-12 16:40:21 	  	RFXCOM 	29 (XmitRxChar) Response xmitter#1 was 33
Jan-12 16:40:21 	  	RFXCOM 	29 (sockDataArrival) TCP 192.168.0.5,10002 data received: 33
Jan-12 16:40:20 	  	RFXCOM 	29 (CheckTransmitters) xmitter #1 new state:WaitAck
Jan-12 16:40:20 	  	RFXCOM 	29 (CheckTransmitters) xmit length:21
Jan-12 16:40:20 	  	RFXCOM 	29 (sockSendEnd) nbr of bytes send: 6
Jan-12 16:40:20 	  	RFXCOM 	29 (TxData) TCP 192.168.0.5,10002 data xmitted: 2100E6A49700
Jan-12 16:40:20 	  	RFXCOM 	29 (DeviceCmd) transmitter #1 packet: 2100E6A49700
Jan-12 16:40:20 	  	RFXCOM 	29 (DeviceCmd) called with:X_XMIT[1]Q:A:8:39A92:1:_On
Jan-12 16:40:20 	  	RFXCOM 	29 (DeviceCmd) called with dvref:96 cmd:_On
Jan-12 16:40:20 	  	RFXCOM 	29 (ODevXmit) called with:96:_On
Jan-12 16:40:20 	  	RFXCOM 	29 (SetIOMulti) set value: 100->ref:96 ControlType:Button
Jan-12 16:40:20 	  	Device Control 	Device: Beneden Woonkamer Voor Lamp Tafel to On (100) by/from: CAPI Control Handler 
User avatar
b_weijenberg
Forum Moderator
Forum Moderator
Posts: 1744
Joined: Sun May 14, 2006 4:32 pm
Location: Netherlands

Re: Create KAKU output devices in HS3 / RFCcom

Post by b_weijenberg »

The previous setting using dev code 9 should be OK.
The AC dimmer is controlled by the remote?

Or pair the HS3 device again with the AC dimmer, put the dimmer in learn mode and transmit an ON command.
mrqnapper
Member
Member
Posts: 234
Joined: Sat Jun 25, 2011 1:08 pm

Re: Create KAKU output devices in HS3 / RFCcom

Post by mrqnapper »

I have been using these devices for several years on a row, using the same system of "including" them in HS3 with RFXCOM. I can still control the devices with the remote (Lucky me. It would not improve the waf). The dimmer is build into a wall socket... So for now I prefer to do it the software way!
mrqnapper
Member
Member
Posts: 234
Joined: Sat Jun 25, 2011 1:08 pm

Re: Create KAKU output devices in HS3 / RFCcom

Post by mrqnapper »

b_weijenberg wrote:I suppose there is a bug in the plug-in, try the output device with device code 8
Is the plugin different for Linux or Windows HS3? It has been working without a problem before so it should still work right? Any solution? If you need some more log info let me know?

Wiechert
User avatar
b_weijenberg
Forum Moderator
Forum Moderator
Posts: 1744
Joined: Sun May 14, 2006 4:32 pm
Location: Netherlands

Re: Create KAKU output devices in HS3 / RFCcom

Post by b_weijenberg »

The plug-ins are the same for Windows and Linux.
The communication with the transmitter is also OK as the transmitter responds correct with an Ack.

Contact support for more debugging steps
mrqnapper
Member
Member
Posts: 234
Joined: Sat Jun 25, 2011 1:08 pm

Re: Create KAKU output devices in HS3 / RFCcom

Post by mrqnapper »

I tried to pair the device pushing the learning button on the device and than pressing the on button in HS3. That did not work either! If I remove the plugin and install it again, do I also need to recreate the already created RFXCOM input / output devices again?
User avatar
b_weijenberg
Forum Moderator
Forum Moderator
Posts: 1744
Joined: Sun May 14, 2006 4:32 pm
Location: Netherlands

Re: Create KAKU output devices in HS3 / RFCcom

Post by b_weijenberg »

Re-install of the plug-in does not help!! It operates correct as the trace information is OK.

Are you sure it is a RFXmitter and not a transmitter?

Again: Contact support for more debugging steps
Post Reply

Return to “Rfxcom Receivers & Transmitters Forum”