paulbates

I messaged yosmart and got this reply: Hub 3 has not been released yet but the main improvements in Hub 3 include: 1. It contains a SIM card inside, with an optional data plan available, allowing customers to use it without an internet connection. 2. It is equipped with backup batteries that can operate without power for a couple of hours. 3. It has an Ethernet port but does not include a speaker function. The ET port would be nice but the other features won't make a difference for me, and the speaker will. I'll go ahead with a hub 2.

I'm vaguely familiar with weigand. I'm assuming there are dry contacts on the weigand controller? The Insteon io module (2450) can be an easy choice as an Insteon network / PLM already exists... add it to eisy, connect its contacts to the appropriate weigand terminals and update your programs to check the garage or buzz people in. Like any technical solution, there are limitations.. for the 2450 its it's power-line only, so if the entry doors are far away in terms of wire feet, signal could be a problem, potentially solved by plugging a dual band device near by. Also having signal linc, or equivalent parts, installed on the panel to bridge the power leg greatly enhances Insteon power-line only devices' performance. Also, the 2450 package take a lot of space around an outlet and only controls one in and one out set of contacts. If your building wiring has all of the contact management concentrated in one location, sometimes additional electrical work is needed to add gangs for outlets, there needs to be 1 gang of space between each plugged in io module. If its not concentrated this isn't a problem I just installed 2 iolincs and a sensor on one of the hots.. I had to replace a single gang box on a cement wall with a 4 gang box to make room. Another possibility is YoSmart Yolink products. You buy a hub from them, which integrated with eisy via plugin. They have dry contact support. They also have a number of sensors. I don't have yolink yet but will be installing it soon for the sensor support.

I have yolink projects to do. I was ready to place my first order and saw a Hub 3 coming soon, but their site could not be more vague about what features it will bring. I've gone through the threads on the yolink forum here and there are several mentions of a local api / cloudless version coming of the hub coming. I'm not against having cloud supported HA as I used to be, but would like the advantages of things working and sending notifications when the cloud is down (ISY Portal and Venstar are my points of reference for this type of support) Does anyone on this forum know if Hub 3 will be the Local API capable and cloudless operation, maybe someone is beta testing a 3?

Thank you.. 10' is what I'm going to need for this installation as well

Thanks Techman, and I had your same experience at my last house, outside MS1's, where phantom Insteon "Ons" happened when the battery died.

I'm about to install an MS in my garage. Does anyone know if the small block iPhone charger will power it s. It's 5 watts. The manual is vague about the actual power requirement - 5 volt micro USB I'm going to try it but wondering if anyone has before, since I have a number of these around.. normally "unglowing" led Christmas lights.

It's probably time to open a ticket with UDI. You see the program flip green, and the scene and "run then" work instantly, something else is wrong.

Glad to hear it. I had a couple bumps getting a new eisy and new Insteon PLM going at my new-to-me house.. similar story that the PLM initially appeared to be dead.. but wasn't. And I'm really happy with the news system and the addition of UDM... I do all my new Insteon device adds and scene additions using it

I recently set up a new eisy on a new 2413u and had the same problem. It took several eisy power off / on cycles, including a longer off (~30 secs) for it to work.. and since then its been fine.

It's worth noting that restoring to a new PLM, using Restore PLM, it will take a while. The address of the old PLM is still in every device on your Insteon network, and needs to be replaced.... one a time. If you have battery devices like motion or door sensors, they have to be put in manual linking mode, you have to be ready for that. There's an icon on the admin console that I believe skips battery devices, so you can do all the non battery ones first, and then turn it on afterwards and deal just with battery devices. Its at the very end of the row of icons.

After experimenting with the ecobee occupancy sensors via the plugin, I know they work... and also know that our dog "trips" them. I scrolled through the api and don't see the ecobee app's geofence presented as a data point. I know UDM can do this, but its not practical or necessary to put UDM on my wife's phone; she has & likes the ecobee app. Is it possible to add the ecobee geofence state via the plugin?

It should be possible... Use the "schedule" clauses with AND and the other device conditions. It's hard to be more specific without more info or a sample program you might have started

Here's a more elegant one program version that came up on my drive back home from family Christmas If 'Wireless Tags / Utility Room Sensor' Event State is Detected Movement Then Set 'Basement / Utility Room' On Else Wait 15 minutes Set 'Basement / Utility Room' Off

If the tag turns off before 15 minutes, the program stops running.. is likely the cause. Try putting the actions in a separate program, and change the 'then' of the current program to run the new program. The new program should have no 'if' statement

https://www.theverge.com/23820078/matters-biggest-problem-apple-google-thread-border-router-interoperability This article from this summer gives a detailed description of the state of affairs. UDI is not the bottle neck. They're suffering, like other integrators, from the governing bodies decision to let Apple, Google, Samsung et. al. mutually agree and cooperate on proprietary products & border routers. Going to need to let the dust created from the dust settle😒.

I went back and reviewed the intro thread for system notifications via UDM UDM system notifications work for me and not suggesting removing them from UDM. The question is, is there a way for them to also be provided to the the Notification Plugin? Not a hight priority; but it would be nice to have all notifications in one spot. I can see an "order of events" problem in this request; in that system notifications can't be sent to a plugin that hasn't loaded yet... and which notification plugin to pick when there is more than one iox device.

+1 This is something good to do on your terms, not when the card finally gives up

One more idea.. the common element of the problem is the program - you're sure every thing is good in the program? .. maybe open and resave it

Just to clarify a few things You did "Restore Device" for both, and that ran successfully? A lot gets communicated from the PLM to the devices for that to complete, which suggests the PLM can talk to the devices The eisy PLM is plugged into the same outlet as the ISY? One more thing, easy to try through I'm not sure it works with scenes. I used it at my last house that had problem areas and it helped... adjust the individual device retries: Right click on the device Pick advanced / PLM Communications Bump the Retries up to 2 or 3 and retest

My understanding is you substitute the Group key where you would have used the User Key

My understanding of pushover is that phones are associated with one account. You could put that to the test by going to pushover and trying to add your wife's number to your account to see if that works.... if it does, make a group on pushover with both devices They do offer pushover for teams at a cost which I believe would meet the requirement but seems pricey to me for what it gives for you requirement, Something else to try, a workaround of sorts: Jimbo's plugin defines the User Key and application key for each node.. so you can define similar notifications nodes for each account for the same type notification, and send them back to back in a program.

I believe the program is actually firing when you turn 'Office / OnOff-9.1 On-Off Module' on. The reason you're not seeing any notifications is because your "Then" statements either aren't doing anything, or erroring out. Before writing a program, test the notifications individually to make sure they are working Edit.. to prove this theory right (or wrong) add the following statement in the then Your devices 'Office / OnOff-9.1 On-Off Module' pick "Beep" from the drop down as the action When you turn the device on, it will beep at the device, showing that "Control" is actually working

Based on recent threads, I'm guessing that the notifications are new... have you tested them? What happens if you right-click on the program and select "run then" to force the program to run?

The. I ink for the device direct is different than the links for the scene. I would right click on one of the devices and pick "Restore device" and then retest the scene. This may not be it, but important to eliminate and doesn't take long to do.

If I read the first post right, you should be able to set the on levels for the local switch behaviors (first post) and each/every scene (;ast post) and have those 2 things be different. If there are multiple scenes associated with keypad buttons, you'll have to open each scene and change all of the members, including the second entry on the second graphic - foyerrecessed 1st floor. You can do a lot with variables but my understanding of what you want should be solvable with scenes... just a lot of detail work for every "moving part" in the setup