Making sure WebIOPi is running all the time

[Funkanzan]

If you follow the tutorial steps over at Eric Ptak's WebIOPi page, you might have run WebIOPi in interactive mode rather than daemon mode. While that's kinda cool because it shows you commands as they are received, if you exit out of this mode, then WebIOPi isn't running any more and you won't be able to connect to it.

The following instructions are from: https://code.google.com/p/webiopi/wiki/INSTALL

---

Running WebIOPi (Daemon)
You can also start/stop the background service, the configuration will be loaded from /etc/webiopi/config.

$ sudo /etc/init.d/webiopi start
$ sudo /etc/init.d/webiopi stop

Auto start at boot - To setup your system to start webiopi at boot :

$ sudo update-rc.d webiopi defaults

To remove webiopi start from boot :

$ sudo update-rc.d webiopi remove

---

To confirm that Weaved and WebIOPi are both running, use this command:

pi@raspberrypi ~ $ ps aux | grep -i web

This output line confirms WebIOPi is running:

root 2275 0.1 2.6 32360 11760 ? Sl Nov14 16:01 /usr/bin/python3 -m webiopi -l /var/log/webiopi -c /etc/webiopi/config

This output line confirms the Weaved Service is running:

root 12739 0.1 0.2 2292 920 ? S Nov24 0:31 /usr/bin/weavedConnectd -f /etc/weaved/services/Weavedwebiopi8000.conf -d /var/run/Weavedwebiopi8000.pid

Any matches beyond that can be ignored.

pi 13629 0.0 0.1 3552 868 pts/1 S+ 02:04 0:00 grep --color=auto -i web

[Funkanzan]

[JimiFx]

Hi Weaved:

this is what I got from the command you suggested:
pi@raspberrypi ~ $ ps aux | grep -i web
root 2112 0.1 1.5 32372 13976 ? Sl Aug06 1:30 /usr/bin/python3 -m webiopi -l /var/log/webiopi -c /etc/webiopi/config
root 2221 0.0 0.1 2336 1688 ? S Aug06 0:59 /usr/bin/weavedConnectd -f /etc/weaved/services/Weavedwebiopi8000.conf -d /var/run/Weavedwebiopi8000.pid
pi 4496 0.0 0.1 2444 1596 pts/0 S+ 16:22 0:00 grep --color=auto -i web

Everything look ok?

[JimiFx]

Is this a Pi2 ? Or RaspberryPi B/B+ ?

[noelkuck]

RasPi2 B+, I think. I can check.

[noelkuck]

Not a B+. I would guess it is a Pi2. Not a B or B+. I am trying to understand why I am not able to establish connection over a cellular network. WiFi on my LAN is good. And yes, I am using the iPhone Weaved app. Thanks.

[Funkanzan]

Hi Noel,

Maybe we can remove WebIOPi from the equation temporarily.

You can temporarily install another web server on port 80 for testing. It will not interfere in anyway with WebIOPi.

I recommend lighttpd for testing.

Run:

sudo apt-get install lighttpd

After it finishes, the lighttpd web server should be running, listening on port 80.

You can enter your Pi's IP address into the URL bar of a browser on the same LAN and it should show you the default placeholder web page from lighttpd.

Assuming that works, then run the Weaved installer and install a Weaved service for http on port 80.

Next, connect your phone to cellular, disconnect it from Wi-Fi, start the Weaved app and connect to the lighttpd service. It should open up the same default page. This would indicate that Weaved is working for http connections. If not, we'll have to dig into it further because it really should work!

To remove lighttpd after testing, you should run:

sudo apt-get remove lighttpd

although in general it does not cause any harm to leave it there.

[JimiFx]

Hi Noel,

I'm sure WebIOPi had some issues with running on the Pi 2 when Pi 2 first came out but I don't know the details. Please see here.
http://trouch.com/2015/02/10/webiopi-0-7-1-with-weaved-iot-kit/ where it says "WebIOPi currently does not support Raspberry Pi 2 yet, but some good things are coming. Stay tuned for updates."

Also see here ... https://groups.google.com/forum/#!topic/webiopi/RGtrRfFJMKY there are some proposed patches here by other WebIOPi users to enable WebIOPi on Pi2.

[Funkanzan]

Noel,

Can I ask you how your LAN is connected to the internet? Some people have experienced problems with Xfinity when the security settings were set to maximum.

Thx

Gary

[noelkuck]

Thanks the the feedback. I had seen the patches as well as V0.7.1 of WebIOPi which was supposed to address the compatibility issues. Neither have provided any fix, at least for me. When I run weavedConnectd -n I get:
WeavedConnectd built Feb 26 2015 at 10:53:39 Now Starting Up
Version 2.11 - (c)2015 Weaved, Inc. All Rights Reserved
Built with UPNP NATPMP ALIGN BCASTER MALLOC_POOL LINUX RESOLVE BIGBUF pool=262144
Weaved Development Kit Version based on Rasberry Pi Version
alloc pool

Running Weaved Network Diagnostics

Checking if DNS works ... .[OK]
Checking TCP connectivity to weaved.com... [OK]
Checking UDP connectivity to weaved.com...
Send to 174.36.235.146:5959 []
Send to 174.36.235.146:5959 [] [no response rc=0] [FAIL]
Checking if UPNP Router is found ... [NOT FOUND -1]
Checking if NAT-PMP Router is found...[NOT FOUND]

UDP connections to the internet are not working.
Possible remedies to this problem include :
1) UDP is blocked, Weaved needs UDP connectivity to work. Call your network provider.
2) UDP is firwealled, check your firewall configuration.
3) It is possible that your location only allows TCP connections via a proxy, Weaved will not currently work in these cases.\nnThis router doesn't remap new connections to new ports, this is optimal.
Static Pool Free
Endian : Little
SHA1 test
SHA1 calculated is D29B143379C5F1E62CB89CE0B45246EE5CC4D3DA
Should Be D29B143379C5F1E62CB89CE0B45246EE5CC4D3DA
RC4 test
RC4 Calulated is 9A03817B144F1610AB94FDA75BD8
Should Be 9A03817B144F1610AB94FDA75BD8
XXTEA test
XXTEA Calulated is 5164FC5FEA483B7158883A98277C2CCE
Should Be 5164FC5FEA483B7158883A98277C2CCE

[Funkanzan]

What do you get when you run

weavedConnectd -n

?

[Funkanzan]

Here's your problem:

UDP connections to the internet are not working.
Possible remedies to this problem include :
1) UDP is blocked, Weaved needs UDP connectivity to work. Call your network provider.
2) UDP is firwealled, check your firewall configuration.
3) It is possible that your location only allows TCP connections via a proxy, Weaved will not currently work in these cases.

Any idea why UDP is blocked at your location?