Conversation
Test Results 72 files 508 suites 0s ⏱️ For more details on these errors, see this check. Results for commit b3cc43b. ♻️ This comment has been updated with latest results. |
|
Minimum allowed coverage is Generated by 🐒 cobertura-action against b3cc43b |
5abb504 to
eb50abd
Compare
|
Invitation URL: |
a7fcbb4 to
09c0f55
Compare
| clusters.RadonConcentrationMeasurement.attributes.MeasuredValue, | ||
| clusters.RadonConcentrationMeasurement.attributes.MeasurementUnit, | ||
| }, | ||
| [capabilities.relativeHumidityMeasurement.ID] = { |
There was a problem hiding this comment.
This was a duplicate entry
| -- remove leading "-" | ||
| profile_name = string.sub(profile_name, 2) | ||
|
|
||
| device.log.info_with({hub_logs=true}, string.format("Updating device profile to %s.", profile_name)) |
There was a problem hiding this comment.
I removed this log because I realized this is now logged by the lua libs
d3ae5af to
01d94a4
Compare
|
Duplicate profile check: Warning - duplicate profiles detected. |
8e21d60 to
a2e702f
Compare
a2e702f to
0de69b8
Compare
0de69b8 to
8bff4f6
Compare
| ib.data.elements.min_measured_value == nil or ib.data.elements.min_measured_value.value == nil or | ||
| ib.data.elements.max_measured_value == nil or ib.data.elements.max_measured_value.value == nil or | ||
| ib.data.elements.min_measured_value.value >= ib.data.elements.max_measured_value.value then | ||
| device.log.warn_with({hub_logs = true}, "Device reported invalid soil moisture limits") |
There was a problem hiding this comment.
Can you expand on this warning to give slightly more info?
| sensor_utils.set_field_for_endpoint(device, fields.SOIL_LIMIT_MIN, ib.endpoint_id, ib.data.elements.min_measured_value.value) | ||
| sensor_utils.set_field_for_endpoint(device, fields.SOIL_LIMIT_MAX, ib.endpoint_id, ib.data.elements.max_measured_value.value) |
There was a problem hiding this comment.
Should we have sanity checks here you think?
| if device:supports_capability(capabilities.relativeHumidityMeasurement) then | ||
| profile_name = profile_name .. "-humidity" | ||
| -- Soil Sensor fingerprints to the humidity profile, so we should also check for | ||
| -- TemperatureMeasurement, which is an optional cluster for this device type. |
There was a problem hiding this comment.
might be worth adding a TODO comment about having a new category for soil sensor. Otherwise this kinda doesn't make sense why there'd be a separate profile
| update_device_profile() | ||
| test.wait_for_events() |
There was a problem hiding this comment.
I suggest we break this into a separate test. I don't think we need to test the do configure profile update in a relative humidity report test. I think this makes changing tests later more difficult. Same comment for other tests.
Basically I think we should have this profile update be its own test, separate from everything else.
c744895 to
b3cc43b
Compare
This adds support for the Soil Sensor device type, introduced with Matter 1.5.