Just a nice new feature @michaeljoos I like it 
You just canât help yourself, can you?
1 Like
I am just wondering whatâs openhabs definition of a bug is long learning journey but I am happy to write Wikipedia new
2 days ago a bug or feature was resolved what I wrote here and it was called as a feature request and so I donât care about it 2 days ago someone fixed it with the remark as a bugâŠ
So my learning is call it as a feature make some noise and it get fixed quicklyâŠ
I guess youâll never understand it âŠ
- Wrt to your rules file reloading issue (Reloading of rules files doesn't work properly in openHAB 4.3.1 till openHAB 5.2 snapshot · Issue #4529 · openhab/openhab-core · GitHub): @Nadahar and others looked into it and I guess invested a good amount of time into the investigation. Unfortunately no one was able to find a cause, and you not being able to provide the requested information required for debugging might be part of the reason for not finding a cause.
- Wrt to charting (Chart hover tooltip shows incorrect future dates / mismatched data point · Issue #3655 · openhab/openhab-webui · GitHub): Reporting something you consider a bug, then experiencing disagreement about whether is a bug or not, and in response to that starting a campaign of calling bugs feature, repeatedly pinging maintainers, demanding to look into your report will do anything but cause people to look into your report.
I am fed up with your behaviour, so @moderators please step in. When you check @milo âs activity, youâll find enough postings of his campaign.
See here for example
All others can be found by searching easily:)
If yo look on this
There is a proof inside that the chart is behaving differently on with a snap out of the code and so on âŠbut no answer on it why different behavior is there depending on how you configure an itemâŠ
An again no I canât open any pull request because I have never learned it and I only program via chat gpt and also have other projects running I take care on it
Thatâs a good example of how issue reporting should work: Someone reports a bug or requests a feature, all required information is provided, someone answers it, there is a fact-based discussion and in conclusion a fix is developed.
I can see no one declaring the report a feature request, there were only valid concerns expressed about possibly breaking existing behaviour when fixing this.
If you would handle your other issues the same way that would be appreciated.
1 Like
Look up the forum there was a long discussion about it between me and rich and different other personâŠI opened one and deleted because it was declined now itâs inside I love it fight was 1 or 2 years
And also no I donât search for you chat gpt can help
And again @florian-h05 your comment makes no sense for the chart tooltip you do not even read my comments
So why I should do more effort in it
It seems like ChatGPT has some way to go before it can help you - with your attitude. Iâm honestly questioning what you think you can possibly achieve by saying things the way you do. Could it be that, not only are you unable to (or uninterested in) figure out how to code what you want, but you arenât even able to express is in a way that is comprehensible to others?
If the same feature/bugfix/whatever that you have been âfighting forâ for a long time, has been implemented in a short time when somebody else proposed it, doesnât it make you at least a bit curious about why your attempt failed? Could it be something with how you go about it?
2 Likes
I can simple answer
@milo : please stop that. Thatâs annoying. You can buy a commercial system and there you can demand professional support.
Here we should be as respectful as possible to our fellow developers and supporters. Doesnât matter if itâs a bug or a feature. Nobody is paid here. I would appreciate if you would reduce the amount of posts to a minimum.
6 Likes
If I can proof there is throughout the graphs a different behavior why no one is taken care of it? Tell me where and what I should reportâŠ
Iâm not questioning that there might be a problem or even a bug. I donât like the way you try to make pressure. Many users have problems to solve just like you and manage to be friendly and polite without being pushy
2 Likes
The problem is there was a declined on GitHub and the forum so it will never changed or fixed or whatever⊠I am not making the pressure that the issue get fixed I am making the pressure that the problem is accepted⊠thatâs a big difference and also one other user agreed with me but still it gets declined
I am circling and someone need to cut the circle to get a lineâŠthatâs why I am making pressureâŠ
Itâs like Don Quijote
It doesnât really matter what you âmake pressureâ for - it has the opposite effect. If you spent that energy trying to contribute to the problem being solved instead, with information, insight, observation, contribution, testing, whatever you can offer, the chances for a return for your investment is much better.
Also, sometimes people disagree. I disagree with people âall the timeâ. That happens, people have different concerns and priorities. But even when you disagree, youâre better off trying to explain your point of view, make it seem reasonable, than trying to âbullyâ those that oppose you. The only thing you achieve by doing that, is turning those that havenât yet taken a position against you too.
3 Likes
Please read the threads and GitHub issue everything is explained and code snippets, screenshot includedâŠ
And that is the misunderstanding: Nobody is obliged to see a problem like you see it.
Even if you are right.
This is all volunteer work.
If none of the developers sees it like you (doesnât matter why) thatâs currently the end. If you cannot provide better information you have to wait (even if you think your information was sufficient). Insisting and repeating is just negative for the community.
2 Likes
Please read the posts and GitHub issue