[quote=“amg0, post:565, topic:185570”][quote=“tomtcom, post:560, topic:185570”][quote=“amg0”][quote=“tomtcom, post:557, topic:185570”][quote=“amg0, post:554, topic:185570”]V 0.56.364
[ul][li]Scene History dialog ( since lua log restarted )[/li]
[li]Device Variable History ( since lua log restarted )[/li][/ul]
You press the little calendar button ( respectively in device variable dialog box for variable, or in scene dashboard panel ) and it will show you the history that it has found in the log
This feature will never replace database-based solution like DataMine/DataYours etc but it gives the history it finds in the lua logs for you, so let’s call it “recent history” since the last reboot or last log rotation
NOTE: I assume logs are on the vera box in /var/log/cmh but if some of you use logs on USB, please help me here by telling me the absolute file path where log can be read, I can then maybe do something equivalent for people putting logs on external storage/usb.
Install by autoupdate or with magic url : ?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=CreatePlugin&PluginNum=8246&Version=28028[/quote]
Hey amg0, auto update is reverting me back to .313. This is partly from my earlier post. I hit the update, confirm, after a while I reload the page and back to .313. The magic url will work fine and I’ll do that now but I’m not sure how to troubleshoot.
Also, from the prior version, I couldn’t get the mobile page to update past .313 either even after cache cleaning on Chrome for Android.
Any suggestions?[/quote]
Do you do local access or remote ? It seems I have issues with remote I may have to reduce auto update to local access[/quote]
I tried both a couple times so I couldn’t recall the order of which I did it.[/quote]
ok, I looked into this and I believe the problem is with remote access.
in order to know if there is a newer version, ALTUI makes an ajax call to read HTTP( or HTTPS ) //code.mios.com/svn_public/mios_alternate_ui/lastver.txt using JSONP standard to overcome the same domain origin restrictions imposed by browsers.
code.mios.com is a convenient server for me as I can update files easily and fast whenever I need and it should work in httpS mode without problem. in remote access, everything happens in HTTPS, all seems to work perfectly but when ALTUI tries to access https//code.mios.com/svn_public/mios_alternate_ui/lastver.txt , and this time it fails because of a certificate naming issue. the certificate does not seem to be aligned with the name code.mios.com and therefore the browser is not happy and reject the AJAX call. for ALTUI this is not an issue but the autoupdate feature will not happen, thats all.
Chrome is pretty clear about the issue ( at least in french )
Impossible de v?rifier sur le serveur qu'il s'agit bien du domaine code.mios.com, car son
certificat de s?curit? provient du domaine *.repositoryhosting.com. Cela peut ?tre d? ? une
mauvaise configuration ou bien ? l'interception de votre connexion par un pirate informatique.
to fix it it would require either
- to lower the security in your browser and accept code.mios.com as a trusted site even if certificate is not correct, which I do not really recommend. I have made the test to force chrome to open this and then it works but I have not found in chrome option where to modify the settings to make code.mios.com a trusted site
- to find another https server, like sjolhagen one but it is less convenient for me to publish files there … and I change this file often
- MCV to renew their code.mios.com certificate…
so I propose to NOT fix this issue and simply decide that autoupdate is not a feature for remote access. it is probably sane anyhow to only do an auto-update when you have local access, just in case the upgrade does not work well.[/quote]
That makes sense and understood, agreed with NOT fixing this. Appreciate all the fine details very much.