awnet_local_data_<mac_address> as file name can't copy in Windows #26
Labels
bug
Something isn't working
Comments
|
This is a legitimate usage that I simply had not thought of. Will work the fix into the next release. Thanks! |
Merged
tlskinneriv
added a commit
that referenced
this issue
Jun 17, 2023
Fixed: - Storage key for data to valid Windows file path, migration on first run, resolves [#26](#26) - Last Rain sensor now behaving correctly, was previously updating to "Unknown" when it had no data, resolves [#28](#28) - Keys for lightning data storage are converted to strings by the storage provider, perform conversions when data is accessed, resolves [#29](#29)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Integration Version:
v1.1.1
Home Assistant Version:
2023.5.4
Describe the bug
A clear and concise description of what the bug is.
The integration creates a file in the .storage directory whose filename is incompatible with the Windows filesystem due to use of colons ( : ) in the filename. This prevents copying of this file using Windows as a mechanism for directly copying this file for backups and other purposes.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Expected behavior is the ability to use Samba and other methods to copy the file using Windows
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Debug log output from the integration (see Home Assistant docs for how to enable debug logging for an integration; integration name: "custom_components.awnet_local")
The text was updated successfully, but these errors were encountered: