The integration supports G90-based security systems might be distributed under different vendors - Golden Security, PST, Kerui etc. Those having G90 in the model name has a good chance to be supported - please give it a try and report back.

Actual interface with the security system is implemented via pyg90alarm Python package.

You might want to enable door close alerts ("Alarm Alert -> Door close" in mobile application), so the integration properly reflects the state of a door sensor. Not enabling it will lead the sensor to become inactive in 3 seconds, same behavior as for other sensors types. This is another limitation of the device, as it doesn't indicate when the sensor became inactive for most of the cases. Please note enabling the door alert will have more notifications (and possible SMS messages if you enabled those in mobile application) to be sent.

The panel configuration options are available as Home Assistant entities and can be configured through the UI - navigate to "Settings -> Devices & Services -> Golden Security Alarm -> <serial number>", corresponding entities will be listed there. SIA and CID options are only shown when the panel supports them (some panels do not expose SIA/CID configuration).

Notifications from the alarm panel are essential for the integration - the notifications allow to reflect sensor and panel states change as they occurs.

The integration supports several protocols for the notifications:

• Cloud protocol (the default, recommended)
• Local protocol
• Cloud protocol with chaining

Please see below for the details on each.

For the protocol to be active at the alarm panel the device should have its IP address set to 10.10.10.250. That is a specific limitation of how device's firmware works.

Additionally, the protocol implies the cloud servers are operational - missing or delayed notifications with this protocol have been seen when vendor's cloud servers are inoperational. Presumably, device takes cloud communications with higher priority and doesn't get to local notifications protocol if cloud communications are slow or timing out.

If your alarm panel is in a subnet different from one Home Assistant runs, making the integration receiving the local notification messages will require additional steps - the notifications are sent by alarm panel as broadcast packets, thus you'll need those forwarded to the Home Assistant subnet. Alternatively, you could consider the alert simulation or a different protocol below.

Despite its name the procotol does not depend on any Internet connectivity (unless using the chained mode below), the integration just implements same protocol the panel uses to communicate with cloud servers - the devices is "tricked" into thinking it is still communicating with the cloud servers, while actual communication happens with the integration. As the result, no alarm panel's traffic will be sent to vendor's cloud servers - they will consider the panel being offline, so does the mobile application.

With this protocol it is no longer required for the alarm panel to have 10.10.10.250 IP address.

The protocol requires the Home Assistant instance to be reachable by the alarm panel over the network using IP address and port configured in the integration, IP address to send notifications to and Port to send notifications to options. Depending on your network setup you might need to adjust Port to listen for panel traffic on to be different from the above. For example, you run Home Assistant under Kubernetes and expose the service on a different port - in that case you could leave ``Port to listen for panel traffic onwith default value, and configure the service's port asPort to send notifications to`. Same applies to other network setups like Docker, reverse proxies etc.

It works similar to Cloud notifications protocol, but also sends a copy of each notification up to vendor's cloud servers. Thus, it does depend on Internet connectivity and the cloud servers to be operational, but allows the mobile application to function normally.

The integration will still properly reflect sensor and panel state changes even if cloud servers are down, it won't just send notifications copy there for apparent reasons.

• Use cloud notifications protocol if

  • You cannot or don't want to assign the alarm panel 10.10.10.250 IP address
  • You would like to be fully local with no dependency on cloud servers
  • You are ok to have mobile application showing the panel as offline (apparently, only applies when the mobile application works still)

• Use local notifications protocol if

  • You can assign the alarm panel 10.10.10.250 IP address and
  • You are ok to have sensors not reflecting state change when cloud server are down

• Use cloud notifications protocol with chaining if

  • You cannot or don't want to assign the alarm panel 10.10.10.250 IP address or
  • Do not want sensors not reflecting their state when cloud servers are down
  • Would like the mobile application to work normally

If none above works for you - the integration supports simulating the device alerts from the history it records. It is implemented by pyg90alarm Python package, and it does so by periodically polling the device history and sending newer entries down the code path as if those been received from device. The mode is enabled by selecting Simulate device alerts from history option in integration configuration, and enabling particular alert types you're interested in via mobile application. This mode will still have limitations as not reflecting the state of motion sensors (as those come as notifications not alerts).

If no notifications protocols are possible still, the integration will have additional limitations:

• Delays reflecting panel status up to 30 seconds
• Sensor state changes will be absent

To help diagnosing if notifications protocol is working properly the integration exposes additional sensors:

• Last device packet time: indicates the time when integration successfully processed the last notification from the panel
• Last upstream packet time: indicates the time when cloud servers responded to a copy of notification the integration sent - the sensor is only applicable when using cloud notifications protocol with chaining

• Install HACS by following Setup and Configuration steps
• Download Golden Security Alarm integration in HACS
• Add the Golden Security Alarm integration in Home Assistant

If you need to troubleshoot the integration it is recommended to first enable debug logging for it, to capture additional details.

For that you'll need to add following options to Home Assistant's configuration.yaml. Please note this will also set logging level to info for all other Home Assistant components - please adjust default: info to fit your needs.

logger:
  default: info
  logs:
    pyg90alarm: debug
    homeassistant.gs_alarm: debug
    custom_components.gs_alarm: debug