But then I got 2 messages
Hopefully cracked the OAuth2 login refresh, so the 24 hour limit should be gone.
Hello Adrian, Would you have any idea why Ring Alarm Contact Sensors are not being found by the ST Community app? They are Z-Wave devices that are using a SmartThings Custom Edge Driver that was created by Developer Milan Jurovic. Here are the device’s metrics and raw description:
The app interfaces to a SmartThings account, so if you have added them to SmartThings then I guess they should be available to the app.
To be honest, with the pending change to SmartThings API policy, I might have to pull the app in a few months, so if it doesn’t support them now, I won’t be spending any time developing the app further until I know the repercussions of the change.
I completely understand your hesitation regarding SmartThings’ pending API policy changes, but I really appreciate all the work you’ve put into this app. It does a fantastic job interfacing with SmartThings!
Nearly all of my devices are discovered flawlessly, including Z-Wave, Matter, and Zigbee devices. When I updated to the OAuth connection yesterday, additional Z-Wave switches and Z-Wave contact sensors were picked up, but the Ring Alarm Z-Wave contact sensors specifically were not.
(In the images below, those framed in red are GE Z-Wave switches, the blue frame is a Ring Alarm Z-Wave Motion Sensor. My Ring 2nd Gen Keypad was discovered as well.)
Since the Ring Motion Sensor and Keypad transferred fine, I’m wondering if SmartThings exposes the Ring Contact Sensors under a different capability profile or security category in their API endpoint?
One detail worth noting is that these Ring Contact Sensors were paired to SmartThings using Z-Wave S2 security. Since the Ring Motion Sensor and Keypad transferred fine, I’m wondering if SmartThings exposes S2-paired Ring Contact Sensors under a different device profile or custom capability schema in their cloud API?
If there’s an app log or device JSON payload I can grab from the app settings to help you see how SmartThings presents those contact sensors, please let me know. Thanks again for your support!
Update on the Ring Sensors: "I wanted to share one more detail that narrows this down: both my Ring Motion Sensor and Ring Contact Sensors are using Milan Jurovic’s custom Edge Driver (‘Z-Wave Ring Sensor’ from Milan’s channel).
The Ring Motion Sensor transfers into Homey perfectly, but the Ring Contact Sensor does not. Since both use the same driver channel, it looks like SmartThings is presenting the Contact Sensor’s profile or primary capability category slightly differently under this driver’s fingerprint than the Motion Sensor."
UPDATE: Not sure what you did Adrian, but the Ring Alarm Content Sensors are now displaying inside Homey Pro. Thank you for your kind assistance. ~ Bud 
Samsung EHS Cascade Controller MCM-D3E0N – improved EHS / cascade support
Hi @Adrian_Rockall,
First of all, thank you for all the work you have put into the SmartThings Community app. It is very useful, and thanks to your app I have now managed to get my Samsung EHS system into Homey.
I have a Samsung EHS Cascade Controller MCM-D3E0N controlling three Samsung heat pumps. The cascade controller itself supports up to eight heat pumps.
The system is connected to SmartThings, and I can add it to Homey using the SmartThings Device driver in your app.
My installation consists of:
- DHW
- Zone 1
- Zone 2
- Three active heat pumps in the cascade
SmartThings currently exposes the following components:
mainINDOOR1INDOOR2heatpump-1throughheatpump-8
I have verified the mapping as:
main= DHWINDOOR1= Zone 1INDOOR2= Zone 2
In Homey this results in three devices:
-
Heatpump: main -
Heatpump: INDOOR1 -
Heatpump: INDOOR2
The zone temperatures and setpoints seem to work quite well.
There is however one clear issue with main / DHW.
SmartThings reports the DHW temperature correctly and also reports the correct target temperature. The DHW target is currently 65 °C, and SmartThings reports the allowed setpoint range for main as 40–65 °C.
Homey displays the current DHW temperature correctly, but the target temperature is shown as 35 °C.
I have attached a screenshot showing this. In the screenshot the actual DHW temperature is approximately 68 °C, while Homey shows the target as 35 °C.
It looks as if the generic SmartThings Device driver is using a normal Homey thermostat temperature range instead of the EHS DHW range.
The other interesting part is the cascade itself.
SmartThings exposes heatpump-1 through heatpump-8 using:
samsungce.ehsCascadeOverview
In my installation, heat pumps 1–3 are active, while heat pumps 4–8 contain null values, as only three outdoor units are installed.
For the active heat pumps SmartThings exposes information such as:
- Heat pump ID
- Operation time
- Energy usage
- Operating mode/status (
heating,dhw,stopped, etc.) - Error code
- Backup heater status
- Backup boiler status
- Demand response status
- PV status
- Outdoor temperature
- Water inlet temperature
- Water outlet temperature
It would be great if the Samsung EHS driver could recognise this cascade structure and expose more of the EHS-specific information in Homey.
Ideally:
mainrecognised as DHW with the correct setpoint rangeINDOOR1andINDOOR2recognised as the two heating zones- Active
heatpump-xcomponents detected automatically - Individual heat pump status, operation time and energy data available in Homey
- Unused heat pump slots ignored when their ID/data is null
I have also exported the SmartThings Advanced Attributes and Commands data and uploaded sanitised versions here:
The private IDs, serial number and location information have been removed.
I also have the complete SmartThings Raw JSON available if that would be useful, and I have access to the physical cascade controller if you would like me to test anything or change parameters.
Thanks again for your work on the app, and for considering support for the Samsung EHS cascade controller.
I’ve got a Meross MTS960 Smart Wi-Fi thermostat that I’ve added but the power consumption from the device is not exposed through Smartthings. Any possibility to add this?
ATM I am waiting to see the outcome of Samsung’s latest news that they want to start charging for API access. If they are going to make the developer pay then I will have to pull the app, but if they charge the user then I can possibly continue although I won’t be paying, so it will be difficult to test anything. After they pulled the lifetime access code and time limited them to 24 hours, I replaced the few devices I had on that platform, so all I have now is my washing machine and it’s no big deal if that stops working with Homey.
So, I currently have a few logs queued up for extra support and you are welcome to send your log if you want to.
Thanks Adrian. I’ve now sent the Detected log.
I really appreciate the work you’ve already put into the app, and I completely understand the uncertainty around Samsung’s upcoming API pricing changes.
If you decide to look into the EHS Cascade support, I’d be happy to contribute €100 towards the work.
Just let me know the best way to contribute.
Hello Adrian. I will soon be installing a new machine from Samsung. Samsung Bespoke WD11DB7B85GBU3 combi washer/dryer, is this supported in your program?
I can’t say for sure, but the app picks up properties rather than specific devices, so there’s a strong possibility.
ok that’s great then i guess i’ll put it in as a washing machine. thanks for the reply 
