Perhaps there is a topic to promote Gladys even more on these features? Some are related, for example the Linky part will be interesting if we gain the ability in Gladys to consult data over a dedicated period.
To accelerate certain developments: In the Android tinkering sphere (root & co), I have seen developers propose kitties to buy the phone for which the root is most requested. We could propose a similar system:
by lending the equipment during development?
by « sponsoring » the development by contributing to a dedicated kitty?
For example, I see @Pti_Nico who is developing blindly for Yeelight, as was the case with others for Zigbee previously.
This is exactly the strategy I took to choose the topics to cover in videos, with Zigbee2mqtt and SSD installation being highly searched topics on the forum.
100% agree, it’s a great idea.
I think « sponsorship » would be fairer. I don’t find it very « fun » for a developer to just receive equipment, code for someone else, and return the equipment: what’s in it for the dev?
On the other hand, if there’s a fund to finance equipment (if it’s just a few bulbs, it’s not a gift worth €1000), the developer provides their skills in exchange for cool equipment, and they have a real interest since they develop for their personal use and can continue to follow the integration
Do you know of any particular service for setting up funds?
For Linky, in my mind, it’s the second development I’m going to tackle once I’ve finished the Alexa integration. However, at the moment, I’ve chosen not to be on the « communication/tutorials/forum » tab to revive the community a bit, more than development where I’ve almost « over-developed » in 2021, without communicating enough, and therefore sometimes I felt like I was developing « for nothing » since usage wasn’t changing. I’m catching up in 2022 and it’s working well!
Money can then be transferred to a real bank account, up to €500/month with no fees.
(For free Lydia users, the limit of money that can be transferred without fees to an external bank account is €500/month. Beyond that, a 1.5% commission is applied. More information here.*)
Lydia is great, just need to see if we can send without a Lydia account like we can on most platforms, because not everyone has Lydia (especially among our non-French French-speaking friends )
I’ve looked into the different options, and Papayoux seems pretty good when you think about it
Granted, there are fees, but as soon as there’s bank card payment, it’s impossible to have no fees.
In the case of Lydia, their « piggy bank » system is just a « bait » for their product, so they cover the banking fees in exchange, which is equivalent to their cost of acquiring new users since you have to create an account.
For a 50€ material funding, with Papayoux it’s 50*1.9% + 0.20€ = 1€15 in fees.
I use Lydia a lot and I like it, but I’m afraid it might discourage contributors who want to give but don’t have a Lydia account?
Often what I notice is that the project developers are often a younger audience who have Lydia, but the community members who are not developers but have the means to help are often older people who consequently don’t have this kind of application (I might be wrong, feel free to tell me)
Sure! So @lmilcent, you mentioned that @Pti_Nico needs some Yeelight devices?
Like these Yeelight devices?
I don’t even know if you need me for this. Maybe the developer should create the fundraiser, so they can receive the money, buy the items, and handle the delivery themselves. That way, it avoids unnecessary messages about the address and such
Yes, and moreover, we must be clear about this: the fact that a fundraiser is organized to finance equipment for someone does not constitute a work contract with an obligation of results.
We remain in a « volunteer » framework where someone kindly dedicates their time to advance the community, and this regardless of the amount of the fundraiser
Similarly on the « merge/review » side of PRs, the requirements for merging PRs remain the same regardless of the PR. If a fundraiser is organized, and a beginner developer submits a PR that does not meet quality standards, it will remain pending until all the boxes are green (it seems obvious but I’m saying it to be sure, no bad surprises! )
I don’t think so, I think it really needs to stay in a « peer-to-peer » philosophy directly between the developer and those who want to fund the hardware.
The pots won’t reach €1000, the idea is just that a developer says « Okay I’d like to help develop this service, I need €50 to buy Yeelight », and then 10 people give €5 and the developer equips himself and the pot is closed
@lmilcent, what criteria are you basing this on to make such extrapolations?
Here is, to confirm, the list of lamps that I own, referenced in the Yeelight application (which you should know if you have one too) (but I can also find the invoices if you wish…).
Unfortunately, I don’t have all the available models to test and integrate them into the service, so it is possible that some models are not recognized. Maybe I should change the device discovery method, but for that, a good part of the code needs to be rethought…
Sorry if I am not as active as before, but starting almost two years ago, you are one of the few, recently, to have given me constructive feedback following your tests, and concrete help on the subject.
Unfortunately, I no longer have as much time available to advance on a development that no one seems to want to help me with, whether by proposing improvements, fixes or code suggestions.
On this subject, I would like to thank @AlexTrovato thanks to whom I was able to advance more quickly on the development of the EweLink service.
While reading your message, I realized I misunderstood the exchanges on the following topic:
I thought you didn’t have a Yeelight but were still trying to develop the module, whereas you were actually trying to help solve a problem on a model different from yours, my mistake!
Having already noticed this for others (attempts at) development, I wanted to propose a solution for situations like these and enable development under the best conditions.
In my opinion, you are encountering the problems of community open-source in some cases, namely many people asking for a lot of things, but few coming to help It’s never pleasant, but you have to deal with it..
Thanks again for your developments so far anyway Sometimes all it takes is for someone to lay the groundwork for the development to be taken over by another, as was the case with Zigbee with @Reno and @cicoub13!
If I’m not mistaken, there are Wi-Fi / Bluetooth / Zigbee compatible devices at Tuya.
The idea would be to manage everything, that is to say, create a link with the Smart Life app (I think that’s what it’s called). A bit like the ewelink integration?
Personally, I equipped myself a while ago with a Tuya gateway… before realizing that it was not supported by zigbee2mqtt - and I understood NOTHING about how to create this integration.
So if a Tuya integration were to see the light of day, I would be delighted!
It’s never pleasant, but you have to deal with it..
Sometimes all it takes is for someone to lay the groundwork for the development to be taken over by another, as was the case with Zigbee with 