Port Problem / Altsteon UI5

Other Devices & Integrations More Home Control
1

Hello,

Ok first off very new at programing here on vera3 but some experience [a little compared to you all]…

I have a Vera3 UI6, which due to door lock problem, rolled back to a UI5.
I am using windows and up loaded all the files to the Luup files through the window on the dashboard. All are there and the newest copies from “member fba website”

Then I reset the PLM and have two insteon modules. A sprinkler and garage door controllers, note the garage door opener worked perfect until the port was closed and the new altsteon took over. I turned off the insteon native.

ok so I got all the files in
I set up the PLM code and got a box for it on the dashboard [rechecked the codes pretty sure they are right]
I set up the EzFlora and the Garage Hawk, codes seem to be right and they appeared on the dash panel.
I saved everything as I went along and then went to run it.

I keep getting two errors…

First error on panels was “device not ready” but that’s gone now, since I tweaked the USB as shown in picture, when I click on a button.

Now I have “Ok : Failed to open IO Port”

I have tried everything to get this to connect or wake up, or at least I think I have? I am so close and after hours of playing trail and error I have gotten this far… So now I reach out to hopeful solve the problem. Before I get the hammer and start beating the screen…LOL

Also GREAT job member “fba” your work is great there…

I through in some screen shots and can send more…

Here are the codes I used and put in…

PLM
Device type : urn:geektaco-info:device:plm:1
Internal ID : plm
Description : plm
Upnp Device Filename : D_InsteonPlm.xml
Upnp Implementation Filename : I_InsteonPlm.xml
Ip Address : XXX.XXX.X.XXX
MAC :
Room : <doesn’t matter>
Parent device : No parent/Please select

SPRINKLERS
Device type : urn:schemas-geektaco-info:device:EzFlora:1
Internal ID : XX.XX.XX
Description : Sprinkler
Upnp Device Filename : D_InsteonEzFlora.xml
Upnp Implementation Filename : I_InsteonEzFlora.xml
Ip Address :
MAC :
Room : <don’t care>
Parent device : plm

GARAGE HAWK
Device type : urn:geektaco-info:device:GarageHawkGarage:1
Internal ID : XX.XX.XX
Description : Garge Hawk
Upnp Device Filename : D_InsteonGarageHawkGarage.xml
Upnp Implementation Filename : I_InsteonGarageHawkGarage.xml
Ip Address :
MAC :
Room : <don’t care>
Parent device : plm

And thanks to everyone and all the HELP!
Smiles
Ron

2

I have no idea if this is causing your problem, but my altsteon setup looks slightly different (note the port number).

3

Not sure why my pic I took said 3482 it says and looks like yours now 3481… go figure right? but thanks I did go check.

4

Altsteon via the GUI doesn’t use the serial port. The Altsteon daemon, which you upload directly to Vera via scp, uses the USB port.

You should run the daemon directly for testing. Do this by SSHing into Vera, changing to the directory where Altsteon is installed, and running:./altsteon -p /dev/ttyUSB0 -dd -fYou might need to use “/dev/ttyUSB1” instead. The -dd is debug, and the -f is “run in foreground”

There is more information in the “altsteon_instructions.txt” file contained in the delivery.

5

[quote=“PurdueGuy, post:4, topic:180144”]Altsteon via the GUI doesn’t use the serial port. The Altsteon daemon, which you upload directly to Vera via scp, uses the USB port.

You should run the daemon directly for testing. Do this by SSHing into Vera, changing to the directory where Altsteon is installed, and running:./altsteon -p /dev/ttyUSB0 -dd -fYou might need to use “/dev/ttyUSB1” instead. The -dd is debug, and the -f is “run in foreground”

There is more information in the “altsteon_instructions.txt” file contained in the delivery.[/quote]

Hello there and thanks for looking at this I have spent hours and seemed to made some headway but not there.

I did as you asked and below is a pic of the return on it. I took more pic’s to show you what all I did…

I uploaded the files both through the UI and through ssl.
I changed the chrom on altsteon & altsteon_cli to 755
I tried to follow the steps but finally got it to point to ttyUSB1 from ttyUSB0 where it seems to like to keep going.
I changed to the garage control because I knew that worked before the Altsteon. I programmed both the plm and the garage control as instructed and made sure the plm was seeing the controller. but it keeps saying “Ok : Failed to open IO Port” & “Opening serialConnection…” The serial connection has never opened up on the panel page.
I have rebooted but then it looses the usb1 and goes back to usb0.

I really appreciate your help on this as I only need to get these two things running. I am at that point, you know where u want to take a hammer to everything…LOL

Let me know what I should try next or if you see whats wrong.

Thanks again
Smiles
Ron

6

You shouldn’t be using the “Serial Port Configuration” at all.
I think Vera and Altsteon are fighting over the serial port (USB) and causing conflicts.

I do not have a PLM plugged in at the moment, so my serial port page is empty.
I can test later and plug in a USB PLM and see how it looks.

The ONLY reference anywhere to use should be in the startup LUA.

You also have an error in yours (which may or may not matter).
It should be:[code]local plm = “/dev/ttyUSB1”

os.execute(“/overlay/sbin/altsteon -p " … plm)”[/code](or ttyUSB0 as appropriate for others reading this).

7

[quote=“PurdueGuy, post:6, topic:180144”]You shouldn’t be using the “Serial Port Configuration” at all.
I think Vera and Altsteon are fighting over the serial port (USB) and causing conflicts.

I do not have a PLM plugged in at the moment, so my serial port page is empty.
I can test later and plug in a USB PLM and see how it looks.

The ONLY reference anywhere to use should be in the startup LUA.

You also have an error in yours (which may or may not matter).
It should be:[code]local plm = “/dev/ttyUSB1”

os.execute(“/overlay/sbin/altsteon -p " … plm)”[/code](or ttyUSB0 as appropriate for others reading this).[/quote]

ok made the changes and now from the picture at the top of it a new error appears…

I will wait on your test there and let me know what to do next… thanks again

8

I attached a capture of what mine looks like.
I would suggest you set “Used by device” back to the default of “- Please select -” and save/reload LUUP.

9

[quote=“PurdueGuy, post:8, topic:180144”]I attached a capture of what mine looks like.
I would suggest you set “Used by device” back to the default of “- Please select -” and save/reload LUUP.[/quote]

Ok think I got it… it fought me a bit but I unplugged it and pressed the button on the plm and re-plugged it in and it let me change the settings then. But yet another thing comes up see photo…

If it matters I have a vera3 that was a UI6 rolled back per the tech’s department to UI5. I also have two usb’s slots on the back and I have it in the second which appears to be #1 I have tried to move them from one to another when I fought it to see tttyusb1… just some back ground if that helps.

Thanks
Ron

10

I would reboot Vera (power cycle) and make sure the altsteon daemon is running.
If you SSH into vera, run ps -ef | grep altto check (and post the results back here). Also, verify if “ttyUSB0” or “ttyUSB1” is correct per the instructions.

Also, what does your PLM device settings look like? Do a capture of each tab for the PLM device.

11

[quote=“PurdueGuy, post:10, topic:180144”]I would reboot Vera (power cycle) and make sure the altsteon daemon is running.
If you SSH into vera, run ps -ef | grep altto check (and post the results back here). Also, verify if “ttyUSB0” or “ttyUSB1” is correct per the instructions.

Also, what does your PLM device settings look like? Do a capture of each tab for the PLM device.[/quote]

Ok sorry took so long had to go to work…

Ok did as you asked and got the following, Also because I restarted it went back to ttyUSB0 and the plm is plugged into the ttyUSB1, usually when I unplug the plm and holding the button down when I hook it back it makes it go to ttyUSB1 but I tried 3 times and it stays in ttyUSB0.

I ran that code see below 3 times 5 min’s apart for yea…

I took pic’s of all the panels for you as well as here are the codes I used in the plm and the garage door.

PLM
Device type : urn:geektaco-info:device:plm:1
Internal ID : plm
Description : plm
Upnp Device Filename : D_InsteonPlm.xml
Upnp Implementation Filename : I_InsteonPlm.xml
Ip Address : 192.168.1.147
MAC :
Room : <doesn’t matter>
Parent device : No parent/Please select

GARAGE HAWK
Device type : urn:geektaco-info:device:GarageHawkGarage:1
Internal ID : 28.ca.03
Description : Garage Hawk
Upnp Device Filename : D_InsteonGarageHawkGarage.xml
Upnp Implementation Filename : I_InsteonGarageHawkGarage.xml
Ip Address :
MAC :
Room : <don’t care>
Parent device : plm

I am lost and not sure what to try next so pretty open to anything you want to try here…

Thanks again
Ron

12

That’s true, but I’m using altsteon with the serial port settings as shown in my earlier screenshot, and altsteon is still working fine for me.

You should run the daemon directly for testing. Do this by SSHing into Vera, changing to the directory where Altsteon is installed, and running:[code]./altsteon -p /dev/ttyUSB0 -dd -f[/code]You might need to use "/dev/ttyUSB1" instead. The -dd is debug, and the -f is "run in foreground"

There is more information in the “altsteon_instructions.txt” file contained in the delivery.

If he does that, he first needs to kill any existing daemon, or it’s not going to work.

13

That’s true, but I’m using altsteon with the serial port settings as shown in my earlier screenshot, and altsteon is still working fine for me.

You should run the daemon directly for testing. Do this by SSHing into Vera, changing to the directory where Altsteon is installed, and running:[code]./altsteon -p /dev/ttyUSB0 -dd -f[/code]You might need to use "/dev/ttyUSB1" instead. The -dd is debug, and the -f is "run in foreground"

There is more information in the “altsteon_instructions.txt” file contained in the delivery.

If he does that, he first needs to kill any existing daemon, or it’s not going to work.[/quote]

Hello and thanks for chimming in… I ran that code of yours before and again just now it just keeps coming back the same…

/overlay$ ./altsteon -p /dev/ttyUSB0 -dd -f
-ash: ./altsteon: not found
/overlay$ /altsteon -p /dev/ttyUSB0 -dd -f
-ash: /altsteon: not found
/overlay$ /altsteon -p /dev/ttyUSB1 -dd -f
-ash: /altsteon: not found
/overlay$ ./altsteon -p /dev/ttyUSB1 -dd -f
-ash: ./altsteon: not found

As for running two daemons I’m not sure if I got one running now? as well as what’s your thought on why I have the plm in ttyusb1 of two plugs and it keeps saying and reverting to ttyusb0? I am open to try anything you guys may suggest!

Thanks for your help

14

Based on the “ps -ef | grep alt” you do not have altsteon running. That’s a problem.
You need to change to the directory you installed altsteon in, or run it with the full path.
Log in, and run “/overlay/sbin/altsteon -p /dev/ttUSB0”

As far as USB0 vs USB1, pressing the button on the PLM will have no effect. Vera decides when the PLM is plugged in what ID to assign it. The best way to find out what it will be is plug in all USB devices, reboot, and then check. Then Vera will enumerate them in order. If you plug them in and unplug, they could be different each time.

Also, on the PLM settings, use “127.0.0.1” and not the actual IP address of Vera. A security update made the default listen on 127.0.0.1 only.

15

The quick way to figure out which port is being used is:

[tt]dmesg | grep ttyUSB[/tt]

If you’re lucky, only one line will be printed out, such as:

[tt]usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0[/tt]

This tells me that my USB plm is connected to [tt]/dev/ttyUSB0[/tt].

If you’re unlucky, there will be multiple lines, with different USB devices listed. Chances are, the last one will (hopefully) be the correct one to use.

16

Ok, I ran both codes and the read outs are below neither seemed to change anything. so as a run through here’s what I did. I originally uploaded the files through and on the vera3 UI5, what I re did to make sure they were there was re upload the files to root/overlay/sbin they also copied themselves to the root/sbin…

I chrom’ed the files altsteon & altsteon_cli to 755

I factory reset the PLM and reconnected it and made sure the garage hawk was included/added to it.

I then restarted the vera3 [unplugged it waited a few and plug it back in.

I made new PLM & Garagehawk panels.

I found a few code mistakes and I got to to get all the way to the door but it is not connected to the usb. Here’s copy’s of all the codes I ran after all the above…

And copies of what I set the panels to and a few pic’s… Did I miss anything? I think I have read that instruction sheet so many times I think I wrote it… LOL

let me know what we should try next… and thanks there for all your help!

copies of codes and results… They were ran in the order they are on the listing…

Code ran and results = dmesg [note only copied last half of print out]
usbcore: registered new interface driver rt2800usb
loop: module loaded
PPP generic driver version 2.4.2
ip_tables: (C) 2000-2006 Netfilter Core Team
NET: Registered protocol family 24
ehci_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver
rt3883-ehci rt3883-ehci: Ralink RT3883 built-in EHCI controller
rt3883-ehci rt3883-ehci: new USB bus registered, assigned bus number 1
rt3883-ehci rt3883-ehci: irq 26, io mem 0x101c0000
rt3883-ehci rt3883-ehci: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
nf_conntrack version 0.5.0 (1991 buckets, 7964 max)
xt_time: kernel timezone is -0000
ohci_hcd: USB 1.1 ‘Open’ Host Controller (OHCI) Driver
rt3883-ohci rt3883-ohci: Ralink RT3883 built-in OHCI controller
rt3883-ohci rt3883-ohci: new USB bus registered, assigned bus number 2
rt3883-ohci rt3883-ohci: irq 26, io mem 0x101c1000
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
usbcore: registered new interface driver usbserial
USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial Driver core
Initializing USB Mass Storage driver…
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb 2-1: new full speed USB device using rt3883-ohci and address 2
USB Serial support registered for Belkin / Peracom / GoHubs USB Serial Adapter
usbcore: registered new interface driver belkin
belkin_sa: v1.3:USB Belkin Serial converter driver
USB Serial support registered for cp210x
usbcore: registered new interface driver cp210x
cp210x: v0.09:Silicon Labs CP210x RS232 serial adaptor driver
USB Serial support registered for FTDI USB Serial Device
usbcore: registered new interface driver ftdi_sio
ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver
USB Serial support registered for Keyspan - (without firmware)
USB Serial support registered for Keyspan 1 port adapter
USB Serial support registered for Keyspan 2 port adapter
USB Serial support registered for Keyspan 4 port adapter
usbcore: registered new interface driver keyspan
keyspan: v1.1.5:Keyspan USB to Serial Converter Driver
USB Serial support registered for MCT U232
usbcore: registered new interface driver mct_u232
mct_u232: z2.1:Magic Control Technology USB-RS232 converter driver
USB Serial support registered for GSM modem (1-port)
usbcore: registered new interface driver option
option: v0.7.2:USB Driver for GSM modems
USB Serial support registered for pl2303
usbcore: registered new interface driver pl2303
pl2303: Prolific PL2303 USB to serial adaptor driver
ftdi_sio 2-1:1.0: FTDI USB Serial Device converter detected
usb 2-1: Detected FT232RL
usb 2-1: Number of endpoints 2
usb 2-1: Endpoint 1 MaxPacketSize 64
usb 2-1: Endpoint 2 MaxPacketSize 64
usb 2-1: Setting MaxPacketSize 64
usbcore: registered new interface driver cdc_acm
cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
br-lan: port 2(wlan0) entering forwarding state
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
br-lan: port 2(wlan0) entering forwarding state
br-lan: port 2(wlan0) entering forwarding state
br-lan: port 1(eth0.1) entering forwarding state
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering disabled state
device eth0.1 left promiscuous mode
br-lan: port 1(eth0.1) entering disabled state
device eth0 left promiscuous mode
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
device eth0 entered promiscuous mode
device eth0.1 entered promiscuous mode
br-lan: port 1(eth0.1) entering forwarding state
br-lan: port 1(eth0.1) entering forwarding state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
br-lan: port 2(wlan0) entering forwarding state
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
br-lan: port 1(eth0.1) entering forwarding state
br-lan: port 1(eth0.1) entering forwarding state
br-lan: port 1(eth0.1) entering forwarding state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
br-lan: port 2(wlan0) entering forwarding state
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
br-lan: port 2(wlan0) entering forwarding state
ramips-wdt: timeout value 60 must be 0 < timeout < 25

CODE RAN = dmesg | grep “FTDI”
/sbin$ dmesg | grep “FTDI”
USB Serial support registered for FTDI USB Serial Device
ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver
ftdi_sio 2-1:1.0: FTDI USB Serial Device converter detected
usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0

CODE RAN = ps -ef | grep alt
/sbin$ ps -ef | grep alt
4875 root 568 S /overlay/sbin/altsteon -p /dev/ttyUSB0
23653 root 1672 S grep alt

CODE RAN = ./altsteon -p /dev/ttyUSB0 -dd -f/sbin$ ./altsteon -p /dev/ttyUSB0 -dd -f
Debug Level : 2
[INFO ] [3/15/2014 - 23:15:50] - --| Starting altsteon!
[DEBUG] [3/15/2014 - 23:15:50] - Opening /dev/ttyUSB0…
[INFO ] [3/15/2014 - 23:15:50] - Running on non-apple Hardware
[DEBUG] [3/15/2014 - 23:15:51] - Sending : 0260
[ERROR] [3/15/2014 - 23:16:01] - PLM didn’t respond!
[INFO ] [3/15/2014 - 23:16:01] - Modem info :
[INFO ] [3/15/2014 - 23:16:01] - cflag = 00000CBE
[INFO ] [3/15/2014 - 23:16:01] - oflag = 00000000
[INFO ] [3/15/2014 - 23:16:01] - iflag = 00000804
[INFO ] [3/15/2014 - 23:16:01] - lflag = 00000000
[ERROR] [3/15/2014 - 23:16:01] - Failed to initialize PLM.

CODE RAN = dmesg | grep ttyUSB
/sbin$ dmesg | grep ttyUSB
usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0

Pic’s taken below right after all the codes were Ran!

Does that IP “127.0.0.1” need to be in place of the one on the usb panel? pic below?

Thanks and look forward to the next step…

17

I’m confused by the post. What’s not working, and how do you know that?

Just as an aside: after the vera/plm has been connected and “working” for a few minutes (the altsteon daemon has been running), run the following command, from a terminal window (do not put it into the startup lua dialog or any other dialog box):

[tt]/overlay/sbin/altsteon_cli[/tt]

Then type “[tt]list[/tt]” (without the quotes) and press [Enter]. That will display the currently “known” altsteon devices. Showing us the list might help. However, note that, after a reboot/reload, it can take a minute or two or more for that list to become fully populated (which is why I suggest waiting for a few minutes before doing it).

To exit that program, just press Ctrl-C.

18

[quote=“JustSomeGuy, post:17, topic:180144”]I’m confused by the post. What’s not working, and how do you know that?

Just as an aside: after the vera/plm has been connected and “working” for a few minutes (the altsteon daemon has been running), run the following command, from a terminal window (do not put it into the startup lua dialog or any other dialog box):

[tt]/overlay/sbin/altsteon_cli[/tt]

Then type “[tt]list[/tt]” (without the quotes) and press [Enter]. That will display the currently “known” altsteon devices. Showing us the list might help. However, note that, after a reboot/reload, it can take a minute or two or more for that list to become fully populated (which is why I suggest waiting for a few minutes before doing it).

To exit that program, just press Ctrl-C.[/quote]

Ok did exactly as you asked and here is a copy…

Cmd : /overlay/sbin/altsteon_cli
end:004E,02:FFFE,02 - Unknown device ‘end:004E,02’.

Cmd : list
28.ca.03:0046,02,07,00,00,28,CA,03 - 28.ca.03 (DevCat : 7 SubCat : 0 Hidden : 0 Addr : 28.CA.03)
plm:0046,02,03,15,1,23,99,84 - plm (DevCat : 3 SubCat : 21 Hidden : 1 Addr : 23.99.84)
end:004E,02 - End of list.

I think I see the plm and then the garagehawk there…
going to give it a few minutes and see if they work and if not will try rebooting and then wait and see if they work… let you know what I find out unless you read something different there?
Thanks for your help on this…

19

Well, assuming that the garagehawk is at 28.ca.03, then it does appear to be seen.

You are following the altsteon instructions to add the garagehawk devices, right? (It’s hard to tell, but the altsteon instructions seem to be unclear about what kind of functionality is supported with the garagehawk.)

20

[quote=“JustSomeGuy, post:19, topic:180144”]Well, assuming that the garagehawk is at 28.ca.03, then it does appear to be seen.

You are following the altsteon instructions to add the garagehawk devices, right? (It’s hard to tell, but the altsteon instructions seem to be unclear about what kind of functionality is supported with the garagehawk.)[/quote]

Yes I did I think it is right past post showed the connection but now waited about 30min after a reboot and it still won’t show a connection on the plm panel to usb serial port, it just shows the loading bar and no buttons on either the hawk or plm panels?

whats the difference with hawk and hawkremote?