Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

beebotte.com - retain vs write API (weird persistance, possible to add) - not a bug I think #96

Open
christianruppert opened this issue May 30, 2023 · 0 comments

Comments

@christianruppert
Copy link

christianruppert commented May 30, 2023

Hi,
first of all thanks for this awesome library. I have a small issue with a "custom" API, namely:

https://beebotte.com/docs/clientapi#write

Background: They offer a quite nice MQTT with a solid free tier and some ability to "persist" messages. But as far as I understand it they are not using the official "retain" flag - but a separate API (god knows why, I asked their support and will update here if I hear back).

They also have something called "Rules" - which would allow me to take one topic and on publish WRITE it to another topic - kind of getting what I want, but a bit ugly (they dont support listen to publish and then write to same channel, would cause loop).

It seems like only the URL is different for persistence (see e.g. here: https://github.com/beebotte/bbt_php/blob/master/src/bbt.php)

And finally a link to their arduino sample (where they only use simple publish) - which works:
https://github.com/beebotte/bbt_arduino_examples

So the main question would be "is it possible to support their API" - maybe by a fork. Sadly my C sucks (Kotlin, mobile world) - otherwise I would give it a try. I will post in their repo as well and cross link it, if others have the same issue.

So not really a bug, just a pitfall due to custom API, I guess.

Chris

PS: Link to related topic: beebotte/bbt_arduino_examples#5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant