| Author |  | 
      
        | Lenny Senior Member
 
  
 
 Joined: January 06 2008
 Online Status: Offline
 Posts: 102
 | 
          All of a sudden I am unable to control my thermostats from powerhome. The Raw log shows RX Insteon NAK. If I adjust the thermostat manually powerhome receives the change just fine. I have cleared my PLM and did an Add Full and rebuilt the links on one of the thermostats. Neither action resulted in any errors in the raw log. If it was a wireless "COMM" issue I'd expect the problem to be both directions. Anyone have any ideas? I'm running PH 2.1.5d.
           | Posted: January 04 2016 at 16:54 | IP Logged |   |  
           | 
 |  Thanks
 
 Edited by Lenny - January 04 2016 at 16:56
 | 
       
        | Back to Top |     | 
       
       
        |  | 
        | Lenny Senior Member
 
  
 
 Joined: January 06 2008
 Online Status: Offline
 Posts: 102
 | 
          Ok, I did some more thinking and testing. I did apply
           | Posted: January 04 2016 at 18:05 | IP Logged |   |  
           | 
 |  2.1.5d over the holiday and I wondered if that had
 anything to do with it... So I renamed my 2.1.5d
 folder and put back my 2.1.5c folder and thermostats
 work perfectly.
 
 Then I put 2.1.5d back and then PH can't control them.
 
 I then put 2.1.5c back and copied my "2.1.5d db" that
 I have been using into the 2.1.5c folder to rule out
 DB issues and it still works as expected.
 
 This leads me to believe something changed in 2.1.5d
 to cause the issue.
 
 Dave, if you need more details or me to do some
 testing let me know.
 Thanks
 | 
       
        | Back to Top |     | 
       
       
        |  | 
        | dhoward Admin Group
 
  
  
 Joined: June 29 2001
 Location: United States
 Online Status: Offline
 Posts: 4447
 | 
          Lenny,
           | Posted: January 04 2016 at 21:13 | IP Logged |   |  
           | 
 |  
 If its not too much problem, can you send me a sample
 (or screenshot) of the raw insteon of a successful
 command using 2.1.5c as well as an unsuccessful
 command using 2.1.5d.
 
 Being able to compare the two actual Insteon commands
 being sent by the two separate versions should help me
 to track what is going on.
 
 Thanks,
 
 Dave.
 
 | 
       
        | Back to Top |       | 
       
       
        |  | 
        | Lenny Senior Member
 
  
 
 Joined: January 06 2008
 Online Status: Offline
 Posts: 102
 | 
          Thanks Dave, I sent you a PM with a link to download the
           | Posted: January 05 2016 at 07:27 | IP Logged |   |  
           | 
 |  logs and screen recording. Let me know if you have you
 any issues.
 
 Thanks,
 
 Lenny
 | 
       
        | Back to Top |     | 
       
       
        |  | 
        | dhoward Admin Group
 
  
  
 Joined: June 29 2001
 Location: United States
 Online Status: Offline
 Posts: 4447
 | 
          Lenny,
           | Posted: January 22 2016 at 14:37 | IP Logged |   |  
           | 
 |  
 Finally analyzed the data you sent me and I can see
 what is going on. In 2.1.5c, the commands to the
 thermostat are standard length commands (which work).
 In 2.1.5d, the commands are being sent as extended
 length commands which your thermostat obviously doesnt
 like. Ive analyzed the code between 2.1.5c and 2.1.5d
 and this section of code is unchanged (I even went
 back to 2.1.5a and it was the same). In any event, the
 problem is the extended command which we need to be
 changed to a standard command.
 
 The code whether to send a standard or extended
 command is covered by a couple of bits of information.
 First thing to check in both 2.1.5c and 2.1.5d is the
 IEngine column for the thermostat device in Insteon
 Explorer. You'll need to scroll almost all the way to
 the right.
 
 The second thing to check (in each version so I can
 compare) is the status of the operating flags. In the
 PH Multi-Editor in SQL mode (Shift-F5), run the
 following SQL statement:
 
 select value from insteondeviceflags where address =
 'PUT IN THE INSTEON ADDRESS OF YOUR TSTAT DEVICE' and
 cmd1 = 31 and cmd2 = 0 and data1 = 0 and data2 = 0 and
 flag = 0
 
 Be sure to substitute the insteon address of your
 device as indicated above and make note of the
 returned values.
 
 Next step is to run this formula in PH ME in formula
 mode (shift+F6):
 
 ph_insteonwithret("THE ID OF YOUR TSTAT DEVICE",31,0)
 
 Substitute the PowerHome ID (not the Insteon address)
 as appropriate.
 
 Let me know the results of the above as I think it
 will help me pinpoint a bug.
 
 Thanks and appreciate your patience.
 
 Dave.
 
 | 
       
        | Back to Top |       | 
       
       
        |  | 
        | Lenny Senior Member
 
  
 
 Joined: January 06 2008
 Online Status: Offline
 Posts: 102
 | 
          Thanks Dave I'm not sure this info will help.
           | Posted: January 23 2016 at 09:29 | IP Logged |   |  
           | 
 |  
 My 3 stats IEngine info for my Stats
 
   
 The SQL query for all 3 stats return value of 0
 
 The PH command for all 3 stats evaluates to 0 for both 2.1.5c & 2.1.5d
 
 I'll PM you the PLM Log.
 
 
 
 | 
       
        | Back to Top |     | 
       
       
        |  | 
        | dhoward Admin Group
 
  
  
 Joined: June 29 2001
 Location: United States
 Online Status: Offline
 Posts: 4447
 | 
          Lenny,
           | Posted: January 24 2016 at 13:57 | IP Logged |   |  
           | 
 |  
 The screenshot for the IEngine data is from 2.1.5c or
 2.1.5d (or both)?
 
 The SQL query that you ran and all 3 stats returned 0,
 was that for both 2.1.5c and 2.1.5d?
 
 If its both for both questions, then definitely not
 what I was expecting. I was expecting the IEngine data
 to be different between C and D or the SQL query for D
 to be other than 0 or actually no rows returned.
 
 If there are/were no differences between C & D, try
 controlling the thermostat using D and see if the
 problem is still there. If it is, change the IEngine
 in D to "Legacy", save the changes and then try again.
 
 Let me know,
 
 Dave.
 
 | 
       
        | Back to Top |       | 
       
       
        |  |