If this is your first visit, be sure to check out the FAQ. You must register before you can post. Your first post will be checked for appropriate content
(SPAM) - please allow a bit of time for that. After that, you'll be able to post at will!
3.0.7 works like a charm. All 3 reported problems are fixed now.
This is the result of a quick test. I'll let you know if something shows up later in real life implementation and use.
BLRadioRA is much smarter now allowing me to delete 18 (master controls) x 17 (buttons) = 306 HS3 devices that were created automatically by BLRadioRA just for tracking master buttons. This massive number of devices clogged my system creating sluggishness and inconveniences. If you haven't removed this automatic creation of HS3 devices you may consider removing it for the convenience of your clients.
3.0.7 is a real breakthrough adding direct triggers for MC button press without going trough a bulk of associated devices. I think it is worth promoting it to a major upgrade at level 4.0 or 3.1 within the next update.
Thank you very much for the cooperation and for the quick turnaround.
Best regards,
RISquare
Last edited by risquare; January 14, 2018, 05:23 PM.
Just noticed that the press of "raise" and "lower" buttons of a Master Control is not processed by BLRadioRA 3.0.7.
The log sample below does show that BLRadioRA does receive the information ( commands RBR for "raise release" and LBP for "lower press" RBP for "raise pressed" and LBR for "lower release") however it doesn't process it as there is no trigger based on RBP, RBR, LBP, or LBR.
If I may propose a solution to the problem it is this. As far as both are related to a particular master control (MC) ( 11 in the example below), particular system (S1 in the example below) and particular button (01 in the example below) than the best way to add this functionality is to add four more options in the existing trigger at the fourth (last) level called "Status". The drop down box of Status has 3 elements now On, Off, Any. If you add 4 more for "Raise Pressed", "Raise Released", "Lower Pressed" and "Lower Released" to the mix than it will do the trick. However all "lower" and "raise" should stand on their own and not covered by "any". "Any" should cover only "on" and "off" as it does now.
Attached is a photo of a typical Lutron Radio RA MC with "raise" and "lower" buttons visible at the bottom left.
Thanks,
RISquare
Jan-14 1:38:14 PM BLRadioRA Info Message Rcvd --> LBR,11,01,S1
Jan-14 1:38:14 PM BLRadioRA Info Message Rcvd --> LBP,11,01,S1
Jan-14 1:38:12 PM BLRadioRA Info Message Rcvd --> RBR,11,01,S1
Jan-14 1:38:11 PM BLRadioRA Info Message Rcvd --> RBP,11,01,S1
Jan-14 1:38:07 PM TTS Speak ():test test test test
Jan-14 1:38:07 PM Event Event Trigger "test Lutron received on"
Jan-14 1:38:07 PM BLRadioRA Info Message Rcvd --> MBP,11,01,OFF,S1
Attached Files
Last edited by risquare; January 15, 2018, 02:14 AM.
Found another problem.
None of the Radio RA devices activates "Referencing Device(s)" feature of HS3.
If you go to View --> Events in HS3 you will see 3 tabs at the top. The 3rd one is named "Referencing Device(s)". It will show all events that use a particular device if you select such device from the drop down box.
It is very useful for troubleshooting.
I have an event hidden somewhere among hundreds of events that turns on some Radio RA lights in the middle of the day. I want to trace, find and delete or modify this event, however I can't because BLRadio RA doesn't report its devices to "Referencing Devices" feature or this feature is somehow disabled for all BL Radio RA devices.
Just noticed v.3.10 is out
What does it fix?
I have problems with Google Home sync. Particularly BLRadioRA type devices will not sync. I disabled all others and tried to sync only BLRadioRa devices and failed. Could be a GH integration problem beyond BLRAdioRA.
Does v 3.10 address GH or something else? Pls advise.
Thanks.
To follow up on my previous post.
These device types do NOT cause problems with Google Home sync
BLRadioRA Zone
BLRAdioRA Phantom Button
BLRAdioRA Phantom Button Special
BTW what is the obsession of plug-in developers to create so many "device types". I have at least 50 device types in my system created mostly by plug-ins. Too many to handle. Also I'm suspicious that some of them create problems with Google Home and Siri integration as these apps look at the device type in particular. Furthermore we the users of plug-ins are not permitted to change the device type when it is "owned" by a plug-in.
Thanks.
To follow up on my previous post.
These device types do NOT cause problems with Google Home sync
BLRadioRA Zone
BLRAdioRA Phantom Button
BLRAdioRA Phantom Button Special
BTW what is the obsession of plug-in developers to create so many "device types". I have at least 50 device types in my system created mostly by plug-ins. Too many to handle. Also I'm suspicious that some of them create problems with Google Home and Siri integration as these apps look at the device type in particular. Furthermore we the users of plug-ins are not permitted to change the device type when it is "owned" by a plug-in.
Comment