Mod

Nice work @Kurtsejr, thanks for reporting back

Nice work on the internet connectivity @Kurtsejr

It is an issue on some (newer?) linux versions. It has been fixed in the development version of MySensors. You can switch to the development version, or add the fix yourself.

See https://github.com/mysensors/MySensors/issues/1431 and https://github.com/mysensors/MySensors/pull/1446/files

Sorry for the inconvenience.

TRSx80 created this issue in mysensors/MySensors

closed Remove stropts.h? #1431

mfalkvidd created this issue in mysensors/MySensors

closed Rpi gw: Remove stropts.h include #1446

@Kurtsejr said in MySensors GW on rpi3:

How do I remove if more that one instance is started? - I will try to google it. Perhaps it's easier to start from beginning again

sudo systemctl stop mysgw.service will stop the gateway service if it is currently running. It will start automatically again after reboot (unless disabled).

sudo systemctl disable mysgw.service will disable autostart, but will keep the service running if it has already been started.

https://www.linuxtrainingacademy.com/systemd-cheat-sheet/ can be a good place to start

@Kurtsejr said in MySensors GW on rpi3:

Has something changed? or is it github that does not response?

The Raspberry Pi probably doesn't have the right settings for connecting to Internet. What happens if you run ping google.com for example? You should get something like this:

ping google.com
PING google.com (142.250.179.142) 56(84) bytes of data.
64 bytes from ams17s10-in-f14.1e100.net (142.250.179.142): icmp_seq=1 ttl=58 time=33.3 ms
64 bytes from ams17s10-in-f14.1e100.net (142.250.179.142): icmp_seq=2 ttl=58 time=33.4 ms

If you don't get any replies, the raspberry pi doesn't have a working internet connection.

@Kurtsejr I tested the gateway on a spare raspberry pi and it does indeed print lots of ERROR accept: Bad file descriptor when more than one instance of the gateway is started. The solution is easy: don't start two instances at the same time.

The reason is actually printed in the log: ERROR bind: Address already in use but is easy to miss due to the many ERROR accept: Bad file descriptor

INFO  Starting gateway...
INFO  Protocol version - 2.4.0-alpha
DEBUG MCO:BGN:INIT GW,CP=R-NGL---,FQ=NA,REL=0,VER=2.4.0-alpha
ERROR bind: Address already in use
ERROR Failed to bind!
DEBUG MCO:BGN:STP
DEBUG MCO:REG:NOT NEEDED
DEBUG MCO:BGN:INIT OK,TSP=NA
ERROR accept: Bad file descriptor
ERROR accept: Bad file descriptor
ERROR accept: Bad file descriptor
ERROR accept: Bad file descriptor

To check if the gateway has started automatically, run sudo systemctl enable mysgw.service

@Kurtsejr yes the gateway will start automatically at each boot, unless automatic start is disabled.

@Kurtsejr did you reboot befor running sudo ./bin/mysgw?
If that’s the case my guess is that the gateway was already started automatically at boot. When you tried to start another instance, the tcp port was already in use.

@Kurtsejr what configure command did you use?
Were there any warnings or errors during make?
What image are you using?

https://github.com/mysensors/MySensors/blob/253109d3ff00ec524c5d1e1dfcd8e197c96e54c2/core/MyEepromAddresses.h might be useful