I did in fact enable USB 3.0; and I was able to select my Z-wave dongle from the list in the drop-down below.
As for the IP, I was trying to connect to the VM address; my existing HA system is running on a RPi with IP 10.0.0.57.
EDIT: I use duckdns and my snapshot includes that. Everything seems to work fine until loading the snapshot. I have set up the VM at least four times now, each with the same result.
Can you explain this comment: “you need to change ip_syno to the ip your VM got…” I know the new IP assigned to the VM and am attempting to access it at port 8123 via the browser. I can ping that IP. Is there something else I need to do?
step 2 - then try a snapshot from the old configuration
reassembling from snapshot may take longer, so be patient
if you have duckdns in the old snapshot, you also have it with the domain you are using on RPi, so try to open a port for ip_address_vmm:8123 on the router
for sure close the port for ip_rpi: 8123 or change it to others, eg: 8124, but before that you have to add to configuration.yaml (on RPi) next:
http:
server_port: 8124
then try logging in with your domain _ _ _. duckdns.org:8123 to new HA and old HA (RPi) should be go on address _ _ _. duckdns.org:8124
Well, that is the problem. I can connect to the new HA instance easily to restore my snapshot. After that, I can’t connect to the new HA instance at all. I get the error as shown in the browser window above.
I created a new HA installation on VMM last night. It’s assigned IP address 10.0.0.219. I connected to 10.0.0.219:8123 and selected my snapshot to restore. I left browser window open (unnecessary, I know) to restore overnight last night (figure 7 hours). In the morning, the browser still showed “restoring,” until just a few moments ago. I refreshed the browser–URL 10.0.0.219:8123–and it shows the same error as shown in my screen shot above.
I have shut down the VMM and restarted. It picks up the same IP address, but that doesn’t work either. Now, as HA is starting up on VMM, I get this page:
That’s pretty typical of HA while it’s loading up. I’ve seen that before when bringing up IP:8123 right after a restart. But before too long, I see the, “this page isn’t working” error.
Not sure where to go from here. The issue appears to be in my snapshot, but it’s working just fine on my RPi.
I’ll change my router port forwarding and see if that changes anything. What I don’t remember how to do is change the port on my RPi instance of HA… it’s not in config.yaml under http. I’m sure I did it through the UI somewhere, or it’s defaulted and the only place to change it is in config.yaml.
I figured since I’m only accessing locally, duckdns wouldn’t be a factor.
Ahhh… I’m up and running. There was some IP or port conflict, somehow, that was preventing my VM instance of HA from loading. Thank you.
Now I just need to find the path for the Z-wave USB on the Synology so I can change it in ZwaveJS.
EDIT: it’s /dev/ttyS1, but none of my devices are available, yet. Now I’m running into this error.
EDIT 2: OK, it’s working now! But with /dev/ttyUSB0? That’s not what dmesg grep | tty shows me. But… whatever. It’s working. My first Z-wave device took 3-4 seconds to respond, but everything else is much faster, so I’ll just give it some time, some updates, and some reboots to see if that fixes things. Thanks again! I bought @fredrike a beer and would like to do the same for you. Please let me know how.
Hello guys,
I tried to move docker version to vmm version. I’ve got the first screen that HomeAssistant ready. Then I chose to restore from a snapshot. After that the only answer quite long ago: " homeassistant.local refused to connect.".
In Docker container I can open log or terminal and see what happens. Please advise how to track errors or the current conditions in the virtual machine? I pressed “Connect”, used “root” for the login and see “ha >”. What can I do now?
This sounds exactly like the issue I was having yesterday… see above.
@blavak68 correctly diagnosed my issue. Ultimately, the snapshot introduced the existing IP:port configuration from my old HA instance, which caused a conflict. The final fix for me was to remove the old HA instance from the network. It took some time and reboots for my router to purge the IP address and forwarding rules.
After long long waiting, HomeAssistant started normally and everything Ok now. I was patient But as I mentioned, I would prefer to see logs and commands flow to understand that process is going, and I need just wait.
Would you please recommend the optimal settings for virtual machine for home assistant with several addons like Node Red, Esphome, Mqtt, Deconz? I set 3Mb memory and 2 cores. Maybe one core is enough on DS 218+…
All these can be extended if your usage calls for more resources.
They also write:
Note: You are free to assign as much resources as you wish to the VM, please assign enough based on your add-on needs)
I don’t have any performance issue on my DS716+II with 1 vCPU and 2 GB ram. But I’m just using HomeAssistant-OS to run addons (have not taken the time to migrate my 5 years old Docker instance yet).
The problem is, that VMM always somehow unmounts the USB Dongles. You need always to edit your VMM, go to “Others” (look the picture i attached) and add the deconz stick. Somehow you have to do this everytime the VM restarts… is there a ways to automate this maybe @fredrike?
This happens to me too. Every reboot of the VM I have to check the USB devices. Sometimes they stick, sometimes they have to be manually selected again.
I would like to delete home-assistant_v2.db file. Sometimes it’s necessary when homeassistant can’t start. Please advise can I do it?
I opened VMM in Synology, pressed “Connect” button, logged in with “root” and see “ha >” invitation. But it allows to run “ha” commands only. I can’t do “rm” command. If I try to connect to VM with ssh, it refuses connections
Please help and describe is it possible to work with core files over ssh?
to serge
i installed the supervisor addon sambashare in Home Assistant.
Go to top of the sambashare-card chose configuration
add username and password.
Password in quotation marks.
under allow_hosts in the config-file:
I added the ip of my synology and the ip of the VM. It works.
Click on save and start sambashare.
If you use windows:
go to add a network address
then next
in this window you have to put in the network-address from your HA-VM without :8123
like this example: \\192.168.179.201 (please take your ip-address)
Then start search and click on the ip of your VM
After this you choose the config folder.
Click on ok.
Now you can work per copy and paste.
I think it is similar with an Apple-system.
But as I mentioned, I would prefer to see logs and commands flow to understand that process is going, and I need just wait.