开云体育

I have a very large Lutron QSX integration program.
The lutron logs are complaining about some href buttons not existing.
As any of you that have done qsx integration know, there can be literally hundreds of these href's in a program.

I have a couple I'm trying to track down but a lack of a simple find function in Simpl is proving to be problematic.

I've tried opening the smw in Notepad++ and searching in that but cannot find any href parameters even ones I can clearly see.

Anyone have any suggestions to track down parameters in a program?

Thanks

If you know the exact parameter text you're searching for, you could F9 the entire lighting folder and replace the parameter text with "". If the module flags incomplete parameters then you'll get a warning with a pointer to the location you're looking for. If it doesn't flag "" then you could try some other invalid text for the field.

Unfortunately I think what he is dealing with means a digit is off in his parameters and Lutron is kicking him errors that the href doesn't exist.? I don't believe there is a way to know an href that is erroring then search for it in parameters.? I've been in these shoes and it sucks.

I'm waiting for another large QSX system until I do this, but I am going to modify how my modules work to read from a file for href's instead of using the pre-built modules.? These larger systems, you absolutely need the ability to locate and change these href's easier.? Unfortunately the current QSX modules, though ControlConcepts did a good job on the initial build really need a second version with a lot of modifications for things like feedback, dimming, href handling, etc.

Alex,

F9 & replace with an empty parameter worked a treat as the process will fail and brings up the Replace Substrings dialog with a Warning - Could not replace Parameter Zone_href_ID on Symbol: S:x.x.x.x.x
So that enabled me to track down the rouge ID's.
Thanks

Awesome. Glad it worked for you.