Teken

I appreciate the feed back this looks to be a larger task then first envisioned. I know you already linked the calendar program and most of the required code is there so some of it needs to be modified etc. But, its the other portion of the code which makes me take pause. I may have to abandon this idea until perhaps 5.XX offers something similar to what I need. At the current time my little box is a little taxed and don't know if adding more programs will cause it to stumble. It would be really great to see one day the ISY have just a native calendar where a person could just pick and have follow up options as is now to repeat, from day, month, year, from this time etc. But also have the ability to recall a known state / time stamp. I guess when you come from other industrial applications where these features are just there. Its not something a person thinks about until its not. I am going to consider the options laid out here and decide if the time vs investment will be worth the over all effort placed. Thank You both . . .

If all steps have been done and its not the battery its possible you have a bad unit. Its pretty rare to be honest because I can count on one hand the amount of people who have complained about a bunk MS sensor. I wouldn't waste anymore time with this and just initiated a RMA so you can get up and running again. When you have time please do state the production date and ISY firmware for the sensor. You never know there might be a bad batch floating around . . .

So the above can be inserted into a custom e-mail and each time the e-mail is sent it will reflect either the same data or changed data?

Thank you both but in case this was not made clear. My over all intent is to maintain the same date and time until there is a change in state for the values listed. So if the lowest temp was recorded on December 01, 2015 at 12:00 PM as -29. This value should survive a reboot and firmware upgrade. If the low temp changes say on December 05, 2015 at 3:33 PM as -35. This new value and time stamp should be updated and in place. I don't think the listed programs will do this, right?

Sounds simple but unfortunately no easy way to obtain said data. I do hope you realize you Eastern folks do sound a little off eh? Ha . . .

When you return please do measure the battery in case it was on the shelf for a long period of time. Its one of those things where you don't expect to see a flat cell but it happens.

I take it from your reply what I am asking can't presently be done?

Harold, You sure are patient and I solute you for waiting so long. Its safe to say many would not have held out this long before deploying their system. But I can relate because I was in the very same boat when I was interested in deploying a temperature / humidity detection grid in my home. At the time there wasn't anything I felt were the right match based on my criteria. This was also seen with the RPi as I didn't feel the first and second generations of these devices were sufficient to meet my needs now and into the future. Years later the RPi 2 was released and it was worth the wait knowing I was future proofed. I truly believe if and when the Smartlabs gives UDI the nod to flash the PLM chips. We will see many great things from this company because those across the pond will finally be able to purchase a ISY Series Controller. This new and untapped market alone will provide needed income to allow UDI to push forward in many fronts. Consider if only 1000 EU users purchase the ISY Series Controller and how that will help the companies revenue stream. Imagine 10,000 users? All of the above numbers are so small when people look at the amount of people in the EU but it puts into perspective what a small number of people can do for a company.

Time permitting can you change out the battery again and insure its above 9 VDC. Also try another hard reset of the device and then delete it from the ISY and add it back in and report success / failure. Is the device under two years old?

With the latest Smartlabs 2.XX hardware which uses better capacitors along with firmware to address the ALL ON / ALL OFF. If you really need a new 2413S PLM it might be pretty safe to purchase one now. Perhaps UDI will be in the position to release their multi national PLM by the end of the year? As I understood the current issue it was a combination of waiting to see if the next batch of firmware would resolve the ALL ON / ALL OFF issues. Also receiving the OK from Smartlabs they would be allowed to have the tools to reflash any PLM chip moving forward. I believe the second requirement may be the sticking point here . . .

Just to be clear the LED hasn't been turned off or dimmed right? Also the correct jumper is still in place (factory inserted) so it can by default use a controller such as the ISY to execute the options. If all of the above is true and the device is under the 2 year warranty period I would send it back via RMA.

I would do the following in case it was over looked. 1. Replace the battery. 2. Verify settings are correct for sensitivity, dusk 2 dawn, nigh mode only, etc. 3. You can after steps 1 & 2 hard reset the device and select restore device and see if it operates as expected.

Yes . . . It should be noted this was reversed in some hardware / years of production. The most famous was the cryptic values stuck on with some $0.00000000000001 label maker!

I don't recall if this question or problem has ever been posed by a member so here goes. I have a program that tracks the current, low, high values. Whether it be energy, voltage, humidity, temperature, etc. The system currently sends me a e-mail from 1 to 3 times a day depending on what the application is being monitored etc. I would like to know is there a method where I can have a time stamp with the last change with the above fields? Examples Below: Current: 20'C 12:00 PM 18/08/2015 Low: 15'C 5:42 PM 05/12/2014 HIGH: 35'C 3:48 PM 22/07/2015 As you see in the fictitious example above which I have high lighted in different colors. Is there a method where these time stamps can exist until such time as these values change? From that point forward those dates and times would obviously change to reflect the current, low, high values?? These time stamps should exist even after a firmware update / system reboot. Make sense, clear as mud???

Yes, you can . . . Could you explain how you're going to disable door sensor? Do you mean disable the ISY Program?

This doesn't really answer your question you posed but some installs where wiring was not possible. I used a double switch plate changed the old toggle switch to a standard decora. Added in a micro relay / dimmer at the light fixture then on the spare plate hole used a 8 button remote link. This *appearance* wise gave the look of two decora switches and also allowed control of extra Insteon enabled loads. The only down side was no real time status etc. But it was a good compromise of wiring and having the same control etc.

This is a very comprehensive program that monitors all aspects of the Leak Sensor but you can modify it to use for the door sensor. http://forum.universal-devices.com/topic/11566-leak-sensors-a-suggested-complete-program-package/?hl=%2Bleak+%2Bsensor

Manual? What manual?? Who reads the manual, we are men, you don't need no stinkin manual! Ha . . .

To add more clarification to what LeeG has posted. In my humble opinion if you have a small Insteon network of less than five devices and very few programs / scenes. Its really not the end of the world as its just a small amount of time. If on the other hand you have extensive programs, scenes, and Insteon network. The small amount of time will seem like years when you have to recreate all the links, scenes, and associate all the programs to the missing devices etc. But, if the above is not germain to your current situation by all means follow through . . .

If you purchased both (new) units together its highly likely the hardware / firmware is the same. I only ask because over the years many battery operated devices have had minor firmware changes to how it behaves. Many of us have also noted firmware levels showing the exactly the same but operate completely different. The most frustrating aspect of this is often times these changes are introduced mid production. Meaning something will have v.43, and another person will have the exact same v.43 but it will operate and behave completely differently. This has been seen in the Open-Close, Leak Sensor, and Door Sensors.

Further to what LeeG has asked I assume you're using Belias's program to monitor the heart beat status?

Motion Sensors have never had a heart beat.

That was the confirmation I was looking for actually. Are the sensors you have in place all made in the same production year and have the same ISY firmware as listed? I ask because Smartlabs has been well known to change behavior with out informing the general public and their 3rd party vendors.

Alan, I agree the stated RF range of Insteon devices rarely meet the published specs listed by Smartlabs. But you should note that the range you see listed is direct line of sight free air. Any material in the way of the device will either absorb, or reflect the signal. Best practice is to place any dual band plugin devices at the four corners of the house. Whether that be basement, main, and upstairs (assuming you have a second floor). This insures RF coupling to any battery operated devices which require it. I've done more than 300+ Insteon installs and following this basic premise insures consistent RF signalling. When finances do not allow such hardware deployment a plugin dual band device is placed as close to a central point in the home. This is a compromise but does bolster the RF signal to power line communications. Keep in mind no amount of coupling / bridging by a dual band device will circumvent signal suckers / noise makers in the home. Most common are older 915 mhz portable phones, baby monitors, camera's, etc. Any computer related devices, UPS, cell chargers, need to be placed on a Insteon Filter Linc. Lastly, I can assure you Z-Wave is not the silver bullet when compared to Insteon. Depending upon which generation and device, brand, model, you will still require bridging repeaters to allow proper signalling. The Gen 5 Z-Wave devices have started to roll out and they advertise extended RF range, programming speed, and security. Even with this they require lots of repeaters to complete their mesh network.

You can not query a battery operated device. When you see a status of On/Off this is because the battery operated device sent a signal indicating its last state. When you do a firmware update or reboot the ISY that state will either be lost or show the last known state. This is expected behavior of the system and is not a fault. You do not need to relink any battery operated devices at all . . .