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

[Dave's Reef]

Thank you very much! I was also thinking about the jailbreak, but I don't know if that can fix.. I was able to try Firefox but I had the same issue... We have to find a way to install iOS10 :D

I was having a similar issue with mine what are you typing in to connect I had to type the IP address not the name of the pie and also no HTTP either just the IP only hopefully this helps you

 

[Ranjib]

Hello,
i would like to implement a contactless water sensor.
Do you think this model (DFRobot FIT0212 ) work with reefpi for the auto top off ?
Thanks

Non-contact_Liquid_Level_Switch_SKU_FIT0212-DFRobot

wiki:Non-contact Liquid Level Switch

wiki.dfrobot.com

I have not tried this, if it works like normal digital input then it should fine. Otherwise we have to do some software work

 

[Ranjib]

I have not tried this, if it works like normal digital input then it should fine. Otherwise we have to do some software work

I just looked at the specs , I think it will work . Let us know if you test this

 

[dmolavi]

What are the benefits of using something like the Digital Loggers Pro Switch with Reef-Pi? Does it take the place of something like the American DJ relay?

It's a "smart power switch" with a robust API and no reliance on any cloud services (so if the company goes under tomorrow, you can still use the remote functionality). I've been using one for several years and LOVE it. Well worth the money.

 

[lepetitnicolas]

I just looked at the specs , I think it will work . Let us know if you test this

OK ! thanks
I order the sensor right now.
I would give feedback as soon as I received it

 

[robsworld78]

Hello,
i would like to implement a contactless water sensor.
Do you think this model (DFRobot FIT0212 ) work with reefpi for the auto top off ?
Thanks

Non-contact_Liquid_Level_Switch_SKU_FIT0212-DFRobot

wiki:Non-contact Liquid Level Switch

wiki.dfrobot.com

Your set and that sensor looks good but here's another option that works for anyone else looking for something similar. There's a few versions, the V at the end of model is what you want. They go through thick glass and you can take the cap off and adjust the sensitivity.

XKC-Y25-T12V Non Contact Liquid Level Switch Stick Type Durable Water Level Sensor Module

Only US$7.49, buy best xkc-y25-t12v non contact liquid level switch stick type durable water level sensor module sale online store at wholesale price.

www.banggood.com

EDIT: Oops, almost forgot Pi is only 3.3v, the sensor I posted needs 5v and outputs 5v so could damage Pi pin.

Now I look at the other sensor it's 5v too so likely 5v comes out, make sure you check. If it does put out 5v you'll need to add a voltage divider which is 2 resistors, 4.7k and 9.1k.

 

[elysics]

So that filedriver was a huge help, finally got the energenie powerbar running without trying to learn how to write a usb driver, just added a cronjob that translates the file outputs to calls to the control program every 10 seconds. Not perfect, but it works. So that's another viable european powerbar option now.

Now that the heater/cooler display in the dashboard actually does something for me, is there some api stuff or other hack to manually change the temperature scale to a range useful for celsius? A search through this thread has brought up a few people complaining about this, but no solution.

 

[Schreiber]

Anyone able to shed some light on why I've had zero luck getting a temperature sensor to show up on this build?

1 wire is enabled

When I run ls in /sys/bus/w1/devices, I get the following output:
00-2e0000000000 00-4e0000000000 00-ce0000000000 w1_bus_master1

I unplugged the sensor, plugged in another & got this:

00-190000000000 00-690000000000 00-e90000000000 w1_bus_master1

Sometimes when I run ls, I only get the first 2 strings of numbers & the w1_bus_master1

I get the same ls output with or without the sensor plugged in. The numbers changing doesn't seem to follow any sort of pattern.

in the /sys/bus/wi/devices folder, I have 5 folders:

00-260000000000
00-660000000000
00-a60000000000
00-c60000000000
w1_bus_master1

I've eliminated as much complexity as possible. I'm going directly from the sensor to Pi pins (through a 4.7k resistor for data). Nothing else is plugged in.

Dev Mode is not enabled. No errors. I know at least one of the temperature sensors works, as I had it on my other build running just fine.

Checking the output at the pins, I've got 3.3V on the 3.3V pin, .245 Volts on GPIO 4, 0 volts on ground. Should I be seeing higher voltage on GPIO 4? Is that pin possibly dead?

I've been working on this for 3 days & I'm about to go insane. Anyone have some advice to keep me from going crazy?

 

[BenB]

Anyone able to shed some light on why I've had zero luck getting a temperature sensor to show up on this build?

1 wire is enabled

When I run ls in /sys/bus/w1/devices, I get the following output:
00-2e0000000000 00-4e0000000000 00-ce0000000000 w1_bus_master1

I unplugged the sensor, plugged in another & got this:

00-190000000000 00-690000000000 00-e90000000000 w1_bus_master1

Sometimes when I run ls, I only get the first 2 strings of numbers & the w1_bus_master1

I get the same ls output with or without the sensor plugged in. The numbers changing doesn't seem to follow any sort of pattern.

in the /sys/bus/wi/devices folder, I have 5 folders:

00-260000000000
00-660000000000
00-a60000000000
00-c60000000000
w1_bus_master1

I've eliminated as much complexity as possible. I'm going directly from the sensor to Pi pins (through a 4.7k resistor for data). Nothing else is plugged in.

Dev Mode is not enabled. No errors. I know at least one of the temperature sensors works, as I had it on my other build running just fine.

Checking the output at the pins, I've got 3.3V on the 3.3V pin, .245 Volts on GPIO 4, 0 volts on ground. Should I be seeing higher voltage on GPIO 4? Is that pin possibly dead?

I've been working on this for 3 days & I'm about to go insane. Anyone have some advice to keep me from going crazy?

You can use an other pin, see how to here:

1-WIRE at Raspberry Pi GPIO Pinout

Raspberry Pi One-Wire pins

pinout.xyz

 

[Schreiber]

You can use an other pin, see how to here:

1-WIRE at Raspberry Pi GPIO Pinout

Raspberry Pi One-Wire pins

pinout.xyz

Ohhh, neat. Didn't realize 1-wire was configurable. I had always assumed it was a dedicated pin, like I2C.

I'll give that a shot once my Pi is back up & running. I formatted it out of frustration, lol.

 

[Schreiber]

No luck, switching it to a GPIO pin I'm sure is working didn't work either.

If it's any help knowing, after formatting, these are the 3 folders I have in /sys/bus/w1/devices after formatting:

00-40000000000
00-80000000000
w1_bus_master1

and I get this output when running ls:

00-20000000000 00-c0000000000 w1_bus_master1

Every time I feel like I know what I'm doing, something more & more unusual pops up. I'm naming a few gray hairs on my head after @Ranjib :p Kidding, I'm sure it's something dumb I'm doing, but I can't figure it out for the life of me. I've tried on 3.2 & 3.4 with different temperature sensors & different Pis with no luck so far.

 

[Schreiber]

Ugh, most frustrating victory lap ever. I got it working.... but still have no idea what the issue was.

I had the temperature screen up, checked to see if there was a sensor (there wasn't).

I unplugged it & flipped its wires- Gnd was hooked to 3.3v, 3.3V to Gnd. No sensor detected.

I flipped it back.... sensor detected.

I'm at a loss. I'm just happy my 3 day battle is won!

 

[Ranjib]

So that filedriver was a huge help, finally got the energenie powerbar running without trying to learn how to write a usb driver, just added a cronjob that translates the file outputs to calls to the control program every 10 seconds. Not perfect, but it works. So that's another viable european powerbar option now.

Now that the heater/cooler display in the dashboard actually does something for me, is there some api stuff or other hack to manually change the temperature scale to a range useful for celsius? A search through this thread has brought up a few people complaining about this, but no solution.

set it up again with Celsius as unit from very beginning.

 

[elysics]

set it up again with Celsius as unit from very beginning.

Do i have to set Celsius somewhere else too or only when setting up a temperature sensor? Because i have always immediately set it to celsius. Just redid it anyway, by deleting the sensor and setting it up again filling in all the fields, but the scale still goes to 86.

 

[Des Westcott]

I've just updated to reef-pi ver3.4. Update went OK. Download was very slow. Like VERY slow, but it downloaded and installed.

All looked fine until I went to the dashboard. Graphs were there, but when I mouse-over them, all the date and time info is "Jan-01-00:00, 0001" For temp, pH, ATO. All the reading are there, just date stamps are gone / reset.
Reloaded reef-pi and refreshed browser - Same thing.
Rebooted reef-pi and refreshed browser - Same thing.

My latest readings are showing with the correct time / date so all good.

 

[peejay]

I have updated to 3.4. Now, on the Dashboard my equipment no longer shows in red when they are turned off. They appear in green when they switch on. Was this a deliberate move, a bug or just something gone wrong my end
?
Thanks.

 

[Ranjib]

I have updated to 3.4. Now, on the Dashboard my equipment no longer shows in red when they are turned off. They appear in green when they switch on. Was this a deliberate move, a bug or just something gone wrong my end
?
Thanks.

That’s not a deliberate move. We updated the charting library to address some deprecation warning, I’ll cross check .

 

[Ranjib]

I've just updated to reef-pi ver3.4. Update went OK. Download was very slow. Like VERY slow, but it downloaded and installed.

All looked fine until I went to the dashboard. Graphs were there, but when I mouse-over them, all the date and time info is "Jan-01-00:00, 0001" For temp, pH, ATO. All the reading are there, just date stamps are gone / reset.
Reloaded reef-pi and refreshed browser - Same thing.
Rebooted reef-pi and refreshed browser - Same thing.

My latest readings are showing with the correct time / date so all good.

Oops . I know what happened. We fixed a bug a that was messing up the charts due to missing year in time stamp. That is causing all older timestamp parsing to fail resulting in default timestamp (which is Jan 1 ,01). I fear this is permanent. I can revert back the change, but then we’ll get the old bug back. This should not impact anything other than the timestamps in chart, for older usage data.

 

[peejay]

That’s not a deliberate move. We updated the charting library to address some deprecation warning, I’ll cross check .

Appreciated.

 

[Des Westcott]

Oops . I know what happened. We fixed a bug a that was messing up the charts due to missing year in time stamp. That is causing all older timestamp parsing to fail resulting in default timestamp (which is Jan 1 ,01). I fear this is permanent. I can revert back the change, but then we’ll get the old bug back. This should not impact anything other than the timestamps in chart, for older usage data.

Cool. It's largely benign, because I can still see the graph visually, and I still have the point data, just not the dates. And going forward it's fine. In a couple of weeks I won't even remember it happened. Glad I could point out something for you Devs to fix. We all know you sit around bored with nothing to do most of the time :D:D:D Just kidding. Constantly grateful for the work you guys do.