Jump to content

Insteon Tstat Status


shannong

Recommended Posts

I have an Insteon Tstat 2441TH v.10 (as reported by ISY). The temperature status rarely updates in Agave both on the node and on the Home screen. In fact, it seems like the only time it updates is when I press the "connected square" in the top right corner to read all the nodes on the ISY. However, the Humidity status updates without issue. 

 

On a minor note, the tstat reports temp in .5 increments, which the ISY Admin Console reports. The tstat display rounds up. Agave rounds down. It would probably be optimal to have Agave round up to match the display of the tstat.

 

My Zwave Tstats seem to work fine.

 

Samsung S6 w/ Android 6.0.1

Agave. 1.2.103

Link to comment

I have an Insteon Tstat 2441TH v.10 (as reported by ISY). The temperature status rarely updates in Agave both on the node and on the Home screen. In fact, it seems like the only time it updates is when I press the "connected square" in the top right corner to read all the nodes on the ISY. However, the Humidity status updates without issue. 

 

On a minor note, the tstat reports temp in .5 increments, which the ISY Admin Console reports. The tstat display rounds up. Agave rounds down. It would probably be optimal to have Agave round up to match the display of the tstat.

 

My Zwave Tstats seem to work fine.

 

Samsung S6 w/ Android 6.0.1

Agave. 1.2.103

 

I've had issues with a few thermostats not reporting all of the correct information over the subscription socket on updates.  This prevents Agave from being able to display all of the correct information without pulling all the data again, as you describe.  I would first suggest trying this on another app to see if it is localized in Agave.  If not there is not much I can do without receiving the data from the ISY. 

 

As for the rounding, I will need a node dump and a current temp report of the thermostat from you to see where the rounding is going wrong.  

Link to comment

Hmm... Attached as a text file. Trying again.

I think I got your rounding fixed.  

 

As for the reporting issue.  there is not way for me to verify the issue unless I have access to that type of thermostat to see it it actually sending the correct data. 

Is it a wired or wireless model?

Link to comment

I think I got your rounding fixed.  

 

As for the reporting issue.  there is not way for me to verify the issue unless I have access to that type of thermostat to see it it actually sending the correct data. 

Is it a wired or wireless model?

2441TH is the wired Insteon stat.

2441ZTH is the wireless Insteon stat.

Link to comment

James, I am having this same issue as well.  The only time I see the current temp update (and be correct) is if I force an update by pressing the green box in upper right.

 

I captured some wireshark traces ... it looks like Agave isn't formatting the rest request for the tstat correctly, as it leaves out the "nodes" part of the path.

 

 

When I start Agave, I see a request for "rest/config", and then shortly after that, the following request (2F 7E 59 is my tstat):

GET /rest/2F%207E%2059%201 HTTP/1.1
Connection: Keep-Alive
Content-Type: application/json
Accept: application/json
Authorization: Basic <snipped>
User-Agent: Dalvik/2.1.0 (Linux; U; Android 7.0; Nexus 5X Build/N5D91L)
Host: 192.168.1.10
Accept-Encoding: gzip

I've seen both a 404 and also no response to this malformed request.

 

Later on, I see Agave do the same malformed request, followed by the CLIMD and CLIFS queries.

 

When I press the green connected box, Agave does a full "rest/nodes" request to retrieve all nodes and updates the temp via that response.

 

I suspect adding the "nodes" part of the path to the above request would get this mostly working.

Link to comment

James, I am having this same issue as well.  The only time I see the current temp update (and be correct) is if I force an update by pressing the green box in upper right.

 

I captured some wireshark traces ... it looks like Agave isn't formatting the rest request for the tstat correctly, as it leaves out the "nodes" part of the path.

 

 

When I start Agave, I see a request for "rest/config", and then shortly after that, the following request (2F 7E 59 is my tstat):

GET /rest/2F%207E%2059%201 HTTP/1.1
Connection: Keep-Alive
Content-Type: application/json
Accept: application/json
Authorization: Basic <snipped>
User-Agent: Dalvik/2.1.0 (Linux; U; Android 7.0; Nexus 5X Build/N5D91L)
Host: 192.168.1.10
Accept-Encoding: gzip

I've seen both a 404 and also no response to this malformed request.

 

Later on, I see Agave do the same malformed request, followed by the CLIMD and CLIFS queries.

 

When I press the green connected box, Agave does a full "rest/nodes" request to retrieve all nodes and updates the temp via that response.

 

I suspect adding the "nodes" part of the path to the above request would get this mostly working.

Good information.  And you see all of this from the home/favorites screen?  

Link to comment

James, I am having this same issue as well.  The only time I see the current temp update (and be correct) is if I force an update by pressing the green box in upper right.

 

I captured some wireshark traces ... it looks like Agave isn't formatting the rest request for the tstat correctly, as it leaves out the "nodes" part of the path.

 

 

When I start Agave, I see a request for "rest/config", and then shortly after that, the following request (2F 7E 59 is my tstat):

GET /rest/2F%207E%2059%201 HTTP/1.1
Connection: Keep-Alive
Content-Type: application/json
Accept: application/json
Authorization: Basic <snipped>
User-Agent: Dalvik/2.1.0 (Linux; U; Android 7.0; Nexus 5X Build/N5D91L)
Host: 192.168.1.10
Accept-Encoding: gzip

I've seen both a 404 and also no response to this malformed request.

 

Later on, I see Agave do the same malformed request, followed by the CLIMD and CLIFS queries.

 

When I press the green connected box, Agave does a full "rest/nodes" request to retrieve all nodes and updates the temp via that response.

 

I suspect adding the "nodes" part of the path to the above request would get this mostly working.

 

I really thank you for reporting this.  This was effecting more then thermostats.  I am not sure how it happened, but a small chunk of code was improperly formatted for requesting the nodes information.  I have corrected it and will have it out soon as it effects so much.  

Link to comment

Archived

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


  • Recently Browsing

    • No registered users viewing this page.
  • Who's Online (See full list)

    • There are no registered users currently online
  • Forum Statistics

    • Total Topics
      36.6k
    • Total Posts
      368.1k
×
×
  • Create New...