Toddimus

I bought my first ISY994 almost 14 years ago. Had a few Insteon modems die along the way (not UDI's fault), assumed it was just the cost of playing the geeky game. Somewhere along the line, I think I must have had an ISY994 die along the way because I have an extra. Can't really remember what happened there. Now I have a Polisy Pro that initially just ran Polyglot integrations which have since been deprecated (more on that later). About a year ago, I finally migrated my totally functional ISY994 system/programs/Z-wave network over to the Polisy. It was supposed to be the bee's knees. By the time I ended up migrating, there was a new and improved, bee's knees called the EISY. I get it, they had to change suppliers for their uber-cheap imported box that can run the Java backend to maintain compatibility. What initially pissed me off was that the recommended Zooz Z-stick was no longer supported on the "latest" version of ISY firmware on the now deprecated Polisy. You can still use it but you can't upgrade to the latest versions of firmware because it's not supported. Instead, you have to buy the MatterZ stick because that's the new thing and you just have to have it, or it won't work unless you stay on old firmware. Fast forward to now... My Polisy updated itself to v5.8.4 (I think) firmware apparently within the last few days/weeks. I didn't do it. Now, it needs rebooting every day. My old Polyglot 2 integrations are dead. I had a LOT of archaic ISY Java admin interface code programmed around those Polyglot integrations. And now, you need a subscription to maintain connectivity to the system from the smart phone. I get it. The company needs to make money and needs to monetize this thing. I totally get it. I'm just not willing to buy an EISY (~$300) and a Zmatter (~$125) to replace the stuff that worked just fine until the ecosystem I had been using is suddenly deprecated. I just did the subscription for the next year for the portal. I'm fine with a subscription. I'd probably pay $50/year if it just worked and I didn't have to deal with it all the time. But, alas it doesn't. I had hoped I didn't need to babysit it. But I do. Why does the Insteon light take so long to react to a motion sensor when the Z-wave reacts immediately? Why do I still occasionally get an all-on event? Why does the Polisy reboot when the living room motion sensors have a bunch of triggers (can't I have a party in my living room)?? I think I'm done with UDI unless there's a clear path to a stable system that I can rely upon for at least a few years. I wish it wasn't this way but I'm at my wit's end. I'll likely be migrating control to either Home Assistant or OpenHAB (both of which I have run in parallel for many years). I just find that I can't rely upon the Polisy and the ISY/Polyglot infrastructure anymore. To be honest, I'm bummed. I'm not one to be a complainer or squeaky wheel. I've tried to make the ISY work. And I have ~50 Insteon devices in my house. I have a ridiculous amount of time building ISY programs. And I made some really cool automation stuff over the years. But I realize this is the state of affairs. I think I have to begin the process of migrating away. It's just not stable anymore. As I said, I'm bummed, or you could even say, disappointed. Please tell me I'm wrong and pull me off the edge because I'd love to just have an update and fix everything. I just don't see it happening. Especially on "old" Polisy hardware with Zooz Zstick.

FWIW, this worked for me as well. Thank you for this!!!!! I get the zwave menu instead of the Zmatter not responding. Now I just need to get the zwave devices added. That's proving to be a chore. I updated to v7.18 firmware on the Zooz, so maybe that's the problem. I'll try reverting to v7.17, which seems to have worked for others.

I use an Autelis Bridge for Pentair Intellitouch connection, but apparently Autelis seems to be AWOL for the last year or so that's not an option. And that's a lot more involved than what you're asking to do. You could possibly use the GPIO pins of a RaspberryPi and to be on the safe side, have those outputs drive 4 small relays. The RPi's GPIO pins are only 3.3V so you get something like this to buffer between it and the Pentair relays: Raspberry Pi relay hat Then, use this Polyglot Node Server, which can probably run on the same Raspberry Pi. https://github.com/exking/udi-gpio-poly I haven't tried the GPIO node server, nor have I tried one of those relay hats but it seems like you could put something together for ~$50.

Yeah, it did work with precision set to 0 or 1. When the precision is set to 0, I think it just drops whatever "mantissa" there is, rather than rounding. So 99.9 would equal 99. EDIT: I stand corrected. See the second set of variables below: Precision set to 0 does seem to do rounding:

Because of the post by @kclenden I had to test it out myself too. One weird thing is that when you manually change a variable on the variables tab, you need to hit enter or it doesn't "stick". Here's programs that works both ways:

@mmb On the variables page where you have your Temp_Current defined, right click on the row and select "Change Precision". I'm pretty sure that's how you change it from "Integer" to a "Floating Point" (even if it's defined on the "Integer" tab! ) You can select from 0 up to 8 digits of precision. I think that should fix your problem.

FWIW... I saw issues with Alexa earlier today too. Seems to work now.

I have the same question/issue with my Velux skylights, which are driven by a pair of Insteon I/O modules. To open them, I have a program that makes one I/O turn "ON" and the other "OFF" (and the opposite polarities for closing). It just so happens that this is the way the Velux "home automation bridge" works. It actually has been a good thing to combat the dreaded Insteon "ALL ON" bug. When that happens, both I/O modules go high (i.e. ON), and that would actually stop any movement that's currently in progress, though I've never had an ALL ON event while the skylights were in transit. I've just gotten used to saying "Alexa, turn the skylights on (or off)". It's weird and non-intuitive for anyone other than me. It would be very cool if it were to be fixed so I could use the words "open" and "close", but in the mean time, I'll keep using "ON" and "OFF".

I've been keeping an eye on this thread. I plan to check it out soon, maybe this week. Been too busy to get deep into loading/testing it out. Thanks for your work on it!!

That valve might be a good tool to use for an automatic pool filling system, if I ever get around to automating my pool.

Both, I think. I honestly didn't look that hard at it. I was getting our toddler to bed and got distracted. Nothing stood out to me though. Definitely weren't a bunch of individual device or scenes turned full on in the log. Sorry I'm not more help. Il try to document it better next time. Sent from my iPhone using Tapatalk

I didn't have any All On events for about 14 months ... from the time I did my initial install in our new house until about a month ago. I just had another one last night. Both times, I was opening a door that has a hidden door sensor in it. There also happens to be a wireless motion sensor on the far side of the door that I was opening. Not sure if the motion sensor would have had enough time to "see" me before the All On actually happened. I think the first time, the hidden door sensor had a low battery. Maybe it tried to send out its low battery signal on top of the regular door open signal it was trying to send? The first time, I wasn't able to get to the log to check. Last night, I looked in the ISY log and didn't see anything that looked suspicious.

This is extremely cool! I recently put some extra blank switch locations around the house in preparation for something like this. I had been thinking of using old iPhones or maybe some sort of small tablet, but a RPi with touch screen would be awesome! In fact, I just received two more RPi 2 boards today that I ordered from Makershed. They are having a big sale. They were already half off ($20) and then there was a 20% off coupon code which made them $16 each! Yes, that's for the latest RPi2. Looks like they are out of stock now though.

Well, that answers that question. You even did the math for me Stu, thanks. So I won't worry about it then. Any thoughts on the new feature for automatically populating the permutations of the adjust scene function I suggested for the interface? I did go through and do it manually with all the permutations and it wasn't that bad but it would be nice to be able to automate some of that process if possible.

Follow up question... I assume these adjust scene actions actually write updates to the internal non-volatile (is it EEPROM?) of the devices. Is there any issue with degradation if I write to these say... 5 times per day? I commented about this in one of the Ideascale items where the originator (Jim Searle) wanted to be able to programmatically enable/disable devices from being responders to scenes. By the way, this is a great idea, if it can be done... http://udi.ideascale.com/a/dtd/Allow-disabling-a-device-in-a-program/83037-32911 This would also theoretically require writes to the devices' non-volatile memory. Any thoughts on the longevity of the non-volatile memory's write endurance? 10 years x 365 days x 5 writes per day is almost 20,000 write actions. Thanks, Todd