Hello every one,
I have a raspberry pi B rev2 and a 8 releey board. I marked "use gpio" option and i receive this error:

root@raspberrypi:/home/pi/SIP# python sip.py
Traceback (most recent call last):
  File "sip.py", line 24, in <module>
    import gv
  File "/home/pi/SIP/gv.py", line 103, in <module>
    report_error(u"pigpio not found. Using RPi.GPIO", e)
NameError: name 'report_error' is not defined


Can someone help me to setup the gpio pins?

At this point the program does not start due to this error...


Sorry for my bad english
Thank

SIP revision 4.1 has been pushed to GitHub.
This rev includes improved responsive behavior on mobile devices and all paths are relative.

I installed and played with SIP for a while (I like it) but now I cannot get it to run, with this error (full terminal text below):

socket.error: No socket could be created -- (('::192.168.1.15', 8666, 0, 0): [Errno 99] Cannot assign requested address)

As you can see I changed the port (tried several). Also tried stopping the service and status with systemctl:

pi@192.168.1.15:~/SIP$ sudo service sip stop
Failed to stop sip.service: Unit sip.service not loaded.

pi@192.168.1.15:~/SIP$ systemctl status sip
Unit sip.service could not be found.

Thanks for any thoughts!
Gary

pi@192.168.1.15:~/SIP$ sudo python sip.py
Messge from Signaling plugin!: Just an example!
plugins loaded:
  mobile_app
  plugin_manager
  signaling_examples
  system_update
zones changed
Starting timing loop

[0, 0, 0, 0, 0, 0, 0, 0]
http://::192.168.1.15:8666/
Traceback (most recent call last):
  File "sip.py", line 291, in <module>
    app.run()
  File "sip.py", line 219, in run
    return web.httpserver.runsimple(func, (ip, port))
  File "/home/pi/SIP/web/httpserver.py", line 178, in runsimple
    server.start()
  File "/home/pi/SIP/cheroot/server.py", line 1820, in start
    self.prepare()
  File "/home/pi/SIP/cheroot/server.py", line 1779, in prepare
    raise socket.error(msg)
socket.error: No socket could be created -- (('::192.168.1.15', 8666, 0, 0): [Errno 99] Cannot assign requested address)

I am attempting to use a BeagleBone Black (BBB) Wireless A5, and have run into a few minor issues that required steps in addition to the setup instructions on your website. My background is mainly in embedded micro-controllers so I am somewhat new to embedded Linux. I am using Debian GNU/Linux 10 (buster) and have gone through all of the recommended updates/upgrades on Beaglebone website (https://beagleboard.org/upgrade) prior to following your setup instructions (https://github.com/Dan-in-CA/SIP/wiki/installation). Below are some additional steps taken to get sip.py to run smoothly. 

1. "nginx" was using port 80, so I disabled it, which allowed spi.py to load without error and I can now access the SIP's home page in my browser using the IP address of the BBB.
   
2. I was getting a GPIO error and realized Adafruit_BBIO.GPIO was not installed, so I followed the manual install instructions (https://pypi.org/project/Adafruit_BBIO/), which allowed sip.py to load without the GPIO error.
   

Hello All, 

I have a pi 4 connected to OSPI board with the pins directly plugged into the board. I have a separate power supply going into the pi, as its a pi4 which draws more power and it either doesn't start or I get the lightening (low power) symbol on startup if I don't supply its own power. 

Everything is working well in general, but I'd like to connect the pi via a rainbow cable rather than plug the GPIO pins directly into the board as I've noticed the pi4 gets a bit warm. If I have it via the Rainbow cable I can power a fan on the pi4 to cool it down. 

What I wanted to confirm is:

a) is the list of used GPIO pins here still correct? https://rayshobby.net/docs/ospi14_manual.pdf
b) Assuming if I drop the 2 x 5v ports and the earth, is this likely to cause a problem? As I have a separate power supply going in I don't believe it would, but just checking. 

Many thanks in advance.

Chris

Hi all,
   I have just installed SIP into a container (via git), exposed the port 80 and started off the service by python3 sip.py from /SIP within the container.
  Everything worked out, service is reachable....
   However, I tried to enable the relay_16 plugin and got the following reported by sip on the console:

Would be nice to limit the system to not run for anything less than x mins/secs in the Weather Plugin.  My system ran for a whopping 6 secs per station yesterday.

Cheers!

Hi Dan,
could you add the pins definition possibility to the Relay16 plugin? It means which relay is wired to which Raspberry PI pin. I see I can set it in the relay16.py file, line #70, but I'm afraid when the plugin will be updated, my config will reset.

Is possible to integrate Netatmo weather station instead openwathermap.org?

I think in many locations openweather isn't so precisious.

Hi Dan,

I just upgraded to v4 from 3 and ran into a problem. In order to avoid opening a port in my router specifically for SIP, I had been running it at 

https://mydomain.com/sip/

I have one machine which listens on 443 and proxies to others depending on the URL, e.g. in this case to a PI running SIP for all URLs that start with /sip/

With version 3, this worked fine, but it doesn't work in 4. The first problem I tracked down is that base.html has