WebCore Error with 2.3.4.120, Strange Command

[fieldsjm]

Receiving unusually log warnings, the log is not specific to any piston, associated with the base webcore instance. Below are a couple examples but there are about 30 of them at the same time.

app:132022-12-16 11:22:18.585 AMwarnStrange command SystemDisarm with commands [n:SystemDisarm, p:[null], cm:true] has nulls
app:132022-12-16 11:22:18.583 AMwarnStrange command SystemArm with commands [n:SystemArm, p:[null], cm:true] has nulls
app:132022-12-16 11:22:18.442 AMwarnStrange command toggleSoundMode with commands [n:toggleSoundMode, p:[null], cm:true] has nulls
app:132022-12-16 11:22:18.439 AMwarnStrange command togglePictureMode with commands [n:togglePictureMode, p:[null], cm:true] has nulls
app:132022-12-16 11:22:18.364 AMwarnStrange command toggleSoundMode with commands [n:toggleSoundMode, p:[null], cm:true] has nulls
app:132022-12-16 11:22:18.361 AMwarnStrange command togglePictureMode with commands [n:togglePictureMode, p:[null], cm:true] has nulls
app:132022-12-16 11:22:17.466 AMwarnStrange command inactive with commands [n:inactive, p:[null], cm:true] has nulls
app:132022-12-16 11:22:17.463 AMwarnStrange command active with commands [n:active, p:[null], cm:true] has nulls
app:132022-12-16 11:22:17.460 AMwarnStrange command SystemDisarm with commands [n:SystemDisarm, p:[null], cm:true] has nulls
app:132022-12-16 11:22:17.458 AMwarnStrange command SystemArm with commands [n:SystemArm, p:[null], cm:true] has nulls
app:132022-12-16 11:22:17.419 AMwarnStrange command SystemDisarm with commands [n:SystemDisarm, p:[null], cm:true] has nulls
app:132022-12-16 11:22:17.416 AMwarnStrange command SystemArm with commands [n:SystemArm, p:[null], cm:true] has nulls
app:132022-12-16 11:22:17.414 AMwarnStrange command MotionDetectionEnable with commands [n:MotionDetectionEnable, p:[null], cm:true] has nulls
app:132022-12-16 11:22:17.411 AMwarnStrange command MotionDetectionDisable with commands [n:MotionDetectionDisable, p:[null], cm:true] has nulls
app:132022-12-16 11:22:15.552 AMwarnStrange command SystemDisarm with commands [n:SystemDisarm, p:[null], cm:true] has nulls
app:132022-12-16 11:22:15.548 AMwarnStrange command SystemArm with commands [n:SystemArm, p:[null], cm:true] has nulls
app:132022-12-16 11:22:15.395 AMwarnStrange command toggleSoundMode with commands [n:toggleSoundMode, p:[null], cm:true] has nulls
app:132022-12-16 11:22:15.392 AMwarnStrange command togglePictureMode with commands [n:togglePictureMode, p:[null], cm:true] has nulls
app:132022-12-16 11:22:15.308 AMwarnStrange command toggleSoundMode with commands [n:toggleSoundMode, p:[null], cm:true] has nulls
app:132022-12-16 11:22:15.305 AMwarnStrange command togglePictureMode with commands [n:togglePictureMode, p:[null], cm:true] has nulls
app:132022-12-16 11:22:14.317 AMwarnStrange command inactive with commands [n:inactive, p:[null], cm:true] has nulls
app:132022-12-16 11:22:14.314 AMwarnStrange command active with commands [n:active, p:[null], cm:true] has nulls
app:132022-12-16 11:22:14.312 AMwarnStrange command SystemDisarm with commands [n:SystemDisarm, p:[null], cm:true] has nulls
app:132022-12-16 11:22:14.309 AMwarnStrange command SystemArm with commands [n:SystemArm, p:[null], cm:true] has nulls
app:132022-12-16 11:22:14.257 AMwarnStrange command SystemDisarm with commands [n:SystemDisarm, p:[null], cm:true] has nulls
app:132022-12-16 11:22:14.254 AMwarnStrange command SystemArm with commands [n:SystemArm, p:[null], cm:true] has nulls
app:132022-12-16 11:22:14.251 AMwarnStrange command MotionDetectionEnable with commands [n:MotionDetectionEnable, p:[null], cm:true] has nulls
app:132022-12-16 11:22:14.249 AMwarnStrange command MotionDetectionDisable with commands [n:MotionDetectionDisable, p:[null], cm:true] has nulls

Started appearing after update to 2.3.4.120.

Doesn't seem to be interfering with any particular piston.

[nh.schottfam]

Can you let me know what device handler that is? (or point me to GitHub for it)?

The warning is benign, but I want to see what is going on in the drivers.

This is the 2nd case I've seen of a driver with weird command definitions not providing the data types.

[fieldsjm]

The logs above in IDE are coming from the App, WebCore v0.3.114.20220203. I have not been able to associate the warning with a specific device. Automations appear to be running correctly.

Do you want to gitHub for the app?

I updated the log above to include the full list so you can see the variety of "strange" commands.

[nh.schottfam]

In your device handlers you can see the commands they offer.

It looks like a Tv driver of some type

Looks like some kind of security device/panel of some type

I'll try to update the message to include the device name.

Really strange device driver coding I expect.

[fieldsjm]

I can start narrowing them down....

The TV driver would be the custom driver called Samsung TV Remote, it contains the togglePicturemode, etc commands

systemArm/systemDisarm would be from the Blink Sync Module
https://www.drdsnell.com/projects/hubitat/drivers/BlinkChild-SyncModule.groovy
part of

[PROJECT] Driver for Blink API

UPDATE - November 8th, 2022 On November 3rd, 2022 the Blink servers were updated to block certain User-Agents. The driver has now been updated (November 8th, 2022) to get this working again and a longer-term solution to this problem will be added in the future. Thanks to @tomw for the idea about the User-Agent. Description: Drivers for polling the Blink API for your Blink cameras and related devices. BlinkAPI.groovy = REQUIRED BlinkChild.groovy = REQUIRED BlinkChild-Network.groovy = R…

active and inactive could be a number of devices ¯_(°_°)_/¯

[nh.schottfam]

Again the error is benign, but the devices have some weird definitions:

In the TV driver:

command "toggleInputSource", [[name: "SmartThings Function"]]

it should be:

command "toggleInputSource"

Typically commands should be

command "name", "string"

or more complex:

command "playWeather", [[name: "Set Volume", type: "NUMBER", description: "Sets the volume before playing the message"],[name: "Restore Volume", type: "NUMBER", description: "Restores the volume after playing the message"]]

Notice there is a type

In the blink driver

Same issue, no type for the arguments:

command "SystemArm", [ [ name: "This will Arm system Sync Module is on" ] ]

ie it should be

command "SystemArm"

Ie the arguments are parameters, and in both causes the author's seem to think they can use this for some form of documentation.

In both cases if you remove the 'non parameters', this will resolve it as the command actually do not have parameters.

[snell]

This was a method that was recommended to me as a way to include some information for the users to know what commands might actually DO as there is not a way to display information otherwise for commands (on the device page) unless you include parameters and my commands do not need parameters in these cases.

This does not appear to be "outside" the guidelines for command formatting.

[nh.schottfam]

Those are command parameters like setLevel(level)

webCoRE is trying to fill into the IDE for it to understand parameters and valid levels.

I have not seen an HE driver do whatever it is folks are trying to do here.

[snell]

Below is an image of what this code results in on the device's page. Quite simple description point for the driver. Part of the reason for this (at least for my drivers) is that the SystemArm command is related to the parent device's Arm System command (it actually is the same behind the scenes). BUT when it is coming from a child device it does not need the user to enter the parameters like it would on the parent (which needs to know which Network to Arm, whereas the child knows what Network it is part of and can provide it).

I added these methods in for some driver commands (primarily my Blink ones but I think I use it on others) a year or two ago when I was trying to find a way to add some message here. Since Hubitat has no built-in method this was recommended to me as a way to have some message displayed for the end-user. Unless you know of some other method... I would love to have a proper tooltip or equivalent but I do not know when/if that is on their roadmap.

[fieldsjm]

@nh.schottfam Thanks for clarifying, i'm glad it is benign and now I can just ignore. My ocd freaks out when a muliple of logs pop up unexpectedly.

@snell I do appreciate the description on commands, i've always wondered why there wasn't a more clean cut way to do this.

[snell]

Thanks. It bothers me though that I am causing errors (even benign errors) with someone else's stuff though also... so I am trying to find a better way for a description but no luck yet.