{"action":"closed","issue":{"url":"https://api.github.com/repos/OttoWinter/esphomeyaml/issues/20","repository_url":"https://api.github.com/repos/OttoWinter/esphomeyaml","labels_url":"https://api.github.com/repos/OttoWinter/esphomeyaml/issues/20/labels{/name}","comments_url":"https://api.github.com/repos/OttoWinter/esphomeyaml/issues/20/comments","events_url":"https://api.github.com/repos/OttoWinter/esphomeyaml/issues/20/events","html_url":"https://github.com/OttoWinter/esphomeyaml/issues/20","id":326733873,"node_id":"MDU6SXNzdWUzMjY3MzM4NzM=","number":20,"title":"Feature request: Specify custom target IPs for OTA update","user":{"login":"simonszu","id":700707,"node_id":"MDQ6VXNlcjcwMDcwNw==","avatar_url":"https://avatars0.githubusercontent.com/u/700707?v=4","gravatar_id":"","url":"https://api.github.com/users/simonszu","html_url":"https://github.com/simonszu","followers_url":"https://api.github.com/users/simonszu/followers","following_url":"https://api.github.com/users/simonszu/following{/other_user}","gists_url":"https://api.github.com/users/simonszu/gists{/gist_id}","starred_url":"https://api.github.com/users/simonszu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/simonszu/subscriptions","organizations_url":"https://api.github.com/users/simonszu/orgs","repos_url":"https://api.github.com/users/simonszu/repos","events_url":"https://api.github.com/users/simonszu/events{/privacy}","received_events_url":"https://api.github.com/users/simonszu/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":8,"created_at":"2018-05-26T12:14:45Z","updated_at":"2018-11-27T22:31:37Z","closed_at":"2018-11-27T22:31:37Z","author_association":"NONE","body":"Following some best practices, i have separated my IoT Devices into a separate VLAN, which also has a separate SSID in my Wifi access point. I don't want to impute writing malicious code to you, @OttoWinter , but it was easier for me to put the ESPs into this VLAN as well, for firewall ruling and similar actions. \r\n\r\nTo cut a long story short: Another VLAN is another broadcast domain, so the resolving of <hostname>.local during OTA process is failing. The ESP host itself is pingable via its IP address and even via internal DNS, since i specified an entry for it. So it would be great to have an option in the YAML file to specify a specific IP address or hostname for OTA, so that esphomeyaml isn't sending the invitation to <hostname>.local but merely to the specified IP address. \r\n\r\nIf one does not explicitly specify this option, trying <hostname>.local would be a good fallback option. \r\n\r\nOn a somehow related side note: Is port 13564 for the OTA server to listen on a fixed value? I need to specify a firewall rule to enable talkback from the IoT VLAN to the VLAN where my desktop PC resides. "}}
{"actor":{"display_login":"OttoWinter"}}