Nodes stop updating Motion on the Gateway after a while [bad cable...]

[Magnus]

Hi

I'm using the pre build v5 image with two motion nodes.
The problem is that after a while the status of the nodes on the webpage is not updated when the nodes are triggerd and no information i logged, after a reboot of the Raspberry PI everything works for some time before the same thing happens again.

I use the v5 of the prebuilt image with no modifications, an Motino-USB is connected to the Raspberry PI running the Gateway sketch unmodified.

any ideas on how I could troubleshoot this would be appreciated.

[Felix]

Is there any way you can verify the end nodes keep sending data? It does sound like you are never touching the end nodes and it's something on the gateway that stops updating, but I want to verify that.
Next step would be to see what the gateway MoteinoUSB is doing, if it's still receiving the data and passing it through the serial to the Pi.
Also I need to ask if you are refreshing the page but again just verifying, in case there's some kind of socket disconnect - although the page should detect that and say that socket was disconnected (sorry this is almost a stupid question).
Another way would be to have an end node send data more continuously (a 3rd node perhaps or program one of the Motes with a more periodic fake message and see if that keeps updating or it stops as well).
Also what is the timespan after which it stops updating?
Are the PIRs in the MotionMotes modified to support lower voltage thresholds (as shown in the guide)?
Not sure what else, let's try these things and see what you find.

[Magnus]

Hi

I can't explain this but it seems that the USB cable used between the Raspberry PI and the MoteinoUSB is somehow causing this behavior, changing it to another seems to cure the problem.
Very strange since that same cable works when running the Moteino gateway in the Arduino serial monitor.

/Magnus

[Felix]

Unshielded cable?
Changing the cable solves the problem?
Case solved?

[Magnus]

Hi

The setup has been running non stop for several days, the cable was the problem.
Case closed.

/Magnus