01-08-2020, 06:29 PM
(01-08-2020, 06:17 PM)Dean Roddey Wrote: You tell it the port during installation. The URL is just training data. So you need to train it like you would a learning remote. So use something that can send the URL you want to that action to respond to and send it a few times fairly quickly. Once the driver has seen a consistent URL a few times I knows it has it right and it'll store that URL as the trigger for that action. Only the base part of the URL (ignoring the query parameters) is used as the trigger. That's what lets you send the same URL with different parameters and trigger the same command (which can then look at the incoming query parameters and act on them.)
Be careful of some browsers which send more stuff than the URL you send. They can send favorite icon queries and other stuff, which will confuse the training. Better to use some other sort of simple URL sending tool.
I did some more snooping and did a reconfig on the driver just to refresh and I found the port info and such. I edited my original post with info and findings.
That's actually nice (once I figure it out) how to use the same base url with parameters to take different actions in the event rule.... I'll have to figure that out to work on more complex structures. It may just be easier to write a little driver though.