Comments (13)
Just trying to be clear, I don't mean to be offensive
from core.
Hey there @mtdcr, mind taking a look at this issue as it has been labeled with an integration (aten_pe
) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of aten_pe
can trigger bot actions by commenting:
@home-assistant close
Closes the issue.@home-assistant rename Awesome new title
Renames the issue.@home-assistant reopen
Reopen the issue.@home-assistant unassign aten_pe
Removes the current integration label and assignees on the issue, add the integration domain after the command.@home-assistant add-label needs-more-information
Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.@home-assistant remove-label needs-more-information
Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
(message by CodeOwnersMention)
aten_pe documentation
aten_pe source
(message by IssueLinks)
from core.
I'm also getting this issue.
from core.
Someone needs to bump the dependency and test it out
from core.
I have tested the code owner's HACS repo with the PE8108G (latest firmware: 2.4.239), and it's working fine. However, the owner appears to have been inactive for a few months...
from core.
If your issue is around the custom integration, this isn't the place to get support
from core.
Just sharing some information for someone who's desperately looking to integrate a PDU right now, man... Why so offensive? I'm also having trouble with the official integration.
from core.
I have tested the code owner's HACS repo with the PE8108G (latest firmware: 2.4.239), and it's working fine. However, the owner appears to have been inactive for a few months...
I'd recommend to keep using the HACS repo, as I don't intend to maintain two versions, and trying to maintain the version included in Home Assistant hasn't been a delightful experience to me. Of course I'd be fine with any attempt by others to merge the HACS version into Home Assistant, but I won't invest much time myself.
from core.
@mtdcr mind having a chat on discord? I'd love to hear your pain and try to help you with them
from core.
@mtdcr mind having a chat on discord? I'd love to hear your pain and try to help you with them
No, sorry, I'm not on discord. To sum it up, there were too many occurrences of "Thank you for your contribution, but we force you to do this huge unrelated extra task before we accept your small incremental improvement" paired with too many pointless discussion in the area of networking and security basics. My time is limited.
from core.
Is there any way I can help you out with these tasks?
from core.
For this specific issue:
- Take https://github.com/mtdcr/homeassistant-aten-pe/tree/main/custom_components/aten_pe and merge it into Home Assistant. Fill in the missing bits (at least some kind of tests, i guess - see #61806 for a past failed attempt). I'll gladly accept PRs to my repository in order to test any required changes in advance.
More generally (IMO the more desirable way of helping), in case you (as in "the maintainers of Home Assistant") want to create a more welcoming space:
- Stop forcing contributors to maintain code repositories and releases for libraries used exclusively by Home Assistant. Let them decide what's best for their integration. This is the reason why this very issue exists. atenpdu broke multiple times already, because Home Assistant at some point in time updated or replaced its pysnmp dependency to incompatible versions without patching atenpdu at the same time (or giving a heads up at least). This could have been easily done tree-wide if the few relevant lines of code in atenpdu were part of the integration.
- Accept imperfect contributions, especially for new integrations. Let there be space for incremental improvement. Accept that people will choose the way of least resistance eventually. If the hurdles are too high for a few-weekends-per-year pet project, many developers will just give up and find a different solution (like HACS, keeping their code to themselves or moving to an entirely different system).
- Stop closing issues with a bot. Issues do not disappear magically due to inactivity. Yes, some problems disappear unnoticed, but not those where most of the issue comments only get written to stop the bot until everybody just gives up. That's just rude.
These are examples of failed PRs I submitted in the past, that wasted a considerable amount of my and other people's lifetime and killed most of my motivation (just in case you're interested, I don't intend to warm these up):
from core.
From your comments I feel like you disagree with the goals of the project. I can't help you with that. I personally strive for consistent and good Integrations that make use of best practices.
If the problem was that you couldn't get the config flow in, I'd gladly help you with that, but I feel like you've given up so I don't feel like investing time either.
I take your other comments with me. I probably can't act on them, but it's interesting for me to see why people don't like contributing to core.
But let's not continue this discussion about contributing to core in this issue as this issue is meant for aten_pe
from core.
Related Issues (20)
- Ecowitt ws3910 co2 values are not added HOT 1
- Non-blocking "NoneType: None" Error when trying to register a service in async_setup HOT 1
- deCONZ entities: current or voltage are not created HOT 8
- Add mm/s as a native unit of measurement for speed device class HOT 2
- Netdata: host is offline -> periodical errors in log - although scan_interval=99999 HOT 1
- Ondilo ICO API - 400 error - cannot get user HOT 53
- Nuki Integration don't work HOT 4
- Assist with ChatGPT and Gemini Error 400 String Too Long HOT 1
- JVC Integration locks up Projector (jvc_projector) HOT 5
- Unable to change preset mode through Flexit integration HOT 5
- GoodWe GW6000-ES-20 wrong model family detected HOT 1
- GUI Template checks for 'true', but templates return 'True' HOT 1
- i can't backup home assistant core HOT 2
- Inappropriate memory allocation
- WARNING (MainThread) [homeassistant.components.hassio.handler] Found incompatible HTTP option 'server_host'. Watchdog feature disabled HOT 3
- Unable to Authenticate Yale Home using August Integration HOT 39
- "Unknown error occurred" installing Home Assistant iOS HOT 1
- Home Assistant Cloud HOT 3
- Yale integration authentication issue HOT 24
- BMW Connected Drive - no longer possible to login in after update to HAss 2024.8.2 HOT 84
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from core.