Proscenic 790T Integration

Himdola · June 5, 2020, 1:49pm

Add picture entitiy to lovelace and i have used this code;

aspect_ratio: 34%
entity: vacuum.vacuum_cleaner
image: ‘location of your picture on HA’
show_state: true
theme: Google - Dark
type: picture-entity

I mean with that filters this option below, so when you have replaced the filters/brushes or clean the Robot, you set that manually and then you can see it on the card when it was replaced or cleaned…

Just also your integration need well internet connection (no problem about that), i did blocked my vacuum to the internet and the actions from the integration has not worked anymore from HASS

deblockt · June 11, 2020, 7:37am

Hi,

New version of integration is available
This new version allow to display the vacuum cleaning map.

You can find installation doc here: https://github.com/deblockt/hass-proscenic-790T-vacuum/blob/master/README.md#home-assistant-proscenic-790t-vacuum-integration

@Himdola I added you issues on github https://github.com/deblockt/hass-proscenic-790T-vacuum/issues it’s easier to follow it on github. If you have time, you can fill it with more context information to help to debug.

Himdola · June 11, 2020, 3:08pm

Hello @deblockt, yes i will follow thath. I have installed the new version but what do i to add on Lovelace to see the map and where do i add that?

deblockt · June 11, 2020, 4:26pm

I added some documentation about the camera, you can find it here https://github.com/deblockt/hass-proscenic-790T-vacuum/blob/master/README.md#add-to-lovelace .

A summary

To display the camera on lovelace, you can :

use the vacuum-card configure the card using code editor and add map property map: camera.vacuum_map .

entity: vacuum.my_vacuum
image: default
map: camera.vacuum_map
type: 'custom:vacuum-card'

or use a card of type picture-entity

type: picture-entity
entity: vacuum.my_vacuum
camera_image: camera.vacuum_map
aspect_ratio: 100%
show_state: true
show_name: true
tap_action:
  action: more-info

Himdola · June 12, 2020, 10:31am

Ok it works now. Thank you.

Himdola · June 12, 2020, 10:33am

Should that be also possible for 790T? Because on the Proscenic app is that not possible to clean a selected area

deblockt · June 12, 2020, 12:06pm

Nope, it’s not possible :s. I can not add functionality not supported by the proscenic app :s

compoundbow83 · June 12, 2020, 5:36pm

Hello,
sorry, but my english is not the best.

I have a Problem with with the integration.

The Status tell my all the time off and not docked or so on.
And I can´t also start or stop the vacuum the Home Assistant.

In the Log I can see this:
File “/config/custom_components/proscenic/vacuum_proscenic.py”, line 91, in _send_command
raise VacuumUnavailable(‘can not connect to the vacuum. Turn on the physical switch button.’)
custom_components.proscenic.vacuum_proscenic.VacuumUnavailable: can not connect to the vacuum. Turn on the physical switch button.

What can I do?

I have forgot two thinks:
I have an M7 Pro
And the Proscenic App is on an iOS device

gh0s7 · June 22, 2020, 9:25am

Hi, @deblockt! I see you’ve done very good job! Nice work! I even have some ideas about how to extend the integration to wrap all the full functionality, but I’ll share them a little bit later. First I want to integrate the vacuum with your code. I have a little problem with the custom card (the vacuum integration itself is working). I followed the instructions to integrate the card, but lovelace doesn’t recognize it, I mean it says there isn’t such custom card named vacuum-card, even after HA restart.

gh0s7 · June 22, 2020, 8:53pm

Hm … It turned out, that the integration is not working. It can’t connect to the vacuum cleaner. I triple checked the IP, but that was not the problem. I saw that the communication between the app and the vacuum is using only port 80 and 20008, but changing the port is not making any difference. Very strange. It always says that I have to switch the side button. I checked the config parameters, but they are the same (no mistakes). I see the following error multiple times in the log:

2020-06-22 23:49:47 INFO (MainThread) [custom_components.proscenic.vacuum_proscenic] sign in to proscenic server
2020-06-22 23:50:01 DEBUG (MainThread) [custom_components.proscenic.vacuum_proscenic] do not get the map. The vacuum is not cleaning. Waiting 30 seconds
2020-06-22 23:50:18 ERROR (MainThread) [custom_components.proscenic.vacuum_proscenic] error on refresh loop
Traceback (most recent call last):
  File "/config/custom_components/proscenic/vacuum_proscenic.py", line 216, in _refresh_loop
    (reader, writer) = await asyncio.open_connection('47.91.67.181', 8888, loop = self.loop)
  File "/usr/local/lib/python3.7/asyncio/streams.py", line 77, in open_connection
    lambda: protocol, host, port, **kwds)
  File "/usr/local/lib/python3.7/asyncio/base_events.py", line 962, in create_connection
    raise exceptions[0]
  File "/usr/local/lib/python3.7/asyncio/base_events.py", line 949, in create_connection
    await self.sock_connect(sock, address)
  File "/usr/local/lib/python3.7/asyncio/selector_events.py", line 473, in sock_connect
    return await fut
  File "/usr/local/lib/python3.7/asyncio/selector_events.py", line 503, in _sock_connect_cb
    raise OSError(err, f'Connect call failed {address}')
TimeoutError: [Errno 110] Connect call failed ('47.91.67.181', 8888)
2020-06-22 23:50:18 INFO (MainThread) [custom_components.proscenic.vacuum_proscenic] sign in to proscenic server
2020-06-22 23:50:31 DEBUG (MainThread) [custom_components.proscenic.vacuum_proscenic] do not get the map. The vacuum is not cleaning. Waiting 30 seconds

Engineer · June 29, 2020, 8:43pm

I get occasionally the status but mostly it’s off stating please check the side switch. I get no map and no controls work from HA. So its partly working sometimes.
I need to check for latest release but I think I have it already.

I also get connect call failed messages if I try to control it.

deblockt · July 9, 2020, 6:04am

hi @gh0s7 I think that your vacuum use an old version of the firmeware. in 2018 I’ve tried your integration and it not work on my vacuum, your protocol is not supported by my vacuum, and I think that my protocol is not supported by your vacuum. Maybe that we should merge our code to support all vacums. Or maybe just upgrade your firmeware can do the job. My firmeware version are : mcu: 1.8.2614 and wifi 1.0.41.

@Engineer have you some logs about the integration to understand what is the issue?

deblockt · July 9, 2020, 6:06am

Only the 790T proscenic vacuum is supported. I don’t have the M7 pro to perform test. I think that the two vacuum doesn’t use the same protocol.

gh0s7 · July 9, 2020, 12:08pm

@deblockt I updated the firmware last year … Curently it is up to date. I can check the version number later, in the evening.

Engineer · July 9, 2020, 4:15pm

Log Details (ERROR)

Logger: homeassistant.components.websocket_api.http.connection.140421875121424
Source: custom_components/proscenic/vacuum_proscenic.py:92
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 8:10:56 PM (3 occurrences)
Last logged: 8:11:02 PM

can not connect to the vacuum. Turn on the physical switch button.

Traceback (most recent call last): 
File "/config/custom_components/proscenic/vacuum_proscenic.py", line 74, in _send_command (_, writer) = await asyncio.open_connection(self.ip, 8888, loop = self.loop) 
File "/usr/local/lib/python3.7/asyncio/streams.py", line 77, in open_connection lambda: protocol, host, port, **kwds) 
File "/usr/local/lib/python3.7/asyncio/base_events.py", line 962, in create_connection raise exceptions[0] 
File "/usr/local/lib/python3.7/asyncio/base_events.py", line 949, in create_connection await self.sock_connect(sock, address) 
File "/usr/local/lib/python3.7/asyncio/selector_events.py", line 473, in sock_connect return await fut
File "/usr/local/lib/python3.7/asyncio/selector_events.py", line 503, in _sock_connect_cb raise OSError(err, f'Connect call failed {address}') 
ConnectionRefusedError: [Errno 111] 
Connect call failed ('192.168.178.59', 8888) During handling of the above exception, another exception occurred: 
Traceback (most recent call last): 
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 130, in handle_call_service connection.context(msg), 
File "/usr/src/homeassistant/homeassistant/core.py", line 1260, in async_call task.result() 
File "/usr/src/homeassistant/homeassistant/core.py", line 1295, in _execute_service await handler.func(service_call) 
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 209, in handle_service self._platforms.values(), func, call, required_features 
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 454, in entity_service_call future.result() # pop exception if have 
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 595, in async_request_call await coro 
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 485, in _handle_entity_call await result 
File "/config/custom_components/proscenic/vacuum.py", line 183, in async_turn_on await self.device.clean() 
File "/config/custom_components/proscenic/vacuum_proscenic.py", line 63, in clean await self._send_command(b'{"transitCmd":"100"}') 
File "/config/custom_components/proscenic/vacuum_proscenic.py", line 92, in _send_command raise VacuumUnavailable('can not connect to the vacuum. Turn on the physical switch button.') 
custom_components.proscenic.vacuum_proscenic.VacuumUnavailable: can not connect to the vacuum. Turn on the physical switch button.

These are the logs after trying to command it.

I have same mcu as you 1.8.2614 but my esp is 1.036

Engineer · July 10, 2020, 9:29am

It is mostly shown as a status ‘Off’ but when it is working i have seen the state change to something else, i cant remember what and i’ve seen it as ‘Docked’ so it can talk to the robot. Just seems to be commands that are the problem.

Also, no map is ever found by Hassio.

deblockt · July 10, 2020, 12:02pm

The status off is set when we can not contact the vacuum.
To get the vacuum status I use the proscenic cloud server (so i don’t need to contact the vacuum), so the status can be fine, without have capability to send command to the vacuum.
Is your hass server on the same network as your vacuum?

If you perform a capture using Packet capture can you see that the app contact your vacuum using the ip 192.168.178.59 and the port 8888?

Engineer · July 10, 2020, 2:05pm

Yes, same network and the auth id etc was obtained using capture so the app can talk to the vacuum on the ip and port. This is clear in the capture. With the app there is no issue.

Are you saying the status is from the cloud? If so, that doesn’t often work either. Its strange not even the map is obtained. I will look again and double check the port 8888 is not blocked by the router.

Engineer · July 10, 2020, 2:24pm

Sadly, port 888 is fully open for the vacuum across the network. If i restart HA whilst the vacuum is working i get status but if i command it i get the following:

What am i missing? Should i uninstall completely and start from scratch maybe?

deblockt · July 12, 2020, 10:09am

Hi,

thanks for detail.
For your first error, i have it too. But it don’t do any issue with the integration. I have a github issue to fix that. Can you copy paste your log on the issue, I will be able to test with your case. https://github.com/deblockt/hass-proscenic-790T-vacuum/issues/10.

This is strange to have a ‘ConnectionRefusedError’. In general this issue happend if the server (the vacumm) doesn’t listen on the port. You have the same issue as @gh0s7.

Can you try to run this command (from your home assistant server) telnet <your_vacuum_ip> 8888 to see if you have this result:

➜  ~ telnet 192.168.1.31 8888
Trying 192.168.1.31...
Connected to 192.168.1.31.
Escape character is '^]'.

If it not work, you can run this command (can take a time) nc -z -v <your_vacuum_ip> 1-65000 2>&1 | grep succeeded to see all openned port on your vacuum.