yvg240 Posted January 23, 2016 Posted January 23, 2016 I've been using ISY and Insteon for 6 years now. Totally new to z wave and having trouble understanding how to adjust the wake up time. I noticed that while adding the multisensor that the isy is setting a 3600 second wake up time. This is reflected in the log as I am only getting temperature readings once every hour. The device has a minimum wake up time of 4 minutes. I would like to reduce the wake up time to 10 minutes or so realizing that this will have an effect on battery life. Does anyone know how to do this?
MWareman Posted January 23, 2016 Posted January 23, 2016 I don't think ISY is setting it - I think that's just a device default. Like all zwave devices - the device has numbered parameters. The ISY can set them - but which parameter does what is up to the device vendor. You'll need to find the zwave parameter that the Aeotec Multisensor uses for wake up time, and set it to the value you want. I have one of these - I should probably research it myself... (Though I currently use it powered)
MWareman Posted January 23, 2016 Posted January 23, 2016 Actually - the parameter is in the manual... Parameter 111-113 [4 byte decimal] can be configured through your gateway in case the default settings of your MultiSensor are not what you desire. Parameter 111 will set the interval for Group 1 (parameter 101), parameter 112 will set the interval for Group 2 (parameter 102), and parameter 113 will set the interval for Group 3 (parameter 103). As an example, you have set parameter 101 to 241 which will report all of the sensors, and you want to report it every 1800 seconds. Set parameter 111 to 1800 to accomplish this http://products.z-wavealliance.org/MarketCertification/File?folder=&filename=MarketCertificationFiles/1390/MultiSensor%206%20manual%20(3).pdf
MWareman Posted January 23, 2016 Posted January 23, 2016 Right click the device, select 'Z-Wave' 'Set Configuration Parameter' to access the dialog to do this.
yvg240 Posted January 23, 2016 Author Posted January 23, 2016 Wow thanks for the quick response. I have changed it to 600. One of the things that seems inconsistent is the ability to query the settings. Maybe because the ISY is configured to put the device back to sleep? So when I wake it up I get a successful query. But then it seems the device immediately goes back to sleep. Do you understand the parameter size value? I am seeing 1,2,4 and seems to default to 4 when querying the value.
MWareman Posted January 24, 2016 Posted January 24, 2016 Wow thanks for the quick response. I have changed it to 600. One of the things that seems inconsistent is the ability to query the settings. Maybe because the ISY is configured to put the device back to sleep? So when I wake it up I get a successful query. But then it seems the device immediately goes back to sleep. Do you understand the parameter size value? I am seeing 1,2,4 and seems to default to 4 when querying the value. Devices have slots to store data (I believe 255 bytes - but I'm not sure..). Each device is 1,2 or 4 bytes (depending on the manufacturer's functional definition for the parameter). If parameter 1 is defined as a 2 byte parameter - there isn't a parameter 2 (since that's the second byte of parameter 1). If you write something to parameter 2 you'll actually change the function assigned to parameter 1. Some manufacturers tell you what to change to do what. Many are pretty quiet on the function. As far as waking it - most devices *should* support something called 'beam-forming'. This allows a controller to wake a device for sending commands and querying the device. You shouldn't have to wake a zwave device like you do battery powered Insteon devices. However, the success of beam-forming is conditional on having a strong mesh - and devices good at performing the function. Many of us here have had great success with plugging in a few Aeotec Sirens (using them as repeaters) - since they seem to help with this. THey even properly relay secure messages (and the multi-sensor 6 is a dual-mode device - it can be enrolled secure or non-secure). It could simply be that ISY cannot talk directly to the device (using an intermediate device to communicate) - and if the intermediate device does not support beam-forming you won't be able to wake it. You should probably map your zwave network - document which device can see (and talk) to which other devices - and their capabilities... You can do this by viewing the event log and the various options on the zwave menu when you right-click a zwave device. It really helps to diagnose communication issues.
fryfrog Posted January 25, 2016 Posted January 25, 2016 Many of us here have had great success with plugging in a few Aeotec Sirens (using them as repeaters) - since they seem to help with this. THey even properly relay secure messages (and the multi-sensor 6 is a dual-mode device - it can be enrolled secure or non-secure). If you *can* power your multi sensor via usb instead of battery *and* you pair it in secure mode while powered by usb, it'll act as a secure repeater. I recently added a handful of them to my zwave network that was originally just some locks, a thermostat and a siren or two (they ended up powered off for various reasons) and my zwave network went from unreliable as hell to awesome. The multisensor is my new favorite "repeater" since they're pretty cheap and they're far more useful than a siren.
MWareman Posted January 25, 2016 Posted January 25, 2016 Good to know - thanks! I have a few multisensors awaiting install - I suspect I better get on that.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.