copystring
[BUG] Unsupported features / Restart Loop
Bug Description
Hi. I would like to reopen / relate to #793 I have managed to change my IP.
0.6.18 is now working in general, so probably IP not blocked; but still throws some errors (including errors that may relate to https://github.com/copystring/ioBroker.roborock/issues/791 which is already fixed? ) 0.6.19 on the other hand still runs into a instance restart loop and additional robot specific errors.
I have attached the logs. In general I have 4 robots, not 100% sure which errors relate to which (a21 = Q5 Pro?) Below you can see a screenshot of the robots and the related robot version
Steps to Reproduce
Installation of 0.6.18 resp. 0.6.19
Expected Behavior
no errors
Debug Log
Adapter Version
0.6.18 / 0.6.19
JS-Controller Version
7.0.6
Node.js Version
20.19.0
Operating System
Pi OS
Additional Context
Please don't use 0.6.19 or your IP will be banned again. Use the dev or 0.6.18. I'll check your logs later today.
Thanks a lot for your help.
Just for my understanding, maybe I have misunderstood this.
I have installed the "0.6.19" with this path here, I though this is actually the 0.6.19 version, because it shows 0.6.19 also in the adapterinfo then. Or is this actually the dev version, because I used the correct path? Or do I need to use another path? So if this is really the dev version, the log above called 0.6.19 is actually the log from the dev version.
OK then the errors mentioned in the log file called 0.6.19 are actually errors in the dev version
Please test the new dev. I started processing automatic creation of objects when missing. This makes object creation dynamic regardless of robot model automatically, supporting most of the features of future unreleased robots.
Hi. Thanks for the new version.
I did a fresh install. Unfortunately still a lot of warnings and infos. Also 1 restart loop and the object tree is not getting complete (e.g. folder commands completely missing for all 4 robots, so cant control robots).
Attached is the log.
I went back to 0.6.18 because after the IP blockade the version “0.6.19 dev” caused a lot of errors and the adapter was only green for a very short time.
With version 0.6.18 I only have the warning: 2025-04-24 17:47:15.607 - warn: roborock.0 (365343) State "roborock.0.Devices.1aX0gpfJ2s7Qsabd3vbE5P.deviceStatus.carpet_clean_mode" has no existing object, this might lead to an error in future versions
Here is the debug log: iobroker.2025-04-24.log
@TimoGoerlich yes, this was a basic test. I've completed most, if not all, code for dynamic object created mostly independent of robot model. Would you try the new dev?
Thanks again. Seems to run stable at first look, only a few warnings and infos left. Attached is the log. I will observe over next days if everything runs smooth.
One more warning, I noticed that the commands are read-only (can adjust them in advanced mode, but always get this warning):
I installed the latest dev version and only got a warning.
roborock.0 | 2025-04-27 11:47:23.074 | warn | State "roborock.0.Devices.1aX0gpfJ2s7Qsabd3vbE5P.deviceStatus.carpet_mode" has no existing object, this might lead to an error in future versions
Many thanks for your work.
Thanks for testing. The latest dev should have all the fixes you reported. https://github.com/copystring/ioBroker.roborock/tree/dev
Initially looks good. No more warnings. I will test/observe the next couple of days and will report if I find something.
Just dropped message before and now I have a warning ;-(
May this relate to missing WLAN connection though? This robot has a very bad WLAN connection I think due to positioning in my house, so may be the reason for timeout? Sometimes its changing the repeater in my Mesh and then shortly it looses connection I guess. I have seen this in older versions occasionally already
Hmmm. Seems to be not only one affected robot, see attached log. I can reach them via the app, so not sure its a connection issue
I have had a look, but need to test this first. I'll let you know when I got something.
If you like, you can test the new dev, however there is no fix, only improved error logging.
Yes, it looks the same for me. I'll have to find some time to fix this. I will get back to you once I figured out what's wrong.
Please try the new dev https://github.com/copystring/ioBroker.roborock/tree/dev. This has been running quite good for the past days. Let me know how it works out for you.
Unfortunately still some errors, but it seems less
What do you mean by errors? Some warnings are visible in the log, but not errors. The warnings are timeouts when the vacuum didn't respond to the request. Most likely out of my control.
Yes, seems to work. I only regularily get following warnings (as seen in previous log), but as you mention this may be due to connection issues
mhhh now i restarted the adapter to change log level, now I received this:
Please try the new https://github.com/copystring/ioBroker.roborock/tree/dev. I have optimized the order of requests, so most timeouts would be fixed. Occasional timeouts might still happen if the robot does not respond.