Comments (6)
Which release and which PR introduced this property?
065c7b5, part of 1.9.14 release.
Which Home Assistant version is needed to run Alarmo >= 1.9.14?
I only tested with HA 2024.1. Older versions may work as well but untested.
1.9.13 was working fine which has been released at Nov 4, 2023 (thats 3 months since).
Feel free to keep using that version until you're ready for updating HA as well.
I could not spot a "requires at least Home Assistant version 202x.x" breaking change or note on any release notes at https://github.com/nielsfaber/alarmo/releases. I think it is a good practise to at least leave a note if those dependency requirements are not handled properly by HACS.
Alarmo releases are always made and tested with up-to-date (stable) HA version, so the Alarmo release of January was tested on HA 2024.1 (January release). Older versions may work but untested.
Since HA is a plug-in of HA, the development goes hand-in-hand.
Regularly changes in HA force me to make updates in Alarmo.
Are you aware of https://hacs.xyz/docs/publish/integration (see blueprint at https://github.com/ludeeus/integration_blueprint/blob/main/requirements.txt)?
Yes. This project has it set at 2023.4. I will update it to 2023.11 (date of the PR with the breaking change).
from alarmo.
@nielsfaber following up on #882 (comment)
@bcutter your issue is not related to the topic discussed here. I think your issue is caused by an incompatible HA version. The error is related to a property that was added to HA about half a year ago.
Yes, I need to update my HA. At the same time:
- Which release and which PR introduced this property?
- Which Home Assistant version is needed to run Alarmo >= 1.9.14?
- 1.9.13 was working fine which has been released at Nov 4, 2023 (thats 3 months since).
- I could not spot a "requires at least Home Assistant version 202x.x" breaking change or note on any release notes at https://github.com/nielsfaber/alarmo/releases. I think it is a good practise to at least leave a note if those dependency requirements are not handled properly by HACS.
Are you aware of https://hacs.xyz/docs/publish/integration (see blueprint at https://github.com/ludeeus/integration_blueprint/blob/main/requirements.txt)?
homeassistant==2023.8.0
That way people would not run into such issues - the updates are simply not shown at all. That's the "perfect" solution for shipping integrations with HACS. Using the release notes is just the 2nd best attempt, but at least... "better than nothing" :-)
from alarmo.
Thank you for that detailled information 👍
Feel free to keep using that version until you're ready for updating HA as well.
This is the way.
Yes. This project has it set at 2023.4. I will update it to 2023.11 (date of the PR with the breaking change).
If that makes the 1.9.14 update to disappear as long as ones HA is not up to date, I think that's a good "solution" for these cases. Let me know once 1.9.14 (or if necessary 1.9.15) has been changed that way so I can confirm (in theory the update should then not be shown anymore in my HACS (disappear)). Let me check - after that up to you if you want to close this issue.
from alarmo.
The minimum required HA version is already updated:
Line 7 in 8364c75
I believe this setting applies to the whole project. This is not a file that is part of (or connected to) a released version.
So HACS should state that Alarmo is not compatible for your HA version and also hide any updates.
I only tested this functionality myself in combination with a fresh installation. If I remember correctly there was a warning about incompatibility but it was still possible to install any version.
HACS does use internal caching so this change I made one hour ago will probably not be visible to you.
From my side it would be preferable if I could mark a required minimum HA version per Alarmo release.
That way a user would always see the latest updatable version that matches their HA installation.
But I don't believe this is possible in HACS currently.
after that up to you if you want to close this issue.
I think we agree there is not really any bug being discussed here but an incompatibility issue.
I will close this since there will not be any follow up (you know what to do if you want to use 1.9.14 without errors).
A closed issue still allows for further discussion.
from alarmo.
From my side it would be preferable if I could mark a required minimum HA version per Alarmo release.
That way a user would always see the latest updatable version that matches their HA installation.
But I don't believe this is possible in HACS currently.
Oh I was expecting (hoping) this is the case as I did not have a deeper look at the HACS developer docs. What a pity if this is not the case :-( That's quite limitating if you can only set the minimum HA version for the WHOLE integration. That indeed has downsides like new users not being able to use Alarmo at all, because they can't install a former version which would work just fine with their HA version. Are you able to spot the right repo at https://github.com/hacs and would you create a feature request for this must-have feature?
Currently I still see the update unfortunately. No HA restart yet. Hope it will disappear - as there's also no "hide updates" function in HACS like it is in HA Core. So starring at the update I can (should) not install while HA is not up to date is a bit hmm.
But yes, this issue is about update dependency management, not a functional Alarmo integration issue itself, you're absolutely right.
from alarmo.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
from alarmo.
Related Issues (20)
- Alarm can no longer be disarmed by Alarmo Button HOT 11
- Async_alarm_disarm() takes 1 positional argument but 2 were given HOT 14
- Disarm MQTT not working HOT 9
- Sensors open with delayed alarm HOT 1
- Alarmo With google HOT 25
- Cannot disable alarm through HA control panel or automation HOT 1
- Alarmo not disarming HOT 4
- AlarmoBaseEntity.async_alarm_disarm() takes 1 positional argument but 2 were given HOT 1
- Areas & Modes seem to overlaps rather than play nicely? HOT 1
- enable/disable no longer possible after update to 2024.6.1 HOT 9
- Failed in call alarm_control_panel/alarm_disarm. AlarmoBaseEntity.async_alarm_disarm() takes 1 positional argument but 2 were given HOT 3
- Possibility for noficiations/actions for "sequence of events" in Triggered-state
- Failed to Call Service HOT 3
- Different code settings per area HOT 1
- Entity alarm_control_panel. not support this service. HOT 2
- Multilanguage support with Google Assistant HOT 1
- Alert when arming and a sensor is open HOT 1
- Wrong version shown HOT 1
- Missing Alarm control panel after updating HOT 2
- Disable specific sensors temporary with Automation HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from alarmo.