Thanks for looking into my issue!
For now I’m happy that I managed to get WebDAV working, so I can start using the archive again.
But, just as you say, most people probably are not even aware of FTPS vs. SFTP, so maybe in your next release you could just make it more clear that it is FTPS that is supported.
Thanks for you help, and for keeping this great app available for all of us!
I checked the connect with drivehq (free account) and it is working over port 21, it does not work over port 990. In the Homey app you can use both FTP or SFTP (in reality FTPS). So, my conclusion is that FTPS with drivehq (free account) only works in the explicit mode. In explicit mode, an FTPS client “explicitly request” security from an FTPS server and then step up to a mutually agreed encryption method.
When I export my logic, the file name contains the variable ID. Is it possible to add the variable name I gave it? For example, my file name is: variable-1ec0a59e-9451-4263-96e5-6a67fcf16442.csv
Since I have a lot of variables, I can’t distinguish them.
I am able to back-up the data (NICE) and was wondering what you guys are doing with this data… store it for ever or … This is where I am thinking of to use it:
I just installed this app and use it with SMB. It works, i doe get a zip file with the csv files etc…
But when i make an updat of the app Zonnepanelen and i say backup Yesterday.
Then i get a csv file that starts at 02-07-2021 22:00 and it stops at 03-07-2021 21:55.
Is there something wrong? When a flow should start at 14:00 it is starting at 14:00. So the time is right.
And when i open the csv file i get solar power at 3:40. So the time is way of. It should be around 5:40. So there is also 2 hours difference.
Can i do something about that?
Hi Mike. Great you are using the app!
No, there is nothing wrong. Since Homey is used worldwide, the time is measured in UTC or ‘Zulu time’. Hence the ‘z’ at the end of the time code.
So when you live in the Netherlands, yesterday started at 22.00z and ends at 22.00z.
See the actual UTC time here: https://zulutime.net
Thank you. Now I know that there is nothing wrong I can try to change the time with
a macro or something like that.
New version v2.9.0 has been released. In general it improves stability and compatibility.
Is there an update ongoing for app Archive Insights to support SMB NTLMv2?
Since Synology DSM 7.0 Beta, NTLMv1 is disabled, which means that SMB does not work to use in Archive Insights to store the backup to a Synology NAS disk.
Saw this in the log file on my Synology “User [username] from [192.168.1.12] failed to log in via [SMB] due to [NTLMv1 not permitted].” when I tested.
I found this information on Synology’s website “NTLMv1 is disabled since DSM 7.0 Beta for security concerns, and only NTLMv2 is supported by default.”
You should not try to change the times in the database, UTC is a common way to store date/time independent of location. What you need to do is to find a way to explain to the tools that use it to display it formatted for your timezone. That is because if you live in an area that has daylight savings, the difference is not always 2 hours.
I am not aware of this issue. I have posted an issue with the developer of the SMB package that I use. Please see this link and add any info that could help the dev:
Indeed. Took me a while to find this one. First, I notices that there were no exports anymore. I checked SAMBAS setting. The Error in the homey app says: “Error: STATUS_LOGON_FAILURE (0xC0000006d) : the attempted logon is invalid. this is either due to a bad username or authentication information”.
Thanks to Edwin_D I looked at the Synology DSM logs: “User [Myhomey] from [192.168.0.119] failed to log in via [SMB] due to [NTLMv1 not permitted].”
I now switched to ftp, because the port is closed for external use, but I prefer to use SAMBA instead.
I might have to switch to some other SMB package all together. The devs stopped supporting the one I’m using now. But it seems a good SMB library is very hard to find. I will definitely try some though. Will take some time because the packages are all not compatible so it involves quite some rewriting of code.
No prob. FTP works fine I see.
Hello, great App!!
I encountered a problem. I want to export Plugwise data from last year but my Homey reboots everytime. Strange because with other exports it works fine. It can’t be the volume i think.
What can be the problem, for example data last month works fine.
Thanx
Riny
v2.9.1 is pending approval.
First let me thank you for creating this app. Very useful tool to have.
I have a question, though. It appears that the resolution of the data is heavily decreased if exporting for a larger time interval. Is that because Homey only stores a low resolution (e.g 1 hour sample time) version of the data as it gets older? I would assume that is the case, just wanted to check.
Yes, that is indeed what Homey is doing. This is a know strategy for time series databases to ‘compress’ the data by resampling to a lower resolution. It ensures that the insights data never grow bigger then what Homey can handle. Before Athom introduced this strategy the Insights database was growing out of control rapidly.
So if you need high resolution insights you need to export more often (every day or even every hour). If you need the highest possible resolution you need to set up your own database somewhere and use a real time exporter (influxdb, prometheus or mqtt hub)
Ok, thanks. As I guessed, then. Makes sense too, since (as you said) the data would quickly grow very large if they didn’t do that.
Thank you for a very useful app!
I have 2 questions. The first one is related to the question asked above - resolution of the data. At the moment I am mainly interested in exporting the room temperature data from my thermostats. When I export the data for the past hour, I get readings every 5 seconds even though the thermostats report only every 5 minutes. Is there anything I can do about it or is the only solutuon to export every 7 days for example?
My second question is about the data export format. I have an app which lets me set and read the temperature from my floor heating thermostats. I have 11 thermostats and when I export the data, I end up with 11 folders with couple of .json and .csv files. Is there any way to choose what data I want exported? For example only measured temperature and no target temperature? It would also make it easier to get all the files of interest in one folder but at the same time it is not that much work to move them once a week.
Anyway, thank you for the app once again!
