Control some lights on ISY994 remotely from eISY

[MarkJames]

Since upgrading to eISY I've got my old ISY in a part time residence.  It's not worth it to me to upgrade to an eISY in this location as the installation is so small.  I'd like to use my portal/UD mobile app connection in my primary residence with an eISY to be able to control a few devices on my part time residence ISY994.  

So... to that end my rest command to turn on a light on my ISY994 would be something like http://myipaddress:myportforward/rest/nodes/10005/CMD/DOF.  This works fine - port forward and all.  But I'm struggling to turn this into a network resource that a program on the eISY can call.

What would be the exact network resource that I would need in my eISY to be able to send that rest command?  And is there a way for me to embed my username/password?  ie get/post, IP, port, path, and url encoding

 

Thanks in advance

 

mark

 

 

 

[William Olsen]

Mark, I use AI for coding quite often if I get stuck, it does make mistakes but I "trust but verify". I hope this helps!

To properly structure a **REST command** as a **network resource** for your **Eisy** device, you need to create a **Network Resource** entry in the **Admin Console** (or **UD Mobile**) that sends the appropriate command. Below are the steps and the correct formatting.

---

## **Steps to Add a Network Resource in Eisy**
1. **Open the Admin Console**  
   - Log in to **Eisy’s Admin Console**.
   - Navigate to **Configuration** → **Networking** → **Network Resources**.

2. **Click 'New'** to create a new network resource.

3. **Fill in the Details:**
   - **Name:** `Turn Off Node 10005` *(or any descriptive name)*
   - **Protocol:** `HTTP`
   - **Method:** `GET`
   - **Host:** `myipaddress`
   - **Port:** `myportforward`
   - **Path:** `/rest/nodes/10005/CMD/DOF`
   - **Encoding:** `UTF-8`
   - **Timeout:** `5-10 seconds` *(Default is fine)*
   - **Use SNI:** `Unchecked`
   - **User-Agent:** `Custom` *(optional, but useful for troubleshooting)*

4. **Authentication (If Needed)**  
   If your Eisy requires authentication for REST commands, you should add your credentials:
   - **Use Authentication:** ✅ `Checked`
   - **Username:** `admin`
   - **Password:** `yourpassword`

5. **Click 'Save'** and then **Test** to verify the command.

---

## **Alternative: Using HTTPS**
If your **Eisy** or **ISY Portal** requires HTTPS instead of HTTP, modify:
- **Protocol:** `HTTPS`
- **Port:** `443` *(or your secure custom port)*
- **Path:** `/rest/nodes/10005/CMD/DOF`

If your system requires **Basic Authentication in the header**, some setups may require manually including:
```http
Authorization: Basic base64(username:password)
```
However, Eisy usually handles authentication automatically when entered in the fields.

---

## **Triggering the Network Resource in ISY Programs**
Once your **Network Resource** is created, you can:
- Call it from **Eisy/ISY Programs** using `Network Resources → Run Resource`
- Assign it to **KeypadLinc / Scene Control**
- Use it in **Node Servers** (e.g., MQTT or Home Assistant integrations)

---

### **Testing the Network Resource**
After creating it:
1. **Right-click** → `Test` in the Admin Console.
2. If the device responds correctly, integrate it into ISY Programs.