Realtime Event Webhook Driver

[Rexabyte]

You just need to provide the base proxy types:

• thermostat.c4i
• light.c4i
• light_v2.c4i
• lock.c4i
• control4_contactsingle.c4i
• fan.c4i

I'm sure there's more but I believe that's the core of what you had provided.

<property>
  <name>Devices</name>
  <type>DEVICE_SELECTOR</type>
  <items>
    <item>thermostat.c4i</item>
    <item>light.c4i</item>
    <item>light_v2.c4i</item>
    <item>lock.c4i</item>
    <item>control4_contactsingle.c4i</item>
    <item>fan.c4i</item>
  </items>
  <multiselect>true</multiselect>
</property>

 

[harper]

Yea. I do that - but not via an interface for the end user. I will work on that now. 

If there are types that you want to track before I build out the interface - let me know. I will make a new build that tracks more than it already does

[caudingo]

Hi harper,

sorry to bother you... would you have a very rough indication of when the "self healing" capability will be available? Right now I have to re-register events in Composer about every 2 days, which makes it unusable when I'm not home (often). Or is there some workaround? Can I somehow contribute?

Cheers

Chris

[harper]

let me see if i can take care of this later this week. 

 

Do you know lua? feel free to email out of band: harper@nata2.org

[caudingo]

Great! I don't know LUA, but I'm a fast learner!

[RyanE]

12 hours ago, caudingo said:

Great! I don't know LUA, but I'm a fast learner!

First step is to learn that it's spelled Lua, which is a proper name (which means 'moon' in Portuguese), not an acronym.

RyanE

 

[harper]

lol. regardless of how its spelled - i would love help

[eleese]

Hey Harper,

Great work on this driver! I'm looking forward to seeing more proxy types added in the future including AV and advanced lighting scene events.

I'm curious what external logging you've incorporated this driver with. I've been looking for a way to track system usage for awhile now and this driver might be a perfect fit. I saw in your other thread for your Prometheus Metric Logger driver that you're a Plex user so you may be familiar with Tautulli. My thought was a web app similar to Tautulli that offers:

• real-time system usage monitoring that can be filtered (various levels possibly as deep as physical remote/touchpanel button presses)
• historical usage browsing/filtering (think datatables). This would include:
  • watch/listen events
  • av sources, switchers, displays, etc power and input events
  • av source events (current song, service (netflix, amazon, plex, etc)
  • temp & humidity changes
  • advanced lighting scene events
  • individual light changes
  • would NOT include granular button presses
• graphing (temps, humidity, security, etc)
• notifications

Currently I've linked a webhook driver instance with node-red and have this storing all events into a SQLite database. I'm debating where I want to go from here. I'm not sure node-red is the right platform for an app like this so I'd like to hear what you've created and your thoughts on using your driver for an app like I described. 

 

Thanks,

Eric

[harper]

Yea. The webhook -> nodered is a good patch for now. 

This is also why i built the prometheus logger. But i like the idea of something custom to control4. 

let me know what you settle on and whether I can help out at all.