I have some working webcore piston that now generates error in the log and I m not sure what it could be, maybe not too bad but I would like to know what is wrong.
I have a piston that is triggered by url and store value in variables. I now got this error in the log:
My variable is dynamic and the argument is a number from 0 to 7... Its the first time I notice it and looks to store the data... and its the only variable to return this, all other looks good and are the 'same'.
Another log that is now there, from some piston where I use stay, or stay unchanged on some devices as trigger...
Not sure why I got this message & my stay unchanged are not working, I checked the log and the switch is changing, and I made a notification with the state of the switch and each time it have been toggled...I even add a buffer value.
The last one, I trigger a piston from inside another piston with argument. The argument is a number and get transfered well (I store the value in a variable when get called...) but the log show this:
I found this one: The stay unchange for 'variable' seconds was the issue. Since the variable is dynamics and I need a number, it looks like webcore dont translate it and I needs to use number(variable) instead...
Yeah, usually Webcore is good with figuring out the type conversions, but in this case it looks like it is not, possibly because of a hub update that changed something?
I would change the variable types to the specific types the errors are referencing for the type conversions. Where you are getting not valid for string, make sure you are using a variable that is explicitly a number.
If you are getting a value and then using it to update something else, and it is not getting converted correctly, maybe put a variable in-between that is the type you need to do the update.
yes, by using number(myvariable) it works... the only one I m not sure is the one that takes argument and store it in variable. I have multiple dynamics variable and the argument are always a number... but only one of them show the same kind of message... pretty weird!
Probably an update, I updated the hub few days ago... And its probably related to the stay unchanged event not working. All those things happens at the same time!
Is there a way to forward this to hubitat to get a new update?
I've seen people call out to support by name in a thread like this, such as @bobbyD, They may be able to relate the behavior to a change that was made in your release, but I don't think they support the Webcore app for any fixes needed.
I'm usually pretty quick to update, but I've seen enough issues posted with things breaking lately, I'm still on 2.4.0.148 until things settle down, especially with the Zwave updates.
Looks like its working now (webcore translate my variable again) but still have the log errors. I ll let the post there, maybe it would help and collect comments. I still dont know why it stopped working and came back to life...
