Neom
Juin 9, 2024, 5:47
1
Bonjour,
J’utilise Alarmo depuis un certain temps sans soucis, mais il semble s’etre dupliqué apres une MAJ.
Je me dis, pas grave, je MAJ mon tableau de bord avec la nouvelle entité
Bon, bah ça n’est pas la config que je voulais (code, trop de modes etc)
Quand je MAJ mon configuration.yaml, ca n’a pas d’effet…
alarm_control_panel:
- platform: manual
name: alarmo_2
code: xxx
code_arm_required: false # code is not needed for alarm to be armed
disarm_after_trigger: false # the alarm will not disarm after it has been triggered
arming_time: 0 # Time to leave the RV after arming
delay_time: 0 # Time to enter the code after entering the RV
trigger_time: 300 # The time in seconds in which the alarm is firing.
disarmed:
trigger_time: 0 # Alarm can't be triggered when disarmed
1 - comment enlever cette duplication
2 - Si compliqué, comment configurer la nouvelle entité (le code, les modes, …)?
Ma configuration
[center]## System Information
version
core-2024.6.1
installation_type
Home Assistant OS
dev
false
hassio
true
docker
true
user
root
virtualenv
false
python_version
3.12.2
os_name
Linux
os_version
6.6.29-haos
arch
x86_64
timezone
Europe/Paris
config_dir
/config
Home Assistant Community Store
GitHub API
ok
GitHub Content
ok
GitHub Web
ok
GitHub API Calls Remaining
5000
Installed Version
1.34.0
Stage
running
Available Repositories
1386
Downloaded Repositories
8
Home Assistant Cloud
logged_in
false
can_reach_cert_server
ok
can_reach_cloud_auth
ok
can_reach_cloud
ok
Home Assistant Supervisor
host_os
Home Assistant OS 12.3
update_channel
stable
supervisor_version
supervisor-2024.06.0
agent_version
1.6.0
docker_version
25.0.5
disk_total
30.8 GB
disk_used
9.1 GB
healthy
true
supported
true
host_connectivity
true
supervisor_connectivity
true
ntp_synchronized
true
virtualization
kvm
board
ova
supervisor_api
ok
version_api
ok
installed_addons
File editor (5.8.0), Terminal & SSH (9.14.0), Samba share (12.3.1), Samba Backup (5.2.0), ESPHome (2024.5.5)
Dashboards
dashboards
2
resources
2
views
6
mode
storage
Recorder
oldest_recorder_run
7 juin 2024 à 15:09
current_recorder_run
9 juin 2024 à 06:38
estimated_db_size
164.65 MiB
database_engine
sqlite
database_version
3.44.2
Sonoff
version
3.7.3 (e240aaf)
cloud_online
8 / 9
local_online
8 / 8
[/center]
___
Bonjour
je ne sais pas si tu as fait la mise a jour d’ALARMO suite a la MAJ de HA.
Mais j’ai lu qu’il était indispensable de mettre alarmo a jour suite montée de version de HA
1 « J'aime »
Bonjour,
pas de soucis avec la version 2024.6.1 et alarmo 1.10.3
Neom
Juin 9, 2024, 6:22
4
oui j’ai MAJ alarmo apres MAJ de HA
Ton soucis vient de platform: manual
et pas de alarmo. Je pense qu’il y a un bug.
opened 03:15PM - 08 Jun 24 UTC
integration: manual
### The problem
On v2024.6.1 you can not disable the code for disarming. I se… e this is a feature of the MQTT alarm, but not for the manual alarm, can code_disarm_required be added to this integration?
I understand that I can add the code into an automation to disarm, and this partially achieves my goal. However, if you use the UI you must enter a disarm code.
### What version of Home Assistant Core has the issue?
2024.6.1
### What was the last working version of Home Assistant Core?
2024.5
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
Manual Alarm
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/manual/
### Diagnostics information
_No response_
### Example YAML snippet
```yaml
configuration.yaml:
alarm_control_panel:
- platform: manual
name: house
trigger_time: 600
disarm_after_trigger: false
delay_time: 0
arming_time: 0
code_arm_required: false
code: !secret alarm_code
```
### Anything in the logs that might be useful for us?
_No response_
### Additional information
_No response_
Neom
Juin 9, 2024, 7:51
6
ok merci, j’ai quand même 2 entités alarmo et je n’arrive pas a configurer la nouvelle
dans le menu Alarmo
dans le dashboard
Va dans appareils et service / alarmo et configurer. Et désactive ceux que tu veux pas.
Neom
Juin 9, 2024, 9:49
8
c’est ce que j’ai fait, mais ca semble s’appliquer sur la mauvaise instance