I am banging my head against a wall trying to figure out how this action actually works. Since it is a custom function developed by Physical Graph, I was hoping there would be reference API documentation on how it functions, working examples, etc. I have a kludge working with a SmartApp but am try…

But now that I think about it a little more, ‘A’ is a valid result for Dec2Hex(10). Don’t know the reason why hex is needed, but guessing that’s what the hub’s hardware needs and it is too stupid to figure it out on its own. Anyway… hope you reported this via email.

Here’s a function I wrote to potentially solve the issue, but I can’t test it in my office since the IDE doesn’t work behind a firewall for whatever reason… (Have to dig into that later) Can someone saavy with code test this and then set back the device NetworkId to be the debug’d string private c…

@pstuart , I don’t get it why you need to convert IP address to hex. HTTP GET works for me with dotted addresses (192.168.1.100:80). Although I’m calling it from the app, not the device handler.

@geko , The deviceNetworkId in ST for the local hubaction GET needs a hex ip and port in the device settings. HTTPGET which is cloud based, external does not. If you want to port forward your cameras, then you can use HTTPGET but if you don’t want the world seeing your cameras, then you can use my…

I’m not talking about “external” HTTP GET. I’m talking to my WiFi thermostat locally using sendHubAction() and I don’t need to do any hex conversion. Here’s my log reading thermostat version (GET /tstat/version): 5ce516f6-38cc-4e24-8102-793536912397 10:57:49 PM PDT: debug body: {“version”:100} 5c…

Nope. It’s easier than you think :smile: def sendRequest() { TRACE("sendRequest()") def httpRequest = [ method: settings.httpMethod, path: settings.httpResource, headers: [ HOST: state.networkAddr, Accept: "*/*", ] ] def hub…

Apples and oranges… The HOST: in the request has to be in IP:PORT notation. But it all responds on the dni. if you don’t provide it in the hubaction it will default to the configured “Device Network Id” What code are you using. Also, go into devices, click edit on the device, and what is the “Devi…

I’m not passing deviceNetworkId to sendHubAction() like you do, so I don’t need to do any conversion. And like I said, this function is called from the smart app, there is no deviceNetworkId.

But there has to be a device somewhere installed either manually or via the smartApp. It has a “Device Network Id” in Hex notation. Just go into devices, to your tstat and tell me your DNI. It will not be in 192.168.100.1:80 format.

Any Documentation on "physicalgraph device HubAction"?

General Discussion

pstuart (Patrick Stuart [@pstuart]) July 13, 2014, 5:30pm 17

In your device settings, what is your device Network ID set as? I can almost guarantee it is in HEX… You can even see it in the debug ip:C0A80169, port:0050

Starting point hubAction

Topic		Replies	Views
Response from HubAction General Discussion developers	18	4320	March 30, 2016
SmartThings Labs and LAN Devices General Discussion archive_developers	55	15250	January 7, 2016
Multiple hubaction commands in one function and parsing the response Writing Device Types	52	4977	January 4, 2018
Physicalgraph.device.HubAction and POST Devices & Integrations	10	3919	November 29, 2014
Is sending a POST or GET command to a device on the same network as the hub (via custom DH) not supported anymore? Writing Device Types	3	506	July 14, 2021

Any Documentation on "physicalgraph device HubAction"?

Related topics