lilyoyo1

The tabs are glued on as the battery is designed to be none replaceable.

https://forum.universal-devices.com/topic/33710-solution-for-dimmable-led-light-strips-with-automations/

I still had the old link saved. Just people with hub issues so far. You're not missing anything

I didn't even know it came back.

Not sure why you feel polisy may not support insteon in a few years when UDI's next gen controller (eisy) supports insteon as well. The work for insteon is already done. They'd need to rework the whole system to remove insteon capability. Maybe somewhere down the line but definitely not in the near future to worry about another Isy. Besides, you'd simply be continuing on with an obsolete device

@Geddy- this is posted in the wrong forum. Since the op is using Polisy with the zooz stick, it could cause confusion with it being posted in the Isy zwave 300/500 series section To the op @Prana electric. Leviton uses hail for status. You'll have to use programs to query it and get status. https://forum.universal-devices.com/topic/34097-leviton-zwave-plus-doesnt-report-status/#comment-321618

Not all node servers offers a trial. You could use the PG2 version which is free (though unsupported if you want to temporarily test things before purchase

It would help if you provide us with the devices you're having issues with, your programs, how you set it up, your Isy firmware & UI, etc

Same process as swapping out a PLM. Best practice would be to read the wiki and follow it. Not following would be what not to do. https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu#Replace_Modem_.28PLM.29 Also, make sure you have a recent backup of your system before doing anything

Contact UDI

I'd give them time. It was left a complete and utter mess. It'll take time to get a complete team hired, structured in such a way that makes sense for what they want to do and get things up and running. UDI's needs (and ours by extension) are going to be last on their to do list. The pre-existing sourcing issues will probably play a part as well as they'll want to make sure they can accumulate enough parts for their devices let alone another company. They arent buffoons. They didn't buy insteon out of the goodness of their heart. They bought it to make money. Whatever their business plan is, it's going to include 3rd party or it's not. No point in name calling like that just because it may or may not be the same as your desires. While the waiting sucks, it's something we'll have to do. With Ken being a long time fan of UDI in addition to still taking their phone calls (vs a flat out no), It does give me hope of a better future. While I'm done with insteon as it currently is (old line), it would still take a lot for me to use the new line as well. However, I still hope for it's success, and will be patiently waiting and watching to see how this all plays out

Isy exposes what zwave offers within a device category/command class. It's up to the mfg. whether or not they take advantage of it.

It's the same as all of your other devices. Weakness in the zwave design

If you Google ISY wiki, you'll come across the wiki link which has the full instructions on how to use the isy. Within the wiki, there are links to the isy cookbook and instructional videos. If you're looking for personalized help, there is none that I'm aware of. Someone may be willing to help you like that for a fee. The best thing to do is start small with basic stuff and then build out as you learn more. By reading the many threads on here, you may come across something someone else has done and use their programs to help learn more.

Great minds think alike! ?

Of course it is. Cause no one would ever be tempted to see what it does. ?

Not the tape over switch design. ?. Hopefully he takes the disable approach. ?

Did you follow the notes that the developer left? https://forum.universal-devices.com/topic/28703-introducing-the-rainmachine-irrigation-controller/

That depends on your setup. With just a single PLM, you would need to use network resources and send rest commands to your polisy. The isy994 would need to use the zwave only firmware so that it doesnt lock up without a plm attached. That isnt something I have personally done so I wouldnt be able to help you with the scripting.

Probably not. Id make sure you are on the latest ISY firmware for your ISY which is 5.0.16C.

There is no 700 board for the Isy. The latest board for the Isy is the 500 board. Michel has stated that they will not have a 700 board for it (only polisy). With that said, all communication will be at 500 series. I don't use the app so i can't say what the errors mean. If you've already run a network heal on your problem device, I would recommend clearing your Java cache just to ensure there isn't anything causing any conflicts. Next, bring your problem device closer to the Isy and run a heal. Then test to see if the error goes away. If it does then there's a chance it could be environmental. If it doesn't, trying removing the device from the Isy and re-adding. Something could've potentially gotten corrupted in the process. Repeat the tests. If it continues (especially if it's with the same device while others work) it could be a defective device.

Are you using the isy994 or polisy?

Whats the latest version of everything? We hear that alot and then when further questioned, it turns out the person doesnt have the latest. The best way for us to help you is to provide actual details such as your firmware and UI. Having information on both is important. (Help>about) What do you mean by zwave devices are not marked. Ive used zwave in dozens of installs and every single one has started with ZW 00# (number increases after each device)when a device is added. Ditto for every single person on here using zwave. The only way any of that information is missing is if you overwrite it. If youre having to go back through and put a "Z" in front of all your zwave devices then you erased it during setup. Thats a user issue not a software issue. In regards to looking at the event viewer information- did you open the event viewer before or afterwards and set it to level 3? Ditto for update neighbors. Since locks are usually asleep, you want to wake it up by manually locking/unlocking it when you want to run it. On the surface, it appears you have enough hardwired devices in your home for a decent mesh. However, not knowing the layout of things, environment, etc., I cant really help with whether actual placement is great for a strong mesh. Needing to add your minoston's close to your isy does not surprise me. All of your devices must support network wide inclusion for it to work from its final location. Otherwise, you must bring the devices close to your ISY.

Being that you blocked your programs it's hard to tell. Looks like you have a lot going on though. You can try a wait between each line to see if that helps as well as ensure your UI matches your firmware

Its been coming in and out of stock. Many people have been switching to zwave which may be playing a part in it's stock level. Since it's still showing on their webpage nor has Michel stated it's been discontinued, I'm certain it will be coming back in. You can email UDI directly for more assistance if you require a time frame