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

[Ranjib]

With the latest pre-release, my temp probe disappears--Is there a log file I can access to see what is causing this to happen?

Check if the sensor is detected by raspbian/linux. If thats the case then this is not related to reef-pi upgrades.

ls /sys/bus/w1/devices

 

[mk1scott]

Thank you sir. I'll run that code this evening and report back.

 

[Bigtrout]

Check if the sensor is detected by raspbian/linux. If thats the case then this is not related to reef-pi upgrades.

ls /sys/bus/w1/devices

@Ranjib
I have loaded reef pi 3.0 rc1 and have a weird behavior with temp sensors. First off this is being tested on my bullet proof build that was happily running the 3.0 alpha release for months.
Upgrading from 3.0 alpha i had some temp sensors missing so I deleted them all and remade the sensors. All is good and they happily work.
Upon a reload of reef pi a temp sensor will randomly be missing once it reloads. If you delete and remake that sensor it works fine until you do another reef pi reload. I can see all sensors when ssh into pi and issue the command to see them on the onewire bus.

In short:
Sensors created and work fine but upon reef pi reload they will randomly quit working. After deleting and recreating the sensor it will again work fine until a reef pi reload.

This is definitely reef pi software related as going back to 3.0 alpha everything works.

The lighting in reef pi 3.0rc1 seems to be working !

 

[Bigtrout]

@Ranjib
I have loaded reef pi 3.0 rc1 and have a weird behavior with temp sensors. First off this is being tested on my bullet proof build that was happily running the 3.0 alpha release for months.
Upgrading from 3.0 alpha i had some temp sensors missing so I deleted them all and remade the sensors. All is good and they happily work.
Upon a reload of reef pi a temp sensor will randomly be missing once it reloads. If you delete and remake that sensor it works fine until you do another reef pi reload or reboot. I can see all sensors when ssh into pi and issue the command to see them on the onewire bus.

In short:
Sensors created and work fine but upon reef pi reload they will randomly quit working. After deleting and recreating the sensor it will again work fine until a reef pi reload/reboot

 

[Ranjib]

@Ranjib
I have loaded reef pi 3.0 rc1 and have a weird behavior with temp sensors. First off this is being tested on my bullet proof build that was happily running the 3.0 alpha release for months.
Upgrading from 3.0 alpha i had some temp sensors missing so I deleted them all and remade the sensors. All is good and they happily work.
Upon a reload of reef pi a temp sensor will randomly be missing once it reloads. If you delete and remake that sensor it works fine until you do another reef pi reload. I can see all sensors when ssh into pi and issue the command to see them on the onewire bus.

In short:
Sensors created and work fine but upon reef pi reload they will randomly quit working. After deleting and recreating the sensor it will again work fine until a reef pi reload.

This is definitely reef pi software related as going back to 3.0 alpha everything works.

The lighting in reef pi 3.0rc1 seems to be working !

Thank you for the detailed response. Let me run through some tests. We'll not ship 3.0 with such bugs,

 

[Ranjib]

@Ranjib
I have loaded reef pi 3.0 rc1 and have a weird behavior with temp sensors. First off this is being tested on my bullet proof build that was happily running the 3.0 alpha release for months.
Upgrading from 3.0 alpha i had some temp sensors missing so I deleted them all and remade the sensors. All is good and they happily work.
Upon a reload of reef pi a temp sensor will randomly be missing once it reloads. If you delete and remake that sensor it works fine until you do another reef pi reload. I can see all sensors when ssh into pi and issue the command to see them on the onewire bus.

In short:
Sensors created and work fine but upon reef pi reload they will randomly quit working. After deleting and recreating the sensor it will again work fine until a reef pi reload.

This is definitely reef pi software related as going back to 3.0 alpha everything works.

The lighting in reef pi 3.0rc1 seems to be working !

By reload you mean just reef-pi reload, no reboot right?

 

[Bigtrout]

By reload you mean just reef-pi reload, no reboot right?

It happens on both a reload or a reboot

I also noticed that when i would just create a temp sensor, if i tried to create a temp controller controlling equipment it wouldnt save...it wouls tell me there were validation errors. If i controlled nothing and just created a temp sensor it would save it(pending a reload or reboot).
If it helps, one sensor out of my 3 would always survive a reboot or reload...

 

[Bigtrout]

It happens on both a reload or a reboot

I also noticed that when i would just create a temp sensor, if i tried to create a temp controller controlling equipment it wouldnt save...it wouls tell me there were validation errors. If i controlled nothing and just created a temp sensor it would save it(pending a reload or reboot).
If it helps, one sensor out of my 3 would always survive a reboot or reload...

This is repeatable even on a clean reef pi load meaning deleting my database and loading 3.0rc1. Creating nothing except my 3 temp sensors, on a reboot or a reload only one sensor survives.

On a side note im getting pretty good with linux commands :) as long as you save your database its easy to get back to 3.0 alpha and running again!

 

[brandon clow]

I am also reporting success with the lighting portion on reef-pi-3.0.0-rc1-pi3.deb. Great work!

 

[brandon clow]

I want to also note that bug 794 is no longer present in this build. This is excellent news.

 

[AbjectMaelstroM]

Hopefully we can figure out the temp probe issue, otherwise it seems 3.0 is nearly there. Unfortunately, I didn't get the chance play with the new RC due to work. Hopefully I'll have more time this weekend, maybe the stable release will be out (not trying to rush it, as I'd rather have it "right" rather than "sooner").

Keep up the fantastic work and as always, thank you for what you guys do.

 

[mk1scott]

No luck with the original temp sensor. Ran the code, returned nothing. Figured I must have tugged on a wire while moving things around over the weekend.

Plugged in a dual probe I had laying around for a different project, boom, detected both temp sensors. Assigned them in reef pi (rc01). One works while the other doesn't (both worked in a prior iteration of reef pi). Ran "ls /sys/bus/w1/devices" and detects both sensors.

Edit. Deleted the "bad" sensor. Then recreated it but disabled it before saving. It picked up a temp reading in the calibration mode so I then enabled the sensor and it is currently working.

Both temp sensors are running.

 

[Bigtrout]

No luck with the original temp sensor. Ran the code, returned nothing. Figured I must have tugged on a wire while moving things around over the weekend.

Plugged in a dual probe I had laying around for a different project, boom, detected both temp sensors. Assigned them in reef pi (rc01). One works while the other doesn't (both worked in a prior iteration of reef pi). Ran "ls /sys/bus/w1/devices" and detects both sensors.

Edit. Deleted the "bad" sensor. Then recreated it but disabled it before saving. It picked up a temp reading in the calibration mode so I then enabled the sensor and it is currently working.

Both temp sensors are running.

I bet if you do a reload you lose a sensor.

 

[b4tn]

Just finished my upgrade from 2.4 to 3.0. Love the new features that have been added since 2.x! So far everything is up and running and working with some minor work arounds.

- I am getting the same temp sensor issue. On reboot one of my two temp sensors is no longer recognized. It’s there but is removed from the dashboard. Deleting it and re adding seems to fix it until I reboot again

- this is minor and took some experimenting but I have to select a chiller threshhold in order to enable temp control. Otherwise it will not save

- PCA 9865 driver address defaults to 68. Doing some searching looks like the default address is actually 64

- a minor annoyance I was hoping would get fixed is the dashboard errors when an action has not been completed yet. I have doser on the dashboard that are not scheduled to run till tomorrow at 8 pm so two errors will pop up every time I go to the dash board till it runs tomorrow at 8pm

@Ranjib You all have really outdone yourself with all the work put into this. Thanks for keeping my reef running :)

 

[Des Westcott]

Just a small annoyance which would be nice if it could be addressed. When the Temp probes go AWOL, I get the pink bars, which I understand from Ranjib's explanations are benign, but the problem is that they cover up the controls for the buttons on the right (Calibrate, Edit Delete) and unless you can get to the very bottom one in the list, you can't click the "X" to get rid of them, so you can't access the Macro's, Timers or anything.

Or do I have something wrong again? :)

 

[mk1scott]

I bet if you do a reload you lose a sensor.

Both ran through the night just fine. I'll do a reload this evening and report what happens.

 

[brandon clow]

Interesting note on the latest build (rc1). The timer working on all prior builds now are no longer functioning. I get an error of {"error":"Failed to update. Error: Cron ID not found for job ID:9"} | HTTP 500. The last working state was on build 3.0 alpha, I noticed the new fields but no matter what I change this does not rectify the existing timers.

I did observe making a new timer duplicating the exact configuration of the non functioning timer saves and functions without error. Perhaps a link is lost between the two builds when adding the additional time format? While I was able to rectify this I figured this might be worth sharing.

 

[sfgabe]

I am also reporting success with the lighting portion on reef-pi-3.0.0-rc1-pi3.deb. Great work!

Same here, all looks good so far! Thank you again reef-pi team!

+1 on those pop up error messages though, I've accidentally deleted equipment trying to close those boxes on small screens. Perhaps it could just go in the "error" tab? Or have a setting option to hide them altogether?

Here's some new frags from the Manhattan Frag Swap last weekend and a grumpy clown enjoying the new light.

 

[Ranjib]

Interesting note on the latest build (rc1). The timer working on all prior builds now are no longer functioning. I get an error of {"error":"Failed to update. Error: Cron ID not found for job ID:9"} | HTTP 500. The last working state was on build 3.0 alpha, I noticed the new fields but no matter what I change this does not rectify the existing timers.

I did observe making a new timer duplicating the exact configuration of the non functioning timer saves and functions without error. Perhaps a link is lost between the two builds when adding the additional time format? While I was able to rectify this I figured this might be worth sharing.

Yes, we added the ability to specify weekdays (day alternate Wednesday) in timer specification. And as a side effect the old timers will need to be updated for this new format. I’ll keep in mind and call this out in the doc

 

[Mike Kearns]

I too had the pink bars down the side of my screen. I had an optical sensor enabled but forgot to plug it back in. Once I did that, I hit the reload button on my browser (not the reload in reef-pi) and they were gone.