oskrypuch

@MJsanA lot of information in the Polisy & IoP and 700 section. I made a couple of posts, I just recently moved 994 -> Polisy/IoP and added in some ZWave. It all works well. Making the move all at once, actually makes it a lot easier. * Orest

Was the issue reception, from inside of the box? If so, I guess you could put it on the outside top, perhaps a bit "ugly". Which window sensor did you end up using, the ZSE41? * Orest

Thinking of getting one, to monitor the activity at a mailbox with a vertical swinging door. https://www.getzooz.com/zooz-zse43-tilt-shock-xs-sensor/ Looks to be right up to date, 700 series and all. There was this cautionary note at the supplier ... ------ Beta release: you may need to update the firmware in the near future to get full functionality of your device; the device may not be fully compatible with your hub at the time of this release. ------ Anyone got and installed one of these, to work with the Polisy/700 dongle? * Orest

Really? Interesting. But, from your link .. * Orest

So, it now works with .18, and .17, or only .18? * Orest

Setting time backwards may cause PG3 to stop updating until the next day (or it's restarted). ... from the notes on PG3. Does that include the time set back that occurs in the Fall with the move to standard time from summer daylight saving time? * Orest

Well, that was simple. GFCI is the issue. Now, I knew that a GFCI module would stop power line X-10 & Insteon signals, I had just forgotten that the outlet in question was on a GFCI circuit. When I put the unit back in its old outlet and it worked fine there, the mystery started to unravel. Problem solved, the X-10 chime will continue ding-donging. * Orest

OK, so it should work. Certainly the statements are still there in the AC. Will continue to investigate. It may well be that the hardware has finally failed, although it does ding-dong when you first plug it in. Thanks. * Orest

Do I remember correctly, that X-10 support has been removed from IoP? I still have an ancient X-10 ding-donger, which no longer works on IoP. I replaced its function with a cool Ecolink chime/alarm, but wanted to use this guy as an ancillary patio/outside alert. * Orest

A failing SD card would be my first thought, but you've already replaced your card once. Very uncommon, but you might be having a 994 hardware failure. OK, one long shot, do you have any ports open externally at your router, in particular any that allow UDP packets? ISY 994 network operations can be hung by flooding with junk UDP packets coming in through any open port. I got hit with that once, although it was a slightly different issue. Otherwise (or IAC), you should open up a ticket with UD. They respond quickly. * Orest

Unlike with INSTEON devices you need to set config parameters. The AC won't do the work for you like with a 2477D. And even then from what I can see, you still need to set ramp up targets with the Zooz switches in the ISY command. * Orest

OK, went into the OW node, and clicked Load Profile. There was no alert or announcement, and the button stayed pushed, BUT on refresh of the AC I now see what you have depicted. So fixed. Thanks. * Orest

OK, so Node server Online shows 1 now. However, doing an IF statement in ISY, only allows for % on that field, namely 0%, 1% & 2%. Ignoring that it is %, and just testing against 1% (or 0%), doesn't test as TRUE/FALSE. Now, that might be an ISY thing, but this isn't working yet. * Orest

I'm running 5.4.4 and the latest .62 PG3. (just updated) I'm still seeing blank "Node server Online" for OW & WB. What else do I need to do, or is this just something that is still coming down the pike? My (Tempest) WeatherFlow node properly shows True for Node server Online Many thanks for your work on providing these. * Orest

@roberthleeiiThis all came as a nice surprise for all of us, out of the blue, in this thread. * Orest

NO, it won't work. You need the RJ45/DB9 cable. * Orest

SSHed in, all updated, including turning on TPM. No need to guess at the time intervals, it took quite a while for process so nice to have the TERM listing it out. Accessing Polyglot required restarting it, and trying to log in twice, otherwise routine. Enabling TPM took a minute or so to complete. Password tucked away safely. * Orest

Try using the same url directly, in any old browser, instead of using the click of the launcher. * Orest

So, is there even such a thing as Z-Wave associations "scenes", as in Insteon scenes, that are supported in most Z-Wave devices? And, if there is, is it mainly just the popcorn kind of thing response? * Orest

That seems to generally be the case, with anything Z-Wave. Or perhaps it is just me, learning a new modality. [thread drift] I spent quite a bit of time trying to figure out how to set a default max illumination and ramp rate on a Zen72. Finally realized I couldn't use the admin page (like for Insteon), but had to use configuration commands. Even then, I'm not able to set a high illumination setting (below 100%) and an up ramp rate, need to use explicit commands in ISY. I can set a default down ramp rate, because it just goes to 0, so no need to set a level. I'm going to have another look at that, and fiddle a bit more, just wanted to get that one switch in as one 2476 had failed. * Orest

Whoops, saw this only just now ... - If you are a geek, ssh and: sudo pkg update && sudo pkg upgrade && sudo service isy restart

Well, I can still hear the beeps, and the unit is in my study. But, it would be nice if we could just SSH in, and have a terminal session that triggers this, and continues to provide updates. * Orest

@TechmanDid you have to do anything special in the formatting of the .WAV clips? Did you get around the 2GB SD card limitation? * Orest

Aeotec has a somewhat similar device, but it is focused on being a doorbell, has a remote button. Also, it is only 500 series. It is portable (not important for me) and uses a wall wart (less desirable for me). It has preloaded sounds, but does not allow for custom audio clips, and not sure if you can play them without actually using the doorbell. https://aeotec.freshdesk.com/support/solutions/articles/6000202226-doorbell-6-user-guide- IAC, the Aeotec was not a good fit for me. So I went for the Ecolink. Didn't know anything about the company support issues at the time. Hopefully it just keeps on working -- like my old X10 Ding-Donger! Quite pleased with it so far. * Orest

Now that I have access to so many sounds (instead of just the X10 ding-dong), I am finding that sound commands can collide reaching the unit. For example the outside motion sound, and the garage opening sound, commonly do so. So I modified all of my chime programs to wait for any other chime programs that are running to finish, so they only go one at a time. The logic construct is the same for each, below is one example chime program. This one goes chime, chime, "Garage", twice, and is executed when a garage door opens. ding garagex2 - [ID 001E][Parent 0005] If $ding_busy <= 0 Then $ding_busy = 30 Repeat 2 times Set 'inside / ZW 014 Sound Switch' Volume 100% Set 'inside / ZW 014 Sound Switch' On with Tone 12 Wait 3 seconds Set 'inside / ZW 014 Sound Switch' On with Tone 24 Wait 3 seconds Repeat 1 times $ding_busy = 0 Else Wait 1 second $ding_busy -= 1 Run Program 'ding garagex2' (If) $ding_busy is a semaphore/counter that allows a chime program to have exclusive control, but only for a maximum of 30 seconds. (prevents an infinite wait loop in all cases) Each chime program checks for the counter to be 0, and if it is, then takes control of access to the sound device by setting the counter to 30. If a chime program finds the counter not 0, it executes its ELSE clause, and decrements the counter each second. Typically it will be handed control before the 30 sec timeout when some other chime program releases/sets the counter to 0. But in any case, it will be able to take control of the device in no more than 30 seconds. I use <= 0, in case the counter got decremented to -1 or less. The Repeat 1 times statement allows me to add a wait statement at the end of the THEN clause, this is executed after the prior Repeat 2 times loop, and is executed only once. Tidy, and simple. I could add another semaphore to handle a third simultaneous chime request gracefully, but that is very unlikely to happen. * Orest