Announcement

Collapse
No announcement yet.

Magic Light WF bulbs

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • rsisson
    replied
    I let everything sit for a few days, recycle, update, whatever...
    it is now "seeing" the bulbs reasonably reliably, and can control on/off well.
    HOWEVER...
    when I try to do anything with the warmwhite/coolwhite it throws an error.
    it also sometimes seems to get a double frame from the bulb, two identical blocks back to back
    and lastly, it gets very confused if the bulb is not 100% on or off.

    let me know what senerio you would like me to try and capture the logs from...

    Leave a comment:


  • rsisson
    replied
    I Installed the latest Beta... (.302)
    At first, it had a hard time finding the bulbs. and then it found them, as always, as full RGB bulbs.
    I edited the config to the right bulb type are restarted the plugin....

    Here is the log from the last startup.

    The log says there are bulbs, but they don't show up in the Device list AT ALL
    Mar-04 12:15:20 PM MagicHome DEBUG Device model AK001-ZJ200 with Mac Address DC4F22873D8B and Firmware Version 1, proceeding to update Homeseer devices.
    Mar-04 12:15:19 PM MagicHome DEBUG Device model AK001-ZJ200 with Mac Address DC4F2287A570 and Firmware Version 1, proceeding to update Homeseer devices.
    Mar-04 12:15:18 PM MagicHome DEBUG MagicHome Device Poll Inititated.
    Mar-04 12:13:35 PM MagicHome DEBUG Updating Device DC4F22873D8B Cool White Value Pairs
    Mar-04 12:13:35 PM MagicHome DEBUG Existing Device Not Found Creating Device DC4F22873D8B in HomeSeer
    Mar-04 12:13:35 PM MagicHome DEBUG Updating Device DC4F22873D8B Warm White Value Pairs
    Mar-04 12:13:35 PM MagicHome DEBUG Existing Device Not Found Creating Device DC4F22873D8B in HomeSeer
    Mar-04 12:13:35 PM MagicHome DEBUG Updating Device DC4F22873D8B Value Pairs
    Mar-04 12:13:35 PM MagicHome DEBUG Existing Device Not Found Creating Device DC4F22873D8B in HomeSeer
    Mar-04 12:13:35 PM MagicHome DEBUG Updating Device DC4F22873D8B Root Device Value Pairs
    Mar-04 12:13:35 PM MagicHome DEBUG Existing Device Not Found Creating Device DC4F22873D8B in HomeSeer
    Mar-04 12:13:35 PM MagicHome DEBUG Device model AK001-ZJ200 with Mac Address DC4F22873D8B and Firmware Version 1, proceeding to update Homeseer devices.
    Mar-04 12:13:34 PM MagicHome DEBUG Updating Device DC4F2287A570 Cool White Value Pairs
    Mar-04 12:13:34 PM MagicHome DEBUG Existing Device Not Found Creating Device DC4F2287A570 in HomeSeer
    Mar-04 12:13:34 PM MagicHome DEBUG Updating Device DC4F2287A570 Warm White Value Pairs
    Mar-04 12:13:34 PM MagicHome DEBUG Existing Device Not Found Creating Device DC4F2287A570 in HomeSeer
    Mar-04 12:13:34 PM MagicHome DEBUG Updating Device DC4F2287A570 Value Pairs
    Mar-04 12:13:34 PM MagicHome DEBUG Existing Device Not Found Creating Device DC4F2287A570 in HomeSeer
    Mar-04 12:13:34 PM MagicHome DEBUG Updating Device DC4F2287A570 Root Device Value Pairs
    Mar-04 12:13:34 PM MagicHome DEBUG Existing Device Not Found Creating Device DC4F2287A570 in HomeSeer
    Mar-04 12:13:34 PM MagicHome DEBUG Device model AK001-ZJ200 with Mac Address DC4F2287A570 and Firmware Version 1, proceeding to update Homeseer devices.
    Mar-04 12:13:28 PM MagicHome DEBUG Discovery is not running on NIC Adapter isatap.{53492571-B147-4A72-8D16-3467CD1CA04C} as it is the Tunnel Interface
    Mar-04 12:13:28 PM MagicHome DEBUG Discovery is not running on NIC Adapter isatap.{31F67249-DB17-4045-95B6-7426925F34D2} as it is the Tunnel Interface
    Mar-04 12:13:28 PM MagicHome DEBUG Discovery is not running on NIC Adapter Teredo Tunneling Pseudo-Interface as it is the Tunnel Interface
    Mar-04 12:13:28 PM MagicHome DEBUG Discovery is not running on NIC Adapter isatap.{4EE87C55-3E66-4DD7-B4DD-111BE630275F} as it is the Tunnel Interface
    Mar-04 12:13:28 PM MagicHome DEBUG Discovery is not running on NIC Adapter isatap.{284AD6E0-31EE-401E-975E-8327791065B8} as it is the Tunnel Interface
    Mar-04 12:13:28 PM MagicHome DEBUG Discovery is not running on NIC Adapter Loopback Pseudo-Interface 1 as it is the Loopback Interface
    Mar-04 12:13:23 PM MagicHome DEBUG Running Discovery on on NIC Adapter Local Area Connection and will target broadcast address 192.168.1.255
    Mar-04 12:13:23 PM MagicHome DEBUG Discovery will run on on NIC Adapter Local Area Connection
    Mar-04 12:13:18 PM MagicHome DEBUG Running Discovery on on NIC Adapter Wireless Network Connection 2 and will target broadcast address 192.168.1.255
    Mar-04 12:13:18 PM MagicHome DEBUG Discovery will run on on NIC Adapter Wireless Network Connection 2
    Mar-04 12:13:18 PM MagicHome DEBUG Discovery will not run on on NIC Adapter Wireless Network Connection 3 as it is either in a non operational state, Does not support Multicast, or we have failed to get IPv4 Properties
    Mar-04 12:13:18 PM MagicHome DEBUG Discovery will not run on on NIC Adapter Wireless Network Connection 4 as it is either in a non operational state, Does not support Multicast, or we have failed to get IPv4 Properties
    Mar-04 12:13:18 PM MagicHome DEBUG MagicHome Device Poll Inititated.
    Mar-04 12:11:34 PM MagicHome DEBUG Unable to discover any Magic Home devices. please restart the plugin to try again
    Mar-04 12:11:34 PM MagicHome DEBUG Discovery is not running on NIC Adapter isatap.{53492571-B147-4A72-8D16-3467CD1CA04C} as it is not an Ethernet or Wireless Interface
    Mar-04 12:11:34 PM MagicHome DEBUG Discovery is not running on NIC Adapter isatap.{31F67249-DB17-4045-95B6-7426925F34D2} as it is not an Ethernet or Wireless Interface
    Mar-04 12:11:34 PM MagicHome DEBUG Discovery is not running on NIC Adapter Teredo Tunneling Pseudo-Interface as it is not an Ethernet or Wireless Interface
    Mar-04 12:11:34 PM MagicHome DEBUG Discovery is not running on NIC Adapter isatap.{4EE87C55-3E66-4DD7-B4DD-111BE630275F} as it is not an Ethernet or Wireless Interface
    Mar-04 12:11:34 PM MagicHome DEBUG Discovery is not running on NIC Adapter isatap.{284AD6E0-31EE-401E-975E-8327791065B8} as it is not an Ethernet or Wireless Interface
    Mar-04 12:11:34 PM MagicHome DEBUG Discovery is not running on NIC Adapter Loopback Pseudo-Interface 1 as it is the Loopback Interface
    Mar-04 12:11:32 PM Z-Wave Device: Node 31 Hallway Operating State Set to Operating State 3
    Mar-04 12:11:24 PM MagicHome DEBUG Running Discovery on on NIC Adapter Local Area Connection and will target broadcast address 192.168.1.255
    Mar-04 12:11:24 PM MagicHome DEBUG Discovery will run on on NIC Adapter Local Area Connection
    Mar-04 12:11:20 PM Z-Wave Device: Node 34 IBB Office Bob's Office Motion Set to NOTIFICATION for type Home Security, Event: Motion Detected
    Mar-04 12:11:18 PM MagicHome DEBUG Running Discovery on on NIC Adapter Wireless Network Connection 2 and will target broadcast address 192.168.1.255
    Mar-04 12:11:18 PM MagicHome DEBUG Discovery will run on on NIC Adapter Wireless Network Connection 2
    Mar-04 12:11:18 PM MagicHome DEBUG Discovery will not run on on NIC Adapter Wireless Network Connection 3 as it is either in a non operational state, Does not support Multicast, or we have failed to get IPv4 Properties
    Mar-04 12:11:18 PM MagicHome DEBUG Discovery will not run on on NIC Adapter Wireless Network Connection 4 as it is either in a non operational state, Does not support Multicast, or we have failed to get IPv4 Properties
    Mar-04 12:11:18 PM MagicHome DEBUG MagicHome Device Poll Inititated.
    Mar-04 12:11:17 PM Plug-In Finished initializing plug-in MagicHome
    Mar-04 12:11:17 PM Starting Plug-In MagicHome loaded in 398 milliseconds
    Mar-04 12:11:17 PM Starting Plug-In Plugin MagicHome started successfully in 30 milliseconds
    Mar-04 12:11:17 PM Warning Attempt by plugin to register a duplicate link of https://forums.homeseer.com/forum/li...ichome-fuzzysb. Plugin: MagicHome Instance:
    Mar-04 12:11:17 PM MagicHome INFO MagicHome version 1.0.0.302
    Mar-04 12:11:17 PM Starting Plug-In Initializing plugin MagicHome ...

    Leave a comment:


  • rsisson
    replied
    Ok, as I suspected, once I used the magiclight app to set the bulbs to %100 and then off, the plugin worked fine. It just doesn't like the status bytes it gets back at anything other than %100 -on- or -off-. Dimming seems to be the issue,, along with all of the stuff that comes along for the ride, like status bytes, which apparently confuse the hell out of it.

    Just my $.02

    Leave a comment:


  • rsisson
    replied
    Sorry for the Long Debug log post, but I wanted to show all of the loads and other messages... I am not sure how to set a "Filter" on the logs yet...

    Leave a comment:


  • rsisson
    replied
    I just loaded the update, got "different" errors...
    Here is the log after a restart...

    Completely lost my HS connection to the bulbs

    I will reset the bulbs to 100% via the Magic Bulb app and try again.
    They were set to 10% via a MagicBulb timer before they were switched off...
    I don't think HS3 understands anything but %100 on/off.
    Feb-23 11:50:27 AM Z-Wave Device: Node 7 Living Room Home Security Set to NOTIFICATION for type Home Security, Event: No Motion
    Feb-23 11:50:14 AM MagicHome DEBUG Setting Device DC4F22873D8B's power state to On
    Feb-23 11:50:14 AM Device Control Device: MagicHome MagicHome Bobs Sunlite to On (100) by/from: CAPI Control Handler
    Feb-23 11:50:12 AM MagicHome ERROR An Error Occurred, the error reported was: only device types RgbWarmwhiteCoolwhite & LegacyRgbWarmwhiteCoolwhite has white2
    Feb-23 11:50:12 AM MagicHome DEBUG Setting Device DC4F22873D8B's brightness to 100
    Feb-23 11:50:12 AM Device Control Device: MagicHome MagicHome Bobs Sunlite to Dim (value)% (100) by/from: CAPI Control Handler
    Feb-23 11:50:03 AM MagicHome DEBUG Setting Device DC4F22873D8B's power state to On
    Feb-23 11:50:03 AM Device Control Device: MagicHome MagicHome Bobs Sunlite to On (100) by/from: CAPI Control Handler
    Feb-23 11:49:37 AM MagicHome ERROR Unable to update the status of device with IP 192.168.1.6 and Mac Address DC4F22873D8B, the error reported was: Controller sent wrong number of bytes while getting status, the number of bytes received was 28 however we were expecting 14 ,the values received were { 129, 82, 36, 97, 0, 0, 25, 0, 0, 0, 1, 0, 0, 114, 129, 82, 36, 97, 0, 0, 25, 0, 0, 0, 1, 0, 0, 114, }
    Feb-23 11:49:36 AM MagicHome ERROR Unable to update the status of device with IP 192.168.1.7 and Mac Address DC4F2287A570, the error reported was: An existing connection was forcibly closed by the remote host
    Feb-23 11:49:36 AM MagicHome DEBUG MagicHome Device Poll Inititated.
    Feb-23 11:49:16 AM Z-Wave Device: Node 5 Computer Area Multi Home Security Set to NOTIFICATION for type Home Security, Event: No Event
    Feb-23 11:48:40 AM Z-Wave Device: Node 34 IBB Office Bob's Office Luminance Set to 33.27 (%)
    Feb-23 11:48:40 AM Z-Wave Device: Node 34 IBB Office Bob's Office Humidity Set to 43.6 (%)
    Feb-23 11:48:40 AM Z-Wave Device: Node 34 IBB Office Bob's Office Temperature Set to 67.4 (F)
    Feb-23 11:48:08 AM Info Amazon Echo Discovery requested, version: 2
    Feb-23 11:47:38 AM MagicHome DEBUG Device model AK001-ZJ200 with Mac Address DC4F22873D8B and Firmware Version 1, proceeding to update Homeseer devices.
    Feb-23 11:47:37 AM MagicHome DEBUG Device model AK001-ZJ200 with Mac Address DC4F2287A570 and Firmware Version 1, proceeding to update Homeseer devices.
    Feb-23 11:47:36 AM MagicHome DEBUG MagicHome Device Poll Inititated.
    Feb-23 11:46:27 AM Z-Wave Device: Node 2 IBB Office Bobs Desk Set to 99
    Feb-23 11:46:27 AM Device Control Device: Node 2 IBB Office Bobs Desk to On (99) by/from: CAPI Control Handler
    Feb-23 11:46:22 AM Z-Wave Device: Node 34 IBB Office Bob's Office Motion Set to NOTIFICATION for type Home Security, Event: Motion Detected
    Feb-23 11:46:11 AM Z-Wave Device: Node 5 Computer Area Multi Home Security Set to NOTIFICATION for type Home Security, Event: Motion Detected
    Feb-23 11:45:44 AM Z-Wave Device: Node 31 Hallway Operating State Set to Operating State 1
    Feb-23 11:45:43 AM Z-Wave Device: Node 31 Hallway Temperature Set to 69 (F)
    Feb-23 11:45:36 AM MagicHome DEBUG Device model AK001-ZJ200 with Mac Address DC4F22873D8B and Firmware Version 1, proceeding to update Homeseer devices.
    Feb-23 11:45:36 AM MagicHome ERROR Unable to update the status of device with IP 192.168.1.7 and Mac Address DC4F2287A570, the error reported was: An existing connection was forcibly closed by the remote host
    Feb-23 11:45:36 AM MagicHome DEBUG MagicHome Device Poll Inititated.
    Feb-23 11:43:57 AM Z-Wave Device: Node 5 Computer Area Multi Home Security Set to NOTIFICATION for type Home Security, Event: No Event
    Feb-23 11:43:37 AM MagicHome DEBUG Device model AK001-ZJ200 with Mac Address DC4F22873D8B and Firmware Version 1, proceeding to update Homeseer devices.
    Feb-23 11:43:37 AM MagicHome DEBUG Updating Device DC4F2287A570 Cool White Value Pairs
    Feb-23 11:43:37 AM MagicHome DEBUG Updating Device DC4F2287A570 Warm White Value Pairs
    Feb-23 11:43:37 AM MagicHome DEBUG Updating Device Sunlite Value Pairs
    Feb-23 11:43:37 AM MagicHome DEBUG Updating Device DC4F2287A570 Root Device Value Pairs
    Feb-23 11:43:37 AM MagicHome DEBUG Device model AK001-ZJ200 with Mac Address DC4F2287A570 and Firmware Version 1, proceeding to update Homeseer devices.
    Feb-23 11:43:36 AM MagicHome DEBUG MagicHome Device Poll Inititated.
    Feb-23 11:43:24 AM MagicHome DEBUG Writing the Log Level Debug to the MagicHome config file MagicHome.ini
    Feb-23 11:43:24 AM MagicHome DEBUG Writing the Log Level Debug to the MagicHome config file MagicHome.ini
    Feb-23 11:43:12 AM Z-Wave Device: Node 5 Computer Area Multi Luminance Set to 35.36 (%)
    Feb-23 11:43:12 AM Z-Wave Device: Node 5 Computer Area Multi Relative Humidity Set to 37.58 (%)
    Feb-23 11:43:12 AM Z-Wave Device: Node 5 Computer Area Multi Temperature Set to 68.882 (F)
    Feb-23 11:42:05 AM Z-Wave Starting Z-Wave Polling for Network E688343F...
    Feb-23 11:42:01 AM TTS Speak ():Web server port number is 80
    Feb-23 11:41:58 AM TTS Speak ():Welcome to Ninovan Home-Seer Control
    Feb-23 11:41:57 AM Speaker Speaker host added, Name: Ninovan-controller Instance: Default IP address: 127.0.0.1
    Feb-23 11:41:52 AM MagicHome ERROR Unable to update the status of all devices as some devices failed to respond to the status update, please check your devices. If a device has been powered down, please restart the plugin to rediscover devices
    Feb-23 11:41:51 AM MagicHome ERROR Unable to update the status of device with IP 192.168.1.7 and Mac Address DC4F2287A570, the error reported was: No connection could be made because the target machine actively refused it 192.168.1.7:5577
    Feb-23 11:41:39 AM Z-Wave ************************************************************ *******************
    Feb-23 11:41:39 AM Z-Wave STARTUP COMPLETE: All configured interfaces were successfully initialized.
    Feb-23 11:41:39 AM Z-Wave ************************************************************ *******************
    Feb-23 11:41:39 AM Web Server Web Server authorized local login successful from: 192.168.1.34 User: default
    Feb-23 11:41:38 AM Z-Wave Nonovan: ............................................................ ..........
    Feb-23 11:41:38 AM Z-Wave Nonovan: .............................. FINISHED ..............................
    Feb-23 11:41:38 AM Z-Wave Nonovan: ............................................................ ..........
    Feb-23 11:41:38 AM Z-Wave Nonovan is the SIS for the network.
    Feb-23 11:41:38 AM Z-Wave Nonovan There is a SUC/SIS in the network.
    Feb-23 11:41:38 AM Z-Wave Nonovan Controller is static lib.
    Feb-23 11:41:38 AM Z-Wave Nonovan Controller chip type is ZW050x.
    Feb-23 11:41:38 AM Z-Wave The interface's security support has been set.
    Feb-23 11:41:38 AM Z-Wave Nonovan: Found 27 Z-Wave nodes in interface node ID 1 (Nonovan)
    Feb-23 11:41:38 AM Z-Wave Nonovan: Z-Wave interface node ID: 1, Home ID: E688343F
    Feb-23 11:41:38 AM Z-Wave Nonovan: Z-Wave Serial API version: 5
    Feb-23 11:41:38 AM Z-Wave Nonovan: Z-Wave services for the SECURITY COMMAND CLASS were successfully started.
    Feb-23 11:41:37 AM Z-Wave Nonovan: Controller firmware version: 1.0
    Feb-23 11:41:37 AM Z-Wave Nonovan: Controller Manufacturer: Aeon Labs, ID=0x5A, Type=0x2
    Feb-23 11:41:36 AM Info System connected to MyHS Service successfully with license ID 97596.
    Feb-23 11:41:36 AM Info System connected to MyHS Service, waiting for acknowledge...
    Feb-23 11:41:36 AM Startup Start up complete.
    Feb-23 11:41:36 AM Startup Starting HSSentry watchdog.
    Feb-23 11:41:35 AM Startup (Startup.vb script) No speaker clients detected, waiting up to 30 seconds for any to connect...
    Feb-23 11:41:35 AM Startup (Startup.vb script) Scripting is OK and is now running Startup.vb
    Feb-23 11:41:35 AM Startup Starting Event Scheduler...
    Feb-23 11:41:35 AM Startup Running the startup script Startup.vb
    Feb-23 11:41:35 AM Startup Starting Find service...
    Feb-23 11:41:35 AM Startup Updater services starting...
    Feb-23 11:41:35 AM Speech Listening for remote speaker connections on port 10401
    Feb-23 11:41:35 AM Startup Initializing Speaker Client Interface
    Feb-23 11:41:35 AM Startup Start automation engine...
    Feb-23 11:41:35 AM Startup HStouch server started, waiting for clients to connect.
    Feb-23 11:41:35 AM HSTouch Server Server started on port 10200
    Feb-23 11:41:35 AM Plug-In Finished initializing plug-in MagicHome
    Feb-23 11:41:35 AM Starting Plug-In MagicHome loaded in 190 milliseconds
    Feb-23 11:41:35 AM Starting Plug-In Plugin MagicHome started successfully in 33 milliseconds
    Feb-23 11:41:35 AM Warning Attempt by plugin to register a duplicate link of https://forums.homeseer.com/forum/li...ichome-fuzzysb. Plugin: MagicHome Instance:
    Feb-23 11:41:35 AM MagicHome INFO MagicHome version 1.0.0.294
    Feb-23 11:41:35 AM Starting Plug-In Initializing plugin MagicHome ...
    Feb-23 11:41:35 AM Info Plugin MagicHome has connected. IP:127.0.0.1:57665
    Feb-23 11:41:35 AM Plug-In Finished initializing plug-in NetCAM
    Feb-23 11:41:35 AM Starting Plug-In NetCAM loaded in 191 milliseconds
    Feb-23 11:41:35 AM Starting Plug-In Plugin NetCAM started successfully in 18 milliseconds
    Feb-23 11:41:35 AM Starting Plug-In Initializing plugin NetCAM ...
    Feb-23 11:41:35 AM Info Plugin NetCAM has connected. IP:127.0.0.1:57663
    Feb-23 11:41:35 AM Plug-In Finished initializing plug-in Z-Wave
    Feb-23 11:41:35 AM Starting Plug-In Z-Wave loaded in 899 milliseconds
    Feb-23 11:41:35 AM Z-Wave Nonovan: Getting node information from controller...
    Feb-23 11:41:35 AM Z-Wave Nonovan: The Z-Wave API Execution Thread was Started or Restarted.
    Feb-23 11:41:35 AM Z-Wave Nonovan: The Z-Wave Command Execution Thread was Started or Restarted.
    Feb-23 11:41:35 AM Z-Wave Nonovan: ----------------------------------------------------------------------
    Feb-23 11:41:35 AM Z-Wave Initializing Z-Wave interface Nonovan (Aeon Labs Aeotec Z-Stick) on COM5
    Feb-23 11:41:35 AM Z-Wave Nonovan: ----------------------------------------------------------------------
    Feb-23 11:41:35 AM Z-Wave Nonovan: ============================================================ ==========
    Feb-23 11:41:35 AM Z-Wave 465 Simple AV Control Command Class Control Commands have been loaded successfully.
    Feb-23 11:41:35 AM Z-Wave 0 event triggers were loaded from HomeSeer.
    Feb-23 11:41:35 AM Z-Wave 0 event actions were loaded from HomeSeer.
    Feb-23 11:41:35 AM Starting Plug-In Plugin Z-Wave started successfully in 451 milliseconds
    Feb-23 11:41:34 AM Z-Wave 90 total Z-Wave Data Objects loaded.
    Feb-23 11:41:34 AM Z-Wave Network E688343F has 90 device data elements.
    Feb-23 11:41:34 AM Z-Wave 1 Networks were restored from the data in the database... Building data connections.
    Feb-23 11:41:34 AM Z-Wave Loading Z-Wave Data Objects...
    Feb-23 11:41:34 AM Z-Wave 1 total Z-Wave Network Objects loaded.
    Feb-23 11:41:34 AM Z-Wave Loading Z-Wave Network Objects...
    Feb-23 11:41:34 AM Z-Wave Database: Opening (Mode=Read Only) up HomeSeer database C:\Program Files (x86)\HomeSeer HS3\Data\Z-Wave\Z-Wave2.db
    Feb-23 11:41:34 AM Z-Wave InitIO called, plug-in version 3.0.1.252 is being initialized...
    Feb-23 11:41:34 AM Starting Plug-In Initializing plugin Z-Wave ...
    Feb-23 11:41:34 AM Info Plugin Z-Wave has connected. IP:127.0.0.1:57661
    Feb-23 11:41:34 AM Startup Initializing Plug-Ins
    Feb-23 11:41:34 AM Plug-In Found plug-in: Z-Wave, version: 3.0.1.252
    Feb-23 11:41:34 AM Plug-In Found plug-in: NetCAM, version: 3.0.0.14
    Feb-23 11:41:34 AM Plug-In Found plug-in: MagicHome, version: 1.0.0.294
    Feb-23 11:41:34 AM Plug-In Found plug-in: AirplaySpeak, version: 3.0.0.13
    Feb-23 11:41:33 AM Startup Checking for available plug-ins
    Feb-23 11:41:33 AM Info Remote plug-in API interface started on port 10400
    Feb-23 11:41:33 AM Startup Creating ASP.NET application host...
    Feb-23 11:41:33 AM Web Server Web Server started on port 80
    Feb-23 11:41:33 AM Web Server Local IP address (subnet) is: 192.168.1.34 (255.255.255.0)
    Feb-23 11:41:33 AM Startup This version of HomeSeer is registered as a HS3STANDARD version.
    Feb-23 11:41:33 AM Startup Creating Speaker Client Interface Object...
    Feb-23 11:41:33 AM Startup HomeSeer version is: 3.0.0.500
    Feb-23 11:41:33 AM Load Config Loading TIMERS...
    Feb-23 11:41:33 AM Load Config Loading COUNTERS...
    Feb-23 11:41:33 AM Load Config 27 total events loaded.
    Feb-23 11:41:33 AM Load Config Loading Events...
    Feb-23 11:41:33 AM Load Config Loading Event Groups...
    Feb-23 11:41:33 AM Load Config 111 total devices loaded.
    Feb-23 11:41:33 AM Database Loading Devices...
    Feb-23 11:41:33 AM Database Opening (Mode=Read Only) up HomeSeer database C:\Program Files (x86)\HomeSeer HS3\Data\Ninovan.hsd
    Feb-23 11:41:33 AM Startup Loading configuration file ...
    Feb-23 11:41:33 AM Startup Database SAVE process started.
    Feb-23 11:41:33 AM Startup Local voice recognition class started.
    Feb-23 11:41:33 AM Startup Plug-In Interface class started.
    Feb-23 11:41:33 AM Startup E-Mail RECEIVE class started.
    Feb-23 11:41:33 AM Startup E-Mail SEND class started.
    Feb-23 11:41:33 AM Startup Web server class started.
    Feb-23 11:41:33 AM Startup Application interface class started.
    Feb-23 11:41:33 AM Startup COM port classes started.
    Feb-23 11:41:33 AM Startup Creating Class Objects...
    Feb-23 11:41:33 AM Startup
    Feb-23 11:41:33 AM Startup ************************************************************ ********************
    Feb-23 11:41:33 AM Startup HomeSeer version 3.0.0.500 Edition: HS3 Standard Starting Now
    Feb-23 11:41:33 AM Startup ************************************************************ ********************

    Leave a comment:


  • rsisson
    replied

    Getting weird messages in the logs.
    Don't seem to be affecting anything, but
    Feb-18 3:19:06 PM MagicHome ERROR Unable to update the status of device with IP 192.168.1.31 and Mac Address DC4F2287A570, the error reported was: Controller sent wrong number of bytes while getting status, the number of bytes received was 28 however we were expecting 14 ,the values received were { 129, 82, 36, 97, 0, 0, 255, 0, 0, 0, 1, 0, 0, 88, 129, 82, 36, 97, 0, 0, 255, 0, 0, 0, 1, 0, 0, 88, }
    and then earlier
    Feb-18 1:45:05 PM MagicHome ERROR Unable to update the status of device with IP 192.168.1.31 and Mac Address DC4F2287A570, the error reported was: Controller sent wrong number of bytes while getting status, the number of bytes received was 28 however we were expecting 14 ,the values received were { 129, 82, 36, 97, 0, 0, 255, 0, 0, 0, 1, 0, 0, 88, 129, 82, 36, 97, 0, 0, 255, 0, 0, 0, 1, 0, 0, 88, }
    Only one bulb is returning this error... they should be setup the same

    Leave a comment:


  • rsisson
    replied
    Again, that is using the Slider on the HS3 screen next to on/off
    NO Alexa..., (Alexa works fine for on/off)

    Leave a comment:


  • rsisson
    replied
    (Embarrassed face)
    Ok, that fixed everything but the dimming.
    when I try to dim from the HS3 app, I get the errors shown in the log.

    Leave a comment:


  • rsisson
    replied
    Will take a while to cycle through all the cleanup, again, but that should solve some stuff.

    Leave a comment:


  • rsisson
    replied
    Ok, think I found part of it...
    of course it was me..
    i was selecting the rgbwarmwhitecoolwhite not warmwhitecoolwhite so obviously it was going to build the wrong thing...

    Leave a comment:


  • fuzzysb
    replied
    as for you wanting 1 slider that goes from warm to cool, the devices themselves have individual channels, so if you want a single slider from warm to cool i would need to create an additional slider for this, just like i create an additional Colour device for the RGB devices so i can specify a colour from a picker.

    Leave a comment:


  • fuzzysb
    replied
    ok lets take a step back, please confirm that you are using at least v1.0.0.287.

    can you also open up the MagicHome config page and give me a screen grab of that? as my testing shows that if you select WarmwhiteCoolwhite my debug shows that its will not create RGB channels.

    i keep looking at your screen grab it looks messed up, all the devices bundled together in one list? have you changed the grouping order? it should show each device grouped under the parent root device. press the purple button at the top right (the one at the right hand side of these shown below)

    Click image for larger version  Name:	Capture.PNG Views:	1 Size:	4.0 KB ID:	1285975

    this will group them together as individual bulbs. and will be easier to see what is being created for each bulb.

    The other thing you can do is go into the MagicHome settings and choose log to file and specify Debug. then delete all devices, restart the plugin and once devices have been created provide me a screen grab of one bulb (with all child devices grouped together) and the full MagicHome.Log file zipped in a Private message so i can see the discovery and device creation in the debug log.

    give me all of this and we will get to the bottom of the issue very quickly. I don't currently have all the info i need to assist you as your results are completely at odds with my debugs.

    my code for the RGB creation has the following conditions in the If statement

    Code:
    if (dev._deviceType == DeviceType.Rgb || dev._deviceType == DeviceType.LegacyRgb || dev._deviceType == DeviceType.RgbWarmwhite ||
                                dev._deviceType == DeviceType.RgbWarmwhiteCoolwhite || dev._deviceType == DeviceType.LegacyRgbWarmwhiteCoolwhite || dev._deviceType == DeviceType.LegacyBulb || dev._deviceType == DeviceType.Bulb)
    {
          <RGB Device creation occurs here>
    }

    so the only way you can hit the code that creates red/blue/green devices is if your device is one of the following device types

    Rgb
    LegacyRgb
    RgbWarmwhite
    RgbWarmwhiteCoolwhite
    LegacyRgbWarmwhiteCoolwhite
    LegacyBulb
    Bulb

    so you show me that you have blue and green devices in the last screen grab, so the only way that got created is if your device is set to one of the above device types, which you select in the drop down in the settings.

    so if you have your device set to the following in the Magichome plugin config page

    WarmwhiteCoolwhite

    can you then check your magichome.ini file in the Config directory it should have the following in it

    Code:
    [MAGICHOME]
    DC4F22873D8B=WarmwhiteCoolwhite
    DC4F2287A570=WarmwhiteCoolwhite

    if you confirm this is the case then you delete all devices then restart the plugin and let them be recreated you should get only the devices looking like the above.

    I have just ran another debug session to ensure i'm not missing anything.

    i set all my lights to the following in the config page.

    Click image for larger version  Name:	Capture.PNG Views:	1 Size:	21.0 KB ID:	1285976


    i then confirmed the values were set the same in the ini file.

    i then deleted all my lights and then restarted the plugin and i get the following for each bulb. and since i only reference the Red/Green/Blue creation in the code section above then its impossible for you to hit that section of code once the device is set to WarmwhiteCoolwhite

    Click image for larger version  Name:	Capture1.PNG Views:	1 Size:	99.4 KB ID:	1285977
    if you are showing different, it can only be that you set the device type after device creation. it must be done before and then the lights deleted, after that point as long as the dropdown is not changed for that device then no RGB devices will be created.



    Leave a comment:


  • rsisson
    replied
    One more thing...HS3 won't let me select "is dimable" on the configuration page.

    "Alexa, turn on Sunlite" is working reliably... YEA!

    now to figure out why no "is dimable" and get rid of all the RGB stuff...

    wont be able to too much tomorrow, work day for me...

    Leave a comment:


  • rsisson
    replied
    Ok, did all that... and it rebuilt the full RGB setup...
    not just the coolwhite/warmwhite I expected...

    Leave a comment:


  • rsisson
    replied
    Ok, I will do a stop plugin, delete all magichome devices, start plugin, wait.

    while I am waiting, I will delete all the random Alexa devices, there were a few...

    when HS3 is happy, I will do another discover..

    let you know how it all works out...

    Leave a comment:

Working...
X