hi i done all correctly but when i do ls/homeassistant/config, i got "ls: cannot access '/homeassistant/config': No such file or directory ", instead if i do only ls/homeassistant it gives me the foru file, (automations.yaml , blueprints ect...), but when i do hostname -I i got an ip that doesn't work on my browser
Hello, thank you for your good tutorial. Unfortunately not working on my RPI5. Could be the rpi4 image I used problem? Is it going to come also image for rpi5?
Hi very good explain . Please let me know how i can send 2 or more same time from sender and receiver show it ? I want send from ESP32 2 messages 1 message with char and another one send temperature . How i can receive with ESP8266 ? Thank you .😮💨😮💨
Great video! I followed your steps and its working but i cannot access HA outside of the VM. I disabled the firewall but no luck. let me know if anyone can help?
Great video, apart form I get as far as: dpkg -I homeassistant-supervised.deb and I get: root@Homeassistant:~# dpkg -i homeassistant-supervised.deb (Reading database ... 31653 files and directories currently installed.) Preparing to unpack homeassistant-supervised.deb ... [warn] [warn] If you want more control over your own system, run [warn] Home Assistant as a VM or run Home Assistant Core Errors were encountered while processing: homeassistant-supervised root@Homeassistant:~# and nothing else happens. Any help please?
Thanks! I would recommend checking out the written article for the latest steps, as there I can more easily keep things up to date when the HA devs change things: siytek.com/home-assistant-macos-utm-debian-12/
@@siytek Thank-You. I have gotten it up and running. Although now have a Critical warning message in HA - "Unhealthy system - Not Privileged System is currently unhealthy because it does not have privileged access to the docker runtime" and not sure what to do? Any help greatly appreciated.
@@mexicomatt212did you install Debian 12 (rather than Debian 11) and the latest version of Home Assistant? From memory, I think this error can occur when Debian is out of date, compared with the version of HA running on it.
@@siytek I followed your guide, so would of been Debian 12. I have since bee nadvised to just install Home Assistant OS, not the Supervised version, so I am going to try that. But massive thank-you for the video and responding to me.
might be a silly question but i'm new to this. After following all of your steps,i was able to access HA. however, when i closed the VM to change the network setting to bridged, i opened the VM again but couldn't access the HA ip on my browser. I tried to access HA on my browser using the same ip/port. am i doing something wrong? if i change back to shared, it works.
Thanks for the tip, print should work fine for sending text. What error are you getting when using write? I tested this code recently but forgot if I needed to make any changes, maybe check the most recent code on the blog post: siytek.com/esp8266-udp-send-receive/
Thank you for such a great tutorial. I have tried so many way to install home assistant on my HP thin client and always bumped into errors. By following your step by step process, Finally get it running. You are a good tutor
I wonder where are all my Dashboard raw codes are located. my COnfiguration.yaml is as empty as yours and the include files specified in the Configuration.yaml is also nearly empty
@@FifiGiulaHakim"apt install wget udisk2 -y" to install missing packages, although not sure why they are missing? This video is a little out of date now, easier to keep things up to date on the blog, see here for the latest and current method: siytek.com/home-assistant-macos-utm-debian-12/
I use 'dpkg -i --ignore-depends=systemd-resolved homeassistant-supervised.deb' to fix the systemd-resolved error. But i got the Error.(I installed homeassistant-supervised (1.5.1)). Could you please help me? [warn] If you want more control over your own system, run [warn] Home Assistant as a VM or run Home Assistant Core [warn] via a Docker container. [warn] [warn] ModemManager service is enabled. This might cause issue when using se rial devices. Leaving 'diversion of /etc/NetworkManager/NetworkManager.conf to /etc/Networ kManager/NetworkManager.conf.real by homeassistant-supervised' Leaving 'diversion of /etc/NetworkManager/system-connections/default to /etc /NetworkManager/system-connections/default.real by homeassistant-supervised' Leaving 'diversion of /etc/docker/daemon.json to /etc/docker/daemon.json.rea l by homeassistant-supervised' Leaving 'diversion of /etc/network/interfaces to /etc/network/interfaces.rea l by homeassistant-supervised' Unpacking homeassistant-supervised (1.5.0) over (1.5.0) ... Setting up homeassistant-supervised (1.5.0) ... [info] Restarting NetworkManager [info] Enable systemd-resolved dpkg: error processing package homeassistant-supervised (--install): installed homeassistant-supervised package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: homeassistant-supervised
Thank you so much but I would like to make project that , Iwill connect nma0183 serial data by cable to esp 8266 then send it as UDP signal by wifi to read on pc (I have program accept udp package) without internet.Iwant to remove cables. Could you help me how to do that?I don't know how to write any code.
If I pay for this version: "Try this QUICKER and EASIER way to get Home Assistant running on your M1 Mac" Did I get a full home assistant experience or some light version?
Im running a Homeassistant Container on a VServer. Is there an easy way to get access from another machine, without using the Homeassistant interface? VServer is running on Debian, ssh connection works from external windows pc but i cannot access on the address.
I had the same - I tried not deleting the display device (at 2:30 in the video) and don't add a serial device. Then I didn't get the "ERROR: no suitable video mode found". Then I could continue. (2014 Mac mini). Now I'm stuck on the OS-Agent install 1.5.1 from Github - says it's the wrong version - Arm64 instead of AMD64. tried both no luck. If you get that far let me know id you solve it.
@@karloshagen4037 I have found this problem to occur on Intel Macs, are you using Apple Silicon? You can do as the OP suggested and skip the part creating a serial terminal and instead leave the standard display adapter there.
A potential fix for this issue is to edit the GRUB configuration: 1) add the display adapter in UTM as described by the OP 2) boot Debian and log in 3) run "sudo nano /etc/default/grub" 4) edit the line so it is as follows: GRUB_CMDLINE_LINUX="console=ttyS0" 5) save and close with ctrl + x 6) update grub with "sudo update-grub" 7) reboot 8) At "booting in blind mode" wait a moment and you should end up at the login. 9) optionally you can remove the display adapter from UTM settings
Thank's for guide. Anyone been running HA in a UTM VM for a while? How stable has it been? I see that on the UTM website is says base M1 chip kernel panic. I'm using a Mac Studio seems to be running good so far.
I have been using UTM for a while now for many different purposes and I find it very reliable, most likely because it is based on QEMU. A few versions back I found experienced a little crashing with the UTM GUI, but this seems to be resolved now. IMO it is reliable enough for Home Assistant :)
thanks for the tutorial. Homeassistant is up and running now. However, the HomeKit integration doesn't work - the iOS Home App cannot connect to home assistant. Firewall / UTM settings issue?
Yes it will probably be related to the UTM network settings as by default the external network cannot see the virtual network created between UTM guest and host OS's. Give this a try... siytek.com/home-assistant-supervised-on-mac/#give-your-home-assistant-vm-a-seperate-ip-address
Will using VirtualBox and installing the HAOS Installation method cause any problem? I guess adding bridged mode in network, assigning 2 cores and 2GB RAM on M1 Macbook will do the job! I just don't want the hassle of installing debian and docker.
Just a little update on this topic, VirtualBox now supports Apple Silicon, so you could use the VBox images provided on GitHub: osxdaily.com/2022/10/22/you-can-now-run-virtualbox-on-apple-silicon-m1-m2/
