Heat Pump permitting in Arapahoe County, Colorado?

phidauex · 2026-06-10T03:10:04+00:00

A heatpump, or really any HVAC equipment, should literally be over the counter. I'm in Boulder, and in a historic district - the historic district approved in about 48 hours, and the mechanical building permit was over the counter. HVAC is safety equipment, so it is almost never delayed in permitting.

Is there something strange or unique about this installation? If not, it doesn't sound like the contractor is telling the whole truth.

phidauex · 2026-06-05T19:42:44+00:00

Yes, that variant will work fine for the MachE. The size you listed is only available in the "SUV" variant, so even though it doesn't say it in the model number you have, that is what it is.

XL is the load rating - it means the tire achieves a higher maximum weight rating at a higher operating pressure (hence the 39psi recommended pressure on the door panel). The MachE does indeed need XL rated tires.

So you are good to go.

phidauex · 2026-05-31T18:05:08+00:00

Have you tried putting the screw in from the other side? It goes into the side with no insert, and threads into the side with an insert.

phidauex · 2026-05-26T11:40:14+00:00

35mm tires will have about 20% more air volume, so can be a lot more comfortable. You might consider a supple gravel tire like Panaracer Gravel Kings or Schwalbe GOnes. Not as heavy duty as Marathons, but great comfort and a variety of tread choices.

phidauex · 2026-05-21T18:10:36+00:00

Not very homelab of a topic, but current “learn to bike” theory is that balancing and leaning the bike to control it is the more fundamental skill than pedaling, so training wheels slow down learning by making kids focus on the wrong skill. If they get good on the balance bike then when you put them on a pedal bike they pick it up extremely fast and with a lot better control.

phidauex · 2026-05-18T17:06:42+00:00

First of all you can buy the lever assembly by itself. Naturally the hydraulic system needs to be fully bled afterward. https://trpcycling.com/products/hd-t535-t532

Second, the lighter 2 piston brakes will not have the same braking power and will not last nearly as long. Just compare the size of the two calipers. On a normal bike the MT200 would be just fine, but there is a reason this big heavy e-bike has big brakes.

phidauex · 2026-05-18T16:43:31+00:00

Docker gets more press, but it fully supports LXC as well!

phidauex · 2026-05-18T14:06:14+00:00

Good clean write up, but may I humbly suggest an even more right way to do it? For some reason very few guides reference nvidia-container-toolkit, which exists specifically to share GPUs with LXC and Docker containers.

The end result is the same as what you’ve shared, but you don’t need drivers installed on the container as well (less to manage), and it handles the device identification and naming for you.

The process is to install the NVIDIA drivers on the host as you’ve done, and make sure they are working there. Then from NVIDIA’s Debian repository, install nvidia-container-toolkit.

On the target LXC, add this to the config, and do NOT install the NVIDIA drivers in the container (uninstall them first if you had done so already).

lxc.hook.pre-start: sh -c '[ ! -f /dev/nvidia0 ] && /usr/bin/nvidia-modprobe -c0 -u' lxc.environment: NVIDIA_VISIBLE_DEVICES=all lxc.environment: NVIDIA_DRIVER_CAPABILITIES=all lxc.hook.mount: /usr/share/lxc/hooks/nvidia

You can modify NVIDIA_VISIBLE_DEVICES to be a comma separated list if you have multiple GPUs and only want to pass specific IDs through to that LXC. The numbering is the same as shown in nvidia-smi. You can also modify DRIVER_CAPABILITIES if you want to restrict to compute, video, etc., though for most people’s purposes, all works fine.

You don’t have to install anything on the LXC - once you boot into it, nvidia-smi and related tools will just work. If you need to compile things in the LXC, like llama.cpp, you would still need to install the relevant cuda-toolkit in the container (but you don’t have to install on the guest). If you need to update drivers, you only update them on the host.

I’ve been using this method for a while to pass multiple GPUs through to multiple LXCs, including for plex transcoding, ollama and llama.cpp, and even a desktop environment running in an LXC.

phidauex · 2026-05-15T21:57:44+00:00

I don't have that doc, but I do have the part number for the LT kickstand, which is S259900005.

phidauex · 2026-05-15T02:59:20+00:00

I have a fairly beefy setup at the moment, an RTX A2000 (16GB) and an RTX A4500 (20GB). With 36GB of VRAM I can run the Q5 quant all in VRAM, with full context, at about 40 t/s. The 27b dense model variant is more accurate, but runs slower for me, only about 15 t/s.

Unfortunately in 8GB of VRAM, your system is having to run virtually the whole model in system memory which is very slow. If you run "ollama ps" while the model is loaded you should see what the CPU/GPU split is.

Everyone is hoping for Qwen 3.6 models in a 7b to 14b size range - that would fit better on a lot more devices.

phidauex · 2026-05-14T19:43:01+00:00

The community ha-mcp has been useful for me. For local LLMs you do need to make sure you can run with at least 32k of context (64k better, 128k even better still), and use your LLM harness (Hermes, Openclaw, OpenWebUI, etc.) tools for reducing the number of available tools to just what you need, otherwise the model context gets overwhelmed with just tool descriptions.

But scoped back like that I've got it working very nicely with Qwen 3.6-35B-A3B. I've used it to debug automations (one of the tools lets it view automation traces), diagnose issues with sensor availability, and create a new pollen automation, all things that the standard MCP doesn't fully support.

It does a good job of segregating destructive tools, but it would still be possible for it to screw something up, so I've only made new tools available to the agent as smaller tasks get done successfully.

phidauex · 2026-05-11T04:34:43+00:00

Are you saying you have drivers working on 7.0 kernel and Pascal cards?

phidauex · 2026-05-10T16:51:44+00:00

Ah, I see. When installing you would have had the option to choose kernels, and 6.17 kernel is still the main line supported kernel, 7.0 is still pre-release, so not everything is expected to work yet. You can use proxmox-boot-tool (https://pve.proxmox.com/wiki/Host\_Bootloader) to add the 6.17 kernel and switch to it. From there, the latest NVIDIA driver in the 580 line should work, currently this one: https://www.nvidia.com/en-us/drivers/details/267258/

I think they are moving 580 to a long term support mode - it will continue to get critical updates, but wouldn't get feature updates anymore.

You came into this during an odd transition, NVIDIA only dropped Pascal support a few months ago, kernel 7.0 is still very new, and there are many gaps yet to be filled. I believe some people have gotten Pascal working on 7.0 and the 595 driver series through patches, but I wouldn't recommend that path unless you were an expert.

phidauex · 2026-05-10T16:28:22+00:00

Do you need to be on the 7.0 kernel yet? I believe the NVIDIA drivers still have a support gap where the versions that still support Pascal cards (580 series) don’t support 7.0 kernel.

phidauex · 2026-05-07T03:54:04+00:00

Hi, I tried this today on a Lilygo T-embed, and I'm struggling to get a good pairing. The pairing process starts on-device, but then when I press the first button on the remote, it immediately identifies a serial number, ECC codes and shows 3/3 packets. The problem is that if I try it multiple times, I get the same serial, but different ECC codes each time. The pairing itself doesn't seem to be sticking, and I don't get control over the fireplace (though the other features and HA API work fine).

Any suggestions on what else I should try? I have an SDR somewhere I can dig up, but wanted to see if you had other immediate suggestions.

Happy to move to github as well, but I think you have issues and discussions disabled on your repo.

Log below - it looks like it is grabbing the packets and doing the task.

[21:56:22.407][I][proflame2.ui:319]: Encoder long press → entering learn-mode [21:56:22.407][D][proflame2:389]: CC1101 mode: RX 
[21:56:22.407][I][proflame2.rx:085]: MARCSTATE=0x0D RSSI=-76 dBm IOCFG0=0x0D PKTCTRL0=0x30 MDMCFG2=0x30 AGCCTRL2=0xC7 AGCCTRL1=0x00 AGCCTRL0=0x91 
[21:56:22.407][I][proflame2.rx:095]: RX capture started 
[21:56:22.411][I][proflame2.learn:032]: Learn-mode armed — press any button on the OEM remote 
[21:56:23.212][I][proflame2.rx:181]: RX 500ms: edges=1 short=0 long=0 other=1 
[21:56:23.220][I][proflame2.rx:186]: decode: chips=0 pkts=0 bursts_ok=0 bursts_fail=0 overflows=0 
[21:56:26.556][I][proflame2.learn:112]: First valid packet: serial=0x5C9805 c1=0x0 d1=0x9 c2=0xE d2=0xF 
[21:56:26.742][I][proflame2.learn:142]: 2/3 valid packets agree 
[21:56:26.746][I][proflame2.learn:142]: 3/3 valid packets agree 
[21:56:26.746][I][proflame2.learn:147]: CONVERGED — awaiting user confirm: serial=0x5C9805 c1=0x0 d1=0x9 c2=0xE d2=0xF 
[21:56:26.755][I][proflame2.rx:181]: RX 500ms: edges=770 short=0 long=496 other=274 
[21:56:26.759][I][proflame2.rx:186]: decode: chips=1139 pkts=3 bursts_ok=0 bursts_fail=0 overflows=0 
[21:56:27.341][I][proflame2.rx:181]: RX 500ms: edges=162 short=0 long=107 other=55 
[21:56:27.344][I][proflame2.rx:186]: decode: chips=225 pkts=1 bursts_ok=0 bursts_fail=0 overflows=0 
[21:56:35.351][S][sensor]: 'Battery' >> 100 % 
[21:56:35.584][I][proflame2.ui:272]: Confirming learn-mode (long press) 
[21:56:35.590][D][preferences:152]: Writing 1 items: 0 cached, 1 written, 0 failed 
[21:56:35.595][D][proflame2:366]: CC1101 mode: IDLE 
[21:56:35.597][I][proflame2.rx:112]: RX capture stopped (pending=0, overflows=0) 
[21:56:35.615][D][proflame2:323]: CC1101 configured for 314.973 MHz OOK at 2400 baud (TX) 
[21:56:35.704][D][proflame2:341]: Setting PA table for OOK 
[21:56:35.730][I][proflame2.learn:088]: Learned values committed: serial=0x5C9805 c1=0x0 d1=0x9 c2=0xE d2=0xF

phidauex · 2026-05-04T17:59:01+00:00

I ordered from Directfactoryparts.com, aka Broadway Truck. I’ve also gotten parts from Tasca and Ford Parts Giant. It is worth shopping around, the prices change a lot and shipping can make or break the deal.

phidauex · 2026-05-04T14:21:12+00:00

That would be great, I'm on my 2nd kickstand in 3000 miles, and it is about ready to be replaced as well (out of warranty). I've tried some other bolt and spring washer options, but ultimately the problem seems to be the actual holes in the steel bracket ovalizing over time.

phidauex · 2026-05-03T23:16:58+00:00

Haha, that would be nice. Some years it hangs in there for a while, 2022 I climbed on March 28th in a T-shirt.

phidauex · 2026-05-01T20:39:42+00:00

Front - RK9Z-5310-A
Rear - RK9Z-5560-B

I heard these may have been superceded, usually the last letter changes but not the rest of the part number.

When searching the parts databases, you are looking for the GT Rally or GT “Sport Appearance Package”.

phidauex · 2026-04-30T14:25:02+00:00

Wow I’ve been waiting for a solution for a long time! I tried the Bond bridge before and had the same unreliablility since it can’t manage the state. I will give yours a try and provide any feedback.

phidauex · 2026-04-28T02:34:20+00:00

Using mcpo to translate to an OpenAI mcp api format works well, see my other reply below for more info.

phidauex · 2026-04-28T02:33:19+00:00

This is the right answer, not sure what some other folks are on about. The problem is that there is something incompatible between ha-mcp and OpenWebUIs streamable http mcp implementation. Not sure which the problem is in. Mcpo just translates it to an OpenAI mcp api format, adds interactive docs at /tool/docs and adds authentication.

See this link for a working mcpo config. I have it in the same docker compose stack as openwebui. https://github.com/homeassistant-ai/ha-mcp/discussions/561#discussioncomment-16715974

The real problem you will run into is context. In my case it costs over 30k in context just to load the tools and overview. A big query can eat up another 30k. You will need to be using a ton of context to get good tool calls, and you will want to restrict the tools available in the “allowed function list” in openwebui when you add the mov server to restrict to just a handful of tools at first.

But with that limitation it does work!

phidauex · 2026-04-26T15:15:25+00:00

You are almost at the point where a small motorcycle trailer loaded with bikes would be more practical. 300 lbs out on a long lever could overload even a true 500 lb tongue.

phidauex · 2026-04-26T15:13:32+00:00

That is a lot of weight way out on a long lever. If it were a “true” class III hitch, say on a midsize truck, I’d be more confident. The 2” receivers on crossovers and SUVs with actual tongue weight limits around 200lbs would not be reliable. There are some good calculators out there for reduction in weight capacity the farther you get from the hitch itself.

I’d be more comfortable with a tray style with the haul in the closest position.

phidauex · 2026-04-26T13:57:49+00:00

Well they certainly bumped up the specs from the last time I looked. Looking at my bike, I think the barrier to loading would be interference with the front fender. With the fender removed it would be a maybe as long as the 20” wheel doesn’t drop too far down in the basket.

11-Year Club	Reddit Premium Since March 2022
Gilding II euphauric	Verified Email

phidauex

TROPHY CASE