Jevgeni Kiski
Doing actions on behalf of the user on the panel would be complicated but I can make PAI validate sent code and then perform an action. You won't get any...
It can not lead to a vulnerability if you use an MQTT password. Via HASS: Your phone is still protected with a pin code. In hass it is possible to...
😆 Isn't that over complicated? I imagine configuring homeassistant to calculate that. Sounds crazy. https://www.home-assistant.io/integrations/alarm_control_panel.mqtt/
> I think mqtt password is not enough, the client need to be capable to connect to brokers with TLS enabled. If not the password still can be captured as...
> For homeassistant, alternative ideas are welcome :) Evil 🤣 > Also, even with TLS, any client connected to the broker can disarm the panel. If someone as a requirement...
MQTT_CHALLENGE_SECRET value type fixed.
Sure we can. Need to find time for it.
Loading 999 users from EEPROM takes a lot of time even on EVO.
for EVO user definitions with codes are loaded in PAI.
I have pushed https://github.com/ParadoxAlarmInterface/pai/tree/send_panic branch to verify the code. MQTT topic format: `paradox/panic/{panic_type}/{partition}` Payload: `{user_id}` Replace data in curly brackets. `panic_type` can be: - emergency - medical - fire `user_id`...