Cloning scenes in openLuup and AltUI
-
I was trying to change the ID of a couple of scenes and came to the conclusion you can't do this without stopping openLuup, hacking user_data.json and restarting openLuup, which is a pain. (May be this could be added to openLuup ie be able change any scene ID to a non used one.)
So I figured I would try and clone some of the scenes with the idea that I could then manually swap their contents around. Why would I want to do this? Just to make my scene management a bit more simple as all my scenes call the one pile of Lua code. I also wanted to make use of unused scene IDs sprinkled through the scene ID list.
My understanding was the clone would occupy the first unused scene ID. Using AltUI, it just adds the clone on to the end of the list of scene IDs. In openLuup using the console page it failed to create the clone. Hits the URL OK:
http://openLuup:3480/console?action=clone&scene=14
Says this in the log:
GET /console?action=clone&scene=14 HTTP/1.1 tcp{client}: 0x2c05008
Searched high and low and no clones to be found.
I see that AltUI does a create when it clones:
openLuup.server:: GET /data_request?id=scene&action=create&json=WITH_ALL_THE_SCENE_INFO_HERE
Any ideas?
-
This is an inheritance from the vera UI which openLuup reproduced with great fidelity... Would be great if the scene ID could be made available as an editable property. I went through this same ordeal and I ended up indeed manually editing the user_data.json file with an editor. Idea for a feature request of the openLuup console maybe?
-
This is an inheritance from the vera UI which openLuup reproduced with great fidelity... Would be great if the scene ID could be made available as an editable property. I went through this same ordeal and I ended up indeed manually editing the user_data.json file with an editor. Idea for a feature request of the openLuup console maybe?
@rafale77 said in Cloning scenes in openLuup and AltUI:
Idea for a feature request of the openLuup console maybe?
I thought it did this already but if not, that's what I was suggesting in this post way back:
-
The only thing mentioned above not yet implemented is the clone button on the openLuup console scene pages. This is (and I hesitate to say this) an easy fix. It’s just that I never did finish writing the UI because AltUI seemed adequate for the time being. It turns out, though, that AltUI picks the next scene number, whereas openLuup would, indeed, fill in the blanks.
This should be fixed shortly, if I can get some time to do it. Whilst I fully understand that some people somewhere on the spectrum are worried about device numbers, I’ve not come across many who have the same issue with scene numbers.
-
The only thing mentioned above not yet implemented is the clone button on the openLuup console scene pages. This is (and I hesitate to say this) an easy fix. It’s just that I never did finish writing the UI because AltUI seemed adequate for the time being. It turns out, though, that AltUI picks the next scene number, whereas openLuup would, indeed, fill in the blanks.
This should be fixed shortly, if I can get some time to do it. Whilst I fully understand that some people somewhere on the spectrum are worried about device numbers, I’ve not come across many who have the same issue with scene numbers.
-
People tell me all the time I'm on the artistic spectrum. Regardless looking forward to everything being lined up from lowest to highest with no holes. And it's surely AltUI not ALTUI.
@a-lurker said in Cloning scenes in openLuup and AltUI:
People tell me all the time I'm on the artistic spectrum.
That's absolutely fine - you are not alone.
Development version v20.12.31 of openLuup implements the scene clone functionality (from the openLuup console Scene page) with new scene numbers filling in empty slots.
Happy New Year.