Everspring Doorbell UTSE03A

Community Playground General Discussions
1

I thought this device deserved a dedicated named topic rather than under a more generic description (http://forum.micasaverde.com/index.php/topic,7473.0.html) as I wish I had checked the forum before purchasing the unit. Like other posters I found that while I can include both the Push Button (_Scene Controller) and Doorbell (_AV Misc) so they appear on the dashboard (EU, V2, UI5 1.5.408), there appears to be nothing that can be done to detect a button push or activate the doorbell despite references in the manual to primary & secondary controller inclusions, associations, etc.

However I can report some minor progress in relation to the Doorbell: By replacing the device file (advanced settings) with D_BinaryLight1.xml, the Doorbell widget appears like a binary switch which can then be turned on to activate the chime. At this point I can only lament the lack of vision of the product designers, who having provided a facility for 5 different chimes (which the user can alter), failed to provide an option to allow the user to select the chime via z-wave command (like the way the Fortrezz siren can be controlled). This would have made it an excellent multipurpose annunciator.

Unfortunately I have not had any progress on the push button: it appears as a generic _Scene Controller but on the ‘Scenes’ tab none are listed for selection. At this point I am out of my depth whether some aspect of the configuration file could be modified to detect the button press at least. I appreciate not many of the advanced users may have this device but if anyone has any suggestions I’m game to try it. For info the listed capabilities of the device are:

Capabilities 18,150,0,1,1,1,B,|114,134,
Manf Info 96,10,1
Version 2,2,64,1,1

By way of comparison the Aeon Minimote uses the same configuration file (D_SceneController1.xml) and shows:
Capabilities 18,150,0,1,1,1,B,|112,114,133,134,155,
Manf Info 134,1,3
Version 2,2,78,1,17

2

Hi Frasier,

Excellent work! you have my full support on this - if we can get the push button working we are almost there.

Happy to test on my ket if any one has any thoughts.

Many thanks again all.

I will of course keep posted with developments from Everspring as they progress…

3

If that is the [tt]Scenes[/tt] tab of the device, then it may be ok: this tab is not activated for all scene controllers.

Can you create a scene that turns on the chime and select the scene controller as the trigger, with [tt]A scene is activated[/tt] as the event? If so, the question then is what to put for scene number. Could be 1, could be something else.

Capabilities 18,150,0,1,1,1,B,|114,134,
That's a short list of supported command classes. I guess I had expected 133 ([i]Association[/i]) to be in there, so the button can be associated with other devices (Vera in this case).

Also, did you include the push button as secondary controller?

4

Hi oTi,

Many thanks for your time with this.

So i can confirm i have the bell added as above and it works as mentioned - great news! :slight_smile: many thnaks Frasier.

I have added the button as a secondary controller and have followed your sugestion to activate a scene - no joy sadly :frowning:

going to try tinkering - perhaps change the .xml like with the chime but this time for one like the minimote?

Edit: .xml is the same on both “D_SceneController1.xml”

Edit2: tried number 1 to 5 and no joy, also tried resetting push button and adding again as secondary controller - no joy. push button cant be configured either - “unable to get any infromation on node”

5

oTi’s comment on the missing 133 command class reminded me of a similar issue with a TKB switch (http://forum.micasaverde.com/index.php/topic,6233.msg53277.html#msg53277) so I tried adding 133 to the capabilities on the Advanced tab as per that procedure but no success. Where can I find a list of what other command class’ corresponds to the configuration codes? I’m curious what codes 112 and 155 represent?

I’ve looked at the logs and although the button seems to have been successfully included as a secondary controller, nothing seems to happen when the button is pressed, though I guess that could be because it is not used in any scenes or triggers. Is there another way of checking if Vera is detecting when the pushbutton is pressed?

One weird thing is that on the settings tab the configuration date is initially correct and later gets reset to 1 Jan 1970 00.00 ?

6

Mmm, that’s (probably) not good.

The command classes (the numbers after the | in the [tt]Capabilities[/tt]) are listed on this wiki page, sorted 2 different ways.

When you attempt to associate the bell and the button manually (i.e. the way it is done without Vera), does that work in this current state?

7

Thanks for the link to the command classes.

I can exclude both devices from Vera although the push button widget needs to be manually deleted whereas the doorbell automatically deletes as part of the exclusion process.

The door bell can then be included with the push button (as the primary controller) and when the button is pressed the door bell chimes.

The push button seems a little temperamental when trying to include it as a secondary controller you also need to make sure it has been reset before trying inclusion. But even when it seems to have been included ok it does not appear to do anything. According to the manual it stays awake for four minutes after exclusion and reset; during this time you can activate “configure node right now” and it communicates with Vera but once it goes to sleep it never appears to wake up!! There is no obvious option for wakeup interval and nothing seems to happen even when the push button is pressed.

I’ve tried associating the doorbell with it under group 1 (device options tab) while it was awake but it does not work and never returns a current value.

8

Interesting. And with the button as secondary controller, can you successfully manually associate the button and the bell (or is there no separate way to associate the two)?

9

I think the problem is that the push button does not associate correctly with Vera as a secondary controller. According to the manual, if the push button is included as a secondary controller then for association:
“Push button is compatible with with other z-wace enabled devices. Please ensure they have completed inclusion before association. Press the (A)(E) key 3 times (within 1.5 secs), Led flashes off & on alternatively for 30 secs. Put z-wave enabled device (slave) into association mode first, and then put another z-wave enabled device (master) into association mode afterwards”

The problem seems to be that although the push button was (apparently) correctly included as a secondary controller, when you push the (A)(E) button 3 times you dont get any LED flashing. Hence my conclusion that the original inclusion as a secondary controller was not in fact executed properly.

10

Hi Both,

The curent finding match mine also. MCV support stated in a shared email to everspring on this subject:

“We need to know more information on how to add the push button to another Z-Wave controller. Also, we need to know the commands that the push button is sending, because we have tested and we don’t receive any replies from the push button when it is pressed. Please let me know this information.”

but the reply from eversping after 10+ emails over 8+ weeks and 3+ different representatives:

"I understand the application you are seeking for and know the modification
might increase our sales for Door Bell, however, the resource limit issue, we
have to evaluate the real demand and RI.

Bad news is currently we only got request from you, we are afraid we have
difficulties to kick off the modification even pass the evaluation at this
moment, but I will have our RD team to put this on their list and will keep you
updated in time if there is any further action. Thank you for your understanding."

:o …I dont have understanding - one hour with one of there developers and we could get the commands we need to get this working - I even offered to pay for the developers time! I am awaiting a reply from my responce to the above to see if they come back to say they will at least ask a developer to have a look in his lunch hour or something.

I think the dificaulty is I as others may have paid a small fortune for this device but they retail it to wholesale at around 30 bucks s0 as such we are very small in there eyes and unless we said we wanted say 100 units we may be waiting some time.

Any coders fancy having a go at a firmware update?

Hope my rambles help - together we will get it working! 8)

  • Lights_On
11

Hi,
In fact that’s a bad news. I understand your frustration.
I’m also looking for a Zwave doorbel solution. Even RFX seems not easy to find.

The reply from eversping is also understandable. Why put RD ressources into a project whith no potential.
Maybe we can show them that there is in fact a lot of people searching for Zwave doorbel by creating a poll.
The question could be “are you interested by a Zwave solution”.
Yes at any price
Yes at decent price
Already build home malde solution
Not interrested.

Just a suggestion…

Have a nice day,

12

:frowning: This is a stupid situation that ultimately damages the reputation of z-wave as an “interoperable” standard. The two successfully pair as standalone devices so appear to implement the z-wave standard.

To be fair, it appears that Everspring seems to be sitting on its hands by not providing more information regarding the inclusion/association process for the push button to MCV. I suspect that no firmware modifications would even be necessary if they just provided adequate information - unless there is an actual bug in their firmware which stops the pushbutton transmitting anything if it is acting as a secondary controller. If that is the case then they are in breach of consumer law by selling a product that is not fit for purpose (i.e. can’t operate as a secondary controller despite the manual stating it does).

I urge any owners of this device to email both Everspring and the retailer they purchased from to complain that the device is not performing as described. I have not seen any retailer provide a warning that this device will not operate within a wider z-wave network, so they are also potentially in breach of consumer law. As individual consumers we may not have much impact but the retailers should have the volume purchases to carry influence.

It would be interesting if anyone using a PC based Z-wave controller could try this device, maybe more of the z-wave communications would be exposed so we could understand what is (or not) happening. I had a look at the Homeseer and Fibaro forums and see no mention of the device.

I don’t suppose the z-wave certification reports are publicly available? That might provide some clues.

13

Exactly; it seemed like there were issues getting the button to even be properly included as secondary controller, so to validate that I was wondering if it the button and bell could be associated the ‘normal’ way. Apparently not.

Has anyone tried with Z-Wave firmware 2.78 on Vera? (Warning: I don’t think you can just downgrade and upgrade the firmware, so this may not be an easy thing to try, depending on your situation, and probably requires actions along the lines of backing things up, then downgrading, wiping the Z-Wave network (or Vera), testing, then upgrading and restoring the backup to end up with what you had previously.)

Also, does anyone have 2 sets of these / is it possible to include a second push button into another push button’s network? In other words: does the secondary controller mode work in a non-Vera environment?

14

@ oTi,
I have a virgin V2 that I could try at the w/end. Any idea whether UI4 or 5 would be preferable?
In the event that this might make a difference, would you expect that a workaround could then be achieved as I suspect that running 2.78 would not be option for most users?

15

Hi All,

Its great to see this getting motion.

As you are all aware I have been in comunication f0or some time with MCV and Everspring to get a resoloution - even by paid methods and nothing… I will keep trying.

I dont have 2 devices so cant test this sadly.

I dont use the older firmware so before potentional downgrade upgrade scenarios is any one out there with the fiormware and a unit to test? if not i will.

I agree a firmware update is not realy needed - just a chat with an engineer hence my mail some months agao to everspring stating:

“[]…Please could you kindly speak with those able to supply this detail and share it with us? Also it may be better is we find the best informed engineer with answers to all questions on this product and have both that engineer and the MCV Developer talk directly to work together to resolve the issue perhaps?”

why do we think they dont wish to shar the parameters needed?

A poll may be usefull but one would think a quick chat with an enginners at a customers expence / cost would be exceptable right? no a big ask and we are all busy but 5 mins or an hour - we can all fit that in somewhere even if schedualed for 8 weeks time for example - always a slot to do it at some point. apprently not.

I will try and call my “latest” contact at everspring again now but think thay are closed so will be first thing tomorow.

@ oTi is there a way to find all params from any z-wave device - say anouther third part tool - we may then be able to buil custom luup code?

16

Hi All,

Just spoke to eversping again…

So my question to you here in the forum is have we identified yet exactly what we need from them? I have understood that in essence we need a full list of the command class details and any other operation information to empower us to be able to identify why the device is not working.

I would be greatfull for any specific desired questions to add into my email.

My contatc at everspring has asured me she willt ake the email to the PM (i asume project manager) of the device tomrow morning as it is curently 8pm there now and he has finished for the day. This PM will then decide if it is possible to disclose these details given the design is owned by a customer of Everspring and not Everspring them selfs. They have stated the delay in support so far is due to ther current work load - I have stated i understand how busy we can all get but answere simple questions need not tske several months. I am quietly confident we may get a suitable resoloution in the morning following my call however would be rgeatfull of others input as to the exatc questions / request you all think we need to be asking.

Mnay thanks and hope this helps.

17

@LightsOn, ideally it should be MCV who provide the details of what they require to ensure Vera can communicate with the pushbutton. I’m not familiar enough with the z-wave protocol to ask any sensible questions; perhaps oTi will have some input. In essence they will need to provide the details of the sequence & formatting of the z-wave commands expected to be exchanged between the pushbutton and a primary controller when it is being included as a secondary controller.

This issue of the design owned by a customer seems a bit of a smokescreen. Legally if they sell it (with their name), then they are responsible for ensuring it works as described. Z-wave is supposedly an interoperable standard and to date no one seems to have got this device to work within a wider network. They should either provide the required information or withdraw the claims and/or the product. Selling a non-conforming product and then declining to fix the mess due to other priorities is not an acceptable answer for a supposedly reputable manufacturer. I’m sure you can phrase this in a more tactful way to keep the dialogue going… :wink:

18

Hi Frasier,

Mnay thnaks - I shall “wrap” your thoughts nicely :wink:

I have input from MCV nad also just had an emial from them on this saying thnak you for not giving up with everspring - good work 8)

I shall see of oTi has any other input and will send the email late - keep everything crossed for some kind of helpfull answere fronm them…

19

All,

I have just ordered this item from one of my suppliers here in the UK, and it would be nice to see it working properly as it should be.

Should I email my supplier and advise them of this issue?

Many thanks,

Mike

20

Hi Mike,

May be worth it we need all the elp we can get - hope you didnt pay the circa £150…

Kind regards,
-Lights_on