New Beta Posted 10/15/2016 

UPDATE 10/15/16: Today we published what we believe to be a comprehensive and stable update, and as such we're labeling this a Release Candidate and making it a wide release. It includes numerous features, updates, and fixes, including:

• OSRAM/Sylvania Lightify bulbs are now supported
• Complete mobile app overhaul
• New live security display
• Live updating mobile app (no more refresh needed to update device status)
• IntelliMode system mode capability
• Updated REST web services
• And much, much, much, more...!

UPDATE 9/6/16: In addition to the below, as well as fixes for reported bugs over the last few days, a new beta has been released that has IntelliMode enabled. IntelliMode allows you to set system modes like Home, Away, Vacation, and custom modes. These work in concert with events. For example:

Use as an Event Trigger: When house changes to Away mode, do this....
Use as an Event Action: When Event runs, change house to Away mode....
Use as an Event Condition: When Event is triggered, only perform the actions if the house is in Away mode...

Original Post:

Hot off the presses! The first wide-release beta of the CastleOS 2.0 branch! This includes all the backend upgrades and updates. The purpose of this beta is primarily to check the upgrade works correctly. This includes:

• the fix for the Insteon Hub CPU bug
• a brand new event processing engine that supports device properties like "temperature" as triggers, as well as conditions
• the current weather can also be used as an event condition
• all hard-coded references have been replaced by a modular structure for devices and protocols
• the new driver API (all existing internal drivers were converted)
• the new device API (all existing devices are converted)
• you can now change the color of the blue bar on top (each user gets their own)
• climate sensors are supported
• BloomSky weather stations (and weather stations in general) are supported

This is just a short list off the top of my head of some of the majors. In the coming days we'll be rolling out a bunch of app features that we'll be announcing separately. Once we're sure the base backend is stable in the wild, we'll roll out the rest.

To that end, before installing this beta, please be sure to backup configuration.xml and log.sdf (not log.log!) in case anything goes wrong with the update process.

Download Here

Thanks!

-Chris

P.S. This is labeled version 1.3.3025 (or higher), but it is indeed the 2.0 branch. The version number will get bumped to 2.0 with the formal release.
edited by ccicchitelli on 10/16/2016

Wolfieee Wolf wrote:

There was talk about a plugin feature. It that still happening ? Would really like to get my Mi-lights and my Broadlink RM pro running with your software.

Yup, that's in this release! All the existing protocols drivers were converted to the new plugin structure as well. I'll be posting videos shortly explaining how to make plugins.

Blank screen indicates the service isn't starting. Is there an error log in the windows event viewer?

Also I posted this update a few mins ago, it does have some fixes: https://drive.google.com/file/d/0B5j6VE4C-S-GMXNjTUtEYkc5M00/view?usp=sharing

Chris Stack wrote:

Thanks, I tried the update you posted last night, to no avail, I looked in the event log, and it says:

"CastleOS Core Service failed to start: Validation key cannot be null or empty"

I am not sure what the validation key is that it is looking for.

thanks,
Chris

Can you check your configuration.xml file? All look good?

Just restore your backup, no problem. You can start from scratch by uninstalling CastleOS and deleting that folder in ProgramData, but you shouldn't need to.

The white page indicates the service is not loading successfully. Sure there's not an error message in the event viewer?

Hey ATD,

Nest and other cloud devices should be fairly consistent on how often they update. In Nest's case, they use a push system so we don't poll, so it was probably when the first push message came in that everything updated. This is only noticeable after a restart, after that everything stays in sync.

Regarding the Yale locks, I have those here for testing and they are showing correctly, however you might be right that they need to be dropped and reloaded. It depends on when they were originally added to the system. The Get Node Info may not work if it's rejecting the messages for security reasons.

Thanks,
Chris

Assistive Tech Dad wrote:

NEST - On the Devices page when I open the Nest Devices list there are TEMP and HUM numbers on the far right (next to the VIEW button). Both those numbers are zero for all of my thermostats. When I click through on the view button and look at the Climate Osage readout, all my thermostats show valid temp and humidity readings.

YALE LOCKS - Readding them sounded like a good idea, but Castle won't let me delete them. I have tried Remove Failing Device and Replace Failing Device under Manage ZWave Network. I have also tried to Edit the device and click Delete there. I would rather not have to edit raw config files and factory reset my ZWave stick.

(Another beta was posted to the beta folder a few minutes ago)

For Nest, I can confirm the issue with it showing 0 on the devices page. I'm guessing the values aren't initialized correctly there. Will look at that now.

For the Yale locks, are you trying to delete them from delete device, or from remove device in the Z-Wave settings? And what does the lock itself say (or rather, beep) when you tell it to remove itself from the network?

Thanks,
Chris

Chris Cicchitelli wrote:

I've just posted a fix for the Nest issue on the Devices screen (which actually was all thermostats, that's a new feature and it wasn't loading the values correctly).

In my testing, the Nest dev API we use was only showing 0 humidity, even though it should've been showing another value. I'm not sure if the bug is their dev API, or our JSON breakdown (which should be automatic) of the incoming nest data. So when you test it, please let me know if your humidity values sync with real life or not.
Thanks!

-Chris

Will do. Love then new banner announcement for the new beta version available. If I can make a feature request, I would love a button in the UI to do the upgrade (or at least download it and try). I really am trying to run my hub headless, and it is a pain to find time to setup a terminal to do the downloads and upgrades myself.

Assistive Tech Dad wrote:

Will do. Love then new banner announcement for the new beta version available. If I can make a feature request, I would love a button in the UI to do the upgrade (or at least download it and try). I really am trying to run my hub headless, and it is a pain to find time to setup a terminal to do the downloads and upgrades myself.

Thanks for the suggestion! I'll add that to the dev list as a post 2.0 feature in order to avoid feature creep. The standard releases do get installed automatically, but betas are indeed manual. Most of our beta users aren't running on the hub (to date), but that is changing so we'll get betas to install automatically as well.

Thanks!!