[quote=“Intrepid, post:538, topic:170604”][quote=“lolodomo, post:534, topic:170604”][quote=“Intrepid, post:533, topic:170604”]Any idea about adding support for these?
At my knowledge, it is a product supported by the RFXCOM RFXtrx.
First question would be to know if it used 433 MHz ?[/quote]
Reply from rxfcom:
No, this type is not supported. The RFXtrx433 can control rollertrol.com motors.[/quote]
Oups, the “not” was missing in my sentence: it is not a product supported …
[quote=“DRuw, post:539, topic:170604”]Hello all!
First of all, let me apologise for my noob-ness…
I am a complete amature in domotica but I am very eager to learn:)
I bought some items including a Vera3 and a RFXCOM unit but I cant seem to get them to work for some reason.
It starts with the manual in the topic start: I cant seem to get the files uploaded since my vera only displays the first 10 luup files “upload boxes”.
I thought that in that case, I can install the app in the “Install Apps” menu and that worked: plugin appeared.
Now the problem started… it says IP Address attribute must be configured. and the RFXCOM controller device notes a red flag with “Lua Startup Failure”.
The Serial port has been changed acc. starter post but this doesnt change anything.
What am I doing wrong?
If I go to the settings and change the “Controlled via” dropdown to “RFXCOM controlled device” the device dissapears… (crossreference I think?)
I am guessing that my Vera does not know where my RFXCOM is and needs an adress or something but where can I find this?
Thanks for the help!!
edit: when I go to the settings of the RFXCOM controller device, the only thing I can change in teh Settings tab is the Harrison curtain (which I can add)
edit2: when I create another device in the apps-> rfxcom menu, a second one appears (same error) but when I want to remove this one, I have to remove the complete plugin as well???
edit3: when I change the controlled via window to ftdi_sio (which I recognozed from the serial port settings, it error disappears but how do I add devices then? (and is this even correct???)[/quote]
I think you have installed the wrong plugin.
What RFXCOM product did you buy ? USB or LAN version ?
It exists 2 Vera plugins, one for each product, one for the USB RFXtrx433 (my plugin) and one for the RFXLAN managed by evanes.
If you installed from the App Store, you installed the plugin for the RFXLAN as my plugin is not yet available on the App Store.
To upload the files, you can do it in several steps. Just restart after uploading all the files.
[quote=“lolodomo, post:535, topic:170604”][quote=“lolodomo, post:532, topic:170604”][quote=“TommyE, post:531, topic:170604”][quote=“lolodomo, post:530, topic:170604”]For JD101, you have to push the test button on the KD101 and a dev ice will be added in the Vera.
The device created will be a security remote device, not a smoke detector. This device has the ability to send a panic order to the smoke detectors.[/quote]
I tried that already, to no avail.
My detector says KD-101LD, maybe it is not the same thing?
Also, which RFXCOM protocol do I have to enable for the KD-101
Thanks
Tommy[/quote]
I don’t know, that’s not mentioned in the RFXtrx user manual. You have to ask RFXCOM support.[/quote]
I was informed (PM) that the protocol to enable is X10.[/quote]
Finally, after checking, RFXCOM informed me that KD101 does not require X10 protocol enabling. KD101 is always taken into account.
RFXCOM tested with model KD-101LA.
Ap15e reported to me a positive feedback using a KD101 clone: Flamingo FA20RF
So, for the KD-101LD, you might need to exchange directly with RFXCOM support.
[quote=“lolodomo, post:540, topic:170604”]That would be even better if you can provide directly the text (and pictures ?) for the wiki page.
You are welcome if you want to contribute to the wiki page.[/quote]
While its always nice to have people visit my blog (for some insightful commentary on the world of HA 
(yeah right!) - i agree, it would be sensible to use the wiki. I assumed it would need to go there eventually, maybe at Beta or full release stage. I think i have an account to the wiki site, so happy to help out there too if you want to give me access as an editor.
While you do that, here’s a link to an early draft of my next post on the 433mhz Protocols. Now Vera’s Working In 433Mhz – There’s A World Of Different Protocols | Node Central - please let me have any comments/suggestions you have.
Hi folks,
Lolodomo, thanks for your hard work !
I’ve start digging into the Blyss/Avidsen support, that the last firmware of the RFXtrx is supporting.
So I’ve bought one of the Blyss plug to see how it was working.
Those devices are one way only (for 433Mhz ones supported by the RFXtrx): a message is sent from a remote traditionally or in our case the Vera.
So it is far more complex than the X10 security devices 
On another box, a association message is issued to the plug, then off/on message are sent.
So we need those four messages from the RFX/TRX an I guess a particular modus operandi to create the device (I guess something like a manual process that would include this association message).
Anyone would have seen those message codes somewhere ?
Chris
Oups, actually found the documentation on RFXcom web site.
0x0B - 0x15 - 0x00 that’s for Blyss.
then seq number
then id+ groupcode + unitcode.
then the cmd: 0x02 for group on, then seqcmdnbr = 0x00
Will try to code over the next days and see how it works.
Maybe a silly question, but what is the difference between alfa6 and the version that is available at mios app store? There it is named v1.1
It erxists 2 plugins for two different RFXCOM products.
In code.mios.com, the two versions are available:
RFXcom Gateway for the RFXLAN product
RFXtrx Gateway for the USB RFXtrx product
At Mios app store, only the first plugin is available, mine is not yet (will be soon).
[quote=“cboulang, post:546, topic:170604”]Oups, actually found the documentation on RFXcom web site.
0x0B - 0x15 - 0x00 that’s for Blyss.
then seq number
then id+ groupcode + unitcode.
then the cmd: 0x02 for group on, then seqcmdnbr = 0x00
Will try to code over the next days and see how it works.[/quote]
The message for Blyss is described in the RFXCOM SDK.
What is different with similar protocols is that you have a notion of group. That’s not clear for me.
And sorry, I did not understand your explanations relative to the association messages.
The Blyss remote has 4 On/Off buttons and a group code (a b c d) switch.
And each remote has a unique ID.
These parameters are used by the RFXtrx433 to transmit a Blyss command.
See the picture of the Blyss remote
[quote=“lolodomo, post:524, topic:170604”]What’s new in version alpha 6:
Hi lolodomo, I’ve had a go at installing VCPE (by eterlogic.com) on a Windows 7 machines but I just can’t seem to work out what i need to update in Alpha 6 so it looks for that rather than a local port, I tired to create a device type in VCPE for the rfxrtx433 to be a TCP server? Was that right ? What settings did you use ?
What is missing, IMHO:
FYI, the firmware defines what are the protocols enabled by default. They are updated after each firmware installation.
[quote=“parkerc, post:551, topic:170604”][quote=“lolodomo, post:524, topic:170604”]What’s new in version alpha 6:
Hi lolodomo, I’ve had a go at installing VCPE (by eterlogic.com) on a Windows 7 machines but I just can’t seem to work out what i need to update in Alpha 6 so it looks for that rather than a local port, I tired to create a device type in VCPE for the rfxrtx433 to be a TCP server? Was that right ? What settings did you use ?[/quote]
VSPE, not VCPE.
I wrote an explanation on this french forum: http://www.touteladomotique.com/forum/viewtopic.php?f=48&t=7218&start=324#p68693
If a Google translation is not sufficient, I will explain again.
But it is very simple.
Main things to remind: define a device of type TcpServer in VSPE and use port 10000. Then create a new device in Vera UI setting the IP address with the IP of your PC.
That’s all.
[quote=“b_weijenberg, post:550, topic:170604”]The Blyss remote has 4 On/Off buttons and a group code (a b c d) switch.
And each remote has a unique ID.
These parameters are used by the RFXtrx433 to transmit a Blyss command.
See the picture of the Blyss remote
Ok.
Is there something special to consider regarding the association process, like cboulang tried to explain ?
Nothing special.
Pair the Blyss with an ID, group code and unit number. From now on you will be able to control this Blyss module using these codes.
Bert,
so from your standpoint at the pairing does the plug (in my case) ever send a message or not ?
if not, it would mean that, where on x10 we were receiving Id from devices, we have to create and assign id/groupid to the device ?
if this is corect, does it mean that we need to manage (and store ) id, group id, etc within the plugin as it would failed if pairing details are given by the user, may reuse id+group id that have been used already and therefore break the whole stuff ?
Chris
[quote=“b_weijenberg, post:555, topic:170604”]Nothing special.
Pair the Blyss with an ID, group code and unit number. From now on you will be able to control this Blyss module using these codes.[/quote]
No association process is required ?
And what about the group code and unit number of a device (socket for example) ? Is it something that is hardcoded ? Or can the user do the setup of these two data ?
[quote=“cboulang, post:556, topic:170604”]Bert,
so from your standpoint at the pairing does the plug (in my case) ever send a message or not ?
if not, it would mean that, where on x10 we were receiving Id from devices, we have to create and assign id/groupid to the device ?
if this is corect, does it mean that we need to manage (and store ) id, group id, etc within the plugin as it would failed if pairing details are given by the user, may reuse id+group id that have been used already and therefore break the whole stuff ?
Chris[/quote]
I think we have to store the remote id, the group code and the unit number to identify a Vera device, that is the same principle as for the other protocols already managed. And the association feature of the plugin will allow users to define a unique Vera device even if they have several remotes controlling the same physical device.
The only think I need to understand is how is done the association between a remote button and a socket device, and if the group code / unit number is defined by the remote or by the controlled unit ?
Is there a button on the socket device to validate the association for example ?
[quote=“lolodomo, post:542, topic:170604”]I think you have installed the wrong plugin.
What RFXCOM product did you buy ? USB or LAN version ?
It exists 2 Vera plugins, one for each product, one for the USB RFXtrx433 (my plugin) and one for the RFXLAN managed by evanes.
If you installed from the App Store, you installed the plugin for the RFXLAN as my plugin is not yet available on the App Store.
To upload the files, you can do it in several steps. Just restart after uploading all the files.[/quote]
Damn… that was kinda stupid… thanks for the help!
RFXCOM is working fine now… now I have other issues with my Duwi thingies but one thing at a time.
Thanks again for the support!
[quote=“lolodomo, post:558, topic:170604”][quote=“cboulang, post:556, topic:170604”]Bert,
so from your standpoint at the pairing does the plug (in my case) ever send a message or not ?
if not, it would mean that, where on x10 we were receiving Id from devices, we have to create and assign id/groupid to the device ?
if this is corect, does it mean that we need to manage (and store ) id, group id, etc within the plugin as it would failed if pairing details are given by the user, may reuse id+group id that have been used already and therefore break the whole stuff ?
Chris[/quote]
I think we have to store the remote id, the group code and the unit number to identify a Vera device, that is the same principle as for the other protocols already managed. And the association feature of the plugin will allow users to define a unique Vera device even if they have several remotes controlling the same physical device.[/quote]
I agree, but if you refer to the x10 or the code I read, this is where I identify the catch: you are not only storing id sent by the device for later access, I understand there that you have to create the Id, group id, and iterate for each new device. if you have already done this for other device, that’s great. if not it means a quite new laege piece of work to be done.
The only think I need to understand is how is done the association between a remote button and a socket device,let's wait for Bert feedback.
and if the group code / unit number is defined by the remote or by the controlled unit ?You mean a Blyss remote or the Blyss box in this case ? I guess they both can do it. That's what i understand from the blog of the arduino guys who hacked thr Blyss stuff. may be I was over assuming.
Is there a button on the socket device to validate the association for example ?no, you press for several second the only button on the plug/socket, then the remote, there's association, and you're done. the only other thing you can do it remove the association with the remote by pressing the button for a long time.
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules