reef-pi :: An opensource reef tank controller based on Raspberry Pi.

[Zippyfear]

About a minute before reading this I did the same thing... Sadly I think the only current way is it delete and reinstall reef-pi but I am not 100%. I don't plan on changing connectors or adding new ones so I will hold off.

Literally did the same thing a few days ago.. lol. Maybe we can formally request a button to export the DB to a backup, and restore it?! :)

 

[Ranjib]

Literally did the same thing a few days ago.. lol. Maybe we can formally request a button to export the DB to a backup, and restore it?! :)

It is one of the itemized feature thats planned since 2.0, but i never got to actually implement it. Its complicated by the fact that reef-pi 's internal database is going through changes (which i expect to settle by next year, release 5) and lack of validation logic in the controller.
This particular problem comes from the fact that reef-pi allows you to delete drivers without deleting the corresponding connectors first, leaving them zombie.. which results in this. Theres a backend validation logic which should not allow this, as well as front end reliability logic , i.e. the ui should not crash if the driver is not present/undefined. I'll make sure we address this as soon as possible (yes, this work itself is also itemized and im working on it in 4.0). Since the introduction of HAL our feature capability has increased and so is the surface area of different driver induced issues.. we just have to address them one by one and do a much more rigorous job in field testing. Ofcourse, your inputs/feedbacks are the cornerstone of this process.. so thank you .

 

[Des Westcott]

Literally did the same thing a few days ago.. lol. Maybe we can formally request a button to export the DB to a backup, and restore it?! :)

Here is a "Feature Wishlist" started to keep track of things like that

reef-pi User Interface (UI) development thread

After a discussion with @Ranjib, we have decided to open a separate thread for the discussion around the reef-pi User Interface (UI). This thread is for suggesting UI features / upgrades reef-pi users would like to see in reef-pi. Requesting / suggesting a feature here is not going to be a...

www.reef2reef.com

Please copy this post there

One request / "wish" per post and feel free to "Like" any ideas you think are worth seeing. Nothing is a guarantee it will be implemented, but the Devs can get an idea what the community wants and can prioritise what they can implement.

 

[Des Westcott]

It is one of the itemized feature thats planned since 2.0, but i never got to actually implement it. Its complicated by the fact that reef-pi 's internal database is going through changes (which i expect to settle by next year, release 5) and lack of validation logic in the controller.
This particular problem comes from the fact that reef-pi allows you to delete drivers without deleting the corresponding connectors first, leaving them zombie.. which results in this. Theres a backend validation logic which should not allow this, as well as front end reliability logic , i.e. the ui should not crash if the driver is not present/undefined. I'll make sure we address this as soon as possible (yes, this work itself is also itemized and im working on it in 4.0). Since the introduction of HAL our feature capability has increased and so is the surface area of different driver induced issues.. we just have to address them one by one and do a much more rigorous job in field testing. Ofcourse, your inputs/feedbacks are the cornerstone of this process.. so thank you .

Hey Ranjib

How about a teaser of what we could see in the final release of 4.0. ie what features are the team working to include??

 

[robsworld78]

I'm having some issues with Macros, I think its a bug but could be me, using 3.3.1

If I setup a macro to turn on a piece of equipment wait 1 second and turn it off, then attach that macro to a sensor it works. When sensor is open the macro doesn't run and when sensor is closed the macro runs over and over.

I only want it to run once and this is where the problem occurs.

At the end of the macro I add a step to disable the sensor, this does cause the macro to run only once so the sensor seems to get disabled however when I view the ATO sensor tab it still shows it's on and when I click the on/off button nothing happens for it or any other sensors setup up. If I click on/off, leave tab and return, the change is reflected on other sensors but the sensor I just disabled via macro will go off but immediately come back on. Also the communication from UI to system stops, it's like the program is in a loop it can't exit. When I try to change settings they don't take effect as it's not communicating, press refresh and it won't reload. I then power cycle the Pi and I'm able to delete this macro and everything will resume back to normal and I can turn on/off sensors again so it does repair itself once the macro is gone.

This is how I set it up, the last line is what breaks it.

My idea is another macro is triggered via a timer, that macro will enable this sensor which is in a closed position, once it opens it triggers this macro that switches some equipment and then disables the sensor as its no longer needed.

 

[Des Westcott]

I'm having some issues with Macros, I think its a bug but could be me, using 3.3.1

If I setup a macro to turn on a piece of equipment wait 1 second and turn it off, then attach that macro to a sensor it works. When sensor is open the macro doesn't run and when sensor is closed the macro runs over and over.

I only want it to run once and this is where the problem occurs.

At the end of the macro I add a step to disable the sensor, this does cause the macro to run only once so the sensor seems to get disabled however when I view the ATO sensor tab it still shows it's on and when I click the on/off button nothing happens for it or any other sensors setup up. If I click on/off, leave tab and return, the change is reflected on other sensors but the sensor I just disabled via macro will go off but immediately come back on. Also the communication from UI to system stops, it's like the program is in a loop it can't exit. When I try to change settings they don't take effect as it's not communicating, press refresh and it won't reload. I then power cycle the Pi and I'm able to delete this macro and everything will resume back to normal and I can turn on/off sensors again so it does repair itself once the macro is gone.

This is how I set it up, the last line is what breaks it.

My idea is another macro is triggered via a timer, that macro will enable this sensor which is in a closed position, once it opens it triggers this macro that switches some equipment and then disables the sensor as its no longer needed.

This "issue" ties in with my other posts regarding my challenges with Macros and running them off timers as well as macros running macros. I have been processing in my mind how a sensor triggering a macro would work and the response you are getting is what I would expect.

For a macro to run off a timer, it must be reversible and will only run in reverse.

The Macro ability and associated manipulation of them are what (for me anyway) makes reef-pi so brilliant.

As we are developing use cases for the feature, we are going to come accross more and more of these "hiccups".

 

[robsworld78]

This "issue" ties in with my other posts regarding my challenges with Macros and running them off timers as well as macros running macros. I have been processing in my mind how a sensor triggering a macro would work and the response you are getting is what I would expect.

For a macro to run off a timer, it must be reversible and will only run in reverse.

The Macro ability and associated manipulation of them are what (for me anyway) makes reef-pi so brilliant.

As we are developing use cases for the feature, we are going to come accross more and more of these "hiccups".

Yeah macros are great but still need some work, I like the suggestion forum as I was just going to bring this up.

 

[Ranjib]

Hey Ranjib

How about a teaser of what we could see in the final release of 4.0. ie what features are the team working to include??

I think we'll try our best to ship all the features in incremental way.. 3.x series. so 4.0 may not be a big bang release, except we'll introduce some breaking changes. that we dont want to do in 3.x series.
Feature wise you are looking at lot more drivers... things like shelly, DLI webpowerswitch pro on the powercontroller side, humidty sensors.. some kinda of sound based alerting (e.g. mp3 based, since we have a full blown audio capability thanks to pi, so we can do more than just buzzer), ability to customize UI theme and dashboard (its not in a good state in 3.0), ability to log custom parameters, mqtt integration (and in general improvements to allow more home automation in general), ability to run reef-pi as its own wifi hotspot (not wifi client), lots of stability improvements (validation, performance etc) are some of the things that we are working on.

You can get an idea of whats exactly being shipped here: https://github.com/reef-pi/reef-pi/projects/3

 

[Ranjib]

This "issue" ties in with my other posts regarding my challenges with Macros and running them off timers as well as macros running macros. I have been processing in my mind how a sensor triggering a macro would work and the response you are getting is what I would expect.

For a macro to run off a timer, it must be reversible and will only run in reverse.

The Macro ability and associated manipulation of them are what (for me anyway) makes reef-pi so brilliant.

As we are developing use cases for the feature, we are going to come accross more and more of these "hiccups".

Yes.. actually im also trying to find out the best user experience with macro. They are powerful and risky.
I dont sweat about the current state a lot , I know we have to use it and spend consistent effort to make it better, i.e. safer, more powerful and easier to predict. This will take some time.. but i think we'll get this sorted in couple of iterations, as we try to automate more and more complex workflows (water change, salt water mix, photo shoot etc ).

 

[LongBeachReefer562]

Hi @Michael Lane , having an issue setting up my power controller/reefpi gobi hat and was wondering if you had any input on where I screwed up :) board is pi zero

I'm using an SR8 switchpack and channels 7 & 8 arent working on the relay pack. Wasnt sure if the switchpack was bad so ordered a new one and getting the same issue. Below are the voltage readings from each pin in the on and off position.

Any idea what's going on here?

GPIO 08, 11, 25, 09, 24, & 10 - working perfect > off = 1.15v & on= .62v
GPIO 022 - relay stuck open > off = .80V & on = .18v
GPIO 23 - relay non-responsive > off = 1.22v & on=.78v

 

[Michael Lane]

Hi @Michael Lane , having an issue setting up my power controller/reefpi gobi hat and was wondering if you had any input on where I screwed up :) board is pi zero

I'm using an SR8 switchpack and channels 7 & 8 arent working on the relay pack. Wasnt sure if the switchpack was bad so ordered a new one and getting the same issue. Below are the voltage readings from each pin in the on and off position.

Any idea what's going on here?

GPIO 08, 11, 25, 09, 24, & 10 - working perfect > off = 1.15v & on= .62v
GPIO 022 - relay stuck open > off = .80V & on = .18v
GPIO 23 - relay non-responsive > off = 1.22v & on=.78v

It's suspicious that it's 2 pins right next to each other. Can you provide a picture and also show where you measured the voltages?

 

[NeonRabbit221B]

Alright hopefully this bug/issue is easier to resolve and the pH ezo board isn't toast... I rewired with a new non-isolated carrier board. I removed the flux from the solder joints. I found it at its usual address using i2cdetect and then after calibration I started getting this error

ERROR: Failed to json decode. Error: json: unsupported value: NaN

Any ideas?

 

[LongBeachReefer562]

It's suspicious that it's 2 pins right next to each other. Can you provide a picture and also show where you measured the voltages?

I thought it was odd as well. Attached are the pics, pin18 is good and what the other good pins read. 22 and 23 are the problematic ones.

Any ideas?

 

[tastyfish]

This may get lost in the noise, but has anyone outside the US found a decent hardware source for 240v? The Disco light plugbars referenced are 110v US plugs only and kind of wondering if anyone has found some proper voltage kit that will work. :)

 

[Des Westcott]

This may get lost in the noise, but has anyone outside the US found a decent hardware source for 240v? The Disco light plugbars referenced are 110v US plugs only and kind of wondering if anyone has found some proper voltage kit that will work. :)

I don't think so - at least not that I've seen. And I've been looking.

The two best options I see at the moment are

1. build using relay packs
2. WiFi plugs like the TP Link, Shelley units etc.

 

[tastyfish]

I don't think so - at least not that I've seen. And I've been looking.

The two best options I see at the moment are

1. build using relay packs
2. WiFi plugs like the TP Link, Shelley units etc.

Thanks Des, I thought this was the case, but always worth checking.

 

[Des Westcott]

Thanks Des, I thought this was the case, but always worth checking.

Keep looking though There might be an option out there.

 

[That Crusso Kid]

This may get lost in the noise, but has anyone outside the US found a decent hardware source for 240v? The Disco light plugbars referenced are 110v US plugs only and kind of wondering if anyone has found some proper voltage kit that will work. :)

I don't think so - at least not that I've seen. And I've been looking.

The two best options I see at the moment are

1. build using relay packs
2. WiFi plugs like the TP Link, Shelley units etc.

Have either of you tried looking on Aliexpress?

 

[elysics]

This may get lost in the noise, but has anyone outside the US found a decent hardware source for 240v? The Disco light plugbars referenced are 110v US plugs only and kind of wondering if anyone has found some proper voltage kit that will work. :)

There are the Gembird/Energenie SIS-PMS, EG-PMS, EG-PMS2 and so on, with different interfaces (usb, ethernet, wifi), i have one lying around and was planning to write a driver for the usb version but didn't get around to it with the current trouble.

 

[Matevz Savarin]

any idea why this doesnt work? I have 2 wavemakers both set on opposite timers.. pumps keep turning on and off randomly.. now they are both on, but one should be off..strange..