7.0.0beta?

codster

codster

New member
Hello. I was just thinking about updating my software. I see you have a 7.0.0beta linked in the install document now. I read ur working on making it compatible with the newer raspOS? What version of raspOS should we install for this? Trixie?

Thanks for all the hard work. If Trixie isn't support yet for 7.0.0beta, curious if u know roughly a time line? Within the next month? Im in no rush but donno if I should throw this 7.0.0beta on, or wait a couple of weeks.

Thanks.
 
Sort by date Sort by votes
codster said:
Hello. I was just thinking about updating my software. I see you have a 7.0.0beta linked in the install document now. I read ur working on making it compatible with the newer raspOS? What version of raspOS should we install for this? Trixie?

Thanks for all the hard work. If Trixie isn't support yet for 7.0.0beta, curious if u know roughly a time line? Within the next month? Im in no rush but donno if I should throw this 7.0.0beta on, or wait a couple of weeks.

Thanks.
Click to expand...
Hi @codster good timing, I updated the manual last night. I do have a new app ready for beta testing, I'll be posting about it soon. I feel confident about it but do verify everything goes as expected if you try it. It does work with Trixie 32/64 bit versions. If you try it let me know your thoughts, best to use a spare SD card so you card return back to your setup if needed.
 
Upvote 0 Downvote
Hello. I installed 7.0.0b today and everything went great! Thanks. My [Version 1 Rev B] setup is pretty simple (just a temp and ph sensor), but all seems to be working, no errors. I haven't re-calibrated the sensors yet, but they are producing numbers.

My setup:
- RoboTank Controller Version 1 Rev B
- Raspberry Pi 4b
- Raspberry Pi OS Trixie 64bit [Desktop]

Some questions:
- Is the Lite OS version okay to use?
- I followed the directions on the setup page, with using CONTROLLER VERSION 3 for setup, and then setting CONTROLLER VERSION 1 in settings, reboot, and redoing the initial setup. This way worked, but is this still necessary? Since setting the controller version requires a restart, maybe it'd be good to set the initial controller version in the install script? Would make the initial setup a bit easier for people with version 1 and 2 of the controllers. :p
- is the DHT22 (temp and humidty) working with Trixie right now?

Thanks again for all the hard work.
 
Last edited:
Upvote 0 Downvote
Tried installing 7.0.0beta on a Pi Zero 2 W with Raspberry Pi OS Trixie 32-bit Lite and hit an error at the final step.

Setup:
- Robo-Tank Controller Version 3
- Raspberry Pi Zero 2 W
- Raspberry Pi OS Trixie 32-bit Lite
- Robo-Tank 7.0.0beta

Everything went fine through Steps 1-9 (OS update, MariaDB, Apache, PHP all installed successfully). Failed at the app build step with the following:

[ERROR] Building Robo-Tank apps failed.
as: error while loading shared libraries: /lib/arm-linux-gnueabihf/libbfd-2.44-system.so: invalid ELF header

Looks like libbfd-2.44 is installing but coming out corrupted or incompatible on Trixie 32-bit. The previous successful install in this thread was on a Pi 4B — wondering if this is a Zero 2 W specific issue. Let me know if you need the full log. Thanks.
 
Upvote 0 Downvote
Hey Rob,

I gave the Beta a whirl this weekend and everything went mostly smooth, couple notes.

Setup:
- Robo-Tank Controller Version 3
- Raspberry Pi Zero 2 W
- Raspberry Pi OS Trixie 64-bit Lite
- Robo-Tank 7.0.0beta
  • The new scheduling interface doesn't go down to the seconds (just minutes), I have an auto-feeder that runs a motor on an auger screw and need to only run it for a few seconds. Is there a way to do this?
  • My optical water sensors don't seem to be recognized in the software. Do I need to enable in interface perhaps?
  • Is there a tool to setup a conductivity sensor? I got one of your boards about a year ago and would really like to fire it up.
Thanks for the hard work!
 
Upvote 0 Downvote
Hey guys, very sorry, I don't know why I didn't get an email for these.
codster said:
Hello. I installed 7.0.0b today and everything went great! Thanks. My [Version 1 Rev B] setup is pretty simple (just a temp and ph sensor), but all seems to be working, no errors. I haven't re-calibrated the sensors yet, but they are producing numbers.

My setup:
- RoboTank Controller Version 1 Rev B
- Raspberry Pi 4b
- Raspberry Pi OS Trixie 64bit [Desktop]

Some questions:
- Is the Lite OS version okay to use?
- I followed the directions on the setup page, with using CONTROLLER VERSION 3 for setup, and then setting CONTROLLER VERSION 1 in settings, reboot, and redoing the initial setup. This way worked, but is this still necessary? Since setting the controller version requires a restart, maybe it'd be good to set the initial controller version in the install script? Would make the initial setup a bit easier for people with version 1 and 2 of the controllers. :p
- is the DHT22 (temp and humidty) working with Trixie right now?

Thanks again for all the hard work.
Click to expand...
Hi @codster glad to hear it went well. Yeah the Lite OS is good to use, actually best choice as there's less overhead and less to go wrong on the OS side of things.

When you first loaded the app did you not get a startup wizard? Around step 8 or so it asks what controller version you use, it shows a picture of each controller.

The DHT22 doesn't work in current version but I've since added support and it's working well. Some time this coming week I'll be posting an update, if you have auto check enabled it checks every 24 hours and will tell you when it available.

irgunr47 said:
It was a bad SD card (Classic Amazon fakes). I'm up at and running now. Is the scheduling still the same for having equipment power on with reboot?
Click to expand...
Hi @irgunr47 I think we spoke about this through email, glad that solved it. The schedules and custom rules are checked when the controller powers up or reboots, if an outlet should be on when it starts it should switch. I highly recommend unplugging the power or doing a reboot from the System Settings page to verify.

JAC-FISH said:
Hey Rob,

I gave the Beta a whirl this weekend and everything went mostly smooth, couple notes.

Setup:
- Robo-Tank Controller Version 3
- Raspberry Pi Zero 2 W
- Raspberry Pi OS Trixie 64-bit Lite
- Robo-Tank 7.0.0beta
  • The new scheduling interface doesn't go down to the seconds (just minutes), I have an auto-feeder that runs a motor on an auger screw and need to only run it for a few seconds. Is there a way to do this?
  • My optical water sensors don't seem to be recognized in the software. Do I need to enable in interface perhaps?
  • Is there a tool to setup a conductivity sensor? I got one of your boards about a year ago and would really like to fire it up.
Thanks for the hard work!
Click to expand...
Hi @JAC-FISH thanks for letting me know, glad it went ok. That's something I missed, I will update UI so you can set seconds. For now to get around this you could use a custom rule with a schedule. When creating it, untick the "Sensors" trigger option on Step 1 and select "Schedule". On the "Actions" page add the port to turn on, add wait of 3s, then turn port off. That should do it. You can also set more failsafe so the feeder can run too often.

If you didn't get the optical sensor working, you do need to enable it. If you go to the "Sensors" page from Settings menu you can add it there. Then you can use it for other systems. I have since moved all the sensors to a central location as the settings menu was getting too many icons.

Power down the controller and connect the EC circuit to the I2C headers on main controller. Once it starts reload the browser page and it should recognize it. After adding it you can go to the "Probes" page from settings menu and set it up. Let me know how it goes.

RWilt81 said:
How long until this is going to be an official release? I’m interested to try it, but I don’t want to shut my system down
Click to expand...
Hi @RWilt81 I'm not sure when I'll call it "Stable", I still need more feedback. Feeling pretty good though as there hasn't been any major issues yet and around 15 people are testing it. I do have an update coming with some minor fixes and changes and then I'm going to announce it more but still as a Beta. If your tank is ok without a controller for a few hours you could install this on another SD card, check it out and then put your original SD card back in. BUT, I guess that still brings risk, maybe you shock the SD card taking it out and corrupt it.

FranzB said:
I would also be interested in trying the new release. Looking forward to it.

Thanks!
Click to expand...
Hi @FranzB sounds good, if you want to kick the tires a little here's a link to the install script.

docs.google.com

Robo-Tank App Installation Manual - Windows.docx

Raspberry Pi Operating System and Robo-Tank App Software Installation Manual Table of Contents Table of Contents 2 1. Install Raspberry Pi OS (Raspbian) 3 2. Access Raspberry Pi via SSH 10 3. Install Robo-Tank App 12 4. Other Manuals 13 1. Install Raspbe...
docs.google.com docs.google.com
 
Upvote 0 Downvote
I installed 7.0 beta last night to test out but i didn’t like how it looks and how we set up ports etc. it seems like a step backwards. I really like my 6.7 even though a lot of functions don’t work
 
Upvote 0 Downvote
irgunr47 said:
Is the conductivity probe active in 7 beta?
Click to expand...
Hi @irgunr47 very sorry for the long reply, just seeing your message now. I think I found the issue why the forum wasn't sending me alerts.

The conductivity is working in the app but it's still undergoing testing. Currently I don't have any more circuits, waiting for more feedback before I get more.

mytdbm said:
I installed 7.0 beta last night to test out but i didn’t like how it looks and how we set up ports etc. it seems like a step backwards. I really like my 6.7 even though a lot of functions don’t work
Click to expand...

Hi @mytdbm thanks for your honest feedback, I like when people tell me what they actually think. I'm very close to officially releasing it, there's been at least 30 people try it and things have been going really well, much better than original release of 6.x.

Is it the dashboard you don't like the look or all of it? If just dashboard I'm on your side actually, for some reason I've always had a widget layout in my mind but personally I don't like the look that much either. Thankfully a few people have said they do like it so not a complete loss lol. As for the settings pages I don't think they look that bad. The 6.7 dashboard will be back, user will be able to select from multiple layouts as that's not to much work but I think for a while the layout for the settings pages will remain.

I also agree with configuring ports, for simplicity I started with the basic page where user configure ports as my plan was to remove that page completely, a step that shouldn't be needed, that's why I didn't add the controller pics etc. I'm happy to say that has now been done along with some other things.

Currently, I've merged all the sensor and probes into a single page and the same with equipment so things are easier to find. Also ports are automatically configured in the background. For example, if you have a dosing pump on DC2, then you decide you want to use it for an ATO pump it'll do what you use to do on the configure ports page automatically. I've also added an ATO system.

What do you like about 6.7? If it does what you need there's no reason to stop using it. With that said, under the hood 7.0 is much better and lots of fail safes. Currently I believe it has all the features 6.7 has and more. I'm actually feeling pretty good how things are going with it, maybe once I get the new dashboards you can try it again.
 
Upvote 0 Downvote
Hi everyone, I gave 7.0.0 beta a test yesterday. Im configuring everything on a spare PI4 outside the controller.
I really like the new visual. The new ATO setup.

Since I have no temperature sensor connected I dont see any heater setup is it included now ?

Secondly, I configured one dosing pump but now when I go to settings and I click on dosing pump it bring me directly to the one I already configured. I cant add an other one. Is there a bug or I dont understand something ?
 
Upvote 0 Downvote
Alpine_Weiss said:
Hi everyone, I gave 7.0.0 beta a test yesterday. Im configuring everything on a spare PI4 outside the controller.
I really like the new visual. The new ATO setup.

Since I have no temperature sensor connected I dont see any heater setup is it included now ?

Secondly, I configured one dosing pump but now when I go to settings and I click on dosing pump it bring me directly to the one I already configured. I cant add an other one. Is there a bug or I dont understand something ?
Click to expand...
Hi @Alpine_Weiss glad to hear you're trying it out. Did you install 7.0.1, sounds like it as I don't think ATO was in 7.0.0. If so when I push the update you won't receive it but you can update the database in "systemSettings" table to 7.0.0 if you know how.

There is no heater setup yet, currently you need to use two custom rules, one to turn on and another to turn off. Next update possibly will have dedicated heater settings but I need to stop adding soon and get it 7.0.1 out.

For the dosing pumps that's an issue, I've since merge all equipment into it's own settings page and sensors into it's own so it will be much clearer. To add a 2nd dosing pump go to the "Configure Ports" screen, on the port you will use set the function to "dosing pump" and enable it, then when you go to the dosing pump settings page it should show both. Next update you won't need to use the configure ports screen for anything, today that's how you configure ports.
 
Upvote 0 Downvote
I will check for 7.0.0.1 but I used the 7.0.0.0 install script so I was thinking it was that version. Im out for the week but this weekend I will try your fix for the dosing. If that work I will hook it up to the tank.
 
Upvote 0 Downvote
Hopefully this isn't user error, but my outlets come up de-energized after restart while the UI still reports them ON. Toggling the affected outlet to Manual, ON brings it back immediately.

Worth noting how I turn these on in the first place: I use custom rules that I run manually. Nothing is set up in the Schedules section at all. So the ON state being persisted comes from a manually-run custom rule, not from a schedule.

Everything below was Claude AI helping me collect data:

It looks like outlets are requested at startup with a hardcoded initial value of 0, and nothing reconciles them against saved state afterward.

Boot log — all four of my enabled AC outlets:

```
[configurePorts] Loaded 39 configured pins from DB
[acOutlets] Requesting GPIO line 21 for pin 5 (invert=0, initial=0)
[acOutlets] Requesting GPIO line 20 for pin 6 (invert=0, initial=0)
[acOutlets] Requesting GPIO line 6 for pin 11 (invert=0, initial=0)
[acOutlets] Requesting GPIO line 16 for pin 18 (invert=0, initial=0)
```

I went back and added a schedule ON BLOCK that runs 00:00 to 23:59 and it came on with reboot, both UI & actually.


Hope this helps
 
Last edited:
Upvote 0 Downvote
Alpine_Weiss said:
I will check for 7.0.0.1 but I used the 7.0.0.0 install script so I was thinking it was that version. Im out for the week but this weekend I will try your fix for the dosing. If that work I will hook it up to the tank.
Click to expand...
Sounds like you have 7.0.0, you would have had to manually change it, I just didn't think I had the ATO with it yet. Let me know how it goes.

irgunr47 said:
Hopefully this isn't user error, but my outlets come up de-energized after restart while the UI still reports them ON. Toggling the affected outlet to Manual, ON brings it back immediately.

Worth noting how I turn these on in the first place: I use custom rules that I run manually. Nothing is set up in the Schedules section at all. So the ON state being persisted comes from a manually-run custom rule, not from a schedule.

Everything below was Claude AI helping me collect data:

It looks like outlets are requested at startup with a hardcoded initial value of 0, and nothing reconciles them against saved state afterward.

Boot log — all four of my enabled AC outlets:

```
[configurePorts] Loaded 39 configured pins from DB
[acOutlets] Requesting GPIO line 21 for pin 5 (invert=0, initial=0)
[acOutlets] Requesting GPIO line 20 for pin 6 (invert=0, initial=0)
[acOutlets] Requesting GPIO line 6 for pin 11 (invert=0, initial=0)
[acOutlets] Requesting GPIO line 16 for pin 18 (invert=0, initial=0)
```

I went back and added a schedule ON BLOCK that runs 00:00 to 23:59 and it came on with reboot, both UI & actually.


Hope this helps
Click to expand...
Thanks for info, this is an issue that I believe I've fixed. Your correct they were hardcoded to off, immediately after that happens it's supposed to look for related custom rules and schedules and set each outlet accordingly. The manual mode had some issues as well. Sorry shouldn't be much longer before the update is ready, lots of fixes in it.
 
Upvote 0 Downvote
Back
Top