Hi,
I’m working on integration with google assistant, i want to know the thoughts everyone has about the plugins capabilities… i got some pieces working and need to integrate it into a plugin now, but basically i can now turn on or off devices by conversating with google assistant.
-
Google Assistant/Home integration
-
Basically i need some input about how people would like to start the conversation… it’s easy to say turn all the lights off but if we need to turn off a specific device we need to refer to a room or a device type which needs to be defined before, so we can work with dummy switches which execute actions and couple them to rooms or something.
For now i’ll just make it switch/turn on/off light/switch/device number, then we can create a device named light-2 and it’ll switch off light-2 or room-2
-
Hi Daan, Awesome extension you are working on! This will bring Pimatic integration to a whole new level again
.I’d recommend @michbeck100 to have a chat with. He created the integration with Homekit (simply put Apple and Siri), in such a way that scene setup could still be left to Apple Home enabled apps on the mobile device. I think he exposes all Pimatic devices to Homekit, in turn making them available on Apple devices through Apple Home. Grouping and scenarios in the Apple database are then separated from the actual Pimatic setup providing users with maximum flexibility.
Not sure if this is applicable to the Google integration scenario, but he might have some experience you can use to your advantage. I think the architecture of pimatic-hap could be used as a starting point.
Off topic: I am currently working on extending the pimatic-tts plugin to provide text-to-speech to (W)LAN connected speakers and devices, so would also be interested in discussing touch points as one of the engines used for TTS is Google’s. (Think you are Dutch as well, so in private messaging it makes collaboration easier
)"Screw the captain. It's the engineer running the ship!"
pimatic-telegram, pimatic-tts, pimatic-woox, pimatic-lg-smart-tv, pimatic-spotify, pimatic-wakeuplight and some not-announced plugins -
@dan Hey, i’ll stop integrating google assistant
i’m going to try to integrate home control which works with google assistant, this way we can sync devices and assign rooms to devices and just ask assistant logics to turn off specific devices by room or device… this isn’t gonna be an easy job but will be gonna be amazing if it’ll work. -
Hi @DaanNL ,
nice to hear that you are planning to create w way to communicate with google. I stopped with google assistant because the only good way is to get a certified cloud service for pimatic and as I am using alexa its not very high on my wish list. Anyway it would be great because the communication with Android Auto and via smartphone would be possible.
So if you need a tester I am here. I´m not good in google services and only a basic nodejs/javascript programmer. Whats your approach with “home control” and what is it? do you have some infos?Thanks
Daniel
-
@dan said in Google Assistant/Home integration:
I am currently working on extending the pimatic-tts plugin to provide text-to-speech to (W)LAN connected speakers and devices
Hi Dan,
if you have something to test I can be your beta tester. I really like the feature to send text to the Google Home speaker. Maybe you can extend your idea with the possibility to send an mp3 or wav to it. -
Any updates on this topic? Quite interesting since Alexa doesn’t support my language and I would like to stop speaking English in my home.
-
Any progress on this? I would like to assist if possible, do you have it on GitHub?
-
Yes,I switched to home assistant… I made a plugin once which is heavily used and I was not mentioned anywhere in a modified version. It was also hard to make it getting into pkmatic.
So I decided to stop development and switch to another home automation system. -
I switched to home assistant…
-
@daannl said in Google Assistant/Home integration:
I made a plugin once which is heavily used and I was not mentioned anywhere in a modified version. It was also hard to make it getting into pkmatic.
So I decided to stop development and switch to another home automation system.Sorry, I don’t get this!
As far as I can see you have never published a pimatic plugin on the matter and I have never seen a link to your work on github or elsewhere. So, I am not sure what you mean by “I made a plugin once which is heavily used and I was not mentioned anywhere in a modified version”. Does this relate to some other work you did earlier? I guess it relates to your work on virtualhomeduino which is a supplementary project (not a plugin) initially written by sweetpi. At some point @layereight did a fork on your your fork
without explicitly mentioning you as contributorActually @layereight added this in reaction to your concern as explained in the following posts. My thoughts on this:- Your concern is right. If one’s work is based on prior work, this should be explicitly mentioned as part of README. It should be noted, however, the relationship between the projects is clearly visible on github thanks to the fork hierarchy. So, it is visible for everyone on github, that @layereight derived his work from yours as you did from sweetpi’s (without explicitly mentioning it).
- To be fair, the work on virtualhomeduino is preliminary and neither contributions from @layereight or yours have been consolidated into pimatic. So, I think the blame is not on “pimatic” as some users might think just reading your post.
- I don’t see how this issue relates to your initiative on google assistant. From what I read I really doubt you ever started developing the plugin. If so, why not simply saying it? Other developers have also struggled with the plugin development, but it is possible to get some good support from other developers. In particular, this is true, if you are willing to share your work on github - something you haven’t tried as far as I can see. Github and such are collaboration tools, btw.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
If he would have made a fork it wouldn’t seem an issue … But he didn’t fork but copied the source on GitHub.
-
It looks visible from GitHub:
I also agree that it should mention at least what work it is based on, but I can see in the contributors section that he gives you full credit for having migrated to pigpio.
@DaanNL sad to see you go from pimatic, but did you ever start developing on a plugin with Assistant? I would really like to help, but don’t know where to start/how the integration with Assistant should work.
-
@devqon said in Google Assistant/Home integration:
@DaanNL sad to see you go from pimatic
+1
As @Devqon already pointed out @layereight has not plain copied your source code as he also explained earlier. Moreover, @layereight has taken your concern seriously and reacted to your post shortly after and he also added the Contributors section (thanks @Devqon for pointing this out) to the project README shortly after as you can see from the commit log. On forum he also stated his work is github fork on your project. So where is your point here?
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
Hey @DaanNL,
sorry to see you go, mate! The community needs good developers.
I’m also sorry to see you upset. But maybe you misjudge the situation a bit. I clearly forked you on github and I gave you the credit you deserved:
https://forum.pimatic.org/topic/3052/help-homeduino-not-working-anymore-solved/102You did all the work, man! I just reorganized files and simplified the build process. That’s all.
