-
Notifications
You must be signed in to change notification settings - Fork 29
Map feature and garden size entity #262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Conversation
Fix for sander1988#258 deprecated constants VacuumActivity.xxx
Added map/download_map functions
Added download_map service
Added Camera and garden_size entity
added ENTITY_CAMERA and ENTITY_GARDEN_SIZE
added svgutils to the requirements
correct some copy & paste mistakes
coorect some copy & paste mistakes
|
Can you help me find a solution for this? Logger: homeassistant.config_entries Error setting up entry Stein (127604418) for indego |
again correction of some copy and paste mistakes
|
Sorry, i thought i have corrected all copy & paste mistakes this morning but after you reported the failure i looked in the files once more and there were some more. Regards |
|
thanks for doing this. Logger: homeassistant.config_entries Error setting up entry Stein (127604418) for indego |
|
Did you copy the camera.py file to your custom_component/indego folder ? The IndegoCamera class is defined in the camera.py file and then imported and loaded in the init.py (line 47 "from .camera import IndegoCamera"). seems as the import didn`t work. the only idea i have at the moment is, that the class is missing because of the missing camera.py file |
|
Thank you so much. I got it working. It was a spelling error from my side when i created the camera.py file. |
|
Glad to hear that it is working now. It would be great if you could report in some days if it is still working. On my side it was working for some time but since yesterday my mower, mower state and mower state detail entities are suddenly unavailable and i dont know why. My logs say that the update_state took too long or the response was too slow but at the moment i dont know if this is related to the map feature or not. |
|
@kimzeuner could this be related to: #260 |
|
Thanks for the hint but that was not the problem. I was trying to find some further improvements which caused it. The version here should still work. |
|
@sander1988 please add this feature! |
Hello,
It`s me again. I have closed the last pull request for the map feature as i had suddenly issues with the connection (i think because of too many api calls).
This time i have prepared the following:
There is a new service called download_map which has to be used to download the map. It is recommended to use it only once initially or if your map has changed.
The service will download the map and store it in /config/www/indego_map_serialnumber.svg. If there are multiple mowers the serial number which is used in the download_map service will be used. Otherwise it just takes the already existing serial number of the integration. just as it is with e.g. delete_alerts.
Afterwards the camera entity will use this svg file and add the position of the mower to it. The position is updated if there is a regular update from _update_state(longpoll), additional it will send an update_state(force=true) every 60 seconds which means that the position in the map will not be in real time but better then nothing. (60 seconds are also used in iobroker or openhab if i saw it right) so i think there should not be too many api calls. The camera entity itself will show idle when the mower is docked and streaming when the mower is mowing. If the mower is docked there are no api calls for a new position.
Regards