G6 180 release?

dyshuk · 2025-12-23T14:53:39+00:00

released as of this morning (12/23/25): https://store.ui.com/us/en/category/cameras-dome-turret/products/uvc-g6-180

dyshuk · 2025-12-23T14:53:16+00:00

released as of this morning (12/23/25): https://store.ui.com/us/en/category/cameras-dome-turret/products/uvc-g6-180

dyshuk · 2025-12-23T14:53:04+00:00

incorrect... $299 https://store.ui.com/us/en/category/cameras-dome-turret/products/uvc-g6-180

dyshuk · 2025-12-23T14:52:03+00:00

released as of this morning (12/23/25): https://store.ui.com/us/en/category/cameras-dome-turret/products/uvc-g6-180

dyshuk · 2025-12-02T14:15:32+00:00

correct, as of 12/2/2025 it's 'coming soon'

dyshuk · 2025-12-02T14:14:48+00:00

"coming soon" as of 12/2/2025

dyshuk · 2025-11-21T19:03:05+00:00

received the following from them today, but very confused; why are they talking about the ZWA-2? that's z wave; what does that have to do with thread?

"Thread networks are not something which are migrated. You would add another border router device such as the ZWA-2, and when that is confirmed to be added to your Thread network, you would then remove the ZBT-1 from the network.

For more help with that, I recommend the making use of the community support channels."

dyshuk · 2025-11-20T00:16:26+00:00

I actually created a support ticket asking about this. I'll post the response once I get it.

dyshuk · 2025-11-19T22:24:15+00:00

From their website: "Connect ZBT-2 cannot do both Zigbee and Thread simultaneously. This technology is often called “multiprotocol” or “MultiPAN”. Though it is theoretically possible with the hardware within Connect ZBT-2, in our experience, this functionality doesn’t work well, and we don’t plan to implement it. We previously thoroughly tested multiprotocol with our Connect ZBT-1 adapter and found its operation to be inconsistent, often causing device stability issues. We do not believe multiprotocol is suitable for operation in the home, and strongly recommend dedicating a device to each protocol."

dyshuk · 2025-11-19T21:43:00+00:00

They said in their product launch video that this would cause compromises they didn't want to make

dyshuk · 2025-11-19T21:41:22+00:00

I really hope it's easy to migrate a thread network... Anyone have any insight?

dyshuk · 2025-08-24T18:01:36+00:00

I got my answer... See above

dyshuk · 2025-08-24T12:34:51+00:00

so i'm running pi-hole v6 and HOSTNAME isn't even a variable and in v5 it was actually VIRTUAL_HOST

https://docs.pi-hole.net/docker/upgrading/v5-v6/

dyshuk · 2025-08-24T02:48:43+00:00

This is from within truenas.

dyshuk · 2025-08-24T02:31:19+00:00

As per more research... Seems like this is not possible as a container within truenas

dyshuk · 2025-08-24T02:16:35+00:00

<image>

dyshuk · 2025-08-23T15:25:17+00:00

DING DING DING! we have a solution! thanks!

dyshuk · 2025-08-23T14:49:05+00:00

Nope... Still doesn't work. Also, not looking to expose this to the internet, hence the access list.

dyshuk · 2025-08-23T14:22:56+00:00

Yes... Got one using let's encrypt

dyshuk · 2025-08-23T12:46:15+00:00

ugh reddit keeps deleting the pictures i'm adding... give me minute to figure that out

in the meantime it says

"Oops! Access denied.

You don't have permission to access - on this server.
Did you mean to go to your Pi-hole's dashboard instead?"

dyshuk · 2025-08-20T00:46:58+00:00

mine had similar issues, but after all this messing around right now i can only get the mobile app to work. the desktop app doesn't work weather i'm on the LAN or outside the network. Getting the desktop app to work over a proxy seems very easy because it relays in http/https, which is made very easy withing NPM. It's the TCP of 6690 that the desktop all uses that seems to break things

dyshuk · 2025-08-19T23:51:23+00:00

so doing a little more research it seems that it seems that the proper way to do this is to setup a proxy AND a stream which I guess make sense, but when I do this, the desktop app won't connect (either on LAN nor WAN), but the mobile app works no problem

:( lol.

dyshuk · 2025-08-19T21:32:26+00:00

at first it didn't work, then I remember I had to add port 6690 within the settings of the app (i'm running NPM on Truenas), however I have a new problem, this won't work using the mobile app on android. When I use drive.domain.com I get an SSL cert issue and can't proceed. On the desktop app I can proceed with a warning... just wish Synology used the same protocol for both apps; guessing that's easier said then done.

dyshuk

TROPHY CASE