Seems like switching to 'beta controller' did the trick after all.
After restarting the machine, before installing 2.210 i saw the current date/time in the properties
Unfortunately in 2.210 its not working again... after clicking properties i get a pop-up with the notice 'Unable to load details'/'Extended properties are not available for this device'
The writeFileLog command is working just fine... thanks. Would be nice if i could do the same in the RuleLog.
Last communication
- 45 Views
- Last Post 21 February 2013
Axial-User
posted this
20 February 2013
Ryan-Scott
posted this
20 February 2013
When i look at the properties of my devices (switches and dimmers), last communication is allways: 1-1-2000
InControl HA 2.209.4797.12803 updates the status of the devices correctly (for example after i press a switch), so i'm sure there is a more recent communication.
Turning the switch from InControl HA also works just fine, but last communication does not get updates
Are you using the beta controller (tools/options/zwave controller menu)? If I recall correctly, that's the only one that updates the last com date.
Axial-User
posted this
20 February 2013
I did not use the beta controller.
After switching to the beta controller, the 'last comminication' is still the same '1-1-2000' even after switching a devices manualy or thru a scene
Ryan-Scott
posted this
20 February 2013
I did not use the beta controller.
After switching to the beta controller, the 'last comminication' is still the same '1-1-2000' even after switching a devices manualy or thru a scene
Do you poll that device? That date only updates when it receives a communication from it -- so I guess it's not quite named appropriately as it should be "last incoming communication." You might also set it up to be associated to your USB stick so that it'll communicate back to InControl when you turn it on or off at the wall.
By the way, are you using that date for a script or something or is this more of a curiosity?
Axial-User
posted this
20 February 2013
Communication with the device / controller is no problem.
When switching the device itself status is updated (at the default poll interval) every 30 seconds
When changing the device status in InControl HA, the device responses imidiately
But when selecting the devices properties InControl keeps showing 'last communication: 1-1-2000'
Also a 'force poll' does not change this.
So there's nothing wrong with the communication, just the date showed in the devices properties is never getting adjusted.
btw. should i see somthing in the device log? The log for this device (and the other devices) is empty.
I want to know if a device is in a off state for more than a number of minutes in a script, but i did not test if the "stateTracker.timeSinceLastChange" is returning the right result - is it posible to write to the rule log from within a rule script so its easy to add debug info in my scripts.
Ryan-Scott
posted this
20 February 2013
Communication with the device / controller is no problem.
When switching the device itself status is updated (at the default poll interval) every 30 seconds
When changing the device status in InControl HA, the device responses imidiately
But when selecting the devices properties InControl keeps showing 'last communication: 1-1-2000'
Also a 'force poll' does not change this.
So there's nothing wrong with the communication, just the date showed in the devices properties is never getting adjusted.
btw. should i see somthing in the device log? The log for this device (and the other devices) is empty.
I want to know if a device is in a off state for more than a number of minutes in a script, but i did not test if the "stateTracker.timeSinceLastChange" is returning the right result - is it posible to write to the rule log from within a rule script so its easy to add debug info in my scripts.
timeSinceLastChange should be able to tell you accurately, unless that's suffering from the same problem. Let me know and we can did some more.
If you get the latest version of InControl from the forum (this morning it's version 2.210), I've added a new command that'll let you write to the logfile.txt.
writeFileLog("test message");
Will that help with debugging it?
Axial-User
posted this
20 February 2013
Seems like switching to 'beta controller' did the trick after all.
After restarting the machine, before installing 2.210 i saw the current date/time in the properties
Unfortunately in 2.210 its not working again... after clicking properties i get a pop-up with the notice 'Unable to load details'/'Extended properties are not available for this device'
The writeFileLog command is working just fine... thanks. Would be nice if i could do the same in the RuleLog.
Axial-User
posted this
21 February 2013
When switching the device view to list the last communication status is displayed correct
2.210 with beta switch on
