Let me add that I've just started working with a product that
will be an alternative to the Sensibo.? I'm in the process of
talking to the company about some features and waiting for some
product updates so it isn't anything I can discuss at this time.?
However, I just wanted to throw this out in case it turns out that
the integration is terminally broken.? I'm working towards have an
article out in a few months.
Thanks
Jay
On 3/25/2025 4:49 PM, jbasen via
groups.io wrote:
toggle quoted message
Show quoted text
As is always the case, you are the first person to report this
issue.?.
I wish I could help more but certificates are just something
that I fully admit I don't have the necessary knowledge to help
with debugging.? I also don't have any contacts at Sensibo that
I can pull from to provide assistance.? Sensibo does have a
support center website ().?
When I was writing the integration code I had to use them
periodically.? I can't say they were great but it might be worth
a try to send them a message.? At least they might be able to
tell you if they changed anything on their end with a firmware
update.?
Hope this helps, at least a little.
Jay
On 3/25/2025 4:38 PM, gbnet.hifi via
groups.io wrote:
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. ??
?
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...
