[quote=“lolodomo, post:600, topic:170604”][quote=“mho, post:599, topic:170604”]I did not did succeed in using the device creation tab to change your BinaryLight device into a DimmableLight device.
These are my settings of the RFXtrx controller device:
Settings tab:
AC and X10 are enabled, the rest is disabled.
On the device creation tab I enter 11 in Unit code (the altid of the device I want to dim is RC/L2.0/03AB872/11 and in RFXmngr that’s working). After that I press the button: Add AC dimmer. Nothing happens, I am not even prompted to save.[/quote]
You just forgot to enter the remote id.
Enter 03AB872 in the remote id field, enter 11 in the unit code field; push the button “Add AC dimmer”.
If you have taken a look in the logs, you would have discovered a message telling you that your remote id is not valid. Unfortunately, there is no way with the flash interface to popup a message window. So the user is not informed about errors ! Not very cool, I know.[/quote]
That’s it! The devil is in the details…
Thanks very much, it works perfect now!
Setting up my vera3 with rfxcom transceiver and having a couple of issues.
I have tried th following:
I upload all the alpha 6 files (from alpha6 in tags – RFXtrx Gateway) using the upload files section on ui5 (tried through google chrome and ie)
Restart Luup
Create device and use rfxtrx.xml as the Upnp Device Filename.
Restart luup
But when I go into serial port configuration I try and select used by device as “rfxtrx controller device” but its not in the list, only new item is [].
Also when I go to the devices tab he controller has been added as a generic device…
I’ve added initial support for Mertik (G6R-H4T1) / Heaters. Still working on finalizing the code though. Let me know if/how you want to merge the code changes.
I’ve added initial support for Mertik (G6R-H4T1) / Heaters. Still working on finalizing the code though. Let me know if/how you want to merge the code changes.[/quote]
Join the updated files here and I will merge them in code.mios.com.
I hope you start from the files currently in the trunk…
[quote=“Intrepid, post:614, topic:170604”]I’m about ready to order the rfxcom. I looked through the wiki post of compatible devices and saw ‘us x10 iighting’ and ‘us x10 security’.
‘X10 security’ means the ds10a and similar security system sensors, correct?
‘x10 lighting’ means all other RF devices like palmpad remotes, keychain remotes, etc?[/quote]
Be carefull, you will need the RFXtrx310/315 and not the RFXtrx433.
X10 security is relative to alarm, smoke detectors, …
[quote=“lolodomo, post:615, topic:170604”][quote=“Intrepid, post:614, topic:170604”]I’m about ready to order the rfxcom. I looked through the wiki post of compatible devices and saw ‘us x10 iighting’ and ‘us x10 security’.
‘X10 security’ means the ds10a and similar security system sensors, correct?
‘x10 lighting’ means all other RF devices like palmpad remotes, keychain remotes, etc?[/quote]
Be carefull, you will need the RFXtrx310/315 and not the RFXtrx433.
X10 security is relative to alarm, smoke detectors, …[/quote]
thanks for that. US x10 is on 310/315mhz, and most of the other cool stuff (oregon scientific, etc) is 433? there’s not one transceiver for both?
[quote=“Intrepid, post:616, topic:170604”][quote=“lolodomo, post:615, topic:170604”][quote=“Intrepid, post:614, topic:170604”]I’m about ready to order the rfxcom. I looked through the wiki post of compatible devices and saw ‘us x10 iighting’ and ‘us x10 security’.
‘X10 security’ means the ds10a and similar security system sensors, correct?
‘x10 lighting’ means all other RF devices like palmpad remotes, keychain remotes, etc?[/quote]
Be carefull, you will need the RFXtrx310/315 and not the RFXtrx433.
X10 security is relative to alarm, smoke detectors, …[/quote]
thanks for that. US x10 is on 310/315mhz, and most of the other cool stuff (oregon scientific, etc) is 433? there’s not one transceiver for both?[/quote]
I’ve branched of off @38 (Sep-30). The attached code is not final, will do some more updates to it. But you can merge this and review the code. I’ve tried to stick to your coding style as much as possible. CMD_HEATER_UP and CMD_HEATER_DOWN are not yet implemented (will need to figure out what works best in the UI for this, might use the temp. setting). switchPower is also not implemented yet.
Note that I’ve added ToggleState support, but only for limited nr. of devices (will need more work). I also had to change the string.find in actOnMessage and findChild to not use regex (should also be a bit quicker).
Does anyone know why when I switch out batteries of my Oregon Scientific temp sensors they show up in Vera as bunch of completely new device IDs? It’s kind of annoying having to go and change sensor device# in scenes and other codes every time it happens. Is this how OS supposed to work? I have three OS sensors on each of the 3 OS channels. I am using RFXrec433. Thanks.