search

genielabs / HomeGenie

HomeGenie, the programmable automation intelligence
https://homegenie.it
GNU General Public License v3.0
395 stars 155 forks source link

Support for CM19E X10 controller #343

Closed mralapete closed 5 years ago

mralapete commented 5 years ago

The X10 controller CM15Pro has now been discontinued. The only X10 controller now available for sale in Europe is the CM19E, a USB RF only unit. The Vendor ID number for the CM15Pro is 0bc70001 while the Vendor ID number for the CM19E is 0bc70002. The protocol for both units is similar except the CM19E does not include PL (Power Line) control.

Would it be possible to edit the XtenLib to add support for this controller.

tuicemen commented 5 years ago

Ok says build successful but don't see the test program even in the bin/Debug folder

tuicemen commented 5 years ago

ok reran the build and the exe file is now there

tuicemen commented 5 years ago

ok looks like it is seeing RF How do I test the send?

tuicemen commented 5 years ago

Ok figured it out! it sends A1 as soon as the app starts followed by seeing any RF activity. works fine here!

genemars commented 5 years ago

@tuicemen that's awesome. Would you please paste some output so I can ensure that everything is ok and that I can proceed in writing the real driver.

tuicemen commented 5 years ago

sure. I'll reconnect and collect some info or does it save a log somewhere? I noticed security RF codes seemed a little short when watching earlier so I'll try to capture some of those events

tuicemen commented 5 years ago 
2018-11-30 13:55:12.2794 CM19xTest.Program.Main Debug FF
2018-11-30 13:55:13.5256 CM19xTest.Program.Main Debug 02-00
2018-11-30 13:55:13.6136 CM19xTest.Program.Main Debug 02-80
2018-11-30 13:55:23.6414 CM19xTest.Program.Main Debug
2018-11-30 13:55:32.2236 CM19xTest.Program.Main Debug 20-60-9F-20-DF
2018-11-30 13:55:32.3253 CM19xTest.Program.Main Debug 20-60-9F-20-DF
2018-11-30 13:55:32.4373 CM19xTest.Program.Main Debug 20-60-9F-20-DF
2018-11-30 13:55:32.5414 CM19xTest.Program.Main Debug 20-60-9F-20-DF
2018-11-30 13:55:32.6453 CM19xTest.Program.Main Debug 20-60-9F-20-DF
2018-11-30 13:55:32.7573 CM19xTest.Program.Main Debug 20-60-9F-20-DF
2018-11-30 13:55:42.7618 CM19xTest.Program.Main Debug
2018-11-30 13:55:52.7699 CM19xTest.Program.Main Debug
2018-11-30 13:56:01.0932 CM19xTest.Program.Main Debug 02-C0
2018-11-30 13:56:01.2052 CM19xTest.Program.Main Debug 02-C0
2018-11-30 13:56:10.8452 CM19xTest.Program.Main Debug 02-40
2018-11-30 13:56:10.8535 CM19xTest.Program.Main Debug 02-00
2018-11-30 13:56:10.9732 CM19xTest.Program.Main Debug 02-00
2018-11-30 13:56:11.0692 CM19xTest.Program.Main Debug 02-80
2018-11-30 13:56:18.5174 CM19xTest.Program.Main Debug 20-60-9F-08-F7
2018-11-30 13:56:18.8376 CM19xTest.Program.Main Debug 20-60-9F-08-F7
2018-11-30 13:56:18.9494 CM19xTest.Program.Main Debug 20-60-9F-08-F7
2018-11-30 13:56:19.0534 CM19xTest.Program.Main Debug 20-60-9F-08-F7
2018-11-30 13:56:24.4934 CM19xTest.Program.Main Debug 02-C0
2018-11-30 13:56:24.5175 CM19xTest.Program.Main Debug 02-00
2018-11-30 13:56:24.6454 CM19xTest.Program.Main Debug 02-40
2018-11-30 13:56:31.8375 CM19xTest.Program.Main Debug 20-60-9F-18-E7
2018-11-30 13:56:31.9414 CM19xTest.Program.Main Debug 20-60-9F-18-E7
2018-11-30 13:56:32.0534 CM19xTest.Program.Main Debug 20-60-9F-18-E7
2018-11-30 13:56:32.1575 CM19xTest.Program.Main Debug 20-60-9F-18-E7
2018-11-30 13:56:32.2614 CM19xTest.Program.Main Debug 20-60-9F-18-E7
2018-11-30 13:56:32.3734 CM19xTest.Program.Main Debug 20-60-9F-18-E7
2018-11-30 13:56:36.4214 CM19xTest.Program.Main Debug 20-60-9F-38-C7
2018-11-30 13:56:36.5334 CM19xTest.Program.Main Debug 20-60-9F-38-C7
2018-11-30 13:56:36.6374 CM19xTest.Program.Main Debug 20-60-9F-38-C7
2018-11-30 13:56:36.7494 CM19xTest.Program.Main Debug 20-60-9F-38-C7
2018-11-30 13:56:36.8534 CM19xTest.Program.Main Debug 20-60-9F-38-C7
2018-11-30 13:56:36.9575 CM19xTest.Program.Main Debug 20-60-9F-38-C7
2018-11-30 13:56:46.9626 CM19xTest.Program.Main Debug
2018-11-30 13:56:56.9676 CM19xTest.Program.Main Debug
2018-11-30 13:57:06.9726 CM19xTest.Program.Main Debug
2018-11-30 13:57:16.9777 CM19xTest.Program.Main Debug
2018-11-30 13:57:26.9828 CM19xTest.Program.Main Debug

this shows the start commands followed by a1 off then a2 on then off then a3 on&off then A4 on&off I had thought it seen security commands earlier but the door window modules I activated didn't register. the last 5 events are heart beats I assume

tuicemen commented 5 years ago

if there is a specific signal you'd like me to try just let me know and I'll attempt it.

genemars commented 5 years ago

Ok... I've updated the source code. So, create a new folder and download and compile the new code.

What you can do now is trying to generate the following RF:

Anyway I already see from your previous logs that everything is fine and I can probably use the same code I used to decode CM15 RF signals (both security and standard X10 modules) and translate those to a human readable form.

So now I can, almost certainly, say that my CM19E is broken =/ or perhaps this european version needs a different initialization sequence.

tuicemen commented 5 years ago

Ok same links?

tuicemen commented 5 years ago

Ok it appears to see all house codes on/off and the dim brighten commands but no security sensors or security remote signals. here are codes for p1 on followed by dim then brighten just after starting.

pi@X10Hub:~/CM19xTest-master/CM19xTest/bin/Debug $ sudo mono CM19xTest.exe
USB Transceiver
2018-11-30 14:50:07.0026 XTenLib.Drivers.CM19.WriteData Debug WriteData: 20-34-CB-58-A7
2018-11-30 14:50:07.7384 XTenLib.Drivers.CM19.WriteData Debug WriteData: 80-01-00-20-14
2018-11-30 14:50:08.2196 XTenLib.Drivers.CM19.WriteData Debug WriteData: 80-01-00-20-14-24-20-20
2018-11-30 14:50:08.2337 XTenLib.Drivers.CM19.WriteData Debug WriteData: 20-60-9F-00-FF
2018-11-30 14:50:08.2580 XTenLib.Drivers.CM19.ReadData Debug ReadData : FF
2018-11-30 14:50:08.3295 XTenLib.Drivers.CM19.ReadData Debug ReadData : FF
2018-11-30 14:50:30.5937 XTenLib.Drivers.CM19.ReadData Debug ReadData : 20-30-CF-00-FF
2018-11-30 14:50:30.7057 XTenLib.Drivers.CM19.ReadData Debug ReadData : 20-30-CF-00-FF
2018-11-30 14:50:30.8097 XTenLib.Drivers.CM19.ReadData Debug ReadData : 20-30-CF-00-FF
2018-11-30 14:50:30.9137 XTenLib.Drivers.CM19.ReadData Debug ReadData : 20-30-CF-00-FF
2018-11-30 14:50:31.0257 XTenLib.Drivers.CM19.ReadData Debug ReadData : 20-30-CF-00-FF
2018-11-30 14:50:31.1296 XTenLib.Drivers.CM19.ReadData Debug ReadData : 20-30-CF-00-FF
2018-11-30 14:50:36.3779 XTenLib.Drivers.CM19.ReadData Debug ReadData : 20-30-CF-98-67
2018-11-30 14:50:36.4900 XTenLib.Drivers.CM19.ReadData Debug ReadData : 20-30-CF-98-67
2018-11-30 14:50:36.5939 XTenLib.Drivers.CM19.ReadData Debug ReadData : 20-30-CF-98-67
2018-11-30 14:50:36.7059 XTenLib.Drivers.CM19.ReadData Debug ReadData : 20-30-CF-98-67
2018-11-30 14:50:36.8102 XTenLib.Drivers.CM19.ReadData Debug ReadData : 20-30-CF-98-67
2018-11-30 14:50:36.9139 XTenLib.Drivers.CM19.ReadData Debug ReadData : 20-30-CF-98-67
2018-11-30 14:50:40.0339 XTenLib.Drivers.CM19.ReadData Debug ReadData : 20-30-CF-88-77
2018-11-30 14:50:40.1380 XTenLib.Drivers.CM19.ReadData Debug ReadData : 20-30-CF-88-77
2018-11-30 14:50:40.2419 XTenLib.Drivers.CM19.ReadData Debug ReadData : 20-30-CF-88-77
2018-11-30 14:50:40.3539 XTenLib.Drivers.CM19.ReadData Debug ReadData : 20-30-CF-88-77
2018-11-30 14:50:40.4579 XTenLib.Drivers.CM19.ReadData Debug ReadData : 20-30-CF-88-77
2018-11-30 14:50:40.5700 XTenLib.Drivers.CM19.ReadData Debug ReadData : 20-30-CF-88-77
tuicemen commented 5 years ago

perhaps mralapete can confirm the cm19e is different once he returns from his business trip.

genemars commented 5 years ago

@tuicemen can you please update and compile the latest CM19xTest source code? I made a fix and I was able to receive X10 RF security codes (starting with 29) with my CM19E. Oddly I am still not able to receive standard x10 rf codes (starting with 20).

tuicemen commented 5 years ago

OK, it didn't turn on my A1 device at start up but I assume you removed that. the cm19 does see security door windows and motion sensors```

2018-12-03 06:38:21.9482 XTenLib.Drivers.CM19.ReadData Debug ReadData : 29-E5-EA -04-FB-4C-80 2018-12-03 06:38:22.0682 XTenLib.Drivers.CM19.ReadData Debug ReadData : 29-E5-EA -04-FB-4C-80 2018-12-03 06:38:25.5799 XTenLib.Drivers.CM19.ReadData Debug ReadData : 29-E5-EA -84-7B-4C-80 2018-12-03 06:38:25.7080 XTenLib.Drivers.CM19.ReadData Debug ReadData : 29-E5-EA -84-7B-4C-80 2018-12-03 06:38:25.8282 XTenLib.Drivers.CM19.ReadData Debug ReadData : 29-E5-EA -84-7B-4C-80 2018-12-03 06:38:25.9563 XTenLib.Drivers.CM19.ReadData Debug ReadData : 29-E5-EA -84-7B-4C-80 2018-12-03 06:38:26.0842 XTenLib.Drivers.CM19.ReadData Debug ReadData : 29-E5-EA -84-7B-4C-80 2018-12-03 06:38:51.3563 XTenLib.Drivers.CM19.ReadData Debug ReadData : 29-F1-FE-04-FB-FD-80 2018-12-03 06:38:51.4842 XTenLib.Drivers.CM19.ReadData Debug ReadData : 29-F1-FE-04-FB-FD-80 2018-12-03 06:38:51.6202 XTenLib.Drivers.CM19.ReadData Debug ReadData : 29-F1-FE-04-FB-FD-80 2018-12-03 06:38:51.7482 XTenLib.Drivers.CM19.ReadData Debug ReadData : 29-F1-FE-04-FB-FD-80 2018-12-03 06:38:51.8842 XTenLib.Drivers.CM19.ReadData Debug ReadData : 29-F1-FE-04-FB-FD-80 2018-12-03 06:38:52.0123 XTenLib.Drivers.CM19.ReadData Debug ReadData : 29-F1-FE-84-7B-FD-80 2018-12-03 06:38:52.1482 XTenLib.Drivers.CM19.ReadData Debug ReadData : 29-F1-FE-84-7B-FD-80 2018-12-03 06:38:52.2765 XTenLib.Drivers.CM19.ReadData Debug ReadData : 29-F1-FE-84-7B-FD-80 2018-12-03 06:38:52.4122 XTenLib.Drivers.CM19.ReadData Debug ReadData : 29-F1-FE-84-7B-FD-80 2018-12-03 06:38:52.5482 XTenLib.Drivers.CM19.ReadData Debug ReadData : 29-F1-FE-84-7B-FD-80 2018-12-03 06:38:53.2203 XTenLib.Drivers.CM19.ReadData Debug ReadData : 29-01-0E-8C-73-A2-80 2018-12-03 06:38:53.3002 XTenLib.Drivers.CM19.ReadData Debug ReadData : 29-01-0E-8C-73-A2-80 2018-12-03 06:38:53.3882 XTenLib.Drivers.CM19.ReadData Debug ReadData : 29-01-0E-8C-73-A2-80 2018-12-03 06:38:53.4763 XTenLib.Drivers.CM19.ReadData Debug ReadData : 29-01-0E-8C-73-A2-80 2018-12-03 06:38:53.5563 XTenLib.Drivers.CM19.ReadData Debug ReadData : 29-01-0E-8C-73-A2-80

genemars commented 5 years ago

@tuicemen awesome I almost finished writing the driver. I need a few more tests:

A1 ON, A DIM, A BRIGHT C7 ON, C DIM, C BRIGHT P2 OFF, P DIM, P BRIGHT

I also found codes for X10 Camera pan/tilt control and I will be adding support for those codes as well (starting with 14).

tuicemen commented 5 years ago

I'm away for a few days but will attempt do do something from here but it mat be the week end before I can test. Is there any chance RF sends can be added to the CM15? The camera pan n tilt codes I dont expect many use any more with wifi cameras now the norm but I can test those for you as well once you add them.

genemars commented 5 years ago

@tuiceman It's ok because I've finally managed to make my CM19 see standard rf codes (20). It turned out that the remote I was using works with CM15 but not with CM19. I am now using a different X10 remote that works with both (oddly enough both remotes should be sending 433Mhz signal). So I don't need any further info to proceed. I'll keep you guys posted with the progress of the CM19 driver.

tuicemen commented 5 years ago

Thats great news nice to see it isn't defective as you originaly thought

genemars commented 5 years ago

Early release of the new CM19Lib: https://github.com/genielabs/cm19-lib-dotnet there is also a Test.X10 program included.

mralapete commented 5 years ago

@genmars Just back in the loop and noticed further activity on this.

I built the driver as per your latest link https://github.com/genielabs/cm19-lib-dotnet but strangely cannot connect to my CM19. Similar messages to the ones I posted above.

I've done the following using a the Raspberry Pi Zero W with a copy of Raspbian Stretch Lite with Mono 5.4 and using the CM19 Euro version with no other hardware connected.

Installed the libusb git clone https://github.com/genielabs/cm19-lib-dotnet nuget restore (all ok) xbuild (all ok no errors) blacklisted the conflicting ati drivers rebooted Plugged in the CM19 and reporting as X10 wireless transceiver as it should changed to the /bin folder and ran sudo mono Test.X10.exe

Test.X10.exe reporting that it cannot connect to the CM19

As I mentioned earlier the CM19 is a Euro version, the same model as yours. Strange that @tuicemen manage to connect using a similar platform to me.

I also noticed that there are 11 hidden posts above which I cannot access in the body of this issue.Are they hidden for a reason.

S

tuicemen commented 5 years ago

In my tests if you had a cm15 connected you can't just unplug it and plug in the cm19 it will not find the cm19.if I rebooted it would see the cm19

genemars commented 5 years ago

@mralapete my CM19 is also the Euro version and it's working fine. You expand the hidden posts if you click on the hidden notice.

mralapete commented 5 years ago

@tuicemen the setup I'm using never had a CM15 attached. The CM19 when plugged in is correctly identified as the CM19 as per dmesg output.

@genemars mars yes I tried but GitHub is denying me access to those hidden pages.

There's nothing that could possibly be taking control of the CM19 when I plug it in so I have no idea what is causing the non connection of the CM19 when running your Test.X10.exe file

mralapete commented 5 years ago

@genemars I can now access the hidden posts so I can follow your progress on this issue since my last post.

It looks like you have created a functioning driver for the CM19

Could you include this driver in your next beta version of HG so I can fully test it at my end.

genemars commented 5 years ago

@mralapete, yes I'm already working on this. There will be a new HG release before Christmas 🎉

genemars commented 5 years ago

So I updated the CM19 driver repository and added two examples/test programs. I also updated the README.md file with instructions for using the examples programs and the driver itself.

https://github.com/genielabs/cm19-lib-dotnet

Have a look and let me know if there's anything else I should put in the README.md file in order to help users get started with this. Also, please, give me some feedback about the examples programs. Next I'll be integrating this driver in HomeGenie.

tuicemen commented 5 years ago

Did you add support for the pan N Tilt? if so you may wish to add a sample usage for them. I also see no mention of security codes is the driver capable of sending those? It will be a few more days before I can give this a test run, I can't wait to give it a test run .

rubenmg2008 commented 5 years ago

El El jue, 6 dic 2018 a las 19:06, Tuicemen notifications@github.com escribió:

Did you add support for the pan N Tilt? if so you may wish to add a sample usage for them. I also see no mention of security codes is the driver capable of sending those? It will be a few more days before I can give this a test run, I can't wait to give it a test run .

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/genielabs/HomeGenie/issues/343#issuecomment-444990451, or mute the thread https://github.com/notifications/unsubscribe-auth/ADq71VU5Dj_kgNDEluYuvGax20JH8uVIks5u2WqXgaJpZM4X9gKb .

-- Rubén Marrero

genemars commented 5 years ago

Did you add support for the pan N Tilt? if so you may wish to add a sample usage for them. I also see no mention of security codes is the driver capable of sending those? It will be a few more days before I can give this a test run, I can't wait to give it a test run .

I will add support for camera commands later. Anyway both camera and security messages can already be received or sent as raw messages using the method cm19.SendMessage(). I will add some examples to the README.md.

mralapete commented 5 years ago

@genemars thanks for that nice piece of work. Nice to see development like this back on track in HG.

I'll close this issue now that you have a working solution.

genemars commented 5 years ago

@tuicemen I added support for camera commands as well. See the new CM19Lib documentation.

genemars commented 5 years ago

The driver is now ready but the HomeGenie integration it is not yet there. I'm reopening this issue so I can reference and auto-close it as soon as the new HG release is published.

tuicemen commented 5 years ago

I was hoping to play with this but I'm having a hard time getting it to work on my raspi zeroW. I obviously am missing something. is there a simple installer or do I need to build? I've tried the build route but when I try either of the examples I get command not found

genemars commented 5 years ago

Just published a new HomeGenie beta with CM19 support. HomeGenie v1.2-beta.17 Enjoy!

tuicemen commented 5 years ago

woohoo! I'll be testing that out tomorrow!

tuicemen commented 5 years ago

:( well it doesn't work for me I just couldn't wait to test! main issue is now my cm15 doesn't work either

genemars commented 5 years ago

@tuicemen It works for me. Both CM19 and CM15. Both on a fresh install and upgrade. The only thing that is required for CM19 to work is to blacklist the kernel drivers as explained before. In the next HG release blacklisting will not be needed anymore.

genemars commented 5 years ago

@tuiceman this might be a problem related to where libusb is installed. Do the following:

$ ls -la /usr/local/bin/homegenie/lib/mig/libusb*
lrwxrwxrwx 1 root root 42 Oct 20 12:07 /usr/local/bin/homegenie/lib/mig/libusb-1.0.so -> /lib/arm-linux-gnueabi/libusb-1.0.so.0.1.0
$ ls -la /lib/arm-linux-gnueabihf/libusb-1.0.so.0.1.0
-rw-r--r-- 1 root root 79752 Jun 22  2014 /lib/arm-linux-gnueabihf/libusb-1.0.so.0.1.0

basically you have to check that the symbolic link to the libusb library is correct. In the example above, the link is wrong because the directory /lib/arm-linux-gnueabi does not exists in more recent versions of Pi. If the symbolic link point to a wrong path, try to fix the symbolic link and make it point to the right path location:

ln -s /lib/arm-linux-gnueabihf/libusb-1.0.so.0.1.0 /usr/local/bin/homegenie/lib/mig/libusb-1.0.so
genemars commented 5 years ago

@tuicemen I've fixed the MIG.HomeAutomation.dll library, so instead of the instructions in my previous messages, just replace the .dll file in the /usr/local/bin/homegenie/lib/mig folder. The new .dll will take care of creating the needed symbolic links for libusb and also removing the kernel drivers for CM19.

MIG.HomeAutomation.zip

tuicemen commented 5 years ago

@genemars ok this was on a fresh install of Raspbian lite with mono 5.4 and HG 1.2-satble then updated to the beta so files were not blacklisted. I'll replace the dll and do the black list thing and report back.

mralapete commented 5 years ago

@genemars just to confirm I downloaded and installed the beta version .17 and CM19 not working here. I dropped in that dll replacement fie as advised and the X10 icon is still greyed out on the screen. Maybe a little more info on what your current test rig is for this hardware/software wise might help.

tuicemen commented 5 years ago

Still not working for me here either just notice the X10 icon at top is greyed out here too. Also my HomeGenie folder is in /home/pi/ so the location of the dll is /home/pi/homegenie/lib/mig which may also be playing a roll in this not working.

mralapete commented 5 years ago

@tuicemen the location of your HG folder wouldn't be an issue. As long as your files have the correct permissions and ownerships that's all thats important. In the /mig part of the folder how did you insert Genes revised dll file. Does that revised file have the correct permissions and what group is it showing belonging to. Just type ls -l in the /mig folder and report the output

tuicemen commented 5 years ago

I downloaded the zip file to my PC opened it then stopped the HG service then using Filezila copied the file to the correct location never changed any permissions. Humm I just though of something. Windows blocks some aspects of downloaded files and can prevent them from working correctly if not unblocked before unzipping and I didn't do that so I'll retry things. and get back with results.

genemars commented 5 years ago

is there any version of homegenie that works for you? start with that and I will tell you what files to copy from the latest .tgz . This way we can spot from what dll is the issue coming from.

Il giorno lun 10 dic 2018, 15:25 mralapete notifications@github.com ha scritto:

@tuicemen https://github.com/tuicemen the location of your HG folder wouldn't be an issue. As long as your files have the correct permissions and ownerships that's all thats important. In the /mig part of the folder how did you insert Genes revised dll file. Does that revised file have the correct permissions and what group is it showing belonging to. Just type ls -l in the /mig folder and report the output

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/genielabs/HomeGenie/issues/343#issuecomment-445832807, or mute the thread https://github.com/notifications/unsubscribe-auth/AGWJOcxe3_4Omz0DHQ5yMS-MZRLd7PGpks5u3m7AgaJpZM4X9gKb .

genemars commented 5 years ago

@tuicemen @mralapete I am succesfully running latest HG both on Raspbian and Ubuntu.

RASPBERRY PI

$ uname -a
Linux raspberrypi 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux
$ mono --version
Mono JIT compiler version 3.2.8 (Debian 3.2.8+dfsg-10)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
    TLS:           __thread
    SIGSEGV:       normal
    Notifications: epoll
    Architecture:  armel,vfp+hard
    Disabled:      none
    Misc:          softdebug 
    LLVM:          supported, not enabled.
    GC:            sgen

UBUNTU 18

$ uname -a
Linux mobi-dev 4.15.0-42-generic #45-Ubuntu SMP Thu Nov 15 19:32:57 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

$ mono --version
Mono JIT compiler version 4.6.2 (Debian 4.6.2.7+dfsg-1ubuntu1)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
    TLS:           __thread
    SIGSEGV:       altstack
    Notifications: epoll
    Architecture:  amd64
    Disabled:      none
    Misc:          softdebug 
    LLVM:          supported, not enabled.
    GC:            sgen

@tuicemen why are you using mono 5.x and why not installing using gdebi and the .deb package? @mralapete are you also trying a "custom" installation as @tuicemen ?

tuicemen commented 5 years ago

ok retried with out success both cm15 and 19 don't work . here is the out put from ls-l

pi@X10Hub:~/homegenie/lib/mig $ ls -l
total 3240
-rw-r--r-- 1 root root   22528 Dec  9 20:12 CM19Lib.dll
lrwxrwxrwx 1 root root      44 Dec 10 09:55 libusb-1.0.so -> /lib/arm-linux-gnueabihf/libusb-1.0.so.0.1.0
-rw-r--r-- 1 root root    6144 Dec  9 20:12 LibUsb.Common.dll
-rw-r--r-- 1 pi   pi    150016 Sep 22 10:59 LibUsbDotNet.dll
-rw-r--r-- 1 root root  158208 Dec  9 20:12 LibUsbDotNet.LibUsbDotNet.dll
-rw-r--r-- 1 root root     163 Dec  3 16:11 lircconfig.xml
-rw-r--r-- 1 root root  295322 Dec  3 16:11 lircremotes.xml
-rwxr-xr-x 1 pi   pi     13312 Sep 22 10:59 MIG.Controllers.dll
-rw-r--r-- 1 pi   pi     49664 Dec 10 09:54 MIG.HomeAutomation.dll
-rwxr-xr-x 1 pi   pi      9728 Sep 22 10:59 MIG.Media.dll
-rw-r--r-- 1 root root   31232 Dec  9 20:13 MIG.Protocols.dll
-rw-r--r-- 1 root root 2406991 Dec  3 16:11 p1db_custom.xml
drwxr-xr-x 2 pi   pi      4096 Nov 25 18:49 v4l
-rw-r--r-- 1 root root   34816 Dec  9 20:13 XTenLib.dll
-rw-r--r-- 1 root root  103936 Dec  9 20:13 ZWaveLib.dll
pi@X10Hub:~/homegenie/lib/mig $

@genemars I was using v1.1-stable.527 and updated to beta 17

genemars commented 5 years ago

@tuicemen I updated from beta 16 to beta 17.

pi@raspberrypi:~ $ ls -la /usr/local/bin/homegenie/lib/mig
total 3092
drwxr-xr-x 2 pi   pi      4096 Dec 10 10:01 .
drwxrwxr-x 5 pi   pi      4096 Oct 20 11:27 ..
-rw-r--r-- 1 root root   22528 Dec 10 02:44 CM19Lib.dll
lrwxrwxrwx 1 pi   pi        44 Dec 10 10:01 libusb-1.0.so -> /lib/arm-linux-gnueabihf/libusb-1.0.so.0.1.0
-rw-r--r-- 1 root root    6144 Dec 10 02:45 LibUsb.Common.dll
-rw-r--r-- 1 root root  158208 Dec 10 02:45 LibUsbDotNet.LibUsbDotNet.dll
-rw-r--r-- 1 root root     163 Oct 20 12:23 lircconfig.xml
-rw-r--r-- 1 root root  295322 Oct 20 12:23 lircremotes.xml
-rw-r--r-- 1 root root   49152 Dec 10 02:45 MIG.HomeAutomation.dll
-rw-r--r-- 1 root root   31232 Dec 10 02:45 MIG.Protocols.dll
-rw-r--r-- 1 root root 2406991 Oct 20 12:23 p1db_custom.xml
-rw-r--r-- 1 root root   34816 Dec 10 02:45 XTenLib.dll
-rw-r--r-- 1 root root  103936 Dec 10 02:45 ZWaveLib.dll
-rw-r--r-- 1 root root   28234 Dec 10 02:47 zwavenodes.xml

Can you output also the root homegenie folder files? Maybe there are old files that should be deleted. Especially if those files are .dll files that are also present in the lib/mig folder.

tuicemen commented 5 years ago

@genemars I'll try a new image and use the gdebi and the .deb package. the reason for the Mono version of 5.x is that's what provided the least problems with other addon programs. like email pictures if I remember correctly. mralapete and I are creating a HG disk image for X10 users and included that mono version to avoid conflicts we both had. mralapete may have more info on the reason why.

genemars commented 5 years ago

I see you have some extra files in the lib/mig folder :

-rw-r--r-- 1 pi   pi    150016 Sep 22 10:59 LibUsbDotNet.dll

pheraps this file has to be deleted?