{"id":3309,"date":"2023-02-15T02:16:10","date_gmt":"2023-02-15T10:16:10","guid":{"rendered":"https:\/\/192.168.1.30\/wordpress\/?p=3309"},"modified":"2023-02-15T02:16:10","modified_gmt":"2023-02-15T10:16:10","slug":"homeassistant-put-some-ass-in-your-home","status":"publish","type":"post","link":"https:\/\/spiffynasty.com\/blahblahblah\/homeassistant-put-some-ass-in-your-home\/","title":{"rendered":"HomeAssistant | put some ass in your home."},"content":{"rendered":"

Keep having connection issues – it works – then without an changes from me – it’s down.<\/p>\n

NOTES:<\/h2>\n

When you are bridged, the virtual machine asks the router directly for an IP address and can have ports forwarded to it. (Don\u2019t forward 8123 to it, if you have port 443 working). When you set the mode to NAT, it doesn\u2019t ask the router for an IP address Virtualbox gives it an IP address inside the Virtualbox ONLY network, in this mode you would need to port forward to the PC running virtualbox, rather than to the virtual machine itself – though I am not entirely sure how this configuration works myself to be honest, because then you are dealing with double NAT which makes everything a headache to troubleshoot. I believe when you are using the NAT mode, that you need to access Home Assistant via it\u2019s NAT IP which you probably can\u2019t do – because the SSL certificate will probably complain.<\/p>\n

Virtual box on NAS<\/h2>\n

https:\/\/www.asustor.com\/en\/online\/College_topic?topic=249<\/p>\n

So I think if you take the homeassistant ip and add the port from here 3389 you can ssh into the machine.
\n<\/p>\n

\r\nssh -p 2222 user@host\r\n<\/code><\/pre>\n
\n\"\"<\/p>\n
Install Home Assistant<\/h2>\n