Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for dryContact sensors #24

Open
jimboca opened this issue Jan 6, 2019 · 13 comments
Open

Add support for dryContact sensors #24

jimboca opened this issue Jan 6, 2019 · 13 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@jimboca
Copy link
Collaborator

jimboca commented Jan 6, 2019

2019-01-06 12:21:13,174 [Controller] [ERROR] t198772770918:getSensorAddress: Unable to determine sensor address for: {'name': '', 'type': 'monitor_sensor', 'inUse': False, 'id': 'ei:0:1', 'capability': [{'type': 'dryContact', 'value': '0', 'id': ''}]}
2019-01-06 12:21:13,175 [Controller] [ERROR] t198772770918:getSensorAddress: Unable to determine sensor address for: {'name': '', 'type': 'monitor_sensor', 'inUse': False, 'id': 'ei:0:2', 'capability': [{'type': 'dryContact', 'value': '0', 'id': ''}]}
@jimboca
Copy link
Collaborator Author

jimboca commented Jan 6, 2019

@cswelin
Copy link

cswelin commented Jan 26, 2020

2020-01-25 21:52:19,807 [Controller] [ERROR] rs_bbfh:update: Unknown capabilty: {'id': '3', 'type': 'dryContact', 'value': '1'}

To add some additional context.

@jimboca jimboca self-assigned this Dec 25, 2020
jimboca added a commit that referenced this issue Dec 25, 2020
@jimboca
Copy link
Collaborator Author

jimboca commented Dec 25, 2020

I've attempted to add support in 2.2.0 which I plan to release soon, but I'll need users to test and verify.

@jimboca jimboca added this to the 2.2.0 milestone Dec 25, 2020
@jimboca jimboca added the enhancement New feature or request label Dec 25, 2020
@cswelin
Copy link

cswelin commented Dec 25, 2020

I've attempted to add support in 2.2.0 which I plan to release soon, but I'll need users to test and verify.

I do know the new door contact sensors aren't returned in the Thermostat API (I know mine doesn't anymore, used to), so finding a tester with the old sensor might be rare.

@macjeff
Copy link

macjeff commented Dec 27, 2020

i am out of town but updated from remote still getting some errors posted logs
Ecobee_logs_2020-12-27_121543.zip

@jimboca
Copy link
Collaborator Author

jimboca commented Dec 28, 2020

Sorry, hard to test when I don't have one, please try 2.2.1

@macjeff
Copy link

macjeff commented Dec 28, 2020

its fine as i said before i am out of town and i dont have access to admin console right now but except for a few debug messages things look better here are new logs
Ecobee_logs_2020-12-27_213141.zip

@jimboca
Copy link
Collaborator Author

jimboca commented Dec 28, 2020

Thanks, no errors, but I don't see it adding the new node for the dryContact sensor...

@macjeff
Copy link

macjeff commented Dec 28, 2020

In installed the Admin Console on another computer and all my nodes are working and errors gone. Remember when you said I had a dry contact sensor and the errors said that. I looked up and I dont have one. I think the old error messages (not fixed) were incorrect telling you I had one. I dont have a wired sensor other than the humidifier but that just turns on and off based on humidity its reporting correctly

@jimboca
Copy link
Collaborator Author

jimboca commented Dec 28, 2020

Can you send me the download log package? The drycontact may be coming from a remote sensor?

@macjeff
Copy link

macjeff commented Dec 28, 2020

Attached logs as requested

Ecobee_logs_2020-12-28_103749.zip

@jimboca
Copy link
Collaborator Author

jimboca commented Dec 28, 2020

@macjeff, you did get the 2 new nodes for the dry contact sensors

  {
    "_id": "5fe941c09b6a53db8c26638b",
    "address": "n004_ei_0_1",
    "__v": 0,
    "added": true,
    "controller": "false",
    "drivers": {
      "ST": {
        "uom": "17",
        "value": "0"
      }
    },
    "enabled": true,
    "hint": "0x01030200",
    "isprimary": false,
    "name": "Ecobee - ",
    "nodedef": "EcobeeSensorMSD",
    "primary": "n004_t170767287984",
    "profileNum": "4",
    "timeAdded": "1609061460180"
  },
  {
    "_id": "5fe941c09b6a53db8c26638e",
    "address": "n004_ei_0_2",
    "__v": 0,
    "added": true,
    "controller": "false",
    "drivers": {
      "ST": {
        "uom": "17",
        "value": "0"
      }
    },
    "enabled": true,
    "hint": "0x01030200",
    "isprimary": false,
    "name": "Ecobee - ",
    "nodedef": "EcobeeSensorMSD",
    "primary": "n004_t170767287984",
    "profileNum": "4",
    "timeAdded": "1609061460180"
  }

The are both under your "Sunroom" thermostat.

@macjeff
Copy link

macjeff commented Dec 29, 2020

OK now I am very stumped. Since I’m out of town I didn’t look closely enough to see that the sun room thermostat is now showing up. It is an ecobee original and was never supported by the note server before. It doesn’t even support sensors. It runs in the heat pump and has no humidifier or anything else. So I would never of guessed that was what was showing up in my errors as dry contact. My other thermostats are an ecobee three and four which have sensors on both of them but just the room sensor version one and two

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants