Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Test Adapter Husqvarna Automower v0.3.x

    NEWS

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    • Minor js-controller 7.0.7 Update in latest repo

    Test Adapter Husqvarna Automower v0.3.x

    This topic has been deleted. Only users with topic management privileges can see it.
    • W
      Wing.Stefan @greyhound last edited by

      @greyhound Hi, wann geht der Live sodass man diesen im iobroker installieren kann. 2018 ist doch schon eine weile her
      danke

      1 Reply Last reply Reply Quote 1
      • Boronsbruder
        Boronsbruder last edited by Boronsbruder

        @greyhound
        Hilfe!
        Gestern gab der Automower-Adapter mit folgender Meldung den Geist auf!

        2022-03-28 09:27:18.814 - error: husq-automower.0 (30998) updateStatus geo_response.statusCode: 404
        2022-03-28 09:28:19.540 - warn: husq-automower.0 (30998) updateStatus typeof response or result === undefined
        2022-03-28 09:29:20.584 - warn: husq-automower.0 (30998) updateStatus typeof response or result === undefined
        

        Nach einem Neustart der Instanz kam nur noch

        2022-03-28 19:23:51.635 - info: host.zerobroker stopInstance system.adapter.husq-automower.0 (force=false, process=true)
        2022-03-28 19:23:51.637 - info: host.zerobroker stopInstance system.adapter.husq-automower.0 send kill signal
        2022-03-28 19:23:51.639 - info: husq-automower.0 (30998) Got terminate signal TERMINATE_YOURSELF
        2022-03-28 19:23:51.640 - info: husq-automower.0 (30998) Logged off.
        2022-03-28 19:23:51.641 - info: husq-automower.0 (30998) cleaned everything up...
        2022-03-28 19:23:51.641 - info: husq-automower.0 (30998) terminating
        2022-03-28 19:23:51.642 - info: husq-automower.0 (30998) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
        2022-03-28 19:23:52.205 - info: host.zerobroker instance system.adapter.husq-automower.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
        2022-03-28 19:23:54.662 - info: host.zerobroker instance system.adapter.husq-automower.0 started with pid 28334
        2022-03-28 19:23:55.191 - info: husq-automower.0 (28334) starting. Version 1.1.2 (non-npm: truegreyhound/ioBroker.husq-automower#7a8ed7031d6e945544c0adbb05d82cc0f322f954) in /opt/iobroker/node_modules/iobroker.husq-automower, node: v14.19.1, js-controller: 4.0.21
        2022-03-28 19:23:55.217 - info: husq-automower.0 (28334) State value to set for "husq-automower.0.mower.homeLocation.maxDistance" has to be type "number" but received type "string"
        2022-03-28 19:23:55.217 - info: husq-automower.0 (28334) State value to set for "husq-automower.0.mower.waitAfterRain" has to be type "number" but received type "string"
        2022-03-28 19:23:57.208 - info: husq-automower.0 (28334) Logged off.
        2022-03-28 19:23:57.233 - info: husq-automower.0 (28334) updateStatus mower object is NULL
        

        dann im Sekundentakt der "updateStatus mower object is NULL"

        Ich habe schon die Instanz, den Adapter, gelöscht und neuinstalliert...

        Das folgende Log ist nach der Neuinstallation

        2022-03-29 19:37:40.663 - info: host.zerobroker instance system.adapter.husq-automower.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
        2022-03-29 19:37:43.121 - info: host.zerobroker instance system.adapter.husq-automower.0 started with pid 25064
        2022-03-29 19:37:43.403 - debug: husq-automower.0 (25064) Redis Objects: Use Redis connection: 127.0.0.1:9001
        2022-03-29 19:37:43.515 - debug: husq-automower.0 (25064) Objects client ready ... initialize now
        2022-03-29 19:37:43.516 - debug: husq-automower.0 (25064) Objects create System PubSub Client
        2022-03-29 19:37:43.517 - debug: husq-automower.0 (25064) Objects create User PubSub Client
        2022-03-29 19:37:43.545 - debug: husq-automower.0 (25064) Objects client initialize lua scripts
        2022-03-29 19:37:43.548 - debug: husq-automower.0 (25064) Objects connected to redis: 127.0.0.1:9001
        2022-03-29 19:37:43.565 - debug: husq-automower.0 (25064) Redis States: Use Redis connection: 127.0.0.1:6379
        2022-03-29 19:37:43.568 - debug: husq-automower.0 (25064) States create System PubSub Client
        2022-03-29 19:37:43.568 - debug: husq-automower.0 (25064) States create User PubSub Client
        2022-03-29 19:37:43.571 - debug: husq-automower.0 (25064) States connected to redis: 127.0.0.1:6379
        2022-03-29 19:37:43.641 - info: husq-automower.0 (25064) starting. Version 1.1.2 (non-npm: truegreyhound/ioBroker.husq-automower#7a8ed7031d6e945544c0adbb05d82cc0f322f954) in /opt/iobroker/node_modules/iobroker.husq-automower, node: v14.19.1, js-controller: 4.0.21
        2022-03-29 19:37:43.654 - debug: husq-automower.0 (25064) createDataStructure started
        2022-03-29 19:37:43.654 - debug: husq-automower.0 (25064) createChannels started
        2022-03-29 19:37:43.655 - debug: husq-automower.0 (25064) createChannels finished
        2022-03-29 19:37:43.655 - debug: husq-automower.0 (25064) createDataStructure finished
        2022-03-29 19:37:43.656 - debug: husq-automower.0 (25064) Mail address: ************
        2022-03-29 19:37:43.656 - debug: husq-automower.0 (25064) waitAfterRain:
        2022-03-29 19:37:43.657 - debug: husq-automower.0 (25064) syncConfigAsync started
        2022-03-29 19:37:43.658 - debug: husq-automower.0 (25064) createDataStructure, createChannels() finished; result: {"msg":"Success","data":true}
        2022-03-29 19:37:43.658 - debug: husq-automower.0 (25064) createDPs started
        2022-03-29 19:37:43.659 - debug: husq-automower.0 (25064) createDPs finished
        2022-03-29 19:37:43.666 - debug: husq-automower.0 (25064) syncConfigAsync, mJsonLastLocations:[]
        2022-03-29 19:37:43.667 - debug: husq-automower.0 (25064) syncConfigAsync finished
        2022-03-29 19:37:43.669 - info: husq-automower.0 (25064) State value to set for "husq-automower.0.mower.homeLocation.maxDistance" has to be type "number" but received type "string"
        2022-03-29 19:37:43.669 - info: husq-automower.0 (25064) State value to set for "husq-automower.0.mower.waitAfterRain" has to be type "number" but received type "string"
        2022-03-29 19:37:43.718 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.homeLocation.name" with value ""
        2022-03-29 19:37:43.719 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.homeLocation.longitude" with value "0"
        2022-03-29 19:37:43.719 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.homeLocation.latitude" with value "0"
        2022-03-29 19:37:43.719 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.homeLocation.longitudeCP" with value "0"
        2022-03-29 19:37:43.719 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.homeLocation.latitudeCP" with value "0"
        2022-03-29 19:37:43.719 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.homeLocation.longitudeOffset" with value "0"
        2022-03-29 19:37:43.720 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.homeLocation.latitudeOffset" with value "0"
        2022-03-29 19:37:43.720 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.homeLocation.currentDistance" with value "0"
        2022-03-29 19:37:43.720 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.homeLocation.maxDistance" with value "500"
        2022-03-29 19:37:43.720 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.homeLocation.sensitivityLevel" with value "3"
        2022-03-29 19:37:43.720 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.homeLocation.sensitivityRadius" with value "1000"
        2022-03-29 19:37:43.721 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.lastLocation.latitude" with value "0"
        2022-03-29 19:37:43.721 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.lastLocation.longitude" with value "0"
        2022-03-29 19:37:43.721 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.lastLocation.timestamp" with value "0"
        2022-03-29 19:37:43.721 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.statistics.mowingTime" with value "0"
        2022-03-29 19:37:43.722 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.statistics.mowingTimeDaily" with value "0"
        2022-03-29 19:37:43.722 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.statistics.mowingTimeBatteryNew" with value "0"
        2022-03-29 19:37:43.722 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.statistics.batteryChargeCycleDaily" with value "0"
        2022-03-29 19:37:43.722 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.statistics.batteryEfficiencyFactor" with value "0"
        2022-03-29 19:37:43.722 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.statistics.chargingBatteryStarttime" with value "0"
        2022-03-29 19:37:43.722 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.statistics.chargingTimeBatteryCurrent" with value "0"
        2022-03-29 19:37:43.723 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.statistics.chargingTimeBatteryDaily" with value "0"
        2022-03-29 19:37:43.723 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.statistics.chargingTimeBatteryNew" with value "0"
        2022-03-29 19:37:43.723 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.statistics.lastChargingTimeBattery" with value "0"
        2022-03-29 19:37:43.723 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.statistics.currentCoveredDistance" with value "0"
        2022-03-29 19:37:43.723 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.statistics.coveredDistanceDaily" with value "0"
        2022-03-29 19:37:43.723 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.statistics.lastMowingTime" with value "0"
        2022-03-29 19:37:43.724 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.statistics.lastCoveredDistance" with value "0"
        2022-03-29 19:37:43.724 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.statistics.lastStationReturnTime" with value "0"
        2022-03-29 19:37:43.724 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.statistics.overallBatteryChargeCycle" with value "0"
        2022-03-29 19:37:43.724 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.statistics.overallMowingTime" with value "0"
        2022-03-29 19:37:43.724 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.statistics.overallCoveredDistance" with value "0"
        2022-03-29 19:37:43.724 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.action" with value "0"
        2022-03-29 19:37:43.725 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.batteryPercent" with value "0"
        2022-03-29 19:37:43.725 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.currentErrorCode" with value "0"
        2022-03-29 19:37:43.725 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.currentErrorMsg" with value ""
        2022-03-29 19:37:43.725 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.currentErrorCodeTimestamp" with value "0"
        2022-03-29 19:37:43.725 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.lastAction" with value "unkonwn"
        2022-03-29 19:37:43.725 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.lastDockingTime" with value "0"
        2022-03-29 19:37:43.726 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.lastErrorCode" with value "0"
        2022-03-29 19:37:43.726 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.lastErrorMsg" with value ""
        2022-03-29 19:37:43.726 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.lastErrorCodeTimestamp" with value "0"
        2022-03-29 19:37:43.726 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.lastHttpStatus" with value "0"
        2022-03-29 19:37:43.726 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.lastLocations" with value "[]"
        2022-03-29 19:37:43.726 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.lastStatus" with value "unkonwn"
        2022-03-29 19:37:43.726 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.lastStatusTime" with value "0"
        2022-03-29 19:37:43.726 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.lastStatusChangeTime" with value "0"
        2022-03-29 19:37:43.727 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.lastdayLocations" with value "[]"
        2022-03-29 19:37:43.727 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.nextStartSource" with value ""
        2022-03-29 19:37:43.727 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.nextStartTime" with value "0"
        2022-03-29 19:37:43.727 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.nextStartWatching" with value "0"
        2022-03-29 19:37:43.727 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.operatingMode" with value "unkonwn"
        2022-03-29 19:37:43.727 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.stopOnRainEnabled" with value "false"
        2022-03-29 19:37:43.727 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.stoppedDueRain" with value "false"
        2022-03-29 19:37:43.728 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.timerAfterRainStartAt" with value "0"
        2022-03-29 19:37:43.728 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.waitAfterRain" with value ""
        2022-03-29 19:37:43.728 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.sendMessage" with value ""
        2022-03-29 19:37:43.728 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.scheduleTime" with value "1"
        2022-03-29 19:37:43.728 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.http_request_count_day" with value "0"
        2022-03-29 19:37:43.728 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.http_request_count_day" with value "0", set in mnWebRequestCountDay
        2022-03-29 19:37:43.728 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.http_request_count_day_success" with value "0"
        2022-03-29 19:37:43.728 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.http_request_count_day_error" with value "0"
        2022-03-29 19:37:43.729 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.http_request_count_month" with value "0"
        2022-03-29 19:37:43.729 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.http_request_count_month_success" with value "0"
        2022-03-29 19:37:43.729 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.http_request_count_month_error" with value "0"
        2022-03-29 19:37:43.729 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.statistics.mowingStartTime" with value "0"
        2022-03-29 19:37:43.729 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.rawSend" with value ""
        2022-03-29 19:37:43.729 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.rawResponse" with value ""
        2022-03-29 19:37:43.729 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.rawResponse_geo" with value ""
        2022-03-29 19:37:43.730 - debug: husq-automower.0 (25064) syncConfigAsync, processing state: "mower.rawResponse_mowers" with value ""
        2022-03-29 19:37:43.730 - debug: husq-automower.0 (25064) syncConfigAsync, idnLastStatus: unkonwn, idnNextStartTime: 0, mStartMowingTime: 0, idnStoppedDueRain: false, idnCurrentErrorCode: 0, idnCurrentErrorCodeTS: 0
        2022-03-29 19:37:43.730 - debug: husq-automower.0 (25064) syncConfigAsync, idnCurrentCoveredDistance: 0, idnLastLocationLongitude: 0, idnLastLocationLatitude: 0, idnHomeLocationLongitude: 0, idnHomeLocationLatitude: 0
        2022-03-29 19:37:43.730 - debug: husq-automower.0 (25064) syncConfigAsync, idnBatteryPercent: 0, idnBatteryChargeCycleDaily: 0, idnMowingTime: 0, idnMowingTimeDaily: 0
        2022-03-29 19:37:44.658 - debug: husq-automower.0 (25064) dailyAccumulation started
        2022-03-29 19:37:44.658 - debug: husq-automower.0 (25064) dailyAccumulation, stop status timer
        2022-03-29 19:37:44.658 - debug: husq-automower.0 (25064) dailyAccumulation, add current covered distance to overall distance ...
        2022-03-29 19:37:44.659 - debug: husq-automower.0 (25064) dailyAccumulation, move lastlocations to lastday locations
        2022-03-29 19:37:44.659 - debug: husq-automower.0 (25064) dailyAccumulation, add daily mowing time to overall mowing time ...
        2022-03-29 19:37:44.660 - debug: husq-automower.0 (25064) dailyAccumulation, add daily battery charging cycle to overall charging cycle ...
        2022-03-29 19:37:44.660 - debug: husq-automower.0 (25064) dailyAccumulation, add daily http request counter to month ...
        2022-03-29 19:37:44.661 - debug: husq-automower.0 (25064) createStatusScheduler started
        2022-03-29 19:37:44.661 - debug: husq-automower.0 (25064) createStatusScheduler scheduler created, start every 1 secands
        2022-03-29 19:37:44.662 - debug: husq-automower.0 (25064) createStatusScheduler finished
        2022-03-29 19:37:44.662 - debug: husq-automower.0 (25064) dailyAccumulation finished
        2022-03-29 19:37:44.666 - debug: husq-automower.0 (25064) dailyAccumulation, add current covered distance; bCheck: true; stateCDD.ts: 1648575391687; new Date(00): 1648504800000; stateCDD.val: 0
        2022-03-29 19:37:44.666 - debug: husq-automower.0 (25064) dailyAccumulation, stateRCM.ts: 1648575391687; Date: Tue Mar 29 2022 19:36:31 GMT+0200 (Mitteleuropäische Sommerzeit)
        2022-03-29 19:37:44.666 - debug: husq-automower.0 (25064) dailyAccumulation, nDateMonth: 2; nDateRCM_Month_TS: 2
        2022-03-29 19:37:44.668 - debug: husq-automower.0 (25064) dailyAccumulation, stateRCD.ts: 1648575391687; Date: Tue Mar 29 2022 19:36:31 GMT+0200 (Mitteleuropäische Sommerzeit)
        2022-03-29 19:37:44.668 - debug: husq-automower.0 (25064) dailyAccumulation, nDateMonth: 2; nDateRCD_Month_TS: 2; nDateRCD_Day_TS: 2
        2022-03-29 19:37:45.657 - info: husq-automower.0 (25064) Logged off.
        2022-03-29 19:37:45.682 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:37:46.088 - info: husq-automower.0 (25064) Logged on. Checking for mowers.
        2022-03-29 19:37:46.658 - debug: husq-automower.0 (25064) createSubscriberAsync started
        2022-03-29 19:37:46.658 - debug: husq-automower.0 (25064) checkIfItsRaining started
        2022-03-29 19:37:46.659 - debug: husq-automower.0 (25064) checkIfItsRaining finished
        2022-03-29 19:37:46.659 - info: husq-automower.0 (25064) createSubscriberAsync, idRainSensor; stop due rain not enabled.
        2022-03-29 19:37:46.660 - debug: husq-automower.0 (25064) createSubscriberAsync, scheduler for dailyAccumulation created
        2022-03-29 19:37:46.668 - debug: husq-automower.0 (25064) createSubscriberAsync finished
        2022-03-29 19:37:46.683 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:37:47.683 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:37:48.683 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:37:49.684 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:37:50.685 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:37:51.685 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:37:52.686 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:37:53.685 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:37:54.686 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:37:55.686 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:37:56.687 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:37:57.687 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:37:58.688 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:37:59.688 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:38:00.689 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:38:01.689 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:38:02.689 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:38:03.690 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:38:04.690 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:38:05.690 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:38:06.690 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:38:07.691 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:38:08.692 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:38:09.691 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:38:10.691 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:38:11.691 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:38:12.692 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:38:13.691 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:38:14.691 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:38:15.692 - info: husq-automower.0 (25064) updateStatus mower object is NULL
        2022-03-29 19:38:16.245 - info: host.zerobroker "system.adapter.husq-automower.0" disabled
        2022-03-29 19:38:16.246 - info: host.zerobroker stopInstance system.adapter.husq-automower.0 (force=false, process=true)
        2022-03-29 19:38:16.248 - info: host.zerobroker stopInstance system.adapter.husq-automower.0 send kill signal
        2022-03-29 19:38:16.249 - info: husq-automower.0 (25064) Got terminate signal TERMINATE_YOURSELF
        2022-03-29 19:38:16.250 - info: husq-automower.0 (25064) Logged off.
        2022-03-29 19:38:16.251 - info: husq-automower.0 (25064) cleaned everything up...
        2022-03-29 19:38:16.252 - info: husq-automower.0 (25064) terminating
        2022-03-29 19:38:16.253 - info: husq-automower.0 (25064) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
        

        Woher kommts? Wo muss ich suchen? Was kann ich tun?

        Der Mähroboter lief nach der Aus-Winterung ca. 1 Woche ohne Probleme...

        Schon mal Danke für die Hilfe im Vorraus

        R 1 Reply Last reply Reply Quote 0
        • R
          romestylez @Boronsbruder last edited by romestylez

          @boronsbruder ich habe das gleiche Problem und es auch bei GitHub gemeldet. Leider scheint @greyhound aber nicht mehr aktiv zu sein hier.

          Ich würde vermuten das Husqvarna etwas an der API geändert hat (Authentifizierung oder URL). Ich habe schon etwas im Sourcecode geschaut und versucht mit Postman die HTTP Requests vom Adapter nachzubauen aber keine Chance bzw. ich hatte auch nicht wirklich Zeit.

          Wir müssen hier also beten das sich jemand hinsetzt und das Ding irgendwie fixxt.

          R 1 Reply Last reply Reply Quote 0
          • R
            reutli @romestylez last edited by

            @romestylez Habe greyhound per mail kontaktiert, bisher ohne Antwort. War absehbar, dass die alte API von Husqvarna stirbt... Die neue liefert aber nur deutlich weniger (hatte mal begonnen stümperhaft einen Adapter anzufangen).
            Wenn die alte also nicht nur geändert wurde, sondern tot ist, dass muss ein neuer Adapter her. Schade.

            Vielleicht meldet sich @greyhound aber ja noch...

            R 1 Reply Last reply Reply Quote 0
            • R
              romestylez @reutli last edited by

              @reutli ich schaue mal ob ich nicht was aus der normalen Husqvarna App etwas sniffen kann was man benutzten könnte.

              Wäre auf jeden Fall schade. Verstehe es auch nicht wieso man eine API hat diese abschaltet und dann eine weniger umfangreiche rausbringt. Aber gut so ist das halt manchmal.

              Boronsbruder 1 Reply Last reply Reply Quote 0
              • Boronsbruder
                Boronsbruder @romestylez last edited by Boronsbruder

                Was soll eigentlich in der neuen API fehlen?

                Ich finde jetzt nichts, was nicht mindest den Umfang des alten Adapters abdecken könnte. (siehe hier -> Husqvarna Rest Api Doku)
                Man könnte sogar die Einsatzzeiten, Lichter und Mähhöhe verstellen.

                Wenn ich das (mit meinem Laien-Wissen) richtig sehe läuft "nur" die Authentifizierung anders.

                Es werden nun Anfragen, per App-Key limitiert, was heissen würde, dass jeder Adapternutzer einen Account anlegen müsste und einen App-Key holen.

                Oder sehe ich das falsch?

                Im Moment kann leider keinen App-Key beantragen, da anscheinend "Maintenance" ist.

                R 1 Reply Last reply Reply Quote 1
                • R
                  reutli @Boronsbruder last edited by reutli

                  @boronsbruder : Da fehlen (zumindest war es letztes Jahr noch so) z.B. Geo-Daten. Ansonsten habe ich auch reingeschaut und war erstaunt, dass es einiges mehr gibt als 2021.

                  Edit: Geo-Daten sind jetzt auch da... hab' gelogen 🤥

                  Hatte übrigens Kontakt zu @greyhound ... er hat einiges um die Ohren und will sich gegen Ostern um die Thematik kümmern, weil er auch sein mower an den Start bringen will/muss.

                  Ich habe meine Adapterversuche seinerzeit eingestellt, genau wegen der Authentifizierungsthematik und möchte mich (ebenfalls als JavaScript-Anfänger) hier nicht auf's Glatteis begeben, zumal es ja bereits diesen Adapter hier gibt.

                  Soweit ich weiss hat @greyhound ohnehin schon an der neuen API gearbeitet, so dass es vielleicht Ostern was werden könnte.
                  Wenn alle Stricke reissen, hole ich meinen Code nochmals hoch...

                  Boronsbruder 1 Reply Last reply Reply Quote 1
                  • Boronsbruder
                    Boronsbruder @reutli last edited by Boronsbruder

                    @reutli Das hört sich ja mal positiv an!
                    @greyhound: Ich stehe auf jeden Fall als Tester egal, ob Alpha oder Beta zur Verfügung!

                    1 Reply Last reply Reply Quote 1
                    • A
                      andrebu last edited by

                      Ich hoffe auch das sich jemand findet der den Adapter weiter entwickelt oder @greyhound weiter macht. Sitze gerade an einem Blockly damit der Mower die Beregnung steuern kann.

                      H 1 Reply Last reply Reply Quote 0
                      • H
                        h4m4 @andrebu last edited by h4m4

                        Hat jemand diese Adapter mal ausprobiert?
                        https://github.com/ice987987/ioBroker.husqvarna-automower

                        R Boronsbruder M 4 Replies Last reply Reply Quote 0
                        • R
                          reutli @h4m4 last edited by

                          @h4m4 Nein, aber Code sieht ähnlich dem aus aus, den ich gerade bearbeite 🤠
                          Holt die Daten dann über Web-Socket...das mach ich nicht so. Wenn der funktioniert, stelle ich meine Arbeit ein - warte ohnehin auf @greyhound , der an Ostern die Mower in Betrieb nehmen wollte und sich dann den Adapter anschaut.
                          Ich spiele auch nur rum... 😧

                          1 Reply Last reply Reply Quote 0
                          • Boronsbruder
                            Boronsbruder @h4m4 last edited by Boronsbruder

                            @reutli
                            der Vorteil am Websocket ist, dass man nicht pullen muss, sondern Änderungen gepusht werden und die Aktualisierungen nicht begrenzt sind.
                            Die 10000 APi-Anfragen pro Monat sind dann frei für Kommandos.

                            R 1 Reply Last reply Reply Quote 0
                            • R
                              reutli @Boronsbruder last edited by

                              @boronsbruder Wieder was gelernt - danke.
                              Will am WE auch Mäher in Betrieb nehmen (wenn dann die Kabel repariert sind).
                              Dann schaue ich mir den Adapter im Testsystem mal an.

                              1 Reply Last reply Reply Quote 0
                              • M
                                MatthiasUlrich @h4m4 last edited by MatthiasUlrich

                                @h4m4 Die Verbindung ist bei mir scheinbar da, aber die Objekte werden nicht geladen.

                                Aber laut GitHub wird daran gearbeitet. Ich lass ihn mal laufen, vielleicht passiert ja noch was.
                                086d718d-59c6-4954-aebf-59d2bc74709b-grafik.png

                                Boronsbruder 1 Reply Last reply Reply Quote 0
                                • Boronsbruder
                                  Boronsbruder @MatthiasUlrich last edited by Boronsbruder

                                  @matthiasulrich

                                  Was sagt das log?

                                  Edit:
                                  du hast ja noch den Original...

                                  Da wird nix kommen, da die Adresse der Alten-API die Anfrage nach Daten ablehnt...

                                  M 1 Reply Last reply Reply Quote 0
                                  • M
                                    MatthiasUlrich @Boronsbruder last edited by

                                    @boronsbruder Ein Issue ist erstellt inkl. log. Ich bin mit ice987 in Kontakt dazu.

                                    I Boronsbruder 2 Replies Last reply Reply Quote 0
                                    • I
                                      intruder7 @MatthiasUlrich last edited by

                                      @matthiasulrich war doof dass du den Issue zu gemacht hast.... hatte noch kommentiert

                                      M 1 Reply Last reply Reply Quote 0
                                      • M
                                        MatthiasUlrich @intruder7 last edited by

                                        @intruder7 Ich musste schnell reagieren, da ich versehentlich im Log pers. Daten hatte.

                                        I 1 Reply Last reply Reply Quote 0
                                        • I
                                          intruder7 @MatthiasUlrich last edited by

                                          @matthiasulrich hatte ich gesehen 😉

                                          1 Reply Last reply Reply Quote 0
                                          • Boronsbruder
                                            Boronsbruder @MatthiasUlrich last edited by Boronsbruder

                                            @matthiasulrich

                                            Aber die Verbindung zwischen deiner App / Appkey zu den APIs hast du aber schon im Developerportal angelegt?

                                            Hatte ich nämlich bei meinen eigenen Skript-Versuchen auch vergessen...

                                            M 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            525
                                            Online

                                            31.6k
                                            Users

                                            79.5k
                                            Topics

                                            1.3m
                                            Posts

                                            automower husqvarna
                                            72
                                            435
                                            78031
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo