Core: SmartThings Washer sensors not updating

[pplucky]

Home Assistant release with the issue:
0.88.1

Last working Home Assistant release (if known):
None, this is new integration in 0.88.0

Operating environment (Hass.io/Docker/Windows/etc.):
Hassbian (virtual environment)

Component/platform:
SmartThings integration

Description of problem:
Washer Machine related-sensors seem not to be updating

Entity | State | Attributes
-- | -- | --
sensor.washing_machine_washer_completion_time | unknown | device_class: timestamp friendly_name: Washing machine Washer Completion Time
sensor.washing_machine_washer_job_state | none | friendly_name: Washing machine Washer Job State
sensor.washing_machine_washer_machine_state | stop | friendly_name: Washing machine Washer Machine State
sensor.washing_machine_washer_mode | unknown | friendly_name: Washing machine Washer Mode
switch.washing_machine | on | friendly_name: Washing machine icon: mdi:washing-machine

Machine is currently on and schedule to start in a couple of hours:
https://imgur.com/a/WRfziYN

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

None, just displaying automatically generated sensors in UI

Traceback (if applicable):

Additional information:

[andrewsayre]

I assume by not working, you mean they aren't updating?

Reauthorize the app to re-create the subscriptions:

1. Go into the SmartThings Class App
2. Tap Automations -> Home Assistant (or however you named it)
3. Tap Done -> Allow

[pplucky]

Did it twice already and sensors are the same, not updating.

Any other thoughts?

[andrewsayre]

1. Do you have other devices that update as expected in the integration?
2. Is the updated state showing in the SmartThings Classic App? (or do you have to manually refresh it?)

[pplucky]

1. Nope, it’s the only one
2. Yes, it does.
   If you check the printscreens I uploaded to imgur (link in original post), first 2 are from SmartThings Classic App and only the last is from the new SmartThings app.

Machine is currently in delay wash state and it shows as such in both SmartThings’ apps, but not in Home Assistant.

[andrewsayre]

Sorry to clarify the second question... does it update automatically, while the app is open and you’re looking at it? It will poll the device when you open the app or navigate in/out of the device, which is similar to the refresh button, but I’m curious if it updates while you’re looking at it with you doing nothing.

1. Can you share the make/model of the device
2. What is the Device Type Handler that shows up in the SmartThings IDE? https://graph.api.smartthings.com/login/auth

[pplucky]

Sorry to clarify the second question... does it update automatically, while the app is open and you’re looking at it? It will poll the device when you open the app or navigate in/out of the device, which is similar to the refresh button, but I’m curious if it updates while you’re looking at it with you doing nothing.

It doesn't update if the app is open and looking at it! I just checked while I was triggering a delay wash. When I left the app and came back it was updated (as the refresh button would do).

1. Can you share the make/model of the device

Samsung QuickDrive WW80M645OPW/EP

1. What is the Device Type Handler that shows up in the SmartThings IDE? https://graph.api.smartthings.com/login/auth

Device Network ID (I suppose it is what you're asking) is: b3937a5a-8e5a-4b81-bed6-b8deab014875

[andrewsayre]

Thanks for the clarification! There appears to be an issue with direct-cloud connected devices (no hub) where the events aren’t propagating out the through to their webhook API. I’m working with another user that has an affected TV. I’m in touch with engineers from SmartThings who are eager to get this fixed. I’ll let you know if there’s more info needed.

[pplucky]

In the meanwhile I had to restart my HA instance and both State and Job State were updated to the value at the time.

Still then, value has changed already and no further updates were provided to HA.

Please let me know if there's anything else you need from me.

[andrewsayre]

Yes it updates because it pulls the latest status. Need some additional information:

1. The Device UUID.
2. The Location UUID the device is added to.

You get these from the SmartThings IDE by drilling into the Device/Location and pulling the ID out of the URL.

Thank you!

[pplucky]

Here it is:

1. The Device UUID.

24823517-1537-27a8-4a88-f4390205a302

1. The Location UUID the device is added to.

09e64b83-cfd2-4267-b79f-4b6d789dca1e

Thanks in advance.

[andrewsayre]

Thank you. I'll let you know as soon as I have updates.

[christianzappa]

Same issue here with any of my sensors. I have a couple of temperature sensors, presence sensor (life 360) and open/close sensors. All of them only update on reboot. Walked through the same steps as above, removed integration, reinstalled the smart app etc etc still not updating, fine in my Smartthings app and even in Stringify which I use for automation.

[andrewsayre]

@christianzappa Unless you have the same device as OP (Samsung QuickDrive), please open a sperate issue please.

[dbradmit]

This issue does not seem to be the same as #21260. For that user, state data is only reported after tapping refresh. For this user, the data is reported without the need to tap "refresh".

Here's an example of the data payload from a washer:

https://d2ddoduugvun08.cloudfront.net/items/3T3T0n3q1V32020s1926/Screen%20Shot%202019-03-08%20at%204.35.07%20PM.png

[kropling]

Hi,

I might have the same problem. As @pplucky my washer updates status to "on" in Home Assistant shortly after starting a program. But the other parameters are as follows:

sensor.washer_samsung_washer_completion_time | unknown
sensor.washer_samsung_washer_job_state | none
sensor.washer_samsung_washer_machine_state | stop
sensor.washer_samsung_washer_mode | unknown
switch.washer_samsung | on

I have a Samsung WW90M643OBW.

Please let me know if I can help in any way with providing more information about my machine.

[ronschaeffer]

Same issue here. The sensors only update when I restart HA.

EDIT: In contrast to behavior reported by @pplucky and @kropling, switch.washing_machine never updates to on--even when the sensors update after a restart of HA--unless I manually move the switch in the frontend. Of course, manually moving the switch does nothing else.

Washer model: WW90K6414QX
Device Network ID: a2626016-8c81-4ca7-9c66-f6fbe11d24a2
Location ID: 8e947472-b44e-41da-a986-1fd7d162da3a

Just let me know if I can help with more info or testing.

[andrewsayre]

@pplucky Can you upgrade to the latest version of Home Assistant (v0.89.2) and confirm if you're still having this issue?

[pplucky]

@andrewsayre I had upgraded it already, but sensors are only updated on HASS reboot, so still the same.

[clboles]

I'm running 0.90.1 in docker on Ubuntu 18.04. I'm seeing similar behavior for both my Samsung washer (WA54M8750) and dryer (DVE54M8750). The switch, completion time, and mode appear to never be set for the washer or dryer. The job state and machine state are receiving push updates.

Here are sample push updates for a dryer run:

2019-03-26 22:27:32 DEBUG (MainThread) [homeassistant.components.smartthings] Push update received: {'location_id': '********-****-****-****-************', 'device_id': '********-****-****-****-************', 'component_id': 'main', 'capability': 'dryerOperatingState', 'attribute': 'dryerJobState', 'value': 'drying', 'data': None}
2019-03-26 22:27:32 DEBUG (MainThread) [homeassistant.components.smartthings] Push update received: {'location_id': '********-****-****-****-************', 'device_id': '********-****-****-****-************', 'component_id': 'main', 'capability': 'dryerOperatingState', 'attribute': 'machineState', 'value': 'run', 'data': None}
2019-03-26 22:28:31 DEBUG (MainThread) [homeassistant.components.smartthings] Push update received: {'location_id': '********-****-****-****-************', 'device_id': '********-****-****-****-************', 'component_id': 'main', 'capability': 'dryerOperatingState', 'attribute': 'dryerJobState', 'value': 'cooling', 'data': None}
2019-03-26 22:29:42 DEBUG (MainThread) [homeassistant.components.smartthings] Push update received: {'location_id': '********-****-****-****-************', 'device_id': '********-****-****-****-************', 'component_id': 'main', 'capability': 'dryerOperatingState', 'attribute': 'dryerJobState', 'value': 'none', 'data': None}
2019-03-26 22:29:42 DEBUG (MainThread) [homeassistant.components.smartthings] Push update received: {'location_id': '********-****-****-****-************', 'device_id': '********-****-****-****-************', 'component_id': 'main', 'capability': 'dryerOperatingState', 'attribute': 'machineState', 'value': 'stop', 'data': None}

[dbradmit]

@clboles I believe you are experiencing an issue similar to #22245

If you sign into the IDE, do the device Ids in the url start with a C and end in a bunch of zeroes?

https://cl.ly/33bb7eb15219

If so, that is indicative that your appliances are using the legacy appliance integration. I'm currently working to track down additional information on the data and data format expected from these devices.

[clboles]

@dbradmit Yes their IDs do start with C and end in zeros. Both the washer and dryer are M series 2017 models with SmartHome branding. I added them via the new SmartThings app.

Is there anything I can do on my end to have the washer and dryer use a more complete handler, or is the SHP->OCF bridge something that has to be built on the SmartThings service side?

[dbradmit]

This a server-side issue and unfortunately there isn't anything you can do on your end.

[pplucky]

@dbradmit @andrewsayre I recently noticed that the integration sensors started being updated by itself as the machine is being used (while these were not before).

HA version: 0.91.4

Was anything changed on server-side recently?

Even if it was a server-side as discussed, the odd thing to me is that these were updated on HA reboot but not updated anymore.

Thanks for letting me know.

[pplucky]

@kropling @ronschaeffer @clboles Would any of you be able to confirm if this is also working for you now?

[ronschaeffer]

Sorry, but I've migrated my devices off SmartThings by now. Good luck with
the testing.

On Tue, Apr 30, 2019 at 8:38 AM pplucky [e-mail] wrote:

@kropling https://github.com/kropling @ronschaeffer
https://github.com/ronschaeffer @clboles https://github.com/clboles
Would any of you be able to confirm if this is also working for you now?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/21430#issuecomment-487848357,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC6OOEZN2YX3BAV5DU5JNGDPS7ZN5ANCNFSM4GZ64PJQ
.

[kropling]

@pplucky Yes, can confirm that the washer sensors works like a charm now. I have a notification being pushed upon wahser end and works every single time.

Thanks for the effort on this one :)

[pplucky]

@dbradmit @andrewsayre It seems the integration sensors are now being updated by itself as the machine is being used (while these were not before).

Was this fixed on server-side?

Btw, it seems to me that completion time is being updated too often (seems to be filled, even when machine state is no longer run or scheduled to run). Can you also check that?

Thanks in advance once again.

[andrewsayre]

I believe Samsung updated their OCR device-type handlers. I'll close this issue for now since you reported it's working! Yay!

[ronschaeffer]

@kropling @ronschaeffer @clboles Would any of you be able to confirm if this is also working for you now?

@andrewsayre Apologies for replying to a closed issue, but just FYI... I decided to try SmartThings again and can also confirm that the washing machine sensors now work perfectly. Thanks.

[kropling]

Hi, anyone else have their washer sensor to stop working again? Happened a week or two ago. It still reports on the SmartThings app. Also want to mention that my Samsung TV reports to both Home Assistant and SmartThings app as expected.

[pplucky]

Yeah, same here. Last update of completion time was on 05.07.2019.

[andrewsayre]

Please open a new issue. You’re commenting on a closed topic.