I've been working on getting a Home automation project going for a while, using a Rasp pi 1b (26 pin header). This is a well trodden path by others, as it is a project to control status remote sockets: https://securipi.co.uk/remote-433-receivers.pdf
I have been trying for around a couple of weeks to get the transmission side of the project working-to no avail. I have successfully sniffed the unique code, gap and t0/t1 values sent by the remote which came with the sockets, using both Python rpi-rf and pigpio. In terms of hardware I have a separate heterodyne receiver and transmitter and also the cheaper ones which tend to have a shorter range.
Others resources and successful projects I've used to verify what I'm doing are:
I'm using a pigpio python script to replay the codes, but have been unsuccessful in activating a socket. I've also tried transmission via the python rpi-rf scripts. Also to no avail .
Has anyone a suggestion of how I can verify if the transmitter is working, using the equipment I have mentioned? I attempted to use pilight-debug, but could not get it to build - segmentation fault on rasp pi 2.
update 1st Nov I've now had partial success, following soldering a antenna onto the heterodyne transmitter I have. Here are the codes I sniffed from the socket remote, which I am unable to retrieve using pigpio at present. So I used the Python rpi-rf modules and the scripts provided to received and send data.
The codes sniffed from the socket remote are: - 2019-11-01 22:17:52 - [INFO] rpi-rf_receive: 3268719 [pulselength 304, protocol 1]
And on replay from the heterodyne transmitter the resulting receive from the above was: 2019-11-01 22:43:34 - [INFO] rpi-rf_receive: 3268719 [pulselength 136, protocol 3] 2019-11-01 22:43:34 - [INFO] rpi-rf_receive: 3268719 [pulselength 135, protocol 3] 2019-11-01 22:43:34 - [INFO] rpi-rf_receive: 3268719 [pulselength 135, protocol 3]
The socket did not switch on from the above replay.
I disconnected the receiver connected to the Pi, before attempting the transmission from the Pi transmitter. Probably also worth mentioning that the receiver and transmitter are connected to different rasp pi's.
Any suggestions as to why the socket will not activate, given what should be the same waveform generated by the Pi transmitter? Cheers.hikerrobot