forum

To those coming to this thread later and looking for a summary - no, there is no way to reliably match the device ids emitted by the sensor logging app to the actual device itself. The only way I found was to manually build a lookup table and update it every time I add a new device.

Oh, I found it! Pull request raised, though you'll want to rework my translations, I'm sure.

Yikes, I don't think I'll be able to make sense of that without a lot of work. I was hoping just the sensor values logging app was opensource - that seems like a bite-size piece of code I can figure without learning all the other intricacies of the suite. My plan would be simply to add a macro ${nam...

I'd love to know where the -254 comes from! It's the value for one of the events, but otherwise doesn't turn up anywhere in ZWaveApi output. Likewise I can't find an '8' anywhere that might match what I'm seeing in ZAutomation. Is the 254 it reporting the value? Seems unlikely, doesn't really make s...

That mostly works, but one device is coming out of the sensor logger as 3-0-113-8-254 but in ZAutomation it's id is: 3-0-113-8-8-A Is that normal? Will it happen for other devices too? I'm hoping to avoid having to code all sorts of weird exceptions here, is there a better way to get the data? Where...

Great, that got it thanks. It hadn't clocked the api without authentication still uses an account, and that that account is a separate pre-existing one. Should've poked around in management further though, I would've tried that if I'd found it.

Mu apologies, I misread. Devices gives:

Among other things, I tried renaming my device while debugging some issues, to see if it helped - it's now called 'cen', not the default 'zway'. That URL gives me: $ curl -vgL 'http://127.0.0.1:8083/ZAutomation/api/v1/device' * Trying 127.0.0.1... * TCP_NODELAY set * Connected to 127.0.0.1 (127.0.0....

With that URL string I get 'Invalid ZAutomation request'. I have more luck if I change the 'API' to 'api', in that it no longer reports Invalid request, but no matter how I format the string I can't get anything other than "Device doesn't exist". First I verify the device exists and zway k...

Cool, cheers. I've managed to work out what the numbers mean, what I need is a way to map this back to the actual device name. Is there some part of the API where I can pass in those numbers and get back a string telling what device it is? I haven't yet found one. Chopping the numbers and changing f...