Qsys Monitoring Proxy

[Zulema Estabrooks]

Theprogram allows technology companies to develop market-ready solutions seamlessly integrated with Q-SYS, a cloud-manageable platform for audio, video, and control. Nureva has introduced a Q-SYS-certified plugin for its HDL310 and HDL410 audio conferencing systems (the HDL pro series), offering audio control enhancements to simplify the remote experience.

The Q-SYS plugin empowers users to modify the HDL pro series systems directly from the Q-SYS audio, video, and control platform. It allows for recalibration of the microphone system, adjustment of speaker volume, microphone mute, and EQ.

The plugin also incorporates sound location data from the HDL pro series systems, facilitating the automation of Q-SYS cameras without the need for extra programming. Users can monitor the microphone status within the plugin and connect it to a monitoring proxy for seamless monitoring and management through Q-SYS Reflect Enterprise Manager.

The two plug-and-play bundles are fully certified for Teams Rooms and offer high-quality audio and video performance that is easy and cost-effective to implement, operate, and oversee in various environments.

Devices in the Shelly family are IoT nodes connected to the Internet over WiFi. All devices support a common set of configuration parameters, some share common features. Apart from these, each device extends the common HTTP endpoints with a set of device-specific settings and behavior.

Initially, devices come preprogrammed in Access Point mode with no password set. To be able to connect to Allterco's cloud service, synchronize time, etc. the device has to be configured to connect to an existing, Internet-connected WiFi infrastructure.

Shelly devices do not have a built-in real time clock but will automatically synchronize their clock when in WiFi Client mode and there is connection to the Internet. Once the time is synchronized devices can execute commands triggered by user-defined weekly schedule or based on sunrise and sunset times. Geolocation data used for sun events is obtained automatically from the public IP address of the device. However, if this fails, tzautodetect can be disabled and the timezone and geolocation data (for sunrise and sunset calculation) can be set manually. The default NTP server is time.google.com, but a custom one can also be configured.

Since v1.7.0 Shelly devices support "local" action URLs. This allows devices to invoke actions not only on other devices, but on themselves as well. To execute a local action, the action URL should be set with a prefix

Shelly devices can report their settings and state to an Internet connected cloud service. The cloud service can modify the settings and change the device state. All communication is over SSL. This service allows device monitoring and control over the Internet using the accompanying mobile applications.

Shelly devices are built on top of, and along with Mongoose-OS. Mongoose provides an integrated framework for secure sockets, over-the-air updates, application storage, common device housekeeping tasks and more, that are making the reliability and security of the Shelly portfolio possible.

The HTTP method used for performing any of the requests below is intentionally ignored. Most endpoints will always return their specific JSON payload and perform actions if query parameters are specified.

Provides basic information about the device. It does not require HTTP authentication, even if authentication is enabled globally. This endpoint can be used in conjunction with mDNS for device discovery and identification. It accepts no parameters.

To configure timezone and location (for sunrise/sunset calculation) manually, set tzautodetect to false, so that custom values for lat, lng and timezone take effect. For a list of supported timezones, please fetch

Provides information about the current WiFi AP configuration and allows changes. The returned document is identical to the one returned by /settings in the wifi_ap key. Shelly devices do not allow the SSID for AP WiFi mode to be changed.

An identical resource is available at /settings/sta1. This allows for devices to have a second WiFi STA configuration for fallback, and will cycle between the two when the one currently selected becomes unavailable.

HTTP authentication configuration: enabled flag, credentials. unprotected is initially false and is used by the user interface to show a warning when auth is disabled. If the user wants to keep using Shelly without a password, they can set unprotected to hide the warning.

Encapsulates current device status information. While settings can generally be modified and don't react to the environment, this endpoint provides information about transient data which may change due to external conditions.

Shelly devices include basic MQTT support since version 1.3.0. While many device settings are only available over HTTP, MQTT allows for real-time monitoring and eases integration with external systems.

To configure a Shelly device for MQTT, set the connection parameters via the Shelly App, web interface or HTTP /settings endpoint. Note, that enabling MQTT will disable Allterco's cloud service. Shelly devices do not support secure MQTT connections.

By default, the device's MQTT ID is -, for example shelly1-B929CC. The MQTT ID can be changed via the mqtt_id parameter in /settings. If you wish to use custom a MQTT ID, it is recommended that it doesn't exceed 25 characters.

Device state is reported periodically, every 30 seconds by default. This can be changed by setting a new period for updates: mqtt_update_period under /settings. A value of 0 will disable periodic updates.

Default LWT topic and message are shellies/-/online, false. If these are not set after a firmware upgrade -- perform a factory reset of the device.The LWT topic is retained on user configuration (if the Retain flag is set). However, we do not recommend using retained MQTT messages.

The CoIoT protocol is yet another protocol for IoT communication and integration. CoIoT is based on CoAP with some additions as new request code 0.30 for status publishing. All payloads are JSON encoded. All responses are piggyback sent with the acknowledgement to further simplify CoAP implementation.

Every CoIoT device is expected to handle a set of request URIs and generate responses in predefined format. Also every device is required to periodically send a multicast CoAP request with code 0.30 that describes it state.

Some non-standard CoAP options are required to be transmitted to help quickly identify the remote device and determine if further processing is needed. The options are numbered with the help of these C/C++ preprocessor macros:

To follow the CoAP standard, options are numbered above 2048 where proprietary options should reside. LS Bits carry some CoAP proxy flags so we guard them with spacing the numbers with increment of 8.

COIOT_OPTION_STATUS_VALIDITY is a uint16_t in network byte order (big endian) that states the maximal time between this and the next status publish. This way a device can state its report interval. If a report is not received from this device after the interval has passed the device should be considered offline. The LS bit of this option controls how the value is scaled:

This option is mandatory in status response and publishes. It is a uint16_t in network byte order which indicates a change in the status report. When a new status report is handled, all payload processing can be skipped if the serial number does not change from the last processed payload. The value 0 is reserved and should not be sent. This allows easy initialization in the receiving devices.

blk array should hold list of all "blocks" of the device. Each device should have at least one block. For example if your device exposes just a few sensors it needs just one block, but if you have a multi channel relay you should define a block for each relay. Each sensor should be linked to one or many blocks to help users better understand what is measured in more complex devices.

Device descriptions will strive to provide all properties supported by the device, even if they are currentlydisabled/unavailable on the specific device. For example, a Shelly1 will always include a description of properties related to external (add-on) sensors, even if they are not currently attached (but of course, in this case they will be hidden from the status packet).

Every device should respond to CoAP GET request with URI /cit/s and return a JSON payload describing the device. Every device should periodically publish its status using multicast packet in the form of non-confirmable request with code 0.30 and request path /cit/s. This code is non-standard CoAP code and all CoAP compliant servers should silently ignore it. Throughout the status report all values should match sensors ids from the device description. The JSON payload should follow the form:

The 0 in the sensor tuples stands for the channel number. All sensors are required to be emitted in channel 0. Future extensions of the protocol might define a way for the users to define extra mapping for sensors to channels that will be added to the status after the values from channel 0. This will allow for easy reconfiguration of peer to peer network. For example, a multizone alarm system can be configured to react based on channel number activity and not to have to explicitly list every sensor on every siren. Currently the first position in the sensor tuple is reserved and should be 0.

If the web interface of the device cannot be accessed, settings can be brought back to default by switching ON and OFF 5 times the physical switch connected to the device, within the first minute after a reboot or power-on.

Shelly1/1PM also supports auto_on and auto_off settings -- these are timers in seconds which will turn the device ON or OFF when it has been turned OFF or ON respectively, from either a physical button or network command. Thus, the user can set a limit for how long the device can be ON or OFF.

3a8082e126