I was mistaken, this is the version of the device type I’m using: https://github.com/jamesdawson3/SmartThings/blob/patch-1/Aeon%20Doorbell/device_type-aeon-doorbell-v0.4
Yea that’s the same version I’m using, plus your changes listed above
+1, same code, exact same issues. never got a ring outside of Aeon Siren type, no matter what code variation or changes I made.
[quote=“C_Hobbs, post:276, topic:28889, full:true”]
Yea that’s the same version I’m using, plus your changes listed above
[/quote]Have you looked at the Device Events for the doorbell from the My Devices section of the website? It should show whether or not the commands are making it to the device.
This is from the “all” Device Events…
2016-01-12 9:12:01.502 PM EST
moments ago COMMAND btest btest command was sent to Aeon Doorbell - RV v0.4 true
2016-01-12 9:11:43.461 PM EST
moments ago COMMAND refresh refresh command was sent to Aeon Doorbell - RV v0.4 true
2016-01-12 9:11:38.918 PM EST
moments ago COMMAND btest btest command was sent to Aeon Doorbell - RV v0.4 true
2016-01-12 9:11:36.558 PM EST
moments ago COMMAND configure configure command was sent to Aeon Doorbell - RV v0.4 true
2016-01-12 9:11:32.448 PM EST
moments ago COMMAND refresh refresh command was sent to Aeon Doorbell - RV v0.4 true
[quote=“C_Hobbs, post:278, topic:28889, full:true”]
@techvudu thanks for letting me know I’m not alone in beating my head against this wall!
[/quote]ST is having tons of problems tonight so I’d hold off on fighting with it until they straighten things out.
I was able to fix all of my issues and everything all seems to stem from the code defaulting the siren to ringtone #6 but all of us new users only have 5 ringtones out-of-the-box!
So I changed the default value to 5, saved, self published, removed and re-added the device; and a flood of info just came pouring into my logs and now everything seems to be working!
efd1e45e-9e3d-4386-939d-f84fcc77be3f 9:13:49 PM: debug lowBatteryHandler: Aeon Doorbell - RV v0.4 battery is 100
0904b4fb-e164-4902-89d3-6c8e8d87c399 9:13:48 PM: debug Aeon Doorbell - RV v0.4 remote battery is good
0904b4fb-e164-4902-89d3-6c8e8d87c399 9:13:48 PM: debug —CONFIGURATION REPORT V1— Aeon Doorbell - RV v0.4 parameter 42 with a byte size of 1 is set to [0]
efd1e45e-9e3d-4386-939d-f84fcc77be3f 9:13:46 PM: debug lowBatteryHandler: Aeon Doorbell - RV v0.4 battery is 100
0904b4fb-e164-4902-89d3-6c8e8d87c399 9:13:46 PM: debug —CONFIGURATION REPORT V1— Aeon Doorbell - RV v0.4 parameter 11 with a byte size of 1 is set to [0]
0904b4fb-e164-4902-89d3-6c8e8d87c399 9:13:46 PM: debug Aeon Doorbell - RV v0.4 remote battery is good
0904b4fb-e164-4902-89d3-6c8e8d87c399 9:13:46 PM: debug —CONFIGURATION REPORT V1— Aeon Doorbell - RV v0.4 parameter 42 with a byte size of 1 is set to [0]
0904b4fb-e164-4902-89d3-6c8e8d87c399 9:13:45 PM: debug —CONFIGURATION REPORT V1— Aeon Doorbell - RV v0.4 parameter 11 with a byte size of 1 is set to [0]
0904b4fb-e164-4902-89d3-6c8e8d87c399 9:13:44 PM: debug —CONFIGURATION REPORT V1— Aeon Doorbell - RV v0.4 parameter 10 with a byte size of 1 is set to [0]
0904b4fb-e164-4902-89d3-6c8e8d87c399 9:13:44 PM: debug —CONFIGURATION REPORT V1— Aeon Doorbell - RV v0.4 parameter 10 with a byte size of 1 is set to [0]
0904b4fb-e164-4902-89d3-6c8e8d87c399 9:13:44 PM: debug —CONFIGURATION REPORT V1— Aeon Doorbell - RV v0.4 parameter 8 with a byte size of 1 is set to [10]
0904b4fb-e164-4902-89d3-6c8e8d87c399 9:13:43 PM: debug —CONFIGURATION REPORT V1— Aeon Doorbell - RV v0.4 parameter 8 with a byte size of 1 is set to [10]
0904b4fb-e164-4902-89d3-6c8e8d87c399 9:13:43 PM: debug —CONFIGURATION REPORT V1— Aeon Doorbell - RV v0.4 parameter 5 with a byte size of 1 is set to [1]
0904b4fb-e164-4902-89d3-6c8e8d87c399 9:13:42 PM: debug —CONFIGURATION REPORT V1— Aeon Doorbell - RV v0.4 parameter 5 with a byte size of 1 is set to [1]
0904b4fb-e164-4902-89d3-6c8e8d87c399 9:13:42 PM: debug —CONFIGURATION REPORT V1— Aeon Doorbell - RV v0.4 parameter 2 with a byte size of 1 is set to [1]
0904b4fb-e164-4902-89d3-6c8e8d87c399 9:13:41 PM: debug —CONFIGURATION REPORT V1— Aeon Doorbell - RV v0.4 parameter 2 with a byte size of 1 is set to [1]
0904b4fb-e164-4902-89d3-6c8e8d87c399 9:13:41 PM: debug —CONFIGURATION REPORT V1— Aeon Doorbell - RV v0.4 parameter 81 with a byte size of 1 is set to [1]
0904b4fb-e164-4902-89d3-6c8e8d87c399 9:13:40 PM: debug —CONFIGURATION REPORT V1— Aeon Doorbell - RV v0.4 parameter 81 with a byte size of 1 is set to [1]
0904b4fb-e164-4902-89d3-6c8e8d87c399 9:13:40 PM: debug —CONFIGURATION REPORT V1— Aeon Doorbell - RV v0.4 parameter 80 with a byte size of 1 is set to [2]
0904b4fb-e164-4902-89d3-6c8e8d87c399 9:13:39 PM: debug —CONFIGURATION REPORT V1— Aeon Doorbell - RV v0.4 parameter 80 with a byte size of 1 is set to [2]
0904b4fb-e164-4902-89d3-6c8e8d87c399 9:13:38 PM: debug —FIRMWARE MD REPORT V2— Aeon Doorbell - RV v0.4 has Checksum of 46903 firmwareId: 1080, manufacturerId: 1080
0904b4fb-e164-4902-89d3-6c8e8d87c399 9:13:38 PM: debug —FIRMWARE MD REPORT V2— Aeon Doorbell - RV v0.4 has Checksum of 46903 firmwareId: 1080, manufacturerId: 1080
0904b4fb-e164-4902-89d3-6c8e8d87c399 9:13:38 PM: debug —VERSION REPORT V1— Aeon Doorbell - RV v0.4 is running firmware version: 1.11, Z-Wave version: 3.92
0904b4fb-e164-4902-89d3-6c8e8d87c399 9:13:38 PM: debug —VERSION REPORT V1— Aeon Doorbell - RV v0.4 is running firmware version: 1.11, Z-Wave version: 3.92
0904b4fb-e164-4902-89d3-6c8e8d87c399 9:13:37 PM: debug AssociationReport: ‘AssociationReport(groupingIdentifier: 1, maxNodesSupported: 5, nodeId: [1], reportsToFollow: 0)’, hub: ‘1’ reports nodeId: ‘1’ is associated in group: ‘1’
0904b4fb-e164-4902-89d3-6c8e8d87c399 9:13:37 PM: debug AssociationReport: ‘AssociationReport(groupingIdentifier: 1, maxNodesSupported: 5, nodeId: [1], reportsToFollow: 0)’, hub: ‘1’ reports nodeId: ‘1’
This is making even more sense.
I replaced the first file with a silent file to avoid sounds playing in the event of a power blip. However, since I am cascading them - i.e. if Doorbell Switch #1 goes on, RM makes Doorbell #2 playtrack(7) or what not - now when I plug 1 in, 2 makes playtrack 7 - even though that’s not what is intended - the doorbell being powered up must put the switch in on mode.
At least that’s a theory.
May not be in the cards, but utlimately, if the switches only went on when certain tracks played that would be ideal. I don’t know enough about the device’s inner workings or the the DH to know if that’s possible or realistic.
I think what would be ideal, ultimately, is if the doorbell switch were to only ever show on only when the sound defined by device properties was played. Same for alarm or any other ‘switches’ that may integrate into the dh.
If coarse that may not be possible via the dh
Yeah, from what I’ve gathered, if parameter 80 is set to 2, then anytime the doorbell plays a sound (during power up, button pressed, or playTrack command), the device in SmartThings will show as “On”. On the other hand, if parameter 80 is set to 0, then SmartThings will always show the device as “Off” when sounds are played. Given the current device handler, I’ll admit the easiest workaround would be to have two separate doorbells - one to receive button pushes (and thus send notifications, trigger rules, etc), and another to simply just play tracks on command. I’m hoping the device handler can be improved to more effectively combine these two use cases, but I’m afraid I don’t currently have the expertise to pull it off… 
Okay…the second I don’t think I can do it, I think of a better way to do it. Give this a shot, I’ve come up with a way to playTrack, without the switch turning on, and without having to set parameter 80…seems to be much more robust! This still won’t solve the power on issue, but it should eliminate the intermittent notifications from the playTrack command.
1 Like
Nice!
I will be able to run this through Friday and will report back then.
Thank you for working on this first and foremost.
Now I either an an idiot (highly possible) or something aint right
I installed your v0.5 device handler and have it paired to my door bell receiver. I get the correct screen with the options but it does not do anything when the door bell is presses (The chime dings but nothing in ST) I can tell the drdiver to change the tone or volume but it doesnt take.
I get it to light up if I slide the volume slider
0cee3ee5-7d67-4ac1-992e-688031d29a1f 6:28:56 PM: error java.lang.NullPointerException: Cannot invoke method toInteger() on null object @ line 309
and get an error in my log
I don’t seem to be getting any errors here…can you confirm that everything was functional with @Robert_Vandervoort v0.3 code? Also, have you hit the configure tile?
If you go into the device preferences in the IDE, what does it look like? Mine looks like this:
Are all the settings set? Any extra settings?
Seems like you have some extra settings in there…might be residual from another device type. Not sure how to delete them…try puttting a value in that empty box. Perhaps thats throwing the null error. Also, volume range is from 1-10, change that one too.
Line 359 still hasn’t been fixed and that’s most likely why you’re getting the error on line 309.
Line 359 should be:
if (!state.prefAlarmtone) state.prefAlarmtone = 1
1 Like