ISY Insteon 3.0.0.54 - Beta 54 for HS3

[rjbur]

Thermostat CALL Not working

******** UPDATE *******
** Version 3.0.0.10 Alpha **

I upgraded and I even first deleted the thermostat devices per install notes...

It seems that CALL is still not updating the status of the HVAC system.

Here is the ISY Event Log showing the traffic when I choose the Cooling Mode.

Thu 07/31/2014 09:57:55 PM : [INST-TX-I2CS] 02 62 1E 0D C8 1F 6B 05 00 00 00 00 00 00 00 00 00 00 00 00 00 90
Thu 07/31/2014 09:57:55 PM : [INST-ACK    ] 02 62 1E.0D.C8 1F 6B 05 00 00 00 00 00 00 00 00 00 00 00 00 00 90 06        (05)
Thu 07/31/2014 09:57:56 PM : [INST-SRX    ] 02 50 1E.0D.C8 28.CE.74 2B 6B 05           (05)
Thu 07/31/2014 09:57:56 PM : [Std-Direct Ack] 1E.0D.C8-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 07/31/2014 09:57:56 PM : [   1E D C8 1]    CLIMD   2
Thu 07/31/2014 09:58:02 PM : [INST-SRX    ] 02 50 1E.0D.C8 28.CE.74 01 70 02           (02)
Thu 07/31/2014 09:58:02 PM : [Std-Direct  ] 1E.0D.C8-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 07/31/2014 09:58:02 PM : [INST-TX-I2CS] 02 62 1E 0D C8 1F 2E 02 00 00 00 00 00 00 00 00 00 00 00 00 92 96
Thu 07/31/2014 09:58:03 PM : [INST-ACK    ] 02 62 1E.0D.C8 1F 2E 02 00 00 00 00 00 00 00 00 00 00 00 00 92 96 06        (02)
Thu 07/31/2014 09:58:03 PM : [INST-SRX    ] 02 50 1E.0D.C8 28.CE.74 2B 2E 02           (02)
Thu 07/31/2014 09:58:03 PM : [Std-Direct Ack] 1E.0D.C8-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 07/31/2014 09:58:04 PM : [INST-ERX    ] 02 51 1E 0D C8 28 CE 74 11 2E 02 01 04 02 33 26 30 50 33 01 0F E1 45 07 97 
Thu 07/31/2014 09:58:04 PM : [Ext-Direct  ] 1E.0D.C8-->ISY/PLM Group=0, Max Hops=1, Hops Left=0

Here is the HS3 Log for the time-frame that overlaps:

Jul-31 9:58:03 PM	 	ISYInsteon	Event Queue is now empty.
Jul-31 9:58:03 PM	 	ISYInsteon	ProcessEvent : NOT HANDLED: Unsupported ISY message: C=_7 A=1 N=
Jul-31 9:58:03 PM	 	ISYInsteon	Add : Event added to queue. Queue size = 1
Jul-31 9:58:03 PM	 	ISYInsteon	parse_event : control = [_7] action = [1] node = [] eventinfo = [[Ext-Direct ] 1E.0D.C8--{0x3E}ISY/PLM Group=0, Max Hops=1, Hops Left=0]
Jul-31 9:58:03 PM	 	ISYInsteon	parse_event : Entering parse event with {0x3C}Event seqnum="6260" sid="uuid:66"{0x3E3C}control{0x3E}_7{0x3C}/control{0x3E3C}action{0x3E}1{0x3C}/action{0x3E3C}node{0x3E3C}/node{0x3E3C}eventInfo{0x3E}[Ext-Direct ] 1E.0D.C8--{0x3E}ISY/PLM Group=0, Max Hops=1, Hops Left=0{0x3C}/eventInfo{0x3E3C}/Event{0x3E00}
Jul-31 9:58:03 PM	 	ISYInsteon	Event Queue is now empty.
Jul-31 9:58:03 PM	 	ISYInsteon	ProcessEvent : NOT HANDLED: Unsupported ISY message: C=_7 A=1 N=
Jul-31 9:58:03 PM	 	ISYInsteon	Add : Event added to queue. Queue size = 1
Jul-31 9:58:03 PM	 	ISYInsteon	parse_event : control = [_7] action = [1] node = [] eventinfo = [[INST-ERX ] 02 51 1E 0D C8 28 CE 74 11 2E 02 01 04 02 33 26 30 50 33 01 0F E1 45 07 97 ]
Jul-31 9:58:03 PM	 	ISYInsteon	parse_event : Entering parse event with {0x3C}Event seqnum="6259" sid="uuid:66"{0x3E3C}control{0x3E}_7{0x3C}/control{0x3E3C}action{0x3E}1{0x3C}/action{0x3E3C}node{0x3E3C}/node{0x3E3C}eventInfo{0x3E}[INST-ERX ] 02 51 1E 0D C8 28 CE 74 11 2E 02 01 04 02 33 26 30 50 33 01 0F E1 45 07 97 {0x3C}/eventInfo{0x3E3C}/Event{0x3E00}
Jul-31 9:58:02 PM	 	ISYInsteon	Event Queue is now empty.
Jul-31 9:58:02 PM	 	ISYInsteon	ProcessEvent : NOT HANDLED: Unsupported ISY message: C=_7 A=1 N=
Jul-31 9:58:02 PM	 	ISYInsteon	Add : Event added to queue. Queue size = 1
Jul-31 9:58:02 PM	 	ISYInsteon	parse_event : control = [_7] action = [1] node = [] eventinfo = [[Std-Direct Ack] 1E.0D.C8--{0x3E}ISY/PLM Group=0, Max Hops=3, Hops Left=2]
Jul-31 9:58:02 PM	 	ISYInsteon	parse_event : Entering parse event with {0x3C}Event seqnum="6258" sid="uuid:66"{0x3E3C}control{0x3E}_7{0x3C}/control{0x3E3C}action{0x3E}1{0x3C}/action{0x3E3C}node{0x3E3C}/node{0x3E3C}eventInfo{0x3E}[Std-Direct Ack] 1E.0D.C8--{0x3E}ISY/PLM Group=0, Max Hops=3, Hops Left=2{0x3C}/eventInfo{0x3E3C}/Event{0x3E00}
Jul-31 9:58:02 PM	 	ISYInsteon	Event Queue is now empty.
Jul-31 9:58:02 PM	 	ISYInsteon	ProcessEvent : NOT HANDLED: Unsupported ISY message: C=_7 A=1 N=
Jul-31 9:58:02 PM	 	ISYInsteon	Add : Event added to queue. Queue size = 1
Jul-31 9:58:02 PM	 	ISYInsteon	parse_event : control = [_7] action = [1] node = [] eventinfo = [[INST-SRX ] 02 50 1E.0D.C8 28.CE.74 2B 2E 02 (02)]
Jul-31 9:58:02 PM	 	ISYInsteon	parse_event : Entering parse event with {0x3C}Event seqnum="6257" sid="uuid:66"{0x3E3C}control{0x3E}_7{0x3C}/control{0x3E3C}action{0x3E}1{0x3C}/action{0x3E3C}node{0x3E3C}/node{0x3E3C}eventInfo{0x3E}[INST-SRX ] 02 50 1E.0D.C8 28.CE.74 2B 2E 02 (02){0x3C}/eventInfo{0x3E3C}/Event{0x3E00}
Jul-31 9:58:01 PM	 	ISYInsteon	Event Queue is now empty.
Jul-31 9:58:01 PM	 	ISYInsteon	ProcessEvent : NOT HANDLED: Unsupported ISY message: C=_7 A=1 N=
Jul-31 9:58:01 PM	 	ISYInsteon	Add : Event added to queue. Queue size = 1
Jul-31 9:58:01 PM	 	ISYInsteon	parse_event : control = [_7] action = [1] node = [] eventinfo = [[INST-ACK ] 02 62 1E.0D.C8 1F 2E 02 00 00 00 00 00 00 00 00 00 00 00 00 92 96 06 (02)]
Jul-31 9:58:01 PM	 	ISYInsteon	parse_event : Entering parse event with {0x3C}Event seqnum="6256" sid="uuid:66"{0x3E3C}control{0x3E}_7{0x3C}/control{0x3E3C}action{0x3E}1{0x3C}/action{0x3E3C}node{0x3E3C}/node{0x3E3C}eventInfo{0x3E}[INST-ACK ] 02 62 1E.0D.C8 1F 2E 02 00 00 00 00 00 00 00 00 00 00 00 00 92 96 06 (02){0x3C}/eventInfo{0x3E3C}/Event{0x3E00}
Jul-31 9:58:01 PM	 	ISYInsteon	Event Queue is now empty.
Jul-31 9:58:01 PM	 	ISYInsteon	ProcessEvent : NOT HANDLED: Unsupported ISY message: C=_7 A=1 N=
Jul-31 9:58:01 PM	 	ISYInsteon	Add : Event added to queue. Queue size = 1
Jul-31 9:58:01 PM	 	ISYInsteon	parse_event : control = [_7] action = [1] node = [] eventinfo = [[INST-TX-I2CS] 02 62 1E 0D C8 1F 2E 02 00 00 00 00 00 00 00 00 00 00 00 00 92 96]
Jul-31 9:58:01 PM	 	ISYInsteon	Event Queue is now empty.
Jul-31 9:58:01 PM	 	ISYInsteon	parse_event : Entering parse event with {0x3C}Event seqnum="6255" sid="uuid:66"{0x3E3C}control{0x3E}_7{0x3C}/control{0x3E3C}action{0x3E}1{0x3C}/action{0x3E3C}node{0x3E3C}/node{0x3E3C}eventInfo{0x3E}[INST-TX-I2CS] 02 62 1E 0D C8 1F 2E 02 00 00 00 00 00 00 00 00 00 00 00 00 92 96{0x3C}/eventInfo{0x3E3C}/Event{0x3E00}
Jul-31 9:58:01 PM	 	ISYInsteon	ProcessEvent : NOT HANDLED: Unsupported ISY message: C=_7 A=1 N=
Jul-31 9:58:01 PM	 	ISYInsteon	Add : Event added to queue. Queue size = 1
Jul-31 9:58:01 PM	 	ISYInsteon	parse_event : control = [_7] action = [1] node = [] eventinfo = [[Std-Direct ] 1E.0D.C8--{0x3E}ISY/PLM Group=0, Max Hops=1, Hops Left=0]
Jul-31 9:58:01 PM	 	ISYInsteon	parse_event : Entering parse event with {0x3C}Event seqnum="6254" sid="uuid:66"{0x3E3C}control{0x3E}_7{0x3C}/control{0x3E3C}action{0x3E}1{0x3C}/action{0x3E3C}node{0x3E3C}/node{0x3E3C}eventInfo{0x3E}[Std-Direct ] 1E.0D.C8--{0x3E}ISY/PLM Group=0, Max Hops=1, Hops Left=0{0x3C}/eventInfo{0x3E3C}/Event{0x3E00}
Jul-31 9:58:01 PM	 	ISYInsteon	Event Queue is now empty.
Jul-31 9:58:01 PM	 	ISYInsteon	ProcessEvent : NOT HANDLED: Unsupported ISY message: C=_7 A=1 N=
Jul-31 9:58:01 PM	 	ISYInsteon	Add : Event added to queue. Queue size = 1
Jul-31 9:58:01 PM	 	ISYInsteon	parse_event : control = [_7] action = [1] node = [] eventinfo = [[INST-SRX ] 02 50 1E.0D.C8 28.CE.74 01 70 02 (02)]
Jul-31 9:58:01 PM	 	ISYInsteon	parse_event : Entering parse event with {0x3C}Event seqnum="6253" sid="uuid:66"{0x3E3C}control{0x3E}_7{0x3C}/control{0x3E3C}action{0x3E}1{0x3C}/action{0x3E3C}node{0x3E3C}/node{0x3E3C}eventInfo{0x3E}[INST-SRX ] 02 50 1E.0D.C8 28.CE.74 01 70 02 (02){0x3C}/eventInfo{0x3E3C}/Event{0x3E00}
Jul-31 9:57:55 PM	 	ISYInsteon	Event Queue is now empty.
Jul-31 9:57:55 PM	 	ISYInsteon	ISY is idle.
Jul-31 9:57:55 PM	 	ISYInsteon	Add : Event added to queue. Queue size = 1
Jul-31 9:57:55 PM	 	ISYInsteon	parse_event : control = [_5] action = [0] node = [] eventinfo = []
Jul-31 9:57:55 PM	 	ISYInsteon	parse_event : Entering parse event with {0x3C}Event seqnum="6252" sid="uuid:66"{0x3E3C}control{0x3E}_5{0x3C}/control{0x3E3C}action{0x3E}0{0x3C}/action{0x3E3C}node{0x3E3C}/node{0x3E3C}eventInfo{0x3E3C}/eventInfo{0x3E3C}/Event{0x3E00}
Jul-31 9:57:55 PM	 	ISYInsteon	Event Queue is now empty.
Jul-31 9:57:55 PM	 	ISYInsteon	ProcessEvent : NOT HANDLED: Unsupported ISY message: C=_1 A=3 N=1E D C8 1
Jul-31 9:57:55 PM	 	ISYInsteon	Add : Event added to queue. Queue size = 1
Jul-31 9:57:55 PM	 	ISYInsteon	Event Queue is now empty.
Jul-31 9:57:55 PM	 	ISYInsteon	parse_event : control = [_1] action = [3] node = [] eventinfo = [[ 1E D C8 1] CLIMD 2]
Jul-31 9:57:55 PM	 	ISYInsteon	parse_event : Entering parse event with {0x3C}Event seqnum="6251" sid="uuid:66"{0x3E3C}control{0x3E}_1{0x3C}/control{0x3E3C}action{0x3E}3{0x3C}/action{0x3E3C}node{0x3E3C}/node{0x3E3C}eventInfo{0x3E}[ 1E D C8 1] CLIMD 2{0x3C}/eventInfo{0x3E3C}/Event{0x3E00}
Jul-31 9:57:55 PM	 	ISYInsteon	Thermostat/Kitchen/Thermostat - Main Mode is now 2
Jul-31 9:57:55 PM	 	ISYInsteon	Add : Event added to queue. Queue size = 1
Jul-31 9:57:55 PM	 	ISYInsteon	parse_event : control = [CLIMD] action = [2] node = [1E D C8 1] eventinfo = []
Jul-31 9:57:55 PM	 	ISYInsteon	parse_event : Entering parse event with {0x3C}Event seqnum="6250" sid="uuid:66"{0x3E3C}control{0x3E}CLIMD{0x3C}/control{0x3E3C}action{0x3E}2{0x3C}/action{0x3E3C}node{0x3E}1E D C8 1{0x3C}/node{0x3E3C}eventInfo{0x3E3C}/eventInfo{0x3E3C}/Event{0x3E00}
Jul-31 9:57:55 PM	 	ISYInsteon	Event Queue is now empty.
Jul-31 9:57:55 PM	 	ISYInsteon	ProcessEvent : NOT HANDLED: Unsupported ISY message: C=_7 A=1 N=
Jul-31 9:57:55 PM	 	ISYInsteon	Add : Event added to queue. Queue size = 1
Jul-31 9:57:55 PM	 	ISYInsteon	parse_event : control = [_7] action = [1] node = [] eventinfo = [[Std-Direct Ack] 1E.0D.C8--{0x3E}ISY/PLM Group=0, Max Hops=3, Hops Left=2]
Jul-31 9:57:55 PM	 	ISYInsteon	parse_event : Entering parse event with {0x3C}Event seqnum="6249" sid="uuid:66"{0x3E3C}control{0x3E}_7{0x3C}/control{0x3E3C}action{0x3E}1{0x3C}/action{0x3E3C}node{0x3E3C}/node{0x3E3C}eventInfo{0x3E}[Std-Direct Ack] 1E.0D.C8--{0x3E}ISY/PLM Group=0, Max Hops=3, Hops Left=2{0x3C}/eventInfo{0x3E3C}/Event{0x3E00}
Jul-31 9:57:55 PM	 	ISYInsteon	Event Queue is now empty.
Jul-31 9:57:55 PM	 	ISYInsteon	ProcessEvent : NOT HANDLED: Unsupported ISY message: C=_7 A=1 N=
Jul-31 9:57:55 PM	 	ISYInsteon	Add : Event added to queue. Queue size = 1
Jul-31 9:57:55 PM	 	ISYInsteon	parse_event : control = [_7] action = [1] node = [] eventinfo = [[INST-SRX ] 02 50 1E.0D.C8 28.CE.74 2B 6B 05 (05)]
Jul-31 9:57:55 PM	 	ISYInsteon	parse_event : Entering parse event with {0x3C}Event seqnum="6248" sid="uuid:66"{0x3E3C}control{0x3E}_7{0x3C}/control{0x3E3C}action{0x3E}1{0x3C}/action{0x3E3C}node{0x3E3C}/node{0x3E3C}eventInfo{0x3E}[INST-SRX ] 02 50 1E.0D.C8 28.CE.74 2B 6B 05 (05){0x3C}/eventInfo{0x3E3C}/Event{0x3E00}
Jul-31 9:57:54 PM	 	ISYInsteon	Command Queue is now empty.
Jul-31 9:57:54 PM	 	ISYInsteon	Event Queue is now empty.
Jul-31 9:57:54 PM	 	ISYInsteon	ProcessEvent : NOT HANDLED: Unsupported ISY message: C=_7 A=1 N=
Jul-31 9:57:54 PM	 	ISYInsteon	Add : Event added to queue. Queue size = 1
Jul-31 9:57:54 PM	 	ISYInsteon	parse_event : control = [_7] action = [1] node = [] eventinfo = [[INST-ACK ] 02 62 1E.0D.C8 1F 6B 05 00 00 00 00 00 00 00 00 00 00 00 00 00 90 06 (05)]
Jul-31 9:57:54 PM	 	ISYInsteon	parse_event : Entering parse event with {0x3C}Event seqnum="6247" sid="uuid:66"{0x3E3C}control{0x3E}_7{0x3C}/control{0x3E3C}action{0x3E}1{0x3C}/action{0x3E3C}node{0x3E3C}/node{0x3E3C}eventInfo{0x3E}[INST-ACK ] 02 62 1E.0D.C8 1F 6B 05 00 00 00 00 00 00 00 00 00 00 00 00 00 90 06 (05){0x3C}/eventInfo{0x3E3C}/Event{0x3E00}
Jul-31 9:57:54 PM	 	ISYInsteon	Event Queue is now empty.
Jul-31 9:57:54 PM	 	ISYInsteon	ProcessEvent : NOT HANDLED: Unsupported ISY message: C=_7 A=1 N=
Jul-31 9:57:54 PM	 	ISYInsteon	Add : Event added to queue. Queue size = 1

Rich

[bpwwer]

******** UPDATE *******
** Version 3.0.0.10 Alpha **

I upgraded and I even first deleted the thermostat devices per install notes...

It seems that CALL is still not updating the status of the HVAC system.

Here is the ISY Event Log showing the traffic when I choose the Cooling Mode.

Rich,

There's nothing in either of the logs that indicate that the thermostat has switched on the AC and it is now actively cooling the house.

Based on what you wrote a couple posts above, I thought we were on the same page with what mode vs. state (call) meant, but now I'm not sure.

Mode (or operating mode) refers to the mode that the thermostat is set to:
off, heat, cool, auto, program cool, program heat, program auto

Switching the mode simply tells the thermostat to switch to that mode. Your logs show that you switched the thermostat mode to mode #2, cool. That doesn't directly turn on the heating or AC unit, it's only setting the mode of the thermostat itself.

When the thermostat tells either the AC or the furnace to turn on and start cooling or heating the house, it sends a message to the ISY, and the ISY will forward that on to the plug-in. This message is a "call" for heating, cooling, or off.

The "Call" device will only show "Cooling" when your AC is on and actively cooling the house. And I did verify that this was working, when my AC comes on, Call switches to "Cooling" when the AC shuts off, call goes back to "Off".

So check the value when the AC is running, it should be "Cooling" at that point.

There is possibly another bit of information that the thermostat provides. If it is in auto or program auto mode, it may provide a cooling vs. heating state. If so, I think I'm ignoring that now. I think that the recommendation was to not use the auto modes if you're going to control the thermostat via any kind of automation. It doesn't really make sense to have the thermostat's internal logic and your external logic conflicting over what state the thermostat should be in.

Does that make sense?

[rjbur]

Thermostat CALL Not working

Well that's interesting... I actually should have stated that the HVAC system actually turned on... Possibly I did not wait long enough to capture the log.

Either way, the CALL dis not change and continued to report OFF.

I'll try again now...

1) Using the ISY Interface I will now change the MODE of the Thermostat from OFF to COOL.

OK now it is working... What I did do before this was on the ISY Admin interface I Right-Clicked on the "Thermostat - Main" and chose the option to "Restore Device."

Not sure if that kicked the unit in the .... and now its actually reporting COOLING for the "CALL"....


YAHOOO!!! Its up and working...

[rjbur]

HSTouch 3 Not Showing "Thermostat - Main"

OK in an effort to keep post focused on one challenge at a time...

The only big issue left is trying to figure out why the only way I can interface with the Thermostat in HSTouch 3 is by using the "Insteon Device" and not the "Thermostat - Main"???

I know I'm preaching to the choir, but since I cannot I had to create HS3 Events to increase and decrease the HSP and CSP (hot and cold set points). Also I had to create individual MODE buttons for Off, Auto, Heat, and Cool since I could not use the Mode Toggle feature.

Anything you would like me to me to try on my end??

Thanks,
Rich

[rjbur]

ISY (X10NQ) Generic X10 device, Not Queryable - NOT working in HS3

I have created 4 such X10NQ devices in ISY so I can set the "We Are" state of our home. One for Home, Away, Asleep, and On Vacation.

They work great as toggle on/off devices in the ISY web interface as well as the ISY Admin application.

When I try and use them in HS3, they do not toggle, they do not trigger the ISY X10NQ device to toggle??

Thanks,
Rich

PS: Still not Thermostat direct control in HSTouch 3??

[freeon]

I have an event created to be triggered by pressing a key pad(see picture). Acording to the log the plugin sees the button press but does not trigger the event. This is what shows up in the log. Any ideas.

Aug-10 12:20:30 PM ISYInsteon Event Queue is now empty.
Aug-10 12:20:30 PM ISYInsteon ISY Heartbeat message.
Aug-10 12:20:30 PM ISYInsteon parse_event : control = [_0] action = [120] node = [] eventinfo = [] Aug-10 12:20:30 PM ISYInsteon parse_event : Entering parse event with {0x3C}Event seqnum="226" sid="uuid:150"{0x3E3C}control{0x3E}_0{0x3C}/control{0x3E3C}action{0x3E}120{0x3C}/action{0x3E3C}node{0x3E3C}/node{0x3E3C}eventInfo{0x3E3C}/eventInfo{0x3E3C}/Event{0x3E00}
Aug-10 12:20:15 PM ISYInsteon Event Queue is now empty.
Aug-10 12:20:15 PM ISYInsteon Backdoor/Backdoor KP - C sent 255

[bpwwer]

Hi Rich,

What's an X10NQ device?

I have created 4 such X10NQ devices in ISY so I can set the "We Are" state of our home. One for Home, Away, Asleep, and On Vacation.

When I try and use them in HS3, they do not toggle, they do not trigger the ISY X10NQ device to toggle??

Thanks,
Rich

PS: Still not Thermostat direct control in HSTouch 3??

Yes, I know. I still don't know why it doesn't work.

[bpwwer]

I have an event created to be triggered by pressing a key pad(see picture). Acording to the log the plugin sees the button press but does not trigger the event. This is what shows up in the log. Any ideas.

I don't have triggers as such working. With HS2, events like the the button sending an ON command could be used to trigger and event. That's something I want to add to HS3, but HS3 changed how plug-ins interact with the event system completely. I just haven't had the time to figure it out and and get it all working.

Aug-10 12:20:15 PM [/COLOR] ISYInsteon Backdoor/Backdoor KP - C sent 255

It shows here that it sent a command but did the HS device actually change values? The trigger you have will only fire when the device changes value from not 255 and becomes 255. If it was already at 255 when you pressed the button, then nothing would happen.

This type of trigger is something built into HomeSeer and not something the plug-in has any interaction with (other than the changing of the device status and/or value).

[freeon]

I don't have triggers as such working. With HS2, events like the the button sending an ON command could be used to trigger and event. That's something I want to add to HS3, but HS3 changed how plug-ins interact with the event system completely. I just haven't had the time to figure it out and and get it all working.



It shows here that it sent a command but did the HS device actually change values? The trigger you have will only fire when the device changes value from not 255 and becomes 255. If it was already at 255 when you pressed the button, then nothing would happen.

This type of trigger is something built into HomeSeer and not something the plug-in has any interaction with (other than the changing of the device status and/or value).

The device was off and I turned it on and the value changed to 255.

[freeon]

I don't have triggers as such working. With HS2, events like the the button sending an ON command could be used to trigger and event. That's something I want to add to HS3, but HS3 changed how plug-ins interact with the event system completely. I just haven't had the time to figure it out and and get it all working.



It shows here that it sent a command but did the HS device actually change values? The trigger you have will only fire when the device changes value from not 255 and becomes 255. If it was already at 255 when you pressed the button, then nothing would happen.

This type of trigger is something built into HomeSeer and not something the plug-in has any interaction with (other than the changing of the device status and/or value).

It works with one of the keypad and as far as I know they are programmed the same way. When I push keypad G this is what happens. Here is the log.

          Aug-12 7:34:39 AM 
           
         Event 
         Event Trigger "Default All Off" 
         
          Aug-12 7:34:39 AM 
           
         ISYInsteon 
         NodeUpdateHandler : Updating Living Room KP-G Entry from 0 to 100 
         
          Aug-12 7:34:39 AM 
           
         ISYInsteon 
         parse_event : control = [_1] action = [3] node = [] eventinfo = [[ A   D3 56 7] DON 0] 
         
          Aug-12 7:34:39 AM 
           
         ISYInsteon 
         parse_event : Entering parse event with {0x3C}Event   seqnum="1659" sid="uuid:154"{0x3E3C}control{0x3E}_1{0x3C}/control{0x3E3C}action{0x3E}3{0x3C}/action{0x3E3C}node{0x3E3C}/node{0x3E3C}eventInfo{0x3E}[   A D3 56 7] DON 0{0x3C}/eventInfo{0x3E3C}/Event{0x3E00} 
         
          Aug-12 7:34:39 AM 
           
         ISYInsteon 
         Living room/New Living Room KP- G now set to 255 

[rjbur]

Default ISY (X10NQ) Generic X10 device, Not Queryable - NOT working in HS3

An X10NQ device in ISY is sort of a virtual device in ISY.

I can assign it an X10 code such as H1 and I can turn it ON and OFF or TOGGLE it. The status in ISY changes just like a light ON/OFF with a value of 0 for OFF and 100 for ON. No actual device is controlled.

I do see the device in HS3, however, HS3 seems to not know what to do with it. The first look at the devices in HS3 showed that HS3 did not even know what value was for ON and OFF.

I modified this info in HS3, yet I still cannot get HS3 to trigger an ON/OFF state in the ISY device. Works great from ISY where I can change the X10NQ devices state, but in HS3, I donlt even see anything in the ISY event log.

Rich

[bpwwer]

It works with one of the keypad and as far as I know they are programmed the same way. When I push keypad G this is what happens. Here is the log.

          Aug-12 7:34:39 AM 
           
         Event 
         Event Trigger "Default All Off" 
         
          Aug-12 7:34:39 AM 
           
         ISYInsteon 
         NodeUpdateHandler : Updating Living Room KP-G Entry from 0 to 100 
         
          Aug-12 7:34:39 AM 
           
         ISYInsteon 
         parse_event : control = [_1] action = [3] node = [] eventinfo = [[ A   D3 56 7] DON 0] 
         
          Aug-12 7:34:39 AM 
           
         ISYInsteon 
         parse_event : Entering parse event with {0x3C}Event   seqnum="1659" sid="uuid:154"{0x3E3C}control{0x3E}_1{0x3C}/control{0x3E3C}action{0x3E}3{0x3C}/action{0x3E3C}node{0x3E3C}/node{0x3E3C}eventInfo{0x3E}[   A D3 56 7] DON 0{0x3C}/eventInfo{0x3E3C}/Event{0x3E00} 
         
          Aug-12 7:34:39 AM 
           
         ISYInsteon 
         Living room/New Living Room KP- G now set to 255 

Assuming the log above when pressing the 'C' button wasn't missing lines, you are getting different behavior for the two buttons in terms of what the ISY is sending out.

For the 'C' button, the ISY sent a message saying the 'C' button sent a command "ON, level = 255".

The above log shows the ISY sent a message saying the status of 'G' button is now 255.

Right now, the plug-in does nothing with messages like the first. The fact that a controller sent a message won't have any effect. When I get those types of triggers added, you'll be able to trigger off that, but not now.

The second type of message, however, causes the plug-in to update the HS device value. You can create events that trigger off the device value change.

If my assumption that the first log is complete is true, then the buttons are likely either configured differently or you have a program/scene set up for the 'G' button that's causing its status to change. I'm not really an expert on keypad configuration but it might be the difference between a toggle and non-toggle button configuration. Or maybe 'G' is a responder in a scene and 'C' is not?

[bpwwer]

An X10NQ device in ISY is sort of a virtual device in ISY.

I can assign it an X10 code such as H1 and I can turn it ON and OFF or TOGGLE it. The status in ISY changes just like a light ON/OFF with a value of 0 for OFF and 100 for ON. No actual device is controlled.

I do see the device in HS3, however, HS3 seems to not know what to do with it. The first look at the devices in HS3 showed that HS3 did not even know what value was for ON and OFF.

I modified this info in HS3, yet I still cannot get HS3 to trigger an ON/OFF state in the ISY device. Works great from ISY where I can change the X10NQ devices state, but in HS3, I donlt even see anything in the ISY event log.

Rich

Hmm, OK. I haven't had time to look into this yet but are these just X10 devices added using the X10/A10 module?

X10 devices created that way should behave similar to standard dimmer devices from the control aspect. It could be that the plug-in isn't getting status back for them which may cause some issues.

What "Type" does the homeseer device have?

[bpwwer]

An X10NQ device in ISY is sort of a virtual device in ISY.

I can assign it an X10 code such as H1 and I can turn it ON and OFF or TOGGLE it. The status in ISY changes just like a light ON/OFF with a value of 0 for OFF and 100 for ON. No actual device is controlled.

I do see the device in HS3, however, HS3 seems to not know what to do with it. The first look at the devices in HS3 showed that HS3 did not even know what value was for ON and OFF.

I modified this info in HS3, yet I still cannot get HS3 to trigger an ON/OFF state in the ISY device. Works great from ISY where I can change the X10NQ devices state, but in HS3, I donlt even see anything in the ISY event log.

Rich

Ok, I had a chance to look into it and figured out what was going on. I had added support for generic X10 and A10 devices when the X10 modules was first released. Looks like the generic X10NQ type was added later and the plug-in basically was ignoring it.

I added in support for the X10NQ devices and it seems to be working. I also added an error message if it encounters a X10 module device type that's not supported to make it more obvious what's going on if this type of thing happens again.

[rjbur]

Hi Bob,

You stated...

I added in support for the X10NQ devices and it seems to be working.

Fantastic! I'm back again able to focus on this for a short while again.

So how do we get the latest version of the plugin? I noticed it is still at 3.0.0.10... Do I just download the same one again??

Thanks again!

Rich