Hi 

After my original PI and opensprinkler got fried in a power surge I replaced the unit and rebuild the application and then imported a backup of my setup.  It's working great as always but I need to edit a program to add another station.  When I edit the program I get the below error. 

internal server error

Any help would be great

Thanks
Paul

Due to the long distance and a higher number of stations, I would like to control the valves via modbus. I already have Arduino boards ready that can be controlled via modbus. From the Raspberry I can switch them on and of via modbus. Now I would like to use modbus commands (which are python function calls) instead of GPIO pins. What would be the best way? The most clean way would be to write a plugin. But I am not sure if that would be appropriate here as it would influence a central part of the control architecture.

Dan, or someone,

can you explain the use of plugin_map in sip.py, which limits the URL of any button added to plugin_menu to 2-characters plus the leading '/'?

I'm developing a plugin which will add 3 items to the Plugin menu. The URL names are all different, but not the first 2-characters, since they "belong" to the same plugin, the URL names start with the plugin name.

For example, using the proto plugin, if one does the following, the URLs are rejected by the 3-character test in the plugin_map code.

Hi I had a opensprinkler base on a PI 1a which unfortunately received a power surge and a couple of chips on the opensprinkler board have been fried.  So I bought a replacement board and I have been following the instruction from the Github https://github.com/Dan-in-CA/SIP/wiki/installation.  When I manually start the program everything appears to work correctly and I have imported my saved configuration back onto the new SD card .

The issue I have is that when I follow the instructions to make the SIP program start automatically it doesn't work.  I have tried the recommended way 

1.-Starting sip.py from a script in /etc/init.d
2.-using rc.local
3.-using systemd

Nothing seems to work, I'm obviously missing something but I just cannot see what; any help would be greatly appreciated.

Thanks
Paul

UPDATE ***** fixed in SIP Ver 3.1.93 when running the latest Jessie Raspian. **** Thanks to Dan for his assitance with this fix.

Hi there, have a rain sensor issue...SIP ver 3.1.87, Options > Rain sensor, Use Rain sensor ticked and Normally Open ticked.

Shorted Grnd and Pin 8 (Rev1 Pi - GPIO 14) and home page shows Rain Delay and Rain Sensed and Stations show Suppressed by Rain Sensor - good.

Removed short between pins - stays the same...refreshed for >15 minutes, same. Logged out and back in, cleared browser cache, same...
Restarted SIP with Options > System Restart > Restart - same
Restarted RPi with Options > System Restart > Reboot - same
Manually toggled the  Options > Rain sensor, Normally Open to unticked - that cleared the Rain Sensed to No Rain sensed, but the Stations still show Suppressed by Rain sensor.
Toggle it back again and Rain Sensed is back again

how/when is the rain sensor reset?
Is there a time delay?, if so how long and where is it configured? <-- I found this. Home Page > Rain Delay item, click it and it prompts "Enter hours to delay" with a default of zero. I'll try changing the zero to 1.
Cant find any reference to it.
Also had a devil of a time finding any reference to where a rain sensor would be connected. Eventually found one reference to pin 8 here http://nosack.com/sipforum/showthread.ph...ight=pin+8

Recommend that connection of rain sensor contact needs to be added to here https://github.com/Dan-in-CA/SIP/wiki/rain_sensor
Perhaps also mention connection on Options > Rain sensor tooltips.

I'm toying with the idea of integrating images next to the valve controls.    The idea as of right now is to link to network based images, so pictures are not required to be stored locally.  Maybe have an option to store locally.    This will be useful with IP cameras and rPi cameras.


some guidance on where I should look to add in this functionality would be helpful.

Hi,

I have been experimenting with Raspberry Pi, SIP and the MQTT plugins as a Misting System. Controller.  I 'm using a free AWS CloudMQTT service as my broker. I hard coded a Username and Password into MQTT.py to allow authentication on the broker. I'm using a MQTT Client iOS app to control SIP via the broker. This allows me to control the system from outside the house, without having to set up any VPNs or Port Fowarding.

I have found that the MQTT Plugins stops working if the wifi network connection is momentarily lost. I have two wifi hotspots and determined that the Raspberry Pi network connection is stable to one hotspot but not the other. the SIP program continues to work and I can access it via the browser.

I was wanting to turn on the DEBUG logging on SIP, so that I can investigate. How is the best way to do this?

Thanks,
Dave

Hi,

I just wanted to put up a short note that I have started developing a plugin to control a relay board that is interfaced to a Raspberry Pi using a MCP23017 GPIO expander.
The code is very much in its infancy at the moment, and is really just a hack of the relayboard plugin.

My approach has been to abstract the hardware interfacing elements out of the SIP plugin and rather have it call 2 C programs which respectively initialise the MCP23017, and control valves.  This has the side effect that the plugin could be repurposed to interface to a different hardware layer by purely replacing the 2 C programs.

The code still needs tidying, but it looks like it is working so far.

I would be interested to know if anyone else has a use for this plugin.  (That would motivate me more to get it to a point where it can be redistributed.)

Regards,
Geoff.

Since the latest SIP update which I installed yesterday Nov 06 2016, I'm getting an error from the weather_level_adj plugin. I have my location in Options set as pws:STATIONID (replaced with my station ID of course).

The error I'm getting is:

SIP's native web interface now works on mobile devices such as phones and tablets.

It still needs some work but is quite usable.

It does not require installing an app so it won't use extra resources on your device only a web browser is needed. This also allows access to plugins which are not supported by the OpenSporinkler mobile app.

It is also easy to use with a VPN for remote access. I easily set up a VPN server on a Raspberry Pi connected to my home router using PIVPN:
http://www.pivpn.io/

It did require installing the OpenVPN app on my phone but I can now securely access SIP (and other devices on my home network) from anywhere in the world where there is internet connectivity.

Dan