There is no hub of any kind on this machine. this is the only ftdi entry I see
Bus 001 Device 006: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
If I need to I will try to obtain a replacement CM15 online. to replace the old one.
lsusb is reporting seven different devices attached to Bus 1. What exactly have you been attaching to the USB ports on the RPI.
What I suggest you do before you start spending more money on hardware is do a fresh install of Raspberry Pi OS and HG without the the CM11 plugged into the USB port. Once you have that and HG is running report back here and I’ll step you through connecting up the CM11.
Your CM11 has grabbed a serial port and while that can be addressed it would take a bit of time and energy.
Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 005: ID 1d57:f134 Xenta 2.4G Dongle
Bus 001 Device 007: ID 0424:7800 Microchip Technology, Inc. (formerly SMSC)
Bus 001 Device 003: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 002: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Format micro SD as NTFS
Re-image Rpi with Raspberry Pi Imager v1.7.3 on new 16 gb Gigastone micro SD. (My SSD was a casualty of my recent crash)
SSH was setup during Raspberry Pi imaging so first boot was done without any usb connections.
Boot success
Wireless would not setup. Reboot modem Still no wireless on Pi
performed update - upgrade - reboot
lsusb shows
Bus 001 Device 004: ID 0424:7800 Microchip Technology, Inc. (formerly SMSC)
Bus 001 Device 003: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 002: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
After HG install lsusb shows
Bus 001 Device 004: ID 0424:7800 Microchip Technology, Inc. (formerly SMSC)
Bus 001 Device 003: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 002: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
With no USBs plugged in. Only cables plugged in are network,HDMI and power.
HG up and running, data restored.
X10 interface set to select port.
lsusb shows
Bus 001 Device 004: ID 0424:7800 Microchip Technology, Inc. (formerly SMSC)
Bus 001 Device 003: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 002: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
If further information is needed, please let me know.
Nothing is plugged into usb ports.
Thank you for your assistance.
Ok. Ensure that X10 is disabled in HG. Now make sure the rs232 to usb cable is securely connected to the serial connector on the CM11. Plug the USB end into the USB port on the RPI.
Go the HG X10 settings Port to the drop down section. You should see CM15, CM19,CM11. Could you confirm that.
yes.
CM11 - /dev/tty/ama0
Select that option and you should see the X symbol at the top right hand of the screen light up. Could you confirm that.
Obviously you’ll have X10 Enabled at this stage while you select the CM11 option. Is the CM11 working now.
All modules now say “module undefined. module unavailable” and the “X” symbol is grayed out.
Disabling X10 does not bring back the modules
It won’t either. What you need to do is avoid doing a restore of your HG before you have set up X10 on your new system. The problem is you are restoring from a backup of HG that was configured for a CM15 onto a new setup that is now using a CM11. The wrong driver is being restored every time.
What you need to do is establish that your CM11 is actually working. A vanilla install of Raspberry Pi OS and HG is required to remove any old settings that are being carried over from your restore.
I suggest you do this and instead of immediately restoring the HG backup, enable and configure X10 in your new install for the CM11 first and create a single X10 module you can use as a test.
Once you’ve established that the CM11 is working or not we can proceed from there. Remember DO NOT restore your HG backup until all of this is confirmed first.
Does your CM11 work in Windows.
What I can confirm is my CM11 works with HG on an RPI. I’m using a serial to usb cable with the Prolific chipset like this one 1 Port USB to RS232 DB9 Serial Adapter - Serial Cards & Adapters | Ireland
I have 2 CM11s. Each one will work with Windows 10 restored from a Pi install. I will attempt to do a fresh install, but that will need to be tomorrow. I am still recovering from a nasty shot of Covid 19 and need to take frequent breaks. Thank you once again for all your help. Catch you tomorrow.
Dave
Well that’s something. CM11s both confirmed working so I know I’m not wasting time. I assume you confirmed in Windows that your CM15 was dead.
I have a feeling you have some corruption in that HG backup you are restoring but I still need to confirm that the CM11/FTDI serial to usb cable combination will work on the RPI in HG.
As i said all I can definitely confirm is the CM11/Prolific serial to usb cable combination will work on the RPI in HG using the Prolific chipset.
As soon as you have the vanilla install completed whenever post back here and I’ll pick it up at some stage.
I am starting to again believe in RPi with HomeGenie. After a relapse of Covid that was not at all pleasant I returned to my Pi and HG. I borrowed back a Pi I had purchased and set up for a friend and a CM15 from another friend that was no longer being used. The RPi Buckeye set up on the first shot and the CM15 the same. Right now everything works for the first time this summer. So now my old Pi seems to be working as is my Windows install. I believe my first failure was possibly the old CM15 which in turn damaged my Pi. My USB to RS232 adapter apparantly was blown out and could not connect the CM11 to the pi. So right now this comedy of errors I have been in seems to be resolved. I will report back when i can tell this will continue to work.
Thank you very much for the guidance you have given me in this matter.
Dave
Sorry, that would be Bullseye, not Buckeye. Apparently, the Covid brain is still around.
Now that you are back in business take that solid piece of advice…backup. Backup by way of taking an image of your SD card. Keep that image file safe and also burn that image to a second SD card and put that card close by so if your system does indeed fail you can immediately swap cards in your system. Think of it as a replacement fuse.
Just to confirm, as a test I did a fresh install of Raspbian and HG and hooked up a CM11. Everything worked perfectly.
I can now confirm most of my system is now working as it was before my recent difficulties. I am now convinced I had either a power surge or lightning strike nearby as I have run into odd functions and mis-communications with my pi and X10 modules. My x10 transceivers have all started to behave either not at all or with odd performance. Anything controlled with pi or android works fine. Older controllers erratic. Motion sensors are working to the transceivers but will not relay commands to HG. My next step will be to replace the thansceivers with new and try that. Yes it has been an interesting summer, but things are starting to come back together. Can hardly wait to see what will happen next.
What happened next. I walked into the garage this morning and had the lights pop on. First time in weeks. This happened several times as I went in and out of my shop, and then stopped working again. I will try a new transceiver as soon as I can get one and see if this can be resurrected yet again. Hope so. My wife is starting to call me nice names again instead of how she has been referring to me in the past month.