Hi,
I'm a newbie with Z-way and have sofar added a number of lightswitches which works just fine.
I'm running v2.2.0 of z-way software.
Adding a Door/Window sensor (Telldus TZDW-100) didn't work that well.
Inclusion/interview is OK and I can see the sensor in the elements window of the UI and it changes state from off to on when I open the door where it's mounted.
The problem is that I can't build any logic for it, as it's not visible in the scroll lists of the apps.
For example, trying to use Logical rule and use the door sensor as binary condition, it's not in the condition scroll list for selection, I can see all my switches but not this sensor.
Is it a bug or is it just me who don't understand how to build logic with a sensor. What I want to achieve is that when the door is opened a light switch should turn on.
I have this entry in the z-way server logg;
[E] [8083] Callback execution error: TypeError: Cannot read property 'call' of undefined
at ZAutomationAPIWebRequest.ZAutomationWebRequest.handleRequest (automation/WebserverRequestRouter.js:258:40)
at automation/WebserverRequestRouter.js:32:35
at WebServer.document_root (automation/Webserver.js:29:11)
It's beyond my expertise level to understand what this means and if it has any correlation to my sensor problem.
Can someone shed some light on this ?
regards,
Vovven
Problem with Door/Window sensor
-
golaonline
- Posts: 19
- Joined: 16 Dec 2015 21:59
Re: Problem with Door/Window sensor
Hi,
I am almost at the same stage as you Vovven. and I am learning and had no idea about this z-wave/ z-way space.
Can you see if the Interview with the device is complete? I think you can only see if via expert UI. In my case I added a window sensor and interview was not complete and took a long time.
I am able to add this device into a If then sensor and try sending notification email, using the Email&SMS notification app, but no luck so far.
I am not really providing a solution but something that took my significant time yesterday.
I am almost at the same stage as you Vovven. and I am learning and had no idea about this z-wave/ z-way space.
Can you see if the Interview with the device is complete? I think you can only see if via expert UI. In my case I added a window sensor and interview was not complete and took a long time.
I am able to add this device into a If then sensor and try sending notification email, using the Email&SMS notification app, but no luck so far.
I am not really providing a solution but something that took my significant time yesterday.
Re: Problem with Door/Window sensor
The interview is complete and I can see the sensor and it changes state as expected but I can't see/access it in the apps when trying to build a logic based on sensor state.
-
golaonline
- Posts: 19
- Joined: 16 Dec 2015 21:59
Re: Problem with Door/Window sensor
If interview is complete then you should be able to setup a logical workflow, try turning on/off another device on z-wave.
Well, I have made some progress and was able to use If->Then block to turn On or Off a dimmer light based on window sensor state of On of Off.
However I am not able to setup a notification email, i have tried built in Email$SMS Notification, nothing seems to happen and i don't have any idea to troubleshoot it further.
I think I need to use some java script code for email capability, but have not made much progress.
Well, I have made some progress and was able to use If->Then block to turn On or Off a dimmer light based on window sensor state of On of Off.
However I am not able to setup a notification email, i have tried built in Email$SMS Notification, nothing seems to happen and i don't have any idea to troubleshoot it further.
I think I need to use some java script code for email capability, but have not made much progress.
Re: Problem with Door/Window sensor
I reverted back to v2.1.1 and now I can build logic rules with this door sensor.
Everything now works as expected.
My conclusion is that there's a bug in v2.2.0 that prevents this sensor to be included in logical rules.
Is there a special procedure for reporting bugs or is it enough to describe the problem in this forum?
regards,
vovven
Everything now works as expected.
My conclusion is that there's a bug in v2.2.0 that prevents this sensor to be included in logical rules.
Is there a special procedure for reporting bugs or is it enough to describe the problem in this forum?
regards,
vovven
Re: Problem with Door/Window sensor
I have the same problem, judging by just looking in my log. Happens after upgrade to 2.2.0 and only on a restart of the z-way server!
Node 2 and 4 are Aeon Multisonsor 6. Have no ide what to look for to see what drives this errors.
Code: Select all
[2016-01-27 21:08:13.448] [D] [zway] RECEIVED: ( 01 08 00 04 00 02 02 84 07 70 )
[2016-01-27 21:08:13.448] [D] [zway] SENT ACK
[2016-01-27 21:08:13.448] [D] [zway] SETDATA devices.2.data.lastReceived = 0 (0x00000000)
[2016-01-27 21:08:13.448] [I] [zway] Node 2:0 CC Wakeup: Wakeup notification
[2016-01-27 21:08:13.449] [D] [zway] SETDATA devices.2.instances.0.commandClasses.132.data.lastWakeup = 1453925293 (0x56a923ad)
[2016-01-27 21:08:13.449] [D] [zway] SETDATA devices.2.data.isAwake = True
[2016-01-27 21:08:13.449] [D] [zway] SETDATA devices.2.data.lastSend = 3904 (0x00000f40)
[2016-01-27 21:08:13.449] [D] [zway] SETDATA devices.2.data.lastNonceGet = 2904 (0x00000b58)
[2016-01-27 21:08:13.449] [D] [zway] Running wakeup handler for node 2
[2016-01-27 21:08:13.449] [D] [zway] SETDATA devices.2.instances.0.commandClasses.132.data.lastSleep = 1453925293 (0x56a923ad)
[2016-01-27 21:08:13.449] [I] [zway] Node 2:0 CC Wakeup: Send node to sleep
[2016-01-27 21:08:13.450] [I] [zway] Adding job: Wakeup Sleep
[2016-01-27 21:08:13.518] [D] [zway] SENDING (cb 0x02): ( 01 09 00 13 02 02 84 08 05 02 6E )
[2016-01-27 21:08:13.519] [D] [zway] RECEIVED ACK
[2016-01-27 21:08:13.523] [D] [zway] RECEIVED: ( 01 04 01 13 01 E8 )
[2016-01-27 21:08:13.523] [D] [zway] SENT ACK
[2016-01-27 21:08:13.523] [D] [zway] Delivered to Z-Wave stack
[2016-01-27 21:08:13.538] [D] [zway] RECEIVED: ( 01 07 00 13 02 00 00 02 EB )
[2016-01-27 21:08:13.538] [D] [zway] SENT ACK
[2016-01-27 21:08:13.538] [I] [zway] Job 0x13 (Wakeup Sleep): Delivered
[2016-01-27 21:08:13.538] [D] [zway] SETDATA devices.2.data.lastPacketInfo.delivered = True
[2016-01-27 21:08:13.539] [D] [zway] SETDATA devices.2.data.lastPacketInfo.packetLength = 5 (0x00000005)
[2016-01-27 21:08:13.539] [D] [zway] SETDATA devices.2.data.lastPacketInfo.deliveryTime = 14 (0x0000000e)
[2016-01-27 21:08:13.539] [D] [zway] SETDATA devices.2.data.lastPacketInfo = **********
[2016-01-27 21:08:13.539] [D] [zway] SendData Response with callback 0x02 received: received by recipient
[2016-01-27 21:08:13.539] [D] [zway] SETDATA devices.2.data.lastSend = 3913 (0x00000f49)
[2016-01-27 21:08:13.539] [D] [zway] Job 0x13 (Wakeup Sleep): success
[2016-01-27 21:08:13.540] [D] [zway] SETDATA devices.2.data.isAwake = False
[2016-01-27 21:08:13.540] [D] [zway] Sending the queue for node 2 into sleep
[2016-01-27 21:08:13.540] [I] [zway] Removing job: Wakeup Sleep
[2016-01-27 21:08:33.741] [D] [zway] Job 0x13: deleted from queue
[2016-01-27 21:08:35.231] [E] [8083] Callback execution error: TypeError: Cannot read property 'call' of undefined
at ZAutomationAPIWebRequest.ZAutomationWebRequest.handleRequest (automation/WebserverRequestRouter.js:258:40)
at automation/WebserverRequestRouter.js:32:35
at WebServer.document_root (automation/Webserver.js:29:11)
[2016-01-27 21:08:48.865] [E] [8083] Callback execution error: TypeError: Cannot read property 'call' of undefined
at ZAutomationAPIWebRequest.ZAutomationWebRequest.handleRequest (automation/WebserverRequestRouter.js:258:40)
at automation/WebserverRequestRouter.js:32:35
at WebServer.document_root (automation/Webserver.js:29:11)
[2016-01-27 21:09:31.946] [E] [8083] Callback execution error: TypeError: Cannot read property 'call' of undefined
at ZAutomationAPIWebRequest.ZAutomationWebRequest.handleRequest (automation/WebserverRequestRouter.js:258:40)
at automation/WebserverRequestRouter.js:32:35
at WebServer.document_root (automation/Webserver.js:29:11)
[2016-01-27 21:09:41.787] [D] [zway] RECEIVED: ( 01 08 00 04 00 04 02 84 07 76 )
[2016-01-27 21:09:41.788] [D] [zway] SENT ACK
[2016-01-27 21:09:41.788] [D] [zway] SETDATA devices.4.data.lastReceived = 0 (0x00000000)
[2016-01-27 21:09:41.788] [I] [zway] Node 4:0 CC Wakeup: Wakeup notification
[2016-01-27 21:09:41.788] [D] [zway] SETDATA devices.4.instances.0.commandClasses.132.data.lastWakeup = 1453925381 (0x56a92405)
[2016-01-27 21:09:41.788] [D] [zway] SETDATA devices.4.data.lastSend = 12608 (0x00003140)
[2016-01-27 21:09:41.788] [D] [zway] SETDATA devices.4.data.lastNonceGet = 11608 (0x00002d58)
[2016-01-27 21:09:41.789] [D] [zway] Running wakeup handler for node 4
[2016-01-27 21:09:41.789] [D] [zway] SETDATA devices.4.instances.0.commandClasses.132.data.lastSleep = 1453925381 (0x56a92405)
[2016-01-27 21:09:41.789] [I] [zway] Node 4:0 CC Wakeup: Send node to sleep
[2016-01-27 21:09:41.789] [I] [zway] Adding job: Wakeup Sleep
[2016-01-27 21:09:41.858] [D] [zway] SENDING (cb 0x03): ( 01 09 00 13 04 02 84 08 05 03 69 )
[2016-01-27 21:09:41.859] [D] [zway] RECEIVED ACK
[2016-01-27 21:09:41.863] [D] [zway] RECEIVED: ( 01 04 01 13 01 E8 )
[2016-01-27 21:09:41.863] [D] [zway] SENT ACK
[2016-01-27 21:09:41.863] [D] [zway] Delivered to Z-Wave stack
[2016-01-27 21:09:41.878] [D] [zway] RECEIVED: ( 01 07 00 13 03 00 00 02 EA )
[2016-01-27 21:09:41.878] [D] [zway] SENT ACK
[2016-01-27 21:09:41.878] [I] [zway] Job 0x13 (Wakeup Sleep): Delivered
[2016-01-27 21:09:41.878] [D] [zway] SETDATA devices.4.data.lastPacketInfo.delivered = True
[2016-01-27 21:09:41.879] [D] [zway] SETDATA devices.4.data.lastPacketInfo.packetLength = 5 (0x00000005)
[2016-01-27 21:09:41.879] [D] [zway] SETDATA devices.4.data.lastPacketInfo.deliveryTime = 14 (0x0000000e)
[2016-01-27 21:09:41.879] [D] [zway] SETDATA devices.4.data.lastPacketInfo = **********
[2016-01-27 21:09:41.879] [D] [zway] SendData Response with callback 0x03 received: received by recipient
[2016-01-27 21:09:41.880] [D] [zway] SETDATA devices.4.data.lastSend = 12617 (0x00003149)
[2016-01-27 21:09:41.880] [D] [zway] Job 0x13 (Wakeup Sleep): success
[2016-01-27 21:09:41.880] [D] [zway] SETDATA devices.4.data.isAwake = False
[2016-01-27 21:09:41.880] [D] [zway] Sending the queue for node 4 into sleep
[2016-01-27 21:09:41.880] [I] [zway] Removing job: Wakeup Sleep
[2016-01-27 21:09:47.114] [E] [8083] Callback execution error: TypeError: Cannot read property 'call' of undefined
at ZAutomationAPIWebRequest.ZAutomationWebRequest.handleRequest (automation/WebserverRequestRouter.js:258:40)
at automation/WebserverRequestRouter.js:32:35
at WebServer.document_root (automation/Webserver.js:29:11)
[2016-01-27 21:09:54.174] [E] [8083] Callback execution error: TypeError: Cannot read property 'call' of undefined
at ZAutomationAPIWebRequest.ZAutomationWebRequest.handleRequest (automation/WebserverRequestRouter.js:258:40)
at automation/WebserverRequestRouter.js:32:35
at WebServer.document_root (automation/Webserver.js:29:11)
[2016-01-27 21:10:02.080] [D] [zway] Job 0x13: deleted from queue
[2016-01-27 21:10:21.490] [E] [8083] Callback execution error: TypeError: Cannot read property 'call' of undefined
at ZAutomationAPIWebRequest.ZAutomationWebRequest.handleRequest (automation/WebserverRequestRouter.js:258:40)
at automation/WebserverRequestRouter.js:32:35
at WebServer.document_root (automation/Webserver.js:29:11)
[2016-01-27 21:13:13.448] [D] [zway] RECEIVED: ( 01 08 00 04 00 02 02 84 07 70 )
[2016-01-27 21:13:13.448] [D] [zway] SENT ACK
[2016-01-27 21:13:13.448] [D] [zway] SETDATA devices.2.data.lastReceived = 0 (0x00000000)
[2016-01-27 21:13:13.448] [I] [zway] Node 2:0 CC Wakeup: Wakeup notification
[2016-01-27 21:13:13.449] [D] [zway] SETDATA devices.2.instances.0.commandClasses.132.data.lastWakeup = 1453925593 (0x56a924d9)
[2016-01-27 21:13:13.449] [D] [zway] SETDATA devices.2.data.isAwake = True
[2016-01-27 21:13:13.449] [D] [zway] SETDATA devices.2.data.lastSend = 33470 (0x000082be)
[2016-01-27 21:13:13.449] [D] [zway] SETDATA devices.2.data.lastNonceGet = 32470 (0x00007ed6)
[2016-01-27 21:13:13.449] [D] [zway] Running wakeup handler for node 2
[2016-01-27 21:13:13.449] [D] [zway] SETDATA devices.2.instances.0.commandClasses.132.data.lastSleep = 1453925593 (0x56a924d9)
[2016-01-27 21:13:13.449] [I] [zway] Node 2:0 CC Wakeup: Send node to sleep
[2016-01-27 21:13:13.450] [I] [zway] Adding job: Wakeup Sleep
[2016-01-27 21:13:13.519] [D] [zway] SENDING (cb 0x04): ( 01 09 00 13 02 02 84 08 05 04 68 )
[2016-01-27 21:13:13.521] [D] [zway] RECEIVED ACK
[2016-01-27 21:13:13.525] [D] [zway] RECEIVED: ( 01 04 01 13 01 E8 )
[2016-01-27 21:13:13.525] [D] [zway] SENT ACK
Re: Problem with Door/Window sensor
Error "[E] [8083] Callback execution error" is related to the web-interface. It only occurs when I log in or out from my PC through Google Chrome (or Firefox).
It has no relation to the problem with my door/windows sensor which obviously is a bug introduced with v2.2.0
/Vovven
It has no relation to the problem with my door/windows sensor which obviously is a bug introduced with v2.2.0
/Vovven
Re: Problem with Door/Window sensor
Yes, judging by the js-file that throws the error, it sounds like it has something to do with the requests in the GUI. But in my case this happens during server startup, i.e. has nothing to do with login.Vovven wrote:Error "[E] [8083] Callback execution error" is related to the web-interface. It only occurs when I log in or out from my PC through Google Chrome (or Firefox).
-
golaonline
- Posts: 19
- Joined: 16 Dec 2015 21:59
Re: Problem with Door/Window sensor
I am seeing the same error when using the UI now.
[2016-02-11 17:39:32.516] [E] [8083] Callback execution error: TypeError: Cannot read property 'call' of undefined
at ZAutomationAPIWebRequest.ZAutomationWebRequest.handleRequest (automation/WebserverRequestRouter.js:258:40)
at automation/WebserverRequestRouter.js:32:35
at WebServer.document_root (automation/Webserver.js:29:11)
i was running fine on v2.2 till yesterday, i am seeing this issue after the z-way-server was restarted and i don't see any thing in the device event log on UI. Background alerts on one device which I have seem to be working fine.
Any idea on how to get rid of this problem, do i have to downgrade to lower version of UI?
[2016-02-11 17:39:32.516] [E] [8083] Callback execution error: TypeError: Cannot read property 'call' of undefined
at ZAutomationAPIWebRequest.ZAutomationWebRequest.handleRequest (automation/WebserverRequestRouter.js:258:40)
at automation/WebserverRequestRouter.js:32:35
at WebServer.document_root (automation/Webserver.js:29:11)
i was running fine on v2.2 till yesterday, i am seeing this issue after the z-way-server was restarted and i don't see any thing in the device event log on UI. Background alerts on one device which I have seem to be working fine.
Any idea on how to get rid of this problem, do i have to downgrade to lower version of UI?
-
golaonline
- Posts: 19
- Joined: 16 Dec 2015 21:59
Re: Problem with Door/Window sensor
I ended up reinstalling the whole z-way-server set up again today to get rid of this problem. It seems to be gone. i realized that there is a "Inband notifier" app, that is available, and I might have removed it from my last setup where i ran in to the error mentioned above, that was not showing any more notification on the UI.
Looks that removing Inband notifier may be the reason for error, I was facing.
Looks that removing Inband notifier may be the reason for error, I was facing.