Comments (20)
@smarthomefamilyverrips I only test alarmo with the latest HA version, itβs your own choice (and responsibility) to only update one without the other. HA changes a lot of things between their releases, so I have no idea about backwards compatibility. However HACS should state which HA version is required for a certain alarmo release update, at least this information is provided to HACS via this file: https://github.com/nielsfaber/alarmo/blob/main/hacs.json I do not know the procedure for rollback via HACS, but the files for manual installation of all releases ever published remain available for download in this repository.
@nielsfaber Well unfortunately it not did state anywhere that 2024.7 was needed nor I got any message from HACS about this when I updated from.the notification of a new version of alarmo within HACS
from alarmo.
@tackin You may have a point there. I have no idea how HACS works under the hood, but what you're saying makes sense. I will try to remember to update the file before the next release (in case of a breaking change) and test if it works like you describe. Thanks for the pointer π
from alarmo.
I got bitten by this to, now downgrading to the 1.10.3.
I know HACS hide release that aren't compatible usually so i didn't check, mistake happens.
Thank for this post, i could find it quickly :)
Also, please don't talk down to people who wait for ha release to be stable before pushing them to their home.
Not everyone is in the same boat, and some may want to wait for the couple bug-fix every month to be release before updating :)
from alarmo.
Sorry, this version contains changes that requires updating to HA 2024.7.
from alarmo.
@smarthomefamilyverrips
I don't know how HACS deals with this. From Alarmo's side I just provide the property, which is described as 'The minimum required Home Assistant version.' (see https://hacs.xyz/docs/publish/start#hacsjson), so HACS should be able to prevent you from updating to an incompatible release - but apparently it doesn't.
from alarmo.
@smarthomefamilyverrips
I only test alarmo with the latest HA version, itβs your own choice (and responsibility) to only update one without the other.
HA changes a lot of things between their releases, so I have no idea about backwards compatibility.
However HACS should state which HA version is required for a certain alarmo release update, at least this information is provided to HACS via this file:
https://github.com/nielsfaber/alarmo/blob/main/hacs.json
I do not know the procedure for rollback via HACS, but the files for manual installation of all releases ever published remain available for download in this repository.
from alarmo.
@nielsfaber from where should see 2024.7 is needed, HACS just prompts me there is a update, and also let's me do the update... I did re-download 10.3 and seems to work, hope it not will cause any problems in near future.
from alarmo.
.... And I was so 100% sure it will work, because you were so strict last time in requesting 2024.6
;-)
from alarmo.
Confirmed! Update to HA 2024.7 fixed the problem.
from alarmo.
I made the upgrade to v1.10.4 and the upgrade to core-2024.7.0... but HA go in Recovey mode. for me it's not fixed
from alarmo.
Ah yep, same problem here. Don't know why I updated it when I don't have 2024.7 installed and wasn't planning on it until at least .1 was available.
from alarmo.
Sorry for the offtopic, but what image do you have so that it can be updated quickly. I use the stable official, ghcr.io/home-assistant/home-assistant:stable, and it's still in version 2024.6.4.
Thanks
from alarmo.
@ajavibp this is not true. HA 2024.7 was released last night (same as alarmo release). Your link shows this as well.
from alarmo.
l It was finally updated and now works perfectly. Thank you
from alarmo.
Sorry, this version contains changes that requires updating to HA 2024.7.
@nielsfaber why this was not noted in changelog? What to do now can I rollback and redownload 10.3 from HACS?
from alarmo.
Might be, because the bump in your hacs.json to 2024.7.0 was NOT in the Release-Commit itself but was done later in an additional commit. In between HACS "saw" a new Release with "required HA-verson" still at "2024.6.0". So HACS might not be to blame.
from alarmo.
@nielsfaber
Hacs first looks at tags (releases) and the one selected in HA will be installed. If you committed a requirement change later to main, you have to create another release to get that included in HACS installs.
BTW, when you switch HACS to experimental mode, it will create update entities for each integration.
Then you can use the update install service, select the alarmo entity and provide any release or branch name to install. It can also install older releases through the service or the 'main' branch.
Very usefull if you have beta code just on a branch that you want to test through HACS before you create a release.
Edit: I just confirmed that I get the requirement error when trying to install 'main' branch on my HA 2024.6
from alarmo.
Got the same error and updating to HomeAssistant 2024.7.1 fixed it.
from alarmo.
Yeah, I think it will be helpful to cut another release from actual main, because when installing from main branch, I get the min required HA version error and it does not install on HA 2024.06. This is the expected behavior when the min HA version is set accordingly in the hacs.json file.
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 is not triggered when it should HOT 7
- Arming countdown timer as attribute HOT 5
- Alarm area groups HOT 1
- Triggering while disarmed HOT 5
- Alarmo didn't warn when Door/Windows is open HOT 1
- Being able to change the mode while pending or triggered HOT 1
- Allow open initially does not seem to reconnect sensor after close HOT 2
- Skip Exit Delay when Arming from HomeKit
- Add automation start/stop to alarm state change actions HOT 1
- Action - enable or disable automations HOT 1
- alarmo seems to self disable
- Notification: tts.speak incorrect validation
- Add Configurable Delay for "Trigger when unavailable" Feature
- Delay for triggered Sensor HOT 3
- Errors after update - setup failed HOT 3
- Alarmo not being loaded after update to latest version HOT 1
- Alarm disarming itself immediately after arming HOT 4
- Refusing to start HOT 3
- Biometric disarm HOT 1
- Temporarily disable sensor(s) based on Home Assistant entity trigger HOT 1
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.