Closed donburch888 closed 11 months ago
Yes, the scan surely worked, but there is an issue with the write.
It is not clear how tempfile comes into play.
The '/config/scans' directory should be created if it is missing, you can check if it does, and if not create it manually. This is the code that normally does that:
I'll try to reproduce this later, but in the mean time you may be able to get some more info.
I looked with the File Editor add-on, and indeed there is no /config/scans directory - I have created it now. Curiously I see there is also a /config/csv directory (which I don't recall creating), containing /config/csv/test1.
Just tried all_routes_and_neighbours, but this time with the ieee of my coordinator ... and it takes a while but does display a result, so my issue is solved. Thank you.
Now to compare this result with the visualisation.
It is not clear how tempfile comes into play.
From the second error message including my PCs IP and browser type, my guess is that a generic component is used to display a JSON file in a human-readable format.
Oops, used the [Comment] instead of the [Close with comment] button. Thank you
Good new. The csv directory is created with certain commands, normally when you define csvout in the parameters. This is available with the attr_read and attr_write commands for instance. I use it in some scripts to maintain a history of changes and values read (in a CSV file) and some other use cases.
I'm setting up my zigbee mesh again from scratch, and trying to understand LQI, unavailablity and the Visualisation.
This was happening with Home Assistant 2023.7 and zha_toolkit version v0.9.7; and also now with HA 2023.8.
Calling zha_toolkit’s all_routes_and_neighbours but without data
results in two errors:
and
The section from the full log shows:
The massively long DEBUG line between the error messages appears to contain all the network data, so I think the service call worked without any data parameters - it just didn't get saved to temp file, and so couldn't be displayed.