Multiple parsing errors Unexpected token < in JSON at position 0 with plugin v0.1.5 and Valetudo re v.0.10.5

[xorguy]

Hi.

Installed just released v0.1.5 with legacy mode set to true with Valetudo RE 0.10.5 and same errors appears.

`[3/4/2021, 5:10:31 PM] [ValetudoXiaomiVacuum] Error parsing firmware info: SyntaxError: Unexpected token < in JSON at position 0

[3/4/2021, 5:10:31 PM] [ValetudoXiaomiVacuum] Error parsing firmware info: SyntaxError: Unexpected token < in JSON at position 0

[3/4/2021, 5:10:36 PM] [homebridge-valetudo-xiaomi-vacuum] This plugin slows down Homebridge. The read handler for the characteristic 'On' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.

[3/4/2021, 5:10:36 PM] [homebridge-valetudo-xiaomi-vacuum] This plugin slows down Homebridge. The read handler for the characteristic 'On' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.

[3/4/2021, 5:10:36 PM] [homebridge-valetudo-xiaomi-vacuum] This plugin slows down Homebridge. The read handler for the characteristic 'On' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.

[3/4/2021, 5:10:36 PM] [homebridge-valetudo-xiaomi-vacuum] This plugin slows down Homebridge. The read handler for the characteristic 'Status Low Battery' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.

[3/4/2021, 5:10:36 PM] [homebridge-valetudo-xiaomi-vacuum] This plugin slows down Homebridge. The read handler for the characteristic 'Battery Level' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.

[3/4/2021, 5:10:36 PM] [homebridge-valetudo-xiaomi-vacuum] This plugin slows down Homebridge. The read handler for the characteristic 'Charging State' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.

[3/4/2021, 5:10:42 PM] [ValetudoXiaomiVacuum] Error parsing firmware info: SyntaxError: Unexpected token < in JSON at position 0

[3/4/2021, 5:10:42 PM] [ValetudoXiaomiVacuum] Failed to get volume: SyntaxError: Unexpected token < in JSON at position 0

[3/4/2021, 5:10:42 PM] [ValetudoXiaomiVacuum] Failed to get volume for Mute: SyntaxError: Unexpected token < in JSON at
position 0`

[T-Bone90]

The same... :-(

[onfoot]

All right, that was a disaster, sorry. I underestimated the api changes in RE, which I'm currently running. Let's see how it goes with 0.1.6. Seems to work fine with almost all characteristics, that is speeds, battery status (percentage and charging state). Haven't yet checked the cleaning, because I shouldn't make much noise at the moment. ;)

[T-Bone90]

Works better but I get [4.3.2021, 22:06:51] [homebridge-valetudo-xiaomi-vacuum] This plugin generated a warning from the characteristic 'Battery Level': characteristic value expected number and received undefined. See https://git.io/JtMGR for more info. in Homebridge.

[xorguy]

With 0.1.6 no more unexpected tokens, only the same warning as @T-Bone90 mentioned.
[3/4/2021, 11:49:22 PM] [homebridge-valetudo-xiaomi-vacuum] This plugin generated a warning from the characteristic 'Battery Level': characteristic value expected number and received undefined. See https://git.io/JtMGR for more info.
Thanks!

[onfoot]

What version of node and homebridge are you guys running? I fixed the battery level issue in 0.1.7, but the thing is, I'm not getting those errors at all when running. And homebridge is running in debug mode.

[xorguy]

I'm running Homebridge in Docker, no debug mode, and node version is v14.16.0
Updating to plugin version 0.1.7 and the same warning for Battery Level is shown.

[T-Bone90]

Same Error in 0.1.7, every few seconds

[T-Bone90]

It doesn't work that well either. I started the vacuum cleaner with a button on the vacuum cleaner, but I didn't flip a switch in homekit. Only at some point did it start when the cleaning was almost over.
(Sorry fort the bad English ;) )

[onfoot]

Sure, I have to do more testing with the vacuum actually running - we'll get there eventually. ;)

[T-Bone90]

0.1.8 at the moment no errors! Except the above little problem with Homekit.

[xorguy]

Updated to 0.1.8 and no warnings so far. Thanks!
Hope Homekit integration gets better over time.

[onfoot]

The issue with the vacuum's state not being up-to-date may be due to the time interval it uses between status checks when the device is idle. If the time is not yet up, it uses the locally cached status instead of reading it from the device. I'll fix that so that regular checks will happen as usual, but when the phone wants the current status when one's entering the Home app, it will hopefully get a more up-to-date one.

[T-Bone90]

With 0.1.8
[7.3.2021, 03:35:16] [ValetudoXiaomiVacuum] Error parsing current status info: Error: connect ECONNREFUSED 192.168.255.20:80

[onfoot]

That's not something I can fix unfortunately - the connection was refused, so either valetudo died on your vacuum or maybe you have some kind of an IP conflict so another device sits on 192.168.255.20.

[T-Bone90]

Ah ok sorry. No I have no ip conflict. who knows... :-)