Skip to main content

Drivers 5.5.1 · Device profiles 9.5.1

Published on 2026-10-22.

Drivers​

milesight-iot​

DriverChangeWhat changed
msight:am319-hcho-well:2updatedMilesight AM319-HCHO-WELL: standalone yes/no commands exposed as RW in the BACnet/Modbus mapping — Commands now writable through BACnet and Modbus, with their downlink vocabulary: clear_history, pm_self_clean, query_status, reboot, stop_buzzer, stop_transmit. Their R twin is unchanged; decoder and points unchanged.
msight:em410-rdl:2updatedMilesight em410-rdl: standalone yes/no commands exposed as RW in the BACnet/Modbus mapping — Commands now writable through BACnet and Modbus, with their downlink vocabulary: clear_history, radar_blind_calibration, radar_calibration, reboot, report_status, stop_transmit, sync_time. Their R twin is unchanged; decoder and points unchanged.
msight:em411-rdl:1updatedMilesight em411-rdl: standalone yes/no commands exposed as RW in the BACnet/Modbus mapping — Commands now writable through BACnet and Modbus, with their downlink vocabulary: clear_history, radar_blind_calibration, radar_calibration, reboot, report_status, stop_transmit, sync_time. Their R twin is unchanged; decoder and points unchanged.
msight:em500-swl:3updatedMilesight EM500 SWL: standalone yes/no commands exposed as RW in the BACnet/Modbus mapping — Commands now writable through BACnet and Modbus, with their downlink vocabulary: clear_history, reboot, report_status, stop_transmit, sync_time. Their R twin is unchanged; decoder and points unchanged.
msight:gs301:2updatedMilesight gs301: standalone yes/no commands exposed as RW in the BACnet/Modbus mapping — Commands now writable through BACnet and Modbus, with their downlink vocabulary: query_life_remain, reboot. Their R twin is unchanged; decoder and points unchanged.
msight:ts301:2updatedMilesight TS301: standalone yes/no commands exposed as RW in the BACnet/Modbus mapping — Commands now writable through BACnet and Modbus, with their downlink vocabulary: clear_history, reboot, report_status, stop_transmit, sync_time. Their R twin is unchanged; decoder and points unchanged.
msight:ts302:2updatedMilesight TS302: standalone yes/no commands exposed as RW in the BACnet/Modbus mapping — Commands now writable through BACnet and Modbus, with their downlink vocabulary: clear_history, reboot, report_status, stop_transmit, sync_time. Their R twin is unchanged; decoder and points unchanged.
msight:uc511:2updatedMilesight UC511: standalone yes/no commands exposed as RW in the BACnet/Modbus mapping — Commands now writable through BACnet and Modbus, with their downlink vocabulary: clear_history, clear_valve_1_pulse, clear_valve_2_pulse, reboot, report_status, stop_transmit, sync_time. Their R twin is unchanged; decoder and points unchanged.
msight:uc512:2updatedMilesight UC512: standalone yes/no commands exposed as RW in the BACnet/Modbus mapping — Commands now writable through BACnet and Modbus, with their downlink vocabulary: clear_history, clear_valve_1_pulse, clear_valve_2_pulse, reboot, report_status, stop_transmit, sync_time. Their R twin is unchanged; decoder and points unchanged.
msight:vs321:2updatedMilesight vs321: standalone yes/no commands exposed as RW in the BACnet/Modbus mapping — Commands now writable through BACnet and Modbus, with their downlink vocabulary: detect, reboot, reset, stop_transmit. Their R twin is unchanged; decoder and points unchanged.
msight:vs350:2updatedMilesight vs350: standalone yes/no commands exposed as RW in the BACnet/Modbus mapping — Commands now writable through BACnet and Modbus, with their downlink vocabulary: reboot, report_status, reset_cumulative_in, reset_cumulative_out, stop_transmit, sync_time. Their R twin is unchanged; decoder and points unchanged.
msight:vs373:2updatedMilesight vs373: standalone yes/no commands exposed as RW in the BACnet/Modbus mapping — Commands now writable through BACnet and Modbus, with their downlink vocabulary: reboot, release_alarm, report_status, stop_transmit. Their R twin is unchanged; decoder and points unchanged.
msight:ws101:3updatedMilesight WS101: standalone yes/no commands exposed as RW in the BACnet/Modbus mapping — Commands now writable through BACnet and Modbus, with their downlink vocabulary: query_device_status, reboot. Their R twin is unchanged; decoder and points unchanged.
msight:ws201:2updatedMilesight ws201: standalone yes/no commands exposed as RW in the BACnet/Modbus mapping — Commands now writable through BACnet and Modbus, with their downlink vocabulary: reboot, report_status. Their R twin is unchanged; decoder and points unchanged.
msight:ws301:3updatedMilesight WS301 driver: standalone yes/no commands exposed as RW in the BACnet/Modbus mapping — Commands now writable through BACnet and Modbus, with their downlink vocabulary: query_device_status, reboot. Their R twin is unchanged; decoder and points unchanged.
msight:ws501:2updatedMilesight WS501: standalone yes/no commands exposed as RW in the BACnet/Modbus mapping — Commands now writable through BACnet and Modbus, with their downlink vocabulary: reboot, report_attribute, report_status. Their R twin is unchanged; decoder and points unchanged.
msight:ws502:2updatedMilesight WS502: standalone yes/no commands exposed as RW in the BACnet/Modbus mapping — Commands now writable through BACnet and Modbus, with their downlink vocabulary: reboot, report_attribute, report_status. Their R twin is unchanged; decoder and points unchanged.
msight:ws503:2updatedMilesight WS503: standalone yes/no commands exposed as RW in the BACnet/Modbus mapping — Commands now writable through BACnet and Modbus, with their downlink vocabulary: reboot, report_attribute, report_status. Their R twin is unchanged; decoder and points unchanged.
msight:ws513:2updatedMilesight WS513: standalone yes/no commands exposed as RW in the BACnet/Modbus mapping — Commands now writable through BACnet and Modbus, with their downlink vocabulary: reboot, report_status, reset_power_consumption. Their R twin is unchanged; decoder and points unchanged.
msight:ws515:2updatedMilesight WS515: standalone yes/no commands exposed as RW in the BACnet/Modbus mapping — Commands now writable through BACnet and Modbus, with their downlink vocabulary: reboot, report_status, reset_power_consumption. Their R twin is unchanged; decoder and points unchanged.
msight:wt101:2updatedMilesight WT101: standalone yes/no commands exposed as RW in the BACnet/Modbus mapping — Commands now writable through BACnet and Modbus, with their downlink vocabulary: reboot, report_heating_date, report_heating_schedule, report_status, restore_open_window_detection, valve_calibration. Their R twin is unchanged; decoder and points unchanged.
msight:wt201:3updatedMilesight WT201-V2: standalone yes/no commands exposed as RW in the BACnet/Modbus mapping — Commands now writable through BACnet and Modbus, with their downlink vocabulary: reboot. Their R twin is unchanged; decoder and points unchanged.

Device profiles​

atim​

ModelChangeWhat changed
atim:acw-pw:1updatedATIM ACW-PW pilot wire: LoRaWAN class C profile — The ACW-PW is a class C device: the model now uses the class C profile (atim_RFGroup1_1.0.4a_classC). The class A profile is deprecated and stays in this release for the devices already provisioned with it, then leaves the catalog.

yokogawa​

ModelChangeWhat changed
yokogawa:sushi-pressure:1updatedYokogawa Sushi Pressure sensor: CN470 and LoRaWAN 1.0.4 profiles added — Adds two class A LoRaWAN profiles: CN470 (LoRaWAN 1.0.2, fixed 5 dBm conducted power, the maximum the manufacturer gives for China) and EU868 at LoRaWAN 1.0.4 (yokogawa_RFGroup1_1.0.4-RP2-1.0.3_classA), the version Yokogawa now gives for Europe. The existing 1.0.2b profiles stay unchanged for the devices that still need them; the LoRaWAN version tells the two EU868 profiles apart (their names now end with LoRaWAN v1.0.2 and LoRaWAN v1.0.4). Links the manufacturer's specification and user guide and renames the model picture. The sensors list now names the pressure the driver emits instead of the vibration points.
yokogawa:sushi-temp:1updatedYokogawa Sushi Temperature sensor: CN470 and LoRaWAN 1.0.4 profiles added — Adds two class A LoRaWAN profiles: CN470 (LoRaWAN 1.0.2, fixed 5 dBm conducted power, the maximum the manufacturer gives for China) and EU868 at LoRaWAN 1.0.4 (yokogawa_RFGroup1_1.0.4-RP2-1.0.3_classA), the version Yokogawa now gives for Europe. The existing 1.0.2b profiles stay unchanged for the devices that still need them; the LoRaWAN version tells the two EU868 profiles apart (their names now end with LoRaWAN v1.0.2 and LoRaWAN v1.0.4). Links the manufacturer's specification and user guide and renames the model picture. The sensors list now names the temperature the driver emits instead of the vibration points.
yokogawa:sushi-vib:1updatedYokogawa Sushi Vibration sensor: CN470 and LoRaWAN 1.0.4 profiles added — Adds two class A LoRaWAN profiles: CN470 (LoRaWAN 1.0.2, fixed 5 dBm conducted power, the maximum the manufacturer gives for China) and EU868 at LoRaWAN 1.0.4 (yokogawa_RFGroup1_1.0.4-RP2-1.0.3_classA), the version Yokogawa now gives for Europe. The existing 1.0.2b profiles stay unchanged for the devices that still need them; the LoRaWAN version tells the two EU868 profiles apart (their names now end with LoRaWAN v1.0.2 and LoRaWAN v1.0.4). Links the manufacturer's specification and user guide and renames the model picture.
Last updated on