Michel Kohanim

@larryllix, It should create a local LAN network using Thread. But, so far, it has not been very reliable. With kind regards, Michel

Ah, apologies @tazman! We'll figure it out. With kind regards, Michel

@carealtor, I don't know much about HA and SkyConnect. What I know is that our Matter implementation is working excellently with one huge roadblock: Matter commissioning requires Bluetooth connectivity (or WiFi). For Bluetooth, they use BlueZ which is a behemoth of code and very difficult to manage. What we did was to go directly to the HCI level so that things are a little cleaner and without all the gonk from BlueZ. Still a few bugs but very very close. With kind regards, Michel

@Edmund Lam, sudo efibootmgr -v This will let you know which disk the OS was booted from. With kind regards, Michel

@Whitehambone, Not in this release but in the next you will have: - Volume Control - Online/live streams - Bluetooth speakers I love it myself! With kind regards, Michel

@tazman, Please submit a ticket with the exact issue and logs. With kind regards, Michel

@Merlin, If this happened all of a sudden, then I strongly recommend moving your PLM to a different outlet and one which is not shared with other transformers and power supplies. In addition, if you have any INSTEON thermostats, unplug them (take off the faceplate) and also unplug SwitchLincs version 35, KeypadLincs 2A and 2D. With kind regards, Michel

@tosterhouse, You should not have to reboot anything. What's your ticket #? With kind regards, Michel

Should have support for most of these in the upcoming isy release. With kind regards, Michel

Yes. With kind regards, Michel

Hello all, https://developer.isy.io/blog/eisy-way ... added scripts to make configuration eisier 😉. With kind regards, Michel

Hello all, https://developer.isy.io/blog/eisy-way With kind regards, Michel

@Edmund Lam, Unfortunately, it does not work this say, neither do I understand the having a vlan if it can be accessed from another vlan. What's the point? With kind regards, Michel

@carealtor, It's possible but I am not sure how to deal with support as we are (nor do we have resources) to address HA installation/configuration issues. Also, considering the cost of NVMe to be at least $74, it would make the cost of eisy astronomical. But if there's enough demand, we'll definitely consider. With kind regards, Michel

Ah, I see. Thank you for the suggestion and I agree! With kind regards, Michel

@ndfan77, This is great. What's the issue now? With kind regards, Michel

Great, now: sudo pkg update -f With kind regards, Michel

@ndfan77, Please try : curl -s https://pkg.FreeBSD.org and let me know what you get. With kind regards, Michel

@ndfan77, I need to know the contents of: cat /usr/local/etc/pkg/repos/FreeBSD.conf With kind regards, Michel

I am not sure I understand why you wouldn't have the correct pkg repos. vm-bhyve is a very well known package from FreeBSD repo. Have you changed those? If not, are you sure you have access to the internet? With kind regards, Michel

@stevesreed, Apologies, I forgot that udx service starts/stops this service. With regard to refresh, What's pkg refresh? I have never seen that before and it's not a command for pkg. Do you mean: pkg update With kind regards, Michel

Yes and Almost. I did my own testing and decided against the mirror. It was still better performing than eMMC alone but, in some instances, mirror-less performed much better (massive disk writes). With kind regards, Michel

@sjenkins, BIOS/efi labels = if you are attached to a monitor + keyboard, when you boot up, you can keep clicking the F7 button and you get the boot up menu. Without the labels, they look like (A443333/533324) ... with the labels, they look like: eisy.nvme.boot.loader eisy.boot.loader (original eMMC) With regard to the script, it will destroy everything! This said, you will be asked whether or not you want to proceed. With kind regards, Michel

They should be pretty simple to support. Is there any developer documentation especially for discovery? With kind regards, Michel

@Edmund Lam, What exactly is your use case? The way eisy works is this: If you have not setup WiFi, then always Ethernet. If you setup WiFi, then eisy will use WiFi as long as Ethernet cable is not connected. If you add your own WiFi dongle, then you are on your own because it has never been tested. The reason we don't use wlan0 is because we are using a Wifi 6 driver in a VM. With your dongle, you will NOT get WiFi 6. With kind regards, Michel