Sev

sorry, was travelling - not sure I understand the question the upgrade moved the configurations if that is the question - this is what shows in HA   ...

gave it another shot, changing config/arrlo.yaml to include: mode_api: v2 allows me to change the modes again but now additional errors show up > Logger: homeassistant.components.alarm_control_panel Source: helpers/deprecation.py:205 Integration: Alarm...

it is Steve - thanks

I am also highly interested on arm to run on Oracle cloud builds fail - mainly due to filebeat but filebeat arm builds seem to exist

actually I have just figured it out - its the naming conventions of the columns - there are none like eg unbound.client.ip its client.ip

damn this was a tricky one but I finally got it to work. **edit: 02-10-2024 - had to do some minor changes** **My setup is as follows:** **my docker compose...

seems like your signalling is trying to reach port: 10000 instead of using 443 and then being handled ... my setup only exposes 80 and 443 externally no other ports...

based on your previous message it is attempting to make the call to port 10000 instead of 443 not sure what prompts it to do that, check your configuration again,...

did any of you make any progress to update this integration/detection?

I am in the same situation since yesterday and the real issue is there is no way to create an integration user with the required keys that doesnt rollover -...