I’ll be putting in your fixes to the main repo as well. Thank you @adrabkin for your research into this. I had no idea that there would be a length restriction. Yeah I’m also trying to figure out how to debug that command as well. Debugging the http response was easy but not sure about this command.
Edit: Changes have been checked in to github as well. Thanks for the help with that, I don’t know if I would’ve ever noticed that since I don’t have a multi
Note sure that’s needed in the POST command, I just saw that from a successful entry that was coming from the Cloud, so I decided to through it in for good measure.
After looking through some other posts, I think the key for capturing errors is in a callback and tying into physicalgraph.device.HubResponse, but I’m still trying a bunch of things to get it to actually fire on an error.
Ah I gotcha, well its not hurting it 
Might remove it if it does cause an issue. Yeah I’m looking through some posts as well to find a nice example of how this is accomplished since the documentation doesn’t really tell me much.
Well I can get it to log a bunch of “null” lol with this
log.debug hubAction
hubAction
So I think that we’re headed down the right path just need to figure out how to get it to actually throw some text in there besides null
Ran into a new snag with the code.
I added a Schlage lock to the Splunk App to log my lock/unlock. As soon as I lock/unlock I get the following error in the LiveLogging:
groovy.lang.MissingMethodException: No signature of method: script14636285660451520135105.genericHandlers() is applicable for argument types: (physicalgraph.app.EventWrapper) values: [physicalgraph.app.EventWrapper@126344a6]
Possible solutions: genericHandler(java.lang.Object), energyHandler(java.lang.Object)
Seems as soon as it hits the event handler it craps out.
I am using a custom Device Handler for the Lock.
Diving into the lock device handler to see if I can figure this out
Yeah sadly I don’t have a zwave lock (Yet, really considering a yale because well I like Yale locks) So I can’t really debug this. Let me know how the debugging goes and what the fix will be :).
Has anyone tried to log Aeontec Smart Stip plug metering data?
I have a home brew setup that I use this for, and I wanted to log how many watts I am pulling during the brew process.
Is there a SmartApp that could be written that places all the log data on your phone, from which you then can download and do what you please with it?
Thank you!
https://artik.cloud/ has some cool graphing and its free for “hobbyist” usage. ST integration was pretty easy through the smartApp. I only have a few devices on it but it seems pretty nice. There is a data export option.
My other plan is to set up this:
Figure I have artik up and running so I will give it a month or two.
Ben,
Have you had much luck with Artik?
I synced it up with my ST and the Aeon Labs DSC11-ZWUS, and it collects usage data of my virtual switches just fine.
The thing I can’t figure out is how to have it collect the energy data. It currently only gives me switch on and off data.
I will keep trying, but wanted to see if you have any luck around this.
Have used it for that yet. Use it mostly for temps.
I added my Aeon switch, and there was a “Energy” option in the chart. Does the DH support monitoring KW hours?
Just out of curiosity, in the “Add Device” dashboard for Artik cloud, what did you add the Aeon switch as?
I ask, becuase I don’t see the check box for energy.
Thank you,
Shawn
It was under Energy Meters.
I am using this: https://www.amazon.com/Aeon-Labs-DSC06106-ZWUS-Z-Wave-Energy/dp/B007UZH7B8
In the Device Handler, it lists wattage/KwH used.
Great work!
-hal @ splunk
Thank you very much let me know if you have any trouble.
Hi there,
I am fairly new in trying to setting up splunk and programming with smart things. I setup a Splunk-light 6.4 instance, configured a new indexer and called it WilsonST. Can you help me understand if I set up the following correctly?
Local Server - False
Splunk Hostname/IP - WilsonST
Use SSL - False
Splunk Port - 8088 (default port)
Splunk Authentication Token - KeyEnteredFromSplunk
In the Smart Things logs, I am seeing: java.lang.SecurityException: Endpoint http://WilsonST:8088/services/collector/event is blacklisted. @ line 238
When I try to visit http://WilsonST:8088/services/collector/event, it doesn’t work either. Can you provide any assistance on what I am doing incorrectly please?
Thank you,
You are correct that those items are boolean items. I put in the ssl request per request since initially we were sending the events from ST over the web to the box. But then I looked at how to use the local portion to have the hub just feed the events directly to splunk so that way we don’t have to have the port open on the FW for these events.
So if you have local server set to false and I’m assuming that WilsonST is your splunk server? Should you change local to be true? Also is WilsonST a dns resolvable name? In my case I just plugged in the IP address of the splunk box since I didn’t trust my DNS server Let me know how I can help you get this working. Thanks.
Hey Jason,
Unfortunately I am not an expert with splunk. (its literately my first time trying to set this up) I was thinking my hostname would be WilsonSt, but that looks more to be the name of my token.
Can you help me understand where my splunk hostname is located?
I tried using my splunk light URL (https://prd-p-2mm2hg3qnhs8.cloud.splunk.com) and that gave me some new errors
Local Server - False
Splunk Hostname/IP - prd-p-2mm2hg3qnhs8.cloud.splunk.com
Use SSL - True
Splunk Port - 8089 (default port)
Splunk Authentication Token - Token value added for WilsonST
Error - org.apache.http.conn.ConnectTimeoutException: Connect to prd-p-2mm2hg3qnhs8.cloud.splunk.com:8089 [prd-p-2mm2hg3qnhs8.cloud.splunk.com/54.175.156.122] failed: connect timed out
Not sure where the address “/54.175.156.122” came from in the error logs.
I also tried the following two links into my firefox browsers to see what would happen:
prd-p-2mm2hg3qnhs8.cloud.splunk.com:8089/services/collector/event
Error: Secure Connection failed
prd-p-2mm2hg3qnhs8.cloud.splunk.com/services/collector/event
Error: 404 not found
BTW: Thank you once again for providing me support. I greatly appreciate it!
I’m guessing that the 54.175.156.122 is the ip address of the splunk cloud instance.
I myself have a local splunk install. You might want to post on splunk answers and ask what is the best URL for splunk cloud to use the event collector. With a local instance I just point it to the local IP but I’m not sure when it comes to the cloud.
Post in the Splunk Answers and let me know what you get back from there. With the cloud instance it could be a different path which would require another boolean
A neat little trick I found when writing code to get all of you event.
If you create your page, similar to this: (where selectedCapabilities = @Field final selectedCapabilities = [ “actuator”, “sensor” ])
page(name: "deviceAuthorization", title: "", nextPage: "devicesPage", install: false, uninstall: true) {
section("Select Devices to Authorize") {
for (capability in selectedCapabilities) {
input name: "${capability}Capability".toString(), type: "capability.$capability", title: "${capability.capitalize()}Things", multiple: true, required: false
}
}
}
So when you goto your app, all of your devices will be listed in either the actuator or sensor group. If you then put oauthPage: “deviceAuthorization” as the preference options, you can install the app via OAUTH. With that, you can have your SmartApp isntalled via OAUTH.
So, when you want to subscribe to the events you simply:
selectedCapabilities.each{ capability ->
settings."${capability}Capability".each { thing ->
if (subscribed[thing.id]) {
return
}
subscribed[thing.id] = true
thing.supportedAttributes.each { attribute ->
log.debug "subscribe to attribute ${attribute.name}"
subscribe thing, attribute.name, deviceEventHandler
}
thing.supportedCommands.each { command ->
log.debug "subscribe to command ${command.name}"
subscribeToCommand thing, command.name, deviceEventHandler
}
log.debug "subscribed to thing ${thing.id}"
}
}
and you will subscribe to every single event the device throws out and commands as well. (the commands part is nice as you can verify if a command you sent went out) No need to hard code or manually enter all of the attributes. BTW, this also works well when creating generic Web Services.
I must say, much thanks to https://octoblu.com/ as their SmartApp had a lot of this. Just wanted to pass it along as my logging SmartApp is super small in code.
8089 is the service port for Splunk. You can’t connect to it with a web browser. There is web server like behind it, but its for REST API and event collection.
That IP is your IP of your splunk cloud instance
kris@mqdns1:/tmp> dig prd-p-2mm2hg3qnhs8.cloud.splunk.com
;; ANSWER SECTION:
prd-p-2mm2hg3qnhs8.cloud.splunk.com. 29 IN CNAME elb-prod.us-east-1.a1.cloud.splunk.com.
elb-prod.us-east-1.a1.cloud.splunk.com. 59 IN A 54.85.83.45
Can you try with SSL off. If you have SSL on you will need to get a certificate for it work…