V2 (as you would suspect from the below)
luup_log:0: MYVERSION: 1.1.1234 <0x340e>
luup_log:0: CORRECT (1234567890)? 1234567936 <0x340e>
luup_log:0: CORRECT (seconds = 00)? Sat Mar 26 19:10:08 2011 <0x340e>
It’s OpenWrt’s fault. r18159 changed the Lua number representation to float, ostensibly to save memory. r23284 changed it back to double, given Lua’s unwillingness to turn numbers back into integers, it messes with epoch times.
Yes, I know. I’m desperately trying to convince MCV that something is seriously wrong with the Lua component of the current OpenWRT builds for Vera V2 - no acknowledgement so far …
Is this related to vera's inability to get non-integer values from temperature and other sensors?
On the surface Vera’s inability to provide non-integer values is caused by not adhering to the UPnP specification. The UPnP specification clearly states that temperature values are centi-degrees, not degrees. In consequence, all temperature related UPnP variables are off by a factor of 100 - and there is no way left to put non-integer values into the UPnP variables.
MCV shouldn’t use the [tt]upnp-org[/tt] namespace for non-compliant variables - now it’s too late. I cannot think of a fix that wouldn’t break existing Luup code that assumes that temperature values are integer degrees. In other words: don’t expect a fix soon …