| { | |
| "meta": { "theme": "elegant" }, | |
| "basics": { | |
| "name": "Sebastien Vayrette-Gavard", | |
| "label": "Sr Technology Specialist", | |
| "email": "vayrette@gmail.com", | |
| "phone": "(905) 808-6907", | |
| "summary": "Having a real passion for everything IT, I turn challenges into learning opportunities. Working in the field for as long as I can remember, my first experience started hands-on as I learned how to assemble and connect computers.\n\n As the years have passed, I continue to explore the many topics that the IT world has to offer. I usually spend my day around Ansible, Consul, Jenkins, Terraform, Docker, and most recently, Kubernetes. Along with a chatbot, they enable me to quickly deliver self-serve pipelines in order to provide teams around the organization with anything from bootstrapping a new on-premise or cloud environment, triggering a build, deploying a release or switching to a disaster recovery site.\n\n Currently, I have strong experience in designing data-centers and networks, maintaining in |
Until recently, the Google Home app used to communicate with the device over port 8008 (HTTP) and did not require any authentication. Everything in the unofficial documentation worked as expected.
A few days (weeks) ago, Google pushed a new update to all GH devices and all endpoints (except /setup/eureka_info) started returning 403 (forbidden) errors. The app had switched over to port 8443 and HTTPS.