Hi all,
Looks like I have yet another issue with this blasted Z-net interface.
In the evening last night, things seemed to be reactive and I went to sleep.
Looking at the logs, it seems there was enough activity going on to suggest HS3 and z-net were talking - ie: a couple of motion sensors sending their temperature reports in.
Woke up this morning, walked to the landing, motion detected and light turned on. Great!
Went into the bathroom, motion flashed but no light - however it is possible this was a glitch so I'll ignore it for now...
Went downstairs, motion flashed nothing on logs and no light.
Jan-19 07:10:22 Info Amazon Echo Discovery requested, version: 2
Jan-19 07:09:36 Info Amazon Echo Discovery requested, version: 2
Jan-19 07:06:03 Device Control Device: Upstairs Upstairs Landing Upstairs Light to On (255) by/from: CAPI Control Handler
Jan-19 07:05:34 Device Control Device: Upstairs Bedroom Bedroom Light to Off (0) by/from: CAPI Control Handler
Jan-19 07:05:01 Device Control Device: Upstairs Bedroom Bedroom Light to Off (0) by/from: CAPI Control Handler
Jan-19 07:04:59 Device Control Device: Upstairs Bedroom Bedroom Light to (value)% (46) by/from: CAPI Control Handler
Jan-19 07:02:25 Device Control Device: Downstairs Downstairs Landing Downstairs Light to On (255) by/from: CAPI Control Handler
Jan-19 06:58:26 Z-Wave Device: Node 29 Z-Wave Home Security Set to NOTIFICATION for type Home Security, Event: No Event
Jan-19 06:58:11
Here you can see I requested the bedroom light to be turned down via HS3 and twice to turn off. It accepted it and logged it but nothing actually happened.
i then set upstairs light to on, same issue, logged but nothing happened.
As I am typing this, it's been 10 minutes since the above (07:16 now) and everything just fired up. Bedroom light turned down and then off and upstairs light turned on as did the downstairs light requested at 6:58am.
I have had this since moving to z-net but blamed it on the virtual machine (hyper-v) and so yesterday I moved off it and installed it directly onto the server. It seems it has not helped.
It won't be a range thing as the downstairs light requested at 6:58 is literally opposite the interface and I did a optimise yesterday too.
When all this happened, I did a test connectivity on the upstairs light module and got a fail:
Failed to reach node 6 (Root Upstairs Landing Upstairs Light Fibaro Switch Binary)
All this time, I could access the z-net IP, I could access HS3 as per above logs and turning things on/off. the z-wave plug-in states everything was ok with a green tick.
I am running 3.0.1.184 (beta) for z-wave as the current stable release is causing me errors in the log file every minute - something HS support had not seen either and had recommended sticking to 184 but as it stands, HA is unusable if it's this flaky.
Appreciate any help on trying to figure out what the heck is going on
I suppose one test could be to downgrade to the stable - ignore the errors for now but test how reactive it is and stays - is it worth doing this?
Given the virtual machine is clearly not the issue, I might revert back to this and make a snapshot of the 3.0.1.184 version before reverting back down to the stable release.
Thanks
Looks like I have yet another issue with this blasted Z-net interface.
In the evening last night, things seemed to be reactive and I went to sleep.
Looking at the logs, it seems there was enough activity going on to suggest HS3 and z-net were talking - ie: a couple of motion sensors sending their temperature reports in.
Woke up this morning, walked to the landing, motion detected and light turned on. Great!
Went into the bathroom, motion flashed but no light - however it is possible this was a glitch so I'll ignore it for now...
Went downstairs, motion flashed nothing on logs and no light.
Jan-19 07:10:22 Info Amazon Echo Discovery requested, version: 2
Jan-19 07:09:36 Info Amazon Echo Discovery requested, version: 2
Jan-19 07:06:03 Device Control Device: Upstairs Upstairs Landing Upstairs Light to On (255) by/from: CAPI Control Handler
Jan-19 07:05:34 Device Control Device: Upstairs Bedroom Bedroom Light to Off (0) by/from: CAPI Control Handler
Jan-19 07:05:01 Device Control Device: Upstairs Bedroom Bedroom Light to Off (0) by/from: CAPI Control Handler
Jan-19 07:04:59 Device Control Device: Upstairs Bedroom Bedroom Light to (value)% (46) by/from: CAPI Control Handler
Jan-19 07:02:25 Device Control Device: Downstairs Downstairs Landing Downstairs Light to On (255) by/from: CAPI Control Handler
Jan-19 06:58:26 Z-Wave Device: Node 29 Z-Wave Home Security Set to NOTIFICATION for type Home Security, Event: No Event
Jan-19 06:58:11
Here you can see I requested the bedroom light to be turned down via HS3 and twice to turn off. It accepted it and logged it but nothing actually happened.
i then set upstairs light to on, same issue, logged but nothing happened.
As I am typing this, it's been 10 minutes since the above (07:16 now) and everything just fired up. Bedroom light turned down and then off and upstairs light turned on as did the downstairs light requested at 6:58am.
I have had this since moving to z-net but blamed it on the virtual machine (hyper-v) and so yesterday I moved off it and installed it directly onto the server. It seems it has not helped.
It won't be a range thing as the downstairs light requested at 6:58 is literally opposite the interface and I did a optimise yesterday too.
When all this happened, I did a test connectivity on the upstairs light module and got a fail:
Failed to reach node 6 (Root Upstairs Landing Upstairs Light Fibaro Switch Binary)
All this time, I could access the z-net IP, I could access HS3 as per above logs and turning things on/off. the z-wave plug-in states everything was ok with a green tick.
I am running 3.0.1.184 (beta) for z-wave as the current stable release is causing me errors in the log file every minute - something HS support had not seen either and had recommended sticking to 184 but as it stands, HA is unusable if it's this flaky.
Appreciate any help on trying to figure out what the heck is going on
I suppose one test could be to downgrade to the stable - ignore the errors for now but test how reactive it is and stays - is it worth doing this?
Given the virtual machine is clearly not the issue, I might revert back to this and make a snapshot of the 3.0.1.184 version before reverting back down to the stable release.
Thanks
Comment