Announcement

Collapse

Contacting HomeSeer This Week

HomeSeer is open and operational this week. All orders are being processed and shipped as usual. However, some staff are working from home. If you need to contact HomeSeer for support or customer service, please use our Email or Chat options. https://homeseer.com/contact-us/
See more
See less

Magic Color Controllers

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

  • #61
    Ok I'm tied up for the next few hours or so. But will get something over later this evening

    Comment


    • #62
      Originally posted by fuzzysb View Post

      That's why the version is in Beta, it worked in my testing, but i don't have issues with no devices being discovered.

      I think i have found further info on your specific device and firmware. try the latest beta (v1.0.0.148) i've just posted, the dropdown for timeout should work now, and i am hoping finally you should now have devices created, if you don't have devices discovered please increase the timeout until you do. I have also added a Retry Discovery button to retry the discovery once you change the timeout. it's worth noting this won't actually create any new discovered devices until the next device status poll interval which will be shown in the log. (however the last debug line will show how many new devices were discovered if indeed they were)
      Installed 248 (I assume that is what you meant by 148 above). Same issue, the drop down does not retain its value. Logs show "ERROR Unable to update the status of device with IP 10.1.2.25 and Mac Address ACCF232F50A0, the error reported was: Controller sent wrong number of bytes while getting status"

      Comment


      • #63
        Yes that was a typo. Ok please enable debug logging and set the timeout value. Does it not write this into the general section of the magichome.ini file? I deleted all my devices and unplugged and I was able to set the timeout value and it did stick
        ​so I'm unsure why you are having an experience at odds with my testing.

        ​​​​​​The error showing the incorrect number of bytes is very strange. As I updated the dubuglog entry to show the error starting with that error but also show how many bytes were recieved and also print out the bytes recieved in the log.... So please enable debug to a file and restart the plugin and forward the log file that includes that entry, as I really don't know how you are getting the same log as the previous version only and not the new entry.

        Comment


        • #64
          ok RK15 can you try the following 3 commands in packet sender

          First of all can you give me the output to

          packetsender -xtw 500 <IP Address> 5577 "81 8A 8B 96"

          Then now try to the following three commands.

          the below if works will set red
          packetsender -xtw 500 <IP Address> 5577 "31 FF 00 00 00 0F 0F 4E"

          the below if works will set Green
          packetsender -xtw 500 <IP Address> 5577 "31 00 FF 00 00 0F 0F 4E"

          the below if works will set Blue
          packetsender -xtw 500 <IP Address> 5577 "31 00 00 FF 00 0F 0F 4E"

          if none of those work then please try the following

          the below if works will set red
          packetsender -xtw 500 1<IP Address> 5577 "31 FF 00 00 00 00 0F 0F 4E"

          the below if works will set Green
          packetsender -xtw 500 <IP Address> 5577 "31 00 FF 00 00 00 0F 0F 4E"

          the below if works will set Blue
          packetsender -xtw 500 <IP Address> 5577 "31 00 00 FF 00 00 0F 0F 4E"

          i need to know if any of these change the colors.

          the strange part is is that the Warm White Sliders and Cool White Sliders use the exact same function to set them as the colours so i am curious as to why only those specifically work.

          please let me know as it will shed some light on your issue. remember to set the IP address to your lights IP

          Thanks.

          Comment


          • #65
            Originally posted by fuzzysb View Post
            Yes that was a typo. Ok please enable debug logging and set the timeout value. Does it not write this into the general section of the magichome.ini file? I deleted all my devices and unplugged and I was able to set the timeout value and it did stick
            ​so I'm unsure why you are having an experience at odds with my testing.

            ​​​​​​The error showing the incorrect number of bytes is very strange. As I updated the dubuglog entry to show the error starting with that error but also show how many bytes were recieved and also print out the bytes recieved in the log.... So please enable debug to a file and restart the plugin and forward the log file that includes that entry, as I really don't know how you are getting the same log as the previous version only and not the new entry.
            So this was an odd one. My interfaces screen showed:
            Click image for larger version

Name:	Screen Shot 2019-02-09 at 10.46.19 AM.png
Views:	12
Size:	78.1 KB
ID:	1283588 \

            But my log did not reflect that version running. Looks like HS had two copies running, got them both shutdown and did a clean start. The setting is indeed being saved now, so this seems like it was a HS bug or a shutdown bug that caused HS to stay attached to the old copy why reporting the new one was installed (Ive seen it before, but no idea on root cause). So anyhow, now for sure running .248/250 (external and logged versions do not match) No devices. Log:

            Interesting error? "the number of bytes received was 22 however we were expecting at least 11"

            Feb-09 10:47:31 INFO MagicHome version 1.0.0.250
            Feb-09 10:47:36 DEBUG MagicHome Device Poll Inititated.
            Feb-09 10:47:36 DEBUG Discovery is not running on NIC Adapter lo as it is the Loopback Interface
            Feb-09 10:47:36 DEBUG Discovery will run on on NIC Adapter eth3
            Feb-09 10:47:36 DEBUG Running Discovery on on NIC Adapter eth3 and will target broadcast address 10.1.3.255
            Feb-09 10:47:42 DEBUG Discovery is not running on NIC Adapter wlan3 as IPv4 is not Enabled on the Interface
            Feb-09 10:47:42 DEBUG Discovery will run on on NIC Adapter eth3.1000
            Feb-09 10:47:42 DEBUG Running Discovery on on NIC Adapter eth3.1000 and will target broadcast address 10.1.103.255
            Feb-09 10:47:47 DEBUG Discovery is not running on NIC Adapter eth3:1 as it is not an Ethernet or Wifi Adapter
            Feb-09 10:47:48 ERROR Unable to update the status of device with IP 10.1.2.25 and Mac Address ACCF232F50A0, the error reported was: Connection timed out
            Feb-09 10:47:48 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-09 10:49:20 DEBUG Writing the Send/Receive Timeout to 500 to the MagicHome config file MagicHome.ini
            Feb-09 10:49:28 DEBUG MagicHome Device Discovery Inititated.
            Feb-09 10:49:28 DEBUG Discovery is not running on NIC Adapter lo as it is the Loopback Interface
            Feb-09 10:49:28 DEBUG Discovery will run on on NIC Adapter eth3
            Feb-09 10:49:28 DEBUG Running Discovery on on NIC Adapter eth3 and will target broadcast address 10.1.3.255
            Feb-09 10:49:33 DEBUG Discovery is not running on NIC Adapter wlan3 as IPv4 is not Enabled on the Interface
            Feb-09 10:49:33 DEBUG Discovery will run on on NIC Adapter eth3.1000
            Feb-09 10:49:33 DEBUG Running Discovery on on NIC Adapter eth3.1000 and will target broadcast address 10.1.103.255
            Feb-09 10:49:36 DEBUG MagicHome Device Poll Inititated.
            Feb-09 10:49:37 ERROR Unable to update the status of device with IP 10.1.2.25 and Mac Address ACCF232F50A0, the error reported was: Controller sent wrong number of bytes while getting status, the number of bytes received was 22 however we were expecting at least 11 ,the values received were System.Byte[]
            Feb-09 10:49:37 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-09 10:49:38 DEBUG Discovery is not running on NIC Adapter eth3:1 as it is not an Ethernet or Wifi Adapter
            Feb-09 10:49:38 DEBUG No New Devices were discovered, not updating discovery list
            Feb-09 10:51:36 DEBUG MagicHome Device Poll Inititated.
            Feb-09 10:51:37 ERROR Unable to update the status of device with IP 10.1.2.25 and Mac Address ACCF232F50A0, the error reported was: Controller sent wrong number of bytes while getting status, the number of bytes received was 22 however we were expecting at least 11 ,the values received were System.Byte[]
            Feb-09 10:51:37 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-09 10:51:43 DEBUG Writing the Send/Receive Timeout to 2000 to the MagicHome config file MagicHome.ini
            Feb-09 10:51:44 DEBUG MagicHome Device Discovery Inititated.
            Feb-09 10:51:44 DEBUG Discovery is not running on NIC Adapter lo as it is the Loopback Interface
            Feb-09 10:51:44 DEBUG Discovery will run on on NIC Adapter eth3
            Feb-09 10:51:44 DEBUG Running Discovery on on NIC Adapter eth3 and will target broadcast address 10.1.3.255
            Feb-09 10:51:49 DEBUG Discovery is not running on NIC Adapter wlan3 as IPv4 is not Enabled on the Interface
            Feb-09 10:51:49 DEBUG Discovery will run on on NIC Adapter eth3.1000
            Feb-09 10:51:49 DEBUG Running Discovery on on NIC Adapter eth3.1000 and will target broadcast address 10.1.103.255
            Feb-09 10:51:54 DEBUG Discovery is not running on NIC Adapter eth3:1 as it is not an Ethernet or Wifi Adapter
            Feb-09 10:51:54 DEBUG No New Devices were discovered, not updating discovery list
            Feb-09 10:52:40 DEBUG Writing the Send/Receive Timeout to 5000 to the MagicHome config file MagicHome.ini
            Feb-09 10:52:41 DEBUG MagicHome Device Discovery Inititated.
            Feb-09 10:52:41 DEBUG Discovery is not running on NIC Adapter lo as it is the Loopback Interface
            Feb-09 10:52:41 DEBUG Discovery will run on on NIC Adapter eth3
            Feb-09 10:52:41 DEBUG Running Discovery on on NIC Adapter eth3 and will target broadcast address 10.1.3.255
            Feb-09 10:52:46 DEBUG Discovery is not running on NIC Adapter wlan3 as IPv4 is not Enabled on the Interface
            Feb-09 10:52:46 DEBUG Discovery will run on on NIC Adapter eth3.1000
            Feb-09 10:52:46 DEBUG Running Discovery on on NIC Adapter eth3.1000 and will target broadcast address 10.1.103.255
            Feb-09 10:52:51 DEBUG Discovery is not running on NIC Adapter eth3:1 as it is not an Ethernet or Wifi Adapter
            Feb-09 10:52:51 DEBUG No New Devices were discovered, not updating discovery list


            Attached Files

            Comment


            • #66
              bsobel just posted v1.0.0.252 this should i think definitely sort you out, you were right that the error message was interesting. it was a **** up in my logic because of a typo i did >= 11 bytes instead of <= 11 bytes, i've fixed the versioning as i use automatic versioning, it had inadvertently increased the assembly version above the file version. this has been corrected so they are now both at .252

              Comment


              • #67
                Originally posted by fuzzysb View Post
                bsobel just posted v1.0.0.252 this should i think definitely sort you out, you were right that the error message was interesting. it was a **** up in my logic because of a typo i did >= 11 bytes instead of <= 11 bytes, i've fixed the versioning as i use automatic versioning, it had inadvertently increased the assembly version above the file version. this has been corrected so they are now both at .252
                Awesome, off to install.

                Comment


                • #68
                  I am very happy to report that I now indeed have devices created. I can't actually fully test as I am at a different house, but will be going to the compound tomorrow and will visual validate the lights are working. I am trying to determine the right testing for the timeout, I lowered it to 200ms but am seeing an error with different settings now:

                  "Unable to update the status of device with IP 10.1.2.25 and Mac Address ACCF232F50A0, the error reported was: Nullable object must have a value."

                  Suggestions on that?

                  Feb-09 12:16:19 INFO MagicHome version 1.0.0.252
                  Feb-09 12:16:23 DEBUG MagicHome Device Poll Inititated.
                  Feb-09 12:16:23 DEBUG Discovery is not running on NIC Adapter lo as it is the Loopback Interface
                  Feb-09 12:16:23 DEBUG Discovery will run on on NIC Adapter eth3
                  Feb-09 12:16:24 DEBUG Running Discovery on on NIC Adapter eth3 and will target broadcast address 10.1.3.255
                  Feb-09 12:16:29 DEBUG Discovery is not running on NIC Adapter wlan3 as IPv4 is not Enabled on the Interface
                  Feb-09 12:16:29 DEBUG Discovery will run on on NIC Adapter eth3.1000
                  Feb-09 12:16:29 DEBUG Running Discovery on on NIC Adapter eth3.1000 and will target broadcast address 10.1.103.255
                  Feb-09 12:16:34 DEBUG Discovery is not running on NIC Adapter eth3:1 as it is not an Ethernet or Wifi Adapter
                  Feb-09 12:16:39 DEBUG Device model HF-A11-ZJ002 with Mac Address ACCF232F50A0 and Firmware Version 153, proceeding to update Homeseer devices.
                  Feb-09 12:17:05 DEBUG Existing Device Not Found Creating Device ACCF232F50A0 in HomeSeer
                  Feb-09 12:17:05 DEBUG Updating Device ACCF232F50A0 Root Device Value Pairs
                  Feb-09 12:17:21 DEBUG Existing Device Not Found Creating Device ACCF232F50A0 in HomeSeer
                  Feb-09 12:17:21 DEBUG Updating Device ACCF232F50A0 Value Pairs
                  Feb-09 12:17:35 DEBUG Writing the Send/Receive Timeout to 200 to the MagicHome config file MagicHome.ini
                  Feb-09 12:17:36 DEBUG Existing Device Not Found Creating Device ACCF232F50A0 in HomeSeer
                  Feb-09 12:17:36 DEBUG Updating Device ACCF232F50A0 Colour Value Pairs
                  Feb-09 12:17:51 DEBUG Writing the Send/Receive Timeout to 500 to the MagicHome config file MagicHome.ini
                  Feb-09 12:17:51 DEBUG MagicHome Device Discovery Inititated.
                  Feb-09 12:17:51 DEBUG Discovery is not running on NIC Adapter lo as it is the Loopback Interface
                  Feb-09 12:17:51 DEBUG Discovery will run on on NIC Adapter eth3
                  Feb-09 12:17:51 DEBUG Running Discovery on on NIC Adapter eth3 and will target broadcast address 10.1.3.255
                  Feb-09 12:17:51 DEBUG Existing Device Not Found Creating Device ACCF232F50A0 in HomeSeer
                  Feb-09 12:17:51 DEBUG Updating Device ACCF232F50A0 Red Value Pairs
                  Feb-09 12:17:56 DEBUG Discovery is not running on NIC Adapter wlan3 as IPv4 is not Enabled on the Interface
                  Feb-09 12:18:12 DEBUG Discovery will run on on NIC Adapter eth3.1000
                  Feb-09 12:18:12 DEBUG Running Discovery on on NIC Adapter eth3.1000 and will target broadcast address 10.1.103.255
                  Feb-09 12:18:12 DEBUG Existing Device Not Found Creating Device ACCF232F50A0 in HomeSeer
                  Feb-09 12:18:12 DEBUG Updating Device ACCF232F50A0 Green Value Pairs
                  Feb-09 12:18:17 DEBUG Discovery is not running on NIC Adapter eth3:1 as it is not an Ethernet or Wifi Adapter
                  Feb-09 12:18:23 DEBUG MagicHome Device Poll Inititated.
                  Feb-09 12:18:49 DEBUG No New Devices were discovered, not updating discovery list
                  Feb-09 12:18:49 DEBUG Existing Device Not Found Creating Device ACCF232F50A0 in HomeSeer
                  Feb-09 12:18:49 DEBUG Updating Device ACCF232F50A0 Blue Value Pairs
                  Feb-09 12:19:23 DEBUG Existing Device Not Found Creating Device ACCF232F50A0 in HomeSeer
                  Feb-09 12:19:23 DEBUG Updating Device ACCF232F50A0 Warm White Value Pairs
                  Feb-09 12:19:56 DEBUG Writing the Send/Receive Timeout to 200 to the MagicHome config file MagicHome.ini
                  Feb-09 12:19:56 DEBUG Existing Device Not Found Creating Device ACCF232F50A0 in HomeSeer
                  Feb-09 12:19:56 DEBUG Updating Device ACCF232F50A0 Preset Value Pairs
                  Feb-09 12:19:57 ERROR Unable to update the status of device with IP 10.1.2.25 and Mac Address ACCF232F50A0, the error reported was: Nullable object must have a value.
                  Feb-09 12:19:59 DEBUG MagicHome Device Discovery Inititated.
                  Feb-09 12:19:59 DEBUG Discovery is not running on NIC Adapter lo as it is the Loopback Interface
                  Feb-09 12:19:59 DEBUG Discovery will run on on NIC Adapter eth3
                  Feb-09 12:19:59 DEBUG Running Discovery on on NIC Adapter eth3 and will target broadcast address 10.1.3.255
                  Feb-09 12:20:02 DEBUG Device model HF-A11-ZJ002 with Mac Address ACCF232F50A0 and Firmware Version 153, proceeding to update Homeseer devices.
                  Feb-09 12:20:02 ERROR Unable to update the status of device with IP 10.1.2.25 and Mac Address ACCF232F50A0, the error reported was: Nullable object must have a value.
                  Feb-09 12:20:04 DEBUG Discovery is not running on NIC Adapter wlan3 as IPv4 is not Enabled on the Interface
                  Feb-09 12:20:04 DEBUG Discovery will run on on NIC Adapter eth3.1000
                  Feb-09 12:20:04 DEBUG Running Discovery on on NIC Adapter eth3.1000 and will target broadcast address 10.1.103.255
                  Feb-09 12:20:09 DEBUG Discovery is not running on NIC Adapter eth3:1 as it is not an Ethernet or Wifi Adapter
                  Feb-09 12:20:09 DEBUG No New Devices were discovered, not updating discovery list
                  Feb-09 12:20:23 DEBUG MagicHome Device Poll Inititated.
                  Feb-09 12:20:29 DEBUG Device model HF-A11-ZJ002 with Mac Address ACCF232F50A0 and Firmware Version 153, proceeding to update Homeseer devices.
                  Feb-09 12:20:29 ERROR Unable to update the status of device with IP 10.1.2.25 and Mac Address ACCF232F50A0, the error reported was: Nullable object must have a value.

                  Comment


                  • #69
                    Update, can not actually control the lights, I get the same nullable error when I try to:

                    Feb-09 12:22:23 DEBUG Setting Device ACCF232F50A0's power state to On
                    Feb-09 12:22:23 DEBUG MagicHome Device Poll Inititated.
                    Feb-09 12:22:24 DEBUG Device model HF-A11-ZJ002 with Mac Address ACCF232F50A0 and Firmware Version 153, proceeding to update Homeseer devices.
                    Feb-09 12:22:24 ERROR Unable to update the status of device with IP 10.1.2.25 and Mac Address ACCF232F50A0, the error reported was: Nullable object must have a value.
                    Feb-09 12:22:25 ERROR An Error Occurred, the error reported was: Nullable object must have a value.

                    So we are close, very close

                    Comment


                    • #70
                      Ok good. I've got your status return your posted previously. Just need to figure out why it's stating the nullable value requires a value (it's a stupud error as it should have been assigned null for the cold white parameter). I should be able to test it with the status output you posted previously. Leave it with me and I will figure it out

                      Comment


                      • #71
                        Originally posted by fuzzysb View Post
                        Ok good. I've got your status return your posted previously. Just need to figure out why it's stating the nullable value requires a value (it's a stupud error as it should have been assigned null for the cold white parameter). I should be able to test it with the status output you posted previously. Leave it with me and I will figure it out
                        Will do thanks!!

                        Comment


                        • #72

                          packetsender -xtw 500 192.168.0.188 5577 "81 8A 8B 96"

                          c:\Program Files\PacketSender>packetsender -xtw 500 192.168.0.188 5577 "81 8A 8B 96"
                          TCP (54826)://192.168.0.188:5577 81 8A 8B 96

                          Response Time:18:06:05.443
                          Response HEX:81 25 24 61 04 1F FF FF FF 01 02 00 0F 5D
                          Response ASCII:\81%$a\04\1f\ff\ff\ff\01\02\00\0f]

                          ----------------------------------------------------------------
                          NO LIGHTS CHANGED BELOW

                          c:\Program Files\PacketSender>packetsender -xtw 500 192.168.0.188 5577 "31 FF 00 00 00 0F 0F 4E"
                          TCP (55201)://192.168.0.188:5577 31 FF 00 00 00 0F 0F 4E


                          c:\Program Files\PacketSender>packetsender -xtw 500 192.168.0.188 5577 "31 00 FF 00 00 0F 0F 4E"
                          TCP (55229)://192.168.0.188:5577 31 00 FF 00 00 0F 0F 4E


                          c:\Program Files\PacketSender>packetsender -xtw 500 192.168.0.188 5577 "31 00 00 FF 00 0F 0F 4E"
                          TCP (55248)://192.168.0.188:5577 31 00 00 FF 00 0F 0F 4E


                          c:\Program Files\PacketSender>packetsender -xtw 500 192.168.0.188 5577 "31 FF 00 00 00 00 0F 0F 4E"
                          TCP (55328)://192.168.0.188:5577 31 FF 00 00 00 00 0F 0F 4E

                          Response Time:18:10:53.821
                          Response HEX:30
                          Response ASCII:0

                          c:\Program Files\PacketSender>packetsender -xtw 500 192.168.0.188 5577 "31 00 FF 00 00 00 0F 0F 4E"
                          TCP (55359)://192.168.0.188:5577 31 00 FF 00 00 00 0F 0F 4E

                          Response Time:18:11:09.985
                          Response HEX:30
                          Response ASCII:0

                          c:\Program Files\PacketSender>packetsender -xtw 500 192.168.0.188 5577 "31 00 00 FF 00 00 0F 0F 4E"
                          TCP (55379)://192.168.0.188:5577 31 00 00 FF 00 00 0F 0F 4E

                          Response Time:18:11:21.754
                          Response HEX:30
                          Response ASCII:0

                          Comment


                          • #73
                            RK15 i'm definately non the wiser. The last three commands your light has accepted and provided a 0 response which is effectively an OK. Which is the exact same response when my lights accept and change colour.

                            Problem is that yours don't actually change colour.

                            I do have to check the obvious however that the lights were on before you sent the command? as colour controls don't work when the lights are off

                            I am just clutching at straws as you said that the warm and cool white controls do actually work?

                            So they would be

                            warm white:
                            ​​​​​packetsender -xtw 500 192.168.0.188 5577 "31 00 00 00 FF 00 0F 0F 4E"

                            And

                            cool white:
                            packetsender -xtw 500 192.168.0.188 5577 "31 00 00 00 00 FF 0F 0F 4E"

                            Could you also try this one last commands to set red colour and let me know if this one works.

                            packetsender -xtw 500 192.168.0.188 5577 "31 FF 00 00 00 00 F0 0F 2F"

                            Can you check you also get the same ascii 0 return and the lights do change. II a going to have to look around on various other forums for the Linux HA solutions like openhab and their plugin to see if I can catch anyone else hitting this issue with the colour control only.

                            However if you know how to perform a packet capture, you can easily do If you have an android device, there is an app called Packet Capture and this can capture packets sent from an individual app. If you then select hex when viewing the trace and you could provide me the packet that is sent when you set the colour from your app then it would provide all the answers.

                            ​​​​​ If not I will look around some more.
                            ​​​​

                            Comment


                            • #74
                              bsobel i think i found the issue with your device, looks to be another Mono quirk. the code i have to check the dim level works on Windows with your status return from your device, but failed on Mono with the error "Nullable object must have a value"

                              I have rewritten the function with extra checks in place and this now runs for both. so fingers crossed this works for you with the new 1.0.0.254 beta.

                              Comment


                              • #75
                                packetsender -xtw 500 192.168.0.188 5577 "31 FF 00 00 00 00 F0 0F 2F"
                                That work to turn on the red and the others work to for cool and warm

                                Comment

                                Working...
                                X