I’m trying to set up ATI remote wonder II with the USB RFXtrx plugin.
I have installed the plugin , enabled ATI in the plugin settings tab and Saved RFXtrx Settings.
My settings tab shows alpha 6, firmware v55.
What next?
[quote=“drag0n, post:1, topic:173104”]I’m trying to set up ATI remote wonder II with the USB RFXtrx plugin.
I have installed the plugin , enabled ATI in the plugin settings tab and Saved RFXtrx Settings.
My settings tab shows alpha 6, firmware v55.
What next?[/quote]
Push a button on your ATI remote and a new device will be created automatically. Then an event on this new Vera device will be produced each time you push a button of the remote; the scene number is the code of the button you can find in the RFXtrx manual.
I have pushed remote buttons but can’t see any device that has been created.
I know the remote is functional scene I’ve tested it with a PC (using the ATI receiver).
Any logs/other tests I do to see what’s wrong?
The remote has been assigned a remote ID of 1 (verified by the # of flashed after a long press on the remote PC button).
Is the ATI remote received in RFXmngr?
Firmware version needs to be 49 or up.
ATI needs hardware version 1.0 (is displayed in the 1st response in RFXmngr)
And good to know; the following protocols will be degraded or even stopped if ATI is enabled: Meiantech/Atlantic, Oregon, Visonic, Mertik, AD/LightwaveRF
Thanks, I managed to create the ATI device which now appears on Vera as RFX Remote RC4/00.
Using RFXmngr I found out that RFXCom will only recognize commands if you press and hold the button for a second or two.
A short key press is usually (but not always) ignored with RFXCom.
I am now able to trigger scenes using Vera and the ATI remote. However I’m getting very inconsistent results.
Sometimes a 2 second key-press will trigger a scene and sometimes not.
Sometimes I need to keep holding the key for 10 - 13 seconds until the scene is triggered.
Some commands are ignored even if I keep holding the button for 30 seconds 
Is anyone else using the ATI Remote Wonder? Are you getting better results? Any suggestions?
First test with RFXmngr to check that all buttons are detected.
It is known that the transmit range of the ATI Remote Wonder II is limited.
Is the performance better if only ATI receive is enabled?
I have enabled only ATI all along.
I don’t think it’s a range issue, since I get the same inconsistent results from a distance of less than 1 foot
These same buttons are always detected with RFXmgr within 1 - 2 seconds.
Using the plugin the same buttons are sometimes detected, sometimes ignored, sometimes detected only after holding the button pressed for a long time (10 - 15 seconds)
Can you recommend another remote that works better with RFXCom?
[quote=“drag0n, post:7, topic:173104”]I have enabled only ATI all along.
I don’t think it’s a range issue, since I get the same inconsistent results from a distance of less than 1 foot
These same buttons are always detected with RFXmgr within 1 - 2 seconds.
Using the plugin the same buttons are sometimes detected, sometimes ignored, sometimes detected only after holding the button pressed for a long time (10 - 15 seconds)[/quote]
With the version in the trunk (version being in development), you have at the bottom of the Settings tab the display of each message received. Can you check that a new message is received each time you press a button of the remote ?
I see no reason why it would work with RFXmngr and not with the plugin.
Can you recommend another remote that works better with RFXCom?
I bought recently a XDom remote but unfortunately the remote has never worked. So I was never able to test it with the RFXtrx.
The Marmitek X10 remotes can be used, for example EasyTouch35 or EasyControl8.
But only X10 on/off commands are received from these types.
I’ve installed the version in the trunk.
The problem seems to be that it usually requires a very long keypress for the message to be received.
It takes between 2 to 30 seconds of constant holding the remote button until the settings tab displays the new message, such as (for pressing #1):
Last received message:06 30 04 18 00 0D 67Once the message is received scene execution is always immediate.
I couldn’t find any pattern in it. Sometimes a very short keypress will generate the message, and sometimes it can take 30 seconds or more.
This is for the same keypress, from the same physical location in the room.
Note that I didn’t encounter the same problem when testing with RFXmgr.
Have you enabled the same protocols whenusing RFXmngr or VERA?
If additional protocols are enabled when using VERA it is possible that the ATI receiving is not as good
There is no specific setup saved for the plugin.
As you know, the setup is stored directly in the RFXtrx.
Other possibility that could explain a worst reception: the RFXtrx is behind a hub when connected to the Vera ?
I have disconnected the USB hub and connected RFXtrx directly to my VeraLite without any noticeable change.
Still requires a very long keypress for the message to get through.
The ATI protocol is the only protocol enabled.
Distance from the RFXtrx unit also doesn’t seem to be a factor.
[quote=“drag0n, post:13, topic:173104”]I have disconnected the USB hub and connected RFXtrx directly to my VeraLite without any noticeable change.
Still requires a very long keypress for the message to get through.
The ATI protocol is the only protocol enabled.
Distance from the RFXtrx unit also doesn’t seem to be a factor.[/quote]
Did you check the logs (file /var/log/cmh/LuaUPnP.log) in case there would be anormal messages relative to the plugin ?
To summarize:
- key press systematically and instantly received by RFXmngr
- key press sometimes no more received by the plugin
Does it mean that it works well after a restart of the Vera and then suddenly you have the problem ?
I have implemented nothing to detect out-of-sync messages, I will check if RFXmngr has done it.
I don’t really think it could help for your particular problem but I just committed a change that detects and ignores bad starting messages. The detection is not 100% reliable (the used protocol is not appropriate for a reliable detection) but that’s already better than nothing.
I have now purchased an ATI Remote Wonder remote which works perfectly with this plugin.
Scenes are triggered instantly with normal key press (no key holding required).
I’m not sure my previous problems were due to a general problem with the Remote Wonder II remotes or were specific to my remote.
in any case I’m happy to report that everything is working nicely with the ATI Wonder.
Thanks lolodomo for a great plugin and all your help 