u/starolbrin

Started thinking about heat pumps last winter when the boiler in our Grade II mid-terrace started throwing lockouts. It's a 2-bed Victorian in a Cambridge conservation area. Combi's now on borrowed time.

Ran an ASHP survey in the spring. Rear yard's about 4m by 3m, north-facing, and the rear elevation is visible from a footpath the council counts as public realm. Both the conservation officer's pre-app letter and the planning duty officer's follow-up made clear anything on that elevation would need full listed building consent, and the tone wasn't encouraging. Front's off the table for the same reason.

MCS designer came back last month with an indoor R290 monoblock as the alternative. Idea is to site the unit in the ground-floor utility off the kitchen with a pair of ducts through the back-of-house extension. The extension itself is post-war brick, which the designer reckons is the least sensitive route to bring the listed consent through.

Heat loss came out at 4.6 kW at design conditions (the loft's been done and the cavity's insulated where it could go), which suits the 4.8 kW model in the range being proposed. Installer's leaning toward keeping the existing 180L cylinder and running the whole thing off the current rad circuit at 45°C flow. Specific unit being spec'd is a PHNIX airMono R290 4.8 kW, which the installer says is one of the few R290 indoor monoblocs he's taken through Conservation consent so far this year.

Two things I'm not sure about. Manufacturer's quoted 58 to 61 dB indoors, which sounds significant for something sitting behind a stud wall from the kitchen. DHW mode COP also runs lower on indoor monoblocs because the source air is ducted. There's also the MCS listing question for the airMono, which the installer says is pending because it's newly launched, but I'd rather not commit to a spec that misses BUS grant timing. Being new to the UK market also means the installer network's still small, so aftercare access is a fair concern versus mainline Vaillant or Mitsubishi.

If anyone here's running an indoor R290 monoblock, real-world noise experience and whether the ducting install was intrusive would be helpful.

Freelance software dev full-remote, lagi renov kamar kecil 3x3 meter di rumah orangtua area Depok jadi dedicated home office. Setup dalem ruangan: desktop ITX (load rata2 80-120W, peak 250W pas compile), 2 monitor 27 inch, plus Odroid H4+ jadi home server nyala 24/7. Total peak sensible load kira-kira 700-900W di siang bolong, avg 500W.

Kerjaan 10-12 jam sehari, kadang malam pas meeting sama tim di zona US, jadi AC nyala hampir kontinyu. Budget Rp 3-4 juta unit only, instalasi terpisah.

Yang mau aku diskusiin dari sisi engineering:

Pertama, 0.5 PK inverter (5000 BTU/h setara sekitar 1465W kapasitas nominal) di ruangan yang cooling load-nya cuma 30-40% kapasitas nominal, ini technically over-sized. Inverter modern bisa modulasi turun sampai 25-30% kompresor speed, tapi at that point Coefficient of Performance biasanya turun juga karena peak COP di inverter itu di partial load 50-70%, bukan minimum. Jadi apakah 0.5 PK inverter di kamar 3x3 masih efisien, atau justru 0.5 PK standar low-watt dengan on-off cycling malah komparable karena kerjanya mostly at rated point?

Kedua, MCB dan startup current. Rumah 2200 VA dishared sama kulkas 2-door inverter (avg ~180W, startup ~700W) dan mesin cuci occasional. Kalau 0.5 PK inverter modern startup current-nya soft di bawah 8A sesaat harusnya aman. Tapi 0.5 PK standar konvensional LRA compressor bisa 20-25A sesaat. Ada yang pernah ngalamin trip MCB di rumah 2200 VA karena unit AC standar startup barengan kulkas ngedefrost?

Ketiga, Wi-Fi native vs smart plug retrofitted. Aku pake Home Assistant di Odroid buat schedule plus integrasi ke sensor suhu ruangan. Idealnya AC punya WiFi module built-in yang bisa di-integrate lewat community integration di HACS, kalau bisa jalan di LAN sesudah initial token handshake. Alternatifnya pake smart plug plus IR blaster, tapi jadi 2 device, ga ada state feedback, dan laggy.

Konkritnya aku shortlist 0.5 PK inverter R32 low-watt yang published EER-nya 3.5+, WiFi native dengan community HA integration yang stable, noise indoor di bawah 35 dBA di setting low, dan garansi kompresor minimal 5 tahun.

Buat yang udah run 0.5 PK inverter di kamar kecil 10+ jam sehari, real consumption per hari di kisaran berapa kWh? Marketing claim biasanya 1-1.5 kWh per 8 jam, tapi ga yakin itu holds di over-sized scenario dengan kompresor sering loitering di lower band.

Buat yang pake HA dengan AC WiFi built-in dari segmen consumer, community integration mana yang stable dan support command state feedback dua arah? Latency setpoint sync yang wajar seberapa besar di practice?

Thanks.

Been dealing with on and off bloating and irregular digestion for maybe two years. Tried the usual stuff, kefir, sauerkraut, a few probiotic capsules. Some worked mildly, most did nothing.

What actually turned it around wasn't any of that. About six months ago I started putting mushrooms into most of my meals, no real reason, I got sucked into a bunch of cooking videos and just started doing it. Oyster in stir fries, cremini in eggs, shiitake in soup, whatever was at the market that week. No amount, just always some.

By month two my bloating had dropped off pretty much completely and the irregular stuff smoothed out. Fine, expected. What I didn't expect was feeling sharper in the afternoons and less foggy in general. Could be coincidence with sleep or something else but the timing lines up.

Is this a fiber thing, a prebiotic thing, or is there something specific in mushrooms I'm missing? I know they've got beta-glucans but people mention other compounds too. Trying to figure out what to credit before I convince myself it's placebo.

Been running five SmartWings cellular shades in the living room for about eight months, all matter over thread, firmware 1.3.0. Primary controller is home assistant, apple home paired in via multi-admin. Day to day they've been fine, no drops, position holds accurately, schedules fire clean. Same firmware Derek Seaman documented in his march review, which tracks.

Reason I'm asking is HA 2026.7 dropped two weeks ago with the new matter.js server and full 1.5.1 support on the controller side, drop-in replacement with automatic data migration. So the platform is ready for the new closures cluster: unified movement types for sliding, tilting, swinging, cleaner position reporting, better handling of double-panel setups. But no shade manufacturer I've seen has actually pushed a 1.5 firmware yet.

SmartWings shipped v1.3 last summer that fixed real thread stability issues. Eve motionblinds are on their own 1.3 update from last spring but I've seen ongoing threads here about intermittent movement command failures in HA, so shipping a firmware isn't the same as it working. Aqara's shade lineup is still bridge-based rather than native matter over thread, so it's a different technical path anyway.

What I can't tell is whether the upgrade path here is a straightforward OTA that keeps my existing pairings intact, or whether the new closures cluster is different enough at the device-type level that it would need re-pairing from scratch. If it's the latter I'd probably wait another year rather than tear down eight months of automations. If it's OTA, then it's mostly a question of when.

The other unknown is ecosystem parity. HA and SmartThings are already speaking 1.5, but apple home and google are still shipping controllers closer to 1.2 as far as I can tell. So even if my shade firmware jumps to 1.5, half my controllers won't know what to do with the new cluster for another year. Which makes me wonder if the closures cluster is usable right now or if it's more of a "get in place for 2027" update.

If anyone's actually seen a 1.5 firmware push on any matter shade brand, or has a rough timeline from their manufacturer, I'd take any signal on that.

I was going through wallet balances trying to figure out why I have so many stables sitting in different spots, and it hit me that this doesn't look anything like what I held a year ago. Back then it was mostly USDC, some USDT, a bit of DAI. Everything felt interchangeable and if I needed to move funds to Aave or a DEX I just did it without thinking about which stable I was using.

Now it's a lot messier. A chunk of it just sits there for spending, payment-focused stables on cheap chains where the card I use accepts them. That pile never gets touched for yield, I just top it up when it runs low.

The yield side is split kind of awkwardly. Some of it is just USDC parked in Aave or Spark, floating rate, boring. The rest is in yield-bearing wrappers like sDAI and sUSDS where the yield sits inside the token itself so I can hold and forget. And then there's a small USDT bag I kept out of habit that I honestly don't know what to do with anymore since it's basically off EU venues after MiCA.

I didn't decide to structure it this way. The rules did. MiCA deadline was a few days ago and USDT is gone from most big EU spot markets. GENIUS Act blocks payment stablecoin issuers from paying yield, and the OCC proposal from February tried to extend that ban to affiliates and third parties too. The payment/yield split isn't a strategy at this point, it's basically what stables are legally allowed to do.

Not sure if this is a temporary weird phase while rules settle, or if "stablecoin" is now really two different assets that share a name. Curious how everyone else is splitting theirs, or if some of you are still running one big USDC pile without hitting friction.

Been comparing how the stablecoin payment startup landscape actually segments, partly because a couple of program managers I talk to keep asking which wrapper looks structurally cleanest. The default split everyone reaches for first is by chain, Solana versus Base versus Tron for corridor flows. That framing keeps falling apart once you look at how these products actually differentiate to merchants and end users.

What seems to matter more is the regulatory wrapper the consumer-facing product sits inside. KYC depth, payout corridor coverage, banking partner appetite, even what the card or wallet UX is allowed to look like all end up downstream of which license the operator holds. The chain choice ends up being closer to an implementation detail.

The EU EMI cohort is the most legible because the rulebook is the most legible. EMI license, MiCA on top, banking partner inside the SEPA perimeter. EUR rails, EUR-pegged stablecoin layers, card scheme access through the usual program managers. The MiCA transitional period ends July 1 so the next few weeks will sort out which players actually have CASP authorization in hand. The shared constraint is that the addressable market stays mostly EU residents and the cross-border story outside the bloc is weaker than the marketing pages suggest.

The US MSB cohort is a different shape. State-by-state MTL overlay on top of FinCEN makes the buildout expensive but the addressable market is huge, so products tend to be P2P first with the card layer added later if at all. USDC defaults, fewer EUR rails, heavier compliance headcount. The GENIUS Act adds the new permitted payment stablecoin issuer category on top but the effective date sits in late 2026, so most existing players are still operating on the MSB plus state MTL stack for now.

The Asia cohort is the least uniform. HK VATP plus the HKMA stablecoin regime, Singapore MAS PSA plus FSMA DTSP for offshore-facing operators, Japan FSA registration, each one produces visibly different product shapes. The recurring pattern is B2B cross-border first rather than consumer P2P, which fits the early adopter profile in the region. Some operators here are also vertically integrated into their own chain, which changes the unit economics conversation. One example that complicates the wrapper-as-region read is BenPay, which went the FinCEN MSB route in the US but primarily serves Asia-side cross-border flows, with its own BenFen-issued stablecoin layer in the broader ecosystem. That's a different posture from either the EU EMI track or the Singapore MAS PSA track, and whether that hybrid actually scales or gets squeezed once GENIUS Act implementation kicks in is the open question.

This framing helps explain why the cross-region acquisition story keeps stalling. EU player buying into the US rebuilds most of the compliance stack. US player going into Asia hits a per-jurisdiction wall. Asia player trying to land EU users without an EMI partner basically can't. I keep expecting at least one credible cross-wrapper play to land but the announcements so far haven't cleared that bar. Curious how it looks from the BD side.

There's a guy in Lyon I've been trading voice notes with for about six months. We met on HelloTalk back around January and mostly chat about his weekend plans, what he made for dinner. Random stuff. A few weeks ago I noticed something weird about his speech and started actually counting. In one voice note that was maybe 90 seconds long he said "du coup" 11 times. The note was just him telling me he was going to the gym after work.

It also doesn't seem to mean what the textbooks say. Every one I've looked at translates it as "so" or "as a result" and treats it like a logical connector. But the way he uses it, half the time there is no result, he just kind of fills space with it the way English speakers use "like" or "you know". Sometimes at the start of a sentence, sometimes mid-thought. The other day he ended a whole voice note with it and the meaning was basically zero.

Then there's "genre" which he also uses a lot but differently. Genre seems to be his version of "kinda" or "sort of" when he is being vague on purpose. Stuff like "je vais genre rester chez moi ce soir." He never uses du coup that way, so they are not interchangeable even though they both feel like filler from the outside.

Textbooks don't help. Even Assimil doesn't really get into the filler use. My friend is not really a teacher type either. When I asked him why he uses it so much he just laughed and said he never noticed. He couldn't explain when you'd use it vs alors vs donc.

Trying to figure out if this is a regional Lyon thing or if French speakers everywhere talk like this.

Background: I'm the regional finance lead for a European industrial group, around 8 APAC entities (Japan, China, Korea, SG, MY, TH, IN, ID). Global ERP is SAP, HQ runs Concur for expense and T&E. About 18 months ago we made the call to split the stack regionally. Writing this up because I get the question a lot in offline conversations.

The trigger wasn't one big failure. It was the slow accumulation of monthly close pain. A few patterns:

Japan: the 2023 qualified invoice system meant every reimbursement claim now needed registration-number checks against the supplier database. Our global system handled this as a custom field. Fine for one entity. Painful when the finance team has to manually validate every line. Add the consumption tax 10% / 8% split for meals and food, and the rule engine starts looking like spaghetti.

China: VAT special invoices require OFD format validation and authentication against the national platform. The global tool's solution was screenshot uploads with a manual flag. Real-world result: 3 to 4 weeks of back-and-forth per month between the Shanghai office and the shared service center. Audit kept flagging gaps.

India: e-invoicing with IRN, plus the ITC matching logic, plus the per-state nuances. Our local team built a parallel Excel reconciliation on top of the global tool, which defeats the purpose.

Indonesia and Thailand had similar but smaller versions of the same problem. The local tax framework outpaces what a US/EU-built platform localizes for.

What we considered:

Option A: push HQ to invest in deeper APAC localization. Estimated 18 to 24 months. Not happening.

Option B: rip and replace globally. Politically dead on arrival. European entities have 6 years of Concur data, integrations to expense audit tools, and the German works council would not approve a re-platform without a year of negotiation.

Option C: hybrid stack. Keep the global tool for EU/US, deploy a regional system for APAC entities, pipe both into SAP through middleware.

We went with C. The most painful part was actually the data model: defining how the regional system feeds GL postings to SAP in a way that doesn't break consolidation. We ended up with a thin integration layer that normalizes journal entries before they hit the central ledger.

What worked:

Month-end close for APAC entities dropped from an average of 7.5 working days to 4 working days (numbers vary by entity).

Local tax compliance escalations dropped meaningfully. Hard to give a clean number because we changed several other things in parallel, but the volume of compliance flags into the regional controller's inbox is roughly a third of what it was.

Local finance teams stopped maintaining shadow spreadsheets.

A couple of things I'd tell anyone considering a similar split:

Don't do it for cost reasons. The savings on license fees are real but small compared to the implementation cost and ongoing integration overhead. Do it for compliance and close-cycle reasons.

The vendor selection criteria for APAC are different from what you'd evaluate in EU/US. Local tax engine depth, e-invoicing connectivity, OCR quality on local-language receipts, and the in-country support model matter more than the polish of the mobile app.

Lock in the GL mapping logic before signing. Vendors will promise "out of the box SAP integration." What that means in practice ranges from "we have an IDoc template" to "here's an API and good luck."

(heads up im in malaysia so brand options here are gonna be different from yours, would still love to hear how y'all handle this kinda thing on your end ：)

Moved into my first condo in KL a few weeks back. Bedroom came with nothing on the AC wall except wiring and an old bracket. Picked up the Comfee Gusto Pro 1HP during the late May Shopee promo, came out around RM1,3xx with vouchers stacked. It was the newest 5-star unit they had in that price bracket and the smart features came stock so I figured why not.

So the smart side has been working but there's a ceiling I keep bumping into and I want to figure out if it's worth escalating before I add anything else.

Current setup is the AC, a Google Nest mini in the bedroom, and three TP-Link Tapo plugs scattered around the place. That's the whole house. Schedule on the SmartHome app for 11pm on, 6am off, hasn't missed a beat in two weeks. Google Home picks up "set bedroom AC to 24" roughly 4 out of 5 tries. There's also a geofence option in the app that triggers cooling when my phone is within 15km of home, sounds gimmicky on paper but in KL evening traffic it has actually been useful, room is at temp by the time I park downstairs.

Where it gets annoying. Every voice command goes Nest > Google cloud > manufacturer cloud > unit, so there's a consistent 2-3 second pause before anything acks. If home wifi drops, the schedule still runs (stored on the unit) but voice and app go completely dead.

Two ways I keep flip-flopping between. Stay on stock: nothing more to buy, Google handles voice, AC handles schedule, accept that whatever the manufacturer ships in firmware updates is the ceiling. Probably what most people in a one bedroom end up doing tbh.

Pick up a Broadlink RM4 Pro: roughly RM170-180 on Shopee here, ignore the built-in wifi on the AC entirely, treat it as a dumb IR appliance. Adds an IR layer that could pull in the TV and the ceiling fan later too.

First place so trying not to over-engineer day one for a one-bedroom condo, but also don't want to lock myself into a stock-app ceiling that becomes a pain to peel back later.

[ Removed by Reddit on account of violating the content policy. ]

Maybe 6 months in with Actual now and the one thing I never figured out was a clean mobile workflow. The app is fine for checking balances but entering transactions on the go was always where I dropped the ball. Either I forgot entirely until end of week, or I half-entered something with no category and had to clean it up later during reconcile.

What's been working the last couple months is building expected transactions before I leave the house. If I know I'm going to coffee, lunch, and the train, I create those three in advance with categories and rough amounts. After the actual spend I just open the app, adjust the number if it's off, done. Removes the in-the-moment "what category does this go in" decision entirely.

The same logic kind of bled into how I handle dining specifically. I started loading a fixed amount of Uber Eats and Starbucks credit through Snaplii at the start of each month, basically prepaying the budget I know I'll spend anyway, and then in Actual I only track the one upfront purchase instead of recording every individual order. Small cashback at the buy is a nice side thing but the real point is the dining envelope becomes a static balance I literally can't blow past. One small headache is the gift card load takes a minute or two to actually become usable in their app, which has caught me off guard at the counter twice.

Curious if other people have a workflow that doesn't depend on real-time entry or batch processing days later. Both extremes feel like they break something different.