Dan,
 
    I'm writing a plugin that uses weewx weather station to emulate the rain sensor function. With a bit of mods to helpers, gpio_pins, and sip I can pass the output of the plugin to the "rain_sensor" value in helpers, no tracebacks. However, when I print out the plugins.__all__ variable it only shows 1 instance of my plugin in the list. But on the homepage dropdown there are 2 in the list and the stations all show "LOADING......"  I'm using version 4.1.51.

   I  disable my plugin and just let the fake_gpio library control the rain_sensor it randomly changes between 1 and 0, stations, all load and homepage functions as expected. I'm sure I'm creating some kind of loop. in sip.py the tweak I made was to assign plugins.__all__ to a global that I could pass to helpers.py so that I can see if the plugin is loaded to ensure that the rain_sensor variable is being set in the check_rain() subroutine. That all seems to work fine. Just don't understand the problem I've created with the plugin to cause the problem.

Thanks,

  Bryan

Update: Nevermind. Just had to use a gv.sd and add an new global value for the wx_rain_sensor value to pass between plugin and helpers and issue went away.

Hi

I'm playing with node-red and have tried the examples supplied. Thanks for doing those.

All work except I'm not sure what the URL in the HTTP get node should be. 
The post from node-red to SIP works as expected.
SIP and node-red are on two different Rpi's.

The reason i'm asking is that nothing comes in through those nodes

kind regards
daniel

I must be pretty stupid  

I used the curl installation method on a freshly minted rpi os 64-bit lite. I did install python 11.4. also no issues.

SIP seem to install OK. but the service is not starting with the following output:

lcd_adj plugin returns blank page with "internal server error"
I started SIP manually with these commands:
sudo systemctl stop sip
cd SIP
sudo python sip.py

When I select the SETTING LCD button it returns blank page with "internal server error"
This is the error it gives me:

8-19-2023

With the release of version 5.0.0 SIP will run under Python 3 only. Support for Python 2.x has been removed.

The latest Raspberry pi OS uses Python 3.9.2 as default.

If you are running an older version of Raspbian such as Buster it would be a good idea to upgrade to the latest Raspberry Pi OS

This release also includes a new Polish language translation.

A new node-red plugin is included by default but is not yet activated. It is usable but is still a work in progress. The documentation has not been finalized and the SIP irrigation nodes need to be published to the node-red library. This should happen within the next few days. 

8-23-2023
The SIP irrigation nodes can now be installed from the node-red library.
Open "Manage palette" (Alt Shift P) and search for "sip" or "irrigation". You should see a module named
" @sip-irrigation/node-red-sip-irrigation-nodes"

Dan

Hi Dan, Hi all,
Hope you've all been safe and well.....

Noticing general weirdness after install fresh build fresh RPi and SD...
RPi 4, latest Raspian (as of 10/8/2023) and took the python3 path for SIP.

Once installed and started, but prior to reboot, the version and date shows as 4.1.54 (2023-03-25)
After reboot and then make first change, e.g. change Default Language to English and save, (which then restarts SIP) then UI reports 4.1.999 (2015-01-09). 

Also seeing popup message "SIP could not restart.Please restart the program from the command line". This occurs, for example, even after name change when I can hear (default ON relays open and close) and see UI restart SIP.

Once fully configured as I need, it appears to work as previous SIPs I have built, apart from the cosmetic versioning issue and the restart alert popup.

Anyone else?

Hi, I've been using SIP for years but recently having some problems with reliability. This is likely not SIP's fault, I have semi-regular power outs and network outages. I have some alerts set up to let me know if SIP is unavailable for a long time, but it turns out they're not enough. I'd like to add an alert if for whatever reason the sprinklers haven't been active in several days.

I thought of doing this by checking the sip log / history for latest run date. The documentation around the API and the fields it returns is ... not entirely clear to me.

I found info here: https://nosack.com/sipforum/showthread.php?tid=156
cross-referencing that with https://github.com/Dan-in-CA/SIP/blob/ma...erence.txt
I thought I could use the /jc command's lrun section. 
"last run, used to display log line on home page (list [station index, program number, duration, end time])"

While the first two numbers change, I'm always getting the same value for the last two:
  "lrun": [
    0,
    3,
    1200,
    0
  ]

this is the result shortly after one of the stations was open for 20 minutes in the middle of the afternoon.

The date and time are set correctly on the machine where SIP runs.

I also tried the /jl command. I'm getting an empty array, despite the fact that I enabled logs, see the latest run in the web UI and the /wl command downloads a CSV which includes the latest run.

Am I doing something wrong, or can you help me understand the right way to programmatically pull the latest run?

I'm running version: 4.1.53 (2022-12-04).

Dan,

      As I have been hacking away on my weewx plugin. I noticed something with hourly display on the homepage that I have not been able to chase down the cause. If I open the homepage during the time window when programs are scheduled and the system enable is off, the hourly window shows programs scheduled to run/or could have been in an ~1nr window around the current time indicator bar (they are hashed, I think indicating they are not being run). The color/name legend at the bottom shows up but the name portion is not the station name from the programData.json as it would be in for a program that has been or is being run. Instead the name is "PROGRAM #" where, # is the pid of the program. Is that intended?
I have the 24hr-clock option off.

Thanks,

Dan,

    Still hacking away on my weewx weather station plug in prototype.
    I've been scanning the code to understand how the enable/disable program works. The HTTP method is useful and SF for my shell script implementation. However, as I'm implementing the plugin I can't see a variable or list that handles program enables. I see that urls.py and webpages.py is the way the the HTTP method accesses the programData.json file to handle enable/disable.
    Also I see that gv.pd is the load of program data into sip.py for use executing programs.
    Here is my higher level reasoning, I have programs setup to handle my lawn sections, and programs for my veggy garden drip and another program for shrub drips. I use a monthly data json file to enable watering for the three program types. I use lawn as the system enable/disable and programs are always enabled since lawn has the largest window in months (system off in the cold/rainy months). Once system enabled for lawn, I  want to enable/disable veggy garden and shrubs programs based on the growing/hot dry months of the year (May,Jun,July,Aug...)

Any thoughts on the best way for a plugin to modify the programData.json?
   Should I use:  u"/ep" variable to "fake" a GET request via the plugin?
   or
   just use:
        gv.pd[pid]["enabled"] = int(["1/0"])
        jsave(gv.pd, "programData")
   in the plugin?

I have messed around a bit and programData seems to be a dict, which I have not handled yet in python. Seems that a for loop can find the index of an item in the dict and then I can change then enabled entry in that item.

Thanks,
Bryan

I thought I found this info once, but cannot find it again. Are there any docs for the abbreviations used for the global variables in gv.sd?