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

[dmolavi]

I should be available to begin testing on the wireless plugs in a month or so. Is that a functionality I can implement on my end, or will it require extensive work in the CLI?

I have 4 spare TPLink plugs that I can test on...

 

[DirtDiggler2823]

I have 4 spare TPLink plugs that I can test on...

Other than the hardware, what changes are required in the reef-pi?

 

[DirtDiggler2823]

The pH probe is doing well. I do get this error almost daily though: ph subsystem: Failed read probe:Pico-pHError:write /dev/i2c-1: remote I/O error

 

[DirtDiggler2823]

Noticed the resources getting used up pretty quickly recently, and when I went to log into the reef-pi, the UI was missing a lot of items. I went to reboot, and that action was delayed by about 10 seconds. I have the pH probe polling at 90 second intervals. Is that too frequent? Should I change it to hourly, or every 30 minutes?

 

[Ranjib]

Noticed the resources getting used up pretty quickly recently, and when I went to log into the reef-pi, the UI was missing a lot of items. I went to reboot, and that action was delayed by about 10 seconds. I have the pH probe polling at 90 second intervals. Is that too frequent? Should I change it to hourly, or every 30 minutes?

We have to cross check if the culprit is reef-pi or something else running on pi. Assuming its reef-pi, I am noticing 20% memory usage increase in past 10 days. Is that assessment correct? Can you share some details around what all you have configured on the reef-pi? I can then reproduce and fix the issue. I am specifically looking at timer, lights, ato, temp controller, ph etc.

 

[Ranjib]

I have 4 spare TPLink plugs that I can test on...

WHich model? The current driver only supports hs1* series with single outlets

 

[Ranjib]

Other than the hardware, what changes are required in the reef-pi?

You need to execute a command to create the tplink driver using API (similar to ph calibration), thats all, then you can create outlet using that driver and associate it with an equipment using the normal UI

 

[Ranjib]

Browser that is build in to raspbian, and Chrome for android.

The log was empty but that can be because i reset the database, i will try Again.

This is still an issue?

 

[dmolavi]

WHich model? The current driver only supports hs1* series with single outlets

HS105

 

[dmolavi]

You need to execute a command to create the tplink driver using API (similar to ph calibration), thats all, then you can create outlet using that driver and associate it with an equipment using the normal UI

what command is used to create the driver?

 

[Bigtrout]

I have 3.0 and use chrome exclusively to access...3 temp sensors, 2 heater controllers ph board all reading at 60 seconds...8 outlets and 2 macros and 4 lighting pca9685 channels...steady 8 percent mem usage

 

[BenB]

This is still an issue?

Here are the logs:

It looks like a PCA9685 needs to be connected when enabling the PCA9685 option. Only then I do not expect that reef pi does not start, rather gives an error.
Can someone try the same? I have nothing connected to the PI, running 2.4 with raspbian 4.14. From a blank install just enable the "PCA9685" update and reboot.
Deleting the database afterward brings you back to a functioning reef-pi, Thanks!!

 

[Ranjib]

what command is used to create the driver?

create a file with following data (kasa.json) . Type "hs1xx" is important, this tells reef-pi that its a kasa smartplug. Change the SMART_PLUG_IP with your smar plug's IP (check your router or kasa app to get the ip ).

{"name":"KasaTest","type":"hs1xx","config":{"address":"SMART_PLUG_IP:9999"}}

Then use reef-pi api to create a new driver. Use appropriate reef-pi ip. You'll need to create the cookie.txt file using auth/signin api. if its there, it can be reused.

curl -X PUT -d @kasa.json  http://REEF_PI_IP/api/drivers -b cookie.txt

After this you should see a new driver name kasa is visible in Configuration -> Drivers section. You can go to connectors and create outlet and associate the new driver from UI . Let me know how it goes . I was ecstatic to see this working :-)

 

[Ranjib]

Here are the logs:

It looks like a PCA9685 needs to be connected when enabling the PCA9685 option. Only then I do not expect that reef pi does not start, rather gives an error.
Can someone try the same? I have nothing connected to the PI, running 2.4 with raspbian 4.14. From a blank install just enable the "PCA9685" update and reboot.
Deleting the database afterward brings you back to a functioning reef-pi, Thanks!!

this is a bug. :-( . We'll have to fix it.

 

[Ranjib]

create a file with following data (kasa.json) . Type "hs1xx" is important, this tells reef-pi that its a kasa smartplug. Change the SMART_PLUG_IP with your smar plug's IP (check your router or kasa app to get the ip ).

{"name":"KasaTest","type":"hs1xx","config":{"address":"SMART_PLUG_IP:9999"}}

Then use reef-pi api to create a new driver. Use appropriate reef-pi ip. You'll need to create the cookie.txt file using auth/signin api. if its there, it can be reused.

curl -X PUT -d @kasa.json  http://REEF_PI_IP/api/drivers -b cookie.txt

After this you should see a new driver name kasa is visible in Configuration -> Drivers section. You can go to connectors and create outlet and associate the new driver from UI . Let me know how it goes . I was ecstatic to see this working :)

I just noticed this driver support was landed soon after the 3.0 alpha prerelease, so this is not present in rhat release. Are you building from master? If not, you have to wait till I cut a new release of build from master.

 

[dmolavi]

I just noticed this driver support was landed soon after the 3.0 alpha prerelease, so this is not present in rhat release. Are you building from master? If not, you have to wait till I cut a new release of build from master.

I'm building from source. I'll test later today.

 

[Bigtrout]

The really great thing about the tplink driver, or reef pi supporting a good smart plug, is that it eliminates having non technical people having to wire up something to control MAINS(120v or 240v) power. Issues with safety(UL listings and such) are taken off the table if well made UL listed devices are used for the AC side of things.

 

[Ranjib]

The really great thing about the tplink driver, or reef pi supporting a good smart plug, is that it eliminates having non technical people having to wire up something to control MAINS(120v or 240v) power. Issues with safety(UL listings and such) are taken off the table if well made UL listed devices are used for the AC side of things.

I must say I also like the less wire aspect of it :-) . The dependency on WiFi is a concern though.

 

[dmolavi]

if i'm developing my own driver, where should i put the source code in my local repo? any time i try to add it with a command similar to yours above, i get an error about an unknown driver type.

 

[dmolavi]

i should add to my above post that i've updated factories.go to include my driver directory, and placed it in it's own directory in /gospace/pkg/dep/sources/https---github.com-reef--pi-drivers/ and did a make clean and make start-dev...but still no joy.