Receiver doesn't seem to work with espimaticrf

Gleno0h

@lschip if you want, i can look into your pi this weekend, saturday evening probably, to see if i can fix it. Otherwise you are better of installing raspbian instead of xbian and try it then or with another esp. If you want me to look, PM me your putty info.

lschip

Hi Gleno0h,

Thanks for your generous offer.

But as I see it, I am trying to solve a problem nobody else has due to using different equipment.

So I am going to install Raspian instead of Xbian and just bought a v2 homeduino instead of a v3 clone.

I keep the forum informed if this solves the problem.

Thanks for now.

Gleno0h

@lschip alrighty then. Looking forward to hear that it is solved.

lschip

Pfff…
Installed Raspian and Pimatic from scratch.
Bought a Homeduino v2 and programmed this one.
Its receiving rf signals:
0_1524321013118_6c406319-cee5-4991-b01c-5bd421ee1ac2-image.png
Connected the new homeduno to the Raspberry Pi.
Same problem:
0_1524322478221_094f20d8-7034-4c14-8140-e4a75bb31a47-image.png

lsmod shows:
0_1524322366465_f4f04295-4738-4a1d-bdca-643ee9a6e4b2-image.png

cat /dev/ttyUSB0 shows:
0_1524321551711_fef78061-21e2-435e-8760-e6b42d5eac81-image.png
(the working one shows ACK 0)

ls /lib/modules/$(uname -r)/kernel/drivers/usb/serial says:
0_1524321955289_43ff18ae-dc0d-4adb-b0bc-60f8ace9f804-image.png

I don’t know anymore how to solve this…

lschip

New info, I see in the Pimatic log the following:

17:30:13.539 [pimatic-mobile-frontend] info: packing static assets finished
17:30:13.551 [pimatic-mobile-frontend] info: rendering html
17:30:18.145 [pimatic-homeduino] debug: data: "PING"
17:30:18.150 [pimatic-homeduino] debug: data: "RF receive 488 968 1944 4008 0 0 0 0 01020102020201020101010101010101020202010102020202020202010101010101010103"
17:30:18.152 [pimatic-homeduino] debug: data: "RF receive 488 968 1940 4004 0 0 0 0 01020102020201020101010101010101020202010102020202020202010101010101010103"
17:30:18.155 [pimatic-homeduino] debug: data: "RF receive 488 988 1944 132 4004 0 0 0 01020102020201020131010101010101020202010102020202020202010101010101010104"
17:30:18.220 [pimatic] info: rule pimatic-start: pushbullet message sent successfully
Unhandled rejection Error: Command failed: /bin/sh -c  expr `ls /mnt/Ipcameras | wc | awk '{print $1}'`

17:30:18.262 [pimatic-homeduino] debug: data: "ready"
17:30:18.947 [pimatic-homeduino] info: Connected to homeduino device.
17:30:26.074 [pimatic-homeduino] debug: data: "ready"
17:30:26.093 [pimatic-mobile-frontend] info: rendering html finished
17:30:26.194 [pimatic] info: Listening for HTTP-request on port 80...
17:30:26.715 [pimatic-homeduino] debug: data: "ready"
17:30:27.123 [pimatic-homeduino] debug: data: "ready"
17:30:27.582 [pimatic-homeduino] debug: data: "ACK"
Unhandled rejection Error: Command failed: /bin/sh -c  expr `ls /mnt/Ipcameras | wc | awk '{print $1}'`

17:30:27.680 [pimatic-homeduino] debug: Receiving on pin 0
17:30:27.729 [pimatic-homeduino] debug: data: "ACK"
17:30:27.839 [pimatic-homeduino] debug: data: "ACK"
17:30:27.907 [pimatic-homeduino] debug: data: "ACK"
17:30:27.914 [pimatic-homeduino] debug: data: "ACK"
17:30:27.929 [pimatic-homeduino] debug: data: "ACK 1023"
17:30:28.095 [pimatic-homeduino] debug: data: "ACK 1"
17:30:28.111 [pimatic-homeduino] debug: data: "ACK 1"
17:30:28.126 [pimatic-homeduino] debug: data: "ACK 1"
17:30:29.871 [pimatic-homeduino] debug: data: "ACK 1"
17:30:30.927 [pimatic-homeduino] debug: data: "ACK 1"

It seems receiving something at 17:30:18:150 and later.
Then at 17:30:27:729 I see a few "ACK"s but then it goes wrong with "ACK 1"s.
Isn’t that strange?
Is there something else that interferes? What is “ACK 1023”, is this also an error message?

Gleno0h

@lschip funny that it displays debug data and receiving rf signals before even connecting to homeduino…

Did you try a couple of other usb cables, maybe also another port?

I believe you shouldnt receive so many ack messages, it should display “ping” messages.

This is normal behaviour;

05:11:14.219 [pimatic-homeduino] debug: data: "80104866{"buckets":{"0":"260"$unknown message received: 80104866{"buckets":{"0":"260","1":"1300","2":"2700$05:11:14.235 [pimatic-homeduino] debug: data: "UDP Packet 0 done"            unknown message received: UDP Packet 0 done
05:11:14.258 [pimatic-homeduino] debug: data: "UDP Packet 1 done"
unknown message received: UDP Packet 1 done
05:11:14.275 [pimatic-homeduino] debug: data: "UDP Packet 2 done"
unknown message received: UDP Packet 2 done
05:11:14.416 [pimatic-homeduino] debug: data: "UDP Packet 3 done"
unknown message received: UDP Packet 3 done
05:16:32.927 [pimatic-homeduino] debug: data: "PING"
05:21:52.941 [pimatic-homeduino] debug: data: "PING"
05:27:12.955 [pimatic-homeduino] debug: data: "PING"
05:32:12.987 [pimatic-homeduino] debug: data: "PING"
05:37:33.008 [pimatic-homeduino] debug: data: "PING"
05:42:53.026 [pimatic-homeduino] debug: data: "PING"
05:48:13.043 [pimatic-homeduino] debug: data: "PING"
05:53:13.072 [pimatic-homeduino] debug: data: "PING"
05:58:13.112 [pimatic-homeduino] debug: data: "PING"
06:03:33.135 [pimatic-homeduino] debug: data: "PING"
06:08:53.150 [pimatic-homeduino] debug: data: "PING"
06:14:13.174 [pimatic-homeduino] debug: data: "PING"
06:19:33.187 [pimatic-homeduino] debug: data: "PING"
06:24:53.199 [pimatic-homeduino] debug: data: "PING"
06:30:13.219 [pimatic-homeduino] debug: data: "PING"

lschip

I already tried another cable. But the current cable I also used for programming the Homeduino.
I’ll try another port but I don’t think that helps.

The original homeduino (the working one without esp) doesn’t show ping but “ACK 0” all the time, like the new one shows “ACK 1”…
0_1524340623887_fd82e6fe-9eb7-49bf-9b55-4deaaf2ac301-image.png

lschip

More info:
The description of the homeduino is:

Het NodeMCU board kan op zichzelf werken met Lua scripts. Dit board is een versie van het nodemcu board met een CP2102 usb naar serieel converter i.p.v. de CH340 chip en verbeterde ESP-12E module. (i.p.v. ESP-12)

(sorry, its dutch)

Is CP2102 logical or do I need another driver or that?

Gleno0h

@lschip well, this is a quote from the developer, koffienl, over at tweakblogs, telling everyone that the cp2102 should always work;
“Gewoon een NodeMCU met CP2102 chipset kiezen, zit je altijd goed”

You also got a message telling you it is ready 4 times. This should be only once.

This is normal;

06:45:31.419 [pimatic-homeduino] data: "PING"
06:45:31.575 [pimatic-homeduino] data: "ready"
06:45:33.280 [pimatic-homeduino] Connected to homeduino device.
06:46:03.488 [pimatic-mobile-frontend] rendering html finished
06:46:03.695 [pimatic] Listening for HTTP-request on port xxxxx...
06:46:03.947 [pimatic-homeduino] data: "ACK"
06:46:04.658 [pimatic-homeduino] Receiving on pin 0

Also lsmod displays the right information, it is not a driver issue, also because dev/ttyUSB0 outputs information.

/dev/ttyUSB0 is just a symlink to that connected usb device, so the drivers are correct because you get data.

You are using a original raspberry pi, right?
How does it respond on sending rf?

Output of uname -r please.
Maybe we need to downgrade your kernel.

My offer still stands to help you through putty!

lschip

Hi Gleno0H,

The NodeMcu I just bought has a CP2102 chipset so that should be ok now.
I’ll try sending later and let ypu know.
But in the serial monitor of the NodeMcu I see that it is receiving RF signals when I open a door.

I am using an original Raspberry version 3.

uname -r shows:
4.14.34-v7+

Your help through putty is welcome but I have to find a right moment for that. I’ll come back to that.
Thanks!

Gleno0h

@lschip could you flash the development version and give that a run, see if that works for you;

https://github.com/koffienl/ESPimaticRF/tree/development?files=1

Also confirm that the nodemcu is connected with this command;
ls /dev/serial/by-id

lschip

Is this version 0.0.3?
That the version I have installed…

0_1524386280035_e7e7b297-9dc9-4043-93cd-32701b6e9510-image.png

I saw there is a 0.0.6 version: https://github.com/koffienl/ESPimaticRF/tree/development.
Do you men that one?

Gleno0h

@lschip 0.0.6;
https://github.com/koffienl/ESPimaticRF/blob/development/changelog.txt

Gleno0h

@lschip yes, its a development version. There was a bug with sending data to pimatic, maybe you somehow used that version because to be very honest, it is a very strange problem. Seeing i am the only posting, i think no one else has an clue either. Or they are all enjoying the weather and a beer

lschip

Installed the 0.0.6 version on the Homeduino.

And, its working!.

Still ACK 1 all the time:

18:51:35.581 [pimatic-homeduino] debug: contact2:  { id: 295807, contact: false }
18:51:35.587 [pimatic-homeduino] debug: contact3:  { id: 295807, contact: true }
18:51:35.590 [pimatic-homeduino] debug: contact4:  { id: 752768, contact: true, lowBattery: false }
18:51:35.605 [pimatic-homeduino] debug: led1:  { id: 47048, command: 'code:00001110' }
18:51:35.610 [pimatic-homeduino] debug: led2:  { id: 47048, command: 'code:00001110' }
18:51:35.613 [pimatic-homeduino] debug: led3:  { id: 47048, command: 'white' }
18:51:35.616 [pimatic-homeduino] debug: led4:  { id: 47048, command: 'code:00001110' }
18:51:35.657 [pimatic] debug: Suppressing rule css-achterdeur-closed execute because it was executed recently.
18:51:35.662 [pimatic-homeduino] debug: data: "RF receive 1368 460 13984 0 01100101100101010101101001101010101010100101011012"
Unknown RF response "receive 1368 460 13984 0 01100101100101010101101001101010101010100101011012"
18:51:35.669 [pimatic-homeduino] debug: data: "RF signal detected, send to Pimatic"
Unknown RF response "signal detected, send to Pimatic"
18:51:35.672 [pimatic-homeduino] debug: data: "connection failed"
unknown message received: connection failed
18:51:35.846 [pimatic-homeduino] debug: data: "RF receive 1364 464 14036 0 01100101100101010101101001101010101010100101011012"
Unknown RF response "receive 1364 464 14036 0 01100101100101010101101001101010101010100101011012"
18:51:35.853 [pimatic-homeduino] debug: data: "RF signal detected, send to Pimatic"
Unknown RF response "signal detected, send to Pimatic"
18:51:35.855 [pimatic-homeduino] debug: data: "connection failed"
unknown message received: connection failed
18:51:35.960 [pimatic-homeduino] debug: data: "ACK 1"
18:51:36.079 [pimatic-homeduino] debug: data: "RF receive 1364 460 14040 0 01100101100101010101101001101010101010100101011012"
Unknown RF response "receive 1364 460 14040 0 01100101100101010101101001101010101010100101011012"
18:51:36.084 [pimatic-homeduino] debug: data: "RF signal detected, send to Pimatic"
Unknown RF response "signal detected, send to Pimatic"
18:51:36.086 [pimatic-homeduino] debug: data: "connection failed"
unknown message received: connection failed
18:51:36.979 [pimatic-homeduino] debug: data: "ACK 1"
18:51:38.298 [pimatic-homeduino] debug: data: "ACK 1"
18:51:39.351 [pimatic-homeduino] debug: data: "ACK 1"
18:51:40.374 [pimatic-homeduino] debug: data: "ACK 1"
18:51:41.395 [pimatic-homeduino] debug: data: "ACK 1"
18:51:42.414 [pimatic-homeduino] debug: data: "ACK 1"
18:51:43.725 [pimatic-homeduino] debug: data: "ACK 1"
18:51:44.751 [pimatic-homeduino] debug: data: "ACK 1"
18:51:45.771 [pimatic-homeduino] debug: data: "ACK 1"

lschip

mmm…
I had a lightsensor on the original homeduino and not on the NodeMcu.
So I deleted the lightsensor device and the "ACK 1"s are vanished.

Could the be the problem in the first place?

Realy happy it working now.

Special thanks to Gleno0H for constantly pointing out possibilities and supporting me!!!.

Gleno0h

@lschip no problem at all. Could have been the problem indeed. Like i said, it is a weird error so it could have been anything. My espimaticrf stops working if it is too close to another cable so

Anyway, have fun