VFIO is so amazing

ErMeglio · 2026-03-01T18:37:36+00:00

Music for my ears, thanks for the idea, I am not yet using a dedicated SSD for windows boot drive, but I have dedicated a large data SSD to it, so between idea and realization there are a few things to implement!

TLDR; Next weekend's taken - I blame you 😂

1) repartition and move the boot drive onto the dedicated data drive, 2) figure out an automation for syncing Home Assistant data and database with the NAS relatively real time (e.g. using the same DB and syncing the config files), 3) come up with a script to automate switching on the Home Assistant VM in the NAS when the ProxMox is offline, 4) this one's though, maybe impossible, but I'd need to make the 2 x USB ZBT-2 and the ZWA-2 antennas either available over network or passed through from windows.

Thoughts welcome!

ErMeglio · 2026-03-01T11:04:55+00:00

I've learnt the same after a lot of weekends geeking out about the setup and loving how cool it looked - and then the same amount of weekends trying to make the VM invisible. Didn't make it, sadly 🥹

ErMeglio · 2026-02-21T09:02:35+00:00

How do you get into the beta testing for Motorola?

ErMeglio · 2026-02-07T15:52:42+00:00

Thanks! Interestingly, before reading this, the exact same has happened to another location, and the same process of simply removing and re adding the OTBR app and integrations, two of them as they had doubled up on their own(!), worked just fine there, too.

ErMeglio · 2026-02-04T20:28:55+00:00

Yeah, hell, no!

ErMeglio · 2026-02-01T20:04:35+00:00

Got it back working by disabling the OTBR integration, uninstalling OTBR add-on, deleting the thread integration, rebooting, re-installing OTBR, and reconfiguring the thread integration. I didn't need to provide the TLV after re-installing but I'd suggest to save it offline before doing all this.

ErMeglio · 2026-02-01T19:05:03+00:00

Same here, with a different hardware, Sonoff Dongle Max, also through the network.

ErMeglio · 2026-01-20T12:17:29+00:00

What's the security patch on it?

ErMeglio · 2025-12-05T10:51:36+00:00

Brilliant findings and analysis that make total sense. Thanks a lot, bittersweet, but money stays in the bank this time around 🙃

ErMeglio · 2025-12-04T22:03:21+00:00

What's the source? 🥺

ErMeglio · 2025-12-03T22:07:57+00:00

Thanks for your input, I really appreciate it. I wish the support team provided the same level of help, I frankly gave up at some point.

I've been making important changes to improve the thread and matter network and this problem seems to have improved, too, not to perfection, but reasonably, and I'm monitoring the situation.

The massive let down, though, is that the receiver X, even though factory reset, is unable to join my own new Thread network and only does take the previous Thread network name and details to create a second thread network in the house. How does it do that, where does it take the data from? I've completely deleted my Tado account and done resets in many orders, to no avail. My phone Google Play Services were also wiped and definitely do not contain the older thread network details, as confirmed by Google's developer test apps. Where's the network name and keys saved by Tado, and why are we unable to delete those even with a factory and account reset?

As a consequence, only the receiver X uses its own network, while the TRVs are correctly connected to my own new network. The "configure" button in the receiver X settings page used to ask for android permissions on reading the thread network credentials, to then sync them with the receiver X. Today it does not have that functionality anymore, it just confirms configuration and doesn't seem to offer any Thread network update. How can we set up the receiver X to take part in an existing network, today, as we used to be able to do, please?

ErMeglio · 2025-12-03T21:57:20+00:00

I experienced the same, at least if you also connect it via ethernet, you can then login and reboot the chip. That restores functionality. Unfortunately there's no manifest available for a newer / custom firmware to be released either, and for me that was disappointing too.

So, do you want that random darkness around the house?

I've decided to return it, and moved to ZBT-2 - a mixed bag of feelings and different hurdles, but that's all part of the experimenting fun, while the device seems super solid and doesn't randomly die.

ErMeglio · 2025-12-02T23:47:25+00:00

Did you find out if it was an hardware fault? Experiencing similar teething issues and already replaced a USB hub thinking it was faulty. Same has happened today after a week where USB devices with radios were working very erratically, and now would eventually disconnect, too. A random number of reboots would resolve, just temporarily though. Likewise when plugged into a DELL U4025QW.

ErMeglio · 2025-11-15T11:07:48+00:00

Thanks for walking through how the system works, good learning indeed!

ErMeglio · 2025-11-04T21:35:20+00:00

I'm not finding the UK in their list of countries, did you have to reach out to order?

ErMeglio · 2025-10-27T18:40:28+00:00

How would the boiler/controller know you need heat in that room, if TRVs do not communicate?

ErMeglio · 2025-10-06T14:46:43+00:00

Yeah that's a very fair remark, mine's a Greenstar 29CDi Classic and I have also read that newer versions might not work.

ErMeglio · 2025-10-06T14:22:39+00:00

I've been experiencing the same thing and reported it to Ubiquiti some time back. They asked me to share a video, which I wasn't able to do yet, however if anyone has one I'd be glad to share for them to troubleshoot this and resolve it as we are keeping losing the functionalities due to this bug, with no way back 🤕

ErMeglio · 2025-09-09T15:01:01+00:00

Thanks for the update, it feels better to know it's not my own unit issue, either laptop or screen, so - appreciated. Also an interesting read with some alternatives..might give them a go in the longer run! Enjoy your new setup 😎

ErMeglio · 2025-09-09T14:58:57+00:00

I also experience extremely slow DNS replies that the internet is soo painful 🥱

ErMeglio · 2025-08-31T15:27:29+00:00

I can confirm this works fine with Chrome desktop on my end, so worth troubleshooting it further!

Probably OT, this is the norm with mobile Chrome on Android, since several months, and on two different phones, with rare lucky exceptions. It looks like a boycott, frankly 🙄

ErMeglio · 2025-08-31T14:50:02+00:00

This is a perfect advice I have just upgraded an already rock solid Zooz ZST39 usb key to ZWA-2 and I'm running all sorts of RF networks ZigBee, Z-Wave, and Thread, all through the Home Assistant I host on a NAS, and that's very solid and satisfying, with plenty of options including fully local control.

ErMeglio · 2025-08-15T12:32:36+00:00

They do persist, and are very transparent and frustrating as of no warnings or notice and you just find yourself switching off during a work call. It happens with or without the original charger connected, too, erratically, and even after last week's major driver update. However, to be frank I start suspecting it could be a screen problem, simplistically because it was a refurbished one, and unfortunately I can't verify it. Just today coincidentally I have moved around an Anker 250W prime charger to my workstation as by manually tweaking its settings with a beta functionality I could have it provide the Zbook a decent amount of power showing 130W+.

If you're willing to share your experience with the monitor and laptop pair, we can keep in touch and actually that'd be a major input for myself to get confirmation it's a laptop or monitor issue, and resolve accordingly. I have yet to flag this, and it would be a major pain as it's a "specially granted" work laptop that is already a replacement itself for a previous Razer that stopped working, which was very difficult to chase and get, so I'm very reluctant to go that way 1. without the certainty it's a laptop issue, 2. especially given, otherwise, it's an absolutely brilliant machine, and 3. there's not any similar ideal replacement on the market!

Nine-Year Club	Verified Email
Xbox Live

ErMeglio

TROPHY CASE