[et_pb_section bb_built=”1″ admin_label=”section”][et_pb_row admin_label=”row”][et_pb_column type=”4_4″][et_pb_text admin_label=”Text” background_layout=”light” text_orientation=”left” use_border_color=”off” border_color=”#ffffff” border_style=”solid”]<\/p>\n
The Google Home<\/a> device is a standalone device that runs Google Assistant and allows you to do many things just using your voice. It has a growing base of smart home components it can integrate with and someone has created a Home Assistant<\/a> component called Emulated Hue Bridge<\/a>\u00a0that allows Home Assistant to masquerade as a Philips Hue Bridge<\/a>. What’s all that jargon mean? It means that you can set up Home Assistant to pretend it’s a Philips Hue Bridge. Devices that can interact with a Philips Hue Bridge will see it and be able to communicate with it as if it’s the real deal.<\/p>\n Google Home requires that the Philips Hue Bridge should be available on port 80. In Linux this means that you either have to a) run Home Assistant as root (not advised in most cases) or b) set up an iptables rule that will allow the user that runs Home Assistant to bind to one end of a forwarding pipe. Confused? Don’t be! It’s a relatively simple process.\u00a0https:\/\/www.cyberciti.biz\/faq\/linux-port-redirection-with-iptables\/<\/p>\n After you’ve got that figured out all that’s left to do is configure Home Assistant<\/p>\n By default the Emulated Hue component will expose things within your Home Assistant configuration and you’ll be able to control them by name. Once you’ve restarted Home Assistant make sure it’s working by going to http:\/\/<your_ip>\/description.xml and if all goes well you’ll see something similar to this:<\/p>\n [\/et_pb_text][et_pb_text admin_label=”Text” background_layout=”light” text_orientation=”left” use_border_color=”off” border_color=”#ffffff” border_style=”solid”]<\/p>\n The easiest way I’ve found to do more complicated things using Google Home is to use a template switch<\/a>\u00a0platform component but this is limited to on\/off commands. Google Home can control media player<\/a>\u00a0components but it’s not really reliable so I decided to write a template light platform. This expands what you can do by allowing you to issue commands to set the level of devices as well as turn them on and off. It should be available in the 0.46 release version. Check out a preview of the functionality below!<\/p>\n <\/p>\n [\/et_pb_text][et_pb_video admin_label=”Video” src=”https:\/\/youtu.be\/UeFDCZDZQh0″ \/][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":" [et_pb_section bb_built=”1″ admin_label=”section”][et_pb_row admin_label=”row”][et_pb_column type=”4_4″][et_pb_text admin_label=”Text” background_layout=”light” text_orientation=”left” use_border_color=”off” border_color=”#ffffff” border_style=”solid”] The Google Home device is a standalone device that runs Google Assistant and allows you to do many things just using your voice. It has a growing base of smart home components it can integrate with and someone has created a Home Assistant component […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":39,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-187","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.cribbstechnologies.com\/index.php\/wp-json\/wp\/v2\/pages\/187","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cribbstechnologies.com\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.cribbstechnologies.com\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.cribbstechnologies.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cribbstechnologies.com\/index.php\/wp-json\/wp\/v2\/comments?post=187"}],"version-history":[{"count":5,"href":"https:\/\/www.cribbstechnologies.com\/index.php\/wp-json\/wp\/v2\/pages\/187\/revisions"}],"predecessor-version":[{"id":192,"href":"https:\/\/www.cribbstechnologies.com\/index.php\/wp-json\/wp\/v2\/pages\/187\/revisions\/192"}],"up":[{"embeddable":true,"href":"https:\/\/www.cribbstechnologies.com\/index.php\/wp-json\/wp\/v2\/pages\/39"}],"wp:attachment":[{"href":"https:\/\/www.cribbstechnologies.com\/index.php\/wp-json\/wp\/v2\/media?parent=187"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\nemulated_hue:\n type: google\n listen_port: \n advertise_port: 80\n<\/code><\/pre>\n\n<root xmlns="urn:schemas-upnp-org:device-1-0">\n <specversion>\n <major>1<\/major>\n <minor>0<\/minor>\n <\/specversion>\n <urlbase>http:\/\/<Your IP>:80\/<\/urlbase>\n <device>\n <devicetype>urn:schemas-upnp-org:device:Basic:1<\/devicetype>\n <friendlyname>HASS Bridge (<Your IP>)<\/friendlyname>\n <manufacturer>Royal Philips Electronics<\/manufacturer>\n <manufacturerurl>http:\/\/www.philips.com<\/manufacturerurl>\n <modeldescription>Philips hue Personal Wireless Lighting<\/modeldescription>\n <modelname>Philips hue bridge 2015<\/modelname>\n <modelnumber>BSB002<\/modelnumber>\n <modelurl>http:\/\/www.meethue.com<\/modelurl>\n <serialnumber>1234<\/serialnumber>\n <udn>uuid:2f402f80-da50-11e1-9b23-001788255acc<\/udn>\n <\/device>\n<\/root>\n<\/code><\/pre>\n