On 18 Apr 2025, at 8:41?am, jbasen via groups.io <jay.m.basen@...> wrote:
?
I'm glad I've got something that is working for you?
Jay
On 4/17/2025 4:38 PM, gbnet.hifi via groups.io wrote:
This has prompted me to move to Hubitat for sensibo. ? And I¡¯m using Jays driver to communicate back to crestron. ?
I don¡¯t really want to update my crestron firmware as I¡¯ve heard of other people having things broken which were ?working well before updating. ?
On 17 Apr 2025, at 1:12?am, jbasen via groups.io
<jay.m.basen@...> wrote:
?
Thanks Jeremy.
I can make that change but, given the risks you highlight, would prefer to leave it to individual users.
Thanks again
Jay
On 4/16/2025 8:25 AM, Jeremy Weatherford via groups.io wrote:
I'm just a bystander here, but the exception seems to be complaining about the certificate on the remote site, which for this module appears to be
.? I would start by updating the firmware on the processor - it is possible Sensibo switched to a new Certificate Authority which is not accepted by your processor, and the newer firmware
would include this new CA.? If that doesn't work, you can modify the module code by adding "client.HostVerification = false;" after each "HttpsClient client = new HttpsClient();" line (there are 9 of them).? This allows for the possibility of someone intercepting
your traffic and impersonating the Sensibo server.? Only proceed if this is an acceptable risk.? :)
On Tue, Mar 25, 2025 at 2:40?AM gbnet.hifi via <gbnet.hifi=[email protected]> wrote:
I am hoping that @jbasen will see this.?? I have been using your sensibo module for a few years and it has been working fantastically well.
?
Today the module has started erroring.?? Seems to be an SSL issue.