Ambient & Humidity Missing #154
Comments
|
I don't have a thermostat so it's hard for me to say. Please set the debug level to debug and see if the log reports any message that might have that data showing up. Maybe @krkeegan can help? I see this note in the thermostat dev guide (see top of page 6):
|
|
Thanks for the reply. I added the 0x05 group to no avail. Not sure if it's needed since Indigo doesn't seem to use it for its status. Debug has been running (level 10) and no humidity/ambient messages appear. I'll investigate the 0x2E to 0x08 suggestion - perhaps someone who has their thermostat reporting can chime in. I used the setup shown on the Insteon-terminal page. I also tried this with a wired PLM in addition to the Wireless 2448A7 unit - reset the 2448A7 to factory settings and gave it another shot - same result - no ambient/humidity reports. Tho I am receiving cool_sp_command and cool_sp_state. |
|
As of 0.6.9 things seems to be humming along - I now get regular humidity reports from the thermostat but not ambient temperature (most likely a 2441 issue). I solved it by using the new poll function and tying it to an interval automation (pings every 10 minutes). Seems to keep things updated quite nicely. |
|
I'm going to reopen this issue just to verify something I may be doing incorrectly. Some actual messages which appear w/o polling...
Here are my settings... THERMOSTAT:
MODEM:
Any idea why ambient would NOT be sent [yes it's changing] but yet humidity IS? I would assume they are part of the same 0xEF (239) broadcast. I would expect ambient_temp to display as regularly as humid_state. Apologies for beating this dead horse. -H |
|
Hmm, mine works fine. My details are below: Device 22.ZZ.7e received model information: CLIMATE (0x05): '2441TH' (0x0b) 'Insteon Thermostat (915 MHz)' firmware: 0xd Thermostat: Modem: So, two things I see that are different. The group values in D3 on the thermostat. Those should be 0x01 and I see where that mistake is in the code, I will fix that. Our modem values are otherwise the same, except that D3 in the EF group. That one stumps me, not sure how your's ended up with that D3 value. Mine matches what we do in the code. I would be surprised if any of this was the problem, particularly since 75% of the messages are working. But stranger things have happened. |
Modem responder group is likely ignored, but standard practice is to set this to 0x01. This fixes that mistake. May solve TD22057#154, may not
|
If you can, try removing all of the links between the thermostat and the modem and re-running join and then pair. |
|
I did do a clear recently and re-pair resulting in the same issue. Once you have the D3 fix in I’ll try again and see if it resolves the issue.
It is odd that humidity comes over but not ambient temperature (I would expect both). I am running 2 thermostats but that shouldn’t matter.
Right now I’m polling every 10 minutes as a temp fix.
…Sent from my iPhone
On Mar 6, 2020, at 1:55 PM, Kevin Robert Keegan ***@***.***> wrote:
If you can, try removing all of the links between the thermostat and the modem and re-running join and then pair.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
I made a pull request for this branch, it is just the dev branch with one change. You can try checking it out to see if it makes a difference: https://github.com/krkeegan/insteon-mqtt/tree/Issue_154 |
|
I made the change which effectively was changing “group” to “0x01” in the code. Here’s my resulting dump of the thermostat DB... Unfortunately only humidity is being broadcast, still no ambient temp. Commanding thermostat device 4c.7f.d5 (living_room) cmd=print_db 4c.7f.d5 (living_room) device database DeviceDb: (delta None) Unused: Last: GroupMap |
|
I have no idea then. Your setup matches mine now and I get temp updates (on three different devices). All I can suggest is a factory reset. Otherwise, you thermostat seems defective in some way. |
|
You may be correct - I’ll try a factory reset later today - I doubt if they are bad since they worked perfectly with Indigo.
One of the 2 thermostats did report ambient_temp at one point in time, only 1 report last night. So I’m guessing your 0xd3 change made a difference.
Humidity still broadcasts - it’s almost like a bit mask is incorrect. (If there is one to filter reports).
…-H
On Mar 6, 2020, at 9:50 PM, Kevin Robert Keegan ***@***.***> wrote:
I have no idea then. Your setup matches mine now and I get temp updates (on three different devices). All I can suggest is a factory reset.
Otherwise, you thermostat seems defective in some way.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub <#154?email_source=notifications&email_token=AMONC7ILXO2OAXZE7HHY2Q3RGGZARA5CNFSM4H3MFQK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEODNC2I#issuecomment-596037993>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMONC7O5FEVWO65J6JACF3LRGGZARANCNFSM4H3MFQKQ>.
|
|
For completeness I've also included the modem DB for the thermostat. Note that this is only 1 of 2 thermostats - they both have identical configurations.
Complete
Complete |
|
I also noticed I get the refresh request... Thermostat paired It says it's paired - does the "Pairing may fail.." comment indicated the pair failed? |
|
I have never seen that message, but it looks like that message is only part of the cmd_line interface. It appears to be sent if there is any ui output. I may need to revisit that warning. But I don't think it has anything to do with your issue. I have a spare PLM and Thermostat that I have been using to test all of this on, I will reset both of them tonight and see what I get. But honestly I am a bit stumped. I am pretty confident this works beyond just for me since we had users reporting issues with C/F mixups with ambient messages a year ago. |
|
I started to receive reports albeit very intermittently - so the 0xd3 fix definitely made a difference this time around.
I actually used Insteon_terminal to setup one thermostat after a factory reset - no difference - so it’s matching your pairing setup.
Since it’s working let’s claim success.
…-H
On Mar 9, 2020, at 2:39 PM, Kevin Robert Keegan ***@***.***> wrote:
I have never seen that message, but it looks like that message is only part of the cmd_line interface.
It appears to be sent if there is any ui output. I may need to revisit that warning. But I don't think it has anything to do with your issue.
I have a spare PLM and Thermostat that I have been using to test all of this on, I will reset both of them tonight and see what I get. But honestly I am a bit stumped. I am pretty confident this works beyond just for me since we had users reporting issues with C/F mixups with ambient messages a year ago.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub <#154?email_source=notifications&email_token=AMONC7O6E52HBNKXWABFHL3RGVAYNA5CNFSM4H3MFQK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOIR3XY#issuecomment-596712927>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMONC7I6MBOHDJ5NCJQTTOLRGVAYNANCNFSM4H3MFQKQ>.
|
|
If it works at all, I think anything we can do in SW is fixed. The thermostat is a wireless only device. So putting a wired device near it even a plug in thing like an appliancelinc may help. |
Great program - however I'm having an issue obtaining a Thermostat's (2441TH) ambient_temp and humid_state. I'm using a Pi w/a 2448A7 wireless USB modem. Values arrive fine under OpenHAB 2.4 (using the 1.x binding) however under insteon-mqtt I don't receive temp/humid yet set points and other status arrive just fine. Subscribing to Insteon/#.
Any ideas?
Regards,
-Herb
The text was updated successfully, but these errors were encountered: