Announcement

Collapse
No announcement yet.

Doesn't work pls fix I'm a buyer

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • risquare
    replied
    How to solve previous 3 problems at once

    Hi Blade,

    May I propose a solution to the last three problems.

    Why don't you create direct RadioRA triggers in HS3.

    BLRaioRA doesn't create any triggers directly now. Instead the users must rely on related device changes to trigger an event.

    My experience so far with Master Controls (MC), their respective buttons and "devices" is not very positive as the troubles are listed in the messages above.

    I think that it will be very nice and clean solution if you design RadioRA triggers in HS3 as follows

    BLRadioRA MC button press trigger -->Select s1/s2---> Select RadioRA MC -->Select RadioRA button --> Select change to On/off or any press

    Such clean solution will eliminate about 360 (three hundred and sixty) HS3 devices in my case that are used for RadioRA MC buttons. Those are rarely used and also come with problems as explained in the previous posts.

    Thanks,

    RISquare

    Leave a comment:


  • risquare
    replied
    BLRadioRA LED Control controls the wrong devices

    LED Control is supposed to lit a LED light at master control (MC) button. That's all.
    BLRAdioRA LED control command does that ... and more.
    For some reason it turns on/off the associated HS3 device to that MC button.
    This is wrong. The whole idea of MC buttons is for them to "tell" HS3 that someone is pressing a button.
    The only way to do it now in BLRadioRA is to watch for a change of the associated HS3 device to that button.
    If LED control messes with same "device" than it sends the wrong message that someone pressed a button.

    This thing needs fixing.

    Thanks,

    RIsquare

    Leave a comment:


  • risquare
    replied
    Proposed solution to the last 2 problems

    Hi Blade,

    May I propose a solution to the last two problems.

    Why don't you create direct RadioRA triggers in HS3.

    BLRaioRA doesn't create any triggers directly now. Instead the users must rely on related device changes to trigger an event.

    My experience so far with Master Controls (MC), their respective buttons and "devices" is not very positive as the troubles are listed in the messages above.

    I think that it will be very nice and clean solution if you design RadioRA triggers in HS3 as follows

    BLRadioRA MC button press trigger -->Select s1/s2---> Select RadioRA MC -->Select RadioRA button --> Select change to On/off or any press

    Such clean solution will eliminate about 360 (three hundred and sixty) HS3 devices in my case that are used for RadioRA MC buttons. Those are rarely used and also come with problems as explained in the previous posts.

    Thanks,

    RISquare

    Leave a comment:


  • risquare
    replied
    There is no HS3 "device" for "raise" and "lower" buttons of Radio RA Master Controls

    Hi Blade,

    While BLRadioRA creates abundance of HS3 devices for each RadioRA master control (MC), (assuming that each MC has 15+2=17 buttons, while in reality most MC are 5+2=7 buttons) it doesn't create devices for "raise" and "lower" buttons that are quite common on many RadioRA MC. As such there is no BLRadioRA action upon the press of these buttons.
    BLRadioRA does receive and does log a response by Radio RA

    BLRadioRA Info Message Rcvd --> RBP,11,01,S1

    RBP stays for "Raise Button Pressed" in this example

    however BLRadioRA doesn't act in any way in response to this button press because there is no corresponding HS3 device to act upon.

    As a result the press of "raise" and "lower" buttons can not be recognized in HS3 and can't be used for anything.

    I will propose a fix in a separate message here.

    RUSquare

    Leave a comment:


  • risquare
    replied
    MC button "devices" can't be controlled in HS3

    Hi Blade,

    BLRadioRA creates a HS3 "device" for each button of Radio RA Master Controls that are submitted to BLRadioRA.

    These devices are setup in such a way in HS3 that they can't be controlled in HS3. Button press on/off at the web interface doesn't work. Explicit HS3 command in HS3 event doesn't work either.

    The problem is that some buttons in the RadioRA system do send "ON" command only. In order to recognize such button presses I need to take the correspondent HS3 "device" back to "OFF" status so that a subsequent button press is recognized by HS3 and triggers an event.

    Please help.

    RISquare

    Leave a comment:


  • risquare
    replied
    Thanks

    Hi Blade,

    3.0.2 took care of the annoying problem with false zone names display for S2.

    Thanks.

    RISquare

    Leave a comment:


  • Blade
    replied
    Try 3.0.2

    Leave a comment:


  • Blade
    replied
    OK - I will have to take a look at this once I am home

    Leave a comment:


  • risquare
    replied
    BLRadioRA displays wrong zone names.

    Hi Blade,

    BLRadioRA 3.0.1 displays wrong zone names in the collapsed view of events.
    See attached screenshots. The names are correct in the expanded view and the action is correct for these zones. However the names are changed in the collapsed view creating a lot of confusion.
    I did investigate the problem and found out that the problem is related to zones in S2. If a zone is in S2 than you display the respective zone name from S1.
    I think this should be an easy fix.

    This is a real problem that needs fixing.

    Thanks,

    RISquare
    Attached Files
    Last edited by risquare; December 10, 2017, 12:23 PM.

    Leave a comment:


  • risquare
    replied
    ...polishing the plug-in

    Hi Blade,

    These do not affect functionality however fixing them will make the plug-in more polished and mature.

    1. BLRadioRA creates 17 devices for each master control (MC)assuming that the MC has the max number of 15 buttons plus "all off" and "all on" buttons. In reality most MC are 5 buttons (single gang box) or rarely 10 buttons (double gang box) while 15 buttons are extremely rare. In my case I do have about 18 MCs most are 5 buttons. BLRadioRA created the whopping amount of 18x17=306 devices whereas the total of real devices is just 18x7=126.
    It would be nice if the UI allows the user to set up the number of buttons each MC has.

    2. There are "ON" and "OFF" buttons on the web page for each of the MC devices (see above). Those are not functioning as there is no RadioRA command available to emulate MC button press. (There is BP command for the phantom buttons, but not for the real physical buttons).
    Removing those buttons from the web page would be nice although I'm suspicious that it is part of HS3 not part of the plug-in, unless the plug-in can create special devices for status only that are not controllable.

    Cheers,

    RUSquare

    Leave a comment:


  • risquare
    replied
    It is taken care of now.

    Thanks,

    RISquare

    Leave a comment:


  • Blade
    replied
    Try 3.0.1

    Leave a comment:


  • risquare
    replied
    Another snag

    Oooops just hit another snag. Hit upper limit of 12 MC and no more are allowed.
    This is reasonable when you had S1 only. Now that you manage S1 and S2 this allowance has to double to 24.
    In my case I do have 7 (S1) + 10 (S2) = 17

    Pls fix.

    Thanks,

    RISquare

    Leave a comment:


  • risquare
    replied
    As far as the upgraded plug-in (S1/S2) can serve twice as many zones and controls as the original version, may I suggest that you promote it to a major upgrade going to version 3.xx.xx.x if there are not other restrictions that I don't know about.

    RISquare

    Leave a comment:


  • risquare
    replied
    It does work now. The pendulum swung to the other direction. There is no validation now whatsoever which allows me to enter two MC1s both in S1. This shouldn't be allowed in a perfect world but it doesn't bother me much as this is one time activity to configure the system and I can be extra careful.

    Also the HS3 devices that are created and/or deleted in the process of creating/deleting MCs have two issues (none is critical).

    1. Some mess is created when updating the plug-in from one version to another. Some devices are missing others do not delete. However it is all streamlined after manual intervention/clean up. This is happening during a transition (update) only and hard to be reproduced.

    2. All HS3 devices created are "read only" devices. I can't change their status /value from the web page control nor can I change their status/value by event action. It doesn't bother me as they are for a trigger purpose only and their value/status is supposed to change by a press of a button at associated MC, which they do. Just curious is this a bug or a feature?

    Best regards,

    RISquare

    Leave a comment:

Working...
X