Skip to content
View in the app

A better way to browse. Learn more.

Universal Devices Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

ErikN

Members
  • Joined

  • Last visited

Everything posted by ErikN

  1. ErikN replied to ErikN's topic in eisy
    Yeah, seeing that on my older Polisy after the update. Using the new UI, I can now at least separately change the city, longitude/latitude, and DST rule. However, the real issue is that there's no option to set DST always on; the DST only enables or disables the DST rule and if disabled then DST is always off. Using the new UI, however, I was able to change city from Vancouver (UTC-8) to Calgary (UTC-7) and then turn of the DST rule, and make sure the right longitude/latitude were set for Vancouver (after click save, I had to refresh browser to see the full effects of my changes). It's still a fudge but seems to be working so far. Wish the new UI would simply allow me to select city to get the coordinates and then separately set the UTC offset and set the DST rule on or off (or allow me to define my own DST rule like Asus router or some of my NTP digital clocks).
  2. ErikN replied to ErikN's topic in eisy
    A fix was pushed out this evening (thank you UD for quick response!) so it's working properly for me now w.r.t. correct current time and correct sunrise/sunset times based on section of Vancouver, BC, Canada. Hopefully others are finding similar success? Fingers crossed this won't happen again in the spring when many go on DST while some of are / will already be.
  3. ErikN replied to ErikN's topic in eisy
    What we need is: Capability to actually enter a value into the GMT offset field that accepts the valid input rather than setting the GMT offset value to -25,200 Capability to enable or disable the DST rule For example, Vancouver, BC, Canada is now on permanent DST at GMT -7 The only workaround right now is to set location to Calgary, AB, Canada to get the correct time, and then add a +1 hour offset to any timers that use Sunrise or Sunset, which is a real pain ☹️ Erik
  4. ErikN posted a topic in eisy
    Hi. I am running into issues with Daylight Savings Time. British Columbia, Canada (and several other provinces) have moved to permanent Daylight Savings Time. Overnight eisy automatically turned off DST when it should not have. There doesn't seem to be an option in the Configuration screen to select Canada, Vancouver with no DST and the Daylight Savings check box on the Clock screen is greyed out so cannot change the auto DST option and in the location selection window the Daylight Savings Rule cannot be changed either. I have tried manually setting a custom time and location but there is a problem with the Timezone Offset (GMT) field such that, whenever I change it manually, the system sets it to GMT -25200, making it impossible. I have tried hard reboot but doesn't help. I am on version 6.0.4 Any ideas? Thank you ErikN
  5. Thanks guys. Will give it a try on my next day off.
  6. Hi all I have a Polisy Pro connected to Serial PLM all up to date on software. I have replaced the PLM from time to time over the years and as a result have the original DB9 to RJ45 cable that came with the original Serial PLM, plus two brand new never been used serial DB9 to RJ45 cables that came with the new serial PLMs. The weird thing is that neither of the newer serial cables work with the original or new PLM. Only the original cable works. It seems unlikely both new cables would be defective from the factory but I suppose it is possible, unless something has fundamentally changed in how they make the newer cables. Has anyone else experienced this?
  7. Thanks for the ideas. I switched out the PLM and the issue has gone away. Soooo.... could be the PLM failed (caps were replaced not that long ago but who knows) or perhaps that one was more susceptible to power line noise. I will have to experiment to see if any recent holiday plug-ins are causing an issue. Thanks for the tips to help track it down. Erik N
  8. Hi I am running current releases of IoP with just Insteon (no PG2 or 3 modules etc.) I am looking at the event viewer and ever second to two it says it is receiving a status message, reads as follows over and over non-stop: Wed 12/14/2022 09:50:39 PM : [X10-RX ] 02 52 FF 80 Wed 12/14/2022 09:50:39 PM : [ X10] J/Status = off (2) Wed 12/14/2022 09:50:40 PM : [X10-RX ] 02 52 FF 80 Wed 12/14/2022 09:50:40 PM : [ X10] J/Status = off (2) Wed 12/14/2022 09:50:42 PM : [X10-RX ] 02 52 FF 80 Wed 12/14/2022 09:50:42 PM : [ X10] J/Status = off (2) Wed 12/14/2022 09:50:43 PM : [X10-RX ] 02 52 FF 80 I don't seem to have any devices with ID 02 52 FF 80 so not sure where this could be coming from unless it's a failed device. If I understand correctly, this is X10 traffic but I have no X10 devices plugged in (I have 2 but unplugged them to eliminate them as source if this). Anyone have any thoughts on this? If it's a failed device and suggestions on how to track down which device? Thanks ErikN
  9. Thank you everyone this has been very helpful. Erik
  10. Hi folks. I have been watching with interest the developments around Polisy for the last few years. At first I didn't quite understand it but I think I do now but hoping for some clarification and advice. I have a basic ISY994 that has served we well for some time. Almost all INSTEON devices plus a couple very old X10. It is interfaced with an iPhone based remote control system (roomieremote.com) and the two generally work well together. However, with the decline in availability and range of INSTEON devices available, I am looking at expanding into using Z-Wave+ (and maybe more?). This leads me to consider, whether I should upgrade / replace the ISY994 with an ISY994i ZW PRO to provide more capacity and Z-Wave capability, or for a few (well a little more than a few) dollars more make the bigger jump to Polisys with the ZW dongle, which it sounds like is evolving quickly and of course there's always some bugs to but mostly ready for mainstream use now. Just to clarify, in addition to running on a much more powerful UNIX based platform and the capability to add node interfaces to a virtually limitless array of other devices, it is my understanding that Polisys also hosts essentially the same event/device/node-based programmable application with essentially the same interface that runs on the ISY994, and I can basically import a backup of devices, scenes, scripts, network resources, etc. from my existing ISY (or I can re-develop them manually). So I can basically start by replacing my existing ISY994 and port over pretty much everything as is, and then from there expand and start looking at ways to use the new Polisys functionality. Is my understanding correct? Is there anything critical on the ISY that won't port over or won't work at all in this ISY on Polisys environment? The existing ISY994 API / REST interface that my remote control software uses to collect the manifest of devices and to send commands, control devices, run scripts, and receive device status updates, does that still work the same and use the same command string formats? Would you recommend making the jump to Polisys +ZW now, or perhaps just getting the ISY994i ZW+ PRO for now, and consider Polisys once it settles in even further? I am an old-school software developer but have been out of that business for many years and don't have time to join the effort to develop additional node interfaces etc. so I would be paying the full price for Polisys so there is a cost differential between them. Any clarifications or advice would be much appreciated. Erik
  11. ErikN posted a topic in IoX Support
    Anyone know if there are any plans to support some kind of basic text/string variables? Would be nice for example to set a variable contacting IP/Mac address for devices called using the network module.
  12. ErikN posted a topic in ISY994
    Help! I just purchased an ISY-99i/IR (with the PLM + 1 access point) plus 3 Insteon dimmer devices. I am a long-time X10 user, and looking forward to migrating over to Insteon and greater control with the ISY. I am having some difficulties though: I had no trouble linking and controlling 2 dimmer devices (2476DH and2486D) with the ISY, but have not been able to link the 3rd dimmer (2476D). The automatic linking that worked easily for the first 2 devices did not work at all for the 3rd (no error, nothing) so I tried the manual linking it (i.e. "New INSTEON device") and entering the address, but get back an error "Failed writing the Highwater mark" and "Node not added - failed removing links". The event log contains a message ""Failed getting engine version, reverting to i1", not sure if that is relevant. I have tried moving the ISY/PLM to another location. What is really odd is that all 3 dimmer devices are located side by side in the same electrical gang box, and 2 work but 1 doesn't, so it seems hard to believe that there is an interference problem. I even switched the problem dimmer with one that is working and it still doesn't work with the other device still works fine. I tried a factory reset on the device, but did not help. The LEDs seem to indicate that it is going into controller linking mode rather than linking as a responder when I hold down the button to link. Note that it works fine as a stand-alone dimmer but won't link to the ISY. Could this dimmer be faulty? On an unrelated note: How do I unlink a device from the ISY? According to Insteon device doc, to unlink I need to put the controller into unlinking mode, but can't figure out how to do that in the ISY console. Thanks for any help Erik

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.