Need help with Nexia doorbell sensor (before I return it or burn it)

Configuration
21

You need to see what the value is in the topic.

this is the topic

ha/doorbell/notify

It has a value. You are completely ignoring it in your setup, aside from the last attempt with the mqtt sensor. You need to look at the topic and find out what the value is when pressed and unpressed.

22

ok, not sure if this helps but here is my MQTT logs (at the end is when I rang the doorbell),
does this help me?

1553184330: Sending PINGRESP to 75b1382d-ec15-4953-b553-4055e3b6b50d
1553184390: Received PINGREQ from 75b1382d-ec15-4953-b553-4055e3b6b50d
1553184390: Sending PINGRESP to 75b1382d-ec15-4953-b553-4055e3b6b50d
1553184450: Received PINGREQ from 75b1382d-ec15-4953-b553-4055e3b6b50d
1553184450: Sending PINGRESP to 75b1382d-ec15-4953-b553-4055e3b6b50d
1553184510: Received PINGREQ from 75b1382d-ec15-4953-b553-4055e3b6b50d
1553184510: Sending PINGRESP to 75b1382d-ec15-4953-b553-4055e3b6b50d
1553184570: Received PINGREQ from 75b1382d-ec15-4953-b553-4055e3b6b50d
1553184570: Sending PINGRESP to 75b1382d-ec15-4953-b553-4055e3b6b50d
1553184630: Received PINGREQ from 75b1382d-ec15-4953-b553-4055e3b6b50d
1553184630: Sending PINGRESP to 75b1382d-ec15-4953-b553-4055e3b6b50d
1553184648: New connection from 192.168.1.213 on port 1883.
1553184648: New client connected from 192.168.1.213 as FireFlyClient-1d4d (c1, k15, u'').
1553184648: Sending CONNACK to FireFlyClient-1d4d (0, 0)
1553184648: Received PUBLISH from FireFlyClient-1d4d (d0, q0, r1, m0, 'ha/doorbell/notify', ... (24 bytes))
1553184648: Sending PUBLISH to 75b1382d-ec15-4953-b553-4055e3b6b50d (d0, q0, r0, m0, 'ha/doorbell/notify', ... (24 bytes))
23

Looking at the source code. It looks like it is sending a JSON file as the MQTT payload. The JSON is parsed by Home Assistant. Looks to be the voltage of the battery. Sends an update of the battery voltage every time you trigger the doorbell. There were some other posts I saw on automations going off on restart of HA.

24

so, IYO, can I use that to work around the issue you think? or the source code will have to be updated and I would have to do a firmware update (if that’s possible)?
or…
I see I can use IFTTT also, configuring this with HA using it, would this work around the issue? (not great since it would depend on Internet connection but still…