paulbates

The hub is extremely lightweight functionality wise. While it works well, its no comparison to the ISY. it has schedules, does notifications and has simple smart phone apps to turn things on and off. Its essentially an Ethernet connected smartlinc. Its main advantages are that its wired network connected and its x10 signaling seems stronger. A homeseer developer modified his plugin to interface with it and it works very well, its is feasible that the ISY could be updated to interface to it via ET. The disadvantage is that it must be polled via a rest type interface to detect insteon network changes and that can add a slight delay. I did some tests and its not as bad as I would have thought, but measurable. The flip side is that its more reliable than the (non ISY) USB PLM i replaced with it. The way i use it is to control an outletlinc that my current server plugs into. I can remotely access that via on the insteon hub and reboot my server without losing control. Sent from my iPad using Tapatalk HD

It sounds like you are mixing X10 and Insteon messages in the same program? My experience is that the PLM is not that smart about managing that.I have experiences where (I believe) the PLM sends the X10, but the insteon traffic on the network stomps on it. X10, being X10, can not recover from that. An example is if you send an insteon message through the plm, your insteon network goes to work receiving and responding to those messages. Yet right behind the insteon scene message, the program requests an x10 message get sent. The PLM will go right ahead and send that x10 message, even as the other insteon devices are confirming their status. and you get no response from the x10 device A way to check test this theory is to put a longer wait, eg 10 seconds to that keypad message and put x10 last as Lee indicated. If that works, back your way into a shorter time.