Smartthings Integration Refrigerator temperature and set point unknown

[gwheels]

The problem

New Refrigerator with refrigerator and freezer temperature and setpoints showing in Smartthings, but show as "unknown" in smartthings integration.

What version of Home Assistant Core has the issue?

core-2021.11.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Smartthings

Link to integration documentation on our website

https://www.home-assistant.io/integrations/smartthings

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[probot-home-assistant[bot]]

smartthings documentation smartthings source _{^{(message by IssueLinks)}}

[probot-home-assistant[bot]]

Hey there @andrewsayre, mind taking a look at this issue as it has been labeled with an integration (smartthings) you are listed as a code owner for? Thanks! _{^{(message by CodeOwnersMention)}}

[firstof9]

This happens because the smartthings API responds with:

        "main": {
...
            "temperatureMeasurement": {
                "temperature": {
                    "value": null
                }
            },
...

The measurement and setPoint have moved under the "cooler" key instead:

        "cooler": {
            "contactSensor": {
                "contact": {
                    "value": "closed",
                    "timestamp": "2021-12-08T18:13:24.859Z"
                }
            },
            "custom.disabledCapabilities": {
                "disabledCapabilities": {
                    "value": [],
                    "timestamp": "2021-07-27T01:19:43.145Z"
                }
            },
            "temperatureMeasurement": {
                "temperature": {
                    "value": 37,
                    "unit": "F",
                    "timestamp": "2021-12-02T16:11:13.294Z"
                }
            },
            "custom.thermostatSetpointControl": {
                "minimumSetpoint": {
                    "value": 34,
                    "unit": "F",
                    "timestamp": "2021-07-27T01:19:42.452Z"
                },
                "maximumSetpoint": {
                    "value": 44,
                    "unit": "F",
                    "timestamp": "2021-07-27T01:19:42.452Z"
                }
            },
            "thermostatCoolingSetpoint": {
                "coolingSetpoint": {
                    "value": 37,
                    "unit": "F",
                    "timestamp": "2021-07-27T01:19:42.452Z"
                }
            }
        },

Similar with the freezer info:

        "freezer": {
            "contactSensor": {
                "contact": {
                    "value": "closed",
                    "timestamp": "2021-12-08T07:17:33.154Z"
                }
            },
            "custom.disabledCapabilities": {
                "disabledCapabilities": {
                    "value": [],
                    "timestamp": "2021-07-27T01:19:43.145Z"
                }
            },
            "temperatureMeasurement": {
                "temperature": {
                    "value": 0,
                    "unit": "F",
                    "timestamp": "2021-11-13T23:31:15.088Z"
                }
            },
            "custom.thermostatSetpointControl": {
                "minimumSetpoint": {
                    "value": -8,
                    "unit": "F",
                    "timestamp": "2021-07-27T01:19:42.452Z"
                },
                "maximumSetpoint": {
                    "value": 5,
                    "unit": "F",
                    "timestamp": "2021-07-27T01:19:42.452Z"
                }
            },
            "thermostatCoolingSetpoint": {
                "coolingSetpoint": {
                    "value": 0,
                    "unit": "F",
                    "timestamp": "2021-07-27T01:19:42.452Z"
                }
            }
        },

So in order for this to work again I think the library would need updating to allow enumeration of all the keys under "components".

[gwheels]

Thanks. Which library needs the update, and who manages it?

[firstof9]

Library is pysmartthings, keep in mind I'm not 100% sure that's where the issue is located.

[coffeexclutter]

I'm in the same boat. I would love to see an update on this one.

[kernelpanic85]

I had the same issue and found that going into the Smartthings IDE and setting the type to Samsung OCF Refrigerator on the parent device and then Samsung OCF Refrigerator Compartment on the child devices seemed to fix it. I still have an issue with HA not reporting all the sensor values that are present from the Smartthings API, but I suppose that is a separate issue.

[gwheels]

That did the trick! once I determined that the Smartthings IDE is on the Samsung smartthings website. I can now see the refrigerator temperature and setpoint.

How did you configure the freezer child device? I have set the "Refrigerator Freezer" and "freezer" child devices as Samsung OCF Refrigerator Compartment type and tried both the same and unique device network ID's but the temperature and setpoint are not passing to HA like the refrigerator compartment.

[kernelpanic85]

Yes, that seems like a separate issue. I found a bunch of closed issues on Github regarding this and they seem to say that the integration currently doesn't enumerate all the info from the child devices so we are missing all of those sensors. Maybe we can re-surface this and hopefully someone can take a look?

[gwheels]

Hopefully so. Still, some progress is good.

[kernelpanic85]

@andrewsayre any hope of getting the full child components into the integration for the refrigerators?

[markdepalma]

I had the same issue and found that going into the Smartthings IDE and setting the type to Samsung OCF Refrigerator on the parent device and then Samsung OCF Refrigerator Compartment on the child devices seemed to fix it. I still have an issue with HA not reporting all the sensor values that are present from the Smartthings API, but I suppose that is a separate issue.

This worked for me too!

[firstof9]

any hope of getting the full child components into the integration for the refrigerators?

You may run into API limitations if you attempt to subscribe to too many entries. Currently the SmartThings API limits you to 40 subscriptions per app. Not sure why 40, seems like weird limit myself.

[markdepalma]

any hope of getting the full child components into the integration for the refrigerators?

You may run into API limitations if you attempt to subscribe to too many entries. Currently the SmartThings API limits you to 40 subscriptions per app. Not sure why 40, seems like weird limit myself.

Wondering the same here. I have the base fridge/energy stats working but freezer is a child object and not present. I could create my own integration if I have to...

[firstof9]

I could create my own integration if I have to...

It's been done, I'm sure the author wouldn't mind some additional collaboration.

https://github.com/veista/smartthings

[markdepalma]

I could create my own integration if I have to...

It's been done, I'm sure the author wouldn't mind some additional collaboration.

https://github.com/veista/smartthings

Ah, I didn't know about this. Will check it out later. Thanks!

[markdepalma]

Just added on support for my fridge using the work already done by you. Created a pull request: https://github.com/veista/smartthings/pull/23.

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[gwheels]

Stale? Seems so harsh. Still haven't been able to work through this.

How does this look for freezer settings IDE? Obviously temp and setpoint there, but not passing to the HA integration.

[janivr]

Any fix to not show freezer data, but only cooler? Any workaround I can use?

[janivr]

Just added on support for my fridge using the work already done by you. Created a pull request: veista/smartthings#23.

Installed this but got only 4 entities, cooler temp is in but not freezer temp.

[coffeexclutter]

Nice! Thank you!

The only problem I'm having when I do that is with the device ID. Did your device already have a Device Network ID? Mine is blank when I try to change the device type, but requires it to change the device type.

On Wed, Mar 23, 2022, 9:17 PM kernelpanic85 @.***> wrote:

I had the same issue and found that going into the Smartthings IDE and setting the type to Samsung OCF Refrigerator on the parent device and then Samsung OCF Refrigerator Compartment on the child devices seemed to fix it. I still have an issue with HA not reporting all the sensor values that are present from the Smartthings API, but I suppose that is a separate issue.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/61075#issuecomment-1077051233, or unsubscribe https://github.com/notifications/unsubscribe-auth/AORTJZOK2RQH5YCQ36ZLND3VBPUE7ANCNFSM5JNSTELA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[kernelpanic85]

I think I added a Device Network ID to mine. It let me change it no problem. My device type is Samsung OCF Refrigerator.

[gwheels]

I think I added a Device Network ID to mine. It let me change it no problem. My device type is Samsung OCF Refrigerator.

When you add the Device Network ID, does it push the freezer child device to the Smartthings Integration? I've tried both a unique or the same Network ID number as the parent refrigerator ID. Neither causes a new entity in the integration. The freezer temp is present in the native smartthings app (as is my deli drawer), so I know it's there on the Smartthings side.

[bearhntr]

I am trying to follow this - and not sure things are working. I did Uninstall the SmartThings - followed the steps for putting the HACS version - and I am getting a little more -- but still not sure what is wrong. I would really like to get this working - as I hate having to use the ALEXA Link to SmartThings. I also have a RANGE to get installed, a DISHWASHER and a RANGE-HOOD MICROWAVE (soon as my new floors get installed. Wondering if they are all going to give me fits too. Seems there is no way to update Firmware or Software on these things like the Family Hub Fridge does on its own.

[bearhntr]

The WASHER-- definately shows more information - but you have to turn it ON to get more. Been my complaint to SAMSUNG for 1.5 years -- they are Supposed to be SMART, why do I have to walk to it to turn it ON?

and the DRYER

[bearhntr]

What I see in the ENTITIES

[bearhntr]

Now I am seeing these in the logs:

This error originated from a custom integration.

Logger: custom_components.smartthings.smartapp Source: custom_components/smartthings/smartapp.py:330 Integration: SmartThings First occurred: 15:03:38 (12 occurrences) Last logged: 15:03:38

Failed to create subscription for 'refrigeration' under app 'd94a6276-373b-44ee-a774-4591f6bd3fd0': Unprocessable Entity (422): {"requestId": "B306B799-CCB1-4E08-BE5C-66300A48013D", "error": {"code": "LimitError", "message": "subscription limit exceeded", "details": []}} Failed to create subscription for 'custom.error' under app 'd94a6276-373b-44ee-a774-4591f6bd3fd0': Unprocessable Entity (422): {"requestId": "9E0B6D9A-63C4-45BD-A896-0049CFF2A26B", "error": {"code": "LimitError", "message": "subscription limit exceeded", "details": []}} Failed to create subscription for 'custom.soundmode' under app 'd94a6276-373b-44ee-a774-4591f6bd3fd0': Unprocessable Entity (422): {"requestId": "C2BC46EE-5D0F-4A31-BF86-99D0AC50697D", "error": {"code": "LimitError", "message": "subscription limit exceeded", "details": []}} Failed to create subscription for 'samsungce.detergentState' under app 'd94a6276-373b-44ee-a774-4591f6bd3fd0': Unprocessable Entity (422): {"requestId": "65E0441F-8CC7-4D5C-81A2-E31DAE1BAAC0", "error": {"code": "LimitError", "message": "subscription limit exceeded", "details": []}} Failed to create subscription for 'custom.launchapp' under app 'd94a6276-373b-44ee-a774-4591f6bd3fd0': Unprocessable Entity (422): {"requestId": "E9705533-E0AF-446C-8DFB-675ABAAF5BEF", "error": {"code": "LimitError", "message": "subscription limit exceeded", "details": []}}

======================= This error originated from a custom integration.

Logger: custom_components.smartthings.smartapp Source: custom_components/smartthings/smartapp.py:376 Integration: SmartThings First occurred: 15:03:37 (1 occurrences) Last logged: 15:03:37

Some device attributes may not receive push updates and there may be subscription creation failures under app 'd94a6276-373b-44ee-a774-4591f6bd3fd0' because 62 subscriptions are required but there is a limit of 40 per app

=============================

[firstof9]

and the DRYER

Work around for the dryer is to turn on "Cycle Sync" or whatever it's called. This will make the dryer stay on and connected.

Some device attributes may not receive push updates and there may be subscription creation failures under app 'd94a6276-373b-44ee-a774-4591f6bd3fd0' because 62 subscriptions are required but there is a limit of 40 per app

I'm in the same boat here with you, but 69 subscriptions of 40

veista stated they're working on a new library so this will likely help with these issues.

[bearhntr]

@firstof9

Thank You -- I think that setting exists on both WASHER and DRYER - but when it is turned ON on the Washer -- you cannot open the door.

I really wish that SAMSUNG would fix these things....they are supposed to be the leader in "SmartAppliances" -- well theirs ar DUMB! LOL