Hello I am very new to Home Automation. I just bought the new USB transceiver from Rfxcom. I would like to receive a signal when I push the doorbell (KAKU ACDB-6500AC). When I start the RFXmngr and I push the doorbell I see no response. I am using a trial of HomeSeer, and nothing in the event log. When I push a button on a KAKU APA3-1500R then I see the following in the event log from HS2:
26-3-2012 21:21:38 RFXCOM subtype = AC
26-3-2012 21:21:38 RFXCOM Sequence nbr = 188
26-3-2012 21:21:38 RFXCOM ID = 03BAC4A
26-3-2012 21:21:38 RFXCOM Unit = 3
26-3-2012 21:21:38 RFXCOM Command =
26-3-2012 21:21:38 RFXCOM On
26-3-2012 21:21:38 RFXCOM Signal level = 6
26-3-2012 21:21:38 RFXCOM (getHSdevice) input device 'AC[EEB1282]a' found
26-3-2012 21:21:38 RFXCOM (display_E_a) Sensor: AC[EEB1282]a Device:\2 Cmd:2 Dim:100
I try the same with the motion sensor AWST-6000 And nothing in the event log.
The following plugins are installed.
X10 CM15AUSB, , RFXCOM
What can I do.
Rfxcom USB 433.92MHz transceiver and KAKU
Moderator: b_weijenberg
- b_weijenberg
- Forum Moderator
- Posts: 1746
- Joined: Sun May 14, 2006 4:32 pm
- Location: Netherlands
Re: Rfxcom USB 433.92MHz transceiver and KAKU
Disable all protocols in the RFXtrx except the AC protocol. This will make the receiver more sensitive to the AC protocol.
It can happen that a remote or pushbutton is outside the margins of the protocol and not received therefore.
It can happen that a remote or pushbutton is outside the margins of the protocol and not received therefore.
Re: Rfxcom USB 433.92MHz transceiver and KAKU
Thank you, now I can see the signal when using the doorbell. But I hope that I can enable other protocols also, because I want to buy some Oregon Scientific sensors. Is this problem also seen with the LAN version of the transceiver ? Will this be resolved in a newer firmware version ( I used version 29).
- b_weijenberg
- Forum Moderator
- Posts: 1746
- Joined: Sun May 14, 2006 4:32 pm
- Location: Netherlands
Re: Rfxcom USB 433.92MHz transceiver and KAKU
Some protocols use a timing that is very close to each other and if the transmitter is outside the limits it will be detected as another protocol if all protocols are enabled.
This can never be solved in firmware. You can test which protocol decreases the sensitivity for your AC doorbell button: In RFXmngr on the Main tab enable one by one Oregon, AD, Mertik, Hideki (TFA), HomeEasy EU, ARC.
This can never be solved in firmware. You can test which protocol decreases the sensitivity for your AC doorbell button: In RFXmngr on the Main tab enable one by one Oregon, AD, Mertik, Hideki (TFA), HomeEasy EU, ARC.
Re: Rfxcom USB 433.92MHz transceiver and KAKU
Mmmm. now there is no signal from the KaKu doorbell. The only protocol I enabled is AC. The first time I was happy, but now I am disappointed. I does not work very stable.....
- b_weijenberg
- Forum Moderator
- Posts: 1746
- Joined: Sun May 14, 2006 4:32 pm
- Location: Netherlands
Re: Rfxcom USB 433.92MHz transceiver and KAKU
If the button is not received close to the receiver contact support to see if the button can be analyzed.
The number and type of walls in between have impact.
The number and type of walls in between have impact.
- Attachments
-
- RF.jpg (18.4 KiB) Viewed 5819 times