Gå til innhold
  • Bli medlem
Støtt hjemmeautomasjon.no!

Generelt treg zwave / fibaro dimmer

mr.rs4

Av mr.rs4
i HomeSeer

 Del

Anbefalte innlegg

mr.rs4 Bitfikler

mr.rs4

Skrevet
Skrevet (endret)

Av og til så er fibaro dimmer treg, og vil ikke gjøre det den er "kommandert" til. Kan sette % eller skru av på/av, og etter minutter så kan det skje det jeg har satt dimmerene til.

Nå "lever" lyset/dimmerene sine egne liv, og kommer lenge etter på hva jeg har trykket på.

 

Kan det ha noe med "over belastning", som jeg tester ut mine events(tester ut hvordan ting fungere)?

 

Har restartet zwave plugin et par ganger og PC er restartet 1 gang. 

 

Hva kan være galt?


Log:

Spoiler

 

feb-13 00.20.59   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.59   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.58   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.58   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.57   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.57   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.56   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.56   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.55   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.55   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.54   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.54   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.53   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.53   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.52   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.52   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.51   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.51   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.50   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.50   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.49   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.49   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.48   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.48   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.47   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.47   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.46   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.46   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.45   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010002025322048C2E00030000105A0000000000
feb-13 00.20.45   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 2
feb-13 00.20.45   RFXCOM Transceiver #1 alive check, seq# 2
feb-13 00.20.45   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.45   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.44   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.44   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.43   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.43   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.42   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.42   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.41   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.41   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.40   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.40   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.39   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.39   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.38   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.38   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.37   Z-Wave *******************************************************************************
feb-13 00.20.37   Z-Wave STARTUP COMPLETE: All configured interfaces were successfully initialized.
feb-13 00.20.37   Z-Wave *******************************************************************************
feb-13 00.20.37   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.37   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.36   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.36   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.36   Z-Wave ZMEEUZB1: ......................................................................
feb-13 00.20.36   Z-Wave ZMEEUZB1: .............................. FINISHED ..............................
feb-13 00.20.36   Z-Wave ZMEEUZB1: ......................................................................
feb-13 00.20.36   Z-Wave ZMEEUZB1 is the SIS for the network.
feb-13 00.20.36   Z-Wave ZMEEUZB1 There is a SUC/SIS in the network.
feb-13 00.20.36   Z-Wave ZMEEUZB1 Controller is static lib.
feb-13 00.20.36   Z-Wave ZMEEUZB1 Controller chip type is ZW050x.
feb-13 00.20.36   Z-Wave The interface's security support has been set.
feb-13 00.20.36   Z-Wave ZMEEUZB1: Found 13 Z-Wave nodes in interface node ID 1 (ZMEEUZB1)
feb-13 00.20.36   Z-Wave ZMEEUZB1: Z-Wave interface node ID: 1, Home ID: FC0DBD69
feb-13 00.20.36   Z-Wave ZMEEUZB1: Z-Wave Serial API version: 6
feb-13 00.20.36   Z-Wave ZMEEUZB1: Z-Wave services for the SECURITY COMMAND CLASS were successfully started.
feb-13 00.20.35   Z-Wave ZMEEUZB1: Controller firmware version: 5.25
feb-13 00.20.35   Z-Wave ZMEEUZB1: Controller Manufacturer: PowerLynx, ID=0x1, Type=0x4
feb-13 00.20.35   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.35   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.34   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.34   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.33   Z-Wave 465 Simple AV Control Command Class Control Commands have been loaded successfully.
feb-13 00.20.33   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.33   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.33   Plug-In Finished initializing plug-in Z-Wave
feb-13 00.20.33   Starting Plug-In Z-Wave loaded in 1204 milliseconds
feb-13 00.20.33   Z-Wave ZMEEUZB1: Getting node information from controller...
feb-13 00.20.33   Z-Wave ZMEEUZB1: The Z-Wave API Execution Thread was Started or Restarted.
feb-13 00.20.33   Z-Wave ZMEEUZB1: The Z-Wave Command Execution Thread was Started or Restarted.
feb-13 00.20.33   Z-Wave ZMEEUZB1: ----------------------------------------------------------------------
feb-13 00.20.33   Z-Wave Initializing Z-Wave interface ZMEEUZB1 (Z-Wave.me UZB) on COM3
feb-13 00.20.33   Z-Wave ZMEEUZB1: ----------------------------------------------------------------------
feb-13 00.20.33   Z-Wave ZMEEUZB1: ======================================================================
feb-13 00.20.33   Z-Wave 0 event triggers were loaded from HomeSeer.
feb-13 00.20.33   Z-Wave 0 event actions were loaded from HomeSeer.
feb-13 00.20.33   Starting Plug-In Plugin Z-Wave started successfully in 645 milliseconds
feb-13 00.20.32   Z-Wave 117 total Z-Wave Data Objects loaded.
feb-13 00.20.32   Z-Wave Network FC0DBD69 has 117 device data elements.
feb-13 00.20.32   Z-Wave 1 Networks were restored from the data in the database... Building data connections.
feb-13 00.20.32   Z-Wave Loading Z-Wave Data Objects...
feb-13 00.20.32   Z-Wave 1 total Z-Wave Network Objects loaded.
feb-13 00.20.32   Z-Wave Loading Z-Wave Network Objects...
feb-13 00.20.32   Z-Wave Database: Opening (Mode=Read Only) up HomeSeer database C:\Program Files (x86)\HomeSeer HS3\Data\Z-Wave\Z-Wave2.db
feb-13 00.20.32   Z-Wave InitIO called, plug-in version 3.0.1.252 is being initialized...
feb-13 00.20.32   Starting Plug-In Initializing plugin Z-Wave ...
feb-13 00.20.32   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.32   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.32   Info Plugin Z-Wave has connected. IP:127.0.0.1:50500
feb-13 00.20.31   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.31   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.30   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.30   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.29   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.29   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.28   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.28   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.27   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.27   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.26   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.26   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.25   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.25   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.24   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.24   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.23   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.23   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.22   Info Plugin Z-Wave with instance: has disconnected
feb-13 00.20.22   Plug-In Shutting down Plug-In: Z-Wave
feb-13 00.20.22   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.22   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.21   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.21   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.20   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.20   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.19   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.19   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.18   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.18   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.17   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.17   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.16   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.16   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.15   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.15   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.14   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.14   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.13   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.13   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.12   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.12   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.12   Device Control Device: 2 Stue Switch Multilevel 1 - Tak Lys to Off (0) by/from: CAPI Control Handler
feb-13 00.20.11   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.11   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.10   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.10   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.09   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.09   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.08   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.08   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.07   Device Control Device: 2 Stue Switch Multilevel 1 - Tak Lys to (value)% (18) by/from: CAPI Control Handler
feb-13 00.20.07   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.07   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.06   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.06   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.05   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.05   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.04   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.04   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.03   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.03   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.02   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.02   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.01   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.01   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.20.00   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.20.00   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.19.59   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.19.59   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.19.59   Z-Wave *******************************************************************************
feb-13 00.19.59   Z-Wave STARTUP COMPLETE: All configured interfaces were successfully initialized.
feb-13 00.19.59   Z-Wave *******************************************************************************
feb-13 00.19.58   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.19.58   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.19.57   Z-Wave ZMEEUZB1: ......................................................................
feb-13 00.19.57   Z-Wave ZMEEUZB1: .............................. FINISHED ..............................
feb-13 00.19.57   Z-Wave ZMEEUZB1: ......................................................................
feb-13 00.19.57   Z-Wave ZMEEUZB1 is the SIS for the network.
feb-13 00.19.57   Z-Wave ZMEEUZB1 There is a SUC/SIS in the network.
feb-13 00.19.57   Z-Wave ZMEEUZB1 Controller is static lib.
feb-13 00.19.57   Z-Wave ZMEEUZB1 Controller chip type is ZW050x.
feb-13 00.19.57   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.19.57   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.19.57   Z-Wave The interface's security support has been set.
feb-13 00.19.57   TTS Speak ():Web server port number is 8088
feb-13 00.19.57   Z-Wave ZMEEUZB1: Found 13 Z-Wave nodes in interface node ID 1 (ZMEEUZB1)
feb-13 00.19.57   Z-Wave ZMEEUZB1: Z-Wave interface node ID: 1, Home ID: FC0DBD69
feb-13 00.19.57   Z-Wave ZMEEUZB1: Z-Wave Serial API version: 6
feb-13 00.19.57   Z-Wave ZMEEUZB1: Z-Wave services for the SECURITY COMMAND CLASS were successfully started.
feb-13 00.19.57   JowiHue Refresh bridge deCONZ-GW set to 30 seconds after establishing direct connection
feb-13 00.19.56   TTS Speak ():Welcome to Home-Seer
feb-13 00.19.56   Speaker Speaker host added, Name: DESKTOP-V3N8D7O Instance: Default IP address: 127.0.0.1
feb-13 00.19.56   Z-Wave ZMEEUZB1: Controller firmware version: 5.25
feb-13 00.19.56   Z-Wave ZMEEUZB1: Controller Manufacturer: PowerLynx, ID=0x1, Type=0x4
feb-13 00.19.56   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.19.56   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.19.56   JowiHue socket opened for deCONZ-GW on 192.168.120.115:443
feb-13 00.19.55   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 00.19.55   Event Event Trigger "3 etg - Lys bad Bad Lys AV"
feb-13 00.19.55   Info System connected to MyHS Service successfully with license ID 117690.
feb-13 00.19.55   Info System connected to MyHS Service, waiting for acknowledge...
feb-13 00.19.54   Startup Start up complete.
feb-13 00.19.54   Startup HSSentry is disabled in Setup, sentry will not be started.
feb-13 00.19.54   Startup (Startup.vb script) No speaker clients detected, waiting up to 30 seconds for any to connect...
feb-13 00.19.54   Startup (Startup.vb script) Scripting is OK and is now running Startup.vb
feb-13 00.19.54   Startup Starting Event Scheduler...
feb-13 00.19.54   Startup Running the startup script Startup.vb
feb-13 00.19.54   Info Starting speaker client...
feb-13 00.19.54   Startup Starting Find service...
feb-13 00.19.54   Startup Updater services starting...
feb-13 00.19.53   Z-Wave ZMEEUZB1: Getting node information from controller...
feb-13 00.19.53   Z-Wave ZMEEUZB1: The Z-Wave API Execution Thread was Started or Restarted.
feb-13 00.19.53   Database Opening (Mode=Read/Write) up HomeSeer Energy database C:\Program Files (x86)\HomeSeer HS3\Data\Energy\Energy.hsd
feb-13 00.19.53   Z-Wave 465 Simple AV Control Command Class Control Commands have been loaded successfully.
feb-13 00.19.53   Speech Listening for remote speaker connections on port 10401
feb-13 00.19.53   Startup Initializing Speaker Client Interface
feb-13 00.19.53   Startup Start automation engine...
feb-13 00.19.53   Z-Wave ZMEEUZB1: The Z-Wave Command Execution Thread was Started or Restarted.
feb-13 00.19.53   Startup HStouch server started, waiting for clients to connect.
feb-13 00.19.53   HSTouch Server Server started on port 10200
feb-13 00.19.53   Z-Wave ZMEEUZB1: ----------------------------------------------------------------------
feb-13 00.19.53   Z-Wave Initializing Z-Wave interface ZMEEUZB1 (Z-Wave.me UZB) on COM3
feb-13 00.19.53   Z-Wave ZMEEUZB1: ----------------------------------------------------------------------
feb-13 00.19.53   Z-Wave ZMEEUZB1: ======================================================================
feb-13 00.19.53   Plug-In Finished initializing plug-in Z-Wave
feb-13 00.19.53   Starting Plug-In Z-Wave loaded in 1216 milliseconds
feb-13 00.19.53   Z-Wave 0 event triggers were loaded from HomeSeer.
feb-13 00.19.53   Z-Wave 0 event actions were loaded from HomeSeer.
feb-13 00.19.53   Starting Plug-In Plugin Z-Wave started successfully in 701 milliseconds
feb-13 00.19.53   JowiHue ==============================================================================================
feb-13 00.19.53   JowiHue 0 Animations available for use in this plugin
feb-13 00.19.53   JowiHue 0 Local scenes available for use in the JowiHue plugin
feb-13 00.19.53   JowiHue 22 Presets available for use in the JowiHue plugin
feb-13 00.19.53   JowiHue -------------------------------------Plugin info ---------------------------------------------
feb-13 00.19.53   JowiHue 1 Daylight sensor found on bridge 'deCONZ-GW'
feb-13 00.19.53   JowiHue 2 Remote switch(s) found on bridge 'deCONZ-GW' with 2 supporting HS device(s)
feb-13 00.19.53   JowiHue Bridge deCONZ-GW is at version 2.5.20 of type deCONZ on a ConBee
feb-13 00.19.53   JowiHue 6 Groups available on bridge 'deCONZ-GW'
feb-13 00.19.53   JowiHue 3 lights and/or plugs connected to bridge 'deCONZ-GW'
feb-13 00.19.53   JowiHue -------------------------------------Bridge info ---------------------------------------------
feb-13 00.19.53   JowiHue ==============================================================================================
feb-13 00.19.53   Z-Wave 117 total Z-Wave Data Objects loaded.
feb-13 00.19.53   Z-Wave Network FC0DBD69 has 117 device data elements.
feb-13 00.19.53   Z-Wave 1 Networks were restored from the data in the database... Building data connections.
feb-13 00.19.53   Z-Wave Loading Z-Wave Data Objects...
feb-13 00.19.53   Z-Wave 1 total Z-Wave Network Objects loaded.
feb-13 00.19.53   Z-Wave Loading Z-Wave Network Objects...
feb-13 00.19.53   Z-Wave Database: Opening (Mode=Read Only) up HomeSeer database C:\Program Files (x86)\HomeSeer HS3\Data\Z-Wave\Z-Wave2.db
feb-13 00.19.53   Z-Wave InitIO called, plug-in version 3.0.1.252 is being initialized...
feb-13 00.19.53   Starting Plug-In Initializing plugin Z-Wave ...
feb-13 00.19.52   Info Plugin Z-Wave has connected. IP:127.0.0.1:49729
feb-13 00.19.52   JowiHue * Connected to bridge deCONZ-GW at 192.168.120.115:80
feb-13 00.19.52   Plug-In Finished initializing plug-in JowiHue
feb-13 00.19.52   Starting Plug-In JowiHue loaded in 785 milliseconds
feb-13 00.19.52   Starting Plug-In Plugin JowiHue started successfully in 358 milliseconds
feb-13 00.19.52   JowiHue InitIO:Plugin basic initialisation done
feb-13 00.19.52   JowiHue Starting plugin JowiHue 2.0.2.15 on Windows
feb-13 00.19.52   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010001025322048C2E00030000105A0000000000
feb-13 00.19.52   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 1
feb-13 00.19.52   Starting Plug-In Initializing plugin JowiHue ...
feb-13 00.19.52   RFXCOM Transceiver #1 transmit Get Status
feb-13 00.19.51   Info Plugin JowiHue has connected. IP:127.0.0.1:49715
feb-13 00.19.51   Plug-In Finished initializing plug-in RFXCOM
feb-13 00.19.51   Starting Plug-In RFXCOM loaded in 662 milliseconds
feb-13 00.19.51   Starting Plug-In Plugin RFXCOM started successfully in 315 milliseconds
feb-13 00.19.51   RFXCOM 37 (InitTRX) Connect Transceiver #1 on COM5
feb-13 00.19.51   RFXCOM 37 (InitIO) RFXCOM version is:30.0.0.37
feb-13 00.19.51   Starting Plug-In Initializing plugin RFXCOM ...
feb-13 00.19.51   Info Plugin RFXCOM has connected. IP:127.0.0.1:49704
feb-13 00.19.50   Plug-In Finished initializing plug-in MyQ
feb-13 00.19.50   Starting Plug-In MyQ loaded in 1378 milliseconds
feb-13 00.19.50   Starting Plug-In Plugin MyQ started successfully in 129 milliseconds
feb-13 00.19.50   MyQ Initializing version 1.2018.717.1011
feb-13 00.19.50   Starting Plug-In Initializing plugin MyQ ...
feb-13 00.19.50   Info Plugin MyQ has connected. IP:127.0.0.1:49698
feb-13 00.19.49   Plug-In Finished initializing plug-in BLBackup
feb-13 00.19.49   Starting Plug-In BLBackup loaded in 427 milliseconds
feb-13 00.19.49   Starting Plug-In Plugin BLBackup started successfully in 43 milliseconds
feb-13 00.19.49   BLBackup start BLBackup plugin has been initialized
feb-13 00.19.49   BLBackup start Backup Folders have been loaded.
feb-13 00.19.49   BLBackup start Loaded configuration successfully
feb-13 00.19.49   BLBackup start BLBackup version is: 2.0.59.0
feb-13 00.19.49   BLBackup start Initializing BLBackup...
feb-13 00.19.49   Starting Plug-In Initializing plugin BLBackup ...
feb-13 00.19.49   Info Plugin BLBackup has connected. IP:127.0.0.1:49687
feb-13 00.19.49   Warning File does not exist: C:\Program Files (x86)\HomeSeer HS3\html\images\HomeSeer\status\angle-position.png
feb-13 00.19.49   Warning File does not exist: C:\Program Files (x86)\HomeSeer HS3\html\images\HomeSeer\status\seismic.png
feb-13 00.19.48   Startup Initializing Plug-Ins
feb-13 00.19.48   Plug-In Found plug-in: Z-Wave, version: 3.0.1.252
feb-13 00.19.48   Plug-In Found plug-in: RFXCOM, version: 30.0.0.37
feb-13 00.19.48   Plug-In Found plug-in: MyQ, version: 1.2018.717.1011
feb-13 00.19.48   Plug-In Found plug-in: JowiHue, version: 2.0.2.15
feb-13 00.19.47   Plug-In Found plug-in: BLBackup, version: 2.0.59.0
feb-13 00.19.47   Web Server Web Server authorized local login successful from: 192.168.120.2 User: [email protected]
feb-13 00.19.47   Startup Checking for available plug-ins
feb-13 00.19.47   Info Remote plug-in API interface started on port 10400
feb-13 00.19.47   Startup Creating ASP.NET application host...
feb-13 00.19.46   Web Server Web Server started on localhost, port 8088
feb-13 00.19.46   Web Server Web server remote access is disabled. It can only be accessed from this computer
feb-13 00.19.46   Web Server The web server has been bound specifically to IP address 192.168.120.115
feb-13 00.19.46   Web Server Local IP address (subnet) is: 192.168.120.115 (255.255.255.0)
feb-13 00.19.46   Startup This version of HomeSeer is registered as a HS3PRO version.
feb-13 00.19.46   HSPhone HomeSeer Phone Web Interface initializing.
feb-13 00.19.46   Startup Initializing phone interface...
feb-13 00.19.46   Startup Creating Speaker Client Interface Object...
feb-13 00.19.46   Startup HomeSeer version is: 3.0.0.500
feb-13 00.19.46   Load Config Loading TIMERS...
feb-13 00.19.46   Load Config Loading COUNTERS...
feb-13 00.19.46   Load Config 43 total events loaded.
feb-13 00.19.46   Load Config Loading Events...
feb-13 00.19.46   Load Config Loading Event Groups...
feb-13 00.19.46   Load Config 147 total devices loaded.
feb-13 00.19.46   Database Loading Devices...
feb-13 00.19.46   Database Opening (Mode=Read Only) up HomeSeer database C:\Program Files (x86)\HomeSeer HS3\Data\HomeSeerData.hsd
feb-13 00.19.46   Startup Loading configuration file ...
feb-13 00.19.46   Startup Database SAVE process started.
feb-13 00.19.46   Startup Local voice recognition class started.
feb-13 00.19.46   Startup Plug-In Interface class started.
feb-13 00.19.46   Startup E-Mail RECEIVE class started.
feb-13 00.19.46   Startup E-Mail SEND class started.
feb-13 00.19.46   Startup Web server class started.
feb-13 00.19.46   Startup Application interface class started.
feb-13 00.19.46   Startup COM port classes started.
feb-13 00.19.46   Startup Creating Class Objects...
feb-13 00.19.46   Startup  
feb-13 00.19.46   Startup ********************************************************************************
feb-13 00.19.46   Startup HomeSeer version 3.0.0.500 Edition: HS3 Pro Starting Now
feb-13 00.19.46   Startup ********************************************************************************
feb-13 00.19.46   Startup  
feb-13 00.19.46   Startup Settings Loaded.

 

 
Endret av mr.rs4
Lenke til kommentar
Del på andre sider
mr.rs4 Bitfikler

mr.rs4

Skrevet
  • Forfatter
Skrevet
6 minutes ago, GeneralVirus said:

Hvis du ser i loggen din så ser du at taklys bad settes til av hvert sekund. Hvordan ser eventet ditt som heter "3 etg - Lys bad Bad Lys AV" ut? Der har du mest sannsynlig problemet ditt. Prøv å legg til en til trigger med at lyset også må være på for at det skal kjøre.

Ok, det har jeg ikke satt opp nei

 

Dette hadde jeg satt opp, som var kanskje feil...

Spoiler

image.thumb.png.1b221d5175e41f7a1b34857e68b58f83.png

 

 

Er dette bedre?

Med AND IF This device has a value equal to - Any value. Eller skal det stå On, for da er det vel på uansett hvilke % dimmeren har?

Spoiler

image.thumb.png.74996d33ba076a2b5be30a7663b82541.png

 

 

Lenke til kommentar
Del på andre sider
GeneralVirus Loddebolt

GeneralVirus

Skrevet
Skrevet
7 minutes ago, mr.rs4 said:

Dette hadde jeg satt opp, som var kanskje feil...

Ja, denne vil trigge hvert sekund etter at det har gått 12 minutter til neste gang det blir motion. Du burde bytte ut "This device has been/for at least" til "has been/for excactly".

 

11 minutes ago, mr.rs4 said:

Med AND IF This device has a value equal to - Any value. Eller skal det stå On, for da er det vel på uansett hvilke % dimmeren har?

Hvis du setter det til "Any value" kan du jo egentlig la være, enten on eller greater then 1.

  • Like 1
  • Thanks 1
Lenke til kommentar
Del på andre sider
mr.rs4 Bitfikler

mr.rs4

Skrevet
  • Forfatter
Skrevet

Ok, slik som det er nå, har jeg ikke så mange triggere enda. Har satt opp bevegelse trigger og tids punkt trigger foreløpig for det meste.

 

Har satt opp en trigger på bevegelse i dør sensor, og da bruker jeg "This device has been/for at least" 

Dette for å slå på en "varsel" lys, om at noen kommer, og jeg er i et rom med mye støy. 

 

Hadde det vært bedre og brukt "has been/for excactly" med å "varsle" meg?

Lenke til kommentar
Del på andre sider
mr.rs4 Bitfikler

mr.rs4

Skrevet
  • Forfatter
Skrevet

Har forandret en del ting her og der, men ser fortsatt aktivitet i LOG, og lurer på om det er vanlig

 

Oppsett på gang 3 etg

Spoiler

image.thumb.png.db85ee4eecc4423168f70f54ea582ca4.png

 

 

Log, er det vanlig med slik aktivitet?

Spoiler

 

feb-13 03.56.06   Z-Wave Device: 3 Gang Power - Tak Lys Set to 0,9 (W)
feb-13 03.55.56   Z-Wave Device: 3 Gang Power - Tak Lys Set to 1 (W)
feb-13 03.55.46   Z-Wave Device: 3 Gang Power - Tak Lys Set to 0,9 (W)
feb-13 03.55.39   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010000025322048C2E00030000105A0000000000
feb-13 03.55.39   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 0
feb-13 03.55.39   RFXCOM Transceiver #1 alive check, seq# 0
feb-13 03.55.36   Z-Wave Device: 3 Gang Power - Tak Lys Set to 1 (W)
feb-13 03.55.25   Z-Wave Device: 3 Gang Power - Tak Lys Set to 0,9 (W)
feb-13 03.55.11   Z-Wave Device: 3 Gang Power - Tak Lys Set to 1 (W)
feb-13 03.54.59   Z-Wave Device: 3 Gang Power - Tak Lys Set to 0,9 (W)
feb-13 03.54.49   Z-Wave Device: 3 Gang Power - Tak Lys Set to 1 (W)
feb-13 03.54.46   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100FF025322048C2E00030000105A0000000000
feb-13 03.54.46   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 255
feb-13 03.54.46   RFXCOM Transceiver #1 alive check, seq# FF
feb-13 03.54.39   Z-Wave Device: 3 Gang Power - Tak Lys Set to 0,9 (W)
feb-13 03.54.29   Z-Wave Device: 3 Gang Power - Tak Lys Set to 1 (W)
feb-13 03.54.09   Z-Wave Device: 3 Gang Power - Tak Lys Set to 0,9 (W)
feb-13 03.53.59   Z-Wave Device: 3 Gang Power - Tak Lys Set to 1 (W)
feb-13 03.53.54   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100FE025322048C2E00030000105A0000000000
feb-13 03.53.54   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 254
feb-13 03.53.54   RFXCOM Transceiver #1 alive check, seq# FE
feb-13 03.53.37   Z-Wave Device: 3 Gang Power - Tak Lys Set to 0,9 (W)
feb-13 03.53.27   Z-Wave Device: 3 Gang Power - Tak Lys Set to 1 (W)
feb-13 03.53.01   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100FD025322048C2E00030000105A0000000000
feb-13 03.53.01   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 253
feb-13 03.53.01   RFXCOM Transceiver #1 alive check, seq# FD
feb-13 03.52.38   Z-Wave Device: 3 Gang Power - Tak Lys Set to 0,9 (W)
feb-13 03.52.28   Z-Wave Device: 3 Gang Power - Tak Lys Set to 1 (W)
feb-13 03.52.17   Z-Wave Device: 3 Gang Power - Tak Lys Set to 0,9 (W)
feb-13 03.52.09   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100FC025322048C2E00030000105A0000000000
feb-13 03.52.09   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 252
feb-13 03.52.08   RFXCOM Transceiver #1 alive check, seq# FC
feb-13 03.52.07   Z-Wave Device: 3 Gang Power - Tak Lys Set to 1 (W)
feb-13 03.51.57   Z-Wave Device: 3 Gang Power - Tak Lys Set to 0,9 (W)
feb-13 03.51.48   Z-Wave Device: 3 Gang Power - Tak Lys Set to 1 (W)
feb-13 03.51.38   Z-Wave Device: 3 Gang Power - Tak Lys Set to 0,9 (W)
feb-13 03.51.27   Z-Wave Device: 3 Gang Power - Tak Lys Set to 1 (W)
feb-13 03.51.17   Z-Wave Device: 3 Gang Power - Tak Lys Set to 0,9 (W)
feb-13 03.51.16   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100FB025322048C2E00030000105A0000000000
feb-13 03.51.16   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 251
feb-13 03.51.16   RFXCOM Transceiver #1 alive check, seq# FB
feb-13 03.51.07   Z-Wave Device: 3 Gang Power - Tak Lys Set to 1 (W)
feb-13 03.50.44   Z-Wave Device: 3 Gang Power - Tak Lys Set to 0,9 (W)
feb-13 03.50.33   Z-Wave Device: 3 Gang Power - Tak Lys Set to 1 (W)
feb-13 03.50.23   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100FA025322048C2E00030000105A0000000000
feb-13 03.50.23   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 250
feb-13 03.50.23   RFXCOM Transceiver #1 alive check, seq# FA
feb-13 03.50.21   Z-Wave Device: 3 Gang Power - Tak Lys Set to 0,9 (W)
feb-13 03.50.10   Z-Wave Device: 3 Gang Power - Tak Lys Set to 1 (W)
feb-13 03.49.57   Z-Wave Device: 3 Gang Power - Tak Lys Set to 0,9 (W)
feb-13 03.49.52   JowiHue Cannot find key for light Light 3 - Sovreom 1 (id=3) was it removed from the bridge?
feb-13 03.49.52   JowiHue Cannot find key for light Light 2 - TV Stue (id=2) was it removed from the bridge?
feb-13 03.49.46   Z-Wave Device: 3 Gang Power - Tak Lys Set to 1 (W)
feb-13 03.49.35   Z-Wave Device: 3 Gang Power - Tak Lys Set to 0,9 (W)
feb-13 03.49.31   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100F9025322048C2E00030000105A0000000000
feb-13 03.49.31   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 249
feb-13 03.49.31   RFXCOM Transceiver #1 alive check, seq# F9
feb-13 03.49.25   Z-Wave Device: 3 Gang Power - Tak Lys Set to 1 (W)
feb-13 03.49.09   Z-Wave Device: 3 Gang Power - Tak Lys Set to 0,9 (W)
feb-13 03.48.58   Z-Wave Device: 3 Gang Power - Tak Lys Set to 1 (W)
feb-13 03.48.46   Z-Wave Device: 3 Gang Power - Tak Lys Set to 0,9 (W)
feb-13 03.48.38   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100F8025322048C2E00030000105A0000000000
feb-13 03.48.38   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 248
feb-13 03.48.38   RFXCOM Transceiver #1 alive check, seq# F8
feb-13 03.48.36   Z-Wave Device: 3 Gang Power - Tak Lys Set to 1 (W)
feb-13 03.47.46   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100F7025322048C2E00030000105A0000000000
feb-13 03.47.46   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 247
feb-13 03.47.46   RFXCOM Transceiver #1 alive check, seq# F7
feb-13 03.47.33   Z-Wave Device: 3 Gang Power - Tak Lys Set to 0,9 (W)
feb-13 03.47.20   Z-Wave Device: 3 Gang Power - Tak Lys Set to 1 (W)
feb-13 03.47.16   Z-Wave Device: 2 TV Stue Power - Tak Lys Set to 37,3 (W)
feb-13 03.47.14   Z-Wave Device: 2 TV Stue Power - Tak Lys Set to 37,4 (W)
feb-13 03.47.10   Z-Wave Device: 3 Gang Power - Tak Lys Set to 0,9 (W)
feb-13 03.47.10   Device Control Device: 2 TV Stue Switch Multilevel 1 - Tak Lys to 20% (20)
feb-13 03.47.10   Event Event Trigger "2 etg - Lys TV Stue TV Stue Kveld"
feb-13 03.47.10   Event Event 2 etg - Lys TV Stue TV Stue Kveld triggered by the event page 'Run' button.
feb-13 03.47.04   Z-Wave Device: 2 TV Stue Power - Tak Lys Set to 86,4 (W)
feb-13 03.46.57   Device Control Device: 2 TV Stue Switch Multilevel 1 - Tak Lys to (value)% (47) by/from: CAPI Control Handler
feb-13 03.46.57   Z-Wave Device: 3 Gang Power - Tak Lys Set to 1 (W)
feb-13 03.46.56   Z-Wave Device: 2 TV Stue Power - Tak Lys Set to 63,7 (W)
feb-13 03.46.55   Device Control Device: 2 TV Stue Switch Multilevel 1 - Tak Lys to On (99) by/from: CAPI Control Handler
feb-13 03.46.53   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100F6025322048C2E00030000105A0000000000
feb-13 03.46.53   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 246
feb-13 03.46.53   RFXCOM Transceiver #1 alive check, seq# F6
feb-13 03.46.51   Z-Wave Device: 3 Bad Power - Tak Lys Set to 12,7 (W)
feb-13 03.46.47   Z-Wave Device: 3 Gang Power - Tak Lys Set to 0,9 (W)
feb-13 03.46.36   Z-Wave Device: 3 Gang Power - Tak Lys Set to 1 (W)
feb-13 03.46.26   Z-Wave Device: 3 Gang Power - Tak Lys Set to 0,9 (W)
feb-13 03.46.16   Z-Wave Device: 3 Gang Power - Tak Lys Set to 1 (W)
feb-13 03.46.16   Z-Wave Device: 2 TV Stue General Purpose Alarm - TV Stue Set to NO ALARM (0)
feb-13 03.46.15   Z-Wave Device: 2 TV Stue Sensor Binary - TV Stue Set to Off/Closed/No Motion
feb-13 03.46.15   Z-Wave Device: 2 TV Stue Home Security - TV Stue Set to NOTIFICATION for type Home Security, Event: No Event
feb-13 03.46.06   Z-Wave Device: 3 Gang Power - Tak Lys Set to 0,9 (W)
feb-13 03.46.01   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100F5025322048C2E00030000105A0000000000
feb-13 03.46.01   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 245
feb-13 03.46.01   RFXCOM Transceiver #1 alive check, seq# F5
feb-13 03.46.00   Z-Wave Device: 2 TV Stue Power - Tak Lys Set to 0 (W)
feb-13 03.45.58   Device Control Device: 2 TV Stue Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 03.45.58   Event Event Trigger "Alt lys - Av om natten -- Kanskje Slettes TV Stue Lys - Av om ikke bevegelse på en stund"
feb-13 03.45.57   Device Control Device: 2 TV Stue Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 03.45.57   Event Event Trigger "Alt lys - Av om natten -- Kanskje Slettes TV Stue Lys - Av om ikke bevegelse på en stund"
feb-13 03.45.56   Device Control Device: 2 TV Stue Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 03.45.56   Event Event Trigger "Alt lys - Av om natten -- Kanskje Slettes TV Stue Lys - Av om ikke bevegelse på en stund"
feb-13 03.45.55   Device Control Device: 2 TV Stue Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 03.45.55   Event Event Trigger "Alt lys - Av om natten -- Kanskje Slettes TV Stue Lys - Av om ikke bevegelse på en stund"
feb-13 03.45.54   Device Control Device: 2 TV Stue Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 03.45.54   Event Event Trigger "Alt lys - Av om natten -- Kanskje Slettes TV Stue Lys - Av om ikke bevegelse på en stund"
feb-13 03.45.53   Z-Wave Device: 2 TV Stue Switch Multilevel 1 - Tak Lys Set to 38%
feb-13 03.45.53   Device Control Device: 2 TV Stue Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 03.45.53   Event Event Trigger "Alt lys - Av om natten -- Kanskje Slettes TV Stue Lys - Av om ikke bevegelse på en stund"
feb-13 03.45.52   Device Control Device: 2 TV Stue Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 03.45.52   Event Event Trigger "Alt lys - Av om natten -- Kanskje Slettes TV Stue Lys - Av om ikke bevegelse på en stund"
feb-13 03.45.51   Z-Wave Device: 3 Gang Power - Tak Lys Set to 1 (W)
feb-13 03.45.51   Device Control Device: 2 TV Stue Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 03.45.51   Event Event Trigger "Alt lys - Av om natten -- Kanskje Slettes TV Stue Lys - Av om ikke bevegelse på en stund"
feb-13 03.45.50   Device Control Device: 2 TV Stue Switch Multilevel 1 - Tak Lys to Off (0)
feb-13 03.45.50   Event Event Trigger "Alt lys - Av om natten -- Kanskje Slettes TV Stue Lys - Av om ikke bevegelse på en stund"
feb-13 03.45.49   Z-Wave Device: 2 TV Stue Power - Tak Lys Set to 6 (W)
feb-13 03.45.49   Z-Wave Device: 2 TV Stue Luminance - TV Stue Set to 3 (Lux)
feb-13 03.45.49   Z-Wave Device: 2 TV Stue Home Security - TV Stue Set to NOTIFICATION for type Home Security, Event: Tampering Cover Removed
feb-13 03.45.49   Device Control Device: 2 TV Stue Switch Multilevel 1 - Tak Lys to Off (0)

 

 

Lenke til kommentar
Del på andre sider
ZoRaC Blåtannlege

ZoRaC

Skrevet
Skrevet
6 timer siden, mr.rs4 skrev:

Hvor "ofte" bør en heller bruke "has been/for excactly" istedenfor "This device has been/for at least"?

Eller i hvilke situasjoner bør en ha "has been/for excactly"?

 

Hvis du vil at noe skal skje hvert eneste sekund i evig tid etter tiden du angir (f.eks 12 min), så bruker du «has been for at least». Vil du at noe skal skje EN gang etter tiden du angir (f.eks 12 min), så angir du «has been for exactly». 

 

Jeg kommer ikke på et eneste tilfelle der «has been for at least» bør brukes...

  • Thanks 1
Lenke til kommentar
Del på andre sider
ZoRaC Blåtannlege

ZoRaC

Skrevet
Skrevet
4 timer siden, mr.rs4 skrev:

 Log, er det vanlig med slik aktivitet?

 

Ja, den ligger nå akkurat i grensa 0,9w og 1w. Default er at den skal rapportere ved 10% endring, så da blir det slik. Jeg har endret parameter til 50% endring før den skal rapportere. Gjorde det på alle dimmere for et pr uker siden og synes jeg merker at ting er raskere pga mindre trafikk (kan selvsagt være innbilning). :) 

Lenke til kommentar
Del på andre sider
Moskus Automatiker

Moskus

Skrevet
Skrevet

Næmmen SE hva som står i HS-skolen del 7:

 

Sitat

Q: Hva er forskjellen på triggerne "Device Has Been X for Exactly Y time" og "Device Has Been X for At Least Y time"?
     Vil det ikke være best å bruke "At Least"?

A: Som trigger er "At Least" veldig skummel å bruke, et eksempel på hvor galt det kan gå kan du lese her. Grunnen er forskjellen i hvordan disse to trigges.

 

Nå er det litt mer komplisert enn det som forklares her (og sjekkene skjer oftere enn det), men la oss for enkelhets skyld si at alle eventer blir sjekket hvert sekund. Normalt skal et Event kun kjøre en gang, med mindre det er gode grunner til å kjøre det flere ganger, men sannsynligvis aldri så ofte som hvert sekund

Et event med trigger "Taklys has been OFF for exactly 2 minutes" vil kun kjøre den ene gangen, og ferdig med det.

Et event med trigger "Taklys has been OFF for at least 2 minutes" vil kjøre etter 2:00, 2:01, 2:02... altså hvert sekund etter at det har gått to minutter siden taklyset ble skrudd av.

 

Jeg tror grunnen til at folk ofte velger "at least" istedenfor "exactly" er at "exactly" høres så usikkert ut. "Oi, tenk hvis den bommer! Da vil jo 'At Least' være sikrere". Og det finnes tilfeller der "At Least" absolutt kan være nyttig, den er spesielt hendig som en condition. Men hvis du vil bruke den som trigger, så må du legge til andre conditions som gjør at eventet ikke trigges i det uendelige...

 

Bare lufter det enda en gang, liksom: Kanskje det nå hadde vært en idé å lese den fra ende til annen...? ;) 

 

  • Like 2
Lenke til kommentar
Del på andre sider
mr.rs4 Bitfikler

mr.rs4

Skrevet
  • Forfatter
Skrevet

Ja, noe går inn og noe går ikke inn. Den HS skolen er meget bra ?

Noen lærer best med å teste ut, andre lærer best med å lese seg frem til ting. Jeg er nok i den andre kategorien der jeg må teste frem. Skulle ønsket jeg forsto mer med å lese meg frem til ting, hadde vært en del lettere. Men denne Q & A for "Device Has Been X for Exactly Y time" og "Device Has Been X for At Least Y time" burde jeg ha ihvertfall ha visst bedre på.

 

Lenke til kommentar
Del på andre sider
Moskus Automatiker

Moskus

Skrevet
Skrevet
På 16.2.2019 den 1.52, mr.rs4 skrev:

Jeg er nok i den andre kategorien der jeg må teste frem.

Ja, og det er forståelig. Men hvis noe feiler, så hadde det vært både enklere og kjappere å slå opp i kjent literatur... ;)

 

Det hender selvfølgelig at vi bommer alle sammen. :) 

Jeg har gjort feil i eventer jeg også, og kommer garantert til å gjøre det igjen: https://www.hjemmeautomasjon.no/forums/topic/192-dine-automasjonstabber/

 

Lenke til kommentar
Del på andre sider
mr.rs4 Bitfikler

mr.rs4

Skrevet
  • Forfatter
Skrevet

Det har fungert mer eller mindre greit, til dem siste dagene. Har hatt en fibaro dimmer(i 3etg i gangen) der den dimmet 2 stk forskjellige lamper med forskjellige laster. Som dere har sagt så var dette ikke å anbefale og det ser jeg nå. Det fungerte tidligere, men etter hvert som tilbake meldingene som kommer til til dimmer ifra last og videre til z-wave og NUC. Der den ikke kunne "lese" tilbake meldingene. Så jeg tok vekk denne dimmeren fysisk(tok ikke vekk node / dimmer i HS3), og satt opp IKEA pærer der istedenfor. 

 

Nå er systemet helt ustabilt, flere sensorer(bevegelse sensorer) er litt på styr. Har scanet zwave på nytt, optimalisert på nytt uten hjelp.

 

Nå skal jeg teste ut back up, men her har jeg allerede en dimmer som er med i backup(den som jeg tok vekk i 3etg gang). Vil det fortsette med problem? 

 

Ifra log

Spoiler

 

feb-22 20.34.40   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100ED025322048C2E0003000010650000000000
feb-22 20.34.40   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 237
feb-22 20.34.40   RFXCOM Transceiver #1 alive check, seq# ED
feb-22 20.33.48   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100EC025322048C2E0003000010650000000000
feb-22 20.33.48   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 236
feb-22 20.33.48   RFXCOM Transceiver #1 alive check, seq# EC
feb-22 20.32.55   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100EB025322048C2E0003000010650000000000
feb-22 20.32.55   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 235
feb-22 20.32.55   RFXCOM Transceiver #1 alive check, seq# EB
feb-22 20.32.43   Z-Wave Device: 3 Gang Luminance - Gang Set to 17 (Lux)
feb-22 20.32.03   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100EA025322048C2E0003000010650000000000
feb-22 20.32.03   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 234
feb-22 20.32.03   RFXCOM Transceiver #1 alive check, seq# EA
feb-22 20.31.10   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100E9025322048C2E0003000010650000000000
feb-22 20.31.10   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 233
feb-22 20.31.10   RFXCOM Transceiver #1 alive check, seq# E9
feb-22 20.30.18   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100E8025322048C2E0003000010650000000000
feb-22 20.30.18   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 232
feb-22 20.30.18   RFXCOM Transceiver #1 alive check, seq# E8
feb-22 20.29.25   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100E7025322048C2E0003000010650000000000
feb-22 20.29.25   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 231
feb-22 20.29.25   RFXCOM Transceiver #1 alive check, seq# E7
feb-22 20.28.36   Z-Wave Warning ZMEEUZB1 : Secure message received from node 9. It was successfully decrypted but the data sequence ID is out of sequence. (Not Processed)
feb-22 20.28.36   Z-Wave Warning ZMEEUZB1 : Secure message received from node 8. It was successfully decrypted but the data sequence ID is out of sequence. (Not Processed)
feb-22 20.28.36   Z-Wave Device: 3 Bad Sensor Binary - Bad Set to On/Open/Motion
feb-22 20.28.33   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100E6025322048C2E0003000010650000000000
feb-22 20.28.33   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 230
feb-22 20.28.32   RFXCOM Transceiver #1 alive check, seq# E6
feb-22 20.28.23   Z-Wave Device: 2 TV Stue Power - Tak Lys Set to 97,1 (W)
feb-22 20.27.45   Device Control Device: 2 TV Stue Switch Multilevel 1 - Tak Lys to (value)% (54) by/from: CAPI Control Handler
feb-22 20.27.45   Device Control Device: 2 TV Stue Switch Multilevel 1 - Tak Lys to (value)% (54) by/from: CAPI Control Handler
feb-22 20.27.40   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100E5025322048C2E0003000010650000000000
feb-22 20.27.40   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 229
feb-22 20.27.40   RFXCOM Transceiver #1 alive check, seq# E5
feb-22 20.27.26   Z-Wave Device: 3 Bad Sensor Binary - Bad Set to Off/Closed/No Motion
feb-22 20.27.20   Z-Wave Device: 3 Bad Home Security - Bad Set to NOTIFICATION for type Home Security, Event: No Event
feb-22 20.27.01   Z-Wave Device: 3 Bad Power - Tak Lys Set to 79,8 (W)
feb-22 20.26.47   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100E4025322048C2E0003000010650000000000
feb-22 20.26.47   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 228
feb-22 20.26.47   RFXCOM Transceiver #1 alive check, seq# E4
feb-22 20.26.41   Z-Wave Device: 3 Bad Sensor Binary - Bad Set to On/Open/Motion
feb-22 20.26.41   Z-Wave Device: 3 Gang Sensor Binary - Gang Set to On/Open/Motion
feb-22 20.26.40   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to 50% (50)
feb-22 20.26.40   Event Remove Delayed Device Action Removed event: Delayed Actions Switch Multilevel 1 - Tak Lys (Delayed Action) - 1
feb-22 20.26.40   Event Event Trigger "3 etg - Lys bad Bad Kveld"
feb-22 20.26.40   Z-Wave Device: 3 Bad Home Security - Bad Set to NOTIFICATION for type Home Security, Event: Motion Detected
feb-22 20.26.40   Device Control Device: 3 Gang 3etg Vegglampe to 50% (50)
feb-22 20.26.40   Device Control Device: 3 Gang 3etg Taklampe -3 to 40% (40)
feb-22 20.26.40   Device Control Device: 3 Gang 3etg Taklampe -2 to 40% (40)
feb-22 20.26.40   Device Control Device: 3 Gang 3etg Taklampe -1 to 40% (40)
feb-22 20.26.40   Event Remove Delayed Device Action Removed event: Delayed Actions 3etg Vegglampe (Delayed Action)
feb-22 20.26.40   Event Remove Delayed Device Action Removed event: Delayed Actions 3etg Vegglampe (Delayed Action)
feb-22 20.26.40   Event Remove Delayed Device Action Removed event: Delayed Actions 3etg Vegglampe (Delayed Action)
feb-22 20.26.40   Event Remove Delayed Device Action Removed event: Delayed Actions 3etg Vegglampe (Delayed Action)
feb-22 20.26.40   Event Event Trigger "3 etg - Lys Gang - IKEA Gang Kveld - IKEA"
feb-22 20.26.40   Z-Wave Device: 3 Gang Home Security - Gang Set to NOTIFICATION for type Home Security, Event: Motion Detected
feb-22 20.26.02   Info System connected to MyHS Service successfully with license ID 117690.
feb-22 20.26.02   Info System connected to MyHS Service, waiting for acknowledge...
feb-22 20.25.55   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100E3025322048C2E0003000010650000000000
feb-22 20.25.55   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 227
feb-22 20.25.55   RFXCOM Transceiver #1 alive check, seq# E3
feb-22 20.25.09   Z-Wave Device: 2 Stue kW Hours 1 - Tak Lys Set to 23,23 (23,23 kW Hours)
feb-22 20.25.02   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100E2025322048C2E0003000010650000000000
feb-22 20.25.02   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 226
feb-22 20.25.02   RFXCOM Transceiver #1 alive check, seq# E2
feb-22 20.24.29   Z-Wave Device: 3 Gang Sensor Binary - Gang Set to Off/Closed/No Motion
feb-22 20.24.29   Z-Wave Device: 3 Bad Sensor Binary - Bad Set to Off/Closed/No Motion
feb-22 20.24.24   Z-Wave Device: 3 Gang Home Security - Gang Set to NOTIFICATION for type Home Security, Event: No Event
feb-22 20.24.23   Z-Wave Device: 3 Bad Home Security - Bad Set to NOTIFICATION for type Home Security, Event: No Event
feb-22 20.24.10   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100E1025322048C2E0003000010650000000000
feb-22 20.24.10   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 225
feb-22 20.24.10   RFXCOM Transceiver #1 alive check, seq# E1
feb-22 20.23.52   Device Control Device: 3 Gang 3etg Vegglampe to 50% (50)
feb-22 20.23.52   Device Control Device: 3 Gang 3etg Taklampe -3 to 40% (40)
feb-22 20.23.52   Device Control Device: 3 Gang 3etg Taklampe -2 to 40% (40)
feb-22 20.23.52   Device Control Device: 3 Gang 3etg Taklampe -1 to 40% (40)
feb-22 20.23.52   Event Remove Delayed Device Action Removed event: Delayed Actions 3etg Vegglampe (Delayed Action)
feb-22 20.23.52   Event Remove Delayed Device Action Removed event: Delayed Actions 3etg Vegglampe (Delayed Action)
feb-22 20.23.52   Event Remove Delayed Device Action Removed event: Delayed Actions 3etg Vegglampe (Delayed Action)
feb-22 20.23.52   Event Remove Delayed Device Action Removed event: Delayed Actions 3etg Vegglampe (Delayed Action)
feb-22 20.23.52   Event Event Trigger "3 etg - Lys Gang - IKEA Gang Kveld - IKEA"
feb-22 20.23.52   Z-Wave Device: 3 Gang Home Security - Gang Set to NOTIFICATION for type Home Security, Event: Motion Detected
feb-22 20.23.17   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100E0025322048C2E0003000010650000000000
feb-22 20.23.17   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 224
feb-22 20.23.17   RFXCOM Transceiver #1 alive check, seq# E0
feb-22 20.22.25   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100DF025322048C2E0003000010650000000000
feb-22 20.22.25   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 223
feb-22 20.22.25   RFXCOM Transceiver #1 alive check, seq# DF
feb-22 20.21.32   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100DE025322048C2E0003000010650000000000
feb-22 20.21.32   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 222
feb-22 20.21.32   RFXCOM Transceiver #1 alive check, seq# DE
feb-22 20.20.39   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100DD025322048C2E0003000010650000000000
feb-22 20.20.39   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 221
feb-22 20.20.39   RFXCOM Transceiver #1 alive check, seq# DD
feb-22 20.20.17   Z-Wave Device: 2 Stue kW Hours 1 - Tak Lys Set to 23,22 (23,22 kW Hours)
feb-22 20.20.17   Z-Wave Device: 3 Bad Power - Tak Lys Set to 77,6 (W)
feb-22 20.19.47   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100DC025322048C2E0003000010650000000000
feb-22 20.19.47   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 220
feb-22 20.19.47   RFXCOM Transceiver #1 alive check, seq# DC
feb-22 20.18.54   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100DB025322048C2E0003000010650000000000
feb-22 20.18.54   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 219
feb-22 20.18.54   RFXCOM Transceiver #1 alive check, seq# DB
feb-22 20.18.02   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100DA025322048C2E0003000010650000000000
feb-22 20.18.02   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 218
feb-22 20.18.02   RFXCOM Transceiver #1 alive check, seq# DA
feb-22 20.17.09   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100D9025322048C2E0003000010650000000000
feb-22 20.17.09   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 217
feb-22 20.17.09   RFXCOM Transceiver #1 alive check, seq# D9
feb-22 20.17.03   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to 50% (50)
feb-22 20.17.03   Event Remove Delayed Device Action Removed event: Delayed Actions Switch Multilevel 1 - Tak Lys (Delayed Action) - 1
feb-22 20.17.03   Event Event Trigger "3 etg - Lys bad Bad Kveld"
feb-22 20.17.03   Z-Wave Device: 3 Bad Home Security - Bad Set to NOTIFICATION for type Home Security, Event: Motion Detected
feb-22 20.16.17   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100D8025322048C2E0003000010650000000000
feb-22 20.16.17   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 216
feb-22 20.16.17   RFXCOM Transceiver #1 alive check, seq# D8
feb-22 20.15.24   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100D7025322048C2E0003000010650000000000
feb-22 20.15.24   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 215
feb-22 20.15.24   RFXCOM Transceiver #1 alive check, seq# D7
feb-22 20.14.36   Z-Wave Device: 1 Kino kW Hours - Biljard Lys Set to 22,01 (22,01 kW Hours)
feb-22 20.14.32   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100D6025322048C2E0003000010650000000000
feb-22 20.14.32   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 214
feb-22 20.14.32   RFXCOM Transceiver #1 alive check, seq# D6
feb-22 20.13.39   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100D5025322048C2E0003000010650000000000
feb-22 20.13.39   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 213
feb-22 20.13.39   RFXCOM Transceiver #1 alive check, seq# D5
feb-22 20.13.00   Z-Wave Device: 3 Bad Sensor Binary - Bad Set to On/Open/Motion
feb-22 20.12.46   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 040201D400
feb-22 20.12.46   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 040201D300
feb-22 20.12.45   Device Control Device: 1 Kino Nexa MYCR-3500_1 - Stikk - Grønt Lys to Off (0)
feb-22 20.12.45   Device Control Device: 1 Kino Nexa MYCR-3500_1 - Stikk - Grønt Lys to On (100)
feb-22 20.12.44   Event Event Trigger "Dør & Vindu sensorer - Group con & Actions Gang"
feb-22 20.12.44   Z-Wave Device: 2 Gang Sensor Binary - Gang Set to On/Open/Motion
feb-22 20.12.44   Device Control Device: 3 Gang 3etg Vegglampe to 50% (50)
feb-22 20.12.44   Device Control Device: 3 Gang 3etg Taklampe -3 to 40% (40)
feb-22 20.12.44   Device Control Device: 3 Gang 3etg Taklampe -2 to 40% (40)
feb-22 20.12.44   Device Control Device: 3 Gang 3etg Taklampe -1 to 40% (40)
feb-22 20.12.44   Event Remove Delayed Device Action Removed event: Delayed Actions 3etg Vegglampe (Delayed Action)
feb-22 20.12.44   Event Remove Delayed Device Action Removed event: Delayed Actions 3etg Vegglampe (Delayed Action)
feb-22 20.12.44   Event Remove Delayed Device Action Removed event: Delayed Actions 3etg Vegglampe (Delayed Action)
feb-22 20.12.44   Event Remove Delayed Device Action Removed event: Delayed Actions 3etg Vegglampe (Delayed Action)
feb-22 20.12.44   Event Event Trigger "3 etg - Lys Gang - IKEA Gang Kveld - IKEA"
feb-22 20.12.44   Z-Wave Device: 2 Gang Home Security - Gang Set to NOTIFICATION for type Home Security, Event: Motion Detected
feb-22 20.12.35   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to 50% (50)
feb-22 20.12.35   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 0B11005101D4D50601010F60
feb-22 20.12.35   Event Remove Delayed Device Action Removed event: Delayed Actions Switch Multilevel 1 - Tak Lys (Delayed Action) - 1
feb-22 20.12.35   RFXCOM 37 (Display_E_a) Device:AC[1D4D506-1]a Cmd:100
feb-22 20.12.35   Event Event Trigger "3 etg - Lys bad Bad Kveld"
feb-22 20.12.05   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100D2025322048C2E0003000010650000000000
feb-22 20.12.05   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 210
feb-22 20.12.05   RFXCOM Transceiver #1 alive check, seq# D2
feb-22 20.12.04   Z-Wave Device: 2 Gang Temperature - Gang Set to 22,3 (C)
feb-22 20.11.30   Z-Wave Device: 1 Kino Power - Biljard Lys Set to 123,3 (W)
feb-22 20.11.12   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100D1025322048C2E0003000010650000000000
feb-22 20.11.12   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 209
feb-22 20.11.12   RFXCOM Transceiver #1 alive check, seq# D1
feb-22 20.10.34   Z-Wave Device: 2 Gang Sensor Binary - Gang Set to Off/Closed/No Motion
feb-22 20.10.33   Z-Wave Device: 2 Gang Home Security - Gang Set to NOTIFICATION for type Home Security, Event: No Event
feb-22 20.10.25   Z-Wave Device: 2 Stue kW Hours 1 - Tak Lys Set to 23,21 (23,21 kW Hours)
feb-22 20.10.25   Z-Wave Device: 3 Bad Power - Tak Lys Set to 77,9 (W)
feb-22 20.10.19   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 0B11005001D4D50601000060
feb-22 20.10.19   RFXCOM 37 (Display_E_a) Device:AC[1D4D506-1]a Cmd:0
feb-22 20.10.16   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 0B11004F01D4D50601010F60
feb-22 20.10.16   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to 50% (50)
feb-22 20.10.16   Event Remove Delayed Device Action Removed event: Delayed Actions Switch Multilevel 1 - Tak Lys (Delayed Action) - 1
feb-22 20.10.16   Event Event Trigger "3 etg - Lys bad Bad Kveld"
feb-22 20.10.16   RFXCOM 37 (Display_E_a) Device:AC[1D4D506-1]a Cmd:100
feb-22 20.10.06   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100D0025322048C2E0003000010650000000000
feb-22 20.10.06   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 208
feb-22 20.10.06   RFXCOM Transceiver #1 alive check, seq# D0
feb-22 20.10.03   Device Control Device: 3 Gang 3etg Vegglampe to 50% (50)
feb-22 20.10.03   Device Control Device: 3 Gang 3etg Taklampe -3 to 40% (40)
feb-22 20.10.03   Device Control Device: 3 Gang 3etg Taklampe -2 to 40% (40)
feb-22 20.10.03   Device Control Device: 3 Gang 3etg Taklampe -1 to 40% (40)
feb-22 20.10.03   Event Remove Delayed Device Action Removed event: Delayed Actions 3etg Vegglampe (Delayed Action)
feb-22 20.10.03   Event Remove Delayed Device Action Removed event: Delayed Actions 3etg Vegglampe (Delayed Action)
feb-22 20.10.03   Event Remove Delayed Device Action Removed event: Delayed Actions 3etg Vegglampe (Delayed Action)
feb-22 20.10.03   Event Remove Delayed Device Action Removed event: Delayed Actions 3etg Vegglampe (Delayed Action)
feb-22 20.10.03   Event Event Trigger "3 etg - Lys Gang - IKEA Gang Kveld - IKEA"
feb-22 20.10.03   Z-Wave Device: 2 Gang Home Security - Gang Set to NOTIFICATION for type Home Security, Event: Motion Detected
feb-22 20.09.51   Z-Wave Device: 2 Stue Home Security - Egen Set to NOTIFICATION for type Home Security, Event: No Event
feb-22 20.09.13   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100CF025322048C2E0003000010650000000000
feb-22 20.09.13   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 207
feb-22 20.09.13   RFXCOM Transceiver #1 alive check, seq# CF
feb-22 20.08.21   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100CE025322048C2E0003000010650000000000
feb-22 20.08.21   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 206
feb-22 20.08.21   RFXCOM Transceiver #1 alive check, seq# CE
feb-22 20.07.28   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100CD025322048C2E0003000010650000000000
feb-22 20.07.28   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 205
feb-22 20.07.28   RFXCOM Transceiver #1 alive check, seq# CD
feb-22 20.06.36   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 040201CC00
feb-22 20.06.35   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 040201CB00
feb-22 20.06.34   Device Control Device: 1 Kino Nexa MYCR-3500_1 - Stikk - Grønt Lys to Off (0)
feb-22 20.06.34   Device Control Device: 1 Kino Nexa MYCR-3500_1 - Stikk - Grønt Lys to On (100)
feb-22 20.06.33   Event Event Trigger "Dør & Vindu sensorer - Group con & Actions Gang"
feb-22 20.06.33   Z-Wave Device: 2 Gang Sensor Binary - Gang Set to On/Open/Motion
feb-22 20.06.25   Device Control Device: 2 Stue Switch Multilevel 1 - Tak Lys to 40% (40)
feb-22 20.06.25   Event Remove Delayed Device Action Removed event: Delayed Actions Switch Multilevel 1 - Tak Lys (Delayed Action)
feb-22 20.06.25   Event Event Trigger "2 etg - Lys Stue - testing Stue Kveld"
feb-22 20.06.25   Z-Wave Device: 2 Stue Home Security - Egen Set to NOTIFICATION for type Home Security, Event: Motion Detected
feb-22 20.05.57   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100CA025322048C2E0003000010650000000000
feb-22 20.05.57   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 202
feb-22 20.05.57   RFXCOM Transceiver #1 alive check, seq# CA
feb-22 20.05.05   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100C9025322048C2E0003000010650000000000
feb-22 20.05.05   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 201
feb-22 20.05.04   RFXCOM Transceiver #1 alive check, seq# C9
feb-22 20.04.12   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100C8025322048C2E0003000010650000000000
feb-22 20.04.12   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 200
feb-22 20.04.12   RFXCOM Transceiver #1 alive check, seq# C8
feb-22 20.03.30   Z-Wave Device: 2 Stue kW Hours 1 - Tak Lys Set to 23,2 (23,2 kW Hours)
feb-22 20.03.19   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100C7025322048C2E0003000010650000000000
feb-22 20.03.19   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 199
feb-22 20.03.19   RFXCOM Transceiver #1 alive check, seq# C7
feb-22 20.02.27   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100C6025322048C2E0003000010650000000000
feb-22 20.02.27   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 198
feb-22 20.02.27   RFXCOM Transceiver #1 alive check, seq# C6
feb-22 20.02.06   Z-Wave Device: 3 Bad Sensor Binary - Bad Set to Off/Closed/No Motion
feb-22 20.02.06   Z-Wave Device: 3 Gang Home Security - Gang Set to NOTIFICATION for type Home Security, Event: No Event
feb-22 20.02.06   Z-Wave Device: 3 Bad Home Security - Bad Set to NOTIFICATION for type Home Security, Event: No Event
feb-22 20.02.03   Z-Wave Device: 3 Bad Power - Tak Lys Set to 79,5 (W)
feb-22 20.02.02   Z-Wave Device: 2 Gang Sensor Binary - Gang Set to Off/Closed/No Motion
feb-22 20.02.02   Z-Wave Device: 2 Gang Home Security - Gang Set to NOTIFICATION for type Home Security, Event: No Event
feb-22 20.01.59   Z-Wave Device: 3 Bad Power - Tak Lys Set to 81,7 (W)
feb-22 20.01.37   Z-Wave Device: 3 Bad Sensor Binary - Bad Set to On/Open/Motion
feb-22 20.01.36   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to 50% (50)
feb-22 20.01.36   Event Event Trigger "3 etg - Lys bad Bad Kveld"
feb-22 20.01.36   Z-Wave Device: 3 Bad Home Security - Bad Set to NOTIFICATION for type Home Security, Event: Motion Detected
feb-22 20.01.36   Z-Wave Device: 3 Gang Sensor Binary - Gang Set to On/Open/Motion
feb-22 20.01.34   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 040201C500
feb-22 20.01.34   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 040201C400
feb-22 20.01.33   Device Control Device: 1 Kino Nexa MYCR-3500_1 - Stikk - Grønt Lys to Off (0)
feb-22 20.01.33   Device Control Device: 1 Kino Nexa MYCR-3500_1 - Stikk - Grønt Lys to On (100)
feb-22 20.01.32   Event Event Trigger "Dør & Vindu sensorer - Group con & Actions Gang"
feb-22 20.01.32   Z-Wave Device: 2 Gang Sensor Binary - Gang Set to On/Open/Motion
feb-22 20.01.22   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100C3025322048C2E0003000010650000000000
feb-22 20.01.22   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 195
feb-22 20.01.22   RFXCOM Transceiver #1 alive check, seq# C3
feb-22 20.01.22   Z-Wave Device: 3 Bad General Purpose Alarm - Bad Set to NO ALARM (0)
feb-22 20.01.16   Z-Wave Device: 3 Bad Home Security - Bad Set to NOTIFICATION for type Home Security, Event: No Event
feb-22 20.00.29   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100C2025322048C2E0003000010650000000000
feb-22 20.00.29   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 194
feb-22 20.00.29   RFXCOM Transceiver #1 alive check, seq# C2
feb-22 19.59.37   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100C1025322048C2E0003000010650000000000
feb-22 19.59.37   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 193
feb-22 19.59.37   RFXCOM Transceiver #1 alive check, seq# C1
feb-22 19.58.56   Z-Wave Device: 3 Gang Sensor Binary - Gang Set to Off/Closed/No Motion
feb-22 19.58.47   Z-Wave Device: 2 Gang Sensor Binary - Gang Set to Off/Closed/No Motion
feb-22 19.58.44   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100C0025322048C2E0003000010650000000000
feb-22 19.58.44   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 192
feb-22 19.58.44   RFXCOM Transceiver #1 alive check, seq# C0
feb-22 19.58.21   Z-Wave Device: 2 Stue Home Security - Egen Set to NOTIFICATION for type Home Security, Event: No Event
feb-22 19.58.18   Z-Wave Device: 2 Stue Watts 1 - Tak Lys Set to 81,5 (81,5 Watts)
feb-22 19.58.15   Z-Wave Device: 2 Stue Power - Tak Lys Set to 81,5 (W)
feb-22 19.58.08   Z-Wave Device: 3 Gang Sensor Binary - Gang Set to On/Open/Motion
feb-22 19.58.07   Device Control Device: 2 Stue Switch Multilevel 1 - Tak Lys to 40% (40)
feb-22 19.58.07   Event Event Trigger "2 etg - Lys Stue - testing Stue Kveld"
feb-22 19.58.07   Z-Wave Device: 2 Stue Home Security - Egen Set to NOTIFICATION for type Home Security, Event: Motion Detected
feb-22 19.58.07   Device Control Device: 3 Gang 3etg Vegglampe to 50% (50)
feb-22 19.58.07   Device Control Device: 3 Gang 3etg Taklampe -3 to 40% (40)
feb-22 19.58.07   Device Control Device: 3 Gang 3etg Taklampe -2 to 40% (40)
feb-22 19.58.07   Device Control Device: 3 Gang 3etg Taklampe -1 to 40% (40)
feb-22 19.58.07   Event Event Trigger "3 etg - Lys Gang - IKEA Gang Kveld - IKEA"
feb-22 19.58.07   Z-Wave Device: 3 Gang Home Security - Gang Set to NOTIFICATION for type Home Security, Event: Motion Detected
feb-22 19.58.05   Z-Wave Device: 3 Gang Sensor Binary - Gang Set to Off/Closed/No Motion
feb-22 19.58.04   Z-Wave Device: 3 Gang Home Security - Gang Set to NOTIFICATION for type Home Security, Event: No Event
feb-22 19.57.52   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100BF025322048C2E0003000010650000000000
feb-22 19.57.52   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 191
feb-22 19.57.52   RFXCOM Transceiver #1 alive check, seq# BF
feb-22 19.57.33   Z-Wave Device: 2 Stue Watts 1 - Tak Lys Set to 81,6 (81,6 Watts)
feb-22 19.57.31   JowiHue Cannot find key for light Light 4 - Stativ (id=4) was it removed from the bridge?
feb-22 19.57.31   JowiHue Cannot find key for light Light 2 - TV Stue (id=2) was it removed from the bridge?
feb-22 19.56.59   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100BE025322048C2E0003000010650000000000
feb-22 19.56.59   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 190
feb-22 19.56.59   RFXCOM Transceiver #1 alive check, seq# BE
feb-22 19.56.48   Z-Wave Device: 2 Stue kW Hours 1 - Tak Lys Set to 23,19 (23,19 kW Hours)
feb-22 19.56.07   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100BD025322048C2E0003000010650000000000
feb-22 19.56.07   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 189
feb-22 19.56.07   RFXCOM Transceiver #1 alive check, seq# BD
feb-22 19.55.14   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100BC025322048C2E0003000010650000000000
feb-22 19.55.14   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 188
feb-22 19.55.14   RFXCOM Transceiver #1 alive check, seq# BC
feb-22 19.54.21   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100BB025322048C2E0003000010650000000000
feb-22 19.54.21   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 187
feb-22 19.54.21   RFXCOM Transceiver #1 alive check, seq# BB
feb-22 19.53.58   Z-Wave Device: 2 TV Stue Power - Tak Lys Set to 113,8 (W)
feb-22 19.53.31   Warning Plugin Z-Wave is not responding but it is still running, not restarting yet.
feb-22 19.53.29   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100BA025322048C2E0003000010650000000000
feb-22 19.53.29   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 186
feb-22 19.53.29   RFXCOM Transceiver #1 alive check, seq# BA
feb-22 19.53.24   Error Getting web page from plugin page ZWaveWho:Object reference not set to an instance of an object.
feb-22 19.53.23   Device Control Device: 2 TV Stue Switch Multilevel 1 - Tak Lys to (value)% (66) by/from: CAPI Control Handler
feb-22 19.53.20   Device Control Device: 2 TV Stue Switch Multilevel 1 - Tak Lys to (value)% (32) by/from: CAPI Control Handler
feb-22 19.52.45   Device Control Device: 2 TV Stue Switch Multilevel 1 - Tak Lys to (value)% (49) by/from: CAPI Control Handler
feb-22 19.52.39   Device Control Device: 2 TV Stue Switch Multilevel 1 - Tak Lys to Off (0) by/from: CAPI Control Handler
feb-22 19.52.38   Device Control Device: 2 TV Stue Switch Multilevel 1 - Tak Lys to (value)% (49) by/from: CAPI Control Handler
feb-22 19.52.36   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100B9025322048C2E0003000010650000000000
feb-22 19.52.36   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 185
feb-22 19.52.36   RFXCOM Transceiver #1 alive check, seq# B9
feb-22 19.52.30   Device Control Device: 2 TV Stue Switch Multilevel 1 - Tak Lys to (value)% (49) by/from: CAPI Control Handler
feb-22 19.51.44   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100B8025322048C2E0003000010650000000000
feb-22 19.51.44   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 184
feb-22 19.51.44   RFXCOM Transceiver #1 alive check, seq# B8
feb-22 19.50.51   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100B7025322048C2E0003000010650000000000
feb-22 19.50.51   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 183
feb-22 19.50.51   RFXCOM Transceiver #1 alive check, seq# B7
feb-22 19.50.08   Z-Wave Device: 2 Stue kW Hours 1 - Tak Lys Set to 23,18 (23,18 kW Hours)
feb-22 19.49.59   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100B6025322048C2E0003000010650000000000
feb-22 19.49.59   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 182
feb-22 19.49.59   RFXCOM Transceiver #1 alive check, seq# B6
feb-22 19.49.53   Z-Wave Device: 3 Bad General Purpose Alarm - Bad Set to IN ALARM (255)
feb-22 19.49.52   Z-Wave Device: 3 Bad Home Security - Bad Set to NOTIFICATION for type Home Security, Event: Tampering Cover Removed
feb-22 19.49.06   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100B5025322048C2E0003000010650000000000
feb-22 19.49.06   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 181
feb-22 19.49.06   RFXCOM Transceiver #1 alive check, seq# B5
feb-22 19.48.14   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100B4025322048C2E0003000010650000000000
feb-22 19.48.14   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 180
feb-22 19.48.13   RFXCOM Transceiver #1 alive check, seq# B4
feb-22 19.47.21   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100B3025322048C2E0003000010650000000000
feb-22 19.47.21   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 179
feb-22 19.47.21   RFXCOM Transceiver #1 alive check, seq# B3
feb-22 19.46.28   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100B2025322048C2E0003000010650000000000
feb-22 19.46.28   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 178
feb-22 19.46.28   RFXCOM Transceiver #1 alive check, seq# B2
feb-22 19.46.24   Event Deleting event after run: "Delayed Actions Switch Multilevel 1 - Tak Lys (Delayed Action)"
feb-22 19.46.24   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to Off (0)
feb-22 19.46.24   Event Event Trigger "Delayed Actions Switch Multilevel 1 - Tak Lys (Delayed Action)"
feb-22 19.45.36   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100B1025322048C2E0003000010650000000000
feb-22 19.45.36   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 177
feb-22 19.45.36   RFXCOM Transceiver #1 alive check, seq# B1
feb-22 19.44.43   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100B0025322048C2E0003000010650000000000
feb-22 19.44.43   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 176
feb-22 19.44.43   RFXCOM Transceiver #1 alive check, seq# B0
feb-22 19.43.51   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100AF025322048C2E0003000010650000000000
feb-22 19.43.51   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 175
feb-22 19.43.51   RFXCOM Transceiver #1 alive check, seq# AF
feb-22 19.43.35   Event Deleting event after run: "Delayed Actions 3etg Vegglampe (Delayed Action)"
feb-22 19.43.35   Device Control Device: 3 Gang 3etg Vegglampe to Off (0)
feb-22 19.43.35   Device Control Device: 3 Gang 3etg Taklampe -3 to Off (0)
feb-22 19.43.35   Device Control Device: 3 Gang 3etg Taklampe -2 to Off (0)
feb-22 19.43.35   Device Control Device: 3 Gang 3etg Taklampe -1 to Off (0)
feb-22 19.43.35   Event Event Trigger "Delayed Actions 3etg Vegglampe (Delayed Action)"
feb-22 19.43.14   Z-Wave Device: 3 Bad Luminance Set to 3 (Lux)
feb-22 19.42.58   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100AE025322048C2E0003000010650000000000
feb-22 19.42.58   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 174
feb-22 19.42.58   RFXCOM Transceiver #1 alive check, seq# AE
feb-22 19.42.56   Z-Wave Device: 3 Bad Temperature - Bad Set to 24,5 (C)
feb-22 19.42.06   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100AD025322048C2E0003000010650000000000
feb-22 19.42.06   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 173
feb-22 19.42.06   RFXCOM Transceiver #1 alive check, seq# AD
feb-22 19.41.31   Z-Wave Device: 3 Bad Luminance Set to 4 (Lux)
feb-22 19.41.13   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100AC025322048C2E0003000010650000000000
feb-22 19.41.13   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 172
feb-22 19.41.13   RFXCOM Transceiver #1 alive check, seq# AC
feb-22 19.40.20   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100AB025322048C2E0003000010650000000000
feb-22 19.40.20   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 171
feb-22 19.40.20   RFXCOM Transceiver #1 alive check, seq# AB
feb-22 19.39.28   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100AA025322048C2E0003000010650000000000
feb-22 19.39.28   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 170
feb-22 19.39.28   RFXCOM Transceiver #1 alive check, seq# AA
feb-22 19.38.35   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100A9025322048C2E0003000010650000000000
feb-22 19.38.35   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 169
feb-22 19.38.35   RFXCOM Transceiver #1 alive check, seq# A9
feb-22 19.37.43   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100A8025322048C2E0003000010650000000000
feb-22 19.37.43   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 168
feb-22 19.37.43   RFXCOM Transceiver #1 alive check, seq# A8
feb-22 19.36.50   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100A7025322048C2E0003000010650000000000
feb-22 19.36.50   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 167
feb-22 19.36.50   RFXCOM Transceiver #1 alive check, seq# A7
feb-22 19.35.58   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100A6025322048C2E0003000010650000000000
feb-22 19.35.58   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 166
feb-22 19.35.58   RFXCOM Transceiver #1 alive check, seq# A6
feb-22 19.35.56   Z-Wave Device: 3 Bad General Purpose Alarm - Bad Set to NO ALARM (0)
feb-22 19.35.56   Z-Wave Device: 3 Bad Home Security - Bad Set to NOTIFICATION for type Home Security, Event: No Event
feb-22 19.35.05   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100A5025322048C2E0003000010650000000000
feb-22 19.35.05   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 165
feb-22 19.35.05   RFXCOM Transceiver #1 alive check, seq# A5
feb-22 19.34.43   Z-Wave Device: 2 Stue kW Hours 1 - Tak Lys Set to 23,16 (23,16 kW Hours)
feb-22 19.34.36   Z-Wave Optimization complete.
feb-22 19.34.36   Z-Wave ------------------------------------------------------
feb-22 19.34.36   Z-Wave Done. The optimization was not executed as the node cannot be reached.
feb-22 19.34.31   Z-Wave Optimizing node 22 (Node 22 Z-Wave Fibaro Switch)...
feb-22 19.34.31   Z-Wave ------------------------------------------------------
feb-22 19.34.26   Z-Wave Done. The optimization was not executed as the node cannot be reached.
feb-22 19.34.18   Z-Wave Optimizing node 18 (Node 18 Z-Wave Fibaro Switch)...
feb-22 19.34.18   Z-Wave ------------------------------------------------------
feb-22 19.34.18   Z-Wave Done.
feb-22 19.34.14   Z-Wave Optimizing node 11 (1 Kino Fibaro Switch - Biljard Lys)...
feb-22 19.34.14   Z-Wave ------------------------------------------------------
feb-22 19.34.14   Z-Wave Done.
feb-22 19.34.13   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100A4025322048C2E0003000010650000000000
feb-22 19.34.13   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 164
feb-22 19.34.12   RFXCOM Transceiver #1 alive check, seq# A4
feb-22 19.34.10   Z-Wave Optimizing node 5 (3 Bad Fibaro Switch - Tak Lys)...
feb-22 19.34.10   Z-Wave ------------------------------------------------------
feb-22 19.34.05   Z-Wave Done. The optimization was not executed as the node cannot be reached.
feb-22 19.33.57   Z-Wave Optimizing node 4 (iKKE I BRUK iKKE I BRUK Fibaro Switch - Tak Lys)...
feb-22 19.33.57   Z-Wave ------------------------------------------------------
feb-22 19.33.57   Z-Wave Done.
feb-22 19.33.20   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100A3025322048C2E0003000010650000000000
feb-22 19.33.20   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 163
feb-22 19.33.20   RFXCOM Transceiver #1 alive check, seq# A3
feb-22 19.32.55   Z-Wave Warning Z-Wave Command SEND DATA(Node 5) cannot be carried out while network optimization is taking place.
feb-22 19.32.27   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100A2025322048C2E0003000010650000000000
feb-22 19.32.27   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 162
feb-22 19.32.27   RFXCOM Transceiver #1 alive check, seq# A2
feb-22 19.31.55   Z-Wave Warning Z-Wave Command SEND DATA(Node 2) cannot be carried out while network optimization is taking place.
feb-22 19.31.35   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 0B11004E01CFC38A02000070
feb-22 19.31.35   Device Control Device: 3 Gang 3etg Vegglampe to 100% (100)
feb-22 19.31.35   Device Control Device: 3 Gang 3etg Taklampe -3 to 100% (100)
feb-22 19.31.35   Device Control Device: 3 Gang 3etg Taklampe -2 to 100% (100)
feb-22 19.31.35   Device Control Device: 3 Gang 3etg Taklampe -1 to 100% (100)
feb-22 19.31.35   RFXCOM 37 (Display_E_a) Device:AC[1CFC38A-2]a Cmd:0
feb-22 19.31.35   Event Event Trigger "3 etg - Lys Gang - IKEA Gang Fylt LYS - IKEA"
feb-22 19.31.34   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 0B11004D01CFC38A02010F70
feb-22 19.31.34   RFXCOM 37 (Display_E_a) Device:AC[1CFC38A-2]a Cmd:100
feb-22 19.31.32   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 0B11004C01CFC38A02010F60
feb-22 19.31.32   RFXCOM 37 (Display_E_a) Device:AC[1CFC38A-2]a Cmd:100
feb-22 19.31.30   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 0B11004B01D4D50601000060
feb-22 19.31.30   RFXCOM 37 (Display_E_a) Device:AC[1D4D506-1]a Cmd:0
feb-22 19.31.24   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 0B11004A01D4D50601010F60
feb-22 19.31.24   Device Control Device: 3 Bad Switch Multilevel 1 - Tak Lys to 50% (50)
feb-22 19.31.24   RFXCOM 37 (Display_E_a) Device:AC[1D4D506-1]a Cmd:100
feb-22 19.31.24   Event Event Trigger "3 etg - Lys bad Bad Kveld"
feb-22 19.31.20   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 0B11004901CFC38A02010F60
feb-22 19.31.20   RFXCOM 37 (Display_E_a) Device:AC[1CFC38A-2]a Cmd:100
feb-22 19.30.55   Z-Wave Warning Z-Wave Command SEND DATA(Node 22) cannot be carried out while network optimization is taking place.
feb-22 19.30.48   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100A1025322048C2E0003000010650000000000
feb-22 19.30.48   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 161
feb-22 19.30.48   RFXCOM Transceiver #1 alive check, seq# A1
feb-22 19.29.56   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 140100A0025322048C2E0003000010650000000000
feb-22 19.29.56   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 160
feb-22 19.29.56   RFXCOM Transceiver #1 alive check, seq# A0
feb-22 19.29.55   Z-Wave Warning Z-Wave Command SEND DATA(Node 22) cannot be carried out while network optimization is taking place.
feb-22 19.29.03   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 1401009F025322048C2E0003000010650000000000
feb-22 19.29.03   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 159
feb-22 19.29.03   RFXCOM Transceiver #1 alive check, seq# 9F
feb-22 19.28.55   Z-Wave Warning Z-Wave Command SEND DATA(Node 22) cannot be carried out while network optimization is taking place.
feb-22 19.28.11   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 1401009E025322048C2E0003000010650000000000
feb-22 19.28.11   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 158
feb-22 19.28.11   RFXCOM Transceiver #1 alive check, seq# 9E
feb-22 19.27.57   Z-Wave Optimizing node 3 (2 TV Stue Fibaro Switch - Tak Lys)...
feb-22 19.27.57   Z-Wave ------------------------------------------------------
feb-22 19.27.57   Z-Wave Done.
feb-22 19.27.55   Z-Wave Warning Z-Wave Command SEND DATA(Node 22) cannot be carried out while network optimization is taking place.
feb-22 19.27.18   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 1401009D025322048C2E0003000010650000000000
feb-22 19.27.18   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 157
feb-22 19.27.18   RFXCOM Transceiver #1 alive check, seq# 9D
feb-22 19.26.55   Z-Wave Warning Z-Wave Command SEND DATA(Node 22) cannot be carried out while network optimization is taking place.
feb-22 19.26.26   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 1401009C025322048C2E0003000010650000000000
feb-22 19.26.26   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 156
feb-22 19.26.26   RFXCOM Transceiver #1 alive check, seq# 9C
feb-22 19.25.55   Z-Wave Warning Z-Wave Command SEND DATA(Node 22) cannot be carried out while network optimization is taking place.
feb-22 19.25.33   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 1401009B025322048C2E0003000010650000000000
feb-22 19.25.33   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 155
feb-22 19.25.33   RFXCOM Transceiver #1 alive check, seq# 9B
feb-22 19.25.33   Event Deleting event after run: "Delayed Actions Switch Multilevel 1 - Tak Lys (Delayed Action)"
feb-22 19.25.33   Device Control Device: 2 Stue Switch Multilevel 1 - Tak Lys to Off (0)
feb-22 19.25.33   Event Event Trigger "Delayed Actions Switch Multilevel 1 - Tak Lys (Delayed Action)"
feb-22 19.24.55   Z-Wave Warning Z-Wave Command SEND DATA(Node 22) cannot be carried out while network optimization is taking place.
feb-22 19.24.47   Z-Wave Optimizing node 2 (2 Stue Fibaro Switch - Tak Lys)...
feb-22 19.24.47   Z-Wave There are approximately 7 nodes to optimize.
feb-22 19.24.47   Z-Wave Optimize complete wait time is 0:24
feb-22 19.24.47   Z-Wave Warning Device 1 Trim Rom Fibaro Notification Sensor - Trim Rom Dør (21) will not be optimized because it is a non-listening device. Please use Optimize from the device properties for this device after placing the node in an awake state.
feb-22 19.24.47   Z-Wave Warning Device 1 Kino Fibaro Notification Sensor - Ytterdør (20) will not be optimized because it is a non-listening device. Please use Optimize from the device properties for this device after placing the node in an awake state.
feb-22 19.24.47   Z-Wave Warning Device Multi bryter 1 Z-Wave Aeon Labs Wall Controller (19) will not be optimized because it is a non-listening device. Please use Optimize from the device properties for this device after placing the node in an awake state.
feb-22 19.24.47   Z-Wave Warning Device Garasje Garasje Philio Notification Sensor - Egen (14) will not be optimized because it is a non-listening device. Please use Optimize from the device properties for this device after placing the node in an awake state.
feb-22 19.24.47   Z-Wave Warning Device 2 Stue Everspring Notification Sensor - Egen (12) will not be optimized because it is a non-listening device. Please use Optimize from the device properties for this device after placing the node in an awake state.
feb-22 19.24.47   Z-Wave Warning Device 2 TV Stue Fibaro Motion Sensor - TV Stue (10) will not be optimized because it is a non-listening device. Please use Optimize from the device properties for this device after placing the node in an awake state.
feb-22 19.24.47   Z-Wave Warning Device 3 Bad Fibaro Motion Sensor - Bad (9) will not be optimized because it is a non-listening device. Please use Optimize from the device properties for this device after placing the node in an awake state.
feb-22 19.24.47   Z-Wave Warning Device 3 Gang Fibaro Notification Sensor - Gang (8) will not be optimized because it is a non-listening device. Please use Optimize from the device properties for this device after placing the node in an awake state.
feb-22 19.24.47   Z-Wave Warning Device 2 Gang Fibaro Motion Sensor - Gang (7) will not be optimized because it is a non-listening device. Please use Optimize from the device properties for this device after placing the node in an awake state.
feb-22 19.24.47   Z-Wave Warning Device 1 Kino Fibaro Switch - Wall Stikk (6) will not be optimized because it is a non-listening device. Please use Optimize from the device properties for this device after placing the node in an awake state.
feb-22 19.24.47   Z-Wave Warning Device Node 1 Z-Wave ZMEEUZB1 (1) will not be optimized because it is a HomeSeer controller.
feb-22 19.24.47   Z-Wave Starting Z-Wave node neighbor update for all Z-Wave devices...
feb-22 19.24.41   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 1401009A025322048C2E0003000010650000000000
feb-22 19.24.41   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 154
feb-22 19.24.40   RFXCOM Transceiver #1 alive check, seq# 9A
feb-22 19.24.39   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.24.38   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.24.37   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.24.36   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.24.35   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.24.34   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.24.25   Warning Plugin Z-Wave is not responding but it is still running, not restarting yet.
feb-22 19.24.21   Error Calling HSEvent in plugin Z-Wave, Instance :Object reference not set to an instance of an object.
feb-22 19.24.09   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.24.08   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.24.07   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.24.06   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.24.05   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.24.04   Error Getting web page from plugin page ZWaveWho:Object reference not set to an instance of an object.
feb-22 19.23.48   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010099025322048C2E0003000010650000000000
feb-22 19.23.48   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 153
feb-22 19.23.48   RFXCOM Transceiver #1 alive check, seq# 99
feb-22 19.23.19   Error Calling HSEvent in plugin Z-Wave, Instance :Object reference not set to an instance of an object.
feb-22 19.23.13   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.23.11   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.23.09   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.23.08   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.23.07   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.23.07   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.22.55   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010098025322048C2E0003000010650000000000
feb-22 19.22.55   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 152
feb-22 19.22.55   RFXCOM Transceiver #1 alive check, seq# 98
feb-22 19.22.55   Warning Plugin Z-Wave is not responding but it is still running, not restarting yet.
feb-22 19.22.49   Error Calling HSEvent in plugin Z-Wave, Instance :Object reference not set to an instance of an object.
feb-22 19.22.43   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.22.41   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.22.39   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.22.38   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.22.37   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.22.36   Error Getting web page from plugin page ZWaveWho:Object reference not set to an instance of an object.
feb-22 19.22.25   Warning Plugin Z-Wave is not responding but it is still running, not restarting yet.
feb-22 19.22.19   Error Calling HSEvent in plugin Z-Wave, Instance :Object reference not set to an instance of an object.
feb-22 19.22.11   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.22.10   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.22.09   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.22.08   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.22.07   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.22.06   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.22.03   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010097025322048C2E0003000010650000000000
feb-22 19.22.03   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 151
feb-22 19.22.03   RFXCOM Transceiver #1 alive check, seq# 97
feb-22 19.21.55   Warning Plugin Z-Wave is not responding but it is still running, not restarting yet.
feb-22 19.21.41   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.21.40   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.21.39   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.21.38   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.21.37   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.21.36   Error Getting web page from plugin page ZWaveWho:Object reference not set to an instance of an object.
feb-22 19.21.10   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010096025322048C2E0003000010650000000000
feb-22 19.21.10   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 150
feb-22 19.21.10   RFXCOM Transceiver #1 alive check, seq# 96
feb-22 19.21.02   Z-Wave Device: 2 Stue kW Hours 1 - Tak Lys Set to 23,14 (23,14 kW Hours)
feb-22 19.20.55   Z-Wave Finished with Z-Wave device synchronization.
feb-22 19.20.55   Z-Wave Warning Device synchronization/creation aborted by timeout or by the user.
feb-22 19.20.55   Z-Wave Warning 0 out of 1 Child devices of node 22 were created with errors.
feb-22 19.20.55   Z-Wave Warning Z-Wave Sync, Child-Class-Create was aborted early by the user.
feb-22 19.20.55   Z-Wave Warning 0 out of 1 Child devices of node 21 were created with errors.
feb-22 19.20.55   Z-Wave Warning Z-Wave Sync, Child-Class-Create was aborted early by the user.
feb-22 19.20.55   Z-Wave Warning 0 out of 1 Child devices of node 20 were created with errors.
feb-22 19.20.55   Z-Wave Warning Z-Wave Sync, Child-Class-Create was aborted early by the user.
feb-22 19.20.55   Z-Wave Warning 0 out of 1 Child devices of node 19 were created with errors.
feb-22 19.20.55   Z-Wave Warning Z-Wave Sync, Child-Class-Create was aborted early by the user.
feb-22 19.20.55   Z-Wave Warning 0 out of 1 Child devices of node 18 were created with errors.
feb-22 19.20.55   Z-Wave Warning Z-Wave Sync, Child-Class-Create was aborted early by the user.
feb-22 19.20.32   Z-Wave Warning Instant status for Z-Wave device Node 18 Z-Wave Fibaro Switch (18) on Group 3 failed. Please rescan this device when communications are working better to try again.
feb-22 19.20.24   Z-Wave Enabling instant status for Z-Wave device Node 18 Z-Wave Fibaro Switch (18) on Group 3
feb-22 19.20.24   Z-Wave Warning Instant status for Z-Wave device Node 18 Z-Wave Fibaro Switch (18) on Group 2 failed. Please rescan this device when communications are working better to try again.
feb-22 19.20.18   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010095025322048C2E0003000010650000000000
feb-22 19.20.18   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 149
feb-22 19.20.18   RFXCOM Transceiver #1 alive check, seq# 95
feb-22 19.20.16   Z-Wave Enabling instant status for Z-Wave device Node 18 Z-Wave Fibaro Switch (18) on Group 2
feb-22 19.20.16   Z-Wave Warning 0 out of 1 Child devices of node 14 were created with errors.
feb-22 19.20.16   Z-Wave Warning Z-Wave Sync, Child-Class-Create was aborted early by the user.
feb-22 19.20.16   Z-Wave Warning 0 out of 1 Child devices of node 12 were created with errors.
feb-22 19.20.16   Z-Wave Warning Z-Wave Sync, Child-Class-Create was aborted early by the user.
feb-22 19.20.16   Z-Wave Warning 0 out of 1 Child devices of node 11 were created with errors.
feb-22 19.20.16   Z-Wave Warning Z-Wave Sync, Child-Class-Create was aborted early by the user.
feb-22 19.20.15   Z-Wave Assigning return route from node 1 to 1 Kino Fibaro Switch - Biljard Lys
feb-22 19.20.14   Z-Wave Enabling instant status for Z-Wave device 1 Kino Fibaro Switch - Biljard Lys (11) on Group 3
feb-22 19.20.13   Z-Wave Assigning return route from node 1 to 1 Kino Fibaro Switch - Biljard Lys
feb-22 19.20.11   Z-Wave Enabling instant status for Z-Wave device 1 Kino Fibaro Switch - Biljard Lys (11) on Group 2
feb-22 19.20.11   Z-Wave Warning 0 out of 1 Child devices of node 10 were created with errors.
feb-22 19.20.11   Z-Wave Warning Z-Wave Sync, Child-Class-Create was aborted early by the user.
feb-22 19.20.11   Z-Wave Warning 0 out of 1 Child devices of node 9 were created with errors.
feb-22 19.20.11   Z-Wave Warning Z-Wave Sync, Child-Class-Create was aborted early by the user.
feb-22 19.20.11   Z-Wave Warning 0 out of 1 Child devices of node 8 were created with errors.
feb-22 19.20.11   Z-Wave Warning Z-Wave Sync, Child-Class-Create was aborted early by the user.
feb-22 19.20.11   Z-Wave Warning 0 out of 1 Child devices of node 7 were created with errors.
feb-22 19.20.11   Z-Wave Warning Z-Wave Sync, Child-Class-Create was aborted early by the user.
feb-22 19.20.11   Z-Wave Warning 0 out of 1 Child devices of node 5 were created with errors.
feb-22 19.20.11   Z-Wave Warning Z-Wave Sync, Child-Class-Create was aborted early by the user.
feb-22 19.20.07   Z-Wave Getting association information for 3 Bad Fibaro Switch - Tak Lys
feb-22 19.20.06   Z-Wave Assigning return route from node 1 to 3 Bad Fibaro Switch - Tak Lys
feb-22 19.20.05   Z-Wave ZMEEUZB1: Adding association for Z-Wave device 3 Bad Fibaro Switch - Tak Lys (Node 5, Group 2, Endpoint 2) to HomeSeer
feb-22 19.20.04   Z-Wave Assigning return route from node 1 to 3 Bad Fibaro Switch - Tak Lys
feb-22 19.20.03   Z-Wave ZMEEUZB1: Adding association for Z-Wave device 3 Bad Fibaro Switch - Tak Lys (Node 5, Group 2, Endpoint 2) to HomeSeer
feb-22 19.20.02   Z-Wave Assigning return route from node 1 to 3 Bad Fibaro Switch - Tak Lys
feb-22 19.20.01   Z-Wave ZMEEUZB1: Adding association for Z-Wave device 3 Bad Fibaro Switch - Tak Lys (Node 5, Group 1, Endpoint 1) to HomeSeer
feb-22 19.20.00   Z-Wave Assigning return route from node 1 to 3 Bad Fibaro Switch - Tak Lys
feb-22 19.19.59   Z-Wave ZMEEUZB1: Adding association for Z-Wave device 3 Bad Fibaro Switch - Tak Lys (Node 5, Group 1, Endpoint 1) to HomeSeer
feb-22 19.19.59   Z-Wave Warning 0 out of 1 Child devices of node 4 were created with errors.
feb-22 19.19.59   Z-Wave Warning Z-Wave Sync, Child-Class-Create was aborted early by the user.
feb-22 19.19.59   Z-Wave Warning 0 out of 1 Child devices of node 3 were created with errors.
feb-22 19.19.59   Z-Wave Warning Z-Wave Sync, Child-Class-Create was aborted early by the user.
feb-22 19.19.56   Z-Wave Getting association information for 2 TV Stue Fibaro Switch - Tak Lys
feb-22 19.19.54   Z-Wave Assigning return route from node 1 to 2 TV Stue Fibaro Switch - Tak Lys
feb-22 19.19.53   Z-Wave ZMEEUZB1: Adding association for Z-Wave device 2 TV Stue Fibaro Switch - Tak Lys (Node 3, Group 2, Endpoint 2) to HomeSeer
feb-22 19.19.51   Z-Wave Assigning return route from node 1 to 2 TV Stue Fibaro Switch - Tak Lys
feb-22 19.19.50   Z-Wave ZMEEUZB1: Adding association for Z-Wave device 2 TV Stue Fibaro Switch - Tak Lys (Node 3, Group 2, Endpoint 2) to HomeSeer
feb-22 19.19.48   Z-Wave Assigning return route from node 1 to 2 TV Stue Fibaro Switch - Tak Lys
feb-22 19.19.48   Z-Wave ZMEEUZB1: Adding association for Z-Wave device 2 TV Stue Fibaro Switch - Tak Lys (Node 3, Group 1, Endpoint 1) to HomeSeer
feb-22 19.19.45   Z-Wave Assigning return route from node 1 to 2 TV Stue Fibaro Switch - Tak Lys
feb-22 19.19.44   Z-Wave ZMEEUZB1: Adding association for Z-Wave device 2 TV Stue Fibaro Switch - Tak Lys (Node 3, Group 1, Endpoint 1) to HomeSeer
feb-22 19.19.44   Z-Wave Warning 0 out of 1 Child devices of node 2 were created with errors.
feb-22 19.19.44   Z-Wave Warning Z-Wave Sync, Child-Class-Create was aborted early by the user.
feb-22 19.19.42   Z-Wave Getting association information for 2 Stue Fibaro Switch - Tak Lys
feb-22 19.19.40   Z-Wave Assigning return route from node 1 to 2 Stue Fibaro Switch - Tak Lys
feb-22 19.19.40   Z-Wave ZMEEUZB1: Adding association for Z-Wave device 2 Stue Fibaro Switch - Tak Lys (Node 2, Group 2, Endpoint 2) to HomeSeer
feb-22 19.19.39   Z-Wave Assigning return route from node 1 to 2 Stue Fibaro Switch - Tak Lys
feb-22 19.19.38   Z-Wave ZMEEUZB1: Adding association for Z-Wave device 2 Stue Fibaro Switch - Tak Lys (Node 2, Group 2, Endpoint 2) to HomeSeer
feb-22 19.19.37   Z-Wave Assigning return route from node 1 to 2 Stue Fibaro Switch - Tak Lys
feb-22 19.19.36   Z-Wave ZMEEUZB1: Adding association for Z-Wave device 2 Stue Fibaro Switch - Tak Lys (Node 2, Group 1, Endpoint 1) to HomeSeer
feb-22 19.19.35   Z-Wave Assigning return route from node 1 to 2 Stue Fibaro Switch - Tak Lys
feb-22 19.19.34   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.19.34   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.19.34   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.19.34   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.19.34   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.19.34   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.19.29   Z-Wave ZMEEUZB1: Adding association for Z-Wave device 2 Stue Fibaro Switch - Tak Lys (Node 2, Group 1, Endpoint 1) to HomeSeer
feb-22 19.19.29   Z-Wave Warning An error (B) was reported attempting to get multi-channel or multi-instance information from node 22
feb-22 19.19.25   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010094025322048C2E0003000010650000000000
feb-22 19.19.25   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 148
feb-22 19.19.25   RFXCOM Transceiver #1 alive check, seq# 94
feb-22 19.19.24   Warning Plugin Z-Wave is not responding but it is still running, not restarting yet.
feb-22 19.19.21   Z-Wave Error Node 21 did not provide Wake-Up Command Class information - it will not be processed further.
feb-22 19.19.13   Z-Wave Error Node 20 did not provide Wake-Up Command Class information - it will not be processed further.
feb-22 19.19.06   Z-Wave Warning An error (B) was reported attempting to get multi-channel or multi-instance information from node 19
feb-22 19.19.04   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.19.04   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.19.04   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.19.04   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.19.04   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.19.04   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.18.58   Z-Wave Error Exception creating Sensor Multilevel child device of node 18, GET for supported sensor types indicated failure.
feb-22 19.18.54   Warning Plugin Z-Wave is not responding but it is still running, not restarting yet.
feb-22 19.18.37   Z-Wave Error Node 14 did not provide Wake-Up Command Class information - it will not be processed further.
feb-22 19.18.34   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.18.34   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.18.34   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.18.34   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.18.34   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.18.34   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.18.33   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010093025322048C2E0003000010650000000000
feb-22 19.18.33   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 147
feb-22 19.18.33   RFXCOM Transceiver #1 alive check, seq# 93
feb-22 19.18.30   Z-Wave Error Node 12 did not provide Wake-Up Command Class information - it will not be processed further.
feb-22 19.18.24   Warning Plugin Z-Wave is not responding but it is still running, not restarting yet.
feb-22 19.18.04   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.18.04   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.18.04   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.18.04   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.18.04   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.18.04   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.18.02   Z-Wave Error Exception creating Sensor Multilevel child device of node 11, GET for supported sensor types indicated failure.
feb-22 19.17.53   Warning Plugin Z-Wave is not responding but it is still running, not restarting yet.
feb-22 19.17.40   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010092025322048C2E0003000010650000000000
feb-22 19.17.40   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 146
feb-22 19.17.40   RFXCOM Transceiver #1 alive check, seq# 92
feb-22 19.17.34   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.17.34   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.17.34   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.17.34   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.17.34   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.17.34   Error Getting web page from plugin page ZWaveWho:Object reference not set to an instance of an object.
feb-22 19.17.23   Warning Plugin Z-Wave is not responding but it is still running, not restarting yet.
feb-22 19.17.03   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.17.02   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.17.01   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.17.00   Z-Wave Node 11 Meter is Supported for Electric_meter, Type ELECTRIC_W, Scale is INSTANT
feb-22 19.17.00   Z-Wave Node 11 Meter is Supported for Electric_meter, Type ELECTRIC_kWh, Scale is ACCUMULATED
feb-22 19.17.00   Z-Wave Error Node 10 did not provide Wake-Up Command Class information - it will not be processed further.
feb-22 19.17.00   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.17.00   Error Calling HSEvent in plugin Z-Wave, Instance :Object reference not set to an instance of an object.
feb-22 19.16.59   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.16.59   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.16.53   Warning Plugin Z-Wave is not responding but it is still running, not restarting yet.
feb-22 19.16.48   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010091025322048C2E0003000010650000000000
feb-22 19.16.48   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 145
feb-22 19.16.47   RFXCOM Transceiver #1 alive check, seq# 91
feb-22 19.16.33   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.16.32   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.16.31   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.16.30   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.16.30   Error Calling HSEvent in plugin Z-Wave, Instance :Object reference not set to an instance of an object.
feb-22 19.16.29   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.16.29   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.16.23   Warning Plugin Z-Wave is not responding but it is still running, not restarting yet.
feb-22 19.16.03   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.16.02   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.16.01   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.16.00   Z-Wave Error Node 9 did not provide Wake-Up Command Class information - it will not be processed further.
feb-22 19.16.00   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.15.59   Error Posting back to plugin web page ZWaveControllers: Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)
feb-22 19.15.59   Error Getting web page from plugin page ZWaveWho:Object reference not set to an instance of an object.
feb-22 19.15.55   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010090025322048C2E0003000010650000000000
feb-22 19.15.55   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 144
feb-22 19.15.55   RFXCOM Transceiver #1 alive check, seq# 90
feb-22 19.15.50   Z-Wave Device: 3 Bad Luminance Set to 1 (Lux)
feb-22 19.15.02   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 1401008F025322048C2E0003000010650000000000
feb-22 19.15.02   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 143
feb-22 19.15.02   RFXCOM Transceiver #1 alive check, seq# 8F
feb-22 19.15.00   Z-Wave Error Node 8 did not provide Wake-Up Command Class information - it will not be processed further.
feb-22 19.15.00   Log Info The log database is currently 48,62MB in size.
feb-22 19.14.10   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 1401008E025322048C2E0003000010650000000000
feb-22 19.14.10   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 142
feb-22 19.14.10   RFXCOM Transceiver #1 alive check, seq# 8E
feb-22 19.13.31   Z-Wave Device: 3 Gang Luminance - Gang Set to 3 (Lux)
feb-22 19.13.19   Event Deleting event after run: "Delayed Actions 3etg Vegglampe (Delayed Action)"
feb-22 19.13.19   Device Control Device: 3 Gang 3etg Vegglampe to Off (0)
feb-22 19.13.19   Device Control Device: 3 Gang 3etg Taklampe -3 to Off (0)
feb-22 19.13.19   Device Control Device: 3 Gang 3etg Taklampe -2 to Off (0)
feb-22 19.13.19   Device Control Device: 3 Gang 3etg Taklampe -1 to Off (0)
feb-22 19.13.19   Event Event Trigger "Delayed Actions 3etg Vegglampe (Delayed Action)"
feb-22 19.13.17   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 1401008D025322048C2E0003000010650000000000
feb-22 19.13.17   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 141
feb-22 19.13.17   RFXCOM Transceiver #1 alive check, seq# 8D
feb-22 19.13.13   Z-Wave Error Node 7 did not provide Wake-Up Command Class information - it will not be processed further.
feb-22 19.13.05   Z-Wave Node 5 Meter is Supported for Electric_meter, Type ELECTRIC_W, Scale is INSTANT
feb-22 19.13.05   Z-Wave Node 5 Meter is Supported for Electric_meter, Type ELECTRIC_kWh, Scale is ACCUMULATED
feb-22 19.13.04   Z-Wave Processing Information for Node 5 Multi-CHANNEL Command Class of SWITCH_MULTILEVEL_V3, Endpoint 2
feb-22 19.13.04   Z-Wave System Supports Events: System Hardware Failure
feb-22 19.13.04   Z-Wave Power_Management Supports Events: Surge Detected, Voltage Drop Drift, Over Current Detected, Over Load Detected, Load Error
feb-22 19.13.04   Z-Wave Heat Supports Events: Overheat Detected Unknown Location
feb-22 19.13.04   Z-Wave Node 5 Supports 3 Notification Types: Heat Power_Management System
feb-22 19.13.01   Z-Wave Processing Information for Node 5 Multi-CHANNEL Command Class of NOTIFICATION_V6, Endpoint 1
feb-22 19.13.00   Z-Wave Processing Information for Node 5 Multi-CHANNEL Command Class of SENSOR_MULTILEVEL_V8, Endpoint 1
feb-22 19.13.00   Z-Wave Node 5 Meter Instance 1 is Supported for Electric_meter, Type ELECTRIC_W, Scale is INSTANT
feb-22 19.13.00   Z-Wave Node 5 Meter Instance 1 is Supported for Electric_meter, Type ELECTRIC_kWh, Scale is ACCUMULATED
feb-22 19.13.00   Z-Wave Processing Information for Node 5 Multi-CHANNEL Command Class of METER_V2, Endpoint 1
feb-22 19.12.59   Z-Wave Processing Information for Node 5 Multi-CHANNEL Command Class of SWITCH_MULTILEVEL_V3, Endpoint 1
feb-22 19.12.57   Z-Wave Warning An error (B) was reported attempting to get multi-channel or multi-instance information from node 4
feb-22 19.12.49   Z-Wave Node 3 Meter is Supported for Electric_meter, Type ELECTRIC_W, Scale is INSTANT
feb-22 19.12.49   Z-Wave Node 3 Meter is Supported for Electric_meter, Type ELECTRIC_kWh, Scale is ACCUMULATED
feb-22 19.12.49   Z-Wave Processing Information for Node 3 Multi-CHANNEL Command Class of SWITCH_MULTILEVEL_V3, Endpoint 2
feb-22 19.12.49   Z-Wave System Supports Events: System Hardware Failure
feb-22 19.12.49   Z-Wave Power_Management Supports Events: Surge Detected, Voltage Drop Drift, Over Current Detected, Over Load Detected, Load Error
feb-22 19.12.49   Z-Wave Heat Supports Events: Overheat Detected Unknown Location
feb-22 19.12.49   Z-Wave Node 3 Supports 3 Notification Types: Heat Power_Management System
feb-22 19.12.47   Z-Wave Processing Information for Node 3 Multi-CHANNEL Command Class of NOTIFICATION_V6, Endpoint 1
feb-22 19.12.46   Z-Wave Processing Information for Node 3 Multi-CHANNEL Command Class of SENSOR_MULTILEVEL_V8, Endpoint 1
feb-22 19.12.46   Z-Wave Node 3 Meter Instance 1 is Supported for Electric_meter, Type ELECTRIC_W, Scale is INSTANT
feb-22 19.12.46   Z-Wave Node 3 Meter Instance 1 is Supported for Electric_meter, Type ELECTRIC_kWh, Scale is ACCUMULATED
feb-22 19.12.46   Z-Wave Processing Information for Node 3 Multi-CHANNEL Command Class of METER_V2, Endpoint 1
feb-22 19.12.46   Z-Wave Processing Information for Node 3 Multi-CHANNEL Command Class of SWITCH_MULTILEVEL_V3, Endpoint 1
feb-22 19.12.44   Z-Wave Node 2 Meter is Supported for Electric_meter, Type ELECTRIC_W, Scale is INSTANT
feb-22 19.12.44   Z-Wave Node 2 Meter is Supported for Electric_meter, Type ELECTRIC_kWh, Scale is ACCUMULATED
feb-22 19.12.44   Z-Wave Processing Information for Node 2 Multi-CHANNEL Command Class of SWITCH_MULTILEVEL_V3, Endpoint 2
feb-22 19.12.44   Z-Wave System Supports Events: System Hardware Failure
feb-22 19.12.44   Z-Wave Power_Management Supports Events: Surge Detected, Voltage Drop Drift, Over Current Detected, Over Load Detected, Load Error
feb-22 19.12.44   Z-Wave Heat Supports Events: Overheat Detected Unknown Location
feb-22 19.12.44   Z-Wave Node 2 Supports 3 Notification Types: Heat Power_Management System
feb-22 19.12.42   Z-Wave Processing Information for Node 2 Multi-CHANNEL Command Class of NOTIFICATION_V6, Endpoint 1
feb-22 19.12.42   Z-Wave Processing Information for Node 2 Multi-CHANNEL Command Class of SENSOR_MULTILEVEL_V8, Endpoint 1
feb-22 19.12.42   Z-Wave Node 2 Meter Instance 1 is Supported for Electric_meter, Type ELECTRIC_W, Scale is INSTANT
feb-22 19.12.42   Z-Wave Node 2 Meter Instance 1 is Supported for Electric_meter, Type ELECTRIC_kWh, Scale is ACCUMULATED
feb-22 19.12.42   Z-Wave Processing Information for Node 2 Multi-CHANNEL Command Class of METER_V2, Endpoint 1
feb-22 19.12.41   Z-Wave Processing Information for Node 2 Multi-CHANNEL Command Class of SWITCH_MULTILEVEL_V3, Endpoint 1
feb-22 19.12.40   Z-Wave Device: 3 Bad Home Security - Bad Set to NOTIFICATION for type Home Security, Event: Tampering Cover Removed
feb-22 19.12.27   Z-Wave Node 22 is a Z-Wave Plus node. Retrieving ZWPlus Info...
feb-22 19.12.27   Z-Wave Node 22 is Z-Wave version: Lib: 4,24 App: 3.5
feb-22 19.12.27   Z-Wave Warning Error getting version information for node 22, Send failed.
feb-22 19.12.25   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 1401008C025322048C2E0003000010650000000000
feb-22 19.12.25   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 140
feb-22 19.12.25   RFXCOM Transceiver #1 alive check, seq# 8C
feb-22 19.12.19   Z-Wave Node: 22 Controls Class(es): SCENE_ACTIVATION
feb-22 19.12.19   Z-Wave Node: 22 Supports Class(es): ZWAVEPLUS_INFO, BASIC_V2, VERSION, MANUFACTURER_SPECIFIC_V2, SWITCH_MULTILEVEL_V3, DEVICE_RESET_LOCALLY, ASSOCIATION_GRP_INFO_V2, ASSOCIATION, POWERLEVEL, FIRMWARE_UPDATE_MD, CRC_16_ENCAP, CONFIGURATION, SENSOR_MULTILEVEL_V8, METER_V2, MULTI_INSTANCE_ASSOCIATION, MULTI_CHANNEL_V3, PROTECTION, NOTIFICATION_V6, SWITCH_ALL, APPLICATION_STATUS, SCENE_ACTIVATION
feb-22 19.12.11   Z-Wave Node 21 is a Z-Wave Plus node. Retrieving ZWPlus Info...
feb-22 19.12.11   Z-Wave Node 21 is Z-Wave version: Lib: 4,38 App: 3.2
feb-22 19.12.11   Z-Wave Warning Error getting version information for node 21, Send failed.
feb-22 19.11.59   Z-Wave Node: 21 Supports Secure Class(es): ASSOCIATION, CONFIGURATION, DEVICE_RESET_LOCALLY, MANUFACTURER_SPECIFIC_V2, MULTI_INSTANCE_ASSOCIATION, NOTIFICATION_V6, VERSION, WAKE_UP
feb-22 19.11.59   Z-Wave Node: 21 Supports Class(es): ZWAVEPLUS_INFO, ASSOCIATION, ASSOCIATION_GRP_INFO_V2, APPLICATION_STATUS, BATTERY, CONFIGURATION, CRC_16_ENCAP, DEVICE_RESET_LOCALLY, FIRMWARE_UPDATE_MD, MANUFACTURER_SPECIFIC_V2, MULTI_INSTANCE_ASSOCIATION, NOTIFICATION_V6, POWERLEVEL, SECURITY, SENSOR_MULTILEVEL_V8, VERSION, WAKE_UP
feb-22 19.11.46   Z-Wave Node 20 is a Z-Wave Plus node. Retrieving ZWPlus Info...
feb-22 19.11.46   Z-Wave Node 20 is Z-Wave version: Lib: 4,38 App: 3.2
feb-22 19.11.46   Z-Wave Warning Error getting version information for node 20, Send failed.
feb-22 19.11.38   Z-Wave Node: 20 Supports Secure Class(es): ASSOCIATION, CONFIGURATION, DEVICE_RESET_LOCALLY, MANUFACTURER_SPECIFIC_V2, MULTI_INSTANCE_ASSOCIATION, NOTIFICATION_V6, VERSION, WAKE_UP
feb-22 19.11.38   Z-Wave Node: 20 Supports Class(es): ZWAVEPLUS_INFO, ASSOCIATION, ASSOCIATION_GRP_INFO_V2, APPLICATION_STATUS, BATTERY, CONFIGURATION, CRC_16_ENCAP, DEVICE_RESET_LOCALLY, FIRMWARE_UPDATE_MD, MANUFACTURER_SPECIFIC_V2, MULTI_INSTANCE_ASSOCIATION, NOTIFICATION_V6, POWERLEVEL, SECURITY, SENSOR_MULTILEVEL_V8, VERSION, WAKE_UP
feb-22 19.11.32   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 1401008B025322048C2E0003000010650000000000
feb-22 19.11.32   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 139
feb-22 19.11.32   RFXCOM Transceiver #1 alive check, seq# 8B
feb-22 19.11.31   Z-Wave Device: 1 Kino Power - Biljard Lys Set to 123 (W)
feb-22 19.11.30   Z-Wave Node 19 is a Z-Wave Plus node. Retrieving ZWPlus Info...
feb-22 19.11.30   Z-Wave Node 19 is Z-Wave version: Lib: 4,62 App: 2.3
feb-22 19.11.30   Z-Wave Warning Error getting version information for node 19, Send failed.
feb-22 19.11.23   Z-Wave Node: 19 Controls Class(es): SWITCH_BINARY, SWITCH_MULTILEVEL_V3
feb-22 19.11.23   Z-Wave Node: 19 Supports Class(es): ZWAVEPLUS_INFO, ASSOCIATION, ASSOCIATION_GRP_INFO_V2, MULTI_INSTANCE_ASSOCIATION, MULTI_CHANNEL_V3, VERSION, CONFIGURATION, MANUFACTURER_SPECIFIC_V2, DEVICE_RESET_LOCALLY, POWERLEVEL, WAKE_UP, BATTERY, CENTRAL_SCENE_V2, NOTIFICATION_V6, FIRMWARE_UPDATE_MD
feb-22 19.11.15   Z-Wave Node 18 is a Z-Wave Plus node. Retrieving ZWPlus Info...
feb-22 19.11.15   Z-Wave Node 18 is Z-Wave version: Lib: 4,24 App: 3.2
feb-22 19.11.15   Z-Wave Warning Error getting version information for node 18, Send failed.
feb-22 19.11.07   Z-Wave Node: 18 Supports Class(es): ZWAVEPLUS_INFO, APPLICATION_STATUS, ASSOCIATION, ASSOCIATION_GRP_INFO_V2, CONFIGURATION, CRC_16_ENCAP, DEVICE_RESET_LOCALLY, FIRMWARE_UPDATE_MD, MANUFACTURER_SPECIFIC_V2, METER_V2, MULTI_INSTANCE_ASSOCIATION, NOTIFICATION_V6, POWERLEVEL, SECURITY, SENSOR_MULTILEVEL_V8, SWITCH_BINARY, VERSION
feb-22 19.10.59   Z-Wave Node 14 is a Z-Wave Plus node. Retrieving ZWPlus Info...
feb-22 19.10.59   Z-Wave Node 14 is Z-Wave version: Lib: 4,38 App: 1.28
feb-22 19.10.59   Z-Wave Warning Error getting version information for node 14, Send failed.
feb-22 19.10.51   Z-Wave Node: 14 Controls Class(es): BASIC_V2
feb-22 19.10.51   Z-Wave Node: 14 Supports Secure Class(es): BATTERY, NOTIFICATION_V6, ASSOCIATION, CONFIGURATION, SENSOR_BINARY, WAKE_UP
feb-22 19.10.51   Z-Wave Node: 14 Supports Class(es): ZWAVEPLUS_INFO, BATTERY, NOTIFICATION_V6, ASSOCIATION, CONFIGURATION, MANUFACTURER_SPECIFIC_V2, VERSION, SENSOR_BINARY, WAKE_UP, ASSOCIATION_GRP_INFO_V2, POWERLEVEL, DEVICE_RESET_LOCALLY, MULTI_CMD, SECURITY
feb-22 19.10.44   Z-Wave Node 12 is a Z-Wave Plus node. Retrieving ZWPlus Info...
feb-22 19.10.44   Z-Wave Node 12 is Z-Wave version: Lib: 4,61 App: 1.0
feb-22 19.10.44   Z-Wave Warning Error getting version information for node 12, Send failed.
feb-22 19.10.40   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 1401008A025322048C2E0003000010650000000000
feb-22 19.10.40   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 138
feb-22 19.10.40   RFXCOM Transceiver #1 alive check, seq# 8A
feb-22 19.10.36   Z-Wave Node: 12 Supports Secure Class(es): VERSION, ASSOCIATION, ASSOCIATION_GRP_INFO_V2, MANUFACTURER_SPECIFIC_V2, DEVICE_RESET_LOCALLY, POWERLEVEL, SUPERVISION, FIRMWARE_UPDATE_MD, BATTERY, WAKE_UP, NOTIFICATION_V6, CONFIGURATION
feb-22 19.10.36   Z-Wave Node: 12 Supports Class(es): ZWAVEPLUS_INFO, ASSOCIATION, ASSOCIATION_GRP_INFO_V2, TRANSPORT_SERVICE, VERSION, MANUFACTURER_SPECIFIC_V2, DEVICE_RESET_LOCALLY, POWERLEVEL, SECURITY, SECURITY_2, SUPERVISION, FIRMWARE_UPDATE_MD, BATTERY, WAKE_UP, NOTIFICATION_V6, CONFIGURATION
feb-22 19.10.36   Z-Wave Node 11 is a Z-Wave Plus node. Retrieving ZWPlus Info...
feb-22 19.10.36   Z-Wave Node 11 is Z-Wave version: Lib: 4,24 App: 3.2
feb-22 19.10.34   Z-Wave Node: 11 Supports Secure Class(es): ASSOCIATION, CONFIGURATION, MANUFACTURER_SPECIFIC_V2, DEVICE_RESET_LOCALLY, MULTI_INSTANCE_ASSOCIATION, SWITCH_BINARY, VERSION
feb-22 19.10.34   Z-Wave Node: 11 Supports Class(es): ZWAVEPLUS_INFO, APPLICATION_STATUS, ASSOCIATION, ASSOCIATION_GRP_INFO_V2, CONFIGURATION, CRC_16_ENCAP, DEVICE_RESET_LOCALLY, FIRMWARE_UPDATE_MD, MANUFACTURER_SPECIFIC_V2, METER_V2, MULTI_INSTANCE_ASSOCIATION, NOTIFICATION_V6, POWERLEVEL, SECURITY, SENSOR_MULTILEVEL_V8, SWITCH_BINARY, VERSION
feb-22 19.10.27   Z-Wave Node 10 is a Z-Wave Plus node. Retrieving ZWPlus Info...
feb-22 19.10.27   Z-Wave Node 10 is Z-Wave version: Lib: 4,05 App: 3.2
feb-22 19.10.27   Z-Wave Warning Error getting version information for node 10, Send failed.
feb-22 19.10.15   Z-Wave Node: 10 Supports Secure Class(es): BASIC_V2, DEVICE_RESET_LOCALLY, ASSOCIATION, WAKE_UP, NOTIFICATION_V6, MULTI_INSTANCE_ASSOCIATION, CONFIGURATION, SENSOR_BINARY, SENSOR_ALARM
feb-22 19.10.15   Z-Wave Node: 10 Supports Class(es): ZWAVEPLUS_INFO, BASIC_V2, VERSION, MANUFACTURER_SPECIFIC_V2, DEVICE_RESET_LOCALLY, ASSOCIATION_GRP_INFO_V2, ASSOCIATION, POWERLEVEL, WAKE_UP, BATTERY, NOTIFICATION_V6, CRC_16_ENCAP, CONFIGURATION, SENSOR_MULTILEVEL_V8, MULTI_INSTANCE_ASSOCIATION, APPLICATION_STATUS, SENSOR_BINARY, SENSOR_ALARM, SECURITY, FIRMWARE_UPDATE_MD
feb-22 19.10.02   Z-Wave Node 9 is a Z-Wave Plus node. Retrieving ZWPlus Info...
feb-22 19.10.02   Z-Wave Node 9 is Z-Wave version: Lib: 4,05 App: 3.2
feb-22 19.10.02   Z-Wave Warning Error getting version information for node 9, Send failed.
feb-22 19.09.49   Z-Wave Node: 9 Supports Secure Class(es): BASIC_V2, DEVICE_RESET_LOCALLY, ASSOCIATION, WAKE_UP, NOTIFICATION_V6, MULTI_INSTANCE_ASSOCIATION, CONFIGURATION, SENSOR_BINARY, SENSOR_ALARM
feb-22 19.09.49   Z-Wave Node: 9 Supports Class(es): ZWAVEPLUS_INFO, BASIC_V2, VERSION, MANUFACTURER_SPECIFIC_V2, DEVICE_RESET_LOCALLY, ASSOCIATION_GRP_INFO_V2, ASSOCIATION, POWERLEVEL, WAKE_UP, BATTERY, NOTIFICATION_V6, CRC_16_ENCAP, CONFIGURATION, SENSOR_MULTILEVEL_V8, MULTI_INSTANCE_ASSOCIATION, APPLICATION_STATUS, SENSOR_BINARY, SENSOR_ALARM, SECURITY, FIRMWARE_UPDATE_MD
feb-22 19.09.47   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010089025322048C2E0003000010650000000000
feb-22 19.09.47   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 137
feb-22 19.09.47   RFXCOM Transceiver #1 alive check, seq# 89
feb-22 19.09.36   Z-Wave Node 8 is a Z-Wave Plus node. Retrieving ZWPlus Info...
feb-22 19.09.36   Z-Wave Node 8 is Z-Wave version: Lib: 4,24 App: 3.3
feb-22 19.09.36   Z-Wave Warning Error getting version information for node 8, Send failed.
feb-22 19.09.23   Z-Wave Node: 8 Supports Secure Class(es): DEVICE_RESET_LOCALLY, ASSOCIATION, WAKE_UP, NOTIFICATION_V6, MULTI_INSTANCE_ASSOCIATION, CONFIGURATION, SENSOR_BINARY, SENSOR_ALARM, BASIC_V2
feb-22 19.09.23   Z-Wave Node: 8 Supports Class(es): ZWAVEPLUS_INFO, VERSION, MANUFACTURER_SPECIFIC_V2, DEVICE_RESET_LOCALLY, ASSOCIATION_GRP_INFO_V2, ASSOCIATION, POWERLEVEL, WAKE_UP, BATTERY, NOTIFICATION_V6, CRC_16_ENCAP, CONFIGURATION, SENSOR_MULTILEVEL_V8, MULTI_INSTANCE_ASSOCIATION, APPLICATION_STATUS, SENSOR_BINARY, SENSOR_ALARM, SECURITY, FIRMWARE_UPDATE_MD
feb-22 19.09.10   Z-Wave Node 7 is a Z-Wave Plus node. Retrieving ZWPlus Info...
feb-22 19.09.10   Z-Wave Node 7 is Z-Wave version: Lib: 4,05 App: 3.2
feb-22 19.09.10   Z-Wave Warning Error getting version information for node 7, Send failed.
feb-22 19.09.02   Z-Wave Node: 7 Supports Secure Class(es): BASIC_V2, DEVICE_RESET_LOCALLY, ASSOCIATION, WAKE_UP, NOTIFICATION_V6, MULTI_INSTANCE_ASSOCIATION, CONFIGURATION, SENSOR_BINARY, SENSOR_ALARM
feb-22 19.09.02   Z-Wave Node: 7 Supports Class(es): ZWAVEPLUS_INFO, BASIC_V2, VERSION, MANUFACTURER_SPECIFIC_V2, DEVICE_RESET_LOCALLY, ASSOCIATION_GRP_INFO_V2, ASSOCIATION, POWERLEVEL, WAKE_UP, BATTERY, NOTIFICATION_V6, CRC_16_ENCAP, CONFIGURATION, SENSOR_MULTILEVEL_V8, MULTI_INSTANCE_ASSOCIATION, APPLICATION_STATUS, SENSOR_BINARY, SENSOR_ALARM, SECURITY, FIRMWARE_UPDATE_MD
feb-22 19.09.02   Z-Wave Node 5 is a Z-Wave Plus node. Retrieving ZWPlus Info...
feb-22 19.09.02   Z-Wave Node 5 is Z-Wave version: Lib: 4,24 App: 3.5
feb-22 19.09.02   Z-Wave Node: 5 Controls Secure Class(es): SCENE_ACTIVATION
feb-22 19.09.02   Z-Wave Node: 5 Controls Class(es): SCENE_ACTIVATION
feb-22 19.09.02   Z-Wave Node: 5 Supports Secure Class(es): BASIC_V2, DEVICE_RESET_LOCALLY, ASSOCIATION, SWITCH_MULTILEVEL_V3, MULTI_INSTANCE_ASSOCIATION, MULTI_CHANNEL_V3, CONFIGURATION, PROTECTION, SWITCH_ALL
feb-22 19.09.02   Z-Wave Node: 5 Supports Class(es): ZWAVEPLUS_INFO, BASIC_V2, VERSION, MANUFACTURER_SPECIFIC_V2, SWITCH_MULTILEVEL_V3, DEVICE_RESET_LOCALLY, ASSOCIATION_GRP_INFO_V2, ASSOCIATION, POWERLEVEL, SECURITY, FIRMWARE_UPDATE_MD, CRC_16_ENCAP, CONFIGURATION, SENSOR_MULTILEVEL_V8, METER_V2, MULTI_INSTANCE_ASSOCIATION, MULTI_CHANNEL_V3, PROTECTION, NOTIFICATION_V6, SWITCH_ALL, APPLICATION_STATUS, SCENE_ACTIVATION
feb-22 19.08.54   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010088025322048C2E0003000010650000000000
feb-22 19.08.54   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 136
feb-22 19.08.54   RFXCOM Transceiver #1 alive check, seq# 88
feb-22 19.08.54   Z-Wave Node 4 is a Z-Wave Plus node. Retrieving ZWPlus Info...
feb-22 19.08.54   Z-Wave Node 4 is Z-Wave version: Lib: 4,24 App: 3.5
feb-22 19.08.54   Z-Wave Warning Error getting version information for node 4, Send failed.
feb-22 19.08.46   Z-Wave Node: 4 Controls Secure Class(es): SCENE_ACTIVATION
feb-22 19.08.46   Z-Wave Node: 4 Controls Class(es): SCENE_ACTIVATION
feb-22 19.08.46   Z-Wave Node: 4 Supports Secure Class(es): BASIC_V2, DEVICE_RESET_LOCALLY, ASSOCIATION, SWITCH_MULTILEVEL_V3, MULTI_INSTANCE_ASSOCIATION, MULTI_CHANNEL_V3, CONFIGURATION, PROTECTION, SWITCH_ALL
feb-22 19.08.46   Z-Wave Node: 4 Supports Class(es): ZWAVEPLUS_INFO, BASIC_V2, VERSION, MANUFACTURER_SPECIFIC_V2, SWITCH_MULTILEVEL_V3, DEVICE_RESET_LOCALLY, ASSOCIATION_GRP_INFO_V2, ASSOCIATION, POWERLEVEL, SECURITY, FIRMWARE_UPDATE_MD, CRC_16_ENCAP, CONFIGURATION, SENSOR_MULTILEVEL_V8, METER_V2, MULTI_INSTANCE_ASSOCIATION, MULTI_CHANNEL_V3, PROTECTION, NOTIFICATION_V6, SWITCH_ALL, APPLICATION_STATUS, SCENE_ACTIVATION
feb-22 19.08.46   Z-Wave Node 3 is a Z-Wave Plus node. Retrieving ZWPlus Info...
feb-22 19.08.46   Z-Wave Node 3 is Z-Wave version: Lib: 4,24 App: 3.5
feb-22 19.08.46   Z-Wave Node: 3 Controls Secure Class(es): SCENE_ACTIVATION
feb-22 19.08.46   Z-Wave Node: 3 Controls Class(es): SCENE_ACTIVATION
feb-22 19.08.46   Z-Wave Node: 3 Supports Secure Class(es): BASIC_V2, DEVICE_RESET_LOCALLY, ASSOCIATION, SWITCH_MULTILEVEL_V3, MULTI_INSTANCE_ASSOCIATION, MULTI_CHANNEL_V3, CONFIGURATION, PROTECTION, SWITCH_ALL
feb-22 19.08.46   Z-Wave Node: 3 Supports Class(es): ZWAVEPLUS_INFO, BASIC_V2, VERSION, MANUFACTURER_SPECIFIC_V2, SWITCH_MULTILEVEL_V3, DEVICE_RESET_LOCALLY, ASSOCIATION_GRP_INFO_V2, ASSOCIATION, POWERLEVEL, SECURITY, FIRMWARE_UPDATE_MD, CRC_16_ENCAP, CONFIGURATION, SENSOR_MULTILEVEL_V8, METER_V2, MULTI_INSTANCE_ASSOCIATION, MULTI_CHANNEL_V3, PROTECTION, NOTIFICATION_V6, SWITCH_ALL, APPLICATION_STATUS, SCENE_ACTIVATION
feb-22 19.08.39   Z-Wave Device: 1 Kino Temperature - Ytterdør Set to 22,3 (C)
feb-22 19.08.39   Z-Wave Node 2 is a Z-Wave Plus node. Retrieving ZWPlus Info...
feb-22 19.08.39   Z-Wave Node 2 is Z-Wave version: Lib: 4,24 App: 3.5
feb-22 19.08.39   Z-Wave Node: 2 Controls Secure Class(es): SCENE_ACTIVATION
feb-22 19.08.39   Z-Wave Node: 2 Controls Class(es): SCENE_ACTIVATION
feb-22 19.08.39   Z-Wave Node: 2 Supports Secure Class(es): BASIC_V2, DEVICE_RESET_LOCALLY, ASSOCIATION, SWITCH_MULTILEVEL_V3, MULTI_INSTANCE_ASSOCIATION, MULTI_CHANNEL_V3, CONFIGURATION, PROTECTION, SWITCH_ALL
feb-22 19.08.39   Z-Wave Node: 2 Supports Class(es): ZWAVEPLUS_INFO, BASIC_V2, VERSION, MANUFACTURER_SPECIFIC_V2, SWITCH_MULTILEVEL_V3, DEVICE_RESET_LOCALLY, ASSOCIATION_GRP_INFO_V2, ASSOCIATION, POWERLEVEL, SECURITY, FIRMWARE_UPDATE_MD, CRC_16_ENCAP, CONFIGURATION, SENSOR_MULTILEVEL_V8, METER_V2, MULTI_INSTANCE_ASSOCIATION, MULTI_CHANNEL_V3, PROTECTION, NOTIFICATION_V6, SWITCH_ALL, APPLICATION_STATUS, SCENE_ACTIVATION
feb-22 19.08.39   Z-Wave Warning If this is an import, you may need to remove and add the device as some devices cannot be added with an import.
feb-22 19.08.39   Z-Wave Warning Failed to get a SECURITY SCHEME or verify the key from node 18. Device may not be added properly to HomeSeer.
feb-22 19.08.39   Z-Wave Error Z-Wave was unable to negotiate a compatible security scheme with node 18
feb-22 19.08.19   Z-Wave Adding using S0 Security, Negotiating or Verifying SECURITY SCHEME for node 18
feb-22 19.08.19   Z-Wave Synchronize nodes finished. Number of device nodes to be created/added = 0
feb-22 19.08.19   Z-Wave Syncing Z-Wave nodes with device list...
feb-22 19.08.19   Z-Wave Found 17 Z-Wave nodes
feb-22 19.08.19   Z-Wave Getting Z-Wave node list for network FC0DBD69...
feb-22 19.08.02   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010087025322048C2E0003000010650000000000
feb-22 19.08.02   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 135
feb-22 19.08.02   RFXCOM Transceiver #1 alive check, seq# 87
feb-22 19.08.01   Z-Wave Finished with Z-Wave device synchronization.
feb-22 19.08.01   Z-Wave Synchronize nodes finished. Number of device nodes to be created/added = 0
feb-22 19.08.00   Z-Wave Syncing Z-Wave nodes with device list...
feb-22 19.08.00   Z-Wave Found 17 Z-Wave nodes
feb-22 19.08.00   Z-Wave Getting Z-Wave node list for network FC0DBD69...
feb-22 19.07.09   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010086025322048C2E0003000010650000000000
feb-22 19.07.09   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 134
feb-22 19.07.09   RFXCOM Transceiver #1 alive check, seq# 86
feb-22 19.06.17   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010085025322048C2E0003000010650000000000
feb-22 19.06.17   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 133
feb-22 19.06.17   RFXCOM Transceiver #1 alive check, seq# 85
feb-22 19.05.46   Z-Wave Device: 2 Stue kW Hours 1 - Tak Lys Set to 23,12 (23,12 kW Hours)
feb-22 19.05.24   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010084025322048C2E0003000010650000000000
feb-22 19.05.24   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 132
feb-22 19.05.24   RFXCOM Transceiver #1 alive check, seq# 84
feb-22 19.04.32   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010083025322048C2E0003000010650000000000
feb-22 19.04.32   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 131
feb-22 19.04.32   RFXCOM Transceiver #1 alive check, seq# 83
feb-22 19.03.39   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010082025322048C2E0003000010650000000000
feb-22 19.03.39   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 130
feb-22 19.03.39   RFXCOM Transceiver #1 alive check, seq# 82
feb-22 19.02.47   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010081025322048C2E0003000010650000000000
feb-22 19.02.47   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 129
feb-22 19.02.47   RFXCOM Transceiver #1 alive check, seq# 81
feb-22 19.01.54   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010080025322048C2E0003000010650000000000
feb-22 19.01.54   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 128
feb-22 19.01.54   RFXCOM Transceiver #1 alive check, seq# 80
feb-22 19.01.22   MyQ Error Exception in httpGET|ErrorCount:1|https://myqexternal.myqdevice.com/api/v4/UserDeviceDetails/Get
feb-22 19.01.01   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 1401007F025322048C2E0003000010650000000000
feb-22 19.01.01   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 127
feb-22 19.01.01   RFXCOM Transceiver #1 alive check, seq# 7F
feb-22 19.00.55   Z-Wave Device: 3 Bad Home Security - Bad Set to NOTIFICATION for type Home Security, Event: No Event
feb-22 19.00.22   Z-Wave Device: 3 Bad Home Security - Bad Set to NOTIFICATION for type Home Security, Event: Tampering Cover Removed
feb-22 19.00.09   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 1401007E025322048C2E0003000010650000000000
feb-22 19.00.09   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 126
feb-22 19.00.09   RFXCOM Transceiver #1 alive check, seq# 7E
feb-22 19.00.06   Z-Wave Device: 2 Stue kW Hours 1 - Tak Lys Set to 23,11 (23,11 kW Hours)
feb-22 18.59.16   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 1401007D025322048C2E0003000010650000000000
feb-22 18.59.16   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 125
feb-22 18.59.16   RFXCOM Transceiver #1 alive check, seq# 7D
feb-22 18.59.03   Z-Wave Device: 2 TV Stue Power - Tak Lys Set to 97,3 (W)
feb-22 18.58.24   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 0B11004801C2138201000060
feb-22 18.58.24   RFXCOM 37 (Display_E_a) Device:AC[1C21382-1]a Cmd:0
feb-22 18.58.19   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 0B11004701CFC38A02010F60
feb-22 18.58.19   Device Control Device: 3 Gang 3etg Vegglampe to 50% (50)
feb-22 18.58.19   Device Control Device: 3 Gang 3etg Taklampe -3 to 40% (40)
feb-22 18.58.19   Device Control Device: 3 Gang 3etg Taklampe -2 to 40% (40)
feb-22 18.58.19   Device Control Device: 3 Gang 3etg Taklampe -1 to 40% (40)
feb-22 18.58.19   RFXCOM 37 (Display_E_a) Device:AC[1CFC38A-2]a Cmd:100
feb-22 18.58.19   Event Event Trigger "3 etg - Lys Gang - IKEA Gang Kveld - IKEA"
feb-22 18.58.18   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 0B11004601CFC38A02000060
feb-22 18.58.18   RFXCOM 37 (Display_E_a) Device:AC[1CFC38A-2]a Cmd:0
feb-22 18.58.06   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 1401007C025322048C2E0003000010650000000000
feb-22 18.58.06   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 124
feb-22 18.58.06   RFXCOM Transceiver #1 alive check, seq# 7C
feb-22 18.57.20   Z-Wave Device: 2 Gang Luminance - Gang Set to 11 (Lux)
feb-22 18.57.13   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 1401007B025322048C2E0003000010650000000000
feb-22 18.57.13   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 123
feb-22 18.57.13   RFXCOM Transceiver #1 alive check, seq# 7B
feb-22 18.57.03   Z-Wave Device: 2 Stue Watts 1 - Tak Lys Set to 82,3 (82,3 Watts)
feb-22 18.57.00   Z-Wave Device: 2 Stue Power - Tak Lys Set to 82,3 (W)
feb-22 18.56.21   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 1401007A025322048C2E0003000010650000000000
feb-22 18.56.21   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 122
feb-22 18.56.21   RFXCOM Transceiver #1 alive check, seq# 7A
feb-22 18.55.44   Z-Wave Device: 2 Stue Home Security - Egen Set to NOTIFICATION for type Home Security, Event: No Event
feb-22 18.55.33   Device Control Device: 2 Stue Switch Multilevel 1 - Tak Lys to 40% (40)
feb-22 18.55.33   Event Event Trigger "2 etg - Lys Stue - testing Stue Kveld"
feb-22 18.55.33   Z-Wave Device: 2 Stue Home Security - Egen Set to NOTIFICATION for type Home Security, Event: Motion Detected
feb-22 18.55.28   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010079025322048C2E0003000010650000000000
feb-22 18.55.28   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 121
feb-22 18.55.28   RFXCOM Transceiver #1 alive check, seq# 79
feb-22 18.54.36   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010078025322048C2E0003000010650000000000
feb-22 18.54.36   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 120
feb-22 18.54.36   RFXCOM Transceiver #1 alive check, seq# 78
feb-22 18.53.43   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010077025322048C2E0003000010650000000000
feb-22 18.53.43   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 119
feb-22 18.53.43   RFXCOM Transceiver #1 alive check, seq# 77
feb-22 18.52.51   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010076025322048C2E0003000010650000000000
feb-22 18.52.51   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 118
feb-22 18.52.51   RFXCOM Transceiver #1 alive check, seq# 76
feb-22 18.51.58   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010075025322048C2E0003000010650000000000
feb-22 18.51.58   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 117
feb-22 18.51.58   RFXCOM Transceiver #1 alive check, seq# 75
feb-22 18.51.06   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010074025322048C2E0003000010650000000000
feb-22 18.51.06   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 116
feb-22 18.51.05   RFXCOM Transceiver #1 alive check, seq# 74
feb-22 18.50.13   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010073025322048C2E0003000010650000000000
feb-22 18.50.13   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 115
feb-22 18.50.13   RFXCOM Transceiver #1 alive check, seq# 73
feb-22 18.49.20   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010072025322048C2E0003000010650000000000
feb-22 18.49.20   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 114
feb-22 18.49.20   RFXCOM Transceiver #1 alive check, seq# 72
feb-22 18.48.28   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010071025322048C2E0003000010650000000000
feb-22 18.48.28   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 113
feb-22 18.48.28   RFXCOM Transceiver #1 alive check, seq# 71
feb-22 18.47.35   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010070025322048C2E0003000010650000000000
feb-22 18.47.35   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 112
feb-22 18.47.35   RFXCOM Transceiver #1 alive check, seq# 70
feb-22 18.46.43   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 1401006F025322048C2E0003000010650000000000
feb-22 18.46.43   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 111
feb-22 18.46.43   RFXCOM Transceiver #1 alive check, seq# 6F
feb-22 18.45.50   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 1401006E025322048C2E0003000010650000000000
feb-22 18.45.50   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 110
feb-22 18.45.50   RFXCOM Transceiver #1 alive check, seq# 6E
feb-22 18.44.58   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 1401006D025322048C2E0003000010650000000000
feb-22 18.44.58   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 109
feb-22 18.44.58   RFXCOM Transceiver #1 alive check, seq# 6D
feb-22 18.44.05   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 1401006C025322048C2E0003000010650000000000
feb-22 18.44.05   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 108
feb-22 18.44.05   RFXCOM Transceiver #1 alive check, seq# 6C
feb-22 18.43.12   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 1401006B025322048C2E0003000010650000000000
feb-22 18.43.12   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 107
feb-22 18.43.12   RFXCOM Transceiver #1 alive check, seq# 6B
feb-22 18.42.20   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 1401006A025322048C2E0003000010650000000000
feb-22 18.42.20   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 106
feb-22 18.42.20   RFXCOM Transceiver #1 alive check, seq# 6A
feb-22 18.41.34   Z-Wave Device: 2 Stue Watts 1 - Tak Lys Set to 0 (0 Watts)
feb-22 18.41.27   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010069025322048C2E0003000010650000000000
feb-22 18.41.27   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 105
feb-22 18.41.27   RFXCOM Transceiver #1 alive check, seq# 69
feb-22 18.40.35   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010068025322048C2E0003000010650000000000
feb-22 18.40.35   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 104
feb-22 18.40.35   RFXCOM Transceiver #1 alive check, seq# 68
feb-22 18.40.02   Z-Wave Device: 2 Stue Watts 1 - Tak Lys Set to 150,1 (150,1 Watts)
feb-22 18.39.59   Z-Wave Device: 2 Stue Power - Tak Lys Set to 150,1 (W)
feb-22 18.39.42   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010067025322048C2E0003000010650000000000
feb-22 18.39.42   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 103
feb-22 18.39.42   RFXCOM Transceiver #1 alive check, seq# 67
feb-22 18.38.50   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010066025322048C2E0003000010650000000000
feb-22 18.38.50   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 102
feb-22 18.38.50   RFXCOM Transceiver #1 alive check, seq# 66
feb-22 18.38.46   Event Deleting event after run: "Delayed Actions Switch Multilevel 1 - Tak Lys (Delayed Action)"
feb-22 18.38.46   Device Control Device: 2 Stue Switch Multilevel 1 - Tak Lys to Off (0)
feb-22 18.38.46   Event Event Trigger "Delayed Actions Switch Multilevel 1 - Tak Lys (Delayed Action)"
feb-22 18.37.57   RFXCOM 37 (RecTRXChar) transceiver #1 packet: 14010065025322048C2E0003000010650000000000
feb-22 18.37.57   RFXCOM 37 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 101
feb-22 18.37.57   RFXCOM Transceiver #1 alive check, seq# 65
feb-22 18.37.31   JowiHue Cannot find key for light Light 4 - Stativ (id=4) was it removed from the bridge?

 

 

Lenke til kommentar
Del på andre sider
Moskus Automatiker

Moskus

Skrevet
Skrevet
12 timer siden, mr.rs4 skrev:

(tok ikke vekk node / dimmer i HS3)

Da må du gjøre det. Utkoblede Z-wave noder gir enda tregere reaksjonstider.

 

 

Jeg vet, for jeg har koblet ut 7 noder den sist uka, men enda ikke rukket å ekskludere dem. Da har reponstiden vært ganske så lang inni mellom. Jobber akkurat nå med å skru på strøm på alle dimmerne og ekskludere dem. Ser ut til at jeg har fått bort den som mye tydeligvis var routet gjennom, da responstiden nå er upåklagelig igjen.

  • Like 1
Lenke til kommentar
Del på andre sider
Ronny Bitfikler

Ronny

Skrevet
Skrevet
7 hours ago, Moskus said:

Utkoblede Z-wave noder gir enda tregere reaksjonstider.

 

Generelt spørsmål rundt dette. Vil det si at noder man har inkludert for test, og så bare tatt av strømmen av el.l. De kan altså lage tregheter i nettet?
Bør man da ekskludere de etter testen ?

 

 

 

Lenke til kommentar
Del på andre sider

Bli med i samtalen

Du kan publisere innhold nå og registrere deg senere. Hvis du har en konto, logg inn nå for å poste med kontoen din.

Gjest
Skriv svar til emnet...

×   Du har limt inn tekst med formatering.   Lim inn uten formatering i stedet

  Du kan kun bruke opp til 75 smilefjes.

×   Lenken din har blitt bygget inn på siden automatisk.   Vis som en ordinær lenke i stedet

×   Tidligere tekst har blitt gjenopprettet.   Tøm tekstverktøy

×   Du kan ikke lime inn bilder direkte. Last opp eller legg inn bilder fra URL.

×
 Del
Gå til emneliste
×
×
  • Opprett ny...

Viktig informasjon

Vi har plassert informasjonskapsler/cookies på din enhet for å gjøre denne siden bedre. Du kan justere dine innstillinger for informasjonskapsler, ellers vil vi anta at dette er ok for deg.