Cheap 433mhz sockets compatible with rfxcom at "action"
Moderator: leecollings
- Redguy
- Posts: 33
- Joined: Saturday 19 November 2016 21:26
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 3.5877
- Location: Maassluis
- Contact:
Cheap 433mhz sockets compatible with rfxcom at "action"
Action (netherlands) is currently selling "flamingo" plugin typer socket sets. They contain 3 plugin sockets and a 4 channel+master rf remote..
The sockets needto belearned to which code they respond and are able to learn multiple codes to respond to (itested with2 codes)
The sockets are compatible with my rfxcom (433mhz) and withdomoticz and work really well. I bought 3 sets and each came with a remote with a unique ID, the sets were only 9 euro's each..
Just thought i would share this
The sockets needto belearned to which code they respond and are able to learn multiple codes to respond to (itested with2 codes)
The sockets are compatible with my rfxcom (433mhz) and withdomoticz and work really well. I bought 3 sets and each came with a remote with a unique ID, the sets were only 9 euro's each..
Just thought i would share this
-
- Posts: 2
- Joined: Wednesday 23 November 2016 21:02
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Cheap 433mhz sockets compatible with rfxcom at "action"
Thanks for the research! Please share the settings in domoticz; what is the device type etc.
- Redguy
- Posts: 33
- Joined: Saturday 19 November 2016 21:26
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 3.5877
- Location: Maassluis
- Contact:
Re: Cheap 433mhz sockets compatible with rfxcom at "action"
The devices use the lighting2 type, subtype ac. The remotes each have a different base ID.
The channel buttons a - d use unit id 2-5 and are picked up by domoticz automatically. Master on/off buttons just send on or off for id 2-5 after each other.
The sockets are not bound to the remote they came with,but can be programmed to another remote as well.. I think you should be able to just set a manual id in domoticz as well..
The channel buttons a - d use unit id 2-5 and are picked up by domoticz automatically. Master on/off buttons just send on or off for id 2-5 after each other.
The sockets are not bound to the remote they came with,but can be programmed to another remote as well.. I think you should be able to just set a manual id in domoticz as well..
Re: Cheap 433mhz sockets compatible with rfxcom at "action"
Hi Redguy,
I have a couple remotes alike the one you describe, from the Action like you. However, they have two rows of 5 switches labeled 'a' to 'e', the left row is 'on' the right row is off. Also the word "impuls" is on the front. Price is about the same. The remote is not recognized by the rxfcom. Putting it in learning mode keeps on saying that no signal is received. I have tried numerous different configs, no luck. I can't find a solution on the web too.
I hope you can put me on the track to get those remotes working.
Regards,
bertdmz.
I have a couple remotes alike the one you describe, from the Action like you. However, they have two rows of 5 switches labeled 'a' to 'e', the left row is 'on' the right row is off. Also the word "impuls" is on the front. Price is about the same. The remote is not recognized by the rxfcom. Putting it in learning mode keeps on saying that no signal is received. I have tried numerous different configs, no luck. I can't find a solution on the web too.
I hope you can put me on the track to get those remotes working.
Regards,
bertdmz.
-
- Posts: 517
- Joined: Friday 12 July 2013 18:13
- Target OS: -
- Domoticz version:
- Location: Netherlands
- Contact:
Re: Cheap 433mhz sockets compatible with rfxcom at "action"
The latest module sold by Action is the smartwares/Flamingo SF501. This module is using the AC protocol and can be paired with up to 5 remote codes. Each RFXtrx433 ID-Unit code combination can be seen as a remote. The remote delivered with the modules is received by the RFXtrx.
The previous module sold by Action was the PROmax. This module is using the IT protocol and could be paired with up to 4 or 5 remote codes. The remote delivered with the modules transmits 3 protocols after each other, IT, AC and ARC. AC and ARC codes are received by the RFXtrx. Note: to remove all paired remotes: connect the module to the power (the LED in the module starts blinking) and transmit a Group Off command.
For a short period the Eurodomest module was sold. This module can be controlled using the ARC protocol. The remote delivered with the modules is not received by the RFXtrx.
Long time ago Action sold the Impuls module. This module can be controlled using the ELRO AB400D protocol. The remote delivered with the modules is not received by the RFXtrx. See chapter 7.3 in the RFXtrx User Guide for the configuration of the switch setting in the module. Remark: if on/off commands are transmitted fast the module does not switch on all commands. This can also be tested using the remote.
The previous module sold by Action was the PROmax. This module is using the IT protocol and could be paired with up to 4 or 5 remote codes. The remote delivered with the modules transmits 3 protocols after each other, IT, AC and ARC. AC and ARC codes are received by the RFXtrx. Note: to remove all paired remotes: connect the module to the power (the LED in the module starts blinking) and transmit a Group Off command.
For a short period the Eurodomest module was sold. This module can be controlled using the ARC protocol. The remote delivered with the modules is not received by the RFXtrx.
Long time ago Action sold the Impuls module. This module can be controlled using the ELRO AB400D protocol. The remote delivered with the modules is not received by the RFXtrx. See chapter 7.3 in the RFXtrx User Guide for the configuration of the switch setting in the module. Remark: if on/off commands are transmitted fast the module does not switch on all commands. This can also be tested using the remote.
RFXtrx433, RFXtrx433E, RFXtrx433XL, RFX433XL, RFX868XL
-
- Posts: 843
- Joined: Sunday 23 February 2014 17:56
- Target OS: Raspberry Pi / ODroid
- Domoticz version: mixed
- Location: Hengelo(Ov)/NL
- Contact:
Re: Cheap 433mhz sockets compatible with rfxcom at "action"
Good deal.
KAKU Smartwares/SF501 works with both RFXCom and RFLinkGateway.
Empirically [= by accident] found 'Programming method' for 2 IDs:
a. fit socket & program to first ID-code according to the user manual by pushing relevant ON-button while LED is flashing
b. pull-out and wait some seconds
c. fit again and program for second code by pushing related ON-button while LED is flashing
'Unprogram' can be achieved according to User Manual by pushing appropriate OFF-button while LED is flashing.
Example application: if you apply buttons A, B and C for individual control of switches, button D might be used for mini-group control of switches.
Just wondering whether other types of KAKU's react the same way (by design or by accident):
any experiences?
KAKU Smartwares/SF501 works with both RFXCom and RFLinkGateway.
Empirically [= by accident] found 'Programming method' for 2 IDs:
a. fit socket & program to first ID-code according to the user manual by pushing relevant ON-button while LED is flashing
b. pull-out and wait some seconds
c. fit again and program for second code by pushing related ON-button while LED is flashing
'Unprogram' can be achieved according to User Manual by pushing appropriate OFF-button while LED is flashing.
Example application: if you apply buttons A, B and C for individual control of switches, button D might be used for mini-group control of switches.
Just wondering whether other types of KAKU's react the same way (by design or by accident):
any experiences?
Set1 = RPI-Zero+RFXCom433+S0PCM+Shield for BMP180/DS18B20/RS485+DDS238-1ZNs
Set2 = RPI-3A++RFLinkGTW+ESP8266s+PWS_WS7000
Common = KAKUs+3*PVLogger+PWS_TFA_Nexus
plus series of 'satellites' for dedicated interfacing, monitoring & control.
Set2 = RPI-3A++RFLinkGTW+ESP8266s+PWS_WS7000
Common = KAKUs+3*PVLogger+PWS_TFA_Nexus
plus series of 'satellites' for dedicated interfacing, monitoring & control.
Re: Cheap 433mhz sockets compatible with rfxcom at "action"
Hi b_weijenberg,
Thanks for your reaction. I guess I have the "old" Action devices. There is no reaction at all from Domoticz. And that is a little disappointing because I bought the rfxtrx just for those devices. I find it an advantage to be able to control each device with the dip-switches inside.
I do also have an Action Pro-max set now. That is being recognized by Domoticz as a lightning 2 AC On/Off device.
Switching the light on indeed shows an "on" light bulb on the screen. Switching it off shows an "off" one. However, clicking on the light bulb on the screen does not switch on or off the device. So, Domoticz recognizes the remote but is not able to control the device. The leds on the rfxtrx do flash shortly when clicking the screen. The light bulb on the screen changes color when clicking on it. Also the text alters from 'Aan' to 'Uit' vice versa.
I am stuck now. Why is Domoticz just doing the half of what it supposed to do?
All of this leads to a situation that I have two sets of devices now (plus the rfxtrx) without being able to control or use them. I hope you can help me here with some new directions to look into. Using the old Action devices would be nice.
The big advantage of the "old" Action devices is that it uses dip-switches to set the device code. The "new" Action devices have to be told to that what button to react. I don't want to have to set all devices again if some fuse blows. That just kills the automation idea or at least introduces a buggy, uncertain situation. If you have a power outage all the devices are waiting for there device code. When Domoticz issues a light-A-on command shortly after power is restored, all other devices see that light-A-on command as master-on command. So you never know if light-A-on command only switches light-A on or that all other lights are switched on too. To be completely sure, you have to make adjustments in your software that after a power outage you delay any command until the timeout on the Action devices is gone (30 seconds). Although small, there is room for a complete breakdown of your home automation. One of the issues to solve here is how to know that a particular group of devices had a power outage. Your software can run very well on a system that had no outage at all. Food for thoughts, because if something can go wrong, eventually it will.
Although the chances such a situation arises may look small, they may be bigger if your home automation software is powered on too after an outage. It may decide that some actions are not taken whilst they should have been according the current time of day. If the software determines that it is 3 am and that it had to switch on the garden lights at 10 pm, it may very well sends a 'garden-light-on' command the moment it discovers that. That moment may lay inside the 30 seconds timeout interval. That simply depends on the software you are using and how fast it is booting. Domoticz can use delays when switching lights on or off. I do not know if this can prevent this kind of things from happening, I am not yet familiar with the software neither do I know how its build and how it records actions and states.
Kind regards,
Bertdmz.
Thanks for your reaction. I guess I have the "old" Action devices. There is no reaction at all from Domoticz. And that is a little disappointing because I bought the rfxtrx just for those devices. I find it an advantage to be able to control each device with the dip-switches inside.
I do also have an Action Pro-max set now. That is being recognized by Domoticz as a lightning 2 AC On/Off device.
Switching the light on indeed shows an "on" light bulb on the screen. Switching it off shows an "off" one. However, clicking on the light bulb on the screen does not switch on or off the device. So, Domoticz recognizes the remote but is not able to control the device. The leds on the rfxtrx do flash shortly when clicking the screen. The light bulb on the screen changes color when clicking on it. Also the text alters from 'Aan' to 'Uit' vice versa.
I am stuck now. Why is Domoticz just doing the half of what it supposed to do?
All of this leads to a situation that I have two sets of devices now (plus the rfxtrx) without being able to control or use them. I hope you can help me here with some new directions to look into. Using the old Action devices would be nice.
The big advantage of the "old" Action devices is that it uses dip-switches to set the device code. The "new" Action devices have to be told to that what button to react. I don't want to have to set all devices again if some fuse blows. That just kills the automation idea or at least introduces a buggy, uncertain situation. If you have a power outage all the devices are waiting for there device code. When Domoticz issues a light-A-on command shortly after power is restored, all other devices see that light-A-on command as master-on command. So you never know if light-A-on command only switches light-A on or that all other lights are switched on too. To be completely sure, you have to make adjustments in your software that after a power outage you delay any command until the timeout on the Action devices is gone (30 seconds). Although small, there is room for a complete breakdown of your home automation. One of the issues to solve here is how to know that a particular group of devices had a power outage. Your software can run very well on a system that had no outage at all. Food for thoughts, because if something can go wrong, eventually it will.
Although the chances such a situation arises may look small, they may be bigger if your home automation software is powered on too after an outage. It may decide that some actions are not taken whilst they should have been according the current time of day. If the software determines that it is 3 am and that it had to switch on the garden lights at 10 pm, it may very well sends a 'garden-light-on' command the moment it discovers that. That moment may lay inside the 30 seconds timeout interval. That simply depends on the software you are using and how fast it is booting. Domoticz can use delays when switching lights on or off. I do not know if this can prevent this kind of things from happening, I am not yet familiar with the software neither do I know how its build and how it records actions and states.
Kind regards,
Bertdmz.
-
- Posts: 17
- Joined: Wednesday 09 March 2016 9:18
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 3.4834
- Contact:
Re: Cheap 433mhz sockets compatible with rfxcom at "action"
Hi. Has anyone used the Smartwares SH5 range sockets with RFXtrx 433?
I am looking for some more cheap sockets, and these look good value. I might just take a punt (seems likely they will be OK) but just checking if anyone can confirm.
SH5-SF-500S/3UK
https://buyhomeeasy.co.uk/catalog/produ ... cts_id=167
Thanks.
I am looking for some more cheap sockets, and these look good value. I might just take a punt (seems likely they will be OK) but just checking if anyone can confirm.
SH5-SF-500S/3UK
https://buyhomeeasy.co.uk/catalog/produ ... cts_id=167
Thanks.
RFXtrx433E
Hive 2 Active Heating
Owl CM180 Energy Monitor
Various HomeEasy Receivers
LightwaveRF Plug-in sockets
Hive 2 Active Heating
Owl CM180 Energy Monitor
Various HomeEasy Receivers
LightwaveRF Plug-in sockets
-
- Posts: 331
- Joined: Wednesday 21 December 2016 9:11
- Target OS: Raspberry Pi / ODroid
- Domoticz version: current
- Contact:
Re: Cheap 433mhz sockets compatible with rfxcom at "action"
I built the 433 clone plugin, it allows the Raspberry Pi to completely copy 433Mhz signals without needing to know a lot about new types of encoding of the signal. I use it with the Action switches.
-
- Posts: 17
- Joined: Wednesday 09 March 2016 9:18
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 3.4834
- Contact:
Re: Cheap 433mhz sockets compatible with rfxcom at "action"
Thanks blauwebuis , please can you point me at some information on your plugin? Is this compatible with the RFXtrx 433 transceiver using other protocols?
RFXtrx433E
Hive 2 Active Heating
Owl CM180 Energy Monitor
Various HomeEasy Receivers
LightwaveRF Plug-in sockets
Hive 2 Active Heating
Owl CM180 Energy Monitor
Various HomeEasy Receivers
LightwaveRF Plug-in sockets
- zenit
- Posts: 17
- Joined: Wednesday 25 March 2015 17:40
- Target OS: Linux
- Domoticz version: Beta
- Location: Berg aan de Maas
- Contact:
Re: Cheap 433mhz sockets compatible with rfxcom at "action"
Hi,
Here's is the link to Blauwebuis his topic about cloning 433Mhz switch signals : viewtopic.php?f=65&t=21567
Here's is the link to Blauwebuis his topic about cloning 433Mhz switch signals : viewtopic.php?f=65&t=21567
- luberth
- Posts: 34
- Joined: Friday 27 April 2018 7:56
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 4.9700
- Location: Bangert 30 Andijk Nederland
- Contact:
Cheap 433mhz sockets compatible with rfxcom at "action"
Last edited by antwan on Friday 23 November 2018 21:02, edited 1 time in total.
Reason: Was in nl
Reason: Was in nl
-
- Posts: 164
- Joined: Sunday 26 April 2020 5:27
- Target OS: Linux
- Domoticz version: 2022.1
- Location: Netherlands
- Contact:
Re: Cheap 433mhz sockets compatible with rfxcom at "action"
I have the Impuls switches from Action and although Domoticz sees them, they don't react when I try to switch them. I have the rfxtrx433xl.
Hue | Zigbee2Mqtt | MQTT | P1 | Xiaomi | RFXCom | Modbus | Qlima | Solaredge
TP-Link | Plugwise | Thermosmart | Node-Red | Grafana | Master and 5 remote servers
TP-Link | Plugwise | Thermosmart | Node-Red | Grafana | Master and 5 remote servers
-
- Posts: 517
- Joined: Friday 12 July 2013 18:13
- Target OS: -
- Domoticz version:
- Location: Netherlands
- Contact:
Re: Cheap 433mhz sockets compatible with rfxcom at "action"
Impuls is not translated in receive. Use lighting1 - Impuls to control these modules.
See also chapter 2.2.2 and 7.3 in the RFXtrx User Guide.
See also chapter 2.2.2 and 7.3 in the RFXtrx User Guide.
RFXtrx433, RFXtrx433E, RFXtrx433XL, RFX433XL, RFX868XL
-
- Posts: 164
- Joined: Sunday 26 April 2020 5:27
- Target OS: Linux
- Domoticz version: 2022.1
- Location: Netherlands
- Contact:
Re: Cheap 433mhz sockets compatible with rfxcom at "action"
Got them working. Thanks.
Hue | Zigbee2Mqtt | MQTT | P1 | Xiaomi | RFXCom | Modbus | Qlima | Solaredge
TP-Link | Plugwise | Thermosmart | Node-Red | Grafana | Master and 5 remote servers
TP-Link | Plugwise | Thermosmart | Node-Red | Grafana | Master and 5 remote servers
Who is online
Users browsing this forum: No registered users and 1 guest