Release 3.3.1 (Beta) Is Now Available!

[andyf0]

Yes to which? 2441TH (Insteon Thermostat for $149) or 2441ZTH (Insteon Wireless Thermostat for $79)?

 

Thanks

 

I see the 2441TH in the New Device pull down menu but not the 2441ZTH. Do you just use the 2441TH device when adding the 2441ZTH?

 

I'm still interested in these even though I sent my original one back. Does anyone know if they've resolved the triacs heating up the temperature sensors yet? Also, the remote wireless version wouldn't have that problem since it's not actually controlling an HVAC unit.

[Teken]

Yes to which? 2441TH (Insteon Thermostat for $149) or 2441ZTH (Insteon Wireless Thermostat for $79)?

 

Thanks

 

I see the 2441TH in the New Device pull down menu but not the 2441ZTH. Do you just use the 2441TH device when adding the 2441ZTH?

 

I'm still interested in these even though I sent my original one back. Does anyone know if they've resolved the triacs heating up the temperature sensors yet? Also, the remote wireless version wouldn't have that problem since it's not actually controlling an HVAC unit.

 

Andyf0,

 

They have not resolved the triac issue as of yet.

 

Teken . . .

[andyf0]

Teken, thanks. I suppose you could de-solder the sensor and wire it outside the thermostat but it would make such a good looking thermostat kinda ugly. How does Venstar not run into this problem? Is it just separation distance from the triacs?

[Teken]

Teken, thanks. I suppose you could de-solder the sensor and wire it outside the thermostat but it would make such a good looking thermostat kinda ugly. How does Venstar not run into this problem? Is it just separation distance from the triacs?

 

The board layout and design from Venstar took these simple problem into account. Obviously, Smarthome did not in this case . . .

 

Teken . . .

[Chris Jahn]

Yes, it blinks yellow no matter when I open the console or how many times I close it and reopen it. Even when I wiped the Java cache and re-open it still blinks yellow. Running the program to let the dog out fixes it. That program turns some outputs on/off. ISY also responds to the F key press by turning some lights on/off. It also bypasses/unbypasses the one zone. Something in there "wakes up" ISY to the armed status of the system. ISY and Elk clearly are communicating since many other things are working, it is just the exit delay being completed that isn't communicating.

 

Also, that light updates correctly when disarmed. "ready to arm with zone violated", "ready to arm", "not ready to arm". It's only when armed that it fails to recognize the end of the delay.

 

Hi apostolakisl,

 

Well this one has me stumped, I cannot recreate it at all. Can you please recreate it with the event viewer on max and post the results. I'm wondering if something unrelated is causing this problem somehow.

[ISYhbsh01]

Yes to which? 2441TH (Insteon Thermostat for $149) or 2441ZTH (Insteon Wireless Thermostat for $79)?

 

Thanks

 

I see the 2441TH in the New Device pull down menu but not the 2441ZTH. Do you just use the 2441TH device when adding the 2441ZTH?

Anyone got the answer to this?

 

Sent from my SPH-D710 using Tapatalk 2

[apostolakisl]

Yes, it blinks yellow no matter when I open the console or how many times I close it and reopen it. Even when I wiped the Java cache and re-open it still blinks yellow. Running the program to let the dog out fixes it. That program turns some outputs on/off. ISY also responds to the F key press by turning some lights on/off. It also bypasses/unbypasses the one zone. Something in there "wakes up" ISY to the armed status of the system. ISY and Elk clearly are communicating since many other things are working, it is just the exit delay being completed that isn't communicating.

 

Also, that light updates correctly when disarmed. "ready to arm with zone violated", "ready to arm", "not ready to arm". It's only when armed that it fails to recognize the end of the delay.

 

Hi apostolakisl,

 

Well this one has me stumped, I cannot recreate it at all. Can you please recreate it with the event viewer on max and post the results. I'm wondering if something unrelated is causing this problem somehow.

 

Chris,

 

I turned the system on using the ISY console. It armed and the exit timer ran to completion. But it still kept blinking. I did get a brief loss of connection to the Elk from ISY which hadn't been happening in the past. But it restored and continued to blink yellow. I walked over to the keypad and hit the f4 key and it corrected the yellow blinking light to armed fully with solid light. You can see where that happened at 7:17:00 when it switched from exit timer to fully armed simultaneous to the f4 action.

 

I did do a reboot on the xep this morning prior to all of this.

 

The "kitchen motion" is me getting up from my computer in the kitchen and walking over to hit the f4 key. I turned the f4 key on, then turned it off.

 

Lou

 

EDIT: Also, I just tried using the ISY java console to do a "press" of f4, and it also corrects the blinking yellow light.

Fri 09/14/2012 07:16:37 AM : [ELK 0 0 8] Keypad : Back Door : Access Code Valid (101/1/0)

 

Fri 09/14/2012 07:16:37 AM : [ELK 1 0 0] Area : Main House : Armed Stay (3/2/0)

 

Fri 09/14/2012 07:16:37 AM : [ELK 1 0 0] Area : Main House : Armed Fully (2/4/0)

 

Fri 09/14/2012 07:16:37 AM : [ELK 1 0 0] Area : Main House : Armed with Exit Timer (2/3/0)

 

Fri 09/14/2012 07:16:37 AM : [ 5 15 36 6] ST 0

 

Fri 09/14/2012 07:16:37 AM : [ 5 15 36 6] ST 255

 

Fri 09/14/2012 07:16:50 AM : [ELK 0 0 0] (156/0/0)

 

Fri 09/14/2012 07:16:58 AM : [ELK 0 0 0] (156/1/0)

 

Fri 09/14/2012 07:17:00 AM : [ELK 0 19 0] Zone : Kitchen Motion : Violated (51/2/0)

 

Fri 09/14/2012 07:17:00 AM : [ELK 0 19 0] Zone : Kitchen Motion : Open (52/1/0)

 

Fri 09/14/2012 07:17:00 AM : [ELK 0 19 0] Zone : Kitchen Motion : Normal (51/0/0)

 

Fri 09/14/2012 07:17:00 AM : [ELK 0 19 0] Zone : Kitchen Motion : EOL (52/2/0)

 

Fri 09/14/2012 07:17:00 AM : [ELK 0 0 8] Keypad : Back Door : bypass 15 minute Pressed (111/1/4)

 

Fri 09/14/2012 07:17:00 AM : [ELK 0 0 8] Keypad : Back Door : Access Code Valid (101/1/0)

 

Fri 09/14/2012 07:17:00 AM : [ELK 0 0 0] Output : Output 101 : On (121/1/101)

 

Fri 09/14/2012 07:17:00 AM : [ELK 0 29 0] Zone : Back Door : Bypassed (51/3/0)

 

Fri 09/14/2012 07:17:00 AM : [ELK 0 0 0] Output : Output 100 : On (121/1/100)

 

Fri 09/14/2012 07:17:00 AM : [ELK 1 0 0] Area : Main House : Armed with Bypass (2/6/0)

 

Fri 09/14/2012 07:17:00 AM : [ 5 15 36 6] ST 0

 

Fri 09/14/2012 07:17:00 AM : [ELK 0 0 8] Keypad : Back Door : bypass 15 minute LED On (112/1/4)

 

Fri 09/14/2012 07:17:01 AM : [ELK 0 0 8] Keypad : Back Door : bypass 15 minute Pressed (111/1/4)

 

Fri 09/14/2012 07:17:01 AM : [ELK 0 0 8] Keypad : Back Door : Access Code Valid (101/1/0)

 

Fri 09/14/2012 07:17:01 AM : [ELK 0 0 0] Output : Output 101 : Off (121/0/101)

 

Fri 09/14/2012 07:17:01 AM : [ELK 0 29 0] Zone : Back Door : Normal (51/0/0)

 

Fri 09/14/2012 07:17:01 AM : [ELK 0 0 0] Output : Output 100 : Off (121/0/100)

 

Fri 09/14/2012 07:17:01 AM : [ELK 1 0 0] Area : Main House : Armed Fully (2/4/0)

 

Fri 09/14/2012 07:17:01 AM : [ELK 0 0 8] Keypad : Back Door : bypass 15 minute LED Off (112/0/4)

 

Fri 09/14/2012 07:17:01 AM : [ 5 15 36 6] ST 255

 

Fri 09/14/2012 07:17:02 AM : [ELK 0 19 0] Zone : Kitchen Motion : Violated (51/2/0)

 

Fri 09/14/2012 07:17:02 AM : [ELK 0 19 0] Zone : Kitchen Motion : Open (52/1/0)

 

[Chris Jahn]

... I did get a brief loss of connection to the Elk from ISY which hadn't been happening in the past ...

 

Hi Lou,

 

This is key because a loss of connection definitely explains the blinking problem, so I'm wondering if your Elk connection has been dropping off more often with the new build. In looking at the code, we weren't always do a query after reconnect, so we'll fix that.

 

Is it possible for you to recreate the problem without the connection dropping?

[apostolakisl]

... I did get a brief loss of connection to the Elk from ISY which hadn't been happening in the past ...

 

Hi Lou,

 

This is key because a loss of connection definitely explains the blinking problem, so I'm wondering if your Elk connection has been dropping off more often with the new build. In looking at the code, we weren't always do a query after reconnect, so we'll fix that.

 

Is it possible for you to recreate the problem without the connection dropping?

 

I just downgraded to 3.2.6 and it is doing it with that as well. So, now I don't know where this is coming from. It is also losing its connection with 3.2.6. I don't know if I have an xep that is going bad or some other network hickup.

[Xathros]

I think I may have found a small issue in 3.3.1.

 

I have 4 2842-222 motion sensors (actually whatever the old number was but the console reports them as the new #) in my setup and since the upgrade, any program that responds to motion is responding twice within one second.

 

Here is an event viewer trace from one such event:

Fri 09/14/2012 03:27:15 PM : [  11 A7 89 1]      DON   1

Fri 09/14/2012 03:27:15 PM : [  11 A7 89 1]       ST 255

Fri 09/14/2012 03:27:16 PM : [  11 A7 89 1]      DON   0

 

Here is the program that responded:

If
       Control 'Basement / Utility Room / Basement Motion-Sensor' is switched On

Then
       $i.cnt.BasementMotion += 1
       Resource 'Syslog-MOTION - Basement'
       Run Program 'Occupancy' (Then Path)

Else
  - No Actions - (To add one, press 'Action')

 

Here is the result from my Syslog Network resource:

Sep 14 15:27:09 192.168.2.20 ISY994i - MOTION - Basement.
Sep 14 15:27:09 192.168.2.20 ISY994i - MOTION - Basement.

 

I have a Triggerlinc that only reports once so it doesn't seem to be battery device specific. Only the motion sensors and only since 3.3.1 upgrade. If I run the Then path of this program (or any of the other motion activated programs) manually, I only get one log entry.

 

For the moment, I have solved the doubling by adding a 1 second wait at the front of the then path on my log and count programs. For programs that activate lights based on motion I don't want to introduce any additional response delays so I am just living with the extra traffic from the double responses.

 

-Xathros

 

EDIT: Because LeeG will most likely ask for it, here is a level 3 trace of another such event:

Fri 09/14/2012 04:01:06 PM : [iNST-SRX    ] 02 50 11.A7.ED 00.00.01 C7 11 01    LTONRR (01)

Fri 09/14/2012 04:01:06 PM : [standard-Group][11.A7.ED-->Group=1] Max Hops=3, Hops Left=1

Fri 09/14/2012 04:01:06 PM : [  11 A7 ED 1]      DON   1

Fri 09/14/2012 04:01:06 PM : [  11 A7 ED 1]       ST 255

Fri 09/14/2012 04:01:06 PM : [iNST-SRX    ] 02 50 11.A7.ED 00.00.01 C7 11 01    LTONRR (01)

Fri 09/14/2012 04:01:06 PM : [standard-Group][11.A7.ED-->Group=1] Max Hops=3, Hops Left=1

Fri 09/14/2012 04:01:06 PM : [iNST-DUP    ] Previous message ignored.

Fri 09/14/2012 04:01:06 PM : [iNST-SRX    ] 02 50 11.A7.ED 0F.D4.32 41 11 01    LTONRR (01)

Fri 09/14/2012 04:01:06 PM : [standard-Cleanup][11.A7.ED-->ISY/PLM Group=1] Max Hops=1, Hops Left=0

Fri 09/14/2012 04:01:06 PM : [  11 A7 ED 1]      DON   0

 

Different sensor - same issue.

[LeeG]

Post an event viewer with level 3 selected so the actual messages from the motion sensor can been seen.

[Nuttycomputer]

Hi MstrD,

 

Unfortunately this feature is only available in Venstar firmware 2.4 and above. I am sorry.

 

With kind regards,

Michel

 

 

Hey Michel. So been using new firmware for a bit and noticed 2 issues. I have the 2491T Venstar firmware version 2.5. Quote above implies the clock function should work. It does not. Should it be working for this model and firmware then? Do I need to re-add?

 

Secondly, In this new firmware this might be between Mobilinc and the ISY but the fan control is showing blank and is uncontrollable from the Mobilinc App. In previous firmware I've only seen this problem with the new Smarthome thermostats not the Venstar's.

[Xathros]

Post an event viewer with level 3 selected so the actual messages from the motion sensor can been seen.

 

 

Haha! Knew it! See the edit in my previous post.

 

Thanks.

 

-X

[LeeG]

Thanks for the level 3 trace, had not seen the edit. The messages look fine. The duplicate Group Broadcast is normal for an RF device. It looks like the Group Cleanup Direct message is being treated as a separate event from the motion sensor. If that is the case it is a glitch in 3.3.1

[apostolakisl]

... I did get a brief loss of connection to the Elk from ISY which hadn't been happening in the past ...

 

Hi Lou,

 

This is key because a loss of connection definitely explains the blinking problem, so I'm wondering if your Elk connection has been dropping off more often with the new build. In looking at the code, we weren't always do a query after reconnect, so we'll fix that.

 

Is it possible for you to recreate the problem without the connection dropping?

 

 

WOOOOHOOOO I FIGURED IT OUT.

 

OK, so here is the deal. I switched to U-verse last week. U-verse appears to either be blocking port 25 or the old dns server address I had it set to may not have worked since it was a road runner server and I was no longer on road runner. Either way, the would hang when it tried to send an email. Since I have it set to send me an email every time the system arms, it was hanging every time I armed it. Eventually it recovers, but not until after the exit timer finished. . .and thus the exit timer completion message never gets through.

 

Sorry to trouble you. But, hopefully you will find this sort of info helpful. Frankly, I find the xep to be a pretty temperamental item. I have never had something crash so often when the settings don't work. It took me close to 2 hours to get it working since I had to reboot the thing like 20 times at like 2 or 3 minutes per boot. ERRRRRR. If you hit "test" on it, and it doesn't like the settings, it just crashes and reboots.

[Michel Kohanim]

hello hbsh01,

 

I am so very sorry for the trouble ... it seems that SmartHome will NOT finalize the API documentation till next week. It was my mistake to assume that they both used the same firmware but they do not. I do apologize.

 

Once the API docs are available, we'll work on it.

 

Again, sincere apologies.

 

With kind regards,

Michel

[Michel Kohanim]

Hi NuttyComputer,

 

I am not sure which firmware version SmartHome is going to go to production with. We tested with v2.4 and perhaps beta. You might want to contact SmartHome.

 

The other issue should be fixed in 3.3.2 to be released today.

 

With kind regards,

Michel

[Chris Jahn]

WOOOOHOOOO I FIGURED IT OUT. ... Sorry to trouble you. But, hopefully you will find this sort of info helpful. ...

It was no trouble at all, I'm happy to hear that you figured out the root cause of the problem.