SHM Clarification 2008-08-31T17:07:27+00:00

HOME Forums Software SimpleHomeNet Utility SHM Clarification

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • Anonymous
    Post count: 20
    #40050 |

    I’m reading the documents trying to understand how linking works so that I can do it using the utility as it appears I ahve devices not supported yet by the ezserrve. My questions are this:
    1) As I understand it, for two devices to communicate, you need two links. One link in the responder for the controller and one link in the controller for the responder.
    2) To do this I go to the manage device links tab, put in the address of my ezio at the device insteon ID(The device database I want to change), and add the ezserve address in the box labeled seccond insteon ID., as well as group one and controller, as I want the EZIO to control the EZServe. I hit creat new link button and it works.
    I now reverse the process with the EZSEvere address at the device insteon ID, and the EZIO address at the box labeled seccond insteon ID. group one, and responder. Just for saftey, I choose display existing link records button, to make sure I have no previous entries for this device, and I get the message (after four retries) “Insteon message timeout”. I get to same thing when I click on “Create new link record”.

    What am I missing here, if I am correct in my understanding that I need a link in both devices for the other device, yet the utility does not allow me to create both links? How should I be doing this for devices that my EZServer built in server does not understand or support?

    Anonymous
    Post count: 1001

    As SHN noted in their response to your earlier Topic on accessing the EZSrve link database while connected using EZSrve, that cannot be done. You do have full read/write access to the EZSrve link database when the SHN Utility is connected using a PLC.

    You are correct in that the Controller device requires a link record pointing to the responder device and the responder device requires a link record containing the controller device address. Those two link records together are considered one link. What EZIOxx device are you trying to link to the EZSrve. Perhaps I can help you get that device linked using EZSrve function rather than SHN Utility function.

    Anonymous
    Post count: 20

    Sorry it didn’t click in the other reply. But what I’m still not clear on now then is how to do what I want to do. IF I can’t create link in EZServe with SHn utility and from earlier post, (IF I underderstood correctly)because my exio2x4 nor EZSnRf are supported via the web interface. Do I need to buy another EZServe to get links into my original EZServe for the unsupported devices?

    My eventual goal, is to have either of my dakotas trigger via the EZSnRF to turn on my porch light togglelink for two minutes, and close relay two on my EZIO2x4 (which starts my camera and buzzes a buzzer) for two minutes.

    One final question regarding the SHN traffic tab. I assume, the sent side displays the traffic that the EZServe sent, and the received side is what the EZServe heard. When I see ” from ID:0C.B4.BA flags:2B cmd1:13 cmd2:0″ on the received side, it means the EZServe heard it, but ignored it, because it did not have a responder link for 0C.B4.BA? Is this correct?

    Jeff 🙂

    Anonymous
    Post count: 1001

    From the bottom up, the Insteon Traffic tab is displaying the messages issued by the SHN Utility and the responses received to those messages. It is not a generalized Insteon message trace. The “ignored” entry is a message which the SHN Utility received that was not in direct response to a message issued by the SHN Utility.

    As I indicated in your original EZSnsRF Topic, I added my EZSnsRF device to EZSrve and using EZSrve Scenes Management, created a Scene (link) between the EZSnsRF as a controller and the EZSrve as a responder. Also, as indicated in my previous post, I was able to trigger an EZSrve macro with a Dakota Alert Motion PIR signal once that Scene was created. There would be two macros to control your togglelink device. One macro would be triggered by the Insteon ON received from the EZSnsRF when it detects the Dakota Alert Motion PIR signal. This macro turns on your togglelinc. The second macro would be triggered by the Insteon OFF from the EZSnsRF when the Dakota Alert Motion PIR sends it’s off signal. The second macro would send a time delayed Insteon OFF to the togglelinc to turn it off. I did not use the SHN Utility to define any of that. My macros turned ON/OFF a LampLinc for my test but the approach would be the same for a togglelinc.

    I have a spare EZIO2X4 which I will add to my EZSrve using the same approach used with the EZSnsRF to confirm that I can add an EZIO2X4 device to EZSrve and create a Scene (link) with the EZIO2X4 using EZSrve Scenes Management function. I’ll post back the results of that test in a few days (holiday delay).

    You can read/write link records in the EZSrve link database with the SHN Utility when connecting using a PLC. I do that when I want to display the link records in my EZSrve link database. Have not found a need to create link records in the EZSrve that way as I have been able to create a Scene (link) using the EZSrve Scenes Management facility. That does not mean that you might not need or want to use the SHN Utility to create EZSrve link records. Just that I have not found that necessary so far. Also, the SHN Utility uses Smarthome’s SDM3 device interface to communicate with the PLC. The SDM3 interface has an Insteon message trace that can be viewed in the SDM3 window by double clicking on the blue T shaped Icon in the System Tray when SDM3 is executing.

    You should be able to add your EZSnsRF device to EZSrve using the technique I described in your original EZSnsRF Topic and create a Controller link between the EZSnsRF and the EZSrve using EZSrve Scenes Management. Post back if you have trouble doing that following the steps I outlined in your original EZSnsRF Topic.

    Anonymous
    Post count: 1001

    I can confirm with a direct test that an EZIO2X4 device can be added to EZSrve (select NO when asked if a link should be created) when the device Save is done. Once the EZIO2X4 device is defined it can be used in the “Then Device:” clause of a macro. The “Does:” field has an Output2-ON and Output2-OFF option which provides for Output Relay 2 to be turned ON or OFF with a macro. The macro can be triggered with an ON or OFF from an EZSnsRF. When an ON is received from the EZSnsRF a macro is triggered that turns ON the EZIO2X4 Relay 2. When an OFF is received from the EZSnsRF a macro is triggered that turns OFF the EZIO2X4 Relay 2 with a time delay. I confirmed with a meter that Relay 2 was turned ON and OFF with those two macros.

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.