oskrypuch

Button labeling with a label maker using transparent film is very easy and effective. Almost indistinguishable from etched buttons, and of course easily modifiable. * Orest

Well, the site description is pretty definitive ...

It will be interesting to see when stock starts appearing, whether there will there be "hording", that is shopping to build your own inventory, or have enough dropped the Insteon flag, and moved on? I have no idea which will prevail, just musing. I am mostly Insteon in a large install, but with a bit of Z-Wave, which I added when SmartHome imploded. Personally, don't think I'd change the ratio that much, but it is nice to be able to add unique Z-Wave products, impressed with them so far. * Orest

Looks like insteon.com ships to US ONLY. But, I just noticed that aartech.ca is listing Insteon products again, and even has some in stock, although those are likely holdovers from old inventory I think, for now. * Orest

For most ISY programming, I just sit down and do it, as the inputs and outputs for many things are pretty trivial. But, that said, even some code that controls several lights based on motion, time of day, and perhaps some other factors, may be difficult to juggle clearly in your head. Some time ago I programmed control of the many zones in the house using a rigorous machine state approach, integrating prioritization, outside weather, time of day, season, location, manual requests for increased heat/cool, etc. And yes, you start on paper (virtual or otherwise), but then the implementation is dog simple, robust and understandable years later -- when you need to inevitably come back and make changes. * Orest

It may be there somewhere, but I haven't seen it. What is the procedure for someone with a Polisy + 700 USB dongle, to upgrade to using the new internal board -- and I mean after you do the physical install. Does it just recognize the new board, and start working? Do you have to switch some set up setings? Do you have to do a backup/restore, what? My interest is academic at the moment, being outside the US, won't see a board for a while. * Orest

Will the USB version be in any way speed bumped (USB vs PCI-e), IOW should you go with the internal board in preference? Also, will that board be ONLY available through UD directly (in which case I am out of luck), or will it be offered to distributors as well? (kind of critical for me) * Orest

I just bought one two months ago, still in the box. It was meant to be a spare for my current operational Polisy. * Orest

Oh dear!! So we may be out of luck for any of the upgrade options. Guess, will have to wait until/if the Cdn distributors pick it up. Of course UD shipping to Canada was almost prohibitively expensive before anyway, compared to other suppliers. Not sure why. * Orest

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

I thought I read that @Michel Kohanim said to expect some NEWS on a PLM alternative "next week", was it a couple of weeks ago now? Did I miss that post somehow, or is it still in process? * 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')