Jump 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.

MarkJames

Members
  • Joined

  • Last visited

Everything posted by MarkJames

  1. I hadn't considered that. I've set my home up as a domain and all the workstations log in for file and resource sharing. This is primarily to keep control of my kids and so I can sleep at night knowing noone is gonna fdisk my drives while I'm away. It also prevents the issue of malware installing itself as noone has admin privileges but me - so if something is gonna get installed I gotta be the one to install it. As a concession, though, I run vmware on one of my workstations so my kid can play all he likes. There are no shared folders with the real world on this setup so he has full admin privileges and I don't much care what he does. Mostly he plays with Greenfoot - a Java kind of interpreter language for kids game development (I think) It would be a non-issue, though, to run a second VM on that machine for homeseer as it has 7gb of RAM in it.... Then again, for $200 I could stick it in a closet, RDP to it for programming, and otherwise forget about it. I'll have to give this some thought. The only issue I can see is hooking the VM machine isn't near the PA system so I couldn't run the audio through the house. It's also a long way from the Stargate so I couldn't control that either. Anyways... sorry for thinking 'out loud', and thanks for the input. Mark PS.. sorry for the 'crappy Atom' comment... didn't realize you worked for Intel If it's any consolation all my computers are Asus mobos with Intel processors.
  2. Well it's quickly becoming apparent that my old celeron based clunker with a whopping 256mb of ram is just not gonna do it for homeseer. It works - but just. As I just dropped the better part of 4grand on a new DVR, cameras, wireless sensors, some more smarthome goodies and a bunch of other stuff the wife doesn't know about I'd say that a new PC of any consequence is out of the question. Bob... you would probably know the answer to this. I'm looking at the Acer Revo - a sort of netbook with a crappy atom processor in it - but it's like $200 and it has a gb of RAM. Would this be enough of a computer for homeseer with your plugin? mark
  3. Always a handy thing to have in a large X-10 installation.
  4. You know your code! It's chugging away doing it's thing. Thanks for the help. mark
  5. That will be it, then. I'm on 2.7.12 I'll go get the beta. Thanks for your help! Mark
  6. Well - I seem to be having some trouble with the homeseer plugin. I got it installed and config runs but I can't add my devices. Here's the log 3/5/2010 9:42:05 PM - Info - Initializing Plug-in: Insteon on COM port 3 3/5/2010 9:42:06 PM - Insteon - PLM contacted on COM3 with an Insteon address of xx.xx.xx and firmware version 85 3/5/2010 9:42:06 PM - Info - Finished initializing plug-in Insteon 3/5/2010 9:42:06 PM - Info - Initializing Plug-in: ISY Insteon 3/5/2010 9:42:06 PM - ISY Insteon - Creating isy class instance: [192.168.xxx.xxx] 3/5/2010 9:42:06 PM - ISY Insteon - COMM: Parse description URL (http://192.168.xxx.xxx/desc) 3/5/2010 9:42:07 PM - ISY Insteon - COMM: Attempt to authenticate ISY access. 3/5/2010 9:42:07 PM - ISY Insteon - COMM: Authenticating with ISY 3/5/2010 9:42:07 PM - ISY Insteon - COMM: Subscription thread started 3/5/2010 9:42:08 PM - ISY Insteon - COMM: Authenticate returned 200 3/5/2010 9:42:09 PM - Database Item - Saving Device Global Insteon All Devices 3/5/2010 9:42:10 PM - ISY Insteon - COMM: service client created 3/5/2010 9:42:10 PM - ISY Insteon - COMM: Set ClientCredentials. 3/5/2010 9:42:10 PM - ISY Insteon - COMM: Busy Check - delay only. 3/5/2010 9:42:18 PM - ISY Insteon - COMM: ISY configuration query attemp 1 failed. 3/5/2010 9:42:18 PM - ISY Insteon - COMM: ISY configuration query attemp 2 failed. 3/5/2010 9:42:19 PM - ISY Insteon - COMM: ISY configuration query attemp 3 failed. 3/5/2010 9:42:19 PM - ISY Insteon - COMM: ISY configuration query attemp 4 failed. 3/5/2010 9:42:19 PM - ISY Insteon - COMM: ISY configuration query attemp 5 failed. 3/5/2010 9:42:19 PM - ISY Insteon - COMM: ISY configuration query attemp 6 failed. 3/5/2010 9:42:20 PM - ISY Insteon - COMM: ISY configuration query attemp 7 failed. 3/5/2010 9:42:20 PM - ISY Insteon - COMM: ISY configuration query attemp 8 failed. 3/5/2010 9:42:20 PM - ISY Insteon - COMM: ISY configuration query attemp 9 failed. 3/5/2010 9:42:20 PM - ISY Insteon - COMM: ISY configuration query attemp 10 failed. 3/5/2010 9:42:21 PM - ISY Insteon - COMM: ISY configuration query failed. 3/5/2010 9:42:21 PM - Info - Finished initializing plug-in ISY Insteon 3/5/2010 9:42:21 PM - Info - Finished initializing X10 interface 3/5/2010 9:42:21 PM - Info - Finished initializing infrared interface 3/5/2010 9:42:26 PM - Info - Local IP address (subnet) is: 192.168.xxx.xxx(255.255.255.0) 3/5/2010 9:42:26 PM - Info - UPNP Discovery started 3/5/2010 9:42:26 PM - Info - Web Server started on port 80 3/5/2010 9:42:27 PM - Info - Web Server authorized local login successful from: 127.0.0.1 User: default 3/5/2010 9:42:27 PM - Info - Creating ASP.NET application host... 3/5/2010 9:42:37 PM - Info - ASP.NET application host created then when I just hit the save button I get 3/5/2010 9:54:04 PM - ISY Insteon - MAIN: Entered GenPage for Status 3/5/2010 9:54:04 PM - ISY Insteon - COMM: GetNodes: No matching nodes of type TYPE_CLIMATE found. 3/5/2010 9:54:04 PM - ISY Insteon - COMM: GetNodes: No matching nodes of type TYPE_WEATHER_MOD found. 3/5/2010 9:54:04 PM - ISY Insteon - COMM: GetNodes: No matching nodes of type TYPE_ENERGY_MOD found. 3/5/2010 9:54:04 PM - ISY Insteon - MAIN: Leaving GenPage for Status 3/5/2010 9:54:08 PM - ISY Insteon - MAIN: Enter Status PagePut 3/5/2010 9:54:09 PM - ISY Insteon - COMM: Subscription thread started 3/5/2010 9:54:09 PM - ISY Insteon - COMM: Calling GetNodesConfig ... 3/5/2010 9:54:09 PM - ISY Insteon - COMM: Subscribe: Caught abort: Thread was being aborted. 3/5/2010 9:54:09 PM - ISY Insteon - COMM: Busy Check - delay only. I've updated to dot net 3.5 and the newest version of the Java runtimes. I've confirmed that I can get to admin console from that machine and connect properly. I do have a number of services disabled on that machine. As I mentioned it's not a very powerful box so I've disabled a lot of services that I normally wouldn't use - network DDE, net tcp port sharing, routing and remote access, and a few others. I'm wondering if that might be the problem. The other potential issue I should point out is that I'm testing Brad77's mediacenter plugin. I'm not sure if the connection from the mce plugin could in some way interfere with the operation of the homeseer connection. I know my Elk rules won't run with my ISY till I disconnect from the Elk. I've tried shutting down MCE while testing the homeseer plugin but, as Scotty would say 'It dinna do a bi agood' mark Edit: [40 minutes later] I thought about it a bit and decided that perhaps I shouldn't have insteon enabled in homeseer if I have the isyinsteon plugin there as well. I thought having 2 PLMs in the system (yeah... I'm strange, I actually have 3) may confuse things. I disabled it and restarted homeseer but it didn't make any difference. I did notice a message that didn't appear in the log - it said 'comm manager found a non-ISY UPnP device' when I hit save on the insteonISY config page. here's the log from an attempt to use the port as 192.168.xxx.xxx:443 (I thought it may need to be https) and with my regular IP again. 3/5/2010 10:31:05 PM - ISY Insteon - MAIN: Entered GenPage for Configuration 3/5/2010 10:31:05 PM - ISY Insteon - MAIN: Leaving GenPage for Configuration 3/5/2010 10:31:12 PM - ISY Insteon - MAIN: Enter PagePut 3/5/2010 10:31:12 PM - ISY Insteon - MAIN: old_loc = 0, location = 0 3/5/2010 10:31:12 PM - ISY Insteon - MAIN: old_loc2 = 0, location2 = 0 3/5/2010 10:31:12 PM - ISY Insteon - MAIN: Leaving PagePut 3/5/2010 10:31:12 PM - ISY Insteon - MAIN: Entered GenPage for Configuration 3/5/2010 10:31:12 PM - ISY Insteon - MAIN: Leaving GenPage for Configuration 3/5/2010 10:31:19 PM - ISY Insteon - MAIN: Enter PagePut 3/5/2010 10:31:19 PM - ISY Insteon - MAIN: PagePut: Calling start_isy() 3/5/2010 10:31:20 PM - ISY Insteon - COMM: Subscribe: Caught abort: Thread was being aborted. 3/5/2010 10:31:20 PM - ISY Insteon - COMM: Subscription thread started 3/5/2010 10:31:20 PM - ISY Insteon - COMM: isy instance reset to initial values. 3/5/2010 10:31:20 PM - ISY Insteon - COMM: Calling GetDescURL(192.168.xxx.xxx:443) 3/5/2010 10:31:20 PM - ISY Insteon - COMM: Parse description URL (http://192.168.xxx.xxx:443/desc) 3/5/2010 10:31:20 PM - ISY Insteon - COMM: Attempting to auto-discover ISY 3/5/2010 10:31:20 PM - ISY Insteon - COMM: Starting auto-discovery 3/5/2010 10:31:25 PM - ISY Insteon - COMM: Found a NON-ISY UPNP device. 3/5/2010 10:31:29 PM - ISY Insteon - COMM: Found a NON-ISY UPNP device. 3/5/2010 10:31:29 PM - ISY Insteon - COMM: Found an ISY: http://192.168.xxx.xxx/desc 3/5/2010 10:31:29 PM - ISY Insteon - COMM: Found URL http://192.168.xxx.xxx/desc 3/5/2010 10:31:29 PM - ISY Insteon - COMM: Parse description URL 3/5/2010 10:31:30 PM - ISY Insteon - COMM: Attempt to authenticate ISY access. 3/5/2010 10:31:30 PM - ISY Insteon - COMM: Authenticating with ISY 3/5/2010 10:31:30 PM - ISY Insteon - COMM: Authenticate returned 200 3/5/2010 10:31:30 PM - ISY Insteon - COMM: service client created 3/5/2010 10:31:30 PM - ISY Insteon - COMM: Set ClientCredentials. 3/5/2010 10:31:30 PM - ISY Insteon - COMM: Busy Check - delay only. 3/5/2010 10:31:31 PM - ISY Insteon - COMM: ISY configuration query attemp 1 failed. 3/5/2010 10:31:32 PM - ISY Insteon - COMM: ISY configuration query attemp 2 failed. 3/5/2010 10:31:32 PM - ISY Insteon - COMM: ISY configuration query attemp 3 failed. 3/5/2010 10:31:32 PM - ISY Insteon - COMM: ISY configuration query attemp 4 failed. 3/5/2010 10:31:32 PM - ISY Insteon - COMM: ISY configuration query attemp 5 failed. 3/5/2010 10:31:33 PM - ISY Insteon - COMM: ISY configuration query attemp 6 failed. 3/5/2010 10:31:33 PM - ISY Insteon - COMM: ISY configuration query attemp 7 failed. 3/5/2010 10:31:33 PM - ISY Insteon - COMM: ISY configuration query attemp 8 failed. 3/5/2010 10:31:33 PM - ISY Insteon - COMM: ISY configuration query attemp 9 failed. 3/5/2010 10:31:34 PM - ISY Insteon - COMM: ISY configuration query attemp 10 failed. 3/5/2010 10:31:34 PM - ISY Insteon - COMM: ISY configuration query failed. 3/5/2010 10:31:34 PM - ISY Insteon - MAIN: old_loc = 0, location = 0 3/5/2010 10:31:34 PM - ISY Insteon - MAIN: old_loc2 = 0, location2 = 0 3/5/2010 10:31:34 PM - ISY Insteon - MAIN: Leaving PagePut 3/5/2010 10:31:34 PM - ISY Insteon - MAIN: Entered GenPage for Configuration 3/5/2010 10:31:34 PM - ISY Insteon - MAIN: Leaving GenPage for Configuration 3/5/2010 10:35:05 PM - ISY Insteon - MAIN: Enter PagePut 3/5/2010 10:35:05 PM - ISY Insteon - MAIN: PagePut: Calling start_isy() 3/5/2010 10:35:06 PM - ISY Insteon - COMM: Subscribe: Caught abort: Thread was being aborted. 3/5/2010 10:35:06 PM - ISY Insteon - COMM: Subscription thread started 3/5/2010 10:35:06 PM - ISY Insteon - COMM: isy instance reset to initial values. 3/5/2010 10:35:06 PM - ISY Insteon - COMM: Calling GetDescURL(192.168.xxx.xxx) 3/5/2010 10:35:06 PM - ISY Insteon - COMM: Parse description URL (http://192.168.xxx.xxx/desc) 3/5/2010 10:35:06 PM - ISY Insteon - COMM: Attempt to authenticate ISY access. 3/5/2010 10:35:06 PM - ISY Insteon - COMM: Authenticating with ISY 3/5/2010 10:35:06 PM - ISY Insteon - COMM: Authenticate returned 200 3/5/2010 10:35:06 PM - ISY Insteon - COMM: service client created 3/5/2010 10:35:06 PM - ISY Insteon - COMM: Set ClientCredentials. 3/5/2010 10:35:06 PM - ISY Insteon - COMM: Busy Check - delay only. 3/5/2010 10:35:07 PM - ISY Insteon - COMM: ISY configuration query attemp 1 failed. 3/5/2010 10:35:08 PM - ISY Insteon - COMM: ISY configuration query attemp 2 failed. 3/5/2010 10:35:08 PM - ISY Insteon - COMM: ISY configuration query attemp 3 failed. 3/5/2010 10:35:08 PM - ISY Insteon - COMM: ISY configuration query attemp 4 failed. 3/5/2010 10:35:09 PM - ISY Insteon - COMM: ISY configuration query attemp 5 failed. 3/5/2010 10:35:09 PM - ISY Insteon - COMM: ISY configuration query attemp 6 failed. 3/5/2010 10:35:09 PM - ISY Insteon - COMM: ISY configuration query attemp 7 failed. 3/5/2010 10:35:09 PM - ISY Insteon - COMM: ISY configuration query attemp 8 failed. 3/5/2010 10:35:10 PM - ISY Insteon - COMM: ISY configuration query attemp 9 failed. 3/5/2010 10:35:10 PM - ISY Insteon - COMM: ISY configuration query attemp 10 failed. 3/5/2010 10:35:10 PM - ISY Insteon - COMM: ISY configuration query failed. 3/5/2010 10:35:10 PM - ISY Insteon - MAIN: old_loc = 0, location = 0 3/5/2010 10:35:10 PM - ISY Insteon - MAIN: old_loc2 = 0, location2 = 0 3/5/2010 10:35:10 PM - ISY Insteon - MAIN: Leaving PagePut 3/5/2010 10:35:10 PM - ISY Insteon - MAIN: Entered GenPage for Configuration 3/5/2010 10:35:10 PM - ISY Insteon - MAIN: Leaving GenPage for Configuration mark
  7. installing 3.5 as we speak... I was on 2.0. Like I said - it's a clunker - it'll be installing 3.5 for 45 minutes easy. Once upon a time there were no JRE's or dot net frameworks..... now it's the first thing you gotta check. Of course back then you had to check your IRQ and your DMA. I guess it's a wash. mark
  8. Thanks, Bob, lol - good to see the author right here. Who woulda thunk it? I'm having a bit of a time getting it to be recognized in the setup screen. I keep getting an 'unable to access HSPI_ISY_insteon.hspi (or something similar - I can't cut/paste from my telnet session) in the log. I'll try updating my .net framework - perhaps it's too old. mark
  9. Thanks - I'll try that. I was using the updater and many of the plugins said 'free to try - x$ to buy' but that one didn't have that notation attached. Thanks again, mark
  10. I didn't see a try-before-you buy with it. All I saw was a 'pay now' button. $60 is a lot to buy something sight-unseen. mark
  11. I was just about to buy the ISY plugin for homeseer. I noticed there's a coupon code box. Does anyone know any coupon codes for this? Thanks in advance, mark
  12. I'm not sure Michel meant that all your devices have to be in the same 'state' as your scene in order to write. If that were the case I'd never be able to write to any of my switches as they're all members of multiples scenes. They'd never be in sync with one another as far as all the different scenes were concerned. If this is, indeed, the case I'd like to know as it would be a significant change to my understanding. mark
  13. Sorry.. this is the quote I was referring to from a different post in which Michel mentioned that you could delay writes. In retrospect it doesn't seem to answer your problem. mark
  14. MarkJames replied to MarkJames's topic in ISY994
    My bad - I assumed the hometroller was some kind of flash-based device that ran only homeseer. Does that work well? I've considered it but rejected the idea thinking that noise and such would make it clunky Are you using stargate relay outs to direct your PA announcements or are you targetting them some other way/not at all? Stargate is truly a stable workhorse. It's hard to make it crash without dumping tons of data into the serial ports. Is this just to integrate everything? Schedules still have to be written in winevm, I would think. I've wanted to use communicating thermostats but my home is a mix of hotwater baseboard heat, electric radiant, and electric baseboard. The electric baseboard requires 220V thermostats. There was once a co mmunicating stat made by ouelette - x10 based - but it's no longer available and you couldn't query it. If I can't do all of it it seems pointless to do part of it. You must have built your home around your HA. Sounds like you've got serial communication wire running all over - that's hard to retrofit, though possible if you're determined enough.
  15. I think oberkc hit it. There are a couple of green icons in 2.7.12 and the previous few releases. One has like a 101 on it - the other says writing. The 101 means that there is a pending write - the writing one - well - is writing. I don't have pro but from what I understand there's a batch write feature. I thought this was mostly intended for RF devices but the impression I got was that it can be used for any. Have you tried rightclicking the device with the green arrow and hit 'write updates'? Or using the batch mode button? I'm with oberkc on this - I don't think that the state of any scene/device matters to it as far as ISY writing to it. If it is it's a behavior I've never seen myself.
  16. MarkJames replied to MarkJames's topic in ISY994
    Are you using the pc based version or the controller based? If it's the pc based do you find it stable? mark
  17. MarkJames posted a topic in ISY994
    Just curious if anyone is using voice prompting at all with their ISY. I come from JDS Stargate so I've become dependent on voice outputs and phone commands. I really miss those. Being informed through a speaker that 'the garage door is open' is far superior, imho, to having a light flash or some other indicator. To accomplish this with ISY I've been using it parallel to PowerHome 2. The PowerHome software supports TTS (text to speech). I have an old PC that I've installed Powerhome on with a second PLM to integrate it into my home system. I haven't added any of my insteon devices to the second PLM - it's just there as an interface between the insteon powerline messaging and the PC. When something turns on - like the garage door I have a program like this If Status 'Garage Door Sensor' is not Off Then Send X10 'E3/On (3)' Set Scene 'Garage Door Open Alert LED' On Else Set Scene 'Garage Door Open Alert LED' Off The Powerhome software sees the E3 On via the PLM and that triggers a TTS event that speaks the words 'Garage Door Open' through an amplifier connected to speakers in the house. It checks the time of day first, of course, so it doesn't go yelling stuff in the middle of the night. This works - sort of. Powerhome is a bit prone to crashing so I have to restart it every couple of days. It would be great to have an interface of some sort that would allow TTS based on Insteon messages/status. Is anyone aware of such a creature? mark
  18. I just read through all the posts in this forum and I think congrats are in order. There doesn't appear to be many problems reported with 2.7.12 Time for the Elk module!
  19. you can't 'write anything'? As in make changes to the link records and change the scene memberships?
  20. That's true - the PLM is a controller for every button, group, load, and scene in the system. There's a long-winded explanation for how controller/responder records works here
  21. MarkJames replied to MarkJames's topic in ISY994
    Good point! I've been lucky - never had an update go bad! Keepin' my fingers crossed!
  22. MarkJames replied to MarkJames's topic in ISY994
    ahh... thank you. So as long as I find ISY just fine through my regular browser session to the ISY ip there's no reason for me to use the launcher. Excellent. I'll keep that link info around in case I need it one day, though. mark
  23. MarkJames posted a topic in ISY994
    Is there a difference between launching the admin console from http://www.universal-devices.com/99i/2.7.12/admin.jnlp vs just pointing my browser straight to the ISY? Why would you use one over the other? mark
  24. I updated from 2.7.11 to 2.7.12 and can no longer play the violin. Curse you, ISY
  25. MarkJames replied to grossmd's topic in ISY994
    I only forward port 80. I use port 800 externally and internally use port 80. My ISY is on port 192.168.0.170 - so my forward looks like this TCP forward external port - 800 internal port - 80 destination IP - 192.168.0.170 My WAN IP (given to me by my ISP and visible in the status section of your router or even easier - just go to whatismyip.com) is, say, 169.154.20.13 - so when I'm away I log on to http://169.154.20.13:800 The reason I use 800 instead of 80 is that some ISP's scan their IP range for web servers and will give you grief if they find one. If you don't care about this you can just forward your port 80 and skip the :800 part as http will take you to port 80 by default. mark

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.