What did you do with Vera today?

Community Playground General Discussions
901

[quote=“clippermiami, post:900, topic:172785”][quote=“clippermiami, post:889, topic:172785”]2@Vera 3 / UI5

Complete installation of 7 @ Vision ZS6101 Smoke Detectors (Monoprice). Because functioning Smoke Detectors are critical as a check on their operation I created PLEG code to notify me via SMS/Pushover if any of them fail to Wake Up within a 2 hour window.[/quote]

Vera 3, UI5, 1.5.672

Yesterday I had the first REAL smoke incident with the new detectors and found something interesting.

Previously I had obtained some aerosol detector tester (http://www.amazon.com/gp/product/B001B3BL0S?psc=1&redirect=true&ref_=oh_aui_detailpage_o02_s00) for periodic testing of the detectors. When I used this stuff the sendor sounds for anywhere etween one to three minutes and Vera reports it as expected. The test eventually times out and the sensor resets itself.

Yesterday I was cooking and created a bit more smoke than usual and the detector went off. (Million dollar idea here: A smoke detector that voice recognizes the phrase “I’m cooking stupid” and shuts itself off) Anyway, the kitchen detector sounded, Vera alerted as expected, sent SMS and turned on all the lights that were programmed to go on to provide a path to a door. The alarm stopped sounding after a few minutes but it never reset itself and continued to show tripped in Vera. I found that a quick press of the test button caused it to chirp three times and it reset in Vera.

But it was most interesting that with the chemical smoke detector test fluid it tripped and reset itself whereas with actual smoke it required a manual reset. Something new every day :)[/quote]

I’m unsure how the detector would know the difference and act differently to each. I suspect it has more to do with VERA updates that have changed the way it resets or the fact that one even lasted longer then the other. But with the way they detect smoke I find it highly unlikely that it’s only the difference between test smoke and real smoke.

902

[quote=“integlikewhoa, post:901, topic:172785”][quote=“clippermiami, post:900, topic:172785”][quote=“clippermiami, post:889, topic:172785”]2@Vera 3 / UI5

Complete installation of 7 @ Vision ZS6101 Smoke Detectors (Monoprice). Because functioning Smoke Detectors are critical as a check on their operation I created PLEG code to notify me via SMS/Pushover if any of them fail to Wake Up within a 2 hour window.[/quote]

Vera 3, UI5, 1.5.672

Yesterday I had the first REAL smoke incident with the new detectors and found something interesting.

Previously I had obtained some aerosol detector tester (http://www.amazon.com/gp/product/B001B3BL0S?psc=1&redirect=true&ref_=oh_aui_detailpage_o02_s00) for periodic testing of the detectors. When I used this stuff the sendor sounds for anywhere etween one to three minutes and Vera reports it as expected. The test eventually times out and the sensor resets itself.

Yesterday I was cooking and created a bit more smoke than usual and the detector went off. (Million dollar idea here: A smoke detector that voice recognizes the phrase “I’m cooking stupid” and shuts itself off) Anyway, the kitchen detector sounded, Vera alerted as expected, sent SMS and turned on all the lights that were programmed to go on to provide a path to a door. The alarm stopped sounding after a few minutes but it never reset itself and continued to show tripped in Vera. I found that a quick press of the test button caused it to chirp three times and it reset in Vera.

But it was most interesting that with the chemical smoke detector test fluid it tripped and reset itself whereas with actual smoke it required a manual reset. Something new every day :)[/quote]

I’m unsure how the detector would know the difference and act differently to each. I suspect it has more to do with VERA updates that have changed the way it resets or the fact that one even lasted longer then the other. But with the way they detect smoke I find it highly unlikely that it’s only the difference between test smoke and real smoke.[/quote]

Yeah, makes no sense to me either but it seems to work that way :slight_smile: Perhaps its duration, if it runs more than a minute or so then it doesn’t self-reset, or something. I haven’t done any significant testing but it worked that way yesterday. Today, who knows, after all it is Vera :slight_smile:

I suppose it could have something to do with the ionization characteristics. The test stuff isn’t “smoke” per se but a volatile liquid that simulates it. Maybe the detector behaves differently in this case. No big deal, as long as I know what it does and hopefully anyone else that encounters similar behavior :slight_smile:

903

[quote=“clippermiami, post:902, topic:172785”]Yeah, makes no sense to me either but it seems to work that way :slight_smile: Perhaps its duration, if it runs more than a minute or so then it doesn’t self-reset, or something. I haven’t done any significant testing but it worked that way yesterday. Today, who knows, after all it is Vera :slight_smile:

I suppose it could have something to do with the ionization characteristics. The test stuff isn’t “smoke” per se but a volatile liquid that simulates it. Maybe the detector behaves differently in this case. No big deal, as long as I know what it does and hopefully anyone else that encounters similar behavior :)[/quote]

Usually it’s just a photo beam that’s broken which trips the detector (but I guess that depends on what kind of detector it is) and smoke, spider, or piece of paper all trips the same.

Whens the last time you tested with the test can? I was thinking it may have been awhile and since that time and yesterday when the real smoke tripped it vera update has changed the way it handles the smoke in that time? If you tested both yesterday then that is out the window and I would go back more to the time issue. But I wasn’t under the impression that you tested it with the can smoke yesterday.

904

[quote=“integlikewhoa, post:903, topic:172785”][quote=“clippermiami, post:902, topic:172785”]Yeah, makes no sense to me either but it seems to work that way :slight_smile: Perhaps its duration, if it runs more than a minute or so then it doesn’t self-reset, or something. I haven’t done any significant testing but it worked that way yesterday. Today, who knows, after all it is Vera :slight_smile:

I suppose it could have something to do with the ionization characteristics. The test stuff isn’t “smoke” per se but a volatile liquid that simulates it. Maybe the detector behaves differently in this case. No big deal, as long as I know what it does and hopefully anyone else that encounters similar behavior :)[/quote]

Usually it’s just a photo beam that’s broken which trips the detector (but I guess that depends on what kind of detector it is) and smoke, spider, or piece of paper all trips the same.

Whens the last time you tested with the test can? I was thinking it may have been awhile and since that time and yesterday when the real smoke tripped it vera update has changed the way it handles the smoke in that time? If you tested both yesterday then that is out the window and I would go back more to the time issue. But I wasn’t under the impression that you tested it with the can smoke yesterday.[/quote]

The actual test date was Sept 14, so just over a month. According to their web site it claims to be just a photoelectric detector. I’ve been on UI5 1.5.672 now for half a year of so so no updates involved. Maybe the time duration?

905

[quote=“clippermiami, post:904, topic:172785”][quote=“integlikewhoa, post:903, topic:172785”][quote=“clippermiami, post:902, topic:172785”]Yeah, makes no sense to me either but it seems to work that way :slight_smile: Perhaps its duration, if it runs more than a minute or so then it doesn’t self-reset, or something. I haven’t done any significant testing but it worked that way yesterday. Today, who knows, after all it is Vera :slight_smile:

I suppose it could have something to do with the ionization characteristics. The test stuff isn’t “smoke” per se but a volatile liquid that simulates it. Maybe the detector behaves differently in this case. No big deal, as long as I know what it does and hopefully anyone else that encounters similar behavior :)[/quote]

Usually it’s just a photo beam that’s broken which trips the detector (but I guess that depends on what kind of detector it is) and smoke, spider, or piece of paper all trips the same.

Whens the last time you tested with the test can? I was thinking it may have been awhile and since that time and yesterday when the real smoke tripped it vera update has changed the way it handles the smoke in that time? If you tested both yesterday then that is out the window and I would go back more to the time issue. But I wasn’t under the impression that you tested it with the can smoke yesterday.[/quote]

The actual test date was Sept 14, so just over a month. According to their web site it claims to be just a photoelectric detector. I’ve been on UI5 1.5.672 now for half a year of so so no updates involved. Maybe the time duration?[/quote]

Whats ui5? ;D

huh yeah maybe the time… who knows.

906

What did I do with vera today?
Nothing new, still waiting for new UI7 firmware with bugfixes and waiting for support to fix multiple problems with multiple tickets.

907

Z-waved my Bathroom light
No that its needed, but now vera can turn back on the Water-Pump if someone goes “off hours” to the bathroom

908

Thats the firmare that actually works :stuck_out_tongue:

909

Thats the firmare that actually works :p[/quote]

;D ;D ;D

910

Used the countdown timer plugin for my Halloween lights/display.
When the doorbell is pushed after dusk, I have my normal outside lights turn off, then some RED LED strip lights start flashing, as well as a sonos speaker that plays an mp3- woman screaming. After 1 mins the normal scene is run to switch everything back to normal.
My neighbor didn’t find it too funny when I set it up last night but we were laughing our #$% off watching through the camera ;D

911

Thats the firmare that actually works :p[/quote]

;D ;D ;D[/quote]

ui7 is the same as ui5 75% working, it’s just a different kind of broken. Best thing ui5 has going for it is no more updates. So nothing will get worse as it sometimes does in ui7 after an update. But also means nothing can ever improve or get better either.

912

[quote=“dp0100, post:910, topic:172785”]Used the countdown timer plugin for my Halloween lights/display.
When the doorbell is pushed after dusk, I have my normal outside lights turn off, then some RED LED strip lights start flashing, as well as a sonos speaker that plays an mp3- woman screaming. After 1 mins the normal scene is run to switch everything back to normal.
My neighbor didn’t find it too funny when I set it up last night but we were laughing our #$% off watching through the camera ;D[/quote]

That is an awesome idea! I’m going to have to steal it for my house.

913

hahahaha that made my day … but its true !!

i still live with the “Never touch a running system” ideology
but my VeraLite does get sweaty more often now … 100 devices my ass … haha

but its definitely in the “die hard” category of devices with UI5 on it (which is a compliment this days)

914

I’m actually quite happy with the performance of my Veralite but I can not expand on it anymore.

915

Good old UI5…

916

Time to move some stuff to openLuup running on RPi or similar?

917

Time to move some stuff to openLuup running on RPi or similar?[/quote]

Not sure if I’m able to invest the time to learn all that. Not quite clear what I would need to learn to pull it of. Do you have an SD card image for RPi2 where all the hard core linux stuff is already prepared?

918

Actually, that’s exactly the reason I use BeagleBone Black instead of RPi… has all the image installed and it’s just a couple of one-liners to add Lua and a couple of necessary modules.

Still a work in progress, but it seems that GCal3 and IosPush and Sonos are working OK. Perhaps come back to it when it’s a bit more mature, if you’re anxious about the effort involved at the moment.

919

I will keep following your progress like always akbooer :wink:

920

I did something similar here, too. I’ve got an asterisk PBX for landline calls so I wrote an AGI that captures the caller id and name (I have an IVR to route calls for me and members of my family), then passes it to Vera through an http luup call into my Sonos which broadcasts it throughout the house (“chime there is an incoming call for from ”).

I’ll probably create a simple database for common numbers that call the house, then have the AGI dip into that to fix the inconsistency of caller id name (“there’s an incoming call for Joe from Grandma” or something similar).

I was using GoogleTTS for the announcements but they recently did something to their API to break requests so now I’m using Microsoft Translate … at least until I install OSX TTS on an unused mac mini that I have (so I’m not at the mercy of cloud based tts providers).

Good stuff.