homeduino doesn't detect first/single transfer

---

Hi!

I have built a homeduino with an Arduino Pro Mini 5V, a 433 transmitter and a 433 receiver. I am able to send and receive RF commands, but reception is not fully working. It doesn’t detect the first transmission. I am able to receive the second transmission and onward from a remote that sends repeatedly. I am not able to receive the single transmission from my Prologue temperature sensor. What could be wrong with my setup?

which rf hardware do you use?
check here
https://forum.pimatic.org/topic/487/hardware-tip-433-mhz-receiver-for-pimatic

The receiver is a CDR03A. There is no obvious problem with range, as it can receive transmissions from the remote at a longer range (10m) than the power outlets that was sold with the remote can (7m).

I also tested with a A2ABTAE-D2 receiver. The only difference is that it receives additional transmissions from a to me unknown source. Still no reception from Prologue or the initial transmission from the remote though.

Is anyone skilled enough to be able to take a raw data dump and explain why the initial transmission is passing undetected? How should the raw data be interpreted, what kind of signal does it represent?

I have implemented an alternative to the ASK decoder in homeduino. It works much better with my equipment, but I don’t have a lot of equipment to test with. I would appreciate if others could test it as well and report back with the results. You can find it at http://formallanguage.blogspot.se/2017/06/ask-baseband-decoder.html

I also plan to write a patch for homeduino to be able to use it with Pimatic in the future.

Regarding the Prologue Model TW007 temperature sensor I have, it seems to be the requirement by homeduino that signal intervals are doubling that prevents it from being recognized, i.e. [pt*1, pt*2, pt*4, pt*8, …]. It seems to use any multiple of the period time, i.e. [pt*1, pt*2, pt*3, pt*4, …].

572 1144 1716 2860 4004 5148 10296 42244 0101010101010101010100000000000000000002000000030000020400020300040005000002000002000000030600020007

@TheOtherMarcus said in homeduino doesn't detect first/single transfer:

I also plan to write a patch for homeduino to be able to use it with Pimatic in the future.

This would be great! See also https://github.com/pimatic/homeduino

I have integrated the decoder in homeduino and I am able to use it together with pimatic. It seems to work fine. It is available at https://github.com/TheOtherMarcus/homeduino

I am questioning the practice to include the trailing sync pulse in the message. The final message in a sequence will not have a deterministic sync pulse length and it will typically be much longer than the sync pulses between messages. This means that the rfcontroljs protocol specification will fail to match the message. The following message sequence from a Nexa remote illustrates the problem.

RF receive 308 2464 1232 10164 0 0 0 0 010002020000020002020000020002000200020002020002000200000200020002000202000200020000020200000200020200000200020002000200020002000203
RF receive 296 2368 1184 10360 0 0 0 0 010002020000020002020000020002000200020002020002000200000200020002000202000200020000020200000200020200000200020002000200020002000203
RF receive 284 2556 1136 10224 0 0 0 0 010002020000020002020000020002000200020002020002000200000200020002000202000200020000020200000200020200000200020002000200020002000203
RF receive 284 2556 1144 60844 0 0 0 0 010002020000020002020000020002000200020002020002000200000200020002000202000200020000020200000200020200000200020002000200020002000203

For devices that only transmit once, this is a fatal issue.

Finally, I have not been able to locate the source for the decoder that uses Raspberry Pi GPIO directly. Can someone help me out here?

How do I use this implementation with pimatic?

@temp said in homeduino doesn't detect first/single transfer:

How do I use this implementation with pimatic?

You need to replace the software in your Arduino with the modified version. The installation procedure is identical to pimatic/homeduino. Start with a clone of the repo.

git clone --recursive https://github.com/TheOtherMarcus/homeduino.git

Then follow the installation instruction for pimatic/homeduino, https://github.com/pimatic/homeduino

@TheOtherMarcus Thanks

@TheOtherMarcus Thanks. Looks promising. We need to get more users testing to your version

Hi!

I just recently stumbled over this discussion - I also have problems with signals getting lost - and I tried it out.
At first it was not working at all. Receiving, sending, all functionality was gone. AND: the moment I started receiving also the normal remote would not work for the RF sockets. I though: “What the f**** is going on?” The idea that I just built an RF jamming devices came to my mind… in fact the problem was:
I used D13 on the arduino for my RF sender. And the updated homeduino by is using D13 for an activity LED (hardcoded).
After I fixed this, the device works just fine for my RF switches.
I think I still have a problem with my temperature sensors. Both from Pearl. One is using the weather1 protocol, the other weather18.
No temperature is detected and even when I trigger the sensor to send RF messages there is no input in pimatic. I am using “discover devices” to detect.
Are there any known topics for these kind of devices? Any hints how to debug?
edit
I did some printf debugging. The code never enters the “if(RFControl::hasData())” block in rfcontrol_command.h
edit

Cheers,
Stefan

P.S. and of course a big thank you to @TheOtherMarcus !