Howto: Raspberry Pi GPIO 433MHz Remote Sockets
Moderators: leecollings, remb0
- gizmocuz
- Posts: 2483
- Joined: Thursday 11 July 2013 18:59
- Target OS: Raspberry Pi / ODroid
- Domoticz version: beta
- Location: Top of the world
- Contact:
Re: Howto: Raspberry Pi GPIO 433MHz Remote Sockets
Okey, and then ? what protocols does it support ?
Quality outlives Quantity!
Re: Howto: Raspberry Pi GPIO 433MHz Remote Sockets
Would it be possible to dim a Nexa WMR-252 from Domoticz with this solution?
-
- Posts: 86
- Joined: Sunday 01 May 2016 0:34
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Location: NL
- Contact:
Re: Howto: Raspberry Pi GPIO 433MHz Remote Sockets
First let me start by excusing myself for being a absolute noob on this board. I just purchased a Pi3, got Domoticz and a Z-WAVE USB stick working, but also purchased the hardware suggested in this topic.
Now comes the question (which I feel somewhat stupid about asking). What tools or wires do I need to purchase to connect the pins on the boards to the GPIO? Should I get regular jumper cables?
Thanks in advance for you patience with me.
Now comes the question (which I feel somewhat stupid about asking). What tools or wires do I need to purchase to connect the pins on the boards to the GPIO? Should I get regular jumper cables?
Thanks in advance for you patience with me.
- sincze
- Posts: 1300
- Joined: Monday 02 June 2014 22:46
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2024.4
- Location: Netherlands / Breda Area
- Contact:
Re: Howto: Raspberry Pi GPIO 433MHz Remote Sockets
I would suggest 'dupont' cables just take a look at aliexpress not that expensive. I bought some male - male, male - female and female - female ones so I can experiment with all kinds of sensors.
Pass2php
LAN: RFLink, P1, OTGW, MySensors
USB: RFXCom, ZWave, Sonoff 3
MQTT: ZIgbee2MQTT,
ZWAVE: Zwave-JS-UI
WIFI: Mi-light, Tasmota, Xiaomi Shelly
Solar: Omnik, PVOutput
Video: Kodi, Harmony HUB, Chromecast
Sensors: You name it I got 1.
LAN: RFLink, P1, OTGW, MySensors
USB: RFXCom, ZWave, Sonoff 3
MQTT: ZIgbee2MQTT,
ZWAVE: Zwave-JS-UI
WIFI: Mi-light, Tasmota, Xiaomi Shelly
Solar: Omnik, PVOutput
Video: Kodi, Harmony HUB, Chromecast
Sensors: You name it I got 1.
-
- Posts: 86
- Joined: Sunday 01 May 2016 0:34
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Location: NL
- Contact:
Re: Howto: Raspberry Pi GPIO 433MHz Remote Sockets
Thanks! Ordering those now.sincze wrote:I would suggest 'dupont' cables just take a look at aliexpress not that expensive. I bought some male - male, male - female and female - female ones so I can experiment with all kinds of sensors.
-
- Posts: 784
- Joined: Wednesday 10 December 2014 13:06
- Target OS: Linux
- Domoticz version: beta
- Location: Bordeaux France
- Contact:
Re: Howto: Raspberry Pi GPIO 433MHz Remote Sockets
I'm sorry to say that GPIO hardware on this case is not usefull...rfsniffer doesn't use gpio as a "switch".
Juste create a dummy hardware and place codesend typo or on and off that all.
With this "how to" you just open and close GPIO17, who doesn't need to move.
Juste create a dummy hardware and place codesend typo or on and off that all.
With this "how to" you just open and close GPIO17, who doesn't need to move.
Domoticz stable 3.5877 for real & Domoticz beta for test
Rfxtrxe / RFLink / Milight / Yeelight / Tasmota / MQTT / BLE / Zigate
http://domo-attitude.fr
Rfxtrxe / RFLink / Milight / Yeelight / Tasmota / MQTT / BLE / Zigate
http://domo-attitude.fr
-
- Posts: 86
- Joined: Sunday 01 May 2016 0:34
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Location: NL
- Contact:
Re: Howto: Raspberry Pi GPIO 433MHz Remote Sockets
Not sure what you mean by this. Are you saying that the 433Mhz chips won't work on RPI3 to control devices like KAKU?deennoo wrote:I'm sorry to say that GPIO hardware on this case is not usefull...rfsniffer doesn't use gpio as a "switch".
Juste create a dummy hardware and place codesend typo or on and off that all.
With this "how to" you just open and close GPIO17, who doesn't need to move.
-
- Posts: 784
- Joined: Wednesday 10 December 2014 13:06
- Target OS: Linux
- Domoticz version: beta
- Location: Bordeaux France
- Contact:
Re: Howto: Raspberry Pi GPIO 433MHz Remote Sockets
That not what i'm saying...
Just try to explain that you dont have to create a gpio hardware on Domoticz to use "codesend".
Codesend + wiringpi got already all configuration to drive gpio.
The way who is shown, just turn on and off a gpio who is already drive by codesend.
This is the same way since RPI1
Just try to explain that you dont have to create a gpio hardware on Domoticz to use "codesend".
Codesend + wiringpi got already all configuration to drive gpio.
The way who is shown, just turn on and off a gpio who is already drive by codesend.
This is the same way since RPI1
Domoticz stable 3.5877 for real & Domoticz beta for test
Rfxtrxe / RFLink / Milight / Yeelight / Tasmota / MQTT / BLE / Zigate
http://domo-attitude.fr
Rfxtrxe / RFLink / Milight / Yeelight / Tasmota / MQTT / BLE / Zigate
http://domo-attitude.fr
-
- Posts: 1
- Joined: Thursday 05 May 2016 21:46
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Howto: Raspberry Pi GPIO 433MHz Remote Sockets
Hi,
I create an application like this. You are able to control the Raspberry GPIO pins from your Computer-Android-Wear device.
If you want take a look "https://github.com/tsoglani/Raspberry_SmartHouseServer"
.
I create an application like this. You are able to control the Raspberry GPIO pins from your Computer-Android-Wear device.
If you want take a look "https://github.com/tsoglani/Raspberry_SmartHouseServer"

-
- Posts: 86
- Joined: Sunday 01 May 2016 0:34
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Location: NL
- Contact:
Re: Howto: Raspberry Pi GPIO 433MHz Remote Sockets
I need some help here. I've connected everything as instructed, installed the bits as descriped, but the RFSniffer gives no numbers when clicking my (KAKU) remote. Any suggestions or ideas?
UPDATE:
When I run RFSniifer the log goes bonkers and makes Domoticz unresponsive.
UPDATE:
When I run RFSniifer the log goes bonkers and makes Domoticz unresponsive.
Code: Select all
2016-05-12 21:08:33.946 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:33.940 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:33.947 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:33.947 GPIO: 1 interrupts in queue.
2016-05-12 21:08:33.947 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:33.947 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:33.947 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:33.947 GPIO: 1 interrupts in queue.
2016-05-12 21:08:33.947 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:33.947 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:33.948 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:33.949 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:33.950 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:33.951 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:33.953 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:33.954 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:33.955 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:33.957 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:33.957 GPIO: 1 interrupts in queue.
2016-05-12 21:08:33.957 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:33.957 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:33.957 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:33.957 GPIO: 1 interrupts in queue.
2016-05-12 21:08:33.957 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:33.956 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:33.957 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:33.958 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:33.960 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:33.961 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:33.962 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:33.963 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:33.966 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:33.966 GPIO: 1 interrupts in queue.
2016-05-12 21:08:33.966 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:33.966 GPIO: 1 interrupts in queue.
2016-05-12 21:08:33.966 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:33.967 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:33.967 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:33.967 GPIO: 1 interrupts in queue.
2016-05-12 21:08:33.967 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:33.967 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:33.967 GPIO: 1 interrupts in queue.
2016-05-12 21:08:33.967 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:33.967 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:33.967 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:33.967 GPIO: 1 interrupts in queue.
2016-05-12 21:08:33.967 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:33.968 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:33.968 GPIO: 1 interrupts in queue.
2016-05-12 21:08:33.968 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:33.968 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:33.968 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:33.968 GPIO: 1 interrupts in queue.
2016-05-12 21:08:33.968 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:33.966 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:33.969 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:33.972 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:33.974 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:33.974 GPIO: 1 interrupts in queue.
2016-05-12 21:08:33.974 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:33.974 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:33.974 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:33.974 GPIO: 1 interrupts in queue.
2016-05-12 21:08:33.974 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:33.974 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:33.974 GPIO: 1 interrupts in queue.
2016-05-12 21:08:33.975 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:33.975 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:33.975 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:33.975 GPIO: 1 interrupts in queue.
2016-05-12 21:08:33.975 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:33.975 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:33.975 GPIO: 1 interrupts in queue.
2016-05-12 21:08:33.975 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:33.975 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:33.975 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:33.975 GPIO: 1 interrupts in queue.
2016-05-12 21:08:33.975 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:33.976 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:33.976 GPIO: 1 interrupts in queue.
2016-05-12 21:08:33.976 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:33.976 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:33.976 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:33.976 GPIO: 1 interrupts in queue.
2016-05-12 21:08:33.976 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:33.974 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:33.976 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:33.976 GPIO: 1 interrupts in queue.
2016-05-12 21:08:33.976 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:33.976 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:33.976 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:33.976 GPIO: 1 interrupts in queue.
2016-05-12 21:08:33.976 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:33.977 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:33.977 GPIO: 1 interrupts in queue.
2016-05-12 21:08:33.977 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:33.977 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:33.977 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:33.977 GPIO: 1 interrupts in queue.
2016-05-12 21:08:33.977 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:38.982 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:38.982 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.982 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:38.982 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.983 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:38.983 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.983 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:38.983 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.981 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:38.983 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:38.983 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.983 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:38.983 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.983 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:38.983 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:38.985 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:38.987 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:38.988 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:38.989 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.989 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:38.989 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:38.989 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:38.989 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.989 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:38.989 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:38.989 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.989 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:38.989 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:38.989 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:38.989 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:38.989 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.989 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:38.989 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.989 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:38.989 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.989 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:38.989 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:38.989 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:38.989 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:38.989 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.990 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:38.990 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:38.990 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:38.990 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.990 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:38.990 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:38.990 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.990 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:38.990 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:38.990 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:38.990 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.990 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:38.990 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:38.990 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.990 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:38.990 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:38.990 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:38.990 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.990 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:38.990 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:38.990 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.990 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:38.990 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.990 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:38.990 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:38.990 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:38.991 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:38.991 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.991 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:38.991 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.991 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:38.991 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.991 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:38.991 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:38.991 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:38.991 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:38.991 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.991 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:38.991 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:38.991 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:38.992 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.992 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:38.988 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:38.992 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:38.992 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.992 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:38.992 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.993 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:38.993 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.993 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:38.993 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.994 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:38.994 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.994 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:38.994 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.994 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:38.994 GPIO: 1 interrupts in queue.
2016-05-12 21:08:38.994 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:38.994 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:38.994 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:43.994 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:43.995 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:43.995 GPIO: 1 interrupts in queue.
2016-05-12 21:08:43.995 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:43.995 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:43.995 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:43.996 GPIO: 1 interrupts in queue.
2016-05-12 21:08:43.996 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:43.996 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:43.996 GPIO: 1 interrupts in queue.
2016-05-12 21:08:43.996 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:43.996 GPIO: 1 interrupts in queue.
2016-05-12 21:08:43.996 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:43.996 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:43.996 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:43.996 GPIO: 1 interrupts in queue.
2016-05-12 21:08:43.996 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:43.995 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:43.996 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:43.998 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:43.999 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:44.001 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:44.001 GPIO: 1 interrupts in queue.
2016-05-12 21:08:44.001 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:44.001 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:44.001 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:44.001 GPIO: 1 interrupts in queue.
2016-05-12 21:08:44.001 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:44.002 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:44.002 GPIO: 1 interrupts in queue.
2016-05-12 21:08:44.002 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:44.002 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:44.002 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:44.002 GPIO: 1 interrupts in queue.
2016-05-12 21:08:44.002 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:44.002 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:44.002 GPIO: 1 interrupts in queue.
2016-05-12 21:08:44.002 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:44.002 GPIO: 1 interrupts in queue.
2016-05-12 21:08:44.002 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:44.002 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:44.002 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:44.002 GPIO: 1 interrupts in queue.
2016-05-12 21:08:44.002 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:44.001 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:44.002 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:44.004 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:44.005 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:44.006 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:44.008 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:44.009 (433Mhz) Lighting 1 (Unknown)
2016-05-12 21:08:44.011 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:44.011 GPIO: 1 interrupts in queue.
2016-05-12 21:08:44.012 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:44.012 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:44.012 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:44.012 GPIO: 1 interrupts in queue.
2016-05-12 21:08:44.012 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:44.012 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:44.012 GPIO: 1 interrupts in queue.
2016-05-12 21:08:44.012 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:44.012 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:44.012 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:44.012 GPIO: 1 interrupts in queue.
2016-05-12 21:08:44.012 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:44.012 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:44.012 GPIO: 1 interrupts in queue.
2016-05-12 21:08:44.012 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:44.012 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:44.012 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:44.012 GPIO: 1 interrupts in queue.
2016-05-12 21:08:44.012 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:44.013 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:44.013 GPIO: 1 interrupts in queue.
2016-05-12 21:08:44.013 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:44.013 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:44.013 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:44.013 GPIO: 1 interrupts in queue.
2016-05-12 21:08:44.013 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:44.013 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:44.013 GPIO: 1 interrupts in queue.
2016-05-12 21:08:44.013 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:44.013 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:44.013 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:44.013 GPIO: 1 interrupts in queue.
2016-05-12 21:08:44.013 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:44.013 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:44.013 GPIO: 1 interrupts in queue.
2016-05-12 21:08:44.014 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:44.014 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:44.014 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:44.014 GPIO: 1 interrupts in queue.
2016-05-12 21:08:44.014 GPIO: Done processing interrupt for GPIO 27.
2016-05-12 21:08:44.014 GPIO: Interrupt for GPIO 27 already queued. Ignoring...
2016-05-12 21:08:44.014 GPIO: 1 interrupts in queue.
2016-05-12 21:08:44.014 GPIO: Acknowledging interrupt for GPIO 27.
2016-05-12 21:08:44.014 GPIO: Processing interrupt for GPIO 27...
2016-05-12 21:08:44.014 GPIO: Queuing interrupt for GPIO 27.
2016-05-12 21:08:44.014 GPIO: 1 interrupts in queue.
2016-05-12 21:08:44.014 GPIO: Done processing interrupt for GPIO 27.
- Attachments
-
- snip_20160512204109.png (133.67 KiB) Viewed 6290 times
-
- Posts: 86
- Joined: Sunday 01 May 2016 0:34
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Location: NL
- Contact:
Re: Howto: Raspberry Pi GPIO 433MHz Remote Sockets
just realized what you are saying. So how do i get the RF Codes for my KAKU plugs to use codesend?deennoo wrote:I'm sorry to say that GPIO hardware on this case is not usefull...rfsniffer doesn't use gpio as a "switch".
Juste create a dummy hardware and place codesend typo or on and off that all.
With this "how to" you just open and close GPIO17, who doesn't need to move.
-
- Posts: 784
- Joined: Wednesday 10 December 2014 13:06
- Target OS: Linux
- Domoticz version: beta
- Location: Bordeaux France
- Contact:
Re: Howto: Raspberry Pi GPIO 433MHz Remote Sockets
Don't know if rfsniffer can get kaku code (i only got phénix plug, and rfsniffer was use for more than 1 1/2 year ago on my side)
Domoticz stable 3.5877 for real & Domoticz beta for test
Rfxtrxe / RFLink / Milight / Yeelight / Tasmota / MQTT / BLE / Zigate
http://domo-attitude.fr
Rfxtrxe / RFLink / Milight / Yeelight / Tasmota / MQTT / BLE / Zigate
http://domo-attitude.fr
-
- Posts: 8
- Joined: Thursday 31 March 2016 15:28
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Howto: Raspberry Pi GPIO 433MHz Remote Sockets
I am so close to getting this working but am stuck at the last hurdle. I have a Etekcity 5 outlet set, raspi B+, 433mhz receiver and transmitter and set it up with the instructions https://timleland.com/wireless-power-ou ... /#comments.
That works great. Installed domoticz and restored my database. Domoticz is running I can use 'codesend' to switch on/off the outlets at the command line.
Here's where I'm stuck.... as suggested in previous posts here I created a dummy switch, entered the 'codesend' commands in the on/off action fields.... nothing, doesn't work. I created scripts with the commands in, and tried calling the scripts from the on/off actions of the dummy switch... nothing. And yet I can enter the same line on the command line and it works.
** Update **
Solved the problem.... simple when you know how.... I was reading another post and saw that I needed 3 slashes after the script: command. Once I added the extra one before the path it worked fine. You learn something every day
That works great. Installed domoticz and restored my database. Domoticz is running I can use 'codesend' to switch on/off the outlets at the command line.
Here's where I'm stuck.... as suggested in previous posts here I created a dummy switch, entered the 'codesend' commands in the on/off action fields.... nothing, doesn't work. I created scripts with the commands in, and tried calling the scripts from the on/off actions of the dummy switch... nothing. And yet I can enter the same line on the command line and it works.
** Update **
Solved the problem.... simple when you know how.... I was reading another post and saw that I needed 3 slashes after the script: command. Once I added the extra one before the path it worked fine. You learn something every day

- sincze
- Posts: 1300
- Joined: Monday 02 June 2014 22:46
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2024.4
- Location: Netherlands / Breda Area
- Contact:
Re: Howto: Raspberry Pi GPIO 433MHz Remote Sockets



Can you show a screenshot of your settings now

Pass2php
LAN: RFLink, P1, OTGW, MySensors
USB: RFXCom, ZWave, Sonoff 3
MQTT: ZIgbee2MQTT,
ZWAVE: Zwave-JS-UI
WIFI: Mi-light, Tasmota, Xiaomi Shelly
Solar: Omnik, PVOutput
Video: Kodi, Harmony HUB, Chromecast
Sensors: You name it I got 1.
LAN: RFLink, P1, OTGW, MySensors
USB: RFXCom, ZWave, Sonoff 3
MQTT: ZIgbee2MQTT,
ZWAVE: Zwave-JS-UI
WIFI: Mi-light, Tasmota, Xiaomi Shelly
Solar: Omnik, PVOutput
Video: Kodi, Harmony HUB, Chromecast
Sensors: You name it I got 1.
-
- Posts: 140
- Joined: Thursday 22 October 2015 21:14
- Target OS: Linux
- Domoticz version: 4.11539
- Contact:
Re: Howto: Raspberry Pi GPIO 433MHz Remote Sockets
I have also got this working.
I did not create a dummy but followed mostly the first posts Wiki.
I first had some trouble installing the ninja stuff. I had to change a line in the Makefile for the compilation to work
(CXXFLAGS=-DRPI change to --> CXXFLAGS=-DRPI -pthread)
After changing one warning remains but al works fine.
After using the RFSniffer I had some trouble with the RX. but that was related to a faulty wire..
Got the codes and could turn on/off the lights from the cli... (yah!)
Then of course in Domoticz tried with script:// but nothing happend..
the 3 slashes tip was also a very needed one!
Many thanks for the first poster!
Must add that I now see that domoticz is crashing... Can't see why yet.. but I see one process of domoticz taking up very high CPU..
Webapp is not responding any more.
edit #2: Is it normal to have like 16 processes for the domoticz daeomon?
I did not create a dummy but followed mostly the first posts Wiki.
I first had some trouble installing the ninja stuff. I had to change a line in the Makefile for the compilation to work
(CXXFLAGS=-DRPI change to --> CXXFLAGS=-DRPI -pthread)
After changing one warning remains but al works fine.
After using the RFSniffer I had some trouble with the RX. but that was related to a faulty wire..
Got the codes and could turn on/off the lights from the cli... (yah!)
Then of course in Domoticz tried with script:// but nothing happend..
the 3 slashes tip was also a very needed one!
Many thanks for the first poster!
Must add that I now see that domoticz is crashing... Can't see why yet.. but I see one process of domoticz taking up very high CPU..
Webapp is not responding any more.
edit #2: Is it normal to have like 16 processes for the domoticz daeomon?
Hardware: Raspberry Pi 3, OTGW, 433MHz Superheterodyne 3310 RF Link
Software: Ubuntu 16.04, Domoticz v3.5468, WiringPi, rc-switch
Software: Ubuntu 16.04, Domoticz v3.5468, WiringPi, rc-switch
-
- Posts: 4
- Joined: Monday 26 September 2016 9:54
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Howto: Raspberry Pi GPIO 433MHz Remote Sockets
Hi guys!
Many thanks for the manual, it worked with my simple 433Mhz LED strip but I am not able to get it working with LightwaveRF mains socket. It worked a while ago but then my SD card failed (and of course no backup), so I had to reinstall everything. Unfortunately, the person who installed it is too busy to help me with it, so trying to DIY. I remember that the socket was put into the programming mode (both LED flashing) and then some random code was send to it from Raspberry PI.
Any ideas how to do it?
Many thanks for the manual, it worked with my simple 433Mhz LED strip but I am not able to get it working with LightwaveRF mains socket. It worked a while ago but then my SD card failed (and of course no backup), so I had to reinstall everything. Unfortunately, the person who installed it is too busy to help me with it, so trying to DIY. I remember that the socket was put into the programming mode (both LED flashing) and then some random code was send to it from Raspberry PI.
Any ideas how to do it?
-
- Posts: 1
- Joined: Friday 30 September 2016 14:37
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Howto: Raspberry Pi GPIO 433MHz Remote Sockets
Great Project - got it up and running in less than an hour. The only thing remaining is the rights using sendcommand and I would guess S well that would prevent domoticz from sending the script. I changed the binding to PI with the chown command, but this command itself is calling wiringpisetup and that needs root. If I would use chown for this, could that make a problem in the future - so what is the right thing to do?Nobody else is having trouble with that issue? Thanks for helping out a not so Unix familiar guy!
-
- Posts: 4
- Joined: Monday 26 September 2016 9:54
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Howto: Raspberry Pi GPIO 433MHz Remote Sockets
anyone please??automationguy wrote:Hi guys!
Many thanks for the manual, it worked with my simple 433Mhz LED strip but I am not able to get it working with LightwaveRF mains socket. It worked a while ago but then my SD card failed (and of course no backup), so I had to reinstall everything. Unfortunately, the person who installed it is too busy to help me with it, so trying to DIY. I remember that the socket was put into the programming mode (both LED flashing) and then some random code was send to it from Raspberry PI.
Any ideas how to do it?
-
- Posts: 4
- Joined: Monday 26 September 2016 9:54
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Howto: Raspberry Pi GPIO 433MHz Remote Sockets
Thanks a lot everyone, the issue has been resolved.
-
- Posts: 3
- Joined: Friday 17 March 2017 22:31
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Howto: Raspberry Pi GPIO 433MHz Remote Sockets
Thanks for your information, i found out that if you have the 433utils working, you can just create a dummy (hardware type), create switches and then just use the script. Then there is no need for hardware settings in Domoticz. When you create a switch you can just leave it at x10, the settings doesn't matter.
I created a dutch tutorial on this: https://shoarma.000webhostapp.com/index ... pberry-pi/ (DUTCH)
I created a dutch tutorial on this: https://shoarma.000webhostapp.com/index ... pberry-pi/ (DUTCH)
Who is online
Users browsing this forum: No registered users and 1 guest