MWareman

2441TH owner here - AWESOME! Thermostat seems to be properly reporting now. No more manual refreshed for me. Interestingly - I had to remove and readd the device - a 'Restore' did not do it for me. I'll let you know about the IO Linc bug - I just noticed the other day my Garage Door kit was reporting the door closed before the door was actually closed when I initiated the close thru the ISY. Michael.

Hi Michel, I upgraded to 3.3.2 the other day - and the issues with the 2441TH are a little different - but still present. I removed the thermostat (only had 1 node from prior version) and added it again (now has 3 nodes). I saw a post earlier that suggested it should have 5 - the main node, two controllers for temp (low and high) and two controllers for humidity (low and high). The last two are still missing, if indeed they are supposed to be there. When I select the thermostat node, the 'Fan State' claims to be 'On'. It's not - it's currently 'Auto' as displayed on the thermostat display. If I do a 'query' - everything updates - but the fan state is still incorrect. When I click 'Set Options' - the 'Report Humidity' check is unchecked. If I check it and click 'OK' - the dialog dismisses. Clicking 'Options' again reveals a still empty check. Reported here: viewtopic.php?p=70205#p70205 The 'Cool Ctl' node appear to have an 'Options' button, as well as set point adjustment buttons. Not sure if it should Same with the 'Heat Ctl'. Thanks! Michael.

I will just add this to the thread. I still have my SmartLinc (2412N) from before I got my ISY. Tonight, I plugged it back in, updated its firmware and linked only the thermostat - so I could compare the experience using the thermostat with MobiLinc via both the ISY and the SmartLinc. In MobiLync with the SmartLinc, the Thermostat seems fully functional - it displays current fan mode (AUTO or ON) with the current state in BOLD. It displays current action of the system (COOLING, HEATING or nothing for idle) and the Temperature and Humidity seem to update nearly live - no refreshes needed. Switching back to the ISY connection - still within MobiLinc - the fan status is not available, system status is not shown and I have to manually sync to update the temperature and humidity. The manual refresh does not get the status of the fan or system (Cooling / Heating etc) - that remains unknown. The only difference seems to be the way the ISY talks to the thermostst. If there are any traces I can take to help figure this out - I'm happy to do my best to help. I'm not convinced this is a thermostat issue myself - but it seems to be more of an ISY issue. See the album at http://imgur.com/a/358xN for screenshots of the two - note that the state of the HVAC was identical with the two - AC running, fan on. Michael.

Just setup a 2441TH (v.0B) myself - and it appears to mostly work for me - temp and humidity being displayed properly and my heat and AC is being controlled properly tot he setpoints I set. I'm not getting status updates sent to the ISY though - have to do a 'Query Status'. Annoying - yes - but not the end of the world. In the admin console, 'Set Options' asks 'Confirm: Report Humidity' is always unchecked - if I check it - writing happens - but when I click 'Set Options' again the box is again unchecked. It does not seem to do anything either. Also 'Fan State' and 'Heat/Cool State' do not get populated in the Web UI (or in the admin console) - so this does not appear to be read correctly either. Michel - you mentioned an 'upcoming beta' in this thread a few weeks ago (after the release of 3.2.6) - and I still see that the latest available is still 3.2.6 (that I am already running). Is there anything in the works that you can reveal that my reduce the reported issues with this thermostat? Many thanks, Michael.

Sounds like a match indeed - my devices link table did match the ISY after the restore when the device was not working properly. Do you by chance have either a RemoteLinc or ControlLinc is in affected scene? There seems to be a UI glitch around the handling of these two devices (at least in my setup). The UI seems to think that the ControlLinc and the RemoteLinc can be a responder - which does not make sense. I've been thinking that may be the source of the issue for me - but it sounds like it may be something more fundamental. Michael.

Quick question: I've noticed a small (probably) issue with the 2430 (ControlLinc) on 3.1.9 (possible earlier versions as well - this is my first beta version). When adding one - it prompts me if I want it to be a Controller or Responder. It really makes no sense for this device to be a responder so I would think it shouldn't ask and just default to being a controller only. The RemoteLinc (2440) does this already. Also, I just had a heck of a time with a KeypadLinc (2486DWH8) secondary button, a LampLinc (2456D3) load, a RemoteLinc (2440) and a ControlLinc (2430). all in a scene. I had everything configured in the ISY and I reset all devices back to favtory defaults (to ensure no old links). I then issued a 'restore' to all devices from the ISY (with the RemoteLinc 'listening') to program all devices for the scene. The results were incomplete. The status lights on the Keypad did not reflect the LampLinc state, neither the RemoteLinc nor the ControlLinc could control the LampLinc - but the KeypadLinc could turn the LampLinc on and off (and the state would be correct in this case). Mobilinc could control the LampLinc and the state on the KeypadLinc was correct in this case. Strange. I do know that when I first deployed the ISY with 2.x I did not have this problem. I had to remove, one by one - all devices from my scene - then re-add them one at a time. Once that was complete - the scene worked properly. In the GUI - the ControlLinc and the RemoteLinc seem to report that are both a 'Controller' and a 'Responder'. It's not really possible for them to be a 'Responder' so I think this may be a UI bug. Could this also be affecting the construction of the scene? Michael.

You're welcome! I not really sure. I don't believe that calls to network resources can have parameters passed to them. I think you have to create a separate network resource to notify each specific message. For example, 'Motion Detected - Garage' and 'Motion Detected - Back Yard' would need to be two separate resources - rather than something like 'Motion Detected - $varDevice'. Likewise - I don't think that the current implementation of variables is capable of being used outside of programs. I do realize this would be much more useful with these two features: Allowing parameters to be passed to network resources Using variables everywhere - SMTP messages, as a part of programs (for instance - turn on the device identified by the current content of a variable) and (of course) as parameters when calling network resources Of course - I'm still very much a noob at this. I am probably very much mistaken! Hopefully someone more knowledgeable can enhance our understanding? The main thread I'm looking at is http://forum.universal-devices.com/viewtopic.php?f=68&t=5987. I know that variables are still very young and developing. I (for one) am looking forward to them growing up! Michael.

Brand new owner here - and thought I'd give something back after figuring this out. Thanks to Michel @ UDI for your help getting this going. I've posted the details on the wiki at http://www.universal-devices.com/mwiki/index.php?title=ISY-99i_Series_INSTEON:Networking:Mobile_Notification Thanks!