Page 1 of 1

Receiver not show KAKU device activity?

Posted: Mon Apr 05, 2010 4:46 pm
by DJF3
Hi,

For some reason I never see any KAKU devices appearing in my logs (HS or RFXreceiver).
Using latest versions of all software

RFXCOM receiver module:
Version request to receiver => F020
4D50538F Version Master=50 Slave=8F

KAKU devices
Wall switch: AWST-8800 (niet 8802!) (http://www.vego.nl/klikaanklikuit/04/wst_8800.htm)
Doorsensor: AMST-606 (http://www.klikaanklikuit.nl/product_detail.asp?id=46)

In the RFXreceiver program I see no packets from any of my KAKU devices.
HS receiver configuration: enabled: X10 / ARC / OS / AC / HEU / RSSI

Any ideas?

Re: Receiver not show KAKU device activity?

Posted: Mon Apr 05, 2010 6:19 pm
by b_weijenberg
Try with HE EU disabled.

What does RFreceiver display?

Re: Receiver not show KAKU device activity?

Posted: Wed Apr 07, 2010 2:59 pm
by DJF3
The WST-8800 wall-switch is working after replacing the battery :D
The Door-sensor (AMST-606) is still not working. Will find a second sensor to see if it might be broken.

All RF enabled in RF Receiver app, just like HS which has everything enabled except for ATI.

Re: Receiver not show KAKU device activity?

Posted: Wed Apr 07, 2010 4:42 pm
by b_weijenberg
Disabling HEU will improve the KAKU detection and disabling AC will improve the HEU detection.

It is not such a good idea to use KAKU or HEU door and motion sensors in a Home Automation environment. They perform perfect in a stand-alone situation but those sensors produce a lot of RF activity which disturbs other RF sensor data. And because they transmit for about 3 to 5 seconds you will have a delay in transmitting commands with the RFXCOM transmitter.

Re: Receiver not show KAKU device activity?

Posted: Sat Apr 17, 2010 2:38 pm
by DJF3
Update: everything seems to work except for 2 AMST-606 door-sensors.. Will continue to do more testing.
DJ

Re: Receiver not show KAKU device activity?

Posted: Fri Jul 16, 2010 12:27 am
by luria
I have the same trouble with the Nexa equvivalent of AMST-606. I have two of these, neither show any activity in Homeseer. Both, however, work flawlessly in xpl-perl.

Re: Receiver not show KAKU device activity?

Posted: Fri Jul 16, 2010 9:38 am
by AshaiRey
Please keep in mind that the AMST-606 isn't the best sensor that KaKu have.
All other devices of Kaku are working fine here but i gave up on these doorsensors.

Re: Receiver not show KAKU device activity?

Posted: Fri Jul 16, 2010 11:03 am
by b_weijenberg
luria, if the sensor is received in another program like xPL-Perl or RFreceiver the AMST606 should also be received as Input Sensor in the Homeseer RFXCOM plug-in. And enable the On/Off for AC devices in the configuration so that an On/Off status is displayed and not a numeric value.

Re: Receiver not show KAKU device activity?

Posted: Mon Jul 19, 2010 12:06 am
by luria
I was finally able to aquire them when I turned off all other protocols other than AC (i have a lot of Oregon stuff and a few other sensors). Their reliability seems to be far worse in homeseer compared to both xpl-perl and Domotiga. There should be no neglible difference, hardware setup is roughly the same (distance is about 6 meters with a wooden wall in between). I'll retry with Domotiga/xpl perl without touching anything, if results are comparable I'll go for Visonic instead. If else I'll report back.

Re: Receiver not show KAKU device activity?

Posted: Mon Jul 19, 2010 1:26 am
by Digit
Luria,
What you are saying is that the RFXCOM is performing better or worse depending on the software you use to receive the data it produces. Yeah right.

My first thought: there CANNOT be a difference. If the RFXCOM receiver is being treated (and configured !!) in exactly the same way by the various 'systems' you've used, it cannot be that you see different results. You're looking through different glasses to the same object (=the RFXCOM receiver) and seeing different things? Don't blame the object before you've carefully examined the glasses you used. Did you? In fact, you can't without much effort, so your conclusion may be wrong; and maybe it's better to rephrase your reliability claim.

Re: Receiver not show KAKU device activity?

Posted: Mon Jul 19, 2010 9:14 am
by b_weijenberg
I agree for the software part with Robert.
But if the Homeseer hardware system does not have a clean power on the USB interface it can disturb receiving. If the USB power is clean it should operate equal to any other system.

If you connect the receiver to Homeseer and before another system was connected to the receiver you have to go to the RFXCOM - Interfaces tab and Modify - Save the receiver settings (with the appropriate protocols enabled and at least AC) to be sure the correct protocols are enabled. The receiver/transmitter settings are not restored at every Homeseer start-up.

Re: Receiver not show KAKU device activity?

Posted: Mon Jul 19, 2010 9:41 pm
by luria
As I said in my previous post: There really should be no difference between the different software setups. Please do not interpret this as a flame war. I'll retry with domotiga/perl-xpl - even if sensor/receiver distance is roughly the same, other things may interfere (I have added some sensors to the setup), the Nexa sensors may already have been on the edge of useful receiving distance, or as previous poster points out, - I'm actually using a different USB hub setup.

Re: Receiver not show KAKU device activity?

Posted: Fri Jul 23, 2010 1:06 pm
by luria
Just a short update: One of the sensors seem to operate reliably. I have enabled all the protocols i need (x10, ac,arc) without apparent degradation. Strange, since homeseer was unable to detect it before i turned off all other protocols. The other sensor is still only working intermittently. However, this may be a range issue, as it's signal has to pass a wall diagonally. Swapping sensors around has no effect. I'm pretty sure that these results will be consistent across platforms, and enjoy my one cheap sensor. Having it on a patio door which lifts upward, then turns outwards is probably ideal for these sensors problems with fast movements.