- spriorMemberOctober 24, 2008 at 12:25 amPost count: 30
I’m trying to set a macro using a EZSnsRF as the watched device using the new firmware 1.57. There’s a “does:” pulldown which displays “Enter COmmand”, but that pulldown doesn’t actually have any choices. I also noticed that the new firmware doesn’t seem to be able to display the link table for the EZSnsRF – I can see responds to links on a LampLinc device which watched the EZSnsRF, but no controls links on the EZSnsRF itself.grif091MemberOctober 24, 2008 at 1:44 amPost count: 1001
This information is in the newly updated EZSrve Operating Guide available from the download section. Select Enter Command from the pulldown list. Press the keyboard delete key. Type 1100 into the Does: field for a macro that will trigger with an ON. Type 1300 into the Does: field for a macro that will trigger with an OFF.
Are you using the new SYNCH EZSERVE button on the Device Management screen to pull the link information from the EZSnsRF into EZSrve?spriorMemberOctober 24, 2008 at 2:10 amPost count: 30
Pressing the SYNCH EZSERVE button does pull the link information from other devices, but doesn’t seem to get anything at all from the EZSnsRF (which I know does currently have a link to a LampLinc).
I was able to enter the code of 1100 in a new macro for the EZSnsRF and it says it created the macro, but I still don’t understand how I’m supposed to know what code to put in there for each channel/group number the EZSnsRF has assigned to each RF channel (I’ve currently got both a driveway and a motion sensor). The other issue is that I’m really just trying to create a macro so that the link will be created and therefore I’ll get an XML notification on port 8002 when the Dakota senses motion – I don’t actually want the macro to turn any devices on/off. Is there a step by step to set this up?grif091MemberOctober 24, 2008 at 2:43 amPost count: 1001
There remains the limitation at 1.57 that a specific Group/Virtual Input cannot be identified on the If side of a macro.
Is your EZSnsRF new? In regard to not seeing active links.
Macro definitions do not create links. You create links through EZSrve Scenes Management or the Set button on the EZSnsRF device. I’d suggest using the Set button on the EZSnsRF for now as that process automatically associates a Virtual Input with a Dakota Alert frequency and Zone number as well as assigning a Group number to the Virtual Input which is used in the Controller and Responder link records. You can use the SHN Utility (free download) connected through EZSrve to view the Virtual Input information in the EZSnsRF to obtain the Group number being used be each active Virtual Input.spriorMemberOctober 24, 2008 at 4:05 amPost count: 30
My EZSnsRF is about a month old (bought new from smarthome.com).spriorMemberOctober 24, 2008 at 4:18 amPost count: 30
In case it helps the model info on the back of the EZSnsRF is: 2412S 0814 0D.FE.A4 v2.8 0009grif091MemberOctober 24, 2008 at 4:53 amPost count: 1001
It is possible that your EZSnsRF contains one of the new PLMs. Smarthome introduced a PLM with larger memory to accommodate more links. This pushes the link database start address higher than most other Insteon devices. Links established with the Set button are stored at the higher address by the PLM and retrieved by the PLM from the higher address when a Dakota Alert signal is received. That is why the links work even though outside legacy code cannot display them because that code only knows about the lower link database start address. At least that is the working assumption for your EZSnsRF. I have an EZIO8SA which came with one of the newer PLMs. Once I figured out why I could not display active link records in the new PLM, curiosity drove me to tweak the Utility. You really don’t need to see the link records to establish a working configuration but if you want to see them, and they really are at the higher address, I have a modified version of the SHN Utility that works at the higher link database address. It is a binary .exe file which cannot be attached to these forum entries. If you want to try my modified Utility send me a PM with an email address where I can send the new .exe and instructions on how/where to install it. The original SHN Utility is not lost and can be restored by renaming a file.
SHN is working on the Utility and should have a formal version that works with the higher database address but there is no target date.
As an update, it has been confirmed that this EZSnsRF is using the higher link database address associated with the larger memory size PLMs. The current 1.78 SHN Utility will not display active links in these new devices.grif091MemberOctober 27, 2008 at 8:58 pmPost count: 1001
The EZSrve 1.58 Image has expanded on the 1.57 enhancements such that Macros can be defined to trigger on a specific Group/Button number. Image 1.57 added the ability to enter a 4 digit hex number in a Timer Command: field and Macro Does: fields. The 4 digit hex number represents cmd1 and cmd2 values. This allows a Timer/Macro to issue an ON to a specific Bright level (1180) for example. Image 1.58 expands on this feature to allow the cmd2 value in the Macro If Does: field to represent a specific Group/Button number. An “If Device: KPL1 Does: 1103″ statement causes the Macro to fire only when an ON command from KPL1 button 3 is received by EZSrve. An “If Device: KPL1 Does: 1203” statement causes the Macro to fire only when a double tap Fast ON command from KPL1 button 3 is received. An “If Device: KPL1 Does: 1303” statement causes the Macro to fire only when an OFF command from KPL1 button 3 is received. This new capability applies to all the devices that supply a Group number on an inbound Group command sequence. This allows a Macro to trigger on a specific Virtual Input Group number from an EZSnsRF or EZX10RF, or a specific Input Group number from one of the EZIOxx family of devices.spriorMemberOctober 27, 2008 at 9:30 pmPost count: 30
Does 1.58 now have the ability to deal with the newest EZSnsRF devices which have a large links database? 1.57 didn’t have that as you’re personally aware…grif091MemberOctober 27, 2008 at 10:29 pmPost count: 1001
There are no changes to that area in 1.58. I take it the link that EZSrve Scene Management created did go to the lower address. Did you add the EZSnsRF device to EZSrve before or after installing the 1.57 image.GaryFunkMemberOctober 28, 2008 at 12:41 amPost count: 5
Hang about. Are you saying that the SimpleHomeNet devices are built inside a PLM?spriorMemberOctober 28, 2008 at 1:08 amPost count: 30
After upgrading the EZServ to FW 1.58 I deleted the device listing for the EZSnsRF and added it again. EZServ couldn’t add a link to it and it couldn’t retrieve the existing links from the device using the new “SYNCH EZSERVE” button. However the version of the SimpleHomeNet utility hacked by grif091 displays the links just fine when I check the “new PLM option”.
If I dump the devices3.xml file and look for the EZSnsRF entry I get the parameters:
Rec=”10″ name=”Dakota” ID=”0D.FE.A4″ DevCat=”0x0000″ Protocol=”2″ MSB=”0F” Status=”0″grif091MemberOctober 28, 2008 at 4:02 amPost count: 1001
sprior, thanks for the update. It is very useful information. I was not sure what would happen if you did that sequence and was reluctant to ask you to do that because of where it leaves you if it did not work. Until we can find a solution, you will have to use the Set button on the EZSnsRF to create the controller links or use EZSrve Scene Management to create the links which will give you the EZSrve side only and follow up with the modified Utility with the New PLM checked to create the corresponding controller of link records in the EZSnsRF itself. Unless you did a reset on the EZSnsRF, the Virtual Input records should be correct.
Earlier in the evening I opened up a conversation with SHN Support about your situation. At that time I did not know what would happen if you deleted and added the EZSnsRF device after uploading 1.57/1.58. You have filled in that blank which should be very helpful. I’ll pass the information on to SHN support. Thanks.
EDIT: I just reread your last post. If you feel like taking a chance, you can change the MSB value from 0F to 3F. That is the Most Significant Byte value for addressing memory. That is the change I made to the SHN Utility. When the New PLM is checked, the MSB starts out at 3F rather than 0F. Actually hold on that thought. I will try it on my EZIO8SA first and let you know.simplehomeMemberOctober 28, 2008 at 4:35 amPost count: 256
Version 1.57 introduced a new field in the device record where the MSB of the database is kept. This value is determined upon device addition and is “0f” for the small database and “3f” for the large one. However, if you can not add the device successfully, the default value for the small size will be used.
We have revised the firmware on several devices so they conform with the i2 commands for electronic linking, in which case the application does not need to know the location of the database since “peek/poke” is not used. The EZSrve firmware already has this feature but some older devices may not totally comply, which would explain why they would not add successfully.
Please call our support line should you desire to update one of your devices or if there are any questions regarding this post.
Please also note that there is no direct way to interrogate a device relative to its links database size. The application software (such as the EZSrve) must determine this size by “peek” and “poke” of locations in the device.grif091MemberOctober 28, 2008 at 4:39 amPost count: 1001
sprior, I changed the MSB value to 3F in my EZIO8SA devices3.xml file and did a SYNCH EZSERVE. EZSrve pulled the 5 active link records.
If you have not modified an XML file, do a LIST FILES. Right click on devices3.xml and select “save target as”, storing the file in a simple directory structure somewhere. I stored mine in c:/temp. There have been problems with complex directory structures containing blanks and/or dots. That may be fixed by now but I know c:/temp or something similar works. Edit the devices3.xml file with WordPad or something similar and change the MSB=0F to MSB=3F. Use the UPLOAD FILE to bring the modified devices3.xml file into EZSrve. Once you see the Successful Upload message, Restart (not Reset) EZSrve. Sorry if you already knew all this. Go into Device Management and try the SYNCH EZSERVE again.
The 5 active links in my EZIO8SA showed up in the Link Records: section and watching the Insteon traffic flow that SDM3 was tracing, the data was pulled starting at 3FF8. Let me know how this works for you.
- You must be logged in to reply to this topic.