This object is in archive!
Wakeup interval bugged
Under Consideration
I cannot save any settings as the wakeup-interval says its maximum value is a large negative number. This is with firmware 0.9.995, I was getting NO_MOTION every minute with 0.9.994 (all with an Aeon Multisensor which worked in the past)
I like this idea 
No connection
Real-time notifications may not work
No connection
Real-time notifications may not work
So how is it for others?
Same problems?
I did not upgrade yet...waiting for some infos.
So how is it for others?
Same problems?
I did not upgrade yet...waiting for some infos.
If I plug in the Aeon Multisensor then it works a lot better than 0.9.994 (which reported NO_MOTION every minute) but on battery you can't save settings due to the GUI wakeup-interval bug mentioned above.
Actually with 0.9.995 it is sometimes only reading temperature and not the other values so something is still messed up :-(
If I plug in the Aeon Multisensor then it works a lot better than 0.9.994 (which reported NO_MOTION every minute) but on battery you can't save settings due to the GUI wakeup-interval bug mentioned above.
Actually with 0.9.995 it is sometimes only reading temperature and not the other values so something is still messed up :-(
Ok I'll stay away from it untill it is fixed.
Thanks
Ok I'll stay away from it untill it is fixed.
Thanks
My Zipabox also runs on version 0.9.995
I removed the Aeon Multisensor, then added it again and now the configuration option to set Wakeup interval is not there anymore.
Now I also get only temperature and movement readings. No humidity, no luminance.
My Zipabox also runs on version 0.9.995
I removed the Aeon Multisensor, then added it again and now the configuration option to set Wakeup interval is not there anymore.
Now I also get only temperature and movement readings. No humidity, no luminance.
Funny... my aeon labs, avfter a battery change, is reporting just the MOTION status and not any more the NO_MOTION. Also the temperature, humidity and luminance are messed up in the dashbaord events.
I have no clue on how to solve this :(
Funny... my aeon labs, avfter a battery change, is reporting just the MOTION status and not any more the NO_MOTION. Also the temperature, humidity and luminance are messed up in the dashbaord events.
I have no clue on how to solve this :(
The box is now reporting changed values to server, and the rules are triggered on changes only. So you won't see NO_MOTION in the log for every interval, and we won't store petabytes of closed doors and no motions in the database.
Bindings, thermostats and alarms still get everything.
The box is now reporting changed values to server, and the rules are triggered on changes only. So you won't see NO_MOTION in the log for every interval, and we won't store petabytes of closed doors and no motions in the database.
Bindings, thermostats and alarms still get everything.
I am running 0.9.998 and I can't set the wake up interval on my multisensor. I have tried to re-apply device descriptors. See attached picture. No vaule I enter gets accepted.
Any comments, Zipato?
I am running 0.9.998 and I can't set the wake up interval on my multisensor. I have tried to re-apply device descriptors. See attached picture. No vaule I enter gets accepted.
Any comments, Zipato?
Replies have been locked on this page!