I finally took the plunge with George for MCV’s help ;D. Thanks George and thanks fba for all your hard work in developing the Altsteon.
The daemon appears to be working beautifully as I can go to altsteon_cli and turn on and off devices, poll them, and the like.
The issue appears to be with the UI communicating to altseon. I have tried several devices with always the same result, the error message “Device not ready” when I click on an event. I attached output from the CLI.
I am only working with one device right now to keep it simple. I tried both the relay and a dimmer. The attached log is for a dimmer. The UI appears to identify the device as a dimmer correctly.
When creating the device I use the following:
Device type : urn:geektaco-info:device:Relay:1
Internal ID : 1B.29.5D
Description : FamilyRoom
Upnp Device Filename : D_InsteonRelay.xml
Upnp Implementation Filename : I_InsteonRelay.xml
Ip Address : <blank>
MAC : <blank>
Room : <don't care>
Parent device : plm
I used copy and paste from the altsteon_instruction.txt to prevent silly mispelling errors and tried this numerous time without avail.
I also turned off native Insteon support.
Checked that the id_parent field which is 33 matches the id of the PLM module.
??? I am at a loss. I think I am missing something simple.
SHould not matter since he already stated that the daemon is running and working fine with the altsteon_cli. Did you load all of the altsteon files onto Vera or only certain ones?
In case this is useful, I added a screenshot of the error message.
From you screenshot you can see that the PLM module is shows as is the module I added to control the relay light. When I click on either on or off, I get the “Device Not Ready” error message. I tried rebooting the both the PLM and Vera to no avail.
There are two reasons you might get the “Device not ready” error. One is that the PLM isn’t configured correctly, the other is that there is a bug in the LUA code for the device. I have numerous dimmers around my house all working perfectly, so my first guess is that the PLM isn’t set up quite right.
If you can send commands via the CLI, then you have that portion all set correctly. You will want to double check the settings for your PLM. The settings can be a little confusing because the native Insteon implementation refers to a serial port when talking to the PLM. Altsteon uses a network socket for communication with the UI. So, you will want to make sure you are configured for an IP address instead of a serial port. (The serial port communication happens with the daemon, the UI then talks to the daemon over a network connection, which on the Vera is usually the loopback interface.)
I have attached three screen shots of my PLM. Make sure the IP address in all three of those screens is 127.0.0.1 (if you are running the daemon directly on the Vera) or the IP address of the remote box if you are running the daemon elsewhere.
Greetings:
I applaud all the work that has gone into the insteon development. I (and many others) thank you!
But, I am having the same problem; “device not ready” error. It is strange because I set up the altsteon daemon, and installed one relay. It worked well (after some addition of missed files) from the web page. Then when I added some more units, one relay, one dimmer, and one motion detector, now every device responded with a “device not ready”. I have noticed that the motion detector icon changed from red to green when the motion detector is tripped, so there is some communication. (the altsteon_cli communicated with all the units OK).
I had initially set up the plm with a fixed IP address of my vera unit, and that has not changed. Changing that to 127.0.0.1 has not made any difference.
I am using vare3, UI5, and firmware 1.5.408
Any suggestions would be appreciated!
schenkl
PS I have noticed that occasionally things work, but if tested again then I get the “device not ready” error…
I have solved my problem…I think that I did not have all the necessary files copied over…One question now, is it possible to scp ALL the files to vera3? I could not find the target directory on vera3 where the files are stored? If that were added instead of manually copying the group of files, I think that it might eliminate many hours of head scratching! Just a thought…
Hi fda,
I am having the “device not ready” message now.
I am able to talk to the 2 devices on the connection using the cli (IOLInc and FanLinc).
I can set light and fan levels with cli.
But when I try that in UI5 I get the device not ready.
However, what is VERY odd… the light level and fan state is updated on UI5.
The other odd thing is the PLM does not have a Connection tab. It goes from Control to Settings to Advanced.
I’m having the same issue. I can control my a relay from cli and I get status updates on the cli when I manually activate the relay. But I get “device not ready from the gui”.
I’m hoping I just missed something simple when setting this up.
EDIT: Well I reset the plm and the light switch and tried again and it worked. So I must not have linked them correctly.
Best Home Automation shopping experience. Shop at Ezlo!