-
Notifications
You must be signed in to change notification settings - Fork 7
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
checkAMatHome >> homeLocation.latitude and/or homeLocation.longitude not set or failure on reading! #23
Comments
Hi, |
Maybe it makes sense to add a switch to enable/disable this function in case you won't use it. BTW I can't set these values manually, they get overwritten asap |
Sorry, what function do you like to switch? My position values remains unchanged, i.e. lat = 47.400096904332386, but a latitudeOffset was set: 47.4000683 What does it mean "warn | (221560) updateStatus, result.operatingMode === HOME". I don't understand this warning, the mower is parked. Is the parking / charging position not the home position? |
I proposed to add a switch to the config section of the adapter like "Check Mower position YES/NO" to enable or disable these checks. After restarting the adapter I was able to enter values ... But I dont get the warning you are getting (yet). |
this switch for checking the position is a good idea. After starting the adapter: same behaviour: |
No didn't get this error on a restart, only State "husq-automower.0.info.mowers_json" has no existing object, this might lead to an error in future versions Maybe open a separate issue for your warning log. |
I "fixxed" this warning by just editing the main.js and in line 1539 i changed this
to
|
Hi,
I also have this issue "checkAMatHome >> homeLocation.latitude and/or homeLocation.longitude not set or failure on reading!" with may 315 as described in #10
I tried v1.1.0 and v 1.1.2.
How can I fix this or can you add a check if these values exist and query them only if they exists?
The warning log every check is really annoying ;-)
Thanks a lot,
KoMa1978
The text was updated successfully, but these errors were encountered: