oskrypuch

Thanks for the report, and for all your work. * Orest

Any headway on this one? * Orest

So, updated ... Audacity (free, open source) does the job nicely for recording the custom WAV files 8Khz sampling (contrary to the leaflet in the box!) mono, 16bit PCM Format 2GB card as default FAT (FAT16) WAV files must start with a two digit number, so requires a leading zero for <=9 (eg. "01 my alert.wav") add additional (>30) WAV files sequentially, 31, 32, 33 etc. substitute WAV files (<=30) can be one or many file name may require a following space after the number if the additional WAV files are not visible in the admin panel to select, then query the device you may need to power-off/power-on the Ecolink, or remove/insert the SD card more than once, to get the WAV files to be initially recognized

Three other observations. The extra WAV files have to be sequencial, so you need 31 xyz.wav, then 32 abc.wav, etc., else the ISY picks up the number of files, but doesn't refer to them by name but rather by index. Weird. So if you have ... 31 32 35 36 37 ... and you ask to play 36, you won't find it. You will find 31, 32, 33, 34 and 35 in the list box. AND, if you ask it to play #35, you will instead get #37 ! Further, I had to QUERY the device, to get the extra files referenced and available. Lastly, The other thing I notice, is pulling the power on the Ecolink, does not kill it, it has some sort of power backup, perhaps a large Cap to carry it through power outages. So, if you really want to power cycle it, it might have to stay unplugged for a while. * Orest

Well, for good measure reformatted the card to FAT (16). No difference, with one exception. The unit still sometimes will not recognize the WAV files. I just pop the SD card out, and push it back in. Often the light will flash on the Ecolink. Eventually the WAV files are found. And, looks like the admin panel has finally picked up the "new" WAV files, starting at 31 and above. Not sure if it was my fiddling with the card in the Ecolink, or it just needed a restart or two, but I can access tones over 30 now. So, what I have now is working for me, even if it is a bit fiddly in application, kind of a "jiggle the cords" kind of thing. I will probably hesitate to make any changes now, in case that throws it off again. 😉 * Orest

Ah, missed the FAT16. That perhaps explains the trouble I'm having. Thanks! * Orest

As to custom sounds (31 and greater), when you added them, the programming popup in the ISY Admin interface recognized it? Did you have to power cycle, or restart the Admin, or Query the device, or anything? * Orest

@Techman I have power cycled it a few times. My one issue was not having a two digit number for the 1 to 9 sounds, but no idea why I can't get the custom sounds to get recognized. In one instance, after adding another WAV file, it went back to the default sounds. I tried power cycling, didn't matter. I then pulled the card, deleted all the files on it, and recopied ALL of the WAV files back. Then it worked again. Odd. Maybe I will try adding a custom numbered sound, but first delete all the files on the card, and re-add all of them together, including the new custom numbered sound. Could be something funky with the SD card as well. * Orest

[list expanded/corrected downthread] OK, that was the secret sauce. 8Khz sampling (contrary to the docs!) 16bit PCM WAV file must start with a two digit number, so requires a leading zero for <=9 may require a following space can only substitute for the default 30 sounds, as far as I can figure. * Orest

Tried something else, renamed the file to start with a leading zero ... 01 my tone.wav That CHANGED what was being played (replacing the default), but the tone (sampling rate) was way off. I'm getting closer, but not there yet. But, looks like we can only replace the default sounds with the current ISY set up. * Orest

@TechmanI am trying to get this set up, without luck. I added wave files to a 2Gb card, started it with a number of 31 or higher. Inserted the card, the light flickers on the Ecolink. But I have no way of running that sound from the ISY admin, the numbers appear hard coded to only go to 30. So, I renamed the file as 1xxxxx.wav, still no go, then just 1.wav, doesn't replace/play when I try sound #1. And, now I notice that you say 8KHz? The doc that comes with it says 16KHz?? It is 16 bit PCM. (using Audacity). I'll try 8KHz. * Orest

A lot of "brands" I don't recognize. I did find a Sandisk finally in micro format, but wouldn't be surprised if it was a knockoff. Well, at least it is not a critical application. * Orest

Tricky finding a 2Gb SD card these days, just looking to do this now. A lot of them are 8Gb reformatted to smaller capacity (but branded as 2Gb), and may not be addressable by the Ecolink unit. * Orest

But, ISY has no way of interrogating the X10 device, to see what address it has. So, the only way to control it, is by sending X10 commands. It may be that you can link an X10 address for a device, so you can address it by name as well in ISY -- but clearly you are still responsible for manually inputting that info. And if you change the X10 address on the device, you'd have to manually change it in ISY again. * Orest

I don't think that you actually add an X10 device, like you would an Insteon or ZWave device. You just use the X10 codes in your program, that correspond to the device, and they get there. That is what I recall doing in some ancient code I had for an X-10 ding-donger. Perhaps you can, but I never did. The below worked. * Orest dingdong - [ID 0007][Parent 0041][Not Enabled] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Send X10 'P9/On (3)' Else - No Actions - (To add one, press 'Action')

Thanks. And it is in stock locally! Grabbed it. * Orest

I actually HAD a real bug in my monitor. And, it had to be my big 34" curved 21:9 unit! It was crawling around between the plates. Disgusting. I just turned off the power, and turned off the lights in the room, and left the lights on in an adjacent room. The next day, it was gone! Thank goodness. Never seen that one before, but googling around, seems it isn't too uncommon. * Orest

In the outside location, I'd be running the AC to it. But I guess that still would not change it from a "battery operated" device. But, yes, end of a ZWave leg, so ... * Orest

So the Aeotec Multisensor 7 does a lot more than just motion. I don't need the extra, but it appears sold out anyway. The Zooz ZSE18 & ZSE29 show as available, but both are series 500 devices. I am more looking for an outside model, the ZSE29. It would be at the "end of the line" in the mesh, but I just don't want to mess up the rest of the system which is all 700. I'm a newbie at Z-Wave, and not sure if this one 500 unit would force a downgrade of the rest of the units so they could run on the same mesh, or whether it is just the need to pass through a unit that causes this issue. Did read through the tips & tricks, but it wasn't that explicit. I have run out of Insteon motions, virtually all of my system remains Insteon, but have been looking at ZWave since the recent events. So far, I am impressed with ZWave. I did take the time to arrange the six or seven modules appropriately, and have a booster. Thoughts anyone? * Orest

Don't use HA, and don't have a Pi. But, could install HA into a VM. Wonder if that would allow for the updates. * Orest

So, it looks like this issue has been addressed by zooz, with the addition of three more settings. Same configs are present now in Zen72 as well. Of course doing a firmware update involves a lot of fiddly legwork at the moment. I'll just continue using ZWave ON/OFF with an explicit value and ramp rate for now, in Polisy, hoping that the new UD zwave boards (this Fall) allow for direct firmware updates. * Orest

I gave up on this, and just use a full rate and final value definition for any ON & OFF commands with the Zooz switches. If there is a way to set the default ramp and ON value (when not using a physical touch), I'd love to know how. * Orest

That was it! Thanks. * Orest

I thought I had managed to run the AC through the portal, at a remote location, off my home LAN. In the past I used to open up ports, but prefer not to do that. I can open the Device/Program list using Select Tool | ISY Web access, but that is not what I'm looking for. * Orest

5.3.4 is the latest for the 994, no harm is a quick update. But, any version from 5.0.16 and up, can migrate to IoP. I believe there can be some issues with some Polyglot nodes if moving from older versions of ISY on the 994. I didn't have any, so moved right from 5.0.16. * Orest