New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in Accumulator Process, maybe #407
Comments
Are you running Redis on your system? |
Yes, Redis is running with redis-cli 2.8.4 |
It looks to be a problem in PHPTileSeries.php With PHP there are packing and unpacking functions:
|
if i do /feed/data.json i get this |
Maybe I found the problem. |
I put this to the last else statement in the get_timevalue |
I also ran into this issue, except with PHPFina and without redis. The feeds.value field in the mysql table is the single precision float that is being rounded down. In my case it was 1257.77 trying to accumulate ~0.002 which would become 1257.77 again. I solved it by altering the mysql table to convert the float to a double. MySQL floats appear to behave slightly differently than regular floats because 1257.772 can actually be stored in 32 bits just fine, but even if I try to edit the field in phpmyadmin, the value flips back to 1257.77 if the datatype is float. This should be changed in Modules/feed/feed_schema.php, change the datatype of value to "double" and then run the "Update Database" function from the administration console. |
Following further discussions in the forum the datatype has been changed to 'double' in the master branch. |
I have a strange situation in process an accumulation.
Every 10 seconds i get a value of 50 to 53 Wh as input.
In processlist I multiply this by 0.001 for kWh and accumulate into a new feed.
The value in the new feed growed like whished, but now it goes over 10000 in value in the new feed.
Now the value seems to be cutted or rounded ?!?
The input stays at 52 Wh but there are added 100Wh every 10 seconds by the accumulator.
this started when the value switched from 9999 to 10.000 ?!?
The text was updated successfully, but these errors were encountered: