Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Official 5.3 Release Thread
#21
5.2.918
  • Update the Schlage BE469 device info to reflect the notification ids from traces we got, so that it will see the status changes correctly (hopefully.)
  • The publish/subscribe stuff introduced an issue in the attribute editor when you invoke some of the editing dialogs for the more complex attributes. If we made a copy of a widget, it would still publish change reports, but it's no longer part of the template, it's a copy of a template member. The template would get an error because it was getting info from a widget it doesn't know about.
  • The publish/subscribe stuff has a fundamental issue in that it only supports async delivery. But for certain types of things, where one thing is being kept in sync with another, this is an issue since more than once change can occur in the source before the target sees the msg. So we need to rework to make it synchronous, then we can build the old async scheme on top of that, so that we can support both. Update a number of subscribers to use the sync mechanism where appropriate. Others can stay with the async, which is fine for notifications and commands. This is quite a bit of work.
  • When you do triggered events in the IV, the event action target isn't being added to the target list, so you get an error if you try to use it to extract event info. That is now fixed.
  • The RCS driver is getting an error when it tries to parse the incoming thermo names prompt because of a failure to adjust for the fact that our list is one larger than the number of actual thermo slots (so that we can use the 1 based indices of the RCS protocol directly.)
  • Our Z-Wave driver disables controllers automatically because we don't need to deal with them as units that the user sees. But, it's going by the basic type and is including (and hence disabling) scene controllers (and possibly other things that we don't support yet but might later.) So we need to use the generic/specific types for this instead, to pick out specifically those that are master or static controllers or installer tools and such.
  • Somewhere along the line during the 5.x transition, the Intf Editor's use of the status bar changed from showing info for the widget the mouse is over to showing info when there is a single widget selected. The former is much more useful so change back to that. The above pub/sub changes makes that fairly straightforward to do now.
  • Add widget area to the widget palette. The above change means you can't see info for covered up widget. You can drill down and select it, but the mouse over doesn't understand that difference. So the widget palette becomes the means to see basic info on such covered up widgets.
Dean Roddey
Software Geek Extraordinaire
Reply
#22
5.2.919
  • The update of the Schlage BE469 device info in the last update to get the notification ids in place (so it would recognize lock/unlock events from the lock itself) got them backwards (locked/unlocked were flipped) so flip them back the other way.
  • Try another approach with WebRIVA for scaling. Get rid of nopixelscale and replace it with vpscale=x, where x is 1, 2, 1.5, ect... So lets the user set the scaling they want. Defaults to 1.0 if not set. Also get rid of the other options which could prevent user scaling via zoom (in theory) so it should now allow for zooming.
Dean Roddey
Software Geek Extraordinaire
Reply
#23
5.2.920
  • Make the ongoing activity timeouts in the new Z-Wave driver progressive, so that they start fairly quick so that we can get going quickly in the face of perhaps a glitch or two. Then they get longer so that we can recover reasonably quickly from a temporary outage. Then they get longer to avoid holding up other stuff while these unresponsive units fail to respond. Make them get longer quicker for frequent listeners. Do a lot other work related to this to try to support this goal.
  • The RA2 driver's thermostat high/low set point fields got their range limits reversed, so high is using low's and vice versa.
  • The RA2 driver isn't taking into account that it can get floating point values for temps.
Dean Roddey
Software Geek Extraordinaire
Reply
#24
5.2.921
  • The Lutron RA2/Caseta/HWQS driver's thermo support wasn't dealing with the possibility of floating point values, which in theory could happen. And it had transposed the high/low SP limit ranges. And it wasn't ignoring the reporting of temp/SP values for the other temp range, and some send both. That could cause out of range errors.
  • In the triggered event filter editor, when you invoke the popup menu for an entry field and select to insert a device moniker, it actually invokes the field selection dialog instead and inserts the field name instead of the device moniker.
  • When I changed all of the interface editor stuff to use the new publish/subscribe mechanism for updating displayed widget info I forgot to have the attribute editor subscribe to widget changes so that it can update the area when you move a widget directly (keyboard or mouse.)
  • When an exclude is done on the new Z-Wave driver it doesn't clear the unit list or the unit state descriptive text below the list (if one was selected.)
  • The Z-Wave driver should try to give the master controller and Z-Stick controller names automatically. They end up disabled automatically and there's no way to name them since they aren't types that we interact with. It would be nice to have them get immediately recognizable names in the unit list.
  • The Admin Intf isn't doing the correct sequence of events to restore it's previously stored position. So if you have a tool bar docked on the left or top, every time you run it it will creep in that direction by the size of the docked window. For bottom/right toolbar placement it didn't matter.
  • If you run the AI and the client service isn't running, it gives a fairly cryptic error that doesn't tell you what you might want to do to fix that issue. Now it tells you probably the client service isn't running.
Dean Roddey
Software Geek Extraordinaire
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Official 5.3 Beta Discussion Thread Dean Roddey 735 43,457 17 minutes ago
Last Post: kfly
  Official 5.2 Beta Discussion Thread Dean Roddey 244 47,855 10-14-2017, 07:57 PM
Last Post: Dean Roddey
  Official 5.2 Beta Release Thread Dean Roddey 13 4,993 10-09-2017, 06:49 PM
Last Post: Dean Roddey
  Official 5.1 Beta Discussion Thread Dean Roddey 453 115,837 05-16-2017, 03:45 PM
Last Post: Dean Roddey
  Official 5.1 Beta Release Thread Dean Roddey 28 12,031 05-12-2017, 05:44 PM
Last Post: Dean Roddey
  Official 5.0 Beta Discussions Dean Roddey 2,019 298,364 11-09-2016, 04:34 PM
Last Post: Dean Roddey
  Official 5.0 Beta Release Thread Dean Roddey 15 9,898 11-01-2016, 10:32 AM
Last Post: Dean Roddey
  Official 4.7 Beta Release Thread Dean Roddey 21 10,406 04-23-2015, 04:20 PM
Last Post: Dean Roddey
  Official 4.7 Beta discussion thread Dean Roddey 295 55,484 04-23-2015, 04:19 PM
Last Post: Dean Roddey
  4.6 Official Beta Discussions Thread Dean Roddey 514 73,689 11-04-2014, 03:57 PM
Last Post: Dean Roddey

Forum Jump:


Users browsing this thread: 1 Guest(s)