Data Input API

[Indoor Reef]

Is there a way to input pH and temperature data into the reef pi via an API? I would like to input the data coming from my Seneye SUD.

 

[attiland]

Is there a way to input pH and temperature data into the reef pi via an API? I would like to input the data coming from my Seneye SUD.

File input is your option.

 

[Indoor Reef]

File input is your option.

Thanks. Do you know where the documentation of this feature is? I'm struggling to find things, typically having to read the source code instead.

 

[Indoor Reef]

I just wanted to share that I've found this discussion which seems to show how to load the analog input data from a file...
Thread 'Displaying Seneye in Reef-Pi' https://www.reef2reef.com/threads/displaying-seneye-in-reef-pi.836074/

I'm going to try it now but looks like it should work. Still interested to know where the official docs are for the analog input features.

The way I'm loading the data is a little different to the discussion above since I'm loading the data from the SUD direct to the raspberry Pi. I can share after incase its helpful for anyone else.

 

[TCoach]

I just wanted to share that I've found this discussion which seems to show how to load the analog input data from a file...
Thread 'Displaying Seneye in Reef-Pi' https://www.reef2reef.com/threads/displaying-seneye-in-reef-pi.836074/

I'm going to try it now but looks like it should work. Still interested to know where the official docs are for the analog input features.

The way I'm loading the data is a little different to the discussion above since I'm loading the data from the SUD direct to the raspberry Pi. I can share after incase its helpful for anyone else.

That’s my code. Still running it today. My research into reading directly from the SUD is not easy. So, for now it is just a file-analog input to reef-pi.

if you are able to make this work, I’d be very interested in hearing.

 

[Indoor Reef]

That’s my code. Still running it today. My research into reading directly from the SUD is not easy. So, for now it is just a file-analog input to reef-pi.

if you are able to make this work, I’d be very interested in hearing.

Thanks for sharing! I've got the reading from the SUD already. You can output in machine readable format too.

I can't take any credit for it but this is what I've used...

GitHub - berarma/sudmon: Command line monitor and library for Seneye USB devices

Command line monitor and library for Seneye USB devices - berarma/sudmon

github.com

Might work for you too!

My problem at the moment is that I can't view the connectors tab.

Wondering if it might be due to using a Model 2011.12 raspberry pi!!! You don't know where is best to edit the config for the hardware do you?

If I can't get it working then I'll probably just write the data to a google sheets or something instead. Got no other hardware at the moment so not a big issue.

 

[TCoach]

@Ranjib Any ideas on his UI issue?

 

[Ranjib]

@Ranjib Any ideas on his UI issue?

I think you have either deleted a driver without deleting its connector or some thing on that line. i.e. reef-pi database is now inconsistent state. If its a new installation reset database and start over.
We have to do a better job at warning users when the delete drivers (to delete the associated connector first), sorry about this

 

[Indoor Reef]

Thanks for the advice. I had followed the guidance to reset the database in the troubleshooting docs but this didn't help. I'm not sure this ever worked for me to be fair as of when I first set it up. Could it be that I'm running on a very old pi model (2011.12) that's causing this? Ive seen some threads about compatibility issues with older pi models.

 

[Ranjib]

Thanks for the advice. I had followed the guidance to reset the database in the troubleshooting docs but this didn't help. I'm not sure this ever worked for me to be fair as of when I first set it up. Could it be that I'm running on a very old pi model (2011.12) that's causing this? Ive seen some threads about compatibility issues with older pi models.

If this is a bug i am able to reproduce, then i can fix it. Pi model should not matter as long as it 40 pin, (pi model b, 2, 3,4, A, zero). The error is about a missing driver, hence im bit surprised to know that it never worked from beginning. Is it a pi with 26 pin? that would explain it..

 

[Indoor Reef]

If this is a bug i am able to reproduce, then i can fix it. Pi model should not matter as long as it 40 pin, (pi model b, 2, 3,4, A, zero). The error is about a missing driver, hence im bit surprised to know that it never worked from beginning. Is it a pi with 26 pin? that would explain it..

26pin. Is this completely incompatible or do I need to rebuild for different hardware?

 

[Ranjib]

26pin. Is this completely incompatible or do I need to rebuild for different hardware?

Yeah It’s not compatible. Rebuilding will not solve the problem. we have to add the pin map for this older revisions in the code,

 

[Indoor Reef]

Yeah It’s not compatible. Rebuilding will not solve the problem. we have to add the pin map for this older revisions in the code,

Thanks for confirming. Is that the only dependency that you know of to get it to run on the older pi? From what I can see this looks to be the forked embd repo, right? I looked where the base addresses are detected in the rpi repo and looking like it would be fine.

 

[Ranjib]

Thanks for confirming. Is that the only dependency that you know of to get it to run on the older pi? From what I can see this looks to be the forked embd repo, right? I looked where the base addresses are detected in the rpi repo and looking like it would be fine.

No idea, since I have not tested it, there could be lot more. We are not using forked embd, it’s consumed from master.