I just checked Mantis for progress on some bugreports.
To my surprise i saw a report on bug 1471 (Door Locks - Fire warning event when battery is below)
In the description i noticed
Tested on 1.1.1234 and 1.1.1249.
Does that mean 1249 is available as beta?
Anyone else have any input?
Given the reporter (@mcvdaniel) this might have been an internal build.
(The current not-officially-released-to-the-general-public beta is well beyond .1245)
[quote=“oTi@, post:2, topic:168401”]Given the reporter (@mcvdaniel) this might have been an internal build.
(The current not-officially-released-to-the-general-public beta is well beyond .1245)[/quote]
@oTi@
Nod nod… i understand development doesnt stop…
Just curious if i missed something.
Maybe MCV can inform us on a next beta and a roadmap…as has been done with 1245 and very much appreciated by a lot of forum members… we’ll see!
Im going to try to keep a version log here.
If anyone (preferrably MCV) can offer release info for a build, please contribute:
Known fix for thermostat setting issues (Horstmann HRT series)
–link removed by wseverino-- referring to build ui4-1.1.1267-1
Contributions would help
I deleted the link because this is an unofficial beta. These guys do multiple builds to test things. Unless the beta team has tested it then there is way to much risk to the community.
@wseverin0
Fine with me, guess you need to go through other forum threads to do some more then since it wasnt originally posted by me. All i was trying to do is a be a bit supportive.
Besides, if you had contacted me i would not have had any problem with editing my own post…
Since MCV does it best to build new and better builds but doesnt always have time to update/inform us, how will we be informed?
Appearantly MCv is working on solving some thermostat issues that some people have with thermostats in europe this looked like a (partial) fix.
Would you be so kind as to let us know where official ARE posted (instead of having to sift through hundreds of forum threads?)
@Henk,
How did you arrive at that conclusion?
I’m sure that @micasaverde will announce the next beta for public consumption:
Ex.1
Ex.2
etc.
As far as I can tell, there are internal builds for MCV’s test purposes. Some are targeted at specific issues and then sometimes given to specific users, under MCV guidance. Some of the builds end up with the Beta Testers, even fewer are released as a public beta and a very select few are made official.
@oTi
Well thanks… i dont “arrive” at conclusions, im open to advice and trying to learn.
Easiest way to do that is make mistakes and accept advice, ask questions.
Thanks -again- for taking the time to do so.
In due time i would be open to an offer to do some beta testing myself (taking up my old daytime job a bit)
Until then, i went through different threads… noticing that 1245 was available for ppl while it was eing discussed in 1183… then later on the new 1245 thread was opened.
Dont get me wrong, im not the grumpy pessimist depicted in the avatar, instead, im more of the humorist behind it…
So im trying to do contribute, willingly accepting advice and “behaviour code”.
I was kinda looking for a beta discussion thread i think, looking to actually incoprporate some visual/available examples and trying to get a discussion going from that!
Does that make sense?
@Henk,
oTi@ hit the nail on the head with the daily builds being controlled experiments. In the end we all end up with the culmination and an official release.
im not the grumpy pessimist depicted in the avatarOh, that's an Avatar? I thought that was a Christmas portrait!! :P
JOD.
chuckle… HRMPPFFF HUMBUG!!!
I know what oTi was referring to…
Im aware of daily (alpha) builds, beta builds (in various iterations) and official releases.
My point is that this forum discusses a lot of problems, solutions, workarounds and general instructions.
Some code here is likely to be more dangerous than an alpha release to an average user.
What i was trying to do was to get a log of different builds together with their intention/release notes/purpose.
for instance, i would like to contribute on the thermostat issue simply because
Now i know that not every release should be open to general public.
On the other hand, we could contribute even by discussing if we knew what build was made, for wat purpose similar to what we do with many other (coding and hardware) issues here.
MCV is already at daily build 1280… Wonder what the roadmap and releasenotes will be when they release the next beta…
My guess would be that there’s a lot of builds going on around UI5 development, and the OEM solution they had mentioned…
I think than more than guessing on what MCV is doing, we should use the system as it is and express ourself on what is not working as it should or as we expect it to work ?
True, but if we had a sense on where their priorities are we can talk about it and let MCV know from the customer point of view what our wants and needs are and help improve the product…
@Henk
An idea: why don’t we create a new section MIOS/General/User requests
A new thread would be created for discussions for every request. As an example, the request for a mechanism to display rooms in the way we want it could be moved there.
What do you think ?
ps: by the way, good job with the main page!
[quote=“huogas, post:15, topic:168401”]@Henk
An idea: why don’t we create a new section MIOS/General/User requests
A new thread would be created for discussions for every request. As an example, the request for a mechanism to display rooms in the way we want it could be moved there.
What do you think ?
ps: by the way, good job with the main page![/quote]
Sounds usefull to me. We would have to discuss the option with @guessed.
The wiki mainpage gave me some headaches but i got there, thanks for the kind words.
Seems were up to daily build 1281… wonder what the progress is…
Bug fixing? Feature improvement? UI5 development?
Cant wait till the first official beta is released by MCV!
How many people actually use the Vera web UI on a regular basis? I really just want it as a simple, solid configuration interface. My interaction with Vera should be via in-wall scene controllers, mobile device remotes/3rd party interfaces to the LUUP URLs, and most importantly automatic (i.e. programmable logic – home automation, not remote control!). Most of the complex logic is doable in LUUP, it’s just a bit awkward and has a steep learning curve. Some wrappers and simplification of the scripting would go a long way… (e.g. a library of common functions that maps your ‘friendly names’ to device/node IDs so you can just write: if (isUnlocked(“Front Door”) and (isNight()) then setLevel(“Kitchen Light”, 50)).
I really hate to think how much time is wasted on stupid bling. It seems Vera is way too underpowered to host all kinds of graphics and AJAX and going off to to scrape weather network and social feeds. I don’t want it to be some sort of central visual life control panel (which I don’t think it has the hardware chops for), I desperately want a reliable, headless home automation appliance. Spend every precious CPU cycle and memory byte monitoring my timers/sensors/events and controlling my devices, not fetching crap off twitter. It seems like the Sigma/Zenesys firmware might not be the most reliable, the Vera/MIOS engine might not be the most reliable, and people are concerned about customizable room ordering in the next version of the UI [please don’t make it alphabetical!] 
UI stands for User Interface. Do I have to say that the UI is the main tool to talk to Vera.
We are not speaking about making Vera the central hub for social media, we just want ordering what is actually the main object in the UI: the rooms. I still don’t think it is too much to ask ? Is it ?
Absolutely no argument there ;D However, I said “web UI”. There are all kinds of other UI’s, (in-wall controllers, SQ Remote, Mobile WAP, etc etc…). Plus I’m hoping not to have to interface with it that much at all… I want to configure it and have it “know what to do” as much as possible. I was just wondering how many people use the WebUI (which basically requires a computer/full tablet) on a very regular basis. It really was a question. If it is most people, that’s fine… just want to know that’s the case and that MCV efforts are on track with what customers use.
Definitely not, I agree the ‘appear in creation order’ is a little cumbersome, but at least it is controllable (alphabetic – an option someone mentioned – is not). However it is far less important to me than not having to un-pair and re-pair all my devices and factory reset on a routine basis.
Based on what I saw in the UI5 screenshots, there is nothing new other than a layout change and some banners with weather/stocks scrolling by. If that is what most customers value then I accept it. I just haven’t seen it asked anywhere “do you want a rock-solid Vera with better automation or should we re-vamp the graphics a fifth time?”. I think MCV would be better off letting the community write their own custom UIs (like TimAlls is doing, like the smartphone plug-ins, etc…). Make a solid “configuration UI”, and then a simple “operator” UI that is end-user-hackable.
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules