At least you can interact.
In mobile Apple devices with iOS <= 16.3 - sliders are not displayed or displayed partially.
That was a “brilliant” decision of developers of Material web controls to make them incompatible with turned-to-be-old versions of iOS.
Can anybody tell me if there is a way to get the different items of a todo list?
E.g. if a todo list contains:
- task a
- task b
Is there a sensor / entity that exposes the different tasks? How would I be able to fetch these in a custom card?
The docs mention that the state of a to-do list entity is a number, which represents the number of incomplete items in the list. But in the attributes, I don’t see the actual tasks inside the todo list nor does the documentation provide a service to fetch the actual tasks.
Never mind - a PR is open to add the service todo.get_items.
Hey thanks for the reply. Sorry I should have said trigger rather than condition.
I’m picturing a trigger where you can specify a number of other triggers which must happen in sequence for the overall trigger to occur.
For example if I want something to happen if someone enters through the garage I might set up a sequence of driveway motion, garage door open, garage inner door open, hallway motion sensor trigger. Triggering any of those things in a different order wouldn’t run the automation, only them happening in that particular sequence.
It’s possible to do this by emulating a state machine with helpers but it’s a bit clunky that way.
Make a trigger for the first and then use a sequence of wait for triggers under the action section for the rest.
You should start a new topic to chat more about this, since it’s not related to the release.
5 Likes
That’s a custom Integration so you need to follow it up with the repo dev’s. ie: ONLY in that other thread.
Thanks for the answer… I read the release blog and the To-Do list Integration page and could not figure this one out until I saw your answer 
.
I have the same problem. All the sensors defined in Node-RED have disappeared. What can I do to solve it?
No problem here, all sensors are updating as expected and are visible. What exactly do you mean with “disappearded”? Did you check the Node-RED Companion integration for errors and are the sensors still triggered in your Flows?
How much free memory do you have when running HA. I had to upgrade from an old Pi 3 to a 4 with 4Gb. HA had slow memory creep and the 1Gb Pi was hanging around 150mb free after a few days. Updates would not work unless I rebooted and freed up as much memory as I could. Now I have over 2G free and updates are fine.
Where is the “To do list” located? Instructions say “You can find the to-do list dashboard in the main sidebar of your Home Assistant instance.”
Yet nothing there. Does this require a custom dashboard to work/show up?
Did you set it up?
1 Like
Same issue here. I have to reboot my Rpi 3+ almost every day. Swap is at 100% and memory >85%.
Did not realize it needed manual install. Got it now…thank you!
The RPi3a+ only has 512Mb of RAM, with the later RPi3b+ only 1Gb.
HAOS has a realistic minimum requirement of 1Gb of RAM, and really needs 2Gb to install add-ons even with zram compression.
Despite what the install docs say, as HASS adds features, more RPi3B+ owners are reporting failures and having to upgrade. Simple installs work - just don’t expect too much.
RPi 3B+ owner here. Four+ years on and still no problems to report. At this moment it’s sitting at 3-5% CPU utilization and between 58 and 59% memory (out of 1G.)
In all fairness, I’m quite sure I could kill it if I started loading up on resource-intensive features.
I also support a remote site with HAOS on a RPi3B+, but that’s very deliberately a simple install with MQTT only and it ticks by with 1Gb of RAM.
Perhaps it’s selection bias, but I’m seeing more and more posts on the forum with RPi3B+ issues and as HAOS gains features, the trend will likely increase so I’m just trying to manage expectations.
Note that the latest $99 Green has 4Gb RAM which is double that even of the 2Gb Yellow. My guess is my SSD Yellow will benefit from a CM5 when it arrives around 2026+ if for nothing else to speed up ESPhome debug cycles.
The update to 2023.11 killed the fibaro integration. The integration becomes a very big delay in reacting. I think, the newly added event handling is the cause.
Is this fixed in the update 2023.3?