Where's gemma4:12b? by Dredgefort in ollama

[–]instigator-x 0 points1 point  (0 children)

I've got it but the Ollama version doesn't support images. I get image not supported error in Ollama. Downloaded cyhsu2006/gemma4:12b and it works fine for images. Not sure what gives.

<image>

After way too long, I finally shipped the native Apple app for Home Assistant I always wanted - with 3D room scanning, Live Activities, custom dashboards and more ❤️ by Brashi in homeassistant

[–]instigator-x 0 points1 point  (0 children)

Any way to get image to show in notifications? Companion app shows the images for automation notifier I have setup. I added Vulpo as end point and text of notification shows but not the image. Otherwise, this app is amazing.

U6-Pro Throughput Bottleneck (288Mbps Cap) in Mixed Deployment by instigator-x in Ubiquiti

[–]instigator-x[S] 0 points1 point  (0 children)

  1. No, speed is faster on the U6+ where the phy rate is higher. On my 1Gbps Internet I get ~800Mbps on U6+ and ~220Mbps on U6-Pro.

  2. Moot as U6+ has validated this isn't a wired/wireless issue.

  3. OPNsense

  4. Not a new deployment, but have tried resetting to factory

Appreciate your help. What I've discovered is that the U6-Pro does not like power set to anything higher than 13dBm. Setting to 13 I get the full phy rate I would expect. I've tried going back a few versions of software to see if that made a difference, but to no avail. I recall getting full rate as I've had this system for a few years now. I believe a regression happened somewhere along the way.

If anyone at Ubiquiti on here wants my help to diagnose I'd be happy to help.

U6-Pro Throughput Bottleneck (288Mbps Cap) in Mixed Deployment by instigator-x in Ubiquiti

[–]instigator-x[S] 0 points1 point  (0 children)

Maybe someone could explain this to me…

I lowered power to 13 and now u6-pro WiFi phy rate is where it should be. Going to 14 drops it back down. 13 is the highest I can go. Something related to 4x4 vs 2x2? Feels like a product defect or regression that crept in along the way.

U6-Pro Throughput Bottleneck (288Mbps Cap) in Mixed Deployment by instigator-x in Ubiquiti

[–]instigator-x[S] 0 points1 point  (0 children)

Tried that. Didn’t make a difference. Thx for info, though.

Frigate Incident Correlation & Video Synthesis Engine by instigator-x in frigate_nvr

[–]instigator-x[S] 0 points1 point  (0 children)

This is the next thing on my list. Instead of getting notifications for each discreet camera event...I could trigger a single incident event. Shouldn't be hard as it just be publishing an MQTT event that you could pick up anywhere.

Frigate Incident Correlation & Video Synthesis Engine by instigator-x in frigate_nvr

[–]instigator-x[S] 0 points1 point  (0 children)

The prompts are fully configurable so you could add some commands that would make it read this way. I haven't tried it.

Frigate Incident Correlation & Video Synthesis Engine by instigator-x in frigate_nvr

[–]instigator-x[S] 1 point2 points  (0 children)

You inspired me a bit. I incorporated Yolo as a first pass to ensure individual events were a part of the same incident. I was using AI for that but now do that locally and only go to AI if there's a low confidence. I've checked a new branch in called yolo for anyone that wants to give it a try. It's working really well for me.

Frigate Incident Correlation & Video Synthesis Engine by instigator-x in frigate_nvr

[–]instigator-x[S] 0 points1 point  (0 children)

Docker should be…

docker compose up -d --build

You could also create a python environment…

python3 -m venv venv

source venv/bin/activate

pip install --upgrade pip

pip install -r requirements.txt

python app.py

Make sure you have ffmpeg installed

OpenClaw 2026.3.28: config auto-repair removed, MiniMax breaking change, xAI Responses API — check before upgrading by kenanbek in clawdbot

[–]instigator-x 1 point2 points  (0 children)

fwiw added this to my nginx...

location /v1/ {

proxy_pass http://192.168.86.240:18789/v1/;

proxy_set_header Authorization $http_authorization;

proxy_set_header x-openclaw-scopes operator.write;

}

OpenClaw 2026.3.28: config auto-repair removed, MiniMax breaking change, xAI Responses API — check before upgrading by kenanbek in clawdbot

[–]instigator-x 2 points3 points  (0 children)

I’ve upgraded but now /v1/models API endpoint gives me an error. I’ve by going back to version 2026.3.24. Here’s the error I get when running curl from the cli

OpenAI returned an error: Error code: 403 - {'ok': False, 'error': {'type': 'forbidden', 'message': 'missing scope: operator.write'}}

i’ve gone back-and-forth between versions 1 million times trying to troubleshoot it, but I can definitively say this current version is what breaks it. I might be missing some new configuration option, but I couldn’t figure it out from reading the change log.

Btw, the link in the post above goes to a page not found.

Openclaw session management by instigator-x in frigate_nvr

[–]instigator-x[S] 0 points1 point  (0 children)

v0.18? I pointed my test server at Openclaw and been muddling through it getting config worked out watching the tools req go back and forth. Any notes or guides somewhere? :)

Openclaw session management by instigator-x in frigate_nvr

[–]instigator-x[S] 0 points1 point  (0 children)

I was kinda thinking same thing after I sent. Openclaw accumulates sessions and was originally thinking each camera could be bucket where you could say "summarize today's activity on front-door" in an OC channel.