tibbar

After submitting a ticket @Michel Kohanim fixed it. Don't know what happened but it looked like there was some kind of update. Anyway up running now thanks to outstanding support from UDI. Thanks @Michel Kohanim.

Yes Just did.

Yes that is what I thought. Yesterday I was on 5.8.4. Didn't try updating myself. Multi function button does not respond. Tried 4,5 and 6 presses , no effect. The router shows port connected, some traffic exchanged but no IP.

Yes all of the above, even moved to a different router - same result.

This morning my EISY went offline and appears to be dead. Here is a pic on HDMI monitor connected to it. Can anyone give any pointers please. No IP address, no matter I do.

I thought we already had this conversation.

WELL... This is a quote I received from Michel with a ticket I submitted to UD: We don't currently support LR mode. So I guess don't matter the certification. Lol.

Just in case anyone is interested @Michel Kohanim confirmed : ZMatter USB: Z-Wave+, Zigbee, and Matter Module for eisy (Z-Wave+ Certified – Long Range) does not support Long Range mode.

DO I dare to reboot EISY? LOL

WE ARE UP AND RUNNING . Thanks @apnar for your script and your time.

Dooh - use EISY IP. lol Dont know how but HA have started.

Router (I,m using pfsense) does not list anything with MAC address of VM. How do you connect to vnc if you do not know IP address?

Remove a lock? Does it mean to delete run.lock file from /storage/vms/homeassistant/ directory?

[admin@eisy ~]$ sudo vm list Password: NAME DATASTORE LOADER CPU MEMORY VNC AUTO STATE homeassistant default uefi 2 2G 0.0.0.0:5900 Yes [1] Locked (eisy)

Should I start over?

I was not able to log in to HA. "Running" was stated by "info homeassistant" command but it did not show any network info. After rebooting it shows "stopped" like the screen shot above.

In all my previous attempts I had same thing happened. Initially right after running a script info homeassistant showed it running but after restarting it always says "stopped".

Yes

That is what I tried before running your script. No matter what I could not "destroy" homeassistant until I did: bhyvectl --vm=homeassistant --destroy

My latest attempt was with script created by @apnar

Hello. After multiple attempts I still can not get HA to run on NVMe. If I try to start HA I get an error saying: ! guest appears to be running already. IF I try to stop it I get : /usr/local/sbin/vm: WARNING: unable to locate process id for homeassistant Can someone please help.

Correct zwave-js only supports it from v9.10.0. Yes I know long range do not mesh (beam). I have a greenhouse that is fair distance away and it works much better in long range mode. Any idead how to use it in EISY?

I do not think it matters if it is 800 or 700 series chip when including Zwave Long Range in Home Assistant. It is just a different process of doing the inclusion and it is just on HA side nothing to do with zwave device so I was wondering if there is a special process of doing it in EISY.

@Techman Sorry for being kind of a jerk. I was just being so irritated and frustrated getting everything working (ISY to EISY and Home Assistant).

No offence but... really? When you do not have an answer you just type? That is the second "answer" you gave me. Isn't dongle called : (Z-Wave+ Certified - Long Range). It has nothing to do with Zooz it works fine. I know what chip they use. Works fine in "Long Range" mode with Home Assistant.