Question regarding communication from HE to NR using the maker API. I am seeing a few things that stand in the way of what I would like to do. I am looking to make sure I understand where they would need to be addressed if they became a priority to that party. (I am not suggesting they should be, just trying to clarify.)
The situation I am trying to address is being able to distinguish between physical and digital switching to on of switch. And to be able to see that the physical switch was turned on even if the state is already on.
I am using the Generic Z-Wave Smart Switch driver and Maker API tied to NR in the standard way.
For the digital versus physical, I am seeing this in the log for the switch:
[dev:33](http://192.168.86.110/logs#dev33)2020-04-07 12:40:49.714 pm [info](http://192.168.86.110/device/edit/33)Master Light Overhead was turned off [physical] [dev:33](http://192.168.86.110/logs#dev33)2020-04-07 12:40:48.616 pm [info](http://192.168.86.110/device/edit/33)Master Light Overhead was turned on [physical] [dev:33](http://192.168.86.110/logs#dev33)2020-04-07 12:40:13.388 pm [info](http://192.168.86.110/device/edit/33)Master Light Overhead was turned off [digital] [dev:33](http://192.168.86.110/logs#dev33)2020-04-07 12:40:11.725 pm [info](http://192.168.86.110/device/edit/33)Master Light Overhead was turned on [digital]
In the log for the maker API, I am seeing:
[app:674](http://192.168.86.110/logs#app674)2020-04-07 12:40:49.781 pm [debug](http://192.168.86.110/installedapp/configure/674)device event: {"name":"switch","value":"off","displayName":"Master Light Overhead","deviceId":"33","descriptionText":"Master Light Overhead was turned off [physical]","unit":null,"data":null} [app:674](http://192.168.86.110/logs#app674)2020-04-07 12:40:48.676 pm [debug](http://192.168.86.110/installedapp/configure/674)device event: {"name":"switch","value":"on","displayName":"Master Light Overhead","deviceId":"33","descriptionText":"Master Light Overhead was turned on [physical]","unit":null,"data":null} [app:674](http://192.168.86.110/logs#app674)2020-04-07 12:40:13.537 pm [debug](http://192.168.86.110/installedapp/configure/674)device event: {"name":"switch","value":"off","displayName":"Master Light Overhead","deviceId":"33","descriptionText":"Master Light Overhead was turned off [digital]","unit":null,"data":null} [app:674](http://192.168.86.110/logs#app674)2020-04-07 12:40:11.836 pm [debug](http://192.168.86.110/installedapp/configure/674)device event: {"name":"switch","value":"on","displayName":"Master Light Overhead","deviceId":"33","descriptionText":"Master Light Overhead was turned on [digital]","unit":null,"data":null}
In the debug log in NR, I am seeing:
4/7/2020, 12:42:15 PMnode: 38b47f05.288b9 Master Light Overhead : msg.payload : Object object name: "switch" currentValue: "on" dataType: "ENUM" values: array[2] 0: "on" 1: "off" value: "on" deviceId: "33" 4/7/2020, 12:42:18 PMnode: 38b47f05.288b9 Master Light Overhead : msg.payload : Object object name: "switch" currentValue: "off" dataType: "ENUM" values: array[2] value: "off" deviceId: "33" 4/7/2020, 12:42:47 PMnode: 38b47f05.288b9 Master Light Overhead : msg : Object object payload: object name: "switch" currentValue: "on" dataType: "ENUM" values: array[2] 0: "on" 1: "off" value: "on" deviceId: "33" topic: "Master Light Overhead" _msgid: "7ad4d8bb.7890a8"
So, does this mean that despite logging physical vs. digital that the maker API is not sending it to the NR node or does this mean that it is sending it, but the current iteration is not capturing that information into the node's output?
Second question, regarding physical after digital in a redundant manner. In the switches log, I see this:
[dev:33](http://192.168.86.110/logs#dev33)2020-04-07 01:05:06.315 pm [info](http://192.168.86.110/device/edit/33)Master Light Overhead was turned off [digital] [dev:33](http://192.168.86.110/logs#dev33)2020-04-07 01:03:44.217 pm [info](http://192.168.86.110/device/edit/33)Master Light Overhead is on [physical] [dev:33](http://192.168.86.110/logs#dev33)2020-04-07 01:03:21.870 pm [info](http://192.168.86.110/device/edit/33)Master Light Overhead was turned on [digital]
While the Maker API log shows:
4/7/2020, 1:03:22 PMnode: 38b47f05.288b9 Master Light Overhead : msg : Object object payload: object name: "switch" currentValue: "on" dataType: "ENUM" values: array[2] value: "on" deviceId: "33" topic: "Master Light Overhead" _msgid: "b64a567b.1ee7c8" 4/7/2020, 1:05:06 PMnode: 38b47f05.288b9 Master Light Overhead : msg : Object object payload: object name: "switch" currentValue: "off" dataType: "ENUM" values: array[2] value: "off" deviceId: "33" topic: "Master Light Overhead" _msgid: "3461d18f.73d31e"
This just points out that the Maker API seems to be ignoring the redundant on (physical) and never sends it to NR.
- Is that the right interpretation of that output?
- If so, is that because of anything I can choose in the Maker API to allow this to be passed?
- If it isn't a configuration choice, then I would have to ask for a change to the Maker API?
Finally, If I understand all of this correctly and these things are unlikely to be changed very rapidly, because the world doesn't revolve around me, is there any reason I couldn't build my own special purpose version of the maker API and the NR hubitat node to care for my particular desire to both pass physical vs digital and to pass redundant commands like the sequence I showed above? (other than programming skill level)