-
AuthorPosts
-
AnonymousInactiveJanuary 14, 2009 at 6:55 pmPost count: 29
Folks, I am new to the EZServe/EZSrve and have a few questions that I couldn’t find scanning this wiki. Here they are:
1) Is it possible to set the dimmer value on a timer to something other than a multiple of 20%?
2) It seems that each timer is linked to a single device. Is there a way to create a timer that controls several devices?
3) How can I customize a timer so that the light ramps on rather than goes immediately to the setting?Many Thanks!
AnonymousInactiveJanuary 14, 2009 at 9:20 pmPost count: 1001You can use an EZSrve Scene (Insteon Group) to accomplish what you are looking for. Create a Scene (Group) with EZSrve as the Controller with one or more devices as Responders. Each device linked as a Responder has a unique set of LD1,LD2,LD3 values. LD1 is the Bright level of the device being turned ON, LD2 is the Ramp rate to use to reach that Bright level, LD3 is the device output Unit number. The output Unit number is 00 for most Responders (LampLinc, ApplianceLinc, SwitchLinc, etc). For a KeypadLinc LD3 is the button number (1-8) to be controlled. For SimpleHomeNet devices that have multiple outputs, it is the output unit number to be controlled. For example, an EZIO2X4 has two output units (relays) where LD3=00 specifies relay 1 and LD3=01 specifies relay 2. The Timer specifies the name of the Scene rather than the name of an individual device.
EDIT: the LD1,LD2,LD3 fields are two digit hex numbers. Refer to the EZSrve User Guide for details on entering absolute hex values into these fields rather than selecting one of the predefined Bright level / Ramp rate values. The ability to enter absolute hex values allows any Bright level or Ramp rate the Responder device supports.
AnonymousInactiveJanuary 15, 2009 at 2:54 amPost count: 29I was headed that way, but when I try to add the EZServe as a controller, say as unit 02, I get this error: “Cannot Add! Device Either not Present or Inactive”. It has to be present because it has been turning on my lights for a month!
AnonymousInactiveJanuary 15, 2009 at 12:48 pmPost count: 1001From the Server Configuration screen click on Restart (not Reset) to reboot EZSrve. Login to EZSrve in a new IE browser session and see if you can use Device View/Control to manually turn on/off one of your devices. If this works then try creating a new scene with EZServe as the Controller.
AnonymousInactiveJanuary 15, 2009 at 4:24 pmPost count: 29Thanks. I tried it, and I am able to control devices, and poll their status. Timers work too. Attached is the screen shot of what I was doing after the restart and the error shown. This is, of course, after I selected EZServe from the pulldown (the pulldown resets to the capture after the error).
AnonymousInactiveJanuary 15, 2009 at 4:34 pmPost count: 29The other strange thing is, my Smarthome Homelinc V2 found it when it spidered my Insteon devices, so the network knows it is there.
AnonymousInactiveJanuary 15, 2009 at 5:01 pmPost count: 55I’m not sure this applies to your situation, but I ran into difficulties adding new scenes when the number of links specific to the EZSrve was greater than 64. In my situation, I was trying to add a scene where the EZSrve was a responder and the scene would get added but disappear on reboot. You may want to check your devices3.xml file. If there are 64 EZServe links on the EZSrve device (as opposed to total links), you probably won’t be able to add more.
Good luck…
AnonymousInactiveJanuary 15, 2009 at 5:52 pmPost count: 1001Display the devices3.xml file and check the EZServe device entry against mine shown below and look for anything unexpected. You are particularly interested in the ID= value to be sure it is the Insteon address of your EZSrve and that the Status= field is 0. To Display the devices3.xml file, click on List Files on the Server Configuration screen. This will display a separate window with the list of xml files in EZSrve. RIGHT click on the devices3.xml entry and select Open in new window.
.
.The 64 link record limit mentioned by SCSweet is a known limitation for which SHN is actively working on a change. Look at the number of link records listed under the EZServe device entry.
AnonymousInactiveJanuary 15, 2009 at 9:00 pmPost count: 29Will check the insteon address when I get home and can see it respond from HomeLinc.
–
–
––
AnonymousInactiveJanuary 15, 2009 at 9:03 pmPost count: 29It must be the correct address, because later in the same devices.xml, you can see the reverse linking:
–
––
–
–<Link Rec="2" ID="01.7E.A8” Grp=”01″ Cntrlr=”0″ LD=”00-00-00″ />
AnonymousInactiveJanuary 16, 2009 at 2:53 amPost count: 1001I traced the command activity on mine when I added EZServe as the Controller to a new scene. The only command issued is a Status Request 0x19 command which echo’s back with 0x00 status. Use the SHN Utility to trace the command sequence when you add EZServe to a new Scene. Perhaps it is responding with some status that does not permit the Scene creation process to continue. The following are the SndIns and InStdMsg messages from the log.txt file when I added EZServe as the Controller.
A few housekeeping questions, is this a new EZSrve or EZBridge? What image level are you running on? Was it purchased from SimpleHomeNet or SmartHome? It is the first time I have seen an Insteon device address start with 0x01. Is this the first Scene you are trying to create with EZServe as a Controller?
Message : 9:04:15 PM Thursday, January 15, 2009
:
:
GetRevisionRevision 01.59
Message : 9:09:34 PM Thursday, January 15, 2009
:
:
SndIns
0X2
0X62
0X6
0X4C
0XA5
0XF
0X19
0X00
0X6
Message : 9:09:34 PM Thursday, January 15, 2009
:
:
InsStdMsg
0X2
0X50
0X6
0X4C
0XA5
0X6
0X4C
0XA5
0X3
0X19
0X00
AnonymousInactiveJanuary 16, 2009 at 3:42 pmPost count: 29Housekeeping..
It is an EZServe purchased in December preloaded with 1.59 as indicated in the screen shot. I got it from SimpleHomeNet (SmartHome sells somthing similar at a lower cost, but also much lower function). I agree, I haven’t any other devices that start with 01.xx.xx . I’ll run that trace over the weekend. This is the very first scene I’m trying to create. I was never able to figure it out, therefore turned to this forum.
The other strange thing was the box it came in just had the device, two! Ethernet cables, and nothing else. Smacks of open boxed goods. But, I kept a stiff upper lip.
AnonymousInactiveJanuary 16, 2009 at 4:32 pmPost count: 1001Thanks for the information. I thought the posted screen shot image was static. Just realized the scroll bar was actually functional. Sorry about that. Coming from SHN directly I would believe the internal PLM is the very latest. The question here is that the Status Request command being issued by EZSrve to test the availability of the controller device results in the command being issued to itself. The concept of EZSrve issuing commands to itself to perform the device SYNCH functions has been shown not to work. There was a functional change made to EZSrve a few images back to change the way EZSrve does a SYNCH operation because of that very situation. I was surprised to see the Status Request command actually coming back looking as though it was successful. The concern is the latest run of PLMs from Smarthome may have changed the way the Status Request command is being processed, bring it into line with the way other commands are processed. If that is so the Status Request may not be working on your EZSrve when it is used to query itself. This would make it consistent with the way the PLM handles other commands that are issued to itself. I’m hoping the xml trace will answer that question.
AnonymousInactiveJanuary 20, 2009 at 12:58 amPost count: 3I am having exactly the same problem with an Ezsrve purchased direct from Simplehomenet at the beginning of January 2009 (1.59 loaded). I cannot create a new scene using the Ezsrve and get the same “Cannot add!….” error message. I know the Ezsrve controller works – I have added the default_01 scene to a timer as a test and it runs right on the money but no matter what I do I cannot add a new scene using the Ezsrve controller. So I am going to watch this thread with great interest. Meanwhile if I stumble across a fix I’ll be sure to post it.
AnonymousInactiveJanuary 20, 2009 at 1:39 amPost count: 29Here is the results from the Insteon Traffic test using 1.80 version of the SHN Utility. I’ve connected to my EZSrve, and can monitor traffic from querys ETC. So, the utility is working. However when I go to add the EZSrve as a controller for a scene, there is no traffic. Nothing seems to be on the line.
-
AuthorPosts
- You must be logged in to reply to this topic.