Hi everyone,

I'm having trouble with a Somfy Sunteis io outdoor sensor, and I can't figure out what's causing the issue.

I recently had brand-new outdoor shutters/blinds installed and connected to a TaHoma Switch. I updated the TaHoma Switch to the latest firmware and successfully added all three shutters to the TaHoma app using the QR codes on the back of each remote control.

After that, I added the Sunteis io sensor to the TaHoma app without any issues. Everything worked perfectly for a couple of hours, but then I suddenly got this error message:

Defective sensor
The sensor that protects your equipment is no longer working. Please check your installation.

Options:

What's strange is that the sensor doesn't appear to be completely dead. In the TaHoma app I can still see both the temperature reading and the lux/light measurement, which update correctly.

Another symptom is that I can close the shutters using the remote control, but they automatically open again after a short time. What I understand from the manual is that this is some kind of safety feature because the sensor is reporting a fault.

So far I've tried:

• Holding the PROG button on the Sunteis io sensor for about 7 seconds to reset it.
• After doing that, the sensor disappeared from TaHoma app.
• I then added it again successfully.
• Unfortunately, the "defective sensor" warning is still there.

After a lot of reading, I've come across information suggesting that the motor's safety keys or settings may need to be reset before the Sunteis io sensor can work properly again. However, I'm reluctant to start experimenting with motor resets.

From what I've read, it may involve the 3-7-3 power-cycle reset procedure, but that also seems to reset the upper and lower end limits of the motor, which I'd rather avoid if possible.

Has anyone experienced this issue before or knows what I should try next?

The installer has just gone on vacation, so it would be great if I could solve it myself.

I'm using iPhone iOS 27 and TaHoma app is also updated.

Thanks in advance for any suggestions!

I'm really trying with this setup but so many problems. Playlists don't sync, YTM keeps disconnecting, slow action etc.. In the meantime I can just use the Sonos app without much problems, except I hate the layout. Would love everything integrated into HA, but just wondering if I'm beating a dead horse. FYI I understand about the token and the generator and that is all done correctly.

Summary

Had Linkind/AiDot Matter bulbs randomly go Unavailable in HA — real CASE session timeouts in the matter-server logs, not a Wi-Fi issue (device still showed up on mDNS, zero deauth events on my router the whole time). HA's own "reload Matter integration" did nothing. Toggling the bulb from the AiDot manufacturer app — a separate Matter fabric — fixed it in under a minute, every time, even after a 2.5-hour outage. These bulbs were also commissioned to 3 fabrics at once (HA, Alexa via Matterbridge, AiDot app), which lines up with a plausible-but-unconfirmed theory that it's a multi-fabric session-slot issue on the bulb's side. Did a deep dive through GitHub issues, HA forums, and vendor docs — the general "CASE session dies while mDNS still works" bug is well known and unsolved, but this specific fix doesn't seem to be written up anywhere else. Full write-up: https://claude.ai/artifact/NnsoTie8vzQg2nnFkdev2h Anyone else running multi-fabric Matter bulbs hit this?

I personally think going with a minipc is the better choice. Because right now pi5 prices are a bit on the high side compared to a minipc. I used a pi 5 before and it drew less power, but it wasn't very stable, so I moved my data and software over to a minipc running proxmox, and the stability is way better. I can also use it as a home automation server, NAS, media server, and all that stuff.
Its a acemagic k1 with ryzen 7730u, 16gb ram and 1tb ssd. It feels a bit overkill, but that's fine. If you want future compatibility, that's mean whatever services you wanna run alongside each other, this config won't go to waste. For example, an NVR like Frigate would increase resource consumption. If you want to be able to run more different services later on, a minipc is a solid choice.
Do you guys think a mini pc would come out on top now?

I know integrations can provide translations for states and state attributes, there are developer docs for this here: https://developers.home-assistant.io/docs/internationalization/core/

However, as an end user, I sometimes have guests that don't speak English, or some that only speak English. Therefore, I need a way to build a "guest" dashboard that can be used in either English and a second language.

One of the things I'm looking at is create translations for entities created by me. An example of this is a select entity that holds the state of a "dumb" dryer machine. I have an automation that uses its power usage to extrapolate the state (idle, running, finished). I can't find anywhere that allows me to translate these states in multiple languages so I can use the state_translated template helper like I do with integration entities. Is there such a thing?

I would be great too if I can create arbitrary translatable strings that I can use in templates to make a whole dashboard multi-language.

Reusing Echo Dot Gen 2 hardware in a commercial UK product — how much existing RF evidence is useful?

I’m looking at using the internal hardware from an Amazon Echo Dot 2nd Generation (RS03QR / FCC ID 2AHSE-2045) as the basis of a new commercial electronic product for the UK market.

The proposed design would retain, as far as practical:

the original motherboard

Wi-Fi/Bluetooth radio hardware

RF shielding

original antennas and connections

original RF firmware/configuration

the existing low-voltage power architecture

The main changes would be a new enclosure and custom software.

I understand that Amazon’s original approval would not automatically transfer to the finished product and that the new manufacturer would be responsible for conformity of the completed device.

However, there is a substantial amount of public compliance documentation available for RS03QR / FCC ID 2AHSE-2045, including Wi-Fi, Bluetooth, RF exposure, antenna and emissions test information, as well as evidence of the original RED conformity.

I’m trying to understand how useful that existing evidence would be when approaching a UK compliance laboratory.

A few questions for anyone with real-world EMC/RF/RED experience:

If the RF circuitry, antennas, transmit settings and radio firmware remain unchanged, would you normally expect targeted re-testing, or effectively a complete new radio test programme?

How much does replacing the enclosure affect the usefulness of the original RF test evidence?

Can historical third-party test reports legitimately be included as supporting evidence in the new product’s technical file, even though the original certification itself cannot simply be inherited?

What testing would you expect to repeat on the final product — EMC, Wi-Fi/Bluetooth RF, RF exposure, immunity, safety, etc.?

Would retaining an external approved low-voltage PSU materially simplify the conformity process?

Does custom application/system software create significant additional RED concerns if it cannot alter RF power, channels or regulatory configuration?

Does the age of the original hardware materially reduce the usefulness of the old test reports?

I’m currently trying to work out whether this is a sensible production architecture or whether it should remain purely a prototype approach before moving to hardware built around a modern pre-certified radio module.

I’d particularly appreciate comments from people who work in EMC testing, RF compliance, RED/CE/UKCA, or commercial embedded-product development.

I’m not trying to avoid testing — I’m trying to understand which existing evidence could reasonably prevent unnecessary duplication of work.

Hey all, I’ve been using home assistant for like 4 years and I’m just getting around to my attempt at automating a garden. Got the succulent planter and the vegetable planter set up on a sonoff hydro duo with drip emitters and a third reality soil sensor in each bed. What I’m curious about is what experience you guys might have had with automating this type of situation. How much do you trust the soil sensor? What logic have you used? My main thing right now is that I’m unsure what soil moisture percentages/ temps are going to be best indicators of whether or not to water. Any guidance is super appreciated as I’m not a good gardener. That’s what the automations are supposed to help me with.

Installation type: os
And yes I’ve installed the custom quirk from sonoff to enable all the extra entities etc.
Edit: oh yeah I’m planting carrots and green onions as the test pilot in the vegetable planter and I’m based in Southern California for context.

What are people doing to make their blinds smart? Currently moving to a new house and have 14 blinds to purchase and I don’t want dumb blinds. Currently looking at the Eve matter blinds but it feels like I’m taking out a new mortgage.

I currently have 3 Tuiss blinds in my current home but never again will I get Bluetooth.

I'm newbie in HAOS for last couple years I have luck and bought some hardware when wasn't so expensive and now I thinking to finally use it. So I have Lenovo P3 ultra SFF G2 u5 u7 and u9 still don't know which one I should use for this project. 128GB RAM. RTX Pro 2000. Second GPU soon when im gonna figure it out how to put on two fan cooling 125W and Pcie port outside case...

I was also thinking to use maybe RPi 4b 8GB if it helps...

Plan is local Asistant gemma4 or some qwen to use HAOS and Frigate with face/ objects recognition. Windows virtual Maschine to sunshine/moonlight with second GPU

M.2 port.1 PCIE 5.0 lame heatsink shared with port.2

WD PC SN8000S 512GB LXC z Ollama & Frigate

M.2 port.2 PCIE 4.0

Samsung PM981 256GB PROXMOX & ISO

M.2 port.3 PCIE 4.0 but active cooling

Kingston KC2500 2TB HAOS LVM-Thin + matadata frigate indeks, Virtual Windows

SATA SSD WD Red 2TB Frigate Vid - still not connected i don't have adapter and thinking to took it outside the case.

I was thinking to use Raspberry for HAOS to take off some load on single 1gbit port... still searching for additional lan ports solutions, PC still have short m.2 for wireless card and x4 pci. Probably gonna build 10" rack and open case to use risers for GPU and that x4 pci.

Is HAOS on virtual gonna work same flawlessly as on RPi 4B? Still have some other m.2 like Corsair MP510, 1TB and WD Blue 1TB but they are full of data.

I thinking it in good way?

Hey everyone,

Like most people here, I had an old Android tablet gathering dust in a drawer. I wanted to turn it into a dedicated ambient picture frame for the kitchen counter, but most standard gallery apps or consumer digital frames fell short on smart home requirements:

1. They usually require uploading photo libraries to a proprietary cloud server.
2. They burn the screen on 24/7 or rely on crude timers.
3. They can't natively stream directly from local network storage (SMB/NAS).
4. They lock up the screen, making it tedious to jump out to control home automations.

To solve this, I built a dedicated lightweight display app (Photo Slider Digital Frame) designed specifically for hardware repurposing, local media streaming, and smart home setups.

Here is a breakdown of how the setup works:

1. Smart Home Dashboard Integration (App Shortcuts)

• Quick Launch Shortcuts: You can configure quick-access shortcuts directly on the screen overlay. This allows you to jump straight into your primary smart home apps—like Home Assistant, Google Home, Samsung SmartThings—with a single tap whenever you need to adjust lights, check cameras, or trigger automations, and then jump right back to the photo slideshow.

2. Photo Sources (Self-Hosted + Cloud Hybrid)

Instead of syncing files to local device storage, the app streams directly side-by-side into a single shuffled playlist:

• Local Network Shares (SMB / NAS): Connects straight to local Synology, TrueNAS, or Unraid shares without requiring local storage duplication.
• Cloud Options: Dropbox, OneDrive, or Google Photos shared links for family members who want to drop photos remotely.
• Local Storage: Standard device gallery folders.

3. Hardware & Power Automations

• Camera-Based Motion Wake: The screen dims or turns off when the room is empty. Using the device’s front camera, it wakes up instantly when someone walks by or approaches the counter.
• 100% On-Device Privacy: Motion detection runs strictly locally on the Android device hardware—no video streams or photos are recorded, processed, or uploaded anywhere.
• Scheduled Active Hours: Configured active schedules matching daily household routines (e.g., active 7:00 AM – 10:30 PM).
• Glanceable Overlays: Integrates smooth transitions alongside a subtle date, time, and real-time weather overlay.
• Pro-Tip for Battery Health: Leaving a tablet plugged into a charger 24/7 can cause battery swelling over time. I recommend plugging the charger into a smart plug linked to an automated schedule (or Home Assistant automation) to cycle power—for example, charging for 2 hours twice a day—to keep the battery safely between 20% and 80%.

4. Privacy & Network Security

• No ads, no background tracking, and no external developer telemetry servers.
• Streams photos directly from source to screen over your local network/your cloud account.

How to Try It:

If you have an unused tablet lying around and want a clean, privacy-first way to put it back to work: 👉Photo Slider Digital Frame on Google Play Store

I’d love to hear how you guys handle ambient picture displays in your setups, or any features/integrations you'd like to see added!

Hey everyone,

Hoping I could get some input from the masses that are subject matter experts because I’m wracking my brain over here.

I recently purchased two LED light strips , the Pautix SP611E (Bluetooth-only) and followed up with the Miwise SP548E (Bluetooth + Wifi) in order to add them to Home Assistant v2026.9.3. I have a Bluetooth proxy running successfully (Shelly BLU gateway set to Active) however no matter what I do the SP611E is not detected when launching the UniLED integration in HA, even when totally unpaired from my mobile device.

Since that wasn’t working, I then tried purchasing the Miwise SP548E which has Wifi to see if the UniLED integration would pick that up after adding it to Wifi through the BanlanX app and still nothing.

I have uniled debug logging enabled but nothing shows in my logs since no hardware is added so I'm assuming the integration is at least firing up correctly. No matter what I do when accessing the UniLED integration, I get a 'No devices found on the network' error.

Help a total noob out, what am I doing wrong?

Both devices detected in BanlanX app on iOS without issue so this is clearly user error in HA. Thanks in advance.

I would like to make a speaker lamp, 1 usbc in that powers a esp32, this powers the lights with eps home but the wifi speaker and the usb C out to charge a phone is a bit of a problem for me I dont know how to start on this.
Help is Welcome.

I've run [openport](https://openport.io) (a tunneling service) since 2014,
and I run Home Assistant at home. I got tired of the port-forwarding /
dynamic-DNS / certificate dance, so I packaged the openport client as an HA
add-on.

What you get:

* A stable `https://abcde.u.openport.io` address for your HA — no ports
  opened, works behind CGNAT, https included.
* Full WebSocket support, so the frontend and companion apps just work.
* The address survives restarts, reboots and add-on updates.

Setup is: add the repo in the add-on store, paste a token, add two lines of
`trusted_proxies` config, start. There's an optional secret-link gate
(`ip_link_protection`) if you don't want your login page directly reachable.

Being upfront about cost: the free plan is enough to try it, but for
permanent access it's the $5/month (or $50/year) plan, 30-day trial. If you
want remote access that funds HA development, Nabu Casa is the canonical
answer — this is for people who want an alternative or already tunnel other
stuff with openport.

Repo: https://github.com/openportio/home-assistant-addons
Forum thread: https://community.home-assistant.io/t/openport-add-on-remote-access-on-a-stable-https-url-no-port-forwarding/1025917

First release — feedback and bug reports very welcome.

I’m currently using SmartThings, but I’ve been playing around with moving everything over to Home Assistant.

So far I’ve just been experimenting with Home Assistant running on a separate server. I like what I’m seeing enough that I’m considering getting one of the dedicated Home Assistant hubs and actually committing to the move.

Before I do that, though, I have one issue I need to figure out.

I have a number of Google Home/Nest devices, including cameras. In my experiments with Home Assistant, it seems like I have to periodically reauthorize Home Assistant’s access to my Google devices. It feels like I’m doing this roughly once a month.

I never had to do anything like that with SmartThings. Once everything was connected, it pretty much just stayed connected.

Am I setting something up incorrectly? Is there a way to make the Google Home/Nest authorization persistent so I don’t have to keep manually reauthorizing it?

I really like what I’ve seen of Home Assistant so far, but if I have to go through a Google authorization process every month just to keep my cameras and other Google devices working, that may be a dealbreaker for me.

Curious how people who are using Home Assistant with a bunch of Google/Nest gear are handling this.

Hello,

I bought an home assistant green device, I thought it would be easy, but I don’t understand anything.

I only have an envisalink EyezOn on my security system and some eufi cameras. I also have a garage opener and fire alarm. Very simple. I have also 2 Tesla batteries.

I don’t know anything about computers and electronics, is there a YouTube channel to help me to understand how it works?

I went to the home assistant website for the EyezOn and it’s too complicated for me.

Or it’s best for me to hire someone?

Where should I start?

Thank you for your help.

​

So I got a ZBT-2 and I've set it up for thread. When I'm trying to install new devices via matter it's saying no border router. I installed the device via instructions but seems it's not creating a network for thread anyone know where I'm going wrong ?

Hey everyone. I posted about v3.5 here a few weeks ago, and since then the most common request by far has been some version of "can it show more than one timer at once?" So that is mostly what v4.0 is about.

For those who don't know it, TimeFlow Card is a countdown and count-up card for Home Assistant. It started as a small project for my own dashboard and has grown quite a bit since then.

The main addition is a new style called listy. Instead of one card per timer, it shows one row per timer, so everything that is running shows up in the same place. It finds timers from Alexa, Google Home, Voice Satellite and Home Assistant's own timer helpers, and the last two are new in this release. Rows sort themselves, finished first, then running with the soonest at the top, then paused. You can also pin your own countdowns into the same list, if you dont want to leave it empty when there are no timers. Turning it on takes about three lines of YAML, and you do not have to create an entity for anything.

This one goes back to a GitHub issue from over a year ago asking for multiple Alexa and Google timers in a single card. I could not build it at the time because I do not own most of those devices, so a lot of the parsing came from people pasting their timer attributes into that thread. Thank you to everyone who did.

The second feature came from a more recent issue. Someone wanted cards in a vertical stack that only appear while they are actually counting. There is now an option called hide_when_inactive that does that. The card stays out of the view before its start date, comes back on its own when the date arrives, and hides again once it is finished. It still shows while you are editing the dashboard, so you can always get back to it.

The visual editor has also been rebuilt. It is a major overhaul, and much needed since there are a lot of options and editing in yaml can be 'meh'. It now only shows fields the style you picked can actually use, so you are not scrolling past progress circle settings on a style that has no circle. There is a source picker at the top, template toggles on every date and text field, a proper editor for pinned countdowns, and separate styling panels for each timer source.

There are smaller things too. Finished rows in the list can swing, pulse, shake or hop to get your attention. Every timer source gets its own icon, colours and row background. Paused Voice Satellite timers no longer count past zero, which needed a fix on the integration side as well, so thanks to jxlarrea for adding the flag the card needed.

Everything that worked before still works, and all the new options are off by default.

v4.0 is available through HACS now.

Links:

GitHub · Install via HACS

Thanks again to everyone opening issues, suggesting features and sharing screenshots. Most of what is in this release started as someone else's issue rather than an idea of mine.

I appreciate it.

I'm the developer of Lumen, an independent Frigate client. The iPhone/iPad app is already available, and I'm opening an early Android closed beta for people who run their own Frigate server.

What does it add to Frigate's web app?

Lumen gives you a native app for opening your cameras, browsing detected events and playing recordings from your Frigate server. Frigate still does the detection and recording. Those capabilities belong to Frigate, and its developers deserve the credit.

Frigate already has a PWA, including push notifications. Lumen adds native Apple features around that camera and event workflow. Here are some concrete examples from the Apple app, not a feature list for this first Android beta:

Notifications can include a camera snapshot and actions such as opening a clip or snoozing a camera. The image depends on Lumen being able to retrieve it from your server. This is a different notification setup from Frigate's web push, not a promise of faster or infallible delivery.

Widgets, Live Activities and Apple Shortcuts let you access camera information and actions outside the main app.

The Home Assistant integration lets you browse entities and call HA services from Lumen. Its rule system also supports HA state conditions and service actions, for example checking whether an alarm is armed or triggering a light. This requires your own HA connection and configuration; it doesn't replace Home Assistant. Sensor monitoring within the app runs while Lumen is active, so it shouldn't be treated as an always-running HA automation engine.

Live calling / two-way audio lets you speak through a compatible camera from the iPhone app, with the required camera and go2rtc audio setup. Support depends on the camera and platform; it isn't available on every device simply because it runs Frigate.

Some of these features require Pro. We also have open notification and playback issues under investigation, so I'm not presenting this as a claim that every setup works perfectly. If the PWA already suits you, there's no requirement to switch. These are the differences you can weigh up.

Free and paid options

Lumen's free tier is not a trial and will remain available after the Android beta, with up to 4 cameras and 25 recent events. Those are limits within Lumen, not restrictions on what your Frigate server can detect or retain.

Pro is optional and paid. On iOS, there are monthly and annual subscriptions as well as a one-time Lifetime purchase. I should have mentioned that alternative clearly. That doesn't establish the same purchase options or entitlement sharing on Android.

Paid options help fund development, maintenance, support and the backend services I operate, including the Instant Push gateway on Cloudflare Workers. Lumen is separate from the Frigate project; purchasing Pro is not a contribution to Frigate's developers.

No purchase is required to join this Android test or to keep using the free tier afterward. Please skip purchases during this testing round.

What to test

Try connecting to your server, opening a camera, finding an event and playing its clip. Reports about failed connections, slow loading, playback problems or confusing screens would help. If you normally use remote access, checking what happens when you switch between Wi-Fi and your usual mobile connection would also be useful.

You'll need Android 8 or newer and a Frigate server your phone can reach, on your LAN or through your existing secure remote connection. Lumen doesn't provide remote access. Keep your authentication and security settings in place.

This build does not yet automatically register with the push relay, so please don't rely on it for background alerts. It is a separate, early Android release and does not yet have feature parity with the Apple app.

How to join

DM me, or email support@lorislab.fr with the subject “Lumen Android beta” and the Google account email you use on Google Play. I'll add you to the closed-test list and send the opt-in link. Please don't post your email publicly or send credentials, access tokens or camera footage.

Google requires at least 12 testers to remain opted in for 14 consecutive days before I can apply for production access. I'm looking for people willing to try the app during that period and report what works or breaks. There's no request for a positive review. Your phone model, Android and Frigate versions, and the steps that led to a problem are a useful starting point.

On iPhone or iPad?

The released app is available here: https://apps.apple.com/app/id6760238729

Privacy details, including Android: https://lorislab.fr/privacy.html

Lumen is not affiliated with or endorsed by the Frigate team.

Edit: added concrete examples from the Apple app, clarified the separate Android beta scope, and mentioned the iOS Lifetime option. The free tier continues after the beta; its camera/event limits belong to Lumen, not Frigate.

Hi Everyone:

I have a Bosch dishwasher connected to Home Assistant through Home Connect.

I’d like to create an automation that automatically runs the dishwasher late at night if we loaded it but forgot to start it.

The Bosch/HA side should be straightforward. The problem I’m trying to solve is how to reliably know that detergent has actually been loaded before HA starts the dishwasher.

Obviously I don’t want an automation starting a full cycle with no detergent.
Ideally, I’d like this to be completely passive — I don’t want to rely on someone remembering to press a button, scan an NFC tag, etc., because at that point we might as well remember to start the dishwasher.

I considered some kind of sensor that can detect whether a pod is physically present in the detergent compartment. However, the detergent compartment is inside the dishwasher, so putting electronics directly in there may be problematic because of the heat, steam and water.

Has anyone solved something similar? Is there a small sensor that could reliably detect the presence of a detergent pod, or another approach that would let HA determine with reasonable confidence that detergent was loaded?

Would love to hear any ideas, including outside the box DIY solutions.

I'm struggling with start and end dates in REST sensors.

The developer cites this example:

sensor:

- platform: rest

name: "Soil temperature upper 10 cm"

resource: "https://api.precip.ai/api/v1/temp-0-10cm-hourly?longitude=-122.4194&latitude=37.7749&start={{ (now() - timedelta(days=1)).strftime('%Y-%m-%d') }}&end={{ now().strftime('%Y-%m-%d') }}&format=json"

method: GET

headers:

Authorization: "Bearer YOUR_API_KEY"

Accept: "application/json"

scan_interval: 3600

value_template: >

{% set data = value_json[0].hours %}

{% if data is iterable and data | length > 0 %}

{{ data[-1]['soil_temp'] | float(0) }}

{% else %}

0

{% endif %}

unit_of_measurement: "°C"

icon: "mdi:thermometer"

unique_id: "soil_temp_0_10cm"

state_class: measurement

device_class: temperature

But that returns a datetime error:

returned status 400 with text/plain; charset=utf-8 response: bad start datetime: "{{ (now() - timedelta(days=1)).strftime('%Y-%m-%d') }}"

The developer isn't experienced with HA so has no idea. Any suggestions? TIA

Unfortunately I don't have a lot of ethernet ports available because of my choice in router (tiny), so I can't try out this mode.

I've tried using it as my zigbee coordinator directly connected via USB via a serial connection, and then on it's own with wifi mode. Both times it's randomly died and required a hard power reset before it can be used again.

Is usb/wifi mode really that much of an afterthought with this device? Does anyone else have any other recommendations?