Jump to content

Configuration/Email/Customization


JSchumann

Recommended Posts

Just installed Insteon Smoke Bridge. I have a custom message as follows:

 

${sys.node.aa bb cc.name}

 

This should send whichever of the 7 node names that is 'on' in the message

 

Node examples from main page

aa.bb.cc-Smoke

aa.bb.cc-CO

aa.bb.cc-Test and so on

 

What I get is:

 

node[aa bb cc]

and 'aa b' is blue and underlined the rest of the text is black

 

Any ideas how to fix?

Link to comment

Well some progress.

 

The ISY links table does show a 1 (aa.bb.cc.1), so I put it in the customization. Now the message shows the node number and the word Smoke (when I press Test).

 

I was hoping that the appropriate of the 7 names would show up

 

Test for Test

CO for CO and so on

Link to comment

All nodes have a number associated with them, aa bb cc x, in the ISY. Devices such as SwitchLincs, LampLincs, ApplianceLincs always have a number 1 as there is only one node per device.

 

An 8 button KeypadLinc has 8 nodes numbered 1-8.

Button A is 1

Button B is 2

Button C is 3

etc

 

The full node identifier aa bb cc x is needed in the email messages.

 

The 1 is for the Primary/First node. If you want to see the value of another node for the same Insteon device use its node number.

Link to comment

You can see what each node has been assigned by entering ....

 

http://192.168.2.3/rest/nodes/

 

 

into a browser. The username/password will be solicited.

 

12 B9 D 1

KPL Floor Dimmer 6

1.27.54.63

true

0

0

0

12 B9 D 1

E13

12 B9 D 3

KPL Floor Dimmer 6 - A

12 B9 D 1

1.27.54.63

true

0

0

0

12 B9 D 1

F01

12 B9 D 4

KPL Floor Dimmer 6 - B

12 B9 D 1

1.27.54.63

true

0

0

0

12 B9 D 1

F02

12 B9 D 5

KPL Floor Dimmer 6 - C

12 B9 D 1

1.27.54.63

true

0

0

0

12 B9 D 1

F03

Link to comment

LeeG, Figured it out. Did what you said and found out each of the 7 has it's own number. So when I put that number in the message, that is the one sent.

 

I wanted the message to send the notification for the node that tripped. What I had to do was change the message from:

 

${sys.node aa bb cc 1.name} to

${sys.node.#.name}

 

The # pulls in the tripped node and sends it in the message.

 

Thanks

Link to comment

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...