Hahaha… looks like I have been gone from the chat for too long
I am the first one to agree on the app needing more ppl engaged. I am happily accepting any and all help, the repository are public and the code is open source so anyone can help adding support for devices.
But no worries @Pavel_Karzov, there are updates on it’s way and I work close to Athom and get great support when needed! Thanks for the concern though
It’s been a while. I know you are all eagerly awaiting a new version of the software, hoping for support for an extensive list of new devices and features. I understand the frustration of not having support for a device that you have invested in.
That being said, I am closing in on a new Live version, hopefully to be released within a few weeks or so. I will start with a new Test version that addresses a bunch of issues with different devices, such as color and saturation issues after adding a new light device, some multi-socket devices triggering all sockets at once, and some multi-gang switches not responding or reporting as they should.
At the same time, a number of extra codes for already added devices will be added, as well as some new devices.
Once the Test version has been proven to work and bugs have been fixed, I will release the Live version and begin adding beta support for some more complicated devices in the Test version. If there are issues with a single device, I will remove it and release the Live version without it to avoid any further delay.
Yeah, I agree, but we did reset…while Github, when you take a look, require reset as well
So kind of… sad. True is that it’s too much for one developer yet, seem Johann, despite of doing tremendous job, is even not accepting PR in the Github… so feeling kind of “ambivalent”. So while we did a reset, I’m not sure Johan will get more time
It’s not disagreement or something, as it was required but not really solution. That’s what I meant.
Open PR’s are either new or have issues/ongoing discussion.
Regarding the thread I hope we can keep it to discussions rather than a long list of requests. Reason I choose to point to Github for request is that it’s no joy in having hundreds of requests of random quality posted again and again for what often turn out to be the same devices with a new manufacturerName. Having to browse through the thread to collect info that I have to add to github as issues (or a notepad on my desktop…) and then search for missing information, cross check with other requests and find images is time I could instead use to create icons, develop code and support you guys.
As of September 2023, I request that all device requests be directed to Github. The reason is straightforward: previously, when requests were made in this thread, I had to manually create an issue on Github, transfer the information, fill in any missing details, and then schedule the device to be added. Additionally, many requests were either duplicates or inquiries about the status of an existing request. On top of this, the thread became difficult to manage, and valuable information and interesting discussions were drowned out by inquiries about new devices or the status of old requests.
I hope that creating a Github account (which is free and straightforward) isn’t too much to ask. Doing so will significantly streamline my process for handling requests and follow-ups. I believe this approach will also encourage more individuals to contribute code.
@johan_bendz I would like to contribute… Im currently doing some tests and reading the documentation I found regarding zigbee implementation, I would like to keep the same project structure and rules. If possible would also like to ask you some questions directly but not sure what’s the best way to reach out to you.
Currently Im implementing Smoke Detector HEIMAN and lcd TS0222 (“_TYZB01_ftdkanlj”, “_TYZB01_kvwjujy9”).