pyg90alarm.local.targeted_discovery
Discovers G90 alarm panel devices with specific ID.
Classes
|
Discovered device with specific ID. |
|
Discovers alarm panel devices with specific ID. |
|
Wire representation of the information about discovered device. |
- class pyg90alarm.local.targeted_discovery.G90TargetedDiscoveryInfo(message, product_name, wifi_protocol_version, cloud_protocol_version, mcu_hw_version, fw_version, gsm_status, wifi_status, server_status, reserved1, reserved2, gsm_signal_level, wifi_signal_level)
Bases:
objectWire representation of the information about discovered device.
- class pyg90alarm.local.targeted_discovery.G90DiscoveredDeviceTargeted(message, product_name, wifi_protocol_version, cloud_protocol_version, mcu_hw_version, fw_version, gsm_status, wifi_status, server_status, reserved1, reserved2, gsm_signal_level, wifi_signal_level, host, port, guid)
Bases:
G90TargetedDiscoveryInfoDiscovered device with specific ID.
- class pyg90alarm.local.targeted_discovery.G90TargetedDiscovery(device_id, **kwargs)
Bases:
G90BaseCommandDiscovers alarm panel devices with specific ID.
- async process()
Initiates the device discovery process.
- Return type:
- property devices: List[G90DiscoveredDeviceTargeted]
The list of discovered devices.
- pause_writing()
Called when the transport’s buffer goes over the high-water mark.
Pause and resume calls are paired – pause_writing() is called once when the buffer goes strictly over the high-water mark (even if subsequent writes increases the buffer size even more), and eventually resume_writing() is called once when the buffer size reaches the low-water mark.
Note that if the buffer size equals the high-water mark, pause_writing() is not called – it must go strictly over. Conversely, resume_writing() is called when the buffer size is equal or lower than the low-water mark. These end conditions are important to ensure that things go as expected when either mark is zero.
NOTE: This is the only Protocol callback that is not called through EventLoop.call_soon() – if it were, it would have no effect when it’s most needed (when the app keeps writing without yielding until pause_writing() is called).
- resume_writing()
Called when the transport’s buffer drains below the low-water mark.
See pause_writing() for details.