-
-
Notifications
You must be signed in to change notification settings - Fork 324
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
Release source code? #5
Comments
Hi, Currently we are in the Test phase, and I like to get feedback from the standard setup. Thats why I wait to release the source to avoid unhelpful noise. |
Sorry for late reply. Really like the project, but for me I would like to view and edit the code instead of building a black box without knowing what's happening inside the device and my data. |
Yes I would also like the source code to be open so us DIY-ers can change the code to our specific needs, help fix bugs and learn how this thing does what it does :) I also don't want to have to put my data in ubidots, instead I'd like it to post the data to my own web service. |
Thanks @koffienl @jaapz for your interest in the project! To answer your questions:
|
Thanks for explaining.
That's the other way around ;) You keep it closed and say "only who contribute can see the code". How do you expect someone to contribute when the source isn't available? |
There are various ways of contributing to the project:
Feel free to share your contribution and I am happy to share early code access to you. |
koffienl, you might wish to wait until the SW is out of alpha test mode. Just like everybody else, including me. There is an entire bunch of people waiting eagerly. |
I already see stuff I would like to add/change (but not necessarily interesting for others):
But hey, I'm not here to bash the project - I wish @universam1 all the best for this project, a lot of homebrewers can't wait to use it. |
Lets talk:
thats possible
already implemented (no graph)
?
Thats the reason for to keep it NDA, because people without understanding of the fundamental principle of this project will "dead modd" it with these approaches. The deep sleep is the soul of being able to run this project at all and there are a lot of tricks around it. I'm eagerly interested in a good reputation with proof of working before all this breaking changes are going to happen. Sorry to say it this way, but do the maths!
This is also already implemented and ready to be used to change update interval on the fly. Though tests have shown that this again increases power consumption with around 100% so not enabled currently.
Here is the point, I'm happy with contribution by translation, so feel free to go ahead! |
For graph you could something like this: http://zooi.oostindie.com/images/977capture.png
Let's say your local wifi has a power loss in the night (or your ISP, or ubidots) and you loose your history. If you write all the measured data to a local (JSON) file you have a backup of the history of all the data.
I understand that, bit it sounds like the point of view from the side of a manufacturer. Shouldn't the people with understanding of what they are doing have the option to choose what they want? Especially in the debug fase when they are building and finetuning the device? ;)
Of Course, doing a extra HTTP call when coming out of sleep will use some extra resources. So make it an option.
|
sources are online |
Great, thanks! |
Hi,
I'm interested in building your project, but you only release compiled BIN files. Do you plan on sharing the source code so one can learn from the code and alter the code for it's own needs?
The text was updated successfully, but these errors were encountered: