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

New Device Request - Sage Doorbell Sensor #2755

Closed
Puntoboy opened this issue May 9, 2020 · 75 comments
Closed

New Device Request - Sage Doorbell Sensor #2755

Puntoboy opened this issue May 9, 2020 · 75 comments

Comments

@Puntoboy
Copy link

Puntoboy commented May 9, 2020

Hello, I've recently bought this sensor and I would like to integrate it with my Home Assistant. Below are what I think are the required screenshots.

image

image

@MattL0
Copy link

MattL0 commented May 12, 2020

+1

@MattL0
Copy link

MattL0 commented May 12, 2020

Just ordered mine.

@Puntoboy
Copy link
Author

I've only bought this sensor as my video doorbell won't send notification to Alexa so I want to use HA to do it instead.

@MattL0
Copy link

MattL0 commented May 19, 2020

is there any new hardware integration on deconz? it is calm since a while @manup

@MattL0
Copy link

MattL0 commented Jun 5, 2020

Up @manup ?

@Mimiix
Copy link
Collaborator

Mimiix commented Jun 6, 2020

@SwoopX

@Mimiix Mimiix closed this as completed Jun 6, 2020
@Mimiix Mimiix reopened this Jun 6, 2020
@ManicGTI
Copy link

+1 here as well, this would be useful for my Nest Hello

@stale
Copy link

stale bot commented Jul 1, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jul 1, 2020
@Puntoboy
Copy link
Author

Puntoboy commented Jul 1, 2020

Any update on this?

@stale stale bot removed the stale label Jul 1, 2020
@MattL0
Copy link

MattL0 commented Jul 1, 2020

+1 would really like to add this to my setup @manup

@SwoopX
Copy link
Collaborator

SwoopX commented Jul 9, 2020

I have no clue if this will work since I don't have the device. Chances are very high that the button map is not correct. I'd require some debug output then.

@Puntoboy
Copy link
Author

Puntoboy commented Jul 9, 2020

I have no clue if this will work since I don't have the device. Chances are very high that the button map is not correct. I'd require some debug output then.

Tell me what you need and I can send it. You'll have to break it down though as I am new to this. Also, it works on ZHA apparently, is there anything you can gain from that?

@SwoopX
Copy link
Collaborator

SwoopX commented Jul 9, 2020

Dunno, they did it with 2 buttons, I do it with one. Should have pretty much the same effect

However, it can be used for 2 doors and they implemented it for the first one only. Got it for both but for the 2nd, I don't know which commands are send. However, I assume it should work fine in your case.

ZHA
grafik

How I did it
grafik

@Puntoboy
Copy link
Author

Puntoboy commented Jul 9, 2020

So what I've found is that I can pair it to Deconz, it appears in the VNC viewer but not in the web app. When I look at the logs in HA there is no input from the device.

@SwoopX
Copy link
Collaborator

SwoopX commented Jul 9, 2020

When I look at the logs in HA there is no input from the device.

No surprise since it's not supported yet.

@Puntoboy
Copy link
Author

Puntoboy commented Jul 9, 2020

When I look at the logs in HA there is no input from the device.

No surprise since it's not supported yet.

Clearly...

So where do we go from here?

@SwoopX
Copy link
Collaborator

SwoopX commented Jul 9, 2020

Wait for the new release and check it out. Changed the button map over here to mimic zha. I feel the device could behave funny otherwise (and possibly brick the intended functionality). Worst case is that you'd require 2 buttons for your home automation, 1 for open and one for close.

@Puntoboy
Copy link
Author

Puntoboy commented Jul 9, 2020

Great thanks. I'll give it a try.

@SwoopX
Copy link
Collaborator

SwoopX commented Jul 27, 2020

Closing this as support has been added with version .79

@SwoopX SwoopX closed this as completed Jul 27, 2020
@ManicGTI
Copy link

Whoop! Thanks.

@Puntoboy
Copy link
Author

Puntoboy commented Jul 27, 2020 via email

@SwoopX
Copy link
Collaborator

SwoopX commented Jul 28, 2020

I need to have some feedback if it works alright though. If not, please raise a seperate issue for that 😉

@oywino
Copy link

oywino commented Apr 17, 2021

I think you have to click in the field "SW Build ID" to bring up the Attribute Editor, and in this click on "Read" (or Read Config) - I don't remember exactly.

@Adjrobinson
Copy link

ah yes, looks like the same, weird, I deleted it again and turned off the routers and paired it in the same room as the combee, still no joy:
image

@Mimiix
Copy link
Collaborator

Mimiix commented Apr 17, 2021

It's normal it doesn't show in phoscon. They need to add support for it.

@Adjrobinson
Copy link

Ok, I have ordered https://www.tindie.com/products/ErikLemcke/doorbell-modernizr-2/ instead so if one of the dev's want the sage one to add it let me know as it's pretty pointless at the moment lol, looks like zigbee2mqtt might support it but I don't want to go down that route.

@oywino
Copy link

oywino commented Apr 17, 2021

It's normal it doesn't show in phoscon. They need to add support for it.

Incorrect. Mine does show in Phoscon as well as in Home Assistance! It's just listed an "unreachable". Using deConz, I can read attribute values, but I cannot activate it. But I have read elsewhere that others have been able to make it work using deConz until they one day disconnected it and could no longer successfully reconnect it again after updating.

@Smanar
Copy link
Collaborator

Smanar commented Apr 17, 2021

"Deconz version 2.05.77", idk in wich one version this device was added, but can you try with a more recent version ?

Can you share the device Json, to see how it is reconized in deconz ?

@oywino
Copy link

oywino commented Apr 17, 2021

I'm using deConz 2.10.04.
I'd love to share my JSON but I don't know how. Please explain.

@Smanar
Copy link
Collaborator

Smanar commented Apr 17, 2021

You can find it.

  • using third app
  • using phoscon with dev console
  • checking direclty the api

http://IP:PORT/api/KEY/lights
and
http://IP:PORT/api/KEY/sensors

IP and PORT are the same than for phoscon
Key is an api key https://dresden-elektronik.github.io/deconz-rest-doc/getting_started/

@oywino
Copy link

oywino commented Apr 17, 2021

Here it is:

"12": {
        "config": {
            "group": "20",
            "on": true,
            "reachable": true
        },
        "ep": 18,
        "etag": "75031fec22a9760f05a1604edebac11b",
        "lastseen": "2021-04-17T06:19Z",
        "manufacturername": "Echostar",
        "mode": 1,
        "modelid": "Bell",
        "name": "Doorbell Sensor",
        "state": {
            "buttonevent": null,
            "lastupdated": "none"
        },
        "swversion": "3.2.2",
        "type": "ZHASwitch",
        "uniqueid": "00:08:89:00:01:d9:af:d2-12-0006"
    },

Strange that this says rechable = true while Phoscon disagrees.

@Smanar
Copy link
Collaborator

Smanar commented Apr 18, 2021

Oups sorry, I have read "doorbell" so in my mind was a "siren" not a button. So if I read correclty, it s a device you can connect to an existing doorbell, but it work as input but not ouput ?

Do you have access to the GUI ? I need log when you press the button, deconz/help/log with "info" and "info_l2"

@oywino
Copy link

oywino commented Apr 18, 2021

Well, that's the whole problem. Because it appears as "unreachable", nothing happens when I press the button.
We first have to make it appear correctly and reachable in deConz.

@Smanar
Copy link
Collaborator

Smanar commented Apr 18, 2021

No I don't say, phoscon but deconz, the application.
You have obligatory something visible on them when using a button in log

@Puntoboy
Copy link
Author

Puntoboy commented Apr 18, 2021 via email

@oywino
Copy link

oywino commented Apr 18, 2021

Sorry I haven’t read all the replies but my sage doorbell is showing in Phoscon and working great with HA.

Could you please share the Entity details that the Sage Doorbell is giving you in HA ?

@Puntoboy
Copy link
Author

Puntoboy commented Apr 18, 2021 via email

@oywino
Copy link

oywino commented Apr 18, 2021

(You forgot the images)

@Puntoboy
Copy link
Author

I didn't :) just the email didn't upload them.

image

image

@oywino
Copy link

oywino commented Apr 18, 2021

Well, thank you, but to me, that looks like the "Device" entry in HA followed by the "sensor" entry from Phoscon, right?
What I was hoping to see, is the "Entity" entry from HA. And please, don't use mobile phone images. I'd much rather see HA images from a full browser (PC or MAC) 🎵😊

@Puntoboy
Copy link
Author

Puntoboy commented Apr 18, 2021 via email

@Puntoboy
Copy link
Author

There is no entity.

image

@oywino
Copy link

oywino commented Apr 19, 2021

Exactly, that's what I don't see either. So you read the state of the bell into automations using deconz.event then?
Did you manage to decipher the event codes?

@Puntoboy
Copy link
Author

Ah yes sorry, I use Node-Red in HA to run the automation. It uses a direct connection to Deconz.

image

@oywino
Copy link

oywino commented Apr 19, 2021

Ok, I see. But still, it is the deconz.event node that you are using.
My problem is that the DoorBell sensor appear as "unreachable" in Phoscon, and consequently it never generates any events,
I am puzzled by the fact that the in JSON it is tagged as "reachable" while in Phoscon it is "unreachable".
I assume that's not the case with your device?

@Puntoboy
Copy link
Author

Puntoboy commented Apr 19, 2021

The sensor appears unreachable in mine as well, but I'm using the switch device (see the first screenshot I shared yesterday).

image

@Puntoboy
Copy link
Author

This is the switch device.

image

@oywino
Copy link

oywino commented Apr 19, 2021

Oh, thank you 👍 That was very interesting.
I now re-paired the sensor after upgrading deconz to v2.11 and now I also have two devices; A sensor and a switch. This is slowly moving forward thanks to your help 😊
Do you know the specs for your bell transformer?

@Puntoboy
Copy link
Author

The transformer was already installed in our house. It's this one https://www.amazon.co.uk/MDC1-01-Traditional-Chime-Built-Transformer/dp/B07CZMBKNH

@Smanar
Copy link
Collaborator

Smanar commented Apr 19, 2021

So the device appear in "sensors" AND "switches" but how many json have the device in this situation ?

@oywino
Copy link

oywino commented Apr 19, 2021

Only one that I could find.
deConz JSON only supports lights and sensors
Switches are not supported. They appear as sensors

@Smanar
Copy link
Collaborator

Smanar commented Apr 19, 2021

Ha, ok, it s normal, switches is something from phoscon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

10 participants