You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sorry that is not possible because the Google Assistant doesn't have a local API. I'd need to have a complicated cloud infrastructure to support Google home which I can't do as a small open source project.
You can do it with the free IFTTT website though, which is compatible with google Assistant. It requires you to do a router port forwarding so the ESP8266 is accessible from the internet. Then you need two IFTTT Webhooks applets that trigger <YourPublicIP>:<YourESPNetworkPort>/win&T=1 for on and <YourPublicIP>:<YourESPNetworkPort>/win&T=0 for off, respectively.
This is not a bug, and there is no way for me to add native Assistant support in the near future sadly.
Therefore I close this issue now.
Feel free to reopen it if you have any further ideas :)
Könnte man nicht eine von Google unterstütze api integrieren? Die api von tuya smart (smart life) ist offen und soll leicht verständlich sein. Viele sub-hersteller (smart life oder auch hama) nutzen die.
Vielleicht hilft ja der link? https://docs.tuya.com/en/cloudapi/cloud_access.html#access-mode
Könnte man überlegen. Würde sicherlich funktionieren, aber im Moment möchte ich keine cloudabhängige API integrieren. Es ist aber möglich, das Ganze mithilfe von IFTTT und Blynk zu bauen: https://www.instructables.com/id/GOOGLE-ASSISTANT-CONTROLLED-SWITCH-USING-NODEMCU/ dazu könnte ich mal ein an WLED angepasstes Tutorial erstellen, weil Blynk ja schon implementiert ist.
Hey, ja mit ifttt habe ich schon einiges umgesetzt; aber die weiblichen Mitglieder der Familie bombardieren die Google home Geräte mit Phrasen die ich vorher nicht angelegt habe und sind dann enttäuscht, wenn auf "hey Google, lightbox Farbe Lavendel" die Farbe dann nicht umgesetzt wird.
In cloud APIs geht's dann aber.
Vielleicht könnte man die Farben ja sprachbasiert mit rgb Werten hinterlegen? /win&color=red/rot
Any update as to having google automation? I've tried using WebCoRE with Smartthings, no luck. Couldn't do Blynk as I'm new to programming. I already set up my ESP8266 with my WS2812b lights and WLED but I want at least Google home to turn them off or on. Any other ideas? I tried adafruit but i'll have to see as I followed a tutorial and I got a bit lost
I spent a little time getting the Blynk webhook working for one of my projects. It takes a bit of leg work, but here's a write up of what I went through to use Google Assistant via IFTTT and Blynk: http://www.robopenguins.com/web-based-door-control-update/
You still have to have a local mqtt instance so this is pretty much the
same thing, wether it's Google, home assistant, openhab or rainmaker ; it's
still acting as the intimediary and you still need a local mqtt instance.
On Fri, 27 Jan 2023, 12:27 pm BrimStoneDK, ***@***.***> wrote:
Thats what I mean. This should work without a HA instance. Full control
using Google assistant. Watch the video ;)
—
Reply to this email directly, view it on GitHub
<#31 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACF5L6LAIH7HRGYDTC36SDWUMB53ANCNFSM4FH2MTMQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
Yes yes agreed. The way I understand it is there has to be some sort of code on the ESP board to be able to add it to the Rainmaker app as an IOT device. The Rainmaker app is then added as a "skill" to Home Assistant there by adding voice control. I dont care if its local or cloud or both. As long as I can use voice control.
Based on my experience with AWS IoT Core and on what I found on the web about connecting an ESP32 to AWS, I'd like to share an idea how this might work without an MQTT broker in the middle.
The solution consists of two parts:
WifiClientSecure to handle the certificates required by AWS to secure the connection
Arduino Client for MQTT for the MQTT part - this is probably not even necessary, but this example uses it. Would be worth testing with WLED's own MQTT setup
The part I can't say much about is how much effort this is to integrate, since I'm rather new to programming microcontrollers. My motivation is to get feedback on this aspect and on whether I'm missing something...
hola, estoy usando esp32 con rainmaker y te deja configurar varios dispositivos, ya que tengo varias luces con wled esp8266 y no es compatible con casi nada el esp8266, se me ocurrio usar el esp32 como master y crear varias luces virtuales en el y que cada luz virtual le envie los comandos desde rainmaker a wled por GET o por MQTT, aun no lo termino de probar pero creo que va a ser una buena solucion para los viejos esp8266 wled que tengo ya en casa y funcionan muy bien. voy a ir comentando aca mis avances y si funciona entonces publico mi codigo para que lo trabajemos en conjunto y tengamos una solucion estable y sin tanto problemas de configurar servidores en la nube.
yo estuve probando esp32 rainmaker y funciona muy bien con google home y alexa. @Aircoookie
@softhack007 This example uses fairly standard TypeScript libraries. I was worried we'd need some special SDK to integrate it, but it turns out we only need to add two HTTP endpoints and add new mDNS entry. We don't need to implement all the protocols from this code. We can only choose those we already use, namely HTTP + mDNS.
When I think about it more deeply, it seems to me that we don't need to make any changes to our device at all. The missing element is only cloud integration. IIf we limit the scope of work very much, I think a simple on/off switch for segments would be one/two day's work. but I don't have a Google Nest to work on it.
Activity
Aircoookie commentedon Jul 2, 2018
Hi,
sorry that is not possible because the Google Assistant doesn't have a local API. I'd need to have a complicated cloud infrastructure to support Google home which I can't do as a small open source project.
You can do it with the free IFTTT website though, which is compatible with google Assistant. It requires you to do a router port forwarding so the ESP8266 is accessible from the internet. Then you need two IFTTT Webhooks applets that trigger
<YourPublicIP>:<YourESPNetworkPort>/win&T=1for on and<YourPublicIP>:<YourESPNetworkPort>/win&T=0for off, respectively.Aircoookie commentedon Aug 4, 2018
This is not a bug, and there is no way for me to add native Assistant support in the near future sadly.
Therefore I close this issue now.
Feel free to reopen it if you have any further ideas :)
km-coded commentedon Jan 22, 2019
Könnte man nicht eine von Google unterstütze api integrieren? Die api von tuya smart (smart life) ist offen und soll leicht verständlich sein. Viele sub-hersteller (smart life oder auch hama) nutzen die.
Vielleicht hilft ja der link?
https://docs.tuya.com/en/cloudapi/cloud_access.html#access-mode
Aircoookie commentedon Jan 23, 2019
Könnte man überlegen. Würde sicherlich funktionieren, aber im Moment möchte ich keine cloudabhängige API integrieren. Es ist aber möglich, das Ganze mithilfe von IFTTT und Blynk zu bauen: https://www.instructables.com/id/GOOGLE-ASSISTANT-CONTROLLED-SWITCH-USING-NODEMCU/ dazu könnte ich mal ein an WLED angepasstes Tutorial erstellen, weil Blynk ja schon implementiert ist.
km-coded commentedon Jan 23, 2019
Hey, ja mit ifttt habe ich schon einiges umgesetzt; aber die weiblichen Mitglieder der Familie bombardieren die Google home Geräte mit Phrasen die ich vorher nicht angelegt habe und sind dann enttäuscht, wenn auf "hey Google, lightbox Farbe Lavendel" die Farbe dann nicht umgesetzt wird.
In cloud APIs geht's dann aber.
Vielleicht könnte man die Farben ja sprachbasiert mit rgb Werten hinterlegen? /win&color=red/rot
aenertia commentedon Dec 25, 2019
This is now possible as there is a local API exposed in the New SDK i think this should be reopened. https://developers.google.com/assistant/smarthome/concepts/local
bitterdog commentedon Dec 28, 2019
right on!
[-]Help needed Integration with Google assistant[/-][+]Integration with Google assistant[/+]Aircoookie commentedon Dec 28, 2019
Not yet looked into it in detail, but I agree that this is a promising change!
Algebruhm8 commentedon Jan 9, 2020
Any update as to having google automation? I've tried using WebCoRE with Smartthings, no luck. Couldn't do Blynk as I'm new to programming. I already set up my ESP8266 with my WS2812b lights and WLED but I want at least Google home to turn them off or on. Any other ideas? I tried adafruit but i'll have to see as I followed a tutorial and I got a bit lost
tommasopeduzzi commentedon Jan 10, 2020
Are there any updates for this feature? I'm looking forward to being able to control my lights with my google home natively!
axlan commentedon Jan 25, 2020
I spent a little time getting the Blynk webhook working for one of my projects. It takes a bit of leg work, but here's a write up of what I went through to use Google Assistant via IFTTT and Blynk: http://www.robopenguins.com/web-based-door-control-update/
54 remaining items
aenertia commentedon Jan 26, 2023
BrimStoneDK commentedon Jan 26, 2023
Yes yes agreed. The way I understand it is there has to be some sort of code on the ESP board to be able to add it to the Rainmaker app as an IOT device. The Rainmaker app is then added as a "skill" to Home Assistant there by adding voice control. I dont care if its local or cloud or both. As long as I can use voice control.
km-coded commentedon Jan 27, 2023
I've setup some IFTTT webhook, is working "okayish"
jbl-proglove commentedon Feb 10, 2023
Based on my experience with AWS IoT Core and on what I found on the web about connecting an ESP32 to AWS, I'd like to share an idea how this might work without an MQTT broker in the middle.
The solution consists of two parts:
The part I can't say much about is how much effort this is to integrate, since I'm rather new to programming microcontrollers. My motivation is to get feedback on this aspect and on whether I'm missing something...
Cheers
jbl-proglove commentedon Feb 10, 2023
Sorry, forgot to add the link to the tutorial...
leocastro5364 commentedon Jul 13, 2023
hola, estoy usando esp32 con rainmaker y te deja configurar varios dispositivos, ya que tengo varias luces con wled esp8266 y no es compatible con casi nada el esp8266, se me ocurrio usar el esp32 como master y crear varias luces virtuales en el y que cada luz virtual le envie los comandos desde rainmaker a wled por GET o por MQTT, aun no lo termino de probar pero creo que va a ser una buena solucion para los viejos esp8266 wled que tengo ya en casa y funcionan muy bien. voy a ir comentando aca mis avances y si funciona entonces publico mi codigo para que lo trabajemos en conjunto y tengamos una solucion estable y sin tanto problemas de configurar servidores en la nube.
yo estuve probando esp32 rainmaker y funciona muy bien con google home y alexa.
@Aircoookie
softhack007 commentedon Jul 13, 2023
Hi, unfortunately most people here (including myself) do not speak Portuguese, could you translate your comment into English? Thanks.
AlejandroHuerta commentedon Aug 17, 2023
Has anyone investigated Google's local fulfillment sdk? https://developers.home.google.com/local-home/overview
Merge pull request wled#31 from craiglink/tubes-only-platform-upgrade
mik-laj commentedon Mar 26, 2026
If anyone is curious, here is the code for implementing the server on the device, compliant with the Local Home SDK:
https://github.com/google-home/smart-home-local/tree/master/device
softhack007 commentedon Mar 26, 2026
... unfortunately it's written in typescript, and uses lots of libraries that we don't have on esp32 or esp8266.
The idea might help, but it's still a long way to walk, if you want to make a usermod based on this example.
mik-laj commentedon Mar 26, 2026
@softhack007 This example uses fairly standard TypeScript libraries. I was worried we'd need some special SDK to integrate it, but it turns out we only need to add two HTTP endpoints and add new mDNS entry. We don't need to implement all the protocols from this code. We can only choose those we already use, namely HTTP + mDNS.
Here is list of libraries: https://github.com/google-home/smart-home-local/blob/b60fe100d9f05292a1a9bff7962da1e49db15c72/device/package.json#L16-L24
Brief analysis of dependencies:
bonjour: ZeroConf service discovery. We currently already have an mDNS server, so this shouldn't be a problem.node-ssdp: SSDP protocol implementation. Not needed. We can use mDNSmulticast-dns-service-types: mDNS service definitions.. Not needed. We can defined service types in our code.express: Web application framework. We already have HTTP server.opc: Pixel control protocol. Not needed. It is example-specific library.cbor: Binary data format. Not needed. It is used by UDP discovery. We can stick to mDNS.xmlbuilder2: XML document builder. Not Needed. It is used by SSDP discovery. We can stick to mDNS.yargs: Command line parser. Not needed.chalk: Terminal string styling. Not needed.I agree it's a bit of work, but it doesn't seem like any libraries are blocking us.
mik-laj commentedon Mar 26, 2026
When I think about it more deeply, it seems to me that we don't need to make any changes to our device at all. The missing element is only cloud integration. IIf we limit the scope of work very much, I think a simple on/off switch for segments would be one/two day's work. but I don't have a Google Nest to work on it.
netmindz commentedon Mar 28, 2026
You can connect Google Home using #5456