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

[Ranjib]

Ranjib, thank you for your support... I decided to reset the database and configure reef-pi again... I'm lucky because I have few settings to arrange.

I have installed the update (btw... thank you very much for what you and your staff are doing for everyone).

I see a new feauture (MQTT based metric emission)... how can I send data (in partucular temperature and ph data) to home assistant (I have installed mosquitto on my Home Assistant docker)?

Just add mqtt server details (hostort) and reef-pi will emit all the metrics to mqtt. Including ph, temperature, equipment state etc. name of the topic will be deduced from name (e.g. ph_reading). I am not knowledgeable for home assistant integration part , may be @sfgabe or someone who is using it can chime in. This is the required first step for mqtt integration , we are likely to have more features in future around mqtt

 

[ChrisNH]

Hive minds,
I have just cut 4.0 release.

I installed the new version and it seems to work thus far. However it did not change the behavior of the temp and ph graphs on the display in regards to the displayed range. Should it have? I thought that was part of the new version.

 

[AbjectMaelstroM]

Just add mqtt server details (hostort) and reef-pi will emit all the metrics to mqtt. Including ph, temperature, equipment state etc. name of the topic will be deduced from name (e.g. ph_reading). I am not knowledgeable for home assistant integration part , may be @sfgabe or someone who is using it can chime in. This is the required first step for mqtt integration , we are likely to have more features in future around mqtt

This is awesome. Can't wait to plug it into HASS.

 

[sfgabe]

Just add mqtt server details (hostort) and reef-pi will emit all the metrics to mqtt. Including ph, temperature, equipment state etc. name of the topic will be deduced from name (e.g. ph_reading). I am not knowledgeable for home assistant integration part , may be @sfgabe or someone who is using it can chime in. This is the required first step for mqtt integration , we are likely to have more features in future around mqtt

I'm excited about this new development @Ranjib ! I need to update to the latest version, but using MQTT instead should take care of the expired cookies that I need to manually refresh every so often with the API method.

As for @Freccialata 's question - I currently use the reef-pi API so I don't have any direct knowledge of the new MQTT setup. In Home Assistant, you'll need to make sure you have an MQTT host set up (check the HASS docs for that), and that reef-pi is pointing to that as the MQTT host. Once that's up and running you should be able to test the reef-pi integration by going into the HASS MQTT integration and "listening" to the topic - it should be something like /reef-pi/ph_reading/ . After you see that that returns a value, you can use that as an mqtt sensor as defined in the hass docs.

@Ranjib is there a doc that has the possible topic addresses? (apologies if it's somewhere in the previous thread, feel free to link)

 

[Ranjib]

I'm excited about this new development @Ranjib ! I need to update to the latest version, but using MQTT instead should take care of the expired cookies that I need to manually refresh every so often with the API method.

As for @Freccialata 's question - I currently use the reef-pi API so I don't have any direct knowledge of the new MQTT setup. In Home Assistant, you'll need to make sure you have an MQTT host set up (check the HASS docs for that), and that reef-pi is pointing to that as the MQTT host. Once that's up and running you should be able to test the reef-pi integration by going into the HASS MQTT integration and "listening" to the topic - it should be something like /reef-pi/ph_reading/ . After you see that that returns a value, you can use that as an mqtt sensor as defined in the hass docs.

@Ranjib is there a doc that has the possible topic addresses? (apologies if it's somewhere in the previous thread, feel free to link)

Not yet. the topic is same as prometheus metric name. generally in the form of "name_reading" . you can get an idea here: https://github.com/reef-pi/reef-pi/search?q=EmitMetric , i plan to add details in the docs soon.

 

[Ranjib]

I installed the new version and it seems to work thus far. However it did not change the behavior of the temp and ph graphs on the display in regards to the displayed range. Should it have? I thought that was part of the new version.

Yes, there is no fix shipped for that specific issue. I started working on a prototype.. but its not shippable yet. I want to tackle this issue though, and not drop the ball.

 

[Freccialata]

I'm excited about this new development @Ranjib ! I need to update to the latest version, but using MQTT instead should take care of the expired cookies that I need to manually refresh every so often with the API method.

As for @Freccialata 's question - I currently use the reef-pi API so I don't have any direct knowledge of the new MQTT setup. In Home Assistant, you'll need to make sure you have an MQTT host set up (check the HASS docs for that), and that reef-pi is pointing to that as the MQTT host. Once that's up and running you should be able to test the reef-pi integration by going into the HASS MQTT integration and "listening" to the topic - it should be something like /reef-pi/ph_reading/ . After you see that that returns a value, you can use that as an mqtt sensor as defined in the hass docs.

@Ranjib is there a doc that has the possible topic addresses? (apologies if it's somewhere in the previous thread, feel free to link)

Thank you @Ranjib and @sfgabe.

I'm still a noob in reef-pi and home assistant... However the real problem is that I'm not a developer.

I have setup in the telemetry board the setting and I don't have kind of error in the errors board, it means that everything is fine (wrong address, wrong username and/or wrong password shows an error)... but I can't see any new identity in the mqtt integration.

I will ask for support to a friend that is a home assistant expert.

@sfgabe : I read some your articles on the net and in this forum too.... but at the moment it's very hard for me to understand and work with API.

I see that someone else is interested in reef-pi integration in home assistant... lets hope that with the mqtt integration in reef-pi the interest gres up and so that we can create a specific thread to make it easyer.

 

[borillion]

So I see Kasa is supported, any ideas about supporting sonoff (ewelink) or Smart Life (Tuya) outlets? I know that some of the sonoff devices have a local lan mode that might be able to give us a way into those.

 

[borillion]

Is there a user contributable wiki we can put information into anywhere?

 

[Ranjib]

So I see Kasa is supported, any ideas about supporting sonoff (ewelink) or Smart Life (Tuya) outlets? I know that some of the sonoff devices have a local lan mode that might be able to give us a way into those.

Shelly drivers are already in. Sonoff not yet

 

[borillion]

I found some code, I will mess it and the standalone demos. See what happens.
Looks like the Tuya and Shelly are compatible. Awesome.

Shelly drivers are already in. Sonoff not yet

 

[Ranjib]

Is there a user contributable wiki we can put information into anywhere?

The official reef-pi website is open source as well and available at reef-pi/website repository . You can add docs there as pr

 

[robsworld78]

Great job @Ranjib, I'm excited for dosing pump control from macro.

 

[sfgabe]

Thank you @Ranjib and @sfgabe.

I'm still a noob in reef-pi and home assistant... However the real problem is that I'm not a developer.

I have setup in the telemetry board the setting and I don't have kind of error in the errors board, it means that everything is fine (wrong address, wrong username and/or wrong password shows an error)... but I can't see any new identity in the mqtt integration.

I will ask for support to a friend that is a home assistant expert.

@sfgabe : I read some your articles on the net and in this forum too.... but at the moment it's very hard for me to understand and work with API.

I see that someone else is interested in reef-pi integration in home assistant... lets hope that with the mqtt integration in reef-pi the interest gres up and so that we can create a specific thread to make it easyer.

Glad I could help confuse you.
I'll update my build thread with MQTT info when I update my reef-pi installations.

 

[Ranjib]

Alrighty, 4.0 release announcement thread is out: https://www.reef2reef.com/threads/reef-pi-4-0-release-announcements.778804 , if you are running reef-pi 4.0, would really appreciate if you share pic of dashboard or build
thank you everyone. I want to take the time and thank all of you for your continued interest in this project, being involved in this thread and make the reef-pi community that means everything to this project.

happy thanksgiving

 

[Yov]

@Ranjib and Team great job again! thanks to all for this fine product and al the effort you put in it! I wi lupgrade in the comming weekend as i like to keep an eye on things if anything changes! Is there a fix for the Macro-Timer issue ? If so i need to change the macro's again and i need to know so my Terrarium does not overflow again!

 

[Des Westcott]

Awesome @Ranjib

I have updated and all went well. I tried out the export db feature in UI and that worked great!

I haven't tried out the Macro stuff yet. Was the issue with Macro's only activating in reverse via Timers and other Macro's ever addressed? And Activating Macros via ATO trigger?

 

[AbjectMaelstroM]

Awesome @Ranjib

I have updated and all went well. I tried out the export db feature in UI and that worked great!

I haven't tried out the Macro stuff yet. Was the issue with Macro's only activating in reverse via Timers and other Macro's ever addressed? And Activating Macros via ATO trigger?

Curious about macros as well. I haven't updated macros to see if they work without being written in reverse; the ones I have that are, still work as they did.

 

[Des Westcott]

Curious about macros as well. I haven't updated macros to see if they work without being written in reverse; the ones I have that are, still work as they did.

Yes. The same with me. They should continue to work in reverse as long as the checkbox is ticked I think.

 

[Des Westcott]

@Ranjib

Reef-pi 4.0 has "fixed" something in AIO. Suddenly I'm getting much more info through to AIO from reef-pi. I never had a problem with throttling due to exceeding the number of feeds on a free account. Since upgrading to 4.0 it's happened a lot. No big deal, I've just deleted the feeds I don't want to show.