Ok, I uploaded the incorrect file... Please use this one:
http://cocoontech.com/forums/topic/19203-input-buttons/page__view__findpost__p__168098
http://cocoontech.com/forums/topic/19203-input-buttons/page__view__findpost__p__168098
Premise Considering Premise
- Thread starter video321
- Start date
Motorola Premise
Ha!!!!
I was just coming to post that my newbie self couldn't get anything to import but the locks and garage door modules.
I did get 2 errors during the addin process though:
LoadStringValue() failed for property 'LinkObject' on object 'sys://Schema/Modules/MiniBrowser/Classes/mbGarageDoorOpener/' -- contents: '{319C45F1-285C-41F3-959A-683DF5FEB120}'
The other one before it was related to Z-wave.
Some errors when starting Premise Control:
A script error occured while system deployed.
SYS Server is requesting script engine to continue.
The details of the error are as follows
LineNumber = 142
Description = Object doesn't support this property or method: 'home.SecuritySystem'
SourceElement = sys://Schema/Modules/MiniBrowser/GlobalScripts/MiniBrowserFunctions
sys://Schema/Modules/MiniBrowser/Classes/mbZWaveLock/
Subclass LinkObject not defined.
sys://Schema/Modules/MiniBrowser/Classes/mbGarageDoorOpener/
Subclass LinkObject not defined.
sys://Schema/Modules/MiniBrowser/GlobalScripts/MiniBrowserFunctions
A script error occured while system deployed.
SYS Server is requesting script engine to continue.
The details of the error are as follows
LineNumber = 142
Description = Object doesn't support this property or method: 'home.SecuritySystem'
SourceElement = sys://Schema/Modules/MiniBrowser/GlobalScripts/MiniBrowserFunctions
sys://Schema/Modules/MiniBrowser/GlobalScripts/MiniBrowserFunctions
A script error occured while system deployed.
SYS Server is requesting script engine to continue.
The details of the error are as follows
LineNumber = 142
Description = Object doesn't support this property or method: 'home.SecuritySystem'
SourceElement = sys://Schema/Modules/MiniBrowser/GlobalScripts/MiniBrowserFunctions
Minibrowser doesn't function.
Thanks for all the help!
A script error occured while system deployed.
SYS Server is requesting script engine to continue.
The details of the error are as follows
LineNumber = 142
Description = Object doesn't support this property or method: 'home.SecuritySystem'
SourceElement = sys://Schema/Modules/MiniBrowser/GlobalScripts/MiniBrowserFunctions
sys://Schema/Modules/MiniBrowser/Classes/mbZWaveLock/
Subclass LinkObject not defined.
sys://Schema/Modules/MiniBrowser/Classes/mbGarageDoorOpener/
Subclass LinkObject not defined.
sys://Schema/Modules/MiniBrowser/GlobalScripts/MiniBrowserFunctions
A script error occured while system deployed.
SYS Server is requesting script engine to continue.
The details of the error are as follows
LineNumber = 142
Description = Object doesn't support this property or method: 'home.SecuritySystem'
SourceElement = sys://Schema/Modules/MiniBrowser/GlobalScripts/MiniBrowserFunctions
sys://Schema/Modules/MiniBrowser/GlobalScripts/MiniBrowserFunctions
A script error occured while system deployed.
SYS Server is requesting script engine to continue.
The details of the error are as follows
LineNumber = 142
Description = Object doesn't support this property or method: 'home.SecuritySystem'
SourceElement = sys://Schema/Modules/MiniBrowser/GlobalScripts/MiniBrowserFunctions
Minibrowser doesn't function.
Thanks for all the help!
You can hit ignore for the link object errors. Since you don't have the z-wave lock module or the garage door module installed, seeing the linking error is normal. However, re-read the post found here: http://cocoontech.com/forums/topic/19203-input-buttons/page__p__168098#entry168098 I just added more instructions for you...
123
Senior Member
The errors you are seeing are a result of dependencies on components that are not part of a standard Premise installation.
One of the most difficult things to do (I suspect in all HA systems) is to develop applications that work well on your Premise system and equally well on someone else's Premise system. It's very easy to customize something to a point that becomes difficult to share with someone else because of a numerous dependencies on other components (found on your Premise system and nowhere else).
When I released MiniBrowser V2.0, I constrained its repertoire to standard, 'out-of-the-box' Premise objects that are part of every Premise installation (listed in the image above). As a result, it avoids the errors you are seeing when things it wants to find aren't present in your Premise system.
Does this mean that MiniBrowser is doomed to render only 'out-of-the-box' Premise objects and custom-made objects are left out in the cold? Nope.
When MiniBrowser encounters an unknown object (i.e. one not found in that list pictured above), it checks if the object has a function called "mbRenderPage" and executes it. So the author of a custom-made object simply needs to include an "mbRenderPage" function (that is responsible for generating a web-page suitable for display by MiniBrowser) and all is well. The custom-object and MiniBrowser remain separate entities with no dependencies.
One of the most difficult things to do (I suspect in all HA systems) is to develop applications that work well on your Premise system and equally well on someone else's Premise system. It's very easy to customize something to a point that becomes difficult to share with someone else because of a numerous dependencies on other components (found on your Premise system and nowhere else).
When I released MiniBrowser V2.0, I constrained its repertoire to standard, 'out-of-the-box' Premise objects that are part of every Premise installation (listed in the image above). As a result, it avoids the errors you are seeing when things it wants to find aren't present in your Premise system.
Does this mean that MiniBrowser is doomed to render only 'out-of-the-box' Premise objects and custom-made objects are left out in the cold? Nope.
When MiniBrowser encounters an unknown object (i.e. one not found in that list pictured above), it checks if the object has a function called "mbRenderPage" and executes it. So the author of a custom-made object simply needs to include an "mbRenderPage" function (that is responsible for generating a web-page suitable for display by MiniBrowser) and all is well. The custom-object and MiniBrowser remain separate entities with no dependencies.
For now, just create a security system under Home and name the object: "SecuritySystem."
The additions to minibrowser were never made generic by me as I got busy with other things.
I would also delete these classes completely:
sys://Schema/Modules/MiniBrowser/Classes/mbZWaveLock
sys://Schema/Modules/MiniBrowser/Classes/mbGarageDoorOpener
and these objects:
sys://Schema/Modules/MiniBrowser/Classes/ValidClasses/ZWaveLock
sys://Schema/Modules/MiniBrowser/Classes/ValidClasses/GarageDoorOpener
The additions to minibrowser were never made generic by me as I got busy with other things.
I would also delete these classes completely:
sys://Schema/Modules/MiniBrowser/Classes/mbZWaveLock
sys://Schema/Modules/MiniBrowser/Classes/mbGarageDoorOpener
and these objects:
sys://Schema/Modules/MiniBrowser/Classes/ValidClasses/ZWaveLock
sys://Schema/Modules/MiniBrowser/Classes/ValidClasses/GarageDoorOpener
123
Senior Member
video321, how's it going?
If you've deleted the classes listed above, etc6849's version of MiniBrowser should be working fine and you'll have a means of arming/disarming your M1 using (just about) any browser.
FWIW, if seeing SecurityZones, via MiniBrowser, is terribly important to you, I can whip up a patch that you can import. Otherwise you can simply wait for the next release of MiniBrowser that'll have it (and probably other things) included.
Let us know if you need more help.
If you've deleted the classes listed above, etc6849's version of MiniBrowser should be working fine and you'll have a means of arming/disarming your M1 using (just about) any browser.
FWIW, if seeing SecurityZones, via MiniBrowser, is terribly important to you, I can whip up a patch that you can import. Otherwise you can simply wait for the next release of MiniBrowser that'll have it (and probably other things) included.
Let us know if you need more help.
Man....you guys are all right 
ray:
I can't express enough how much I appreciate how fast you got me up and running. If it wasn't for the couple little bumps Premise would have been usable in less than an hour! That is impressive! I'll definitely keep an eye out for the updated minibrowser.
Also, if I wanted to connect the Z-wave controller to the M1G can I still use Premise to hold all of the scenes and programming and just send commands for the Elk to relay?
ray:I can't express enough how much I appreciate how fast you got me up and running. If it wasn't for the couple little bumps Premise would have been usable in less than an hour! That is impressive! I'll definitely keep an eye out for the updated minibrowser.
Also, if I wanted to connect the Z-wave controller to the M1G can I still use Premise to hold all of the scenes and programming and just send commands for the Elk to relay?
123
Senior Member
On behalf of everyone, you're welcome!
The ELK M1 driver I created supports Tasks. If you want to activate an ELK M1 Task, bind it to a Button object. Buttons are children of Keypad objects so you'll need to create a Keypad object first followed by a bunch of Buttons.
Home > New > Keypads > Keypad
Keypad > New > Button
NOTE: Premise's Button object has a default LED lamp which indicates the Button's state (ON=Green, OFF=Red). However, if the Button is simply used to trigger something then it's LED serves no purpose. When bound to an ELK M1 Task, a Button's LED will always be Red because a Task is considered to be stateless.
Keypads and Buttons are visible via AutomationBrowser but not in the current version of MiniBrowser. Don't lose heart because I have a beta version of MiniBrowser that supports them (see the attached image) plus SecuritySystem and SecurityZone objects.
The ELK M1 driver I created supports Tasks. If you want to activate an ELK M1 Task, bind it to a Button object. Buttons are children of Keypad objects so you'll need to create a Keypad object first followed by a bunch of Buttons.
Home > New > Keypads > Keypad
Keypad > New > Button
NOTE: Premise's Button object has a default LED lamp which indicates the Button's state (ON=Green, OFF=Red). However, if the Button is simply used to trigger something then it's LED serves no purpose. When bound to an ELK M1 Task, a Button's LED will always be Red because a Task is considered to be stateless.
Keypads and Buttons are visible via AutomationBrowser but not in the current version of MiniBrowser. Don't lose heart because I have a beta version of MiniBrowser that supports them (see the attached image) plus SecuritySystem and SecurityZone objects.
Attachments
2 things I noticed as I've used the security keypad via minibrowser/ppc:
1. I need to be very quick from the time I enter my security code to the time I hit stay/off/away - it needs to be done before the page refreshes (which isn't really an issue) except that with #2...
2. When I arm with stay or away the page doesn't automatically show the armed status. If I disarm then the page automatically refreshes to confirm and will show disarmed. With that said, manually hitting refresh will show the updated status for armed stay/away.
I'm assuming these behaviors are normal, but thought I would point that out for the updated minibrowser - if possible.
Thanks again, guys!
1. I need to be very quick from the time I enter my security code to the time I hit stay/off/away - it needs to be done before the page refreshes (which isn't really an issue) except that with #2...
2. When I arm with stay or away the page doesn't automatically show the armed status. If I disarm then the page automatically refreshes to confirm and will show disarmed. With that said, manually hitting refresh will show the updated status for armed stay/away.
I'm assuming these behaviors are normal, but thought I would point that out for the updated minibrowser - if possible.
Thanks again, guys!
What is the best way to organize my security system on the "Home" screen in builder?
I had to create a "SecuritySystem" object in the root for the minibrowser to function properly, so what is the ideal layout for zones, keypads, outputs, etc.?
Also, how do you make the non-existent Premise homepage NOT come up when opening builder?
I had to create a "SecuritySystem" object in the root for the minibrowser to function properly, so what is the ideal layout for zones, keypads, outputs, etc.?
Also, how do you make the non-existent Premise homepage NOT come up when opening builder?
123
Senior Member
I'll look at the issue of updating the Stay/Away status.
Yeah, when an automatic page refresh swings around, it erases whatever passcode you entered up to that point. If it happens just after you entered the passcode but just before you pressed Stay or Exit ... yup .. the passcode is toast and you have to start over. Just bad luck that the refresh occurred at that moment ... but think of it as a security feature: your passcode never lingers around to be revealed.
Feel free to adjust the automatic refresh period here (for PPC):
Modules > MiniBrowser > Templates > PocketPCRootObj > UIRefreshInterval
The value is in seconds and if set to 0 it disabled automatic refreshes.
FWIW, the beta version of MiniBrowser is making its rounds and offers a new feature that might interest you. If you are using an ELK M1 and QuickArm is enabled, you don't need to enter a passcode to arm Stay/Away. Naturally, you do need to include a passcode to disarm it.
Ideal layout for Security objects? FWIW, I put all SecurityZone objects as children (child-objects) of the SecuritySystem object. They don't show up in MiniBrowser (or AutomatIonBrowser) but that's the way I want it.
You can change Builder's startup URL to be anything you want. The URL is buried inside one of Premise's DLL files and you need a free utility program to modify it. This post explains how to do it.
Yeah, when an automatic page refresh swings around, it erases whatever passcode you entered up to that point. If it happens just after you entered the passcode but just before you pressed Stay or Exit ... yup .. the passcode is toast and you have to start over. Just bad luck that the refresh occurred at that moment ... but think of it as a security feature: your passcode never lingers around to be revealed.
Feel free to adjust the automatic refresh period here (for PPC):
Modules > MiniBrowser > Templates > PocketPCRootObj > UIRefreshInterval
The value is in seconds and if set to 0 it disabled automatic refreshes.
FWIW, the beta version of MiniBrowser is making its rounds and offers a new feature that might interest you. If you are using an ELK M1 and QuickArm is enabled, you don't need to enter a passcode to arm Stay/Away. Naturally, you do need to include a passcode to disarm it.
Ideal layout for Security objects? FWIW, I put all SecurityZone objects as children (child-objects) of the SecuritySystem object. They don't show up in MiniBrowser (or AutomatIonBrowser) but that's the way I want it.
You can change Builder's startup URL to be anything you want. The URL is buried inside one of Premise's DLL files and you need a free utility program to modify it. This post explains how to do it.
