HS 2.0 is available (for real this time)

I have taken the plunge, sort of. I've got HS2 running under VMware on W2kPro. I did a clean install as I didn't have my old HS1.7 config around (that PC died again in May). Here's what I've found.

My inital install failed. I guess it installed .NET Framework, but it still errored out. I got the framework separately and installed it, things worked ok this time.

I still don't have TTS though. Not sure why. The Speaker app errors out when I start it. I'll have to look into that.

I initially didn't have the MDAC 2.8 install. HS2 corrupted the newly-created sample.mdb when it "saved" it on shutdown. Result: restarting HS2 hung because the database was corrupt. Nice. Why can't they just check for the right MDAC version BEFORE messing up the db?

I blew away the db and installed MDAC 2.8, then restarted HS2, it rebuilt the blank sample.mdb and off we went!

BUG: I added a few devices. Made a mistake and named two devices the same, HS2 didn't complain, but I couldn't see both devices on the web GUI. They were in the db, however. I renamed the one I could see, the other one came back, but then I had to modify it to make sure the db wasn't messed up. It LOOKS like it would be fairly easy to get the db screwed up by making this mistake again... not sure what the consequences would be. Maybe they need to enforce unique device names, or modify the web GUI so that it shows ALL devices... not sure what the issue is here but I have some ideas.

BUG: Every time I start HS2, it goes through all my devices and throws an error saying they've been changed, and resets the device types to UNKNOWN. Every time.

I'm running two serial ports into VMware from the main machine. One goes to my Ocelot, which I use for X10 PLC communication. The other goes to my MR26A for X10 RF reception. This is my basic need setup. I could use a few more serial ports, but the Equinox board isn't supported by VMware. For testing, this will be ok.

I had to configure the Ocelot and download the MR26A plugin and configure it from the updater. The config went well on the Ocelot, and I had it create all devices for the Ocelot and the Secu-16 I have. The updater worked well, too. However, the config on the MR26A plugin was a little messy. Initially, the config screen opened behind everything on my desktop, and having no tab at the bottom of the screen, I didn't see it. Took a minute for me to find it and configure the thing.

Then, I made a mistake on it, so after saving the changes, I went back into it. After making the change, it said there was no comm port specified, but I hadn't changed that. I saved anyway and restarted HS2, but no MR26A comms. Errors about no comm port.

I went back onto the MR26A config, plugged in the same existing comm port number there, and voila! it worked this time. Saved and restarted, I had MR26A comms now. This is a plugin issue.

BUG: However, I'm getting lots of program errors with it, and eventually it shuts down. Not good, this is my main RF receiver. Oh well... this is a test instance.

I added a few more devices, set up some events and tested. Seems to work ok.

So far, the base program looks pretty good, solid. I don't have the voice working - it doesn't seem to want to allow me to use the new Speaker app locally. I'll look into that later today or tonight. It might be a VMware thing, or it could be the install - I didn't see SAPI5 installed with HS2, so that might be it.

I'm probably not going to install over an older 1.7 install, simply because I'm moving the first of next month, and there's no reason for me to bring an old config forward since so much will be changing soon. I'm sure there will be pitfalls there, too. Read the docs on the HS2 beta release to get the specifics. No doubt you will have to make some manual changes.

Enjoy!
 
Some Plugin Questions for HS 2.0:

Hmmm, I am a big Ocelot user myself (with SECU16I and RELAY-8 modules). I am using the ADIOcelot program currently under HS1.7 and not Homeseer's Ocelot (older) plugin. How is the current Homeseer 2.0 Ocelot plugin compare to the ADIOcelot plugin? Wonder if Michael McSharry is going to update the ADIOcelot for HS2.0? This would probably rename all of my Ocelot devices if I switched I imagine?!?

I am also a big user of the W800 RF receiver, but use the CM19a for Ninja commands. I see that Ninja support is probably history with HS 2.0. Not to big of a deal as the X10 ocx will let you come up with a script without to much hassle (had a VB6 programming running the Ninja a long time ago at one point).

The CADDX plugin is probably a HUGE downfall for me right now. I can't live without the announcements to Caddx zone changes (that the current 1.7 plugin allows). This is a difficult one as Nitrox, the creator of the original plugin, is not supporting this effort any more. There have been promises from another author, but that has not become a reality as of this point.

WAFCallerID, is it supported? I don't see it even listed on Rupp's hitlist and I'm not sure the author is interested in developing an HS 2.0 compatible one. Actually being a script and not a plugin, hopefully it will work. Can anyone confirm this?

Krumpy has stated that the mlhsplugin (Main Lobby/Homeseer plugin) is working with HS 2.0 (latest version of that plugin), so at least one of my plugins will probably work.

Good luck with all you beta testers and keep us informed of your progress!!
 
From my understanding, the if you want to use all the Ocelot's features, you need ADIOcelot, If you are only using the ocelot for IR (and have no SECU's hooked-up) the HST Ocelot plugin will suffice.

Micheal's made some posts stating that ADIOcelot tested OK with HS 2.0, and that he will likely not be converting it to .NET (I think it's an EXE plugin now). He also mentione that it can be used via XAP as well (if you have it on another machine).

I'm very concerned about the W800 support as well. I'm also shocked that it may become a "pay for" plugin.... I think the manufacturer of the W800 should somehow subsidize the purchse of the plugin, since - probably - a great number of hardware purchsases come from HS users (I think, for some reason, I thought Oman worked for the W800 folks, and that was why the plugin was free - becuase they plugin and hardware were codependant - one is useless without the other).

Anyway, this is probably gonna be one of the rare times that I'm not an early adopter, and will likely let everyone else work out all the bugs (My system runs really well now).
 
Well, had another thought. If the Elk guys would support the W800 via one of the serial ports in the M1 series controllers that would be a HUGE selling point for them (since a compatible HS2.0 Plugin already exists for the Elk). That PLUS the fact that a Homeseer plugin DOES NOT EXIST yet for their largest competitor CADDX Security (NX8e).

BTW Elk Managers, you can send me a refferal check for ALL the Elk sales I just made for you guys! :D
 
Hello all,
I downloaded the new HS 2.0. and installed it. I am a new HS user so I don't know much about it. When I heard that the W800 would not work I stoped testing as this is the trigger mechanism I use. I did notice that the speaker app crashed as Huggy59 mentioned. I could not get it to start.

T.
 
What comes after omega?

No discusion here or in reply to my thread at HS on the "new and improved" features.

Leaves me to wonder if there are any.

Apparently even multi-threading is not what it was cracked up to be.

GLT
 
The Speaker app requires WMP 9 or 10. That was why mine didn't work. It's working now that I've installed WMP. I've also installed it on another remote machine and it works for the TTS. I have not tested VR through it yet.

I'm using the HST Ocelot plugin and it found and loaded my Secu-16 I/O points, and it is working well. I think the differences from the ADIOcelot (which I used on 1.7) are relatively minor, but could be a big factor if you need those extra capabilities.

I think if I chose to go with HS2, that I'll be rolling back to a lot of scripting rather than using plugins, simply because it's going to take some time for old plugins to be updated, and/or new plugins to be written to support existing functionality. But that doesn't bother me - I used a lot of custom scripts anyway cause I didn't like the way the plugins worked and could easily integrate them with new functionality.

I've been a CADDX user, but that may change. Jury is still out on that. I'll wait till I get settled to determine what I do with an alarm system.
 
Thanks for the fix on the Speaker app, downloading WMP now.

My W800 is working like a champ. I installed HS 2.0 by installing over my HS 1.7 directory. I haven't done a lot of testing, but my DS10 and a couple of palm pads/other remote are working. What is the issue supposed to be with it?
 
Chakara said:
My W800 is working like a champ. What is the issue supposed to be with it?
Wow, that is great news. Wonder if anyone else had this luck. People over at HS land were saying it would not work with HS 2.0 because its plugin was not updated! Keep testing and please keep us informed!
 
If you are using Z-wave devices then you will apreciate the multi threading because it nearly instantly updates the status of the devices with polling. There may be a hald second delay but its much faster than the 30 seconds I had to wait with 1.7...

Tomorrow night I will start adding scripts and events and then I will see how good Multi Threading is for the rest of the stuff. I bet its really near since I can have the lights flash and an annoucement that its time for bed at the exact same time.

I'm gonna have a ton of fun with this as long as it stays stable.

I just wish they wouldnt have gotten my hopes up about C# being able to be used for scripting and then I find out it was never really suposed to be included but they may try and add support for it.
 
Change in HS2 Upgrade Pricing

Originally I remember that the upgrade price for HS2 was going to be $39. Now it seems you will only have 30 days to take advantage of this price, otherwise the upgrade is going to $99. Even if you don't plan on going to HS2 right away, you may want to consider buying the upgrade now and save some money.

The Pod
 
I believe it is 30 days from the official release of 2.0.

....so we have 2 years 6 months and 12 days before we have to start worrying. :)
 
I ust went ahead and purchase a 2.0 license, even though I haven't even installed the beta yet (and probably won't install the release version - which they say is slated for THIS FRIDAY - for a while.... unless the few remaining plugins I need crossover).

I figure I'd better do it now, or I might forget and make a $60 mistake.

If by some miracle the last few plugins I need to come out before August 5, however, I may go ahead and upgrade becuase the wife is out of town next week, so I can burn the midnight oil getting things working....
 
Back
Top