Today loghooks can be used to interact with Hubitat, which is great.
http://[Hubitat_IP_Address]/apps/api/[App_ID]/devices/[Device_ID]/[Command]/[Value]?access_token=[Access_Token]
However, there may be times we wish to optionally pass additional data to log.
http://[Hubitat_IP_Address]/apps/api/[App_ID]/devices/[Device_ID]/[Command]/[Value]?access_token=[Access_Token]&log=[level],"Text"
This would be particularly useful when we wish to trigger an event and record supporting information.
Use case 1:
My doorbell (Unifi Doorbell G4 Pro) has fingerprint detection and my dog walker comes to the house and uses her fingerprint to unlock the door. I want to log the user’s name (well, fingerprint ID in this case as name is not available) in the log so I can identify who unlocked the door.
Use case 2:
My whole house generator kicks in and I wish to log status codes and load data when the house was on generator power. I use a virtual switch to indicate when I’m on generator, and want to pass this data when “turning on or off” the virtual switch.
There are obviously other things that someone might wish to pass through as simple log messages without writing a custom driver. The suggestion is to treat this as an optional parameter for backward compatibility, and default the log level if not passed to “info”