Like Neato remove certificate for Vorwerk

[Najihel]

Hello,

At the moment https://github.com/stianaske/pybotvac/blob/master/pybotvac/cert/ksecosys.com.crt is an old certificate :

Serial Number=0F 91 EA 32 C5 00 E8 1C 29 BF 1C 5E 34 20 24 7F
Not Valid Before=Thursday 7 July 2022 at 02:00:00 Central European Summer Time
Not Valid After=Saturday 8 July 2023 at 01:59:59 Central European Summer Time

The production one is

b1:24:bf:bc:02:5b:2f:1c:a6:b8:a3:2d:68:3c:de:0f
            Not Before: May  6 00:00:00 2024 GMT
            Not After : May  6 23:59:59 2025 GMT

Maybe like Neato through #89 it's possible to remove locally stored wildcard certificate of *.ksecosys.com

I think some PR and issues are related to :

• Plugin after OpenSSL Update down nicoh88/homebridge-vorwerk#18
• remove manual cert validation for vorwerk connections #83
• https://community.home-assistant.io/t/creation-of-vorwerk-kobold-component/253166/92

Thanks

[tsloms]

Would be nice if this could be the solution for my issue with the VR200 I own. It's there anything I could do to speed up the process? Is there a way that I can test this...?

[stianaske]

Unfortunately I don't have any way of verifying the Vorwerk logic but I expect that the fix from #89 should work for Vorwerk as well.

If you can either

1. Verify that remove manual cert validation for vorwerk connections #83 resolves your issue or
2. Submit a new PR with required changes

I would be happy to accept the PR and create a new release.

[tsloms]

Unfortunately, I'm no dev, so I have no idea where to find the corresponding files in my homeassistant filesystem. Searched in the custom_components/vorwerk folder and also others. Any hint, where I might find the files to be edited or how I might test the pybotvac changes inside Homeassistant?

[jens4155]

Unfortunately I don't have any way of verifying the Vorwerk logic but I expect that the fix from #89 should work for Vorwerk as well.

If you can either

1. Verify that [remove manual cert validation for vorwerk connections #83](https://github.com/stianaske/pybotvac/pull/83) resolves your issue or

2. Submit a new PR with required changes

I would be happy to accept the PR and create a new release.

I can confirm, that remove manual cert validation for vorwerk connections #83 resolves the issue, in my case a VR 200. Thanks!

[jens4155]

Unfortunately, I'm no dev, so I have no idea where to find the corresponding files in my homeassistant filesystem. Searched in the custom_components/vorwerk folder and also others. Any hint, where I might find the files to be edited or how I might test the pybotvac changes inside Homeassistant?

You need to use a terminal add-on in HA. I use the Advanced SSH & Web Terminal add-on. In my case the file you need to edit is located in /usr/local/lib/python3.13/site-packages/pybotvac/vorwerk.py

[tsloms]

You need to use a terminal add-on in HA. I use the Advanced SSH & Web Terminal add-on. In my case the file you need to edit is located in /usr/local/lib/python3.13/site-packages/pybotvac/vorwerk.py

Thanks for the hint! Unfortunately, there is no such directory on my instance. I'm using the supervised installation of homeassistant on a VM. The only folder in /usr/local/lib/ is called perl5...
if I try to find anything with the name vorwerk, only the custom_component is found. Searching for botvac deliveres no match at all...

I would be glad to finally get this sorted out if someone has any idea where to find this file...

[tsloms]

1. Verify that remove manual cert validation for vorwerk connections #83 resolves your issue or
2. Submit a new PR with required changes

I would be happy to accept the PR and create a new release.

As I'm unable to test this, but @jens4155 already confirmed, I think you can accept the PR. Or do you need us to make a new PR?

It's worth trying anyway, because right now, the integration remains unusable...

Thank you!

[Najihel]

@stianaske Could you please merge the PR ? Thanks.

[stianaske]

Merged #83 which should resolve this.