smart-home-local | Local Home SDK sample

by actions-on-google TypeScript Version: Current License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | smart-home-local Summary

smart-home-local is a TypeScript library. smart-home-local has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

Local Home SDK sample

Support

Quality

Security

License

Reuse

Support

smart-home-local has a low active ecosystem.

It has 253 star(s) with 67 fork(s). There are 22 watchers for this library.

It had no major release in the last 6 months.

There are 9 open issues and 38 have been closed. On average issues are closed in 64 days. There are 53 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of smart-home-local is current.

Quality

smart-home-local has 0 bugs and 0 code smells.

Security

smart-home-local has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

smart-home-local code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

smart-home-local is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

smart-home-local releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of smart-home-local

Get all kandi verified functions for this library.

smart-home-local Key Features

No Key Features are available at this moment for smart-home-local.

smart-home-local Examples and Code Snippets

No Code Snippets are available at this moment for smart-home-local.

Community Discussions

Trending Discussions on smart-home-local

Understanding how javascript code is download in a google home device, for local home execution (action on google smart home)

QUESTION

Understanding how javascript code is download in a google home device, for local home execution (action on google smart home)

Asked 2020-Feb-17 at 10:03

I try to understand how my javascript code that handle local execution bahavior is download in my google home mini. I know I give an url towards a server or a web page here :

Action google interface

And this code is used in my google home to handle local execution but I just put my web page url here, in the test tab. So if I want to deploy my app in a production environnement, how will i do that ? I did not see any other place to put the url toward my code.

I red this page: https://developers.google.com/assistant/smarthome/concepts/local

And followed this tuto: https://github.com/actions-on-google/smart-home-local

Thanks for your answers.

...

ANSWER

Answered 2020-Feb-17 at 10:03

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

Source https://stackoverflow.com/questions/60188710

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install smart-home-local

Configure the cloud service to report the correct device SYNC metadata based on your chosen device type and control protocol. Here are some examples for configuring the service for different use cases:.
Report a single device (strand1) controlled via UDP commands: npm run firebase --prefix functions/ -- functions:config:set \ strand1.leds=16 strand1.channel=1 \ strand1.control_protocol=UDP npm run deploy --prefix functions/
Report three individual light strands connected through a proxy (hub1) and controlled via HTTP commands: npm run firebase --prefix functions/ -- functions:config:set \ hub1.leds=16 hub1.channel=1,2,3 \ hub1.control_protocol=HTTP npm run deploy --prefix functions/
The companion virtual device is a Node.js app that emulates strands of RGB LEDs controllable using the Open Pixel Control protocol and displays the results to the terminal in a colorful way. Note: The virtual device needs to listen on the same local network as the Home device.
Virtual device discovery settings must match the attributes provided in Device Scan Configuration in Develop > Actions > Configure local home SDK. If you modify the attributes in your Device Scan Configuration, you must configure the virtual device accordingly. See the virtual device README for more details on configuring the discovery attributes.
Virtual device control protocol should match control_protocol used with functions:config:set when setting up cloud fulfillment.
Configure the device type as end device or hub/proxy based on the number of --channel parameters provided. A device with more than one channel will be treated as a hub.
Start the virtual device as a single device (strand1) discovered via UDP broadcast and controlled with UDP commands: npm install --prefix device/ npm start --prefix device/ -- \ --device_id strand1 \ --discovery_protocol UDP \ --control_protocol UDP \ --channel 1
Start the virtual device as a hub (hub1) discovered via mDNS and controlling three individual strands with HTTP commands: npm install --prefix device/ npm start --prefix device/ -- \ --device_id hub1 \ --discovery_protocol MDNS \ --control_protocol HTTP \ --channel 1 \ --channel 2 \ --channel 3

Support

Make sure the Google Home device, the virtual device and your workstation are on the same network.Make sure to disable any firewall running on your workstation.

Find more information at: