Neato Component - Add vendors in order to allow support for Vorwerk vacuum

Username and Password are correct
https://beehive.neatocloud.com/sessions does not appear to be the correct URL for Vorwerk?

class Vorwerk:
name = ‘vorwerk’
endpoint = ‘https://beehive.ksecosys.com/
headers = ‘application/vnd.neato.beehve.v1+json’
cert_path = False

@grantc and @Cobi, I submitted pull requests that I think will fix your issues. You can try out the modified code from here:

https://github.com/JeffLIrion/hass-neato-custom-component/tree/temp

2 Likes

Hi Jeff,

Many thanks for the work put in to get this up and running - initial tests are good, but will do some more comprehensive testing tomorrow as it is getting late here. Once again thankyou to yourself and dshokouhi

@dshokouhi and @JeffLIrion, I just want to thak you. It’s fully working!!! The only exception is battery level that is not being exposed. Never the less to be honnest the main goal was to have this witthout workarounds in home assistant.

Again thank you!

@grantc can you please confirm that you get your battery level exposed?

I think I know what the battery issue is I’ll try to submit a fix for that later today. Glad to hear it is working and thanks again to @JeffLIrion for all of his help!

1 Like

Yes I can confirm the % battery level is not showing

ok I think I got the battery level to show up now, my branch was a bit out of date and I remember seeing a bug fix for vacuums that did not have mapping. This branch now includes the most recent HA changes as well.

1 Like

Thanks, % battery now visible

image

1 Like

It also fixed for me. Thank you all for your work. I think that this should be a candidate to be merged in to HA.

2 Likes

PR submitted

Just wondering if anyone has been able to initiate a clean in “eco” mode on the VR200? It always uses, turbo/full power mode and drains the battery too quick. They only way I can see this being possible is via “neato_custom_cleaning” call and this does not work. Eco mode is an option in the Vorwerk app.

This depends on what Vorwerk is expecting do they have any Dev docs to look at?

Is this of any use?

1 Like

I am looking at this now but it looks like we are using the same variables

What happens if you wrap the number in quotes? Doubt it makes a difference but worth a shot :slight_smile:

also if you do not have any maps, try setting category: 2 as well

edit:
One last thing :slight_smile:

If you guys are able to interact with the parent library please post the state output here…this may be more helpful so we can see what service version your vacuums are using. You can run the state command whiles its idle and when its cleaning with the specifications you desire. This can help us understand what values to use.

We may need to fine tune things for Vorwerk if its not working like Neato.

These are the official Neato docs that we base everything off.

https://developers.neatorobotics.com/api/robot-remote-protocol

One thing I am curious about is what Vorwerk models are connected and work with this library and what the service version is for each model :slight_smile:

Hi, thanks once again for looking into this - will try and look at it again in a day or so… work commitments atm.

So the including category: 2 as well and without quotes seems to work fine initiating “eco” mode. Thanks

1 Like