Reports are sent in 2 or 3 messages, each of which needs a generic ok reply, depending on settings. Note this setting is only sent when it is changed and before a report is sent, not as part of the block of settings routinely sent on startup. (There is NO additional 00 in this setting.) Then the port number in hex e.g. Ip address is null terminated ascii string e.g. Lf - line fail network 00=off/01=availableĢ5 1C 20… Monitoring ip address and port. Sp - line fail signal path 00=primary/01=secondary/02=alarm mon/03=any/04=allĮn - encrypt bitmask 01=alarm report | 02=remote access | 04=alarm mon Lv - 00-03 for sia, always 03 for microtechĢ5 1C 18… Comms retries, in the following format:Ģ5 1C 1A… Ethernet device ip address, null terminated string e.g. 27 12 = 0x2712.Ģ5 1C 1E… Secondary reporting address, format as for primary.Ģ5 1C 14… Reporting format and level, in the following format: There is an additional 00 (purpose unknown) and then the port number in hex e.g. Some/all of these commands are sent on device startup, periodically and on change (via the engineer menu).Ģ5 1C 10… Primary reporting ip address and port. Regular poll for device events, send a generic ok/error reply (see above). The last byte of each command/response is a checksum (generally replaced below with XX). it does not interact with the panel through the normal panelethernet interface, but instead through the panelkeypad interface).Īll data values below are in hex. Devices like the LCE-01 provide this via a virtual keypad interface, by emulating a keypad on the RS485 bus (i.e. It does not, as far as I know, provide any direct interface to the alarm to allow it to be set/unset/etc. It can also be used to configure the alarm panel through Honeywell software. The adapter normally provides reports to an Alarm Receiving Centre (ARC). No updates for 10 months at time of writing this.This is a belated follow-up to my previous posts, this time about the Honeywell Galaxy RS485 protocol, covering the Ethernet adapter. Or at the very least a slicker PIN entry window (auto focus to the field, etc) would make this a useable feature. Face ID/ Touch ID have been around for a long time now and are easy for developers to integrate with. But requires you to enter your pin every time, which is very cumbersome. Setting/unsetting the alarm from the app works ok. Thereby only getting notifications if the alarm is going off. Whilst I understand these are useful, ideally I’d prefer to set filters so I could turn these off as required. So you end up with a notification every time the system is set/unset. However there’s no ability to filter what notifications are received. They are cumbersome to setup within the app, but do work. The app works in its basic functionality but requires improvement to make it sleeker and actually useable day to day.įirst, the good stuff - push notifications work well.
0 kommentar(er)
