[solved] device:18 has duplicate state id

Plugins & Plugin Development Alternate UI
#1

I deleted a couple of workflows from AltUI which I implemented in PLEG.
Now i get

15.8.2017, 12:15:36 warning device:18 has duplicate state id 61 for variables: RemoteVariablesToWatch , Wflow_0-19_2 ? 49 15.8.2017, 12:15:36 warning device:18 has duplicate state id 60 for variables: VariablesToSend , Wflow_0-31_0 ? 49 15.8.2017, 12:15:36 warning device:18 has duplicate state id 59 for variables: VariablesToWatch , Wflow_0-19_0 ? 49 15.8.2017, 12:15:36 warning device:18 has duplicate state id 58 for variables: GoogleLastError , Wflow_0-18_2 ? 49 15.8.2017, 12:15:36 warning device:18 has duplicate state id 57 for variables: VoiceRSS_KEY , Data_CustomPages_0 ? 49 15.8.2017, 12:15:36 warning device:18 has duplicate state id 56 for variables: LocalBootstrap , Wflow_0-18_1 ? 49 15.8.2017, 12:15:36 warning device:18 has duplicate state id 55 for variables: LocalCDN , Wflow_0-18_0 ? 49 15.8.2017, 12:15:36 warning device:18 has duplicate state id 54 for variables: ExtraController , Wflow_0-17_3 ? 49 15.8.2017, 12:15:36 warning device:18 has duplicate state id 53 for variables: BackgroundImg , Wflow_0-17_2 ? 49 15.8.2017, 12:15:36 warning device:18 has duplicate state id 52 for variables: ImagePath , Wflow_0-17_1 ? 49 15.8.2017, 12:15:36 warning device:18 has duplicate state id 51 for variables: ThemeCSS , Wflow_0-17_0
device 18 is AltUI.
workflows 19 and 31 have been deleted but show up in the warnings.
I tried debug > fix device states a couple of times, reloaded luup engine, didn’t help.
What can I do to fix the problem?

#2

[quote=“pls90, post:1, topic:196971”]I deleted a couple of workflows from AltUI which I implemented in PLEG.
Now i get

15.8.2017, 12:15:36 warning device:18 has duplicate state id 61 for variables: RemoteVariablesToWatch , Wflow_0-19_2 ? 49 15.8.2017, 12:15:36 warning device:18 has duplicate state id 60 for variables: VariablesToSend , Wflow_0-31_0 ? 49 15.8.2017, 12:15:36 warning device:18 has duplicate state id 59 for variables: VariablesToWatch , Wflow_0-19_0 ? 49 15.8.2017, 12:15:36 warning device:18 has duplicate state id 58 for variables: GoogleLastError , Wflow_0-18_2 ? 49 15.8.2017, 12:15:36 warning device:18 has duplicate state id 57 for variables: VoiceRSS_KEY , Data_CustomPages_0 ? 49 15.8.2017, 12:15:36 warning device:18 has duplicate state id 56 for variables: LocalBootstrap , Wflow_0-18_1 ? 49 15.8.2017, 12:15:36 warning device:18 has duplicate state id 55 for variables: LocalCDN , Wflow_0-18_0 ? 49 15.8.2017, 12:15:36 warning device:18 has duplicate state id 54 for variables: ExtraController , Wflow_0-17_3 ? 49 15.8.2017, 12:15:36 warning device:18 has duplicate state id 53 for variables: BackgroundImg , Wflow_0-17_2 ? 49 15.8.2017, 12:15:36 warning device:18 has duplicate state id 52 for variables: ImagePath , Wflow_0-17_1 ? 49 15.8.2017, 12:15:36 warning device:18 has duplicate state id 51 for variables: ThemeCSS , Wflow_0-17_0
device 18 is AltUI.
workflows 19 and 31 have been deleted but show up in the warnings.
I tried debug > fix device states a couple of times, reloaded luup engine, didn’t help.
What can I do to fix the problem?[/quote]

debug > fix device states Is the only way
Enter 0-18 in the text box then wait until it reloads
That should do it

#3

i did that a couple of times.
Why are workflows mentioned in the warnings although already deleted?

#4

Variables remains in user data. Vera does not support variable delete.

#5

so my only option to get rid of the warnings is to delete the workflows in question and build from scratch?

#6

no that may not help. you basically have in your user_data several device variable associated to that device which have identical variable id. that can only be fixed by manually editing user_data json data structure ( complex & risky ) or by using the procedure that I indicated earlier. do not trigger the luup reload yourself, once you typed in te device id ( 0-18 ) let it go and observe the reload ( orange message button ) hapening by itself

#7

amg, I did as you suggested many times over the past week.
Finally the warning have stopped. Thank you for your patience.