Vision smoke detector zs6101

Hi all,

Does any one have this and if so any idea if it wakes up to send battery level reort? If so I will get one.

I have the everspring detector and although good does not wake up to report battery level, this also means that when I heal my network it stays unconfigured untill I manualy wake it up.

Hope some one has some info.

Many thanks :slight_smile:

Sent from my HTC HD2 using Tapatalk 2

I don’t have either of these devices. Are you sure that it never wakes up? I’ve never seen a battery operated device that never wakes up. Usually they wake up every hour or two and usually the wakeup interval is configurable, though the defaults are usually fine.

I have Everspring door sensors that have an 1800 second(1 hour) default WakeupInterval. They report battery state, receive configuration and routing updates at that time.

Hi Z-Waver,

Thank you for responding.

Yes I agree its crazy but true. The device never wakes up it only does so if you manualy tell it too by taking off the cover and pressing the button.

If you know of a way to get it to wake up that would be ace but I am at a loss. It has the capability I beleive but Everspring did not program this function into the firmware :frowning:

As such if the 6101 does this I would swap out.

Sent from my HTC HD2 using Tapatalk 2

I’ve just got one of these to try it out: Vera does not recognise it correctly - it includes it as a _AVMISC device. I had to overwrite the device file with D_SmokeSensor1.xml to get it to show up as a smoke detector. The device appears to wake up every 30 minutes as configured but the battery level is not updated. I suspect this is due to the Vera implementation as the manual states it will report the battery status to the controller.

Hi fraisier,

Sounds promising then?..

Have you logged a request with mcv to update drivers for this?

If it is waking up have you tried creating a scene to poll the device to get battery level update? That may work? I can’t do that on mine as it just does not wake up at all unless manually done.

Just as anouther question, have you tried a heal on the item. I ask as because mine does not wake up it does not work well on a heal of the network as does not wake up to gain the config. If yours is waking up this should not be an issue, could you confirm?

Cheers Fraisier.

:slight_smile:
Sent from my HTC HD2 using Tapatalk 2

So I decided to go and get one of these and have added it to the network. It included fine and unlike @Frasier mine was recognised as a smoke detector so I did not need to change the D_SmokeSensor1.xml

@Frasier - have you had any more luck with the battery updates? I notice that the Everspring smoke detector I have has a battery level indicator but the vision one does not - could we try swapping or amending a file to achieve this do you think? This is a bit beyond me.

For me the fact that the unit wakes up is far better as it does not any longer cause issues when undertaking a network heal as it wakes up and responds. I am sure I could set a get battery level poll to run every 2 minute that would likely catch the unit when it work up but it would be great if we can get it supported in UI5 as standard.

@LightsOn
Thats interesting that yours configured correctly, maybe mine didn’t and that’s why it showed up incorrectly. I have not had much of a chance to play with it since and did not get around to emailing MCV with any query.

My device has always shown the battery status ok but i don’t think its updating (its still at 100% after a month or so) and I set DataMine to log any updates to the battery level and it does not seem to have recorded any time stamps but maybe that’s because the level has remained at 100%?

Let’s keep posting any observations as the fact that it wakes up regularly makes it a more attractive module than the Everspring version.

yes I agree - lets see how things go. I can confirm I have checked this morning and the system showed battery status so now just to see if it goes down over time.

I am running the MIOS Update Utility so perhaps I had a new update pushed to my device that you had not? hence perhaps why mine configured normally on its own?

I will post back with updates as I notice them