Closed tobihoby closed 8 months ago
No specific mowers are "supported" - its a generic interface to the cloud. Dunno what mowers are actually compatible.
Unfortunately, I have significant problems with the mentioned mower under this plugin. Only the on/off switch works, other switches and sensors do not work at all. In addition, the plug slowed down the entire Homebridge. I have now uninstalled the plugin and everything is working fine again. Does anyone else have a Vision model in use and can confirm the problems?
Maybe check over at the iobroker project where the connector code is from. It should be as compatible as the iobroker plugin is.
many adjustments for vision since version 2.2.0
Are you using the latest code in the plugin?
I see. I seem to have some trouble getting the latest versions of their code to run on my raspi, theres new native dependencies in the iobroker plugin that won't compile, it complains about some aws natives missing, thats annoying.. I'll have to find out whats the deal there before I can push an update with their latest changes.
OK thank you
@tobihoby I published a test version with the next
tag, i.e. you can install it with npm install -g homebridge-landroid@next
to try if it works for you. Might be the natives issue is just due to my dev computer using a 64bit kernel..
After the installation, which also worked correctly, I can't find any entries for the plugin in the config.json and also no Landroid plugin under plugins. I restarted the hombridge.
@normen can you please help me again?
Can you post an error log? I don't understand why installing the plugin would remove anything from your config.json
?
I have now come a step further and have installed the "next" version via the GUI, this version was not displayed to me via the CLI.
However, two mowers are now being created for me in the hombridge.
What is MQTT for an object? I can't remove this either.
[12.8.2023, 07:27:16] [homebridge-landroid] Restarting child bridge... [12.8.2023, 07:27:16] Got SIGTERM, shutting down child bridge process... [12.8.2023, 07:27:21] [homebridge-landroid] Child bridge process ended [12.8.2023, 07:27:21] [homebridge-landroid] Process Ended. Code: 143, Signal: null [12.8.2023, 07:27:28] [homebridge-landroid] Restarting Process... [12.8.2023, 07:27:29] [homebridge-landroid] Launched child bridge with PID 1786025 [12.8.2023, 07:27:30] Registering platform 'homebridge-landroid.Landroid' [12.8.2023, 07:27:30] [homebridge-landroid] Loaded homebridge-landroid v0.12.0 child bridge successfully [12.8.2023, 07:27:30] Loaded 2 cached accessories from cachedAccessories.0E5689E895F9. [12.8.2023, 07:27:30] [homebridge-landroid] Restoring Landroid Landroid Scooter from HomeKit [12.8.2023, 07:27:30] [homebridge-landroid] Fallback for On/Off switch [12.8.2023, 07:27:30] [homebridge-landroid] Restoring Landroid Landroid [object Object] from HomeKit [12.8.2023, 07:27:30] [homebridge-landroid] Fallback for On/Off switch [12.8.2023, 07:27:30] [homebridge-landroid] This plugin generated a warning from the characteristic 'Name': characteristic value expected string and received object. See https://homebridge.io/w/JtMGR for more info. [12.8.2023, 07:27:30] [homebridge-landroid] DidFinishLaunching [12.8.2023, 07:27:30] [homebridge-landroid] Login to worx [12.8.2023, 07:27:30] Homebridge v1.6.1 (HAP v0.11.1) (homebridge-landroid) is running on port 59237. [12.8.2023, 07:27:31] [homebridge-landroid] Connected to worx server [12.8.2023, 07:27:31] [homebridge-landroid] Found 1 devices [12.8.2023, 07:27:31] [homebridge-landroid] Found device Scooter with id 2023xxxxxxxxxxxxxxx [12.8.2023, 07:27:31] [homebridge-landroid] Please wait a few minutes.... clean old version [12.8.2023, 07:27:31] [homebridge-landroid] Done with cleaning [12.8.2023, 07:27:31] [homebridge-landroid] Found Landroid in Worx Cloud with name: Scooter [12.8.2023, 07:27:31] [homebridge-landroid] OneTimeShedule found, create states... [12.8.2023, 07:27:31] [homebridge-landroid] Firmware found, create states... [12.8.2023, 07:27:31] [homebridge-landroid] PartyModus found, create states... [12.8.2023, 07:27:31] [homebridge-landroid] Paused found, create states... [12.8.2023, 07:27:32] [homebridge-landroid] Create folder activityLog and set states. [12.8.2023, 07:27:32] [homebridge-landroid] Create product folder and states for WR206E [12.8.2023, 07:27:32] [homebridge-landroid] Found Landroid in Worx Cloud with name: [object Object] [12.8.2023, 07:27:32] [homebridge-landroid] Start MQTT connection Warning: Signed custom authorizers with signature will not work without a token key name and token value. Your connection may be rejected/stalled on the IoT Core side due to this. Please set the token key name and token value to connect to a signed custom authorizer. [12.8.2023, 07:27:33] [homebridge-landroid] MQTT connected to: iot.eu-west-1.worxlandroid.com [12.8.2023, 07:27:33] [homebridge-landroid] Request Counter: 1
Hm, okay... Seems like the detection goes wrong and it tries to register a MQTT command as a mower. But apart from that your mower is working?
unfortunately not. But I suspect that it is because of the false detection you mentioned.
Nah, it found your mower: "Found Landroid in Worx Cloud with name: Scooter" How does the log look when you send commands to the mower?
the faulty MQTT mower shows the current status. The right mower by name has no status
Uh, can you post that log when you press the HomeKit buttons of each mower? Its kinda hard pulling every answer out of your nose, I neither have a Vision mower nor do I know how your setup looks. Also please enable debug mode for more log output.
you should be able to see everything here.
Not really but I pushed a version that avoids adding the Object mower, maybe that puts the buttons and mowers together correctly.
Thank you for that, but unfortunately it's the same as before.
It still shows the Object mower?
yes, exactly
is there anything new about my problem?
Does this work with the latest version?
I can see the correct mower now, looks much better than before. But I still get the following message in the log:
Warning: Signed custom authorizers with signature will not work without a token key name and token value. Your connection may be rejected/stalled on the IoT Core side due to this. Please set the token key name and token value to connect to a signed custom authorizer.
Is there anything new about this error?
No, this project is discontinued. Check the front page.
Hi,
does the plugin supports the new vision versions? Power status is OK, but partymode and battery level are broken.
Thanks
Tobi