Continuous IP bans caused by the card on Companion App
See original GitHub issueChecklist
- I have updated the card to the latest version available
- I have cleared the cache of my browser
- I have checked if the problem is already reported
The problem
Hi there,
since the last major update of the card (last year), I have problems when using the Home Assistant Companion App.
When I am opening the HA Companion app and the last shown lovelace tab was the tab that includes the vacuum card, I always get an IP ban (I have set up HA to ban IPs after 3 tries). It looks like the card is refreshing in a very high frequency and then I get banned instantly. The problem occurs on both, IOS and Android phones.
My current workaround is to head to a Lovelace tab that doesn’t include the vacuum card every time before closing the HA companion app. But, obviously this is not very user friendly. That’s why I’m reporting the issue.
What version of a card has described problem?
v2.0.10
What was the last working version card?
v1.2.3
What vacuum model do you have problems with?
roborock.vacuum.s5e
Which integration do you use to control your vacuum (link)?
https://www.home-assistant.io/integrations/xiaomi_miio/
What browser (browsers/apps) does have this problem?
iOS/Android
What version of Home Assistant do you use?
2022.2.6
What type of installation are you running?
Home Assistant OS
Card’s configuration
type: custom:xiaomi-vacuum-map-card
map_source:
camera: camera.xiaomi_cloud_map_extractor
calibration_source:
camera: true
entity: vacuum.roborock
vacuum_platform: default
map_modes:
- template: vacuum_clean_segment
predefined_selections:
- id: xx
outline:
- xx
label:
text: Room X
x: xx
'y': xx
offset_x: xx
offset_y: xx
icon:
name: mdi:xx
x: xx
'y': xx
- template: vacuum_goto_predefined
predefined_selections:
- position:
- xx
- xx
label:
text: xx
x: xx
'y': xx
offset_y: xx
icon:
name: mdi:xx
x: xx
'y': xx
- template: vacuum_clean_zone
- template: vacuum_goto
map_locked: true
two_finger_pan: false
Javascript errors shown in the browser’s console (if applicable)
No response
Additional information
No response
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:15 (7 by maintainers)
Top GitHub Comments
I also have this problem, I have tried several different solutions, but none of them worked perfectly. I might have to change the method of retrieving the image
@barrymossel yeah, I think that both these problems have the same origin