Errors, child devices and capabilities about openhab-smartthings HOT 2 OPEN

First of all - which version of the jar file are you using? In January I discovered that Discovery wasn't working & in late January I made an update. If you got the version from my Git repo you should have picked up the version: org.openhab.binding.smartthings-3.1.0-SNAPSHOT.jar. I think this should be the same as the one through openHAB but I don't know what their process is to take bindings they have reviewed and move them to production. During startup do you see any messages in the logs about Discovery running? If not it is likely you have a broken version.

With regards to the timeout messages: I have seen these as well and don't know what causes them but I don't think they are being caused by my Smartthings binding. There is a way to increase the timeout. In the .things file you can add a parameter smartthingsTimeout=xx. In the same block where smartthingsName goes. You can read a lot more about the timeout issue in #98. In particular read this comment from Sept 17.

I have no idea why you are getting SSL error messages. The communications between the ST hub and openHAB has to be over an un-encrypted conversation because the hub doesn't support SSL.

I've not made any attempt to support child devices. One of the (many) challenges has been that I don't have devices to test against. I don't own any Samsung appliances. I have had requests before to support some Samsung appliances (maybe washing machine and dishwasher). To do that I made "simulators" using the Smartthing tools. Lots of hours and of course they can only respond the way I think they should work. It seems like you've used curl and port listener to communicate directly with the hub. Have you tried setting up the port listener and then opening the door and seeing if a message is sent. If you look in THIS file you can see exactly what is supported. And, you can even change the file if you have a way to edit files already in side of a jar/zip file. You can not add new devices but you can change what is there.

I know I haven't answered all of you questions but I need to get out of the house now and wanted to get something back to you today. Let me know if you still want answers to the other questions.

Bob

from openhab-smartthings.

First of all - which version of the jar file are you using? In January I discovered that Discovery wasn't working & in late January I made an update. If you got the version from my Git repo you should have picked up the version: org.openhab.binding.smartthings-3.1.0-SNAPSHOT.jar. I think this should be the same as the one through openHAB but I don't know what their process is to take bindings they have reviewed and move them to production.

I am using the addon version, bundled in openhab-addons-2.5.12.

During startup do you see any messages in the logs about Discovery running? If not it is likely you have a broken version.

Actually I dont, even with Openhab's addon-version. So OK, this might be fixed in a coming release. It's fine anyway now that I've figured out how to configure it manually.

With regards to the timeout messages: I have seen these as well and don't know what causes them but I don't think they are being caused by my Smartthings binding. There is a way to increase the timeout. In the .things file you can add a parameter smartthingsTimeout=xx. In the same block where smartthingsName goes. You can read a lot more about the timeout issue in #98. In particular read this comment from Sept 17.

Perfect, thanks - I will check this and see if it helps.

I have no idea why you are getting SSL error messages. The communications between the ST hub and openHAB has to be over an un-encrypted conversation because the hub doesn't support SSL.

That's what I thought as well. Just figured maybe it could be the reason for messages timing out. But if increasing the timeout resolves the issue, it is indeed unrelated.

I've not made any attempt to support child devices. One of the (many) challenges has been that I don't have devices to test against. I don't own any Samsung appliances. I have had requests before to support some Samsung appliances (maybe washing machine and dishwasher). To do that I made "simulators" using the Smartthing tools. Lots of hours and of course they can only respond the way I think they should work. It seems like you've used curl and port listener to communicate directly with the hub. Have you tried setting up the port listener and then opening the door and seeing if a message is sent. If you look in THIS file you can see exactly what is supported. And, you can even change the file if you have a way to edit files already in side of a jar/zip file. You can not add new devices but you can change what is there.

OK, I understand. I will try and dig into your code and see if I can contribute somehow - as I now have a side-by-side refrigerator, an oven, a cooktop, a dishwasher and a washing machine. So plenty of devices to test on..

EDIT: Alright, so rapidCooling and rapidFreezing are in fact not implemented. Will see if I can figure out what I need to add..
When redirecting the smartapp to my PC and port listener I can see the parent device (Refrigerator) generate an event when the door opens, but not the child devices (Refrigerator Cooler and Refrigerator Freezer). So I guess the smartapp is not forwarding them? I mean I can see the value change in the data tree in Developer Tools, so some kind of event is triggering this? What's perplexing to me is that the values are being populated at startup - where is that coming from if not from an event. In Developer Tools I can see the Event Subscriptions do exist for the child devices as well as parent.

I know I haven't answered all of you questions but I need to get out of the house now and wanted to get something back to you today. Let me know if you still want answers to the other questions.
Bob

Thanks for the quick response Bob, much appreciated!

from openhab-smartthings.