dmolavi
Well-Known Member
HS105
reef-pi :: An opensource reef tank controller based on Raspberry Pi.
- Thread starter Ranjib
- Start date
-
- Tags
- controller raspberry-pi
- Tagged users Ranjib
dmolavi
Well-Known Member
what command is used to create the driver?
- Joined
- Dec 16, 2018
- Messages
- 1,189
- Reaction score
- 2,826
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
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!!
OP
OP
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 ).
Code:
{"name":"KasaTest","type":"hs1xx","config":{"address":"SMART_PLUG_IP:9999"}}
Code:
curl -X PUT -d @kasa.json http://REEF_PI_IP/api/drivers -b cookie.txt
OP
OP
this is a bug. :-( . We'll have to fix it.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!!
OP
OP
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.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 ).
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.Code:{"name":"KasaTest","type":"hs1xx","config":{"address":"SMART_PLUG_IP:9999"}}
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 workingCode:curl -X PUT -d @kasa.json http://REEF_PI_IP/api/drivers -b cookie.txt
dmolavi
Well-Known Member
I'm building from source. I'll test later today.
- Joined
- Dec 16, 2018
- Messages
- 1,189
- Reaction score
- 2,826
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.
OP
OP
I must say I also like the less wire aspect of it
. The dependency on WiFi is a concern though.
dmolavi
Well-Known Member
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
Well-Known Member
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.
- Joined
- Dec 16, 2018
- Messages
- 1,189
- Reaction score
- 2,826
Well the pi depends on wifi. I have a few cheap etekcity esp8266 based outlets and I have to say they dont give me a problem.I must say I also like the less wire aspect of it
OP
OP
you can develop your driver code in someplace inside the reef-pi repo itself (not in reef-pi/driver), and wire it up in here . Once its tested with your physical setup, copy the driver code in reef-pi/drivers, unit test it and raise a PR against reef-pi/drivers. You can refer to your pr branc of reef-pi/drivers that has your code in reef-pi controller repo under Gopkg.toml . Currently it points to master, change it to your remote branch and test again. Let me know if you need any help
OP
OP
Did the existing hs1xxx driver worked?
OP
OP
You have to update the Gopkg.toml and run dep ensure -update github.com/reef-pi/drivers etc.. dont take that route right now. Just keep the code inside reef-pi controller repo and hook it up in the factory as i mentioned before
DirtDiggler2823
If I can't break it, it doesn't exist
It's been almost 24 hours, and my resources are getting chewed up. I'm not running a lot from this box, but since the pH probe went online, it's been a problem. Anything else I can provide to help with this?
dmolavi
Well-Known Member
I added it to my factories.go....so i need to push to my clone and point to that? Before i test w/ my physical setup?
OP
OP
No... this should be enough to test it at your end
dmolavi
Well-Known Member
do i need to do an import here?
Edit: basically, i've got my foo.go and foo_hal.go files. Where do I need to put them, and what import change do i make to factories.go? I added the case to the switch statement, still no luck...
Edit 2: i'm missing something basic here. i changed the 'hs1xx' to 'hs1xx123' but didn't change the json file and it still got added, even after a fresh make start-dev. do i need to do something else to get the factories.go changes to kick in?
Last edited:
Similar threads
- Shipping Available
