Alex Bain

Running into the same problem - something around _client.connect. Any new ideas on what's happening?

Thanks for the work on this, @dirz88. Couple thoughts: 1. What if you wanted the same `macro` to work in two different `areas`? Or, what if certain `remotes` were only...

@dirz88 Thanks for updating this. I'll take a look soon and let you any additional thoughts I've got.

Some answers to your initial questions: 1) Yeah, `lirc_web` isn't going to make any sense if we add `gpio`, `rf`, `zwave`, and `http` based devices. I'm tempted to fork the...

One other thought that would be good to figure out is how to add/remove support for protocols based on what your own requirements are. When the project is called `lirc_web`...

@pkubat 1. Yeah, I believe a `remote` should be just a type of `device` and they map 1:1 2. I agree that different classes or types of devices will have...

4 - Yes - I setup an `osur` branch we can start working from, for now. I think keeping it attached to the `lirc_web` project for now will be fine....

Okay, thanks for providing some context. I'll take a look at that merge request and see if I can work out what was required to get `SIMULATE` support working. Can...

Sorry for the delay. I took some time today and read through this. I appreciate how you refactored the macro engine, I do think this is a cleaner separation than...

Hi Joe, Thanks for the idea - the documentation for this library is still a little sparse. If you want to take a stab at writing up some documentation I...