Closed aromanro closed 6 years ago
<DeviceType key="0x0d1a" label="Seismic Magnitude Sensor" command_classes="0x5a,0x5e,0x59,0x72,0x73,0x85,0x86,0x30,0x31"/> <DeviceType key="0x0d1b" label="Ultraviolet Sensor" command_classes="0x5a,0x5e,0x59,0x72,0x73,0x85,0x86,0x30,0x31"/> <DeviceType key="0x0d1c" label="Electrical Resistivity Sensor" command_classes="0x5a,0x5e,0x59,0x72,0x73,0x85,0x86,0x30,0x31"/> <DeviceType key="0x0b1d" label="Electrical Conductivity Sensor" command_classes="0x5a,0x5e,0x59,0x72,0x73,0x85,0x86,0x30,0x31"/> <DeviceType key="0x0b1e" label="Loudness Sensor" command_classes="0x5a,0x5e,0x59,0x72,0x73,0x85,0x86,0x30,0x31"/> <DeviceType key="0x0b1f" label="Moisture Sensor" command_classes="0x5a,0x5e,0x59,0x72,0x73,0x85,0x86,0x30,0x31"/>
From line 219... it appears that they are in order, counted up, until it changes from 0x0d.. to 0x0b.. It seems to be an error, they all support the common classes up to version class, then 0x30 and 0x31, they might be actually all with 0x0d...
Good Catch... Thanks
From line 219... it appears that they are in order, counted up, until it changes from 0x0d.. to 0x0b.. It seems to be an error, they all support the common classes up to version class, then 0x30 and 0x31, they might be actually all with 0x0d...