ELA

I looked up the number of your device and it is a triggerlinc ( the old name) which they appear to have changed the name. I was thinking you might have been talking about the hidden door sensor. There is some problem with your device or setup that you should investigate. Do you have a program that lets you know if you ever miss a heartbeat ( I had said watchdog, which is another name for heartbeat). You say the sensor is never activated? Did you test activating it to see if you receive the activation's? Check it in the level 3 viewer to see how reliable it is. Do you have a program that runs when the switch is activated? Is there any chance the device is activating too often and you did not know it? It is in a waterproof box ( plastic?) and also waterproofed??. (Can you explain in more detail)? What activates the device? Do you have wires to a remote sw. connected to the device? Something appears to be going wrong with your setup or the device itself. I have 3 of these devices and the batteries last a very long time. Always greater than 1-2 years. They last so long I have not tracked when I replaced the batteries ( but I do with 9V MS sensors since they get changed at a 1-2 yr max interval).

You need to solve why the batteries are draining so fast. Do you have a program monitoring the watchdog? Are they ever not received? What is your communications reliability with that device?

Here is the current demand for a triggerlinc. I would expect it to be similar for the door open/close. As was pointed out you will not have good luck with a 1.2V cell. As I decreased the voltage to the device that can cause it to go into a state where it stays awake for 11 seconds ( while failing to communicate). That will drain the battery much faster.

How many dual band devices do you have? Any other RF-only devices like triggerlincs and do they work? A stuck transmitter on any RF equipped device can screw up a large portion of the RF portion of the network. I know this because I located an On/Off module with a stuck transmitter using an RF signal strength monitor. Resetting that stuck device fixed the issue. Symptoms previous were similar lack of RF-only device operation. Just one other possibility. I was spoiled having a monitor, much more difficult to troubleshoot without.

Dont forget the fan to cool that 10Watt Resistor :) Maybe a 4W nightlight might be a better choice.

Larry, I spent a lot of time on this a long time ago and forget most of the details. Here is a link about that effort; With Lee Gs help I was eventually able to make special scenes that did work but it was a lot of work and not very maintainable. I had created a request for the ISY to support the EZIO8SA using direct commands to support all 256 combinations but it never was implemented as best I know. Maybe some one from UDI can update us?

256 will not work with the EZIO8. The ISY does not support the scenes required to do combinations for the EZIO8. You can do 8 outputs though.

How many dim levels are acceptable? If 8 were enough: EZIO8 & 8 different resistor values.

I too was short changed on that sale..... and I was so looking forward to: "no pass-through outlet" and "much lighter weight"? I would have thought that adding 1000 links would add weight :)

EEproms have historically been known to get corrupted by fast transients or a high rate of change of the voltage applied with respect to time. If a power supply/capacitor becomes intermittently defective, power supply transients could become more prevalent.

I had used ... "If control <device> is switched on" instead of If status. Yet the program triggered every 30seconds. Found that the sensor itself sent Wet commands every 30 seconds or so once activated. Used a variable to get around this. This is a reason not to leave the sensor in the wet state for too long (hrs/days) before resetting it as it will reduce your battery life.

Hello BM, You issue sounded familiar so I checked my notes. They said that if the bit rate was less than 44100 it would not play. Been a while though. Might try looking at that?

Back door / Front door ?

A long while ago I did experiments with my EZIOSA8 in attempts to make custom scenes that could control multiple relay outputs at the same time (w/Thanks to Lee G. and his guidance.). This required creating custom scenes using the SHN utility. As part of that effort I had recorded that the EZIOSA8 ( which has a larger EEprom than the standard PLM) was storing its links at Address 3FFF. The standard PLM stores links at 1FFF. ( at least as best I can recall)

simonsez, Just as Brian has detailed unused inputs need to be terminated ( pulled up or down). I believe your captures indicate that Inp4 (the "C") in the address is noisy.

Hi Teken, Are the problem announcements triggered by RF only devices by any chance? I had one that started to play for 1 sec, stopped and then started the same announcement again due to dupicate RF only device sends. Had to add a delay there.

Brian, I agree and it is the reason that I said only three signal lines should be used. Capacitive coupling occurs between wires inside of the cable. This is often referred to as crosstalk. The longer the cable the worse the crosstalk. Why you do not want anything but a common in the same twisted pair with an Tx or Rx signal. The TTL level signals should not be included in any longer length cables.

Hello Apostolakisl, Since you want to stick with extending the RS232 you might have better results by making your Cat 5 or 6 cable in a more custom fashion. Those cables are really intended for ethernet type differential communications. Rs232 is single ended and to take better advantage of the twisted pairs I would recommend only connecting the three lines needed 1,7,8 as Brian detailed. Use two wire pairs and put tx and gnd on one pair and rx and ground on the other pair. This would of course require a pigtail from pin 7 to the two gnds (commons). here is a link that talks about extending RS232 : http://www.marcspages.co.uk/tech/long232.htm

A follow up note: for anyone who might use a Rpi3 with built-in Wifi on a project such as this: The wireless turns off (by default) every so often as part of Power Management in Openelec 6.0.3 ( Iinux kernal 4.1.18) and that was somewhat frustrating. Resulted in miss-fires of network resources from ISY to RPi. Ping times were excessive - even before timeouts occurred. Upgrading to Openelec 7.0.1 (Linux kernal 4.4.41) appears to have corrected this.

Nice write up Teken, Very kind of you to save others the pain you must have had went through Damn those under_scores! I had added them as a test at the ISY NR end but forgot to change the file name in the music folder also.

Hello Teken, May I ask you to elaborate on what fixed your issue where NR was not working from ISY ... If it was something other than remote settings in Kodi? I have just purchased the network module and this is the first use of same. In Kodi I have all the remote controls turned on. I can send from a web browser and Kodi responds and plays the wav file fine. Yet the ISY "test" for the NR responds just as you have posed here. It seems the NR command syntax is correct but for some reason the ISY is not sending the command out the HTTP. I have turned off the firewall and virus detection temporarily to see if they were holding it up but no luck. Since I have never used the NR module before I am wondering if there is some setup I may have missed.

Well that was sure much easier, thanks. I had enabled Samba as detailed but had no idea why. I googled it after you suggested it and all is well now.

To those with this system working. Thank you for the details already posted. I have most everything figured out but I am stuck on something that seems as though it should be easy - yet I have struggled long enough and want to ask for your guidance. How do you get wav files into the music folder root? I have read about scanning them in using scan item to library. I tried that and it puts the file into an album rather than into the root of the music directory. I have read about needing tags in order for a wav file to be scanned in? I tried adding a tag with Mp3tag. I can see the tag is added yet I cannot scan the wav file into the music directory root. With the wav file loaded on a usb flash stick I can navigate to it from within Kodi and play the wav file fine from the usb stick. I can then scan it to the library and see it in an album. I can also play it using the keyboard/mouse from the album. Just cannot figure out how to get it into the music folder root so that the NR command example provided can then play it. (e.g. "storage/music/my.wav" Any help much appreciated. Ela

madcodger, please do read the datasheet for the filter that was recommended. It recommends other choices as a first choice.

How do you know Stew....? I had thought it was a band stop filter? Maximum impedance at about 120khz or so. Drops off and impedance goes down on either side of that. Can be easily altered by removing one capacitor to increase the impedance 6 fold at 120-130Khz if desiring to use as a circuit isolator (suck reduction) rather than a noise attenuator.