I think (at least from this thread) we have a disagreement on the approach how to implement it ( at least from this thread), I also think that current codebase is not scalable, therefore I started from scratch. I am also not sure about myself how long will I be able to commit, so it’s also a test for me.
You totally miss my point Rich… One have to know there is a problem before beeing able to deal with it. This is what I talk about. For some reason I really cant understand, it seems like this integration just stopped, without anyone notice, untill Gytis started this thread. Thats the problem I´m speaking about.
If the other maintainers knew, or any else. All I ask is that they at least do something, (an announcement asking for help or whatever). Doing nothing, you can be damn sure, nothing gona happen. If they didnt knew, perhaps this is how things could be optimized!
You seem to continuing miss the whole point.
You really believe this is just complaints?
Bingo!
Thats why it´s important to have somekind of procedure to try deal with it. To my understanding, there is none.
It is better than nothing. Question is, is thats how it has to be, (wait untill someone given up waiting and starting on his own). Or would it be better to have a more precise procedure to at least try a deal with such a situation in the future, before it gets to the next “Gytis” ?
Like I mentioned a few post back… It´s a paradox. We´re all dealing with a smarthome system where we try to think and deal with “what if…”. But when it comes to the developing (maintaining) part, there seem to be noone really taking care about "what if… ".
What if a maintainer dissapear (an integration or any other important part seem abandonded). Then what… Whats YOUR suggestion? Wait an see what happens?
Then why don’t you come up with a procedure? Why don’t you figure out how to make such a procedure work? So far all of your posts are “Something’s wrong someone else needs to do something about it.” Well they are not doing something about it. They likely are not going to do something about it or else they already would have been. So if you are not willing to take the lead and volunteer the effort than yes, it’s just complaining.
I look forward to your submission of a proposal to the openHAB project Github with just such a proposal outlined.
I choose not to contribute to OH to solve this particular problem. I choose to volunteer my time to contribute to those things that I have the the skills, time, and interest in doing. And this is the approach and attitude of pretty much all open source developers I’ve ever met.
My suggestion is, since you feel strongly about this, then you come up with something. Don’t wait for someone else to decide to address it. Don’t demand that someone else address it either. You are the one with the grave concerns. You are the one who believes there is some sort of solution that will work. So go see if you can make it happen.
If you want a problem fixed in an open source project you need two things:
recognize that there is a problem to solve
be willing to or find someone willing to volunteer their time to solve the problem.
You’ve 1 covered. What about 2?
If you are not willing to do this yourself or find someone willing to volunteer to do it for you then I maintain my opinion. It’s just complaining and hoping someone else takes notice and does it for you.
Hi @gytisgreitai, Why there isn’t the action.devices.types.LIGHT ? I see you use SWITCH for your lamp, but in this case google home don’t see a light but a switch
I wouldnt mind. But its a organised procedure. As a private user you cant expect one to hunt all around github trying to figure out wether a integration/repo/whatever is “falling” behind. This is something for a more organised level, either at maintainers or AC´s levels.
Yet you expect the maintainers to do so? They have no more insight into all the repos than you do. The AC has even less insight, and it’s not their job.
If you want this to happen then yes, I expect you to spend the time to go through the repos and watch them for signs of abandonment. Or you can establish some sort of organization to do this work. As a “private user” you have as much info and insight into this as any of the maintainers or AC does. And both the AC and maintainers have their own tasks and responsibilities. I don’t see them being willing to take this on.
So please, go do it or stop complaining about it. You’ve said your peace. But if you are not willing to spend time on it why should anyone else volunteer to do so?
Make’s note… don’t get on @rlkoshak bad side.
Actually I brought up this exact issue while ago when someone wanted to sell OH as a residential business venture, he was looking for support with his projects/jobs.
My opinion hasn’t changed, It isn’t fair to expect volunteer’s to provide support from members to resolve issues concerning knowledge in which he was limited.
You should be ready to support with in depth knowledge any product that you would intend to use to support your family. With openHAB it is a complicated amazing tool for the impending future. Be happy you are getting in on the ground floor.
I have spent approx a year and I am only now beginning to understand the architecture, not to mention python, docker, sitemaps, API’s, links and etc.
I agree that if someone feels deeply concerning a problem, then do what others do.
Grab the bull by the horn’s! Not that you can accomplish quickly. Sit at your laptop and learn it.
The good news is that I hope that soon I can contribute as well.
Thank you ALL for the time you have given to provide a platform so many can benefit from.
We Are openHAB Strong
Steve-
There are a lot of devices that are not there yet. Light also comes with action.devices.traits.Brightness trait which also is not done yet and would probably need to be implemented via Dimmer/Number, so it’s on todo…
No, I expected someone had already taken this into consideration.
Precise. But I´ll need to know where to look, and what to do, in case something doesnt look right.
As I explained before, this has to be organised and structured.
If/when noone complaints or mentioned anything, it doesnt mean everything is good. Mostly it means, something could be better, but noone cares about it. You seem to prefere this way.
Its a very bad habbit to target the person complaining or mention something, telling them to fix it themselves, rather than trying to understand, that even a complaint can be the help needed to get things changed. You seem very focused on anyone saying, mentioning, complaining, that they grab the ball and fix it themselves. This is mostly why people aren´t saying anything. And then´ll you´ll end up with noone saying anything anymore, because they dont care.
It´s a circle destruction, and a bad way of thinking, in my opinion.
Anyway, as I said, I wouldnt mind doing what I believe is needed , as long as it gets organised and structured. Without, there is a great risc that things wont be any better.
As evidenced by this whole conversation clearly you can see that’s not the case.
openHAB is an open book. Everything is done out in the open on GitHub for the world to see. Start looking at the Issues and PRs made to the various repos and come up with some sort of metric to tell if a project is in trouble. You know as much as anyone else. You are perfectly capable of organizing and structuring this effort.
I didn’t say don’t mention or say anything. But you keep on complaining about this one issue over and over across multiple threads. So at this point either do something about it or stop complaining. We have been made aware of the problem.
If you see something new, then yes, please raise the issue. But also realize, the issue must be raised on GitHub at some point.
How is it any better that those who do care about it are not willing to do anything more than complain about it on the forum? If you think you are helping the project by just pointing out problems over and over with no intent on working to fixing it then you are part of the problem.
You’ve raised your issue. No one has volunteered to do the work to address your issue. Continuing to complain about the same thing is not going to get things changed. It’s just complaining. It’s not helpful. It will lead nowhere.
If you are looking for some sort of top down organization to impose upon the various OH repos than you are heading down the wrong path. That isn’t how OH as a project is organized. That isn’t how it works. And I doubt the maintainers at large will sign up for such.
But as an effort that you lead, you can organize and structure it how ever you want.
Hi @gytisgreitai. Thanks for your voice about GA maintanance problem. But the greatest thanks for your development attempt. Your approach looks very flexible.
As I understand this topic has to be split into two parts. The first one is to discuss how to manage the overall issue with any component maintenance: ability to maintain maintainers, how to see red flags in the project, explain foundation approach and so on. My proposal is to create by you the second topic: “New implementation of GA integration” to discuss your approach, give you feedback, ask you about details and focus on deployment.
The last one is the question: How to deploy two different ways of GA integratioon (current @MARZIMA and developed by @gytisgreitai) on existing myopenhab.org infrastructure.
I keep the fingers crossed and I hope GA integration features will be enhanced.
My understanding is that the tag naming approach was derived from the initial Apple HomeKit integration.
There have been a few discussions on how to continue having a unified configuration across virtual assistant integrations while introducing customized metadata configuration. The main consensus seems to be to use the recently added semantics metadata support concept. Another idea was to expand the current list of supported tags across integrations but we never got to an agreement in the end.
I think that is a terrific idea. It is not unprecedented to have two binding using the same technology. Matt1 has developed a great ip camera binding when there was already an ip camera binding and has developed many new features
I’ve stated this above, that I’m more targeting self hosted solution rather than hopping to become official addon, I mean even now I have my own hosted myopenhab service with test action wired on google.
Regarding Google allowing multiple implementations, probably not, but then again, have a look at their suggested bindigs, e.g. “Daikin AC Manager India”, “Daikin Smart Home”, “Daikin D’SmartHome Lite” “Essence Australia Smart Home” “Essence Smart Home Beta”. They do look like they should be single items, yet somehow they are split. Also I have no idea how hard or vigorous their approval process is. But afaik this is way too early to think about something official.
PS before I get flamed I come here from home assistant because I have an interest in any open source projects. In looking around I saw this comment and just had to respond. However I am not here as a HA shill. Cheers.
Guys, can you explain for me that please:
is integration with Google Assistant should work now while syncing of new items is disabled to myopenhab.org (according to Myopenhab not reachable) ?
I’ve recently tried to integrate with Google Assistant but was unsuccessful.
It’s very long.
Marzima spent several weeks to push and wait for Google official approval. (Thanks to him and his perseverance!).
Main obstacle was that Google employees had no product to buy and test with, as it would happen with regular smart home device manufacturers, so this was kind of first open source project to be integrated with Google smart home part. Maybe now is better.
BUT there is beta , where you can invite specific google accounts to test your Actions on Google beta, and only those users will see the openHAB-test in Google Home app.
I like also the option for self hosted solution. This is available also with marzima version, but you idea of maybe using Docker or ready-to-use VM, and maybe with a very clear and possible simple setup manual, would make possible to many users to go for the self hosted path.
Another important part to consider is the direct local communication instead of going through myopenhab.
This was suggested as possible improvement (not available initially from google) in one of the issues Integrate with Local Home SDK #102.
Strangely Google Assistant integration with OH is 1-2 seconds slower than Alexa integration (I can test both on same OH instance and same room).
So maybe by using Google Local Home SDK may improve a lot the response time.
Finally I also think opening a new thread for following you implementation, asking for help on testing , progress etc. is a good idea.
The title here is not appropriate anymore for your new implementation effort.
