Securifi Community Forum

Sensors and Home Automation => Home automation => Topic started by: thechadly on October 21, 2014, 09:42:03 am

Title: 2gig CT100
Post by: thechadly on October 21, 2014, 09:42:03 am
The heating function doesn't work correctly on my thermostat.
Title: Re: 2gig CT100
Post by: LGNilsson on October 21, 2014, 10:46:51 am
Well, that's hardly our fault, we only send commands to the thermostat, so if you have a faulty thermostat, take it up with wherever you bought it from.
Title: Re: 2gig CT100
Post by: thechadly on October 21, 2014, 11:28:17 am
Okay let me reword that. The heat function doesn't work with the my almond+, the thermostat itself is fine.  If I go to try and change the heat setting with the almond or my phone it tells me it "could not connect, please try again".  At the same time if I try to change the cooling setting it has no problem. Obviously if i thought it was a problem with the thermostat I would have talked to 2Gig.
Title: Re: 2gig CT100
Post by: LGNilsson on October 21, 2014, 11:40:40 am
Well, it helps if you're specific about the issues, rather than just saying something doesn't work, right? I'm not a mind reader and I can't guess what's wrong.

Followup question then. Does it work from the LCD UI? Does it work from the local UI in the Almond+? Is this using one of the two app or is it via connect.securifi.com?
Again, I can't just figure these things out based on the information you've provided, so if you want help, please at least try to provide some more details than "it doesn't work".
Title: Re: 2gig CT100
Post by: thechadly on October 21, 2014, 01:18:57 pm
It does not work from the Almond UI nor the android app.
Title: Re: 2gig CT100
Post by: LGNilsson on October 21, 2014, 09:58:58 pm
Which Almond UI? I really need you to be very specific here. Does it work from the LCD? If it doesn't work from the LCD it's a firmware related issue which is different from an app/UI issue.
Title: Re: 2gig CT100
Post by: LGNilsson on October 21, 2014, 11:14:54 pm
Well, I just tried with the CT100 we have here in the office and it's responding just fine, so I would guess there's something wrong with your thermostat.
Title: Re: 2gig CT100
Post by: thechadly on October 22, 2014, 11:07:01 am
It doesn't work from the LCD. It also doesn't work from the Android App. The cool setting works fine. It just will not let me change the heat setting from 35 degrees.
Title: Re: 2gig CT100
Post by: LGNilsson on October 22, 2014, 11:14:59 am
I'm sorry, but I don't have any suggestions beyond that it seems like you have a faulty thermostat. As I said, I tested it this morning in the office on a CT100 and it worked just fine. The only thing you could try is to remove and add the thermostat again.
Title: Re: 2gig CT100
Post by: thechadly on October 22, 2014, 01:07:22 pm
Okay, I will try to do that once I get home. I just want to be clear that the heat function on the thermostat itself works just fine. I just can not make any changes to it via Z-wave.
Title: Re: 2gig CT100
Post by: Hoju on November 08, 2014, 07:02:50 pm
I just setup a 2gig CT100 and I am having the same problem. Manually the thermo works fine but through z-wave i can not change the heat. All other z-wave functions seem to be working. I have added and removed the sensor a couple times. I am on R66 firmware.

Just more info it is only raising the heat that does not work through the almond+. This is trying the ios app and LCD UI as well as using 10.10.10.254. When using my computer and almond ip address I get a refresh and retry error when raising the heat.
Title: Re: 2gig CT100
Post by: LGNilsson on November 08, 2014, 09:12:15 pm
This is truly bizarre, as I can adjust all the settings on the unit we have. Can you add the thermostat, then go to help, send logs and send a log, entering the model name of the thermostat and I'll get the software team to have a look.
Now that we have two people having the same issue, it looks like it has to be something wrong on our side.
Title: Re: 2gig CT100
Post by: Hoju on November 09, 2014, 09:24:46 pm
Hey Lars I uploaded the log through the almond+. 
Title: Re: 2gig CT100
Post by: LGNilsson on November 09, 2014, 10:56:13 pm
Thanks, I'll get the software team looking into it.
Title: Re: 2gig CT100
Post by: loon3 on November 13, 2014, 07:16:50 pm
I'm having the same issue.  I sent my logs through the Almond+ as well.

Everything appears to be working but I'm not able to set the temperature for heat. 

Also, in the LCD UI the slider toggle for heat temperature is not visible when I click on the thermostat sensor to open the display.
Title: Re: 2gig CT100
Post by: LGNilsson on November 13, 2014, 09:12:46 pm
Can you guys verify the model number of your thermostats?
Also, would you mind of we do a remote support session with you using team viewer so we can take a look at what's gone wrong?
This is very confusing, as we don't have any of these issues with the unit here in the office.
Title: Re: 2gig CT100
Post by: Hoju on November 13, 2014, 10:39:55 pm
Hi Lars,

The box says CT100. I bought mine from amazon.com: http://www.amazon.com/2gig-CT100-Z-Wave-Programmable-Thermostat/dp/B008CQ4V3Q/ref=sr_1_1?ie=UTF8&qid=1415936266&sr=8-1&keywords=ct100.
I updated firmware and re-added the thermostat but still can not change the heat setting through any zwave function only manually. I would be willing to let you have a look just let me known what you need on my end and we can see if there is a good time. I am on PST.
Title: Re: 2gig CT100
Post by: LGNilsson on November 13, 2014, 10:47:40 pm
I'm starting to think that there are two different versions that somehow don't behave in the same way.
The one we have is this one http://www.lowes.com/pd_388565-69305-CT-101-L_0__?productId=3735317
They look slightly different, but they're both made by the same company and have the same model number.
Title: Re: 2gig CT100
Post by: Hoju on November 15, 2014, 06:54:08 pm
It looks that way. Maybe the Lowes branded one acts a little different. Anyway getting a non Lowes one in for testing? Also other people having this problem were did you buy yours?
Title: Re: 2gig CT100
Post by: Kazy on November 15, 2014, 08:58:20 pm
That Lowes page says CT-101-L. Looks like the model is different.
Title: Re: 2gig CT100
Post by: LGNilsson on November 15, 2014, 10:31:48 pm
The one we have says CT100 and then there's a sticker that says it conforms to the CT100-CT101 something or the other that I can't remember off the top of my head now.
We have a CT101 with our software team and the two are more or less identical.
Title: Re: 2gig CT100
Post by: Hoju on November 23, 2014, 10:39:42 pm
Just a quick update to those who own this. I talked to support and sent logs and explained the problem. They said they would be in touch if they needed anything else and I haven't heard back. Hopefully this gets fixed in the next firmware update.
Title: Re: 2gig CT100
Post by: Sushi on January 13, 2015, 04:22:04 pm
Any news on this? I'm getting the "Could not connect, please try again" message whenever I try to change the Heating temperature.

Thanks,
Scott B.
Title: Re: 2gig CT100
Post by: thechadly on January 13, 2015, 09:53:15 pm
I haven't checked on this in awhile. Sorry everyone is having issues but I'm a little glad that I'm not the only one. Has anyone had any luck with this?
Title: Re: 2gig CT100
Post by: LGNilsson on January 13, 2015, 10:08:50 pm
As mentioned, we're getting a CT100 to test, but our CEO will be bringing it back from the US in a couple of weeks, as we weren't able to get it delivered in time before I headed back from CES.
Title: Re: 2gig CT100
Post by: loon3 on January 24, 2015, 12:04:13 pm
Just checking back in, looks like I'm in the same boat with the slightly different model from Amazon.

Have you gotten your hands on one yet?  I'd love to finally get this working.
Title: Re: 2gig CT100
Post by: Hoju on February 12, 2015, 10:53:48 am
Hi Lars,

I just wanted to double check if the heat function was fixed in this firmware and if so do we have to remove and add the thermostat to get it working.

thanks
Title: Re: 2gig CT100
Post by: LGNilsson on February 12, 2015, 11:44:29 am
I don't think so, but I know they made some changes for the CT-30, so it might be worth a try. I don't know if you have to remove and add it again for this to work or not.
Title: Re: 2gig CT100
Post by: thechadly on February 12, 2015, 05:48:34 pm
I just installed the new update. I still have the same problem with my CT100.
Title: Re: 2gig CT100
Post by: revoman on February 14, 2015, 11:51:26 am
I just got around to connecting my Amazon purchased 2gig CT100 Thermostat to my Almond +.  I was unable to determine if I should use the "SetPointThermostat" or "Thermostat" option.  So I tried "Thermostat".  It almost works, but here are my findings.

My Almond+ is on the newest firmware ("Software Version : AP2-R070-L009-W016-ZW016-ZB005")
I had to push the "Reset" button on the thermostat (located in the upper compartment by the hvac wires) to access the "Radio Mate" option. 
Because its winter here in Utah the thermostat was set to "Heat" mode. 
The CT100 successfully paired with my Almond+.
The Almond+, the WebApp and the Android App all display the correct temperature, Mode, Fan Mode, "Cool" setpoint, idle status's and Battery %.
When the mode is in "Auto" or "Cool" I can activate the Air Conditioner by changing the "Cool" temperature, from all 3 apps.

My issue is I am unable to change the temperature while in "Heat".  All attempts failed the Almond+, the WebApp and the Android Mobile app.   :'( 

The behavior from the Android app is this".  I change the "Heat" temperature from 35 degrees F to 70.  I get a message saying "Updating sensor data.  Please wait."  Between 20 and 30 seconds later the app displays the error "Could not connect, please try again.".  However, if I change the "Cool" slider it correctly sets the "Low" temperature setting in the app. 


Here is the extract from my System Log for the time period of a heat change request.
Code: [Select]
Feb 14 09:45:01 AlmondPlus daemon.info dnsmasq-dhcp[6840]: DHCPINFORM(br-lan) 10.10.10.151 bc:5f:f4:5a:77:57
Feb 14 09:45:01 AlmondPlus daemon.info dnsmasq-dhcp[6840]: DHCPACK(br-lan) 10.10.10.151 bc:5f:f4:5a:77:57 Zippy
Feb 14 09:45:06 AlmondPlus kern.warn kernel: FWLOG: [38343218] WAL_DBGID_TX_BA_SETUP ( 0x436004, 0x6, 0x0, 0x2, 0x0 )
Feb 14 09:45:08 AlmondPlus kern.warn kernel: FWLOG: [38344823] WAL_DBGID_TX_BA_SETUP ( 0x436004, 0x6, 0x20d, 0x40, 0x1 )
Feb 14 09:45:16 AlmondPlus kern.warn kernel: FWLOG: [38352802] WAL_DBGID_TX_BA_SETUP ( 0x436004, 0x6, 0x0, 0x2, 0x0 )
Feb 14 09:45:18 AlmondPlus kern.warn kernel: FWLOG: [38355097] WAL_DBGID_TX_BA_SETUP ( 0x436004, 0x6, 0x20e, 0x40, 0x1 )
Feb 14 09:45:25 AlmondPlus kern.warn kernel: FWLOG: [38362385] WAL_DBGID_TX_BA_SETUP ( 0x436004, 0x6, 0x0, 0x2, 0x0 )
Feb 14 09:45:28 AlmondPlus kern.warn kernel: FWLOG: [38365369] WAL_DBGID_TX_BA_SETUP ( 0x436004, 0x6, 0x20f, 0x40, 0x1 )
Feb 14 09:45:44 AlmondPlus kern.warn kernel: FWLOG: [38381552] WAL_DBGID_TX_BA_SETUP ( 0x436004, 0x6, 0x0, 0x2, 0x0 )
Feb 14 09:45:48 AlmondPlus kern.warn kernel: FWLOG: [38385934] WAL_DBGID_TX_BA_SETUP ( 0x436004, 0x6, 0x212, 0x40, 0x1 )
Feb 14 09:45:53 AlmondPlus kern.warn kernel: FWLOG: [38391135] WAL_DBGID_TX_BA_SETUP ( 0x436004, 0x6, 0x0, 0x2, 0x0 )
Feb 14 09:45:55 AlmondPlus user.info sysinit: RECV Membership query   from 10.10.10.254    to 224.0.0.1
Feb 14 09:45:55 AlmondPlus user.info sysinit: RECV V2 member report   from 10.10.10.153    to 239.255.255.250
Feb 14 09:45:55 AlmondPlus user.info sysinit: Updated route entry for 239.255.255.250 on VIF #1
Feb 14 09:45:55 AlmondPlus user.info sysinit: The source address 10.10.10.153 for group 239.255.255.250, is not in any valid net for upstream VIF.
Feb 14 09:45:56 AlmondPlus user.info sysinit: RECV V2 member report   from 10.10.10.254    to 224.0.0.2
Feb 14 09:45:56 AlmondPlus user.info sysinit: The IGMP message was from myself. Ignoring.
Feb 14 09:45:58 AlmondPlus kern.warn kernel: FWLOG: [38396215] WAL_DBGID_TX_BA_SETUP ( 0x436004, 0x6, 0x213, 0x40, 0x1 )
Feb 14 09:46:30 AlmondPlus user.info sysinit: The source address 10.10.10.153 for group 239.255.255.250, is not in any valid net for upstream VIF.

And the Kernel Log
Code: [Select]
FWLOG: [38509285] WAL_DBGID_TX_BA_SETUP ( 0x436004, 0x6, 0x221, 0x40, 0x1 )
FWLOG: [38515718] WAL_DBGID_TX_BA_SETUP ( 0x436004, 0x6, 0x0, 0x2, 0x0 )
FWLOG: [38519566] WAL_DBGID_TX_BA_SETUP ( 0x436004, 0x6, 0x222, 0x40, 0x1 )

Any help is greatly appreciated.
Title: Re: 2gig CT100
Post by: Sushi on February 26, 2015, 08:54:23 am
@revoman- Nice work describing the problem! Exact same issues I have as well...
Title: Re: 2gig CT100
Post by: lucasrangit on February 28, 2015, 10:16:00 pm
I have similar issues with my 2gig CT100 Z-Wave Programmable Thermostat, purchased from NewEgg.com http://www.newegg.com/Product/Product.aspx?Item=N82E16881169015.


What has worked.
Title: Re: 2gig CT100
Post by: utrph77004 on March 12, 2015, 11:20:58 pm
I have 2 of these thermostats in my house. I've updated my A+ to the latest firmware, and I have the same issue as others reported here. Cannot control heat temp.  Gives error message: unable to connect.

I bought both of mine from Amazon.com as well.

http://www.amazon.com/2gig-CT100-Z-Wave-Programmable-Thermostat/dp/B008CQ4V3Q/ref=sr_1_1?ie=UTF8&qid=1426216787&sr=8-1&keywords=2gig+ct100
Title: Re: 2gig CT100
Post by: mrvw67 on March 16, 2015, 10:36:27 pm
I also just got my Almond+ in today and connected a 2GIG-Z-CT100 to it for the first time. Same behavior as other have posted. "Heat up to" doesn't show a value. If you try to change it from the Web UI it sits for about 4 seconds and then says "Please Refresh & Retry" Currently running FW "AP2-R070as-L009-W016-ZW016-ZB005-BETA"
Title: Re: 2gig CT100
Post by: grouter on March 18, 2015, 12:27:59 pm
>> It doesn't work from the LCD. It also doesn't work from the Android App. The cool setting works fine. It just will not let me change the heat setting from 35 degrees.

I have the same issues when using an Amazon version of the CT100. Heat temp reverts back to 35 degrees.

Thanks
Title: Re: 2gig CT100
Post by: grouter on March 18, 2015, 12:58:02 pm
Using the Android app, when I change the heat slider it says "Updating sensor data. Please wait." and it takes a while and reverts back to 35 degrees and gives a "Could not connect, please try again" error.

Changing the cool slider causes it to refresh data and it does so quickly and saves the new cool temp I set.

Using the LCD GUI, the heat slider set temp keeps reverting/disappearing. Same results on the connect.securifi.com website.

Otherwise, the android app and connect website are correctly reporting the thermostat mode is on heat, fan mode/status, current temp and battery level.

Thanks
Title: Re: 2gig CT100
Post by: grouter on March 20, 2015, 09:24:33 am
A few more things I noticed...

The android app alerts when someone changes the set temp manually on the thermostat, but it reports the room temp instead of the set temp.

Also, the cooling set temp is labeled LO instead of HI  The heat set temp should be the low value.

Thanks


Title: Re: 2gig CT100
Post by: varundev on March 22, 2015, 01:42:46 am
First off, I don't have one of these.  As I was working on something else, I happened to read on the web or this forum somewhere that this was a product ID issue.  The person fixed it by updating the manufacturer_specific.xml file.  They added the following line :

<Product type="6401" id="0107" name="CT100 Thermostat" config="2gig/ct100.xml"/>

To verify the product ID, SSH into the Almond+ and look at the zwcfg_home.xml file to get the product ID.  Here is an excerpt from mine for another device.

 <Node id="17" name="" location="" basic="4" generic="7" specific="1" type="Routing Slave" listening="false" frequentListening="false" beaming="true" routing="true" max_baud_rate="40000" version="4" security="false" query_stage="Complete">
                <Manufacturer id="0086" name="Aeon Labs">
                        <Product type="0102" id="0059" name="Recessed Door Sensor" />

You need the Product type and id from the last line above to enter into the manufacturer_specific.xml file in /almond/config.

I am by no means an expert and don't take any responsibility for damage that may occur.  I haven't even been able to get my device working.  The easiest way to get this without looking through the whole file is to remove and add the thermostat.  That way it's the last Node in the file.  Good luck and if someone does this, let me know if it worked.

Title: Re: 2gig CT100
Post by: grouter on March 22, 2015, 09:57:54 am
I'm looking in /almond/zwcfg_home.xml and only see one node, which looks to be the Almond+ itself.

Code: [Select]
        <Node id="1" name="" location="" basic="2" generic="2" specific="7" type="Gateway" listening="true" frequentListening="false" beaming="true" routing="false" max_baud_rate="40000" version="4" security="false" query_stage="Complete">
                <Manufacturer id="0182" name="Securifi">
                        <Product type="0001" id="0001" name="Almond+" />
                </Manufacturer>

I have three sensors connected.
Title: Re: 2gig CT100
Post by: grouter on March 22, 2015, 10:52:08 am
Here are some links to a z-wave device DB. Found some posts on the CT30 and the entry for this device seems to be complete. The info on the CT100 is lacking and I'm not sure how accurate it is:

http://www.pepper1.net/zwavedb/device?sort=name&sort_type=desc&filter_cmd_class=&filter_frequency=&filter_language=&filter_manufacturer=137&filter_generic_class=18

http://www.pepper1.net/zwavedb/device/289

I tried various device IDs and such but no luck...

Thanks
Title: Re: 2gig CT100
Post by: varundev on March 22, 2015, 11:14:06 am
I'm looking in /almond/zwcfg_home.xml and only see one node, which looks to be the Almond+ itself.

Code: [Select]
        <Node id="1" name="" location="" basic="2" generic="2" specific="7" type="Gateway" listening="true" frequentListening="false" beaming="true" routing="false" max_baud_rate="40000" version="4" security="false" query_stage="Complete">
                <Manufacturer id="0182" name="Securifi">
                        <Product type="0001" id="0001" name="Almond+" />
                </Manufacturer>

I have three sensors connected.


I think you need to look in /hadata/apps/hadata-4c09.  There is another zwcfg_home.xml in there that seems to be more complete than the one in /almond.  I also found a copy in /tmp.

This is exactly why we need some high level documentation on how the Almond+ works so that we can make updates to the Almond+ files get our own devices working outside of the Securifi Software team.
Title: Re: 2gig CT100 FIXED
Post by: grouter on March 22, 2015, 11:43:52 am
Thanks, that's where the sensors live, and the CT100's heat is now working.

First, I changed the following in /hadata/apps/hadata-4c09/zwcfg_home.xml

                <Manufacturer id="0098" name="2GIG Technologies">
                        <Product type="6401" id="0107" name="Unknown: type=6401, id=0107" />
                </Manufacturer>

to...
                <Manufacturer id="0098" name="2GIG Technologies">
                        <Product type="6401" id="0107" name="CT100 Thermostat" />
                </Manufacturer>

and added a line in /almond/config/manufacturer_specifc.xml:

        <Manufacturer id="0098" name="2GIG Technologies">
                <Product type="1e12" id="015c" name="CT30 Thermostat" config="2gig/ct30.xml"/>
                <Product type="1e12" id="015e" name="CT30 Thermostat" config="2gig/ct100.xml"/>
                <Product type="6401" id="0105" name="CT100 Thermostat" config="2gig/ct100.xml"/>
                <Product type="6401" id="0107" name="CT100 Thermostat" config="2gig/ct100.xml"/>
                <Product type="6501" id="000b" name="CT100 Thermostat" config="2gig/ct100.xml"/>
                <Product type="6501" id="000c" name="CT100 Thermostat" config="2gig/ct100.xml"/>
                <Product type="0000" id="0000" name="CT100 Thermostat" config="2gig/ct100.xml"/>
        </Manufacturer>

And then rebooted.  Heat's working...

On the Android app and connect.securifi.com GUIs, "LO" still shows the cooling set point and "HI" still shows the heat set point--and I think these should be reversed--but I'm happy with some functional heat at this point!
Title: Re: 2gig CT100 FIXED
Post by: grouter on March 22, 2015, 12:22:59 pm
On the Android app and connect.securifi.com GUIs, "LO" still shows the cooling set point and "HI" still shows the heat set point--and I think these should be reversed--but I'm happy with some functional heat at this point!

LO and HI is also reported this way on the 10.10.10.254 GUI. I suppose that instead of LO and HI that if it said COOL and HEAT it would be correct.

Prior to my changes, all GUIs (except the LCD) showed the current room temp exactly as was reported on the thermostat, down to the 0.5 degree. Since I made the changes the room temp no longer updates as frequently on all GUIs. It is updating, just not very frequently and the Android app no longer reports any half degrees. However, the Android app's notification log does still report the .5 degree changes.

I'll fiddle some more later...

Thanks
Title: Re: 2gig CT100
Post by: varundev on March 22, 2015, 02:19:13 pm
Great!  Keep us posted.

Now if I could just get my sensors to work...
Title: Re: 2gig CT100
Post by: mobelos on March 22, 2015, 08:30:30 pm
I have one of the CT-100 purchased from Amazon and one from Lowes.  The Lowes one works great. The Amazon one has the heat issue.  I just tried the changes and it still does not operate.  Only wish it did.  Might have to try and get another Lowes one if this problem persists.  Any ideas anyone? :-\
Title: Re: 2gig CT100
Post by: varundev on March 22, 2015, 10:10:50 pm
Did you look at the logs and get the Product ID for your device instead of using the one above?
Title: Re: 2gig CT100
Post by: grouter on March 23, 2015, 12:41:44 am
Did you edit a line or add one in /almond/config/manufacturer_specifc.xml?

Other than that, all I can think of that would break things is, in the file with your connected sensors, editing the wrong sensor.

I haven't tried it yet, but seems that if the correct ID is in /almond/config/manufacturer_specifc.xml you could remove the sensor from the almond, start the reconnect process on the thermostat, and add it back and the almond would detect the device correctly from the start.
Title: Re: 2gig CT100 FIXED
Post by: LGNilsson on March 23, 2015, 02:18:57 am
Thanks, that's where the sensors live, and the CT100's heat is now working.

First, I changed the following in /hadata/apps/hadata-4c09/zwcfg_home.xml

                <Manufacturer id="0098" name="2GIG Technologies">
                        <Product type="6401" id="0107" name="Unknown: type=6401, id=0107" />
                </Manufacturer>

to...
                <Manufacturer id="0098" name="2GIG Technologies">
                        <Product type="6401" id="0107" name="CT100 Thermostat" />
                </Manufacturer>

and added a line in /almond/config/manufacturer_specifc.xml:

        <Manufacturer id="0098" name="2GIG Technologies">
                <Product type="1e12" id="015c" name="CT30 Thermostat" config="2gig/ct30.xml"/>
                <Product type="1e12" id="015e" name="CT30 Thermostat" config="2gig/ct100.xml"/>
                <Product type="6401" id="0105" name="CT100 Thermostat" config="2gig/ct100.xml"/>
                <Product type="6401" id="0107" name="CT100 Thermostat" config="2gig/ct100.xml"/>
                <Product type="6501" id="000b" name="CT100 Thermostat" config="2gig/ct100.xml"/>
                <Product type="6501" id="000c" name="CT100 Thermostat" config="2gig/ct100.xml"/>
                <Product type="0000" id="0000" name="CT100 Thermostat" config="2gig/ct100.xml"/>
        </Manufacturer>

And then rebooted.  Heat's working...

On the Android app and connect.securifi.com GUIs, "LO" still shows the cooling set point and "HI" still shows the heat set point--and I think these should be reversed--but I'm happy with some functional heat at this point!

Thanks for the help, I've asked the software team to implement this. It won't be in the next release firmware, as we're already in a release candidate stage with that one, but I expect that it'll be done for the one after that.
Title: Re: 2gig CT100
Post by: mobelos on March 23, 2015, 10:42:18 am
I added the line.  I really appreciate the responses.  I will try and to un-pair then pair it again and see what happens.
Title: Re: 2gig CT100
Post by: grouter on March 23, 2015, 10:54:24 am
Regarding LO and HI...

Seems that these set points should just be renamed to COOL and HEAT. Reversing them as I suggested earlier won't work for everyone as some people keep their temps dramatically different from my settings.

Thanks
Title: Re: 2gig CT100
Post by: mobelos on March 23, 2015, 11:05:45 am
We are go! Un-paired and re-paired it and everything works now.  I think your assumption works which makes me think.  If you just added the line to the /almond/config/manufacturer_specifc.xml. Then re-paired the device it should work for most people.  Thanks for all the help @grouter and @varundev.  So pumped that all my devices are now working well except my garage door opener but Lars said that will be in an upcoming update.  Have a couple more sensors coming this week to play with including my first dimmer switch.    :D
Title: Re: 2gig CT100
Post by: grouter on March 23, 2015, 06:24:30 pm
Yup, looks like that will work.

I initiated the unlink from the thermostat and it was removed from the Almond+. Followed that by adding, selected Thermostat when prompted on the A+, and it joined again and has working heat from the start. So it just looks like a missing device ID.
Title: Re: 2gig CT100
Post by: grouter on March 24, 2015, 03:08:08 pm
I have noticed that the Android app and web GUIs report incorrectly that the heat is on and the fan is running. However, changing the heat set temp and mode on/off do work properly.

Thanks
Title: Re: 2gig CT100
Post by: grouter on March 24, 2015, 08:20:07 pm
I have noticed that the Android app and web GUIs report incorrectly that the heat is on and the fan is running.

Maybe they just take a long time to update those variables. Setting the temp and mode are instantly issued and recognized.
Title: Re: 2gig CT100
Post by: grouter on April 01, 2015, 04:43:09 pm
I upgraded to R072 the other day and saw some strange behavior with the Amazon CT100. A little digging showed that my thermostat's Product ID didn't make it into the firmware release--the entry I made previously was no longer there. I unpaired, added back the following line and re-paired and everything's fine.

in /almond/config/manufacturer_specifc.xml:

        <Manufacturer id="0098" name="2GIG Technologies">
                <Product type="1e12" id="015c" name="CT30 Thermostat" config="2gig/ct30.xml"/>
                <Product type="1e12" id="015e" name="CT30 Thermostat" config="2gig/ct100.xml"/>
                <Product type="6401" id="0105" name="CT100 Thermostat" config="2gig/ct100.xml"/>
                <Product type="6401" id="0107" name="CT100 Thermostat" config="2gig/ct100.xml"/>
                <Product type="6501" id="000b" name="CT100 Thermostat" config="2gig/ct100.xml"/>
                <Product type="6501" id="000c" name="CT100 Thermostat" config="2gig/ct100.xml"/>
                <Product type="0000" id="0000" name="CT100 Thermostat" config="2gig/ct100.xml"/>
        </Manufacturer>

/hadata/apps/hadata-4c09/zwcfg_home.xml still showed id="0107" after re-pairing.

                <Manufacturer id="0098" name="2GIG Technologies">
                        <Product type="6401" id="0107" name="CT100 Thermostat" />
                </Manufacturer>

Maybe this will make it into the next release??
Title: Re: 2gig CT100
Post by: Automate on April 05, 2015, 03:11:07 pm

This is exactly why we need some high level documentation on how the Almond+ works so that e can make updates to the Almond+ files get our own devices working outside of the Securifi Software team.
+1
Title: Re: 2gig CT100 FIXED
Post by: eyesack on April 25, 2015, 03:11:32 pm
Thanks for the help, I've asked the software team to implement this. It won't be in the next release firmware, as we're already in a release candidate stage with that one, but I expect that it'll be done for the one after that.

Lars - this is a very crucial fix. I cannot imagine that the majority of your end-users have the expertise to perform this fix, and will quite simply give up on using the Almond interface/app altogether. Is there anything you or the Securifi team can do to escalate this as a patch?
Title: Re: 2gig CT100
Post by: LGNilsson on April 27, 2015, 02:33:39 am
Patch, no, but I've reminded the Z-Wave device support developer to add this again for the next firmware release.
Title: Re: 2gig CT100
Post by: grouter on May 01, 2015, 09:57:53 pm
I found this page that shows four CT100 revisions. Unfortunately, they don't provide any device ID numbers for them, just revision numbers. So, looks like there are a few more to add to the A+...

http://products.z-wavealliance.org/regions/2/categories/10/products?company=136
Title: Re: 2gig CT100
Post by: Hoju on May 28, 2015, 09:56:04 am
Has anyone tried the amazon purchased CT100 after updating to R076? I haven't updated yet but was wondering if this is fixed now (furnace is off till winter now)?
Title: Re: 2gig CT100
Post by: grouter on May 28, 2015, 10:00:04 am
I just upgraded to R076 and can't tell that anything changed for the CT100.

Everything works for me except the statuses in the Android app don't properly update.

Heating, cooling and auto modes work as well as fan control.
Title: Re: 2gig CT100
Post by: Hoju on September 18, 2015, 09:47:57 pm
Just wondering if things are working as they should for people with out having to change anything on the almond+. I removed and added the thermo but atill cant set the heat through the ios app or touchscreen.
Title: Re: 2gig CT100
Post by: grouter on September 19, 2015, 06:47:03 pm
Just wondering if things are working as they should for people with out having to change anything on the almond+. I removed and added the thermo but atill cant set the heat through the ios app or touchscreen.

Heat has been working for me from the start (January). I'm using the Android app, though... I've never tried the touch screen to adjust temps.