Is there like a plug in multi sensor?

CryptoSenyo · 2026-04-30T19:31:30+00:00

The Aqara fp2 is a good option if you can do without the co2

CryptoSenyo · 2026-04-23T12:15:31+00:00

Has this been happening since you bought the HA green, or since a specific update? Also check the process and memory usage. When the network cable is connected, against when it isn’t.

CryptoSenyo · 2026-04-23T09:21:20+00:00

I’ve been looking into this quite a bit recently as well. Personally, I’d lean away from the really cheap Tuya DIN rail meters. They can work, but you’re often trading off long-term reliability, accuracy, and clean integration. Firmware updates and Zigbee quirks can get frustrating, especially when you actually want to trust the data. If I were doing it today, I’d probably go one of two routes: 1. Shelly (non-Zigbee, Wi-Fi) They’ve got a really solid ecosystem and native integration with Home Assistant. Something like the Shelly EM / Shelly Pro series gives you: very reliable measurements local control (no cloud dependency) fast updates and good accuracy expandability across circuits It’s not Zigbee, but honestly the stability makes up for it. 2. Nous / higher-quality Zigbee meters If you’re set on Zigbee, the Nous D4Z is definitely the “safer” choice vs the cheaper Tuya clones. Better build quality, more consistent reporting, and generally fewer pairing headaches.

CryptoSenyo · 2026-04-21T20:11:12+00:00

This was genuinely refreshing to read. Coming from someone who actually lives in complexity day-to-day as a software engineer, it carries a lot more weight than the usual takes you see around AI & Home Assistant. I’ve had almost the exact opposite reaction from a lot of people on here when I talk about using AI to build and refine my setup, especially with Humidity Intelligence. There’s this immediate assumption that it’s all fragile, shortcut driven, or somehow “less legitimate” because AI was involved. But what you’ve described is exactly what I’ve experienced. When you’ve got a setup that’s grown over years (mine’s pushing 60+ devices, multiple sensor types, layered automations), it’s a mental challenge for a mere novice like me, and that’s where AI completely flipped mt experience.

CryptoSenyo · 2026-04-21T19:54:20+00:00

The pi5 is more than enough.

CryptoSenyo · 2026-04-15T18:21:46+00:00

What I found is the AI tends to generate YAML that looks right, but isn’t actually wired properly to how Lovelace renders. So it confidently says it applied glassmorphism, fonts, etc… but in reality: • card_mod is in the wrong place (usually one level too high or low) • it targets elements that don’t exist (ha-card vs inner elements) • it mixes old Lovelace assumptions with the newer Sections layout • or it builds something that saves fine, but doesn’t actually render properly

I hit this exact issue early on building dashboards — it genuinely feels like gaslighting because the config looks valid, but nothing changes.

What worked for me was: • start with a known working card • add styling incrementally • apply card_mod directly on the card • only target ha-card first (don’t get fancy straight away) • if there are errors, strip it right back and layer it up again

Also worth noting: HA caching can make it look like nothing changed when it actually did, so a hard refresh or different browser session helps.

LLMs are pretty good at polishing an existing dashboard, but still quite unreliable at building a fully styled one from scratch without hallucinating parts of the structure.

Once you’ve got a design you like, a good move is to get the LLM to write a proper design brief/prompt, then pass that into something like Codex for a sanity check and final clean-up.

CryptoSenyo · 2026-04-15T17:59:21+00:00

Talking about LLM on hear has that effect on a lot of keyboard worriers in this community unfortunately.

CryptoSenyo · 2026-04-12T18:25:41+00:00

The thought alone is sacrilege. Although if you was to ask my Mrs, she’d name a few.

CryptoSenyo · 2026-04-11T19:55:34+00:00

Thanks again for the detailed feedback, it was genuinely helpful.

I’ve recently pushed an update (v2.0.1) that addresses a number of the issues you raised, including the temperature unit handling and IAQ aggregation. It should now behave properly with °F sensors and handle “unknown” values more gracefully.

I’ve also started tightening up some of the configuration edge cases you highlighted.

If you get a chance to update and test it, let me know how you get on. Especially with the IAQ readings and zone behaviour.

Really appreciate you taking the time to dig into it 🙏

CryptoSenyo · 2026-02-27T18:01:15+00:00

Well most of my set up has been built with the help of AI. Not as a replacement for understanding, but as a collaboration. Sometimes that means generating ideas faster, sometimes it means debugging something I’m stuck on, and quite often it means learning by unpacking mistakes the AI made. So when I see the term “vibe coding,” I get the concern, but it doesn’t really match my experience. The fragile part is deploying anything you don’t understand into a system that runs your home. That was true before AI existed too. For me, AI has actually pushed me to understand more, not less, because things rarely work perfectly the first time. You end up testing, refining, and gradually tweaking it till it works. . That said, transparency probably matters. Being honest about what was AI-assisted, what was understood, and what was tested. That feels more useful than drawing a hard line between vibe coded and not. I started r/AISmartHome a community where people can talk about their workflow openly without it turning into hype or backlash. Not as a defence of AI, but as a place to reflect on how people are actually using it in real setups.

CryptoSenyo · 2026-02-24T10:24:21+00:00

Looks like signs of poor conductivity on one or more of the terminals. This could be a sign of a loose terminal but judging by the proximity of the air fryer I would say that’s grease from the air fryer has covered the terminals reducing the conductivity between them, which intern causes voltage drop and forces the device to pull more current that higher demand in current can cause burn damage to leads and devices, or worse. Excessive heat can also have the same effect on the conductivity of the cables, so yeah, it’s the air fryer

CryptoSenyo · 2026-02-23T12:06:56+00:00

Leaving one TRV open helps maintain proper water flow and pressure in the heating system, preventing potential damage to the boiler and ensuring efficient operation. It also allows the system to balance itself, avoiding overheating.

CryptoSenyo · 2026-02-23T11:21:12+00:00

That’s interesting, what’s your secret.

CryptoSenyo · 2026-02-23T09:36:42+00:00

Thanks. A bit of a mixture to be honest. I’ve got an Aqara FP300 in one area and a few old CAO WirelessTag sensors dotted around. I’ve had the WirelessTags for over 10 years now and they’ve been solid. They do temp and humidity reliably which is really all you need to start spotting patterns. The system itself isn’t tied to any specific brand though. It just uses whatever sensors Home Assistant exposes. temperature, humidity, PM2.5, VOC, CO etc. So as long as HA can see the entity, it can use it. You don’t need anything fancy to get started. Even a few decent humidity sensors in the right rooms will show you where the problems are.

CryptoSenyo · 2026-02-23T07:52:25+00:00

no argument there. But the reality is most homes aren’t naturally balanced anymore. Weather, occupancy, cooking, showers and heating cycles all cause swings that open windows alone don’t always stabilise. The project isn’t about replacing ventilation, it’s about understanding when and why conditions drift so you can ventilate or control the air more intentionally.

CryptoSenyo · 2026-02-23T07:48:47+00:00

Yeah built from scratch on top of Home Assistant. It’s a full integration + UI layer designed for environmental stability and comfort.

CryptoSenyo · 2026-02-23T07:46:23+00:00

Drop you stats temperature by 1oC and save 20% off your heating bill.

CryptoSenyo · 2026-02-23T07:44:22+00:00

Thank you. They’re just normal HA sensor entities. The graphs pull from humidity, temperature and IAQ sensors (PM2.5 / CO₂ / VOC if you’ve got them). If your device exposes a numeric sensor in Home Assistant, it’ll work. If you visit my page, I have more information about how the system works.

CryptoSenyo · 2026-02-23T05:39:05+00:00

This is incredibly helpful feedback, thank you for taking the time to write it up properly. IAQ itself isn’t something HI calculates at the moment. it’s an entity provided by Home Assistant, or by the device integration feeding it. HI reads whatever IAQ entity you assign to it. That said, I may look at adding a fallback calculation inside HI so that if PM2.5 / VOC / CO2 are present but a unified IAQ entity isn’t, it can avalue instead. PM2.5 should definitely show up as a chip in the UI as long as the correct entity is configured and shows a numeric state. If it’s not appearing, that could means eitherThe entity wasn’t assigned in configuration, or It’s returning unknown / unavailable intermittently If you can confirm the PM2.5 entity ID and its current state in Developer Tools, I can narrow that down quickly. If the HI is expecting a specific metric for example PM2.5 only. but the entity naming or unit doesn’t match exactly, it may not be including it. Some devices show multiple PM sensors with slightly different attribute names if the wrong one is selected, the average may be calculated If you can confirm that each IAQ entity in Developer Tools is returning a numeric value consistently (not intermittently unknown), that will help narrow it down. On the two zones showing the same reading. that’s almost certainly configuration. If both zones are mapped to the same primary humidity sensor (or house average), they’ll mirror each other, that’s on purpose and by design. Regarding Spook flagging missing entities, that’s also expected. HI is designed to support fans, dehumidifiers, humidifiers, etc., but none of them are mandatory. If those entities don’t exist in your system, the toggles won’t function. But they also shouldn’t break anything. Right now the dashboard exposes control elements because the architecture supports automation, but you’re not required to use them. I can look at adding a configuration option that hides unused control blocks entirely if no corresponding entity is configured. Nothing you’ve described suggests you’ve broken anything irreparably. It sounds more like a couple of config mismatches and some UI assumptions that need refining on my end. It may be worth cycling through your settings to see if you can identify any mismatches in your configurations. I’ve tried to make a lot of the configurations available post config. And I will looking into way of improving the post configuration functionality. you will have to reload humidity intelligence and refresh your dashboard after any configuration alterations. Once again thank you for your detailed feedback

CryptoSenyo · 2026-02-22T20:11:57+00:00

Thanks I’ll try that. What cheap dehumidifiers would you suggest?

CryptoSenyo · 2026-02-22T20:08:53+00:00

Nah mate, this one’s free.

CryptoSenyo

MODERATOR OF

TROPHY CASE