05-24-2017, 08:46 PM
(This post was last modified: 05-24-2017, 08:52 PM by Dean Roddey.)
How long has it been? It will be something like 8 minutes before the next wakeup. It may not do an actual wakeup transmission until then or until maybe you do the batteries. You should see another entry in the logs that says it got a wake up and sent out the queued up messages when that happens.
Once that is done, the motion sensor should send out a notification any time the motion state changes. So that one should show up correctly immediately. The others will take a while. That's not done as a wakeup up, but it just wakes up every so often and sends those values out. I think the auto-config sets it to 8 minutes. Until that happens though, I think the default value is quite a long time.
Not sure about the field name error. I'm assuming it's showing up under the correct name in the client interface and that the Save button is greyed out?
In the driver monitor tab (where you are setting the field) does it show up there under the right name?
Once that is done, the motion sensor should send out a notification any time the motion state changes. So that one should show up correctly immediately. The others will take a while. That's not done as a wakeup up, but it just wakes up every so often and sends those values out. I think the auto-config sets it to 8 minutes. Until that happens though, I think the default value is quite a long time.
Not sure about the field name error. I'm assuming it's showing up under the correct name in the client interface and that the Save button is greyed out?
In the driver monitor tab (where you are setting the field) does it show up there under the right name?
Dean Roddey
Explorans limites defectum
Explorans limites defectum