I have old deleted scenes and notifications listed under scenes on my smartphone and at MO. Half my smartphone display is occupied with non-functional “scenes”. Locally on my Vera2 I cannot find the old scenes/notifications to remove them.
I would appreciate any help to eliminate these ghost “scenes”.
AFAIK, there is no way to remove these scenes (besides editing the config file …).
Using the Luup Lua extensions, you cannot tell whether a scene is a notification scene (which should be invisible on GUIs) or a regular scene.
If you client solely relies on the Luup Lua extensions, it cannot tell a notification scene from a regular scene.
I know this question could be to obvious. Have you checked you don’t have any filter on sections or rooms? Maybe the ghost scenes are hidden there.
@ Ap15e thank you.
Where is the config file and what editor is required to edit the file?
Can you please explain where I can use/look at the Luup Lua extension. Or point me in the direction that I can teach myself about the file formats. If I can find these ghost notifications/scenes, then I can create a unused room to put them in. By putting them in a non-existing unused room, they will not occupy display space.
http://wiki.micasaverde.com/index.php/Luup_Lua_extensions#variable:_scenes
There is no attribute ‘notification’ within luup.scenes. IMHO this is an API defect.
http://wiki.micasaverde.com/index.php/UI_Notes#Getting_the_system_configuration
Run the output through http://www.jsonlint.org/ (but note that the output may contain location information (latitude/longitude) and passwords in the clear (IMHO another defect …), that should be removed …) to get a nicely formatted output.
The structure of notification scenes is:
{ "name": "WZ tripped", "notification_only": 16723, "id": 70, "Timestamp": 1281046281, "room": 0 }It might be possible to change the room id and save the modified config file to /etc/cmh/user_data.json.lzo (use pluto-lzo from the OpenWRT command line to compress the config file). It might be necessary to adjust users.conf.timestamp.
DO SO AT YOUR OWN RISK! YOU MAY BRICK YOUR VERA!
A somewhat safer way would be to extract the scene id from user_data2 (id 70 in the example above) and try to remove the scene via http API (http://wiki.micasaverde.com/index.php/Luup_Requests#scene). There is no way to modify the room a scene belongs to - another API defect. Once again:
DO SO AT YOUR OWN RISK! YOU MAY BRICK YOUR VERA!
@ Ap15e thank you.
I was able to delete the scene using the instructions @ http://wiki.micasaverde.com/index.php/Luup_Requests#scene.
I also have a lot of scenes which are deleted in the UI but are showing in the data.
I’ve found the wiki document but I’m not clear exactly which text from Json I’m entering, I’ve tried a few things and have not managed to get anything to change. I’m sure this is quite simple once you know what you are doing, could anyone point me in the right direction ?.
I’ve understood it to be the below but clearly that’s not correct.
IPADDRESS:3480/data_request?id=(name of scene)=delete&scene=5