smart-home | Smart home config ( RPi , ESP , many sensors

Yes, the implementation of your backend can be designed however you want. You also are not restricted to using Cloud Functions or App Engine. While the end-to-end sample provides one example of how to do it, your backend just has to implement a webhook and respond to intents plus have support to do things like report state.

The API reference contains all the information you needed to build a custom implementation.

A potential solution is VLC (https://www.videolan.org/). VLC has an optional web based frontend, where the media player can be controlled, that is running on the server. It is very basic but plays the audio file. If you know other solutions then please leave another answer.

How to enable the VLC WEB frontend:

1. Open 'Preferences' from the menu
2. At the bottom-left, click 'Show All'. This will show you all VLC configuration
3. Select 'Interface'/'Main Interface' from the list
4. Tick the 'Web'
5. Select 'Interface'/'Main Interface'/'Lua' from the list
6. Add a Password under 'Lua HTTP'. You will use this password without user name - yes, I did not find a way to set user name but password is mandatory - to access the web frontend.
7. Re-start your VLC
8. Open a browser from a device from your LAN
9. Enter the 'http://your_IP:8080' to your browser. For example, http://192.168.1.2:8080
10. Enter your password that you set at step 6., but leave the user name blank

I have tested it with:

• Server: Raspberry PI 3
• OS: Raspbian GNU/Linux 10 (buster)
• VLC: 3.0.11 Vetinari
  • Works with VLC running as GUI application (/usr/bin/vlc)
  • Works with VLC running as a background process (/usr/bin/cvlc/)
• Sound: Well, my screen has some sort-of speaker. Audio was coming out it via the HDMI of my RPI
• Client, where the VLC was successfully controlled from
  • My laptop
  • My smartphone

Some pros:

• Free, open-source
• Configuration and startup is easy
• Frontend is available for both desktop and mobile

Some cons:

• Equalizer is not yet supported
• Frontend is very basic
• Volume cannot be properly controlled from phone: could not slide the slider, but sets the volume to the position where you click on the slider
• Phone: Cannot play all media files in a folder when the folder is clicked. It just played the first, so had to write some shell script to generate playlist files for each and every folder
• Did not find a configuration within VLC to change the default port from 8080 to 80 or to 443 for SSL.

Further guidance for customisation:

• The files for web frontend are stored in /usr/share/vlc/lua/http folder. It uses html, json, xml, js, jquery and this sort of stuff so you should be able to customize it for yourself given you understand the basics of these technologies and languages.
• There is a button on web-frontend that shows you all your files in your home folder. You can navigate to anywhere with it, that raises security concerns. Well, and it is not too nice to wander away from your media files.
• Here you can set your default folder: /usr/share/vlc/lua/http/js/controllers.js

The Device Manager sample app you are working with registers the data scanned from a device QR code to the pending Firestore collection until until the backend can establish that the data provided matches an existing valid device in Cloud IoT Core (see the relevant code).

If you are able to successfully register a device to pending but it's never removed from that collection, then the issue is in that code path somewhere. The cloud function logs should provide some insight into why your code is failing there (e.g. invalid credentials, bad configuration, etc.)

You might also find this blog post helpful, which overviews the architecture of the sample code's use case.

As mentioned briefly in the comments, this is likely because your project is failing to successfully call Report State. The most likely cause of this is that your Home Graph API credentials are missing or incorrect.

In the current sample code, an error in this method call will cause the handler to return deviceOffline from a QUERY. You can also comment out or remove this line to debug the issue.

That page is loaded dynamically using javascript, and the sample html in your question is a result of that. Absent some trickery (you can search around for scripts to handle dynamically loaded pages), GS can't retrieve that data.

Fortunately, not ALL data is loaded like that. If you disable JS on that page, you will get most of the same data, including the info; only this time - it looks like this:

At the moment the Google Home app does not update the state in realtime. If you close and open the app, you should see the state change.

If you call the Report State API and get a 200 response code, then you've done it right.

Finally, i found my response. For now, local execution is just in preview. So no production management is implemented yet.

You have to put this code in your html. it will helps you. Output of this code is ,if email is too large than dots is appear and on hover full email is display.

Finally found the answer.

It wasn't too far from the one I had posted above. Although my problem is that when I generated an API key, the google home cloud console opened the wrong project by default. I had the wrong API key all along.