Re: Sensibo and crestron stopped working
|
Thanks for the thoughts. ? Especially thank you to jbasen for your thoughts. ?
The strange thing is that I have updated nothing. ? I haven’t touched the code or firmware in the cp3 ( yes not a cp4). The certificate on the cp3 is self signed and has an expiry date of 2074. ?
I am wondering if the sensibo has updated its firmware automatically and has an issue with the self signed crestron certificate.?
I’m also trying to work out if the error message is a result of the sensibo not liking the certificate in the crestron cp3 or if it’s a result of the crestron cp3 not liking the certificate on the sensibo. ??
toggle quoted message
Show quoted text
On 26 Mar 2025, at 4:39?am, jbasen via groups.io <jay.m.basen@...> wrote:
?
Thanks for chiming in.? Good idea.
Jay
On 3/25/2025 7:49 AM, ckangis via groups.io wrote:
I'm well above my pay-grade here, so this is just a possible musing...
?
Did you upgrade to some of the most recent FW (I'm assuming this is a CP4)??
There's some issues with HomeKit, DSC, etc. that these newer FWs break related I think to certificate management.
I don't use these interfaces but I'm sure if I updated my CP4's it would break something that they haven't identified, and maybe this is your issue...
I've been staying on the "cp4_2.8003.00056.01.puf", as it seems to be *reasonably* stable...and you know what 'reasonably' means...:)
?
Just throwing this out as a possibility...
|
