HE 306EU Configuration

Post by **DutchAdept** » Tue Aug 04, 2009 7:50 pm

Hi,
To alleviate my KaKu problems I aquired the HE 306EU chime. I've been trying to configure it in Homeseer with the beta rfxcom plugin, but to no avail. The datastream from the pushbutton is only visible with level2 debug (though the device can be added as an AC sensor in the regular fashion). The data tells me it's an AC device with CMD:2 and DIM100. I really don't have a clue what to do next. After adding it as an AC I tried with X10 devicecode L1, but no luck. I did see on the back of the pushbutton an imprint in the plastic like the rotating selectors of KaKu with the arrows pointing to A and 8, but I don't know if that is saying anything. The Chime itself needs to be paired, but doesn't respond to any signal from the RFXmitter. Pushbutton to chime itself works OK, with good range.

Post by **b_weijenberg** » Tue Aug 04, 2009 8:06 pm

Try with an ARC Module in the plugin with address A8.

Did you try with the HE CHIME device?

Post by **DutchAdept** » Tue Aug 04, 2009 9:06 pm

Yup, but as reported it doesn't even show up in the normal logs (normally undeclared arc devices show up as E11 ? On for example). This button only shows in the raw data with CMD:2 and DIM100. I tried the following configs: ARC Chime/module, AC , HE EU Chime, HE EU Module.... no go. Also the chime itself doesn't respond to any command in the program mode. But direct pushbutton signal to chime works great, and no problems getting the two paired.....

Post by **r_255** » Tue Aug 04, 2009 9:18 pm

try to make a event, wich reacts on any devicevalue change.
wich should trigger the chimes.

I just paired my chime with the rfxcom to be sure.. and works for my setup I got the same setup as you working here.

1 push button he eu
1 chime he eu
1 chime kaku

What i did :

1 Push the he eu button a few times to make clear the plugin sees it.
2 go to the input device tab at the rfxcom plugin
3 push the add button and add device until a device like this one is found : AC[10357680]a ( code can be different )

4 fill in the required fields with your info and the plugin will give it a device code like ^10

now you can make an event wich reacts on device any value change and trigger any device in your homeseer list.

Post by **b_weijenberg** » Tue Aug 04, 2009 9:56 pm

The push button is received as Input Device.
Check the box "Use On/Off status for AC remotes" on the Input device main config page to get On/Off statuses instead of numbers.
See chapter 8 http://www.rfxcom.com/documents/RFXCOM% ... 0Guide.pdf

The HE306EU must be configured as HE EU CHIME on the Output device config page. See chapter 11

Post by **DutchAdept** » Tue Aug 04, 2009 10:45 pm

I allready configured about 60 HE eu devices succesfully, remotes and modules/dimmers. The pushbutton should not differ from lets say a timer remote or wall switch right? I have used the ac=on/off setting in the plugin from the start because I have about 15 wallswitches and 4 HE EU remotes, so I never used values. I read the manual again, but described there is just what I have been doing. I clear all heard, add the doorbel device and ring a couple of times to see if it turns up in the logfile. It doesn't and only with debug level 2 I get to see any data concerning the device...... But RFXcom must see the device otherwise I wouldn't be able to add it. Even with all combinations of receiving protocols it's a no go. I'm stumped, and probably overlooking something extremely obvious, but still without a doorbell [:I]

Post by **DutchAdept** » Wed Aug 05, 2009 8:10 pm

This chime experiment turned out some odd results. Both the HE EU Chime and the KaKu ARC chime do not respond when configured as Chime devices. The will not pair and cannot be triggered. But Kaku Chime configured as ARC Module does respond and pairs well, and the same goes for the HE EU Chime configured as a HE EU Module. Beats me but I can use all my chimes using the on command of both modules now[:D]