Announcement

Collapse
No announcement yet.

Magic Color Controllers

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

  • Magic Color Controllers

    Hi,

    I have an existing room with a MagicColor controller. Looks to be a LedNet controller. Naively these seem 'similar' to what you support, I am trying to determine if they are close enough that it makes sense to request you add support (its been on the list of addins to write, but low priority with the others in the works).

    Docs attached, could you take a peek and lmk if you could support it? Scratch that, the attachment is 3.4 meg (larger than the forum allows) Can I email it to you directly?

    Best
    Bill

    Click image for larger version

Name:	Screen Shot 2019-01-17 at 10.01.18 AM.png
Views:	43
Size:	287.8 KB
ID:	1276851

  • #2
    I *think* this controls them correctly, FYI

    Attached Files

    Comment


    • #3
      The lednet controllers support has been requested in the other thread in this forum. I have a device turning up today, after which i will be able to work on adding support. just to set your expectations though, it may take a while as i am currently busy with my job which is currently sucking up all my free time

      Comment


      • #4
        Originally posted by fuzzysb View Post
        The lednet controllers support has been requested in the other thread in this forum. I have a device turning up today, after which i will be able to work on adding support. just to set your expectations though, it may take a while as i am currently busy with my job which is currently sucking up all my free time
        Great and understood. I write plugins as well but also have the ‘real’ job. Been on my list to tackle but I try to avoid writing plugins too close to others if the existing one will get to it. Not a huge rush, running with some scripts but a better solution eventually will be nice.

        Thanks
        Bill

        Comment


        • #5
          Are you sure my plugin doesn't work with your lights? please use the latest beta and test. from my reading, the LedNet and MagicHome Controllers are all ESP8266 controllers. i believe this may well work already.

          Comment


          • #6
            Originally posted by fuzzysb View Post
            Are you sure my plugin doesn't work with your lights? please use the latest beta and test. from my reading, the LedNet and MagicHome Controllers are all ESP8266 controllers. i believe this may well work already.
            Just grabbed the latest, it doesn't find the controller (its on the network, my phone finds it). I also get a warning at each startup:

            Attempt by plugin to register a duplicate link of https://forums.homeseer.com/forum/li...ichome-fuzzysb. Plugin: MagicHome Instance:

            I put the plugin to debug mode, but all the HS log shows is the startup. I don't see any log messages about discovery or anything like that. Anything else I can try? Screen shot is from when I started it in info mode, but no change in logging for debug mode.

            Click image for larger version

Name:	Screen Shot 2019-01-24 at 1.18.51 PM.png
Views:	42
Size:	53.7 KB
ID:	1278831Click image for larger version

Name:	Screen Shot 2019-01-24 at 1.23.32 PM.png
Views:	41
Size:	100.4 KB
ID:	1278832

            Comment


            • #7
              One thought, how are you doing your subnet scan? I assume multicast, but if perchance you are doing an actual scan Im on a /22 not /24

              Controller is 10.1.2.25/255.255.252.0 HS is 10.1.0.20/255.255.252.0 FYI...

              Comment


              • #8
                Ok the discovery sends a udp broadcast packet on Port 48899 on the HS machine or a Windows machine in the same subnet, type the following into power shell and confirm it also returns 255.255.255.255

                [System.Net.IPAddress]::Broadcast

                I also can't find the android app in the UK store you posted in the instructions in the earlier post.

                Comment


                • #9
                  Originally posted by fuzzysb View Post
                  Ok the discovery sends a udp broadcast packet on Port 48899 on the HS machine or a Windows machine in the same subnet, type the following into power shell and confirm it also returns 255.255.255.255
                  [System.Net.IPAddress]::Broadcast
                  I also can't find the android app in the UK store you posted in the instructions in the earlier post.
                  I confirmed the port you are using appears correct, my guess is the non class-c is causing the problem. Can you calculate the broadcast address (assuming today you are using .255 on the same class C). Second concern is there is a virtual NIC (10.1.100.x/255.255.252.0). Are you broadcasting on all available NICs or the first you come across?

                  Its on a SEL (linux) box, so no power shell (otherwise I would have confirmed). My phone is iOS, app is called Magic Color. Haven't looked for it on Android (no Android device to check with). Broadcast would be 10.1.3.255 for that network, full network addresses:

                  Address: 10.1.0.0 00001010.00000001.000000 00.00000000 Netmask: 255.255.252.0 = 22 11111111.11111111.111111 00.00000000 Wildcard: 0.0.3.255 00000000.00000000.000000 11.11111111 => Network: 10.1.0.0/22 00001010.00000001.000000 00.00000000 (Class A) Broadcast: 10.1.3.255 00001010.00000001.000000 11.11111111 HostMin: 10.1.0.1 00001010.00000001.000000 00.00000001 HostMax: 10.1.3.254 00001010.00000001.000000 11.11111110 Hosts/Net: 1022 (Private Internet) Here is the actual ifConfig confirming:
                  eth3 Link encap:Ethernet HWaddr 1c:1b:0d:8e:ae:7a
                  inet addr:10.1.0.20 Bcast:10.1.3.255 Mask:255.255.252.0
                  inet6 addr: fe80::1e1b:dff:fe8e:ae7a/64 Scope:Link
                  UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
                  RX packets:3524615 errors:0 dropped:7636 overruns:0 frame:0
                  TX packets:2038565 errors:0 dropped:0 overruns:0 carrier:0
                  collisions:0 txqueuelen:1000
                  RX bytes:2144633264 (2.1 GB) TX bytes:599577717 (599.5 MB)

                  eth3.1000 Link encap:Ethernet HWaddr 1c:1b:0d:8e:ae:7a
                  inet addr:10.1.101.20 Bcast:10.1.103.255 Mask:255.255.252.0
                  inet6 addr: fe80::1e1b:dff:fe8e:ae7a/64 Scope:Link
                  UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
                  RX packets:504100 errors:0 dropped:0 overruns:0 frame:0
                  TX packets:336636 errors:0 dropped:0 overruns:0 carrier:0
                  collisions:0 txqueuelen:0
                  RX bytes:41945525 (41.9 MB) TX bytes:27612404 (27.6 MB)


                  Manual link:
                  http://www.ledmagical.com/Apps/image...20,370)-EN.pdf

                  Comment


                  • #10
                    I have released v1.0.0.146 in the Beta section, this now has a modified discovery which will ensure it broadcasts the discovery on all nics. i think this was the issue.

                    In my testing with a large number vnics on different subnets I tried /16 /22 /24 /28 i got duplicates returned in the result set so i know it was broadcasting on multiple nics. I have performed a deduplication of the broadcast resultset by mac, but if you weren't getting any returns, you should hopefully do so now.

                    Comment


                    • #11
                      Originally posted by fuzzysb View Post
                      I have released v1.0.0.146 in the Beta section, this now has a modified discovery which will ensure it broadcasts the discovery on all nics. i think this was the issue.

                      In my testing with a large number vnics on different subnets I tried /16 /22 /24 /28 i got duplicates returned in the result set so i know it was broadcasting on multiple nics. I have performed a deduplication of the broadcast resultset by mac, but if you weren't getting any returns, you should hopefully do so now.
                      Off to test, will report back. Thank you!

                      Comment


                      • #12
                        Originally posted by fuzzysb View Post
                        I have released v1.0.0.146 in the Beta section, this now has a modified discovery which will ensure it broadcasts the discovery on all nics. i think this was the issue.

                        In my testing with a large number vnics on different subnets I tried /16 /22 /24 /28 i got duplicates returned in the result set so i know it was broadcasting on multiple nics. I have performed a deduplication of the broadcast resultset by mac, but if you weren't getting any returns, you should hopefully do so now.
                        On 1.0.0.146, unfortunately same issue, no results reported. Any debugging I can do to help?

                        Comment


                        • #13
                          I think then we need to step back and do some sanity checking.

                          from any machine on the same network as your lights, can be Windows/Linux/Mac

                          get packetsender from https://github.com/dannagle/PacketSender or compile on your linux build if fuse doesnt work for the portable version and run the following

                          packetsender -uaw 5000 255.255.255.255 48899 HF-A11ASSISTHREAD

                          on my network it returns all lights:


                          Code:
                          From: ::ffff:192.168.1.36, Port:48899
                          Response Time:10:48:50.580
                          Response HEX:31 39 32 2E 31 36 38 2E 31 30 2E 33 36 2C 36 30 30 31 39 34 38 37 46 38 41 32 2C 41 4B 30 30 31 2D 5A 4A 32 30 30
                          Response ASCII:192.168.1.36,600193A7F8A2,AK001-ZJ200
                          From: ::ffff:192.168.1.155, Port:48899
                          Response Time:10:48:50.581
                          Response HEX:31 39 32 2E 31 36 38 2E 31 30 2E 31 35 35 2C 38 34 30 44 38 45 34 31 33 30 35 41 2C 41 4B 30 30 31 2D 5A 4A 32 30 30
                          Response ASCII:192.168.1.155,840D8A91305A,AK001-ZJ200
                          From: ::ffff:192.168.1.122, Port:48899
                          Response Time:10:48:50.584
                          Response HEX:31 39 32 2E 31 36 38 2E 31 30 2E 31 32 32 2C 36 30 30 31 39 34 38 41 41 45 36 35 2C 41 4B 30 30 31 2D 5A 4A 32 30 30
                          Response ASCII:192.168.1.122,600194842E65,AK001-ZJ200
                          From: ::ffff:192.168.1.137, Port:48899
                          Response Time:10:48:50.588
                          Response HEX:31 39 32 2E 31 36 38 2E 31 30 2E 31 33 37 2C 35 43 43 46 37 46 32 41 31 35 39 45 2C 41 4B 30 30 31 2D 5A 4A 31 30 30
                          Response ASCII:192.168.1.137,5CDE7F2A159E,AK001-ZJ100
                          From: ::ffff:192.168.1.140, Port:48899
                          Response Time:10:48:50.591
                          Response HEX:31 39 32 2E 31 36 38 2E 31 30 2E 31 34 30 2C 35 43 43 46 37 46 32 39 30 44 42 31 2C 41 4B 30 30 31 2D 5A 4A 31 30 30
                          Response ASCII:192.168.1.140,5CCF7C690DB1,AK001-ZJ100
                          if that doesn't do the same on your network then you can try:

                          packetsender -uaw 5000 10.1.3.255 48899 HF-A11ASSISTHREAD

                          try a couple of times for each, however if none of those give any returns then your lights do not respond the standard discovery for these devices. the sample from that ChaseFox website, although device control looks to be the same that did not list a discovery method.

                          but all though Magic Color v2 app is not in the Google Play Store, i did find https://magic-color-v2.en.uptodown.com/android but when installing it, it states its no longer supported and to download Magic Home. if i continue it runs a discovery but discovers nothing, but if i then open up the Magic Home app and that discovers, the other app then discovers the devices but marks them as unknown controllers.

                          that app above is developed by Zengge which is the same developer for Magic Home, if you download the newest Magic Home app on your IOS device, does this discover the devices? I suspect not

                          the only other way you could get this is to run a packet capture, of your app to see if you can capture the discovery packet. i tried from the android app but it doesn't seem to transmit any packets. the fact it says its unsupported makes me think they have crippled the app.

                          another solution is run the following python script

                          Code:
                          #!/usr/bin/python3
                          from socket import *
                          import sys
                          
                          if (len(sys.argv)==3 and sys.argv[1]=='-l'):
                              try:
                                   port=int(sys.argv[2])
                              except ValueError as verr:
                                  print('Invalid port number')
                                  sys.exit(1)
                              try:
                                  s=socket(AF_INET, SOCK_DGRAM)
                                  s.bind(('',port))
                                  while True:
                                      data,address=s.recvfrom(1024)
                                      print((data.decode('utf-8')).rstrip())
                                  s.close()
                              except (KeyboardInterrupt, SystemExit):
                                  s.close()
                                  print('Exit on Keyboard Interrupt')
                          else:
                              print('UDP socket listener by JirkaRCK v1.0\nArguments:\n-l Listen on specific UDP port')
                          and i then run

                          ./getmsg.py -l 48899

                          i see the following output when my plugin, or the magic home app perform a discovery.

                          HF-A11ASSISTHREAD
                          HF-A11ASSISTHREAD
                          HF-A11ASSISTHREAD
                          HF-A11ASSISTHREAD
                          HF-A11ASSISTHREAD
                          HF-A11ASSISTHREAD
                          HF-A11ASSISTHREAD
                          HF-A11ASSISTHREAD
                          HF-A11ASSISTHREAD
                          HF-A11ASSISTHREAD
                          HF-A11ASSISTHREAD


                          do you see anything when running your app? if not then it is not doing a discovery on 48899 and is most likely incompatible with this plugin or control set. sorry

                          Comment


                          • #14
                            At a different house this morning but will go back there this afternoon and try this out. Will report back. Thanks!

                            Comment


                            • #15
                              Fyi I do see the HF-A11ASSISTHREAD when I run the iPhone app. I will see if I also see if form the plugin when I get there.

                              Comment

                              Working...
                              X