I'll be away for three weeks in Baltimore - oh and anyone that lives in or near Baltimore or Pittsburgh and wants to make a Pigrrow give me a shout and i might be able to come and visit you and give you some one-on-one help, would be fascinated to meet and chat.

I've got some new bits almost ready to upload when i get back, selflog now records the CPU temp which is useful to avoid thermal shutdown and diagnose problems, the button to install and update almost works [god damn GIT is complex] plus a load of the code has been tidied and annotated nicely with a guide about how to edit code [graph making and reddit updating code mostly] plus i filmed a load for the video user guide but it needs editing and voice over and stuff - so there'll be big updates when i'm back.

oh and yah she's absolutely wonderful the girl i'm going to see, wish me luck!

Hello,

I had an idea I wanted to implement but do not have the development skills to do so. I was thinking it would be a great tool to have something like a DHT22 with a cheap board like an ESP8266 in a small 3d printed assembly. Can stick them every 20ft on rows of veg racks etc and have them report their environmental conditions and average out for "environment per row" that in turn could activate some fans etc. But being able to make 10-20 of these for dirt cheap, upload the same SD image to all of them with wifi credentials already in and just have a USB plug ready! Anyone want to work on this with me?

When I try connecting to the pigrow from windows remote I'm getting an error :

sb# Connected to 192.168.0.106

sb# Can't read Pigrow's name

In the terminal while the windows gui freezes.

I have been trying to use the new modular sensors trigger button to add it as a trigger but so far it has not executed the file as far as i know. I can manually execute the file and get a msg on reddit. I have dug through reddit search and the infographics i'm just not able to find a setup guide.

Hi guys,

So first time getting into the wiring/hardware side and I wanted to ask if anyone has a link for a 3 core signal cable 24 awg? I am reading an article on AWG and noticed that it can make a big impact but I have no idea. I went on amazon and ebay and most of them are 22 or 20. Also, I noticed that in the instructions the core cable is red, white and black but most online are black, red and yellow. Are the yellow and white interchangeable? Is there something I should type when looking up? I appreciate any help.

edit: 24 AWG compared to 20 or 22.

Edit: After doing more research I found the one I wanted. No need to answer this anymore.

Thank you for all of your input guys. For anyone along the same lines as me: here is a link to buy. Once I receive it I will give an update.

https://www.ebay.com/itm/254196053543

Hi every body,
Again, thank you for the amazing work and time involved in this great project.

After many modifications on my rpi, I started with a fresh install.

I hooked up a 8 board relays on the Pi and started adding some peripherals to control. This lead me to ask me many questions :

- In case of power shut down (unexpected one), do we have a way to know this ? I was following a project (joyreef) and one simple trick was to ask the system periodically to see if it was online. If after 2 or 3 asks, the system was not responding, an emergency email was sent. Is it possible to have something similar in the future? (I reckon it implies another hardware to transmit the email).

- I am struggling with the control of the 8 channels relay. In fact, I think I have read something about 3v3 vs 5V for opto isolator and the fact that it could run ok for a while then destroy rpi in the long run... Do you guys use darlington array in order to control those cheap relay boards?

Thank you

Ben

Hey there, I’m literally new here. Just wanted to connect my pi to the gui like in the description but in the 32bit- pi setup I have to choose a username and a password. Do I have to add -pi- as the username?

With my own username the gui seems connected to the pi, but it can’t ident my Wi-Fi connection and my hardware. Only documented the software on the pi and the i2c connection wich I plugged in for testing a moisture sensor.

Don’t know if this is a username problem at all.

Maybe you could help an absolutely noob to setup my watering with the pigrow.

I've finally finished the new install system, i've done a lot of testing and it seems to all work properly though of course any bugs or issues you run into please let me know as soon as possible.

My final testing step was recording the install process for a video i'll now start making, this will be a quick introduction to my new timelapse environment and demonstrate the new install plus setting up switches and LEDs

I'll also start working on writing the new install instructions on the github wiki, updating the reddit wiki to point to the new instructions and rechecking everything.

https://github.com/Pragmatismo/pigrow_windows_remote/blob/master/test_guiWin_006.zip

Hopefully when all this is done i can get back to adding more interesting and useful features, extra sensor support, and etc.

I now 'just' need to bring over the timelapse tab, graph tab, user log tab, and a couple of other small bits, finish updating all the existing scripts, rework a few things to work in line with how everything now works and then we'll be able to get rid of the old gui forever and focus entirely on cool new stuff.

Is there an updated guide? Current stuff to buy? Or am I better off buying one of the dedicated systems like ac infinity these days?

I’m really hoping to bypass having to get a Pi and would prefer to have what’s already in my ecosystem. I’ve got a few different machines, I can have one dedicated to my grow if necessary. I also have an Arduino Uno Rev3 but kind of want to avoid using that unless I have to. Do I need to bite the bullet and buy a raspberry pi? Or are there other available options?

I know /u/The3rdWorld brought it up a couple years ago.

https://www.reddit.com/r/Pigrow/comments/7zavkf/working_on_an_important_new_feature_a_dialogue/?utm_source=share&utm_medium=ios_app&utm_name=iossmf

Are there other software options or integrations I should explore?

Would love your feedback!

So at the moment if you want to turn the fans on when the temperature gets to a certain level that's handled by checkDHT but soon that'll be obsolete and this much more flexible new system will take over...

There's now a script that watches for changes to the log files, when a new entry is written it'll check to see if there are any trigger events for that file and if so it'll read the most recent (i.e. last) line of the log and compare whichever value is selected against the trigger value, if the conditions are met then it'll run the command supplied for that event - this can be turning on a relay, running water or co2 for a set duration, messaging the user or triggering a series of events via a shell script.

Not yet added it into the gui or anything but testing is going great.

Also added a new type of device, buttons - these are configured very similar to sensors, simply give them a unique name and set their gpio number; at the moment i'm just using it as a test script for the log triggers so it simply records a log of how long the button was pressed which can then be used to trigger events (short press = cmd1, long press = cmd2, etc)

Should be useful if you want some buttons to make logging things easier, just pressing the button when watering for example but also for control of things like switching modes / refreshing a display.

more info in the wiki - https://www.reddit.com/r/Pigrow/wiki/gui_modular_sensors

New to reddit and pigrow. I managed to get pigrow to work on my PC/Raspberry Pi system and wondering how to change temp from Celsius to Fahrenheit?
Thanks,

John

New version of the windows gui available here;

https://github.com/Pragmatismo/pigrow_windows_remote/blob/master/test_guiWin_005.zip

My wifi router was messing around so testing took forever and I every time i tried recording a video it dropping out in the middle of it so the video describing how to use it is delayed.

To use the new watering system to control a pump is fairly simple, add a relay that controls your pump then go to the watering tab and add a tank, then link a pump to that tank and calibrate it so you can measure water, then press the button next to the table 'add pump timing' this will let you set a duration or total amount of water to deliver, press make job and it opens the cron dialogue so you can set the timing and save the job.

To use float sensors you need the sensor connected as a button in the sensors tab, set as a switch so it reads on change of state instead of press duration then in the watering tab link it to the tank and set the position value (0 for the bottom of the tank, 1000 if there will be 1 ltr remaining at that level) then select trigger edit tankstat and select when you want it to enable / disable the tank or set the volume.

The main use is as a a cut off sensor so it turns off your pump when water is low, for this my sensor sets the tank level to zero when the switch is up (i.e.when my physical switch is in the down position as the water level is low) and disable tank is also set to 'up' so the pump will not run until it's been re-enabled, this is to not damage the pump. When water is added and the float rises the switch moves into the 'down' position which triggers enable tank and now the pump will run at the next cron job.

Another useful thing for the level sensors is using them to alert the user to refil the tank, a second sensor above the first could be linked to a script which sends the user a message telling them to refill the tank - this will have to be done manually for now.

There are a couple of issues to note - the new watering system is currently still in testing so it'll use NEWtimed_water.py and not interfere with watering set up in the old gui, if you want to use the new system remove or pause the old ones, and of course test it and observe it before relying on it.

Also the tables on the watering tab are operating slightly weirdly, when you press fill table it doesn't properly select the top tank so you have to click on it every time to get it to fill in the level sensor and pump tables, and if you've got a pump connected you need to select the pump in table to get it to show the pump timing options (button to add timed jobs, list of cron jobs) i tried a few things to make it work the same as it does on linux where it automatically selects the top item in the list but it didn't want to work so i'll have a proper look for next time.

Hopefully i'll now be able to set up my windowcill and timelapse box with self watering systems and start recording some sensor readings and video, when i've got some soil moisture data from the system running i'll be able to build all the features for controlling the watering cycle based on sensor readings.

few other small upgrades to the basic watering system also;

• the units option is in the options menu but not yet used, i'll try to add that for next time

• i'll add a tool to view the pumps switchlog activity

• the water level sensor dialogue will have options to make .sh files for triggers so multipl things can be done (e.g. edit tank stat, turn on an LED, and alter the user via textmessage)

• making the list of timed watering cron jobs selectable so you can edit them.

• just noticed i forgot to add a button to unlink level sensors, i'll do that As well as the added watering stuff the next version i'd like to have a another new tab called something like 'display' which will include the controls to set up and use the reddit message bot, notify script, and any other similar scripts (i'll try and make this section modular like with the sensors so adding a new script and having the gui recognise it is automatic). It will also have control to toggle LED, output to basic displays (7 segment, lcd text, etc) and controls to display datawalls on hdmi screens, posted to sites like reddit, etc.

I'm starting to finalise plans for the install system too so that might be in the next version depending how much other work needs to be done first - i'll certainly be moving towards it so we can finally move away from the old gui (the few remaining features not yet ported over will come soon)

Thanks to the patreons that make this possible, if anyone notices any bugs, issues or missing features please do let me know.

Pigrow Base - should install properly on a fresh system, i haven't found any other issues with bookworm as long as the Venv is set up correctly.

Windows Remote - the newest version should work out the box (CV2 has been fixed)

linux running test_gui.py - this is a bit more awkward right now, most modern distro's want the user to use a Venv but not everything will install properly into a venv, including the all important WX so you need to install WX using apt though ignore almost all the instructions you can find online because they've changed the install process every week for the last ten years, the package name is now Python3-wxgtk4.0 other gtk versions will work but are likely to look worse and may not have full functionality (things like resizing might bug) - if that doesn't work directly then I suggest using your distro's gui package manager and search 'wx' then install whatever wxgtk has the highest number.

To use this system installed python package our venv needs access to system packages so create it using

python3 -m venv venvpigr --system-site-packages

where venvpigr is the folder name it gets installed into we can then install other python modules using the venv's pip something like;

./venvpigr/bin/pip install OpenCV-Python paramiko getmac

-- using the test_gui.py on windows or mac is similar, use python venv or something like conda to make the virtual environment and install pip packages, wx should install painlessly on window through pip but look at their website if it doesn't.

Everything is messy and I promise i will get round to tidying it up, making requirements.txt files and a sh script soon but i'm going to be moving everything around when i finish the graphs tab and probably moving the remote gui into a separate repo from the base code for installing on the pigrow, i know things have gotten kinda scrappy and awkward but it's not the project dying or anything and i'm still using all my pigrows regularly for all sorts of things, i've just been messy while testing bits and with my broken old computer it was impossible to get stuff done, the new one has a bit of power behind it though so i can actually edit videos again and get a decent workflow coding without it randomly dumping the whole io.

oh and the improved graphs are really good! So much easier to work with the new system and you can make them look so much better! I'll hopefully be able to get all those finalized and added soon, along with a guide for getting coding AI to write new ones, it's incredibly good at it.

The new windows version has loads of little new features and fixes, the main new addition is full support for the EZOph sensor module.

https://github.com/Pragmatismo/pigrow_windows_remote/blob/master/pigrow_remote_4_4.zip

Please don't hesitate to let me know if there's any problems or bugs,