Kevin Connolly

I didn't read all 5 pages of posts, so excuse the reask if the answer is already out there. To summarize what I've read: Smarthome is/has discontinued the 2413S PLM except for possibly some warranty replacements...and they are showing currently out of stock. That being the case can someone summarize what the current and future workarounds are?...(Michel?) Posts sometimes get off topic and the proposed/suggested solutions get lost in the mix. I'm one of those guys that needs your basic "buy this and plug it in here" instructions....even if it's a software interface to Raspberry Pi to Outlet connector I can deal with that. What makes me a tad nervous about this situation is having an entire home installation contingent on a single device that's discontinued without a backup plan. I don't know about you guys but I'm married and even the thought of my entire house being offline due to a part I can't get isn't a good one.

Yeah, it's definitely a 300 board than. and yup it's the stock SD card. I once had a raspberry pi run 24/7 for 8 yrs. I just replaced it last year. I now have 3 Pis on two bitscope blades running in a case I designed and my son-in-law printed for me. I run a Polyglot, DNS, VPN, and a NAS. because I have a VPN I have a secondary NAS back up at my son-in-laws house. I've found that once you get your system up and running to where you want it the best course of action is to never upgrade the software. Don't even think about it. Just let it run (I know...I broke that rule. Ha) Since the recent issue with having to rebuild the Polyglot I now also have images of all my installs. In the event of an SD card or board failure I can be back up within minutes assuming I have the hardware in hand. Once I get the ISY back up I'm going to create an image of that SD Card as well.

It's definitely a 300 board or less....if there is a less. I remember I ordered it when it came out as an expansion board. thanks for locating the release file. I wasn't paying attention when I upgraded. I don't upgrade often. I try not to fix things that aren't broken. I rebuilt my Polyglot server because the SD card got toasted. Raspbian sets the swappiness to 60 which wears an SD card out after a year or so with all the writes. So after rebuilding the Polyglot I ended up with ghost nodes even after deleting on the ISY. While playing around chasing ghosts and the reasons for them I noticed that 5.3.4 was out and decided, since I'm in rebuilding mode, to upgrade....bad move on my part. My father used to say: If you're going to be stupid you're going to get hurt. I was being stupid. Ha Thanks for the help.

I'm not sure what Zwave version I was running. I do know that my zwave board is older than 2018 though. So by deduction it looks like 5.0.16C might be the way to go than upgrade to latest in the new ISY. For the old ISY, I'll try a factory reset with a new SD card and see what happens. From what you've said, when I applied 5.3.4 my ISY probably had a WTF moment. Ha

I did some checking, not exhaustive but a few pages in. I don't see where "older" versions are kept.

From checking the portal I was on 5.0.14. Checking to see where prior versions are stored since the rest of the known world is on 5.3-ish

Well I haven't gotten the new ISY yet. That said, I was assuming that the backup I have is the data side of life associated with a minimal level of firmware. (ie if there was a new enhancement I had on the isy that I made the backup from there'll be an issue if I tried to load that up on a lower level firmware.) Figuring most software is backwards compatible (except in the case of platform migration) I was planning on first bringing the new isy up to the latest firmware than applying the backup to that. Correct procedure? As for the Portal thanks for the heads up.

I'm assuming that I can bring up a new ISY utilizing a back up from the old ISY. Is there also a way to migrate my portal to the new ISY easily? The portal looks like it's based on UUID.

I'm not interested in what the data is but just that it's occuring. I figure the device doesn't do anything until there's an action. At least that's what I'm thinking

Personally, I should have done more research before getting the Skybell, but now I have it so I might as well try and work with it. "When you have lemons make lemonade". Without the API though I thought the packet sniffer might be a good option since it's going to send something to the mothership whenever there's a button press or motion anyway. I just wanted to throw it out there to see if there's a more elegant way of doing it. I also know personally about the camera addiction. Ha

I'm throwing this out to the community for feedback. I have a Skybell HD. Skybell has only released it's API to select partners. I'd like to know when motion is detected in order to turn a light on. I can get a Raspberry PI and I can try something that sniffs for packets sent by the Skybell. I think that approach, which wouldn't require their API and would be tons faster than IFTTT, might solve my issue. So, for the group: What are your thoughts on the approach? ...and Once I have the data in the PI how do I get it to my ISY as a simple True/False?

Will do! And thanks.

Nice! Took a bit to get it running, but now everything is good. What other generic poly tidbits are out there?

Say what? Ha. I have a Pi with Polyglot on it. Now, from there, what do I do?

I’m trying to set up a bracket of time for a program that’s not year dependent. To be specific from 12/1 of one year to 1/12 of the next. Any ideas?

Nevermind. Got it to work.

Can someone please define what all the options do for the motion sensor II. It’s not exactly intuitive. Basically I’d like to adjust the on to off timing. But I’m curious about the other options as well.

I've tried Polyglot cloud with my Nest stats. I think Polyglot cloud HUGE potential. Looking forward to more stuff

It’d be Uber helpful. At minimum, I could turn on security cameras not otherwise on, and record events.

Alexa Guard is supposed to send you an alert when it hears something like breaking glass or an alarm. Is there any intention to integrate that alert into the isy?

I realize that I'm replying late to this thread, but I spoke to FirstAlert with regard to this issue. FA told me that all items are broadcast to all connected FA devices...including low battery. That said, in theory, the SB should than also receive these broadcasts.

I'm having the same issue(s). None of my tv channels work anymore. The think that really sucks is that I had everything working perfectly until they changed whatever it is they changed. What ever happened to: Don't fix it if it's not broken. .?

I think I solved the case. Thanks Michel for confirming your end. I called Echo support. It looks like Amazon has claimed the word "the". I had all my device commands start with the word "the" and it seemed to work flawlessly up until yesterday/today. I took the word "the" out of my commands and everything is working again.

Now my devices are hit or miss through the Echo?

Well than I'm not sure what's wrong than. I rebooted my isy. I deleted and rediscovered devices. I see all my devices in the Alexa app. But none of my commands work. Alexa just says she can't find the device.