Here are some sreenshots:
I am trying to connect to my NAS (Synology with DSM 7), but keep on getting an âError: Abortedâ message after some time after which the app crashes. The log indicates an ERR_OSSL_EVP_UNSUPPORTED error occured.
Any ideas how to proceed?
I double checked the share, sub folder, domain, username/password entries, but they are correct.
Seems openssl issue
Thanks. Does this mean that the Archive Insights app needs updating under the hood?
the node version of HP2016/2019 at least needs to be upgraded. It now doesnt match the node version of HP2024. That requires a Homey fw upgrade.
I am using a Homey Pro 2023. Does it also require a firmware update by Athom for the Archive Insights app to work?
My apologies if I am asking the obvious. I am new to Homey Pro and donât have in depth knowledge on the inner workings of the apps that run on Homey or its platform. 
Apps need to be able to run on all Homeyâs out there. But since HP2016/2019 have a different node version from HP2023, I am forced to make a choice for Archive Insights. Now it only runs on the older platforms because most existing users will not have a HP2023.
If everyone would ask Athom to give priority to have all Homey versions use the same active Node version, it would make a solution possible for this app (and some others too)
Ah that clarifies things. I understand where you are coming from. For now I am using the FTP option to save exports on the FTP server of the Micro Web Server app, which works. Thanks for your quick response and efforts in developing this app!
my homey is contstantly crashing and rebooting when using the export.
im trying to get my history out of homey but still with no luck .
what can i do about this. i know its a big chunk of data to export.
I was glad I found this add-on, but was soon disappointed: No matter what I do, this CRAPPY thing is unable to open the network share.
The share is on an Ubuntu Server, samba server has min server and min client = NT1, so it should even woirk with crappy old shit protocol. Basically any device is able to access the share, except Archive Insights.
Error: Error: STATUS_LOGON_FAILURE (0xC000006D) : The attempted logon is invalid.
Yea, invalid ⊠right. username okay, password okay, address correct.
Please fix this or withdraw app. Thank you!
If you do not like the app - no one forces you to use it.
Please, this is exactly why community devs give up on supporting ( & building ) apps.
Is it so hard to just kindly report your issue(s) to see who might help?
The app store is full of other apps which really donât work or are abandoned; youâd address your findings to the app store owner, homey.app/support.
I see your point, BUT: it is not acceptable if there are numerous complaints about the same error days, weeks and months ago and this is not fixed. Sorry, but from git chat it is apparent that the error has been discussed and looked into and hasnât been fixed. It canât be a huge error since this is basic stuff like connecting to a samba share.
Itâs not the first time I install a community addon that is lacking basic functions or is totally buggy. If this is the case, then at least mark it as âbetaâ or âincompleteâ. I donât mind if such an addon lack functions, thatâs okay since itâs developed by people in their free time. But I think one can expect that rudimentary functions should work.
Sincerely
Nils
After going through all the post here, hoping to find a solution, I need some dedicated help I guess. None of the methods I try to export to my Synology NAS work.
- SMB (using âsmb://192.168.2.34/DataWarehouseâ) gives me the error âError: [object Object]â and crashes the app (and, yes with the â/â ok, username & password entered, etc,).
- WebDAV (using âhttps://192.168.2.34/DataWarehouseâ or âhttps://192.168.2.34:5006/DataWarehouseâ) gives me either âError: Invalid response: 405 Not Allowedâ, or âError: Invalid response: 404 Not Foundâ, or âError: certificate has expiredâ.
- For FTP I seemed to not get the right address syntax, all result in âError: getaddrinfo ENOTFOUND 192.168.2.34/DataWarehouse (control socket)â. I tried all permutations of the address, including port number, protocol (ftp or https).
I clearly need some help here and that would be greatly appreciated.
Wilko
I use HomeyPro, with the Homey App on Android. I try to connect Exporteer to my NAS, and whatever I try it is not working.
Usually it gives the pop-op: Error [object Object]; then the app crashes and has to be started again.
I tried everything:
- HomeyPro on Wifi or via Ethernet cable
- NAS in LAN switch or in smaller hub
- smb:// before the name or not.
- UPPERCASE or lowercase server name
- Domain like NAS or like PC or none
Whatever I try I get the same response.
Who can help me further on this?
Regards.
If you canât get the NAS settings to work in the app, you might want to try the FTP option. Typically you can enable an FTP server on the NAS to which you can export the insights to.
NAS (SMB) doesnât work indeed.
What do the logs say?
My guess the SMB version used by the app needs an update.
Tests
- (Very) old NAS: it just times out (itâs SMB version is too old)
- New-ish up-to-date Synology NAS: all kinds of errors (âinvalid folderâ or âobject objectâ, the app quits after every âtest connectionâ action.
Logs:
.
The FTP connection as mentioned by @SunBeech works fine. Pay attention to where to (not) put slashes:
Completely rewritten version 5.0.0 is ready for testing:
- Added SMB NTLMv2 support
- Added SFTP support
- Fix FTPS support and allow implicit FTPS on port 990
- Many stability and resource usage improvements
- Better looking settings page
- Code refactoring
- Updated dependencies
- Translations for all Homey supported languages
- Homey api@3.18.1
This is a major rewrite. It was EXTREMELY difficult to get SMB to work with modern network share servers, but in the end I did manage to do it 
Secondly, I was able to add SFTP support, which is the standard for FTP nowadays.
Thirdly the code was made much more robust and less greedy for resources (memory and CPU), so it should run stable in (almost) all Homeyâs (I hope, please provide feedback)
Please test, and let me know if you like my efforts !
Thatâs faster than fast, Robin!
SMB:
- Synology NAS: SMB v
4.15.9-0644, fixed! It now works. - Very Old NAS: SMB v
3.5.0(2010
), it doesnât work, but probably itâs safer if it just doesnât work.
FTP:
- Synology: still works
- Very Old NAS: still works
FTPS:
- Synology: works
SFTP:
- Synology: works
Findings:
I noticed the file timestamps are 2h ahead
(NL based, +02:00 GMT);
Filenames reflect correct UTC time
Logs show correct UTC time:
Thx for the extensive testing and feedback!
