I had a similar issue. You need to take Incontrol Offline and Online again and it should work as expected after that.
Version 3.88 ALPHA: Multi-channel and preserved virtual device state
- 335 Views
- Last Post 11 May 2014
Ryan-Scott
posted this
29 January 2014
gmerin
posted this
11 May 2014
.
Ralf
posted this
08 April 2014
Creating a custom virtual device for temperature ignores the decimal value. So 16.8 degrees is reported in the GUI (phone and console) as 16 only. If you query the value programmatically (eg command line call) its OK.
n0vtn
posted this
26 March 2014
I am running 3.97 as of today and had been running 3.96 as of one day last week.
I have suddenly been having more difficulty than usual with my Honeywell Thermostat.
I can no longer set the temperature via Z-Wave. It defaults to the schedule setting.
I won't go into detail as to why I have both the Z-Wave and the schedule running unless someone asks.
The thermostat is happily reporting numerous values for heating1, energy heat, energy cool, and current temperature. I have tried changing the setting via my primary controller, secondary controller, via scene, via the device, via my iPhone app and via my Android app, all without success.
I can't be sure where the problem is. Most likely it is just that the thermostat itself has become even more difficult to live with, but it might be related to the upgrades to the InControl software I have been applying to the systems. With that in mind I thought it might be best to report the trouble here.
As a side note on my primary InControl PC the primary Z-Stick is reporting Temperature and Lumenance. It started reporting those values on 3.96 and continues to report them on 3.97. It tells me the temperature is 475 F.
ftsikogi
posted this
20 March 2014
I had a similar issue. You need to take Incontrol Offline and Online again and it should work as expected after that.
catboxer
posted this
19 March 2014
I'm having a strange problem with the Alpha were I've unchecked the "enabled" box for a scene and yet it keeps running away. It's a light that I had coming on at 7pm. I didn't delete the scene, just unchecked the enabled box, and it's still turning on at that time.
Ralf
posted this
11 March 2014
P.S. If you run this version, please let us know by replying here so that we can get a tally of who is using it.
Just a heads up that I tried the latest Alpha. It seems to work fine although I can't test multi-channel. The only problem I encountered was that the device auto-config option didn't work when I tried to add a motion sensor to my network. When I reverted back to the previous official version, it worked fine. I raised an official ticket for this issue.
Cheers.
Axial-User
posted this
09 March 2014
I have tried Version 3.95.1 RC (release 10) and the option to mark the device as off or unreachable when the power source is disconnected is still not working. The device still shows as ON even though there is no power on it. This really affects the scenes that depends on the status of the device. Version 3.62 works just fine. I would like to know if this is a bug or this option has been removed
Ryan-Scott
posted this
05 March 2014
Cloud support is still not being disabled with a blank username and PW. I am on release 8 3.91.xxx and I have set it to blank and it shows connected to cloud in the Incontrol software and my phone can also connect only by cloud.
The latest version should address this. It actually is disabled, but the icon doesn't update to show accurately until version 3.95.
jjbauer
posted this
23 February 2014
I just upgraded to the new version. I love having the option to make a device a fan. However, my iPhone app doesn't have an option for a fan yet. When will that be updated?
catboxer
posted this
21 February 2014
Cloud support is still not being disabled with a blank username and PW. I am on release 8 3.91.xxx and I have set it to blank and it shows connected to cloud in the Incontrol software and my phone can also connect only by cloud.
Axial-User
posted this
21 February 2014
After installing Version 3.92 RC (release 9) Incontrol no longer detects that the device is down after the device misses several polls. This option was introduced in earlier version to detect that the device is down when the power source is disconnected.
Mwyrick
posted this
18 February 2014
Using 3.91.5156.15004
Alarm is set as a DimmerSwitch.
I have a scene called EMail on Arm with a Trigger of "Alarm change to level 33". In the log I have:
2/18/2014 5:59:42 PM: SceneTrigger EMail on Arm: Object reference not set to an instance of an object.
I have found it seems to ignore the "to level 33" section of the trigger. I have a few scenes that should happen at different levels but they all get triggered on any change of the device. Each one will show the above error in the log file. I have to put a condition on the scenes to check the device level to get the desired affect.
- Michael
After looking into it and debugging the pre-script the Error is happing on the sendemail() call. That does not change that the trigger change to level does not seem to look at the level.
Mwyrick
posted this
18 February 2014
Using 3.91.5156.15004
Alarm is set as a DimmerSwitch.
I have a scene called EMail on Arm with a Trigger of "Alarm change to level 33". In the log I have:
2/18/2014 5:59:42 PM: SceneTrigger EMail on Arm: Object reference not set to an instance of an object.
I have found it seems to ignore the "to level 33" section of the trigger. I have a few scenes that should happen at different levels but they all get triggered on any change of the device. Each one will show the above error in the log file. I have to put a condition on the scenes to check the device level to get the desired affect.
- Michael
Ryan-Scott
posted this
18 February 2014
My Multi-sensors are nodes 3, 13, 24, 25, and 26. The short Id's are 20, 30, 46, 50 and 51.
You raise and issue I failed to mention in my original post.
Sometimes when I click on associations they are associated with the controller other times they are not. All of these Multi-Sensors are USB powered (no batteries) so if I am reading the manual correctly they should always be awake. I have checked the association box for the controller and I have auto configured still sometimes when I look they are not associated.
The behavior you describe is common for devices that are outside of optimal communication range with the USB stick. You could try to move it closer... if it's already close, you might try uninstalling the current RC build and installing the official release to see if there's any difference in behavior.
n0vtn
posted this
17 February 2014
My Multi-sensors are nodes 3, 13, 24, 25, and 26. The short Id's are 20, 30, 46, 50 and 51.
You raise and issue I failed to mention in my original post.
Sometimes when I click on associations they are associated with the controller other times they are not. All of these Multi-Sensors are USB powered (no batteries) so if I am reading the manual correctly they should always be awake. I have checked the association box for the controller and I have auto configured still sometimes when I look they are not associated.
Ryan-Scott
posted this
17 February 2014
I'm not seeing any reports in that snipped of text you provided. I do see some reports, but those are most likely temperature/humidity and luminosity reports. If I'm reading this correctly, it looks like node 49 is doing the reporting here - is that one of your sensors?
Just to be sure, have you verified that the sensor is indeed associated with the USB stick (click sensor, wake it up, click associations, check USB stick device)?
n0vtn
posted this
17 February 2014
Where in the Zen Tools do I find this information?
Does it keep a log somewhere? I am not finding any sort of real time monitor.
Yes, once you've connected to your USB stick there's a log in the lower right hand portion of the screen. Here's how mine looks: http://snag.gy/4WkPk.jpg
My Log looks a little different but I am not seeing any indication of motion. Also I can't tell which of the 5 Multi Sensors are reporting in.
See Below:
01:50:21.705: SecurityManager.Init 60 24 38 46 16 50 74 C4 80 D9 10 A8 30 5B 90 08
01:50:52.783: Received: COMMANDCLASSBATTERY.BATTERYREPORT, hex data: 80 03 64
01:50:53.067: Received: COMMANDCLASSSENSORMULTILEVEL.SENSORMULTILEVELREPORT, hex data: 31 05 03 0A 00 AD
01:50:53.365: Received: COMMANDCLASSSENSORMULTILEVEL.SENSORMULTILEVELREPORT, hex data: 31 05 05 01 1B 00
01:50:53.670: Received: COMMANDCLASSSENSORMULTILEVEL.SENSORMULTILEVELREPORT, hex data: 31 05 01 2A 00 EA
01:53:41.823: Received: COMMANDCLASSBATTERY.BATTERYREPORT, hex data: 80 03 64
01:53:41.885: Received: COMMANDCLASSSENSORMULTILEVEL.SENSORMULTILEVELREPORT, hex data: 31 05 03 0A 03 E8
01:53:41.945: Received: COMMANDCLASSSENSORMULTILEVEL.SENSORMULTILEVELREPORT, hex data: 31 05 05 01 2F 00
01:53:42.006: Received: COMMANDCLASSSENSORMULTILEVEL.SENSORMULTILEVELREPORT, hex data: 31 05 01 2A 01 07
01:54:27.805: Received: COMMANDCLASSBATTERY.BATTERYREPORT, hex data: 80 03 64
01:54:27.993: Received: COMMANDCLASSSENSORMULTILEVEL.SENSORMULTILEVELREPORT, hex data: 31 05 03 0A 03 E8
01:54:28.203: Received: COMMANDCLASSSENSORMULTILEVEL.SENSORMULTILEVELREPORT, hex data: 31 05 05 01 32 00
01:54:28.413: Received: COMMANDCLASSSENSORMULTILEVEL.SENSORMULTILEVELREPORT, hex data: 31 05 01 2A 01 08
01:55:52.720: Received: COMMANDCLASSBATTERY.BATTERYREPORT, hex data: 80 03 64
01:55:52.938: Received: COMMANDCLASSSENSORMULTILEVEL.SENSORMULTILEVELREPORT, hex data: 31 05 03 0A 00 AE
01:55:53.235: Received: COMMANDCLASSSENSORMULTILEVEL.SENSORMULTILEVELREPORT, hex data: 31 05 05 01 1B 00
01:55:53.537: Received: COMMANDCLASSSENSORMULTILEVEL.SENSORMULTILEVELREPORT, hex data: 31 05 01 2A 00 EA
01:58:41.844: Received: COMMANDCLASSBATTERY.BATTERYREPORT, hex data: 80 03 64
01:58:41.904: Received: COMMANDCLASSSENSORMULTILEVEL.SENSORMULTILEVELREPORT, hex data: 31 05 03 0A 03 E8
01:58:42.052: Received: COMMANDCLASSSENSORMULTILEVEL.SENSORMULTILEVELREPORT, hex data: 31 05 05 01 2F 00
01:58:42.115: Received: COMMANDCLASSSENSORMULTILEVEL.SENSORMULTILEVELREPORT, hex data: 31 05 01 2A 01 09
01:59:27.825: Received: COMMANDCLASSBATTERY.BATTERYREPORT, hex data: 80 03 64
01:59:28.013: Received: COMMANDCLASSSENSORMULTILEVEL.SENSORMULTILEVELREPORT, hex data: 31 05 03 0A 03 E8
01:59:28.223: Received: COMMANDCLASSSENSORMULTILEVEL.SENSORMULTILEVELREPORT, hex data: 31 05 05 01 32 00
01:59:28.434: Received: COMMANDCLASSSENSORMULTILEVEL.SENSORMULTILEVELREPORT, hex data: 31 05 01 2A 01 09
02:00:52.740: Received: COMMANDCLASSBATTERY.BATTERYREPORT, hex data: 80 03 64
02:00:52.958: Received: COMMANDCLASSSENSORMULTILEVEL.SENSORMULTILEVELREPORT, hex data: 31 05 03 0A 00 A2
02:00:53.256: Received: COMMANDCLASSSENSORMULTILEVEL.SENSORMULTILEVELREPORT, hex data: 31 05 05 01 1B 00
02:00:53.558: Received: COMMANDCLASSSENSORMULTILEVEL.SENSORMULTILEVELREPORT, hex data: 31 05 01 2A 00 EC
02:03:41.863: Received: COMMANDCLASSBATTERY.BAT
mariusz@gmail.com
posted this
17 February 2014
I am on 3.91 and added a ZCOMBO Smoke Detector. The inclusion worked fine (shows up as "Alarm") but I cannot get it Auto configured or set association. Is there a trick to that? I wake it up by holding the button and inserting batteries but it fails every time.
I could never get mine to wake up by performing that procedure. It seems that once it's included, it'll no longer wake up. I had to use InControl to include my ZCOMBO (from the tools menu), which will let it auto configure at the time of inclusion.
Thanks, that worked. It sent code "12!" while testing is there anything else that is reports?
Ryan-Scott
posted this
17 February 2014
I am on 3.91 and added a ZCOMBO Smoke Detector. The inclusion worked fine (shows up as "Alarm") but I cannot get it Auto configured or set association. Is there a trick to that? I wake it up by holding the button and inserting batteries but it fails every time.
I could never get mine to wake up by performing that procedure. It seems that once it's included, it'll no longer wake up. I had to use InControl to include my ZCOMBO (from the tools menu), which will let it auto configure at the time of inclusion.
mariusz@gmail.com
posted this
17 February 2014
I am on 3.91 and added a ZCOMBO Smoke Detector. The inclusion worked fine (shows up as "Alarm") but I cannot get it Auto configured or set association. Is there a trick to that? I wake it up by holding the button and inserting batteries but it fails every time.
