adrigzr / badconga Goto Github PK

Hola.
He instalado el repositorio desde HACS, he copiado la carpeta badconga en mi directorio de custom components y he introducido el código propuesto en mi configuration.yaml.
Pero cuando verifico la configuración, antes de reiniciar, el sistema se queda colgado y tengo que anular el código de configuration.

Hi!

First of all thank you for the integration, great work!

I have a Conga 3090 and it seems to be working well, the only thing missing is the map and everything related to it (Excluding zones, working zones, etc...) It says that the camera.conga entity id is not unique. This entity shold be working? Is there a way to have the map working?

Thank you in advance.

Hi @dave-code-ruiz!

What is the benefit of having these entity services over using the generic vacuum services?

(badconga.return_to_base vs. vacuum.return_to_base+entity_id: vacuum.conga)

Originally posted by @zzarne in #9 (comment)

Hola
Este addon me viene genial para mi Conga 3090, los controles del robot funcionan perfectamente, pero no consigo que se vea el mapa en la tarjeta de Lovelace. He habilitado el debug y no veo ningún error aparente

Looks like not supported yet 6090 model. Would be great to have this. Basic status/commands would be enough for me. Map is secondary to integrate the device with my automations.

If any help is needed please feel free to contact. Thanks for your work!!

First off I'd like to thank and praise @adrigzr for this integration. The code is very well structured, readable and working.

As far as I understand, @adrigzr is no longer supporting it in favor of Valetudo, as stated in pull requests #9 and #13. While I'm in favor of switching to a cloudless solution, it may not (yet) be for everyone, as - as far as I understand - Valetudo requires the user to root the device. This may or may not void the warranty. It may be difficult to inexperienced users and may involve connecting the device to a computer via a service port or via ssh.

@adrigzr could you please

• state the support state in the README.md
• confirm or correct me in my above assumptions
• tell us the state of the Valetudo integration

While there is (assumed) demand for this integration, how about creating an organization which oversees further development?

Newbie with coding .. is there any help on how to start using or testing this code? And system or OS requirements please.

it returns <Status: error>
but it seems to show most other information correctly, and also the "locate" action works.

happy to help troubleshooting.

Thank you. It works perfectly with 5490, even map is showing. There’s any way to implement plan changing?

Logger: root
Source: custom_components/badconga/app/socket.py:28
First occurred: 12:13:54 (1 occurrences)
Last logged: 12:13:54
Uncaught thread exception

Traceback (most recent call last):
File "/usr/local/lib/python3.8/threading.py", line 932, in _bootstrap_inner
self.run()
File "/usr/local/lib/python3.8/threading.py", line 870, in run
self._target(*self._args, **self._kwargs)
File "/config/custom_components/badconga/app/conga.py", line 51, in on_logout
self.loop()
File "/config/custom_components/badconga/app/conga.py", line 30, in loop
return self.client.login(self.email, self.password)
File "/config/custom_components/badconga/app/client.py", line 194, in login
self.socket.connect()
File "/config/custom_components/badconga/app/socket.py", line 28, in connect
self.sock.connect((self.host, self.port))
TimeoutError: [Errno 110] Operation timed out

I get that error from the Home Assistant log. My solution proposal is to catch that error and retry the connect call until the connection is successfully established.

Hi !

What a great job, it works like a charm with a 3290 :)

Do you think if possible to add the go_to_location ? like Mi : https://valetudo.cloud/pages/general/capabilities-overview.html#GoToLocationCapability

Usefull for stay in front of bin after a number of clean cycles instead of simple notifications

From France with love !