Premise Home Icon with red line through it

Motorola Premise

Shinyshoes

Member
I noticed recently that the home icon in the Premise builder has a red circle with a line through it. I have attached an screenshot of this.

It doesn't seem to be affecting anything, but then again, I dont have a lot of stuff connected in premise yet.

Anyone know why this is like this, what it means, and how to get rid of it?

Thanks in advance.
 

Attachments

  • premise home icon1.jpg
    premise home icon1.jpg
    20.2 KB · Views: 6
That icon is displayed when an object is disabled.
  • For example, right-click the "Ensuite" object and click "Properties".
  • Look in the "Attributes" section, locate "Disabled" and select it. Click "Apply".
  • The Ensuite object will now be displayed with red-slash icon (as well as all its child-objects).
  • Uncheck "Disabled" and click "Apply" to restore it.
Now for the core problem: right-clicking the Home object will not display its Properties.


I don't know how you arrived at this condition but here's a guess: did Premise ever display an error message, like maybe something about the Script Queue exceeding its limit, and of the four possible options (View, Disable, Ignore, Ignore All) you chose Disable?

It's possible that "Home" is not truly disabled. Maybe one of Premise's internal services is disabled and Builder has no way of indicating that condition other than by showing "Home" as being disabled. I say this because, under normal circumstances, if you disable an object, its children are disabled as well and, based on the image you posted, that's simply not true for you.

Here's something you might want to try. Create a backup (File > Backup) and open the resulting file with a good text-editor (Notepad++) that knows how to display XML data. Within the XML data, an object's Properties are known as "Flags" and are represented by a hexadecimal number. Search for an object whose "Flags" is set to 0x10. Hex 10 represents Disabled=true. If the object has multiple attributes enabled then it will have a value other than hex 10 and this search will not find it. Even so, it's worth trying it in order to learn if something deep within Premise is disabled. Let us know what you find (if anything).
 
123

Thanks for the extremely comprehensive reply! Yes, I have seen the "Script Queue limit exceeded" error message before, but I usually click ignore (this has happened quite a bit lately while I am debugging my new Nuvo Grand Concerto Driver). I guess it is possible that I clicked the wrong button one of those times.......

I will do the notepad++ search tonight and update you tomorrow. Thanks again.
 
I did as you requested an there are no items that match "0x10" for the flags. If open the properties on any of my rooms in Premise builder it shows that it is disabled and the disabled option is greyed out so I can't enable it.....

I guess now I am stuck at re-loading an old backup and re-applying my changes?
 
I would continue to study the xml file. The answer has always been in there when I messed something up and it has saved me more than once too! If you go to monitor.events do you see an event that shows home as the link object? If not home, what object?

If you suspect home, try searching for Class="sys://Schema/Home/Property" in the xml file. Since I have the Elk module and the occupancy module installed, some of my home properties may be different, but I've pasted what mine looks like so you can compare the flags. My home object shows: Flags="0x120400." This is because the Flag value of 0x120400 is really several flag values OR'ed together (0x100000 + 0x020000 + 0x000400)...

Code:
<Object ID="{4F846CA8-6603-4675-AC66-05A0AF6A8ACD}" Name="Home" Flags="0x120400" Class="sys://Schema/Home/Property" DisplayName="Home (Occupied)" LastOccupied="3/7/2012 2:49:05 PM" OldDisplayName="Home" OccupancyCount="141868" OccupancyLastTrigger="Entry (Occupied) Motion" OccupancyTimeTriggered="3/7/2012 4:51:53 PM" LastZoneTriggered="DWN_ENTRY_MOT (58)" SecurityState="1" CoolingSetPoint="294.538888888889 K" StatusLastFunction="Disarmed, 3/7/2012 4:09:32 PM" LastStateChange="Ready To Arm but a zone is violated and can be Force Armed, 3/7/2012 4:09:32 PM" PowerState="-1" SecurityReady="-1" Temperature="296.483333333333 K" LastFunction="Disarm, 3/7/2012 2:49:07 PM" Brightness="0.15" HeatingSetPoint="291.483333333334 K" >

PS: Forgot to mention 123's old post detailing the use of Flags: http://cocoontech.com/forums/topic/13849-use-flags-to-create-better-drivers/page__view__findpost__p__117759

This old post is/was very useful post for me; thanks 123!
 
I've been able to simulate the problem you're experiencing. If the Home object is disabled, none of its child-objects are displayed with a red-slash yet thet are definitely disabled.

Right-click Home, click Export followed by OK.
Supply a file name and click OK.

Make a copy of this file. I repeat, make a copy of this file. If things go wrong, you can restore from the copy.

Open the file with a text-editor.
Here's what the third line looks like on my Test System when Home is NOT disabled:
<Object ID="{4F846CA8-6603-4675-AC66-05A0AF6A8ACD}" Name="Home" Flags="0x120400" Class="sys://Schema/Home/Property" DisplayName="Large Home Model" >
If the third lime in your file looks like this:
<Object ID="{4F846CA8-6603-4675-AC66-05A0AF6A8ACD}" Name="Home" Flags="0x10" Class="sys://Schema/Home/Property" DisplayName="Large Home Model" >

Or if the Flags value is anything other than 0x120400, then you'll need to set it to 0x120400.

Assuming you've changed Flags to 0x120400, return to Builder and proceed to delete all objects below Home but do not delete Home.
Right-click Home, click Import, and select the edited file. Premise may report errors while importing Media Zones; be sure to select Ignore.

You should now have a Premise Home that is not disabled. You may have to right-click each child-object and ensure Disabled is unchecked.
 
An oldie, but a goodie!  Thanks for this lifesaver... :D
 
Back
Top