pH not registering initial value

Developer Programs Support
1

This is a direct connect client using the st-device-sdk-c API. I have a pH, a temp, and a voltage items under “main”. temp and voltage is showing, but pH isn’t. No errors seen.

I (1647017404:496) [IoT]: st_cap_send_attr(612) > publish event, topic : /v1/deviceEvents/42cf937a-cff8-4095-af78-3d3b8b78d92a, payload :
{“deviceEvents”:[{“component”:“main”,“capability”:“pHMeasurement”,“attribute”:“pH”,“value”:7,“providerData”:{“sequenceNumber”:1,“timestamp”:“1647017404496”}}]}
Sequence number return : 1
I (1647017404:496) [IoT]: iot_cap_call_init_cb(1104) > Call init_cb for voltageMeasurement capability
I (1647017404:500) [IoT]: st_cap_send_attr(612) > publish event, topic : /v1/deviceEvents/42cf937a-cff8-4095-af78-3d3b8b78d92a, payload :
{“deviceEvents”:[{“component”:“main”,“capability”:“voltageMeasurement”,“attribute”:“voltage”,“value”:3.2000000476837158,“providerData”:{“sequenceNumber”:2,“timestamp”:“1647017404500”}}]}
Sequence number return : 2
I (1647017404:504) [IoT]: iot_cap_call_init_cb(1104) > Call init_cb for temperatureMeasurement capability
I (1647017404:504) [IoT]: st_cap_send_attr(612) > publish event, topic : /v1/deviceEvents/42cf937a-cff8-4095-af78-3d3b8b78d92a, payload :
{“deviceEvents”:[{“component”:“main”,“capability”:“temperatureMeasurement”,“attribute”:“temperature”,“value”:20.299999237060547,“unit”:“F”,“providerData”:{“sequenceNumber”:3,“timestamp”:“1647017404504”}}]}
Sequence number return : 3
I (1647017404:519) [IoT]: _do_cmd_tout_check(1041) > New state updated for 8
I (1647017404:520) [IoT]: _do_cmd_tout_check(1048) > previous error code

Screenshot_20220311-121302_SmartThings
Screenshot_20220311-121302_SmartThings1080×2280 129 KB

2

There’s a problem with the presentation for that capability that I’m betting stems from the capitalization of pH. I’ve previously reported the issue (topic below) - @nayelyz might be able to provide an update on any progress fixing it. I ended up creating a custom capability for pH for my pool chlorinator.

3

Thank you for bringing this up, @dcabot25.
I was able to reproduce the issue using another integration type so, the issue is in the capability itself.

@philh30, I found the report made by Erick a while back and it was corrected at some point but it is happening again. So, I will open a new one for the team to analyze the issue further.

Note: For now, the suggestion is to do as @philh30, create a custom capability so you can continue your development.

4

create a custom capability so you can continue your development.
yup, will do. Thanks!

1 Like