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.
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 LogFWLOG: [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.