Felmeddelanden vid användning

[basn]

Hej!

Har lite problem sedan jag installerade Telldus-core-2.0.103, får lite skumma felmeddelanden och är osäker på att jag gjort rätt...
Så bifogar config + felmeddelande

Code: Select all

tdtool --off 1
Turning off device 1, vardagsrum - An error occurred while communicating with TellStick (den stängs av i alla fall)

Number of devices: 3
1       vardagsrum      OFF
2       tv      OFF
3       kok     OFF

Står alltid som off vad man än gör.

Code: Select all

device {
  id = 1
  name = "vardagsrum"
  protocol = "risingsun"
  model = "gao"
  parameters {
    house = "A"
    unit = "1"
  }
}

device {
  id = 2
  name = "tv"
  protocol = "risingsun"
  model = "gao"
  parameters { 
    house = "A"
    unit = "2" 
  }
}  

device {
  id = 3
  name = "kok"
  protocol = "risingsun"
  model = "gao"
  parameters { 
    house = "A"
    unit = "3" 
  }
}

Som sagt, skaffade detta igår så är osäker på hur det ska vara confas så all hjälp uppskattas!

[micke.prag]

Vad har du för batch på din TellStick?

Fungerar on och off även om du får felmeddelande?

[micke.prag]

För övrigt så finns inte modellen "gao" till protokollet "risingsun". Ställ in den som "selflearning" eller "codeswitch".
House är 1-4. Läs mer här:
http://developer.telldus.se/wiki/TellSt ... #risingsun

[basn]

Fungerar att släcka och tända innan jag ställde om också, testade även att ställa som du sa... men det fungerar då också fast får felmeddelande.
Batch 11
sn 701

Code: Select all

device {
  id = 1
  name = "vardagsrum"
  protocol = "risingsun"
  model = "codeswitch"
  parameters {
    house = "1"
    unit = "1"
  }
}

device {
  id = 2
  name = "tv"
  protocol = "risingsun"
  model = "codeswitch"
  parameters { 
    house = "1"
    unit = "2" 
  }
}  

device {
  id = 3
  name = "kok"
  protocol = "risingsun"
  model = "codeswitch"
  parameters { 
    house = "1"
    unit = "3" 
  }
} 

[basn]

När jag hade plockat ur tellsticken och satt i och startat om telldusd så får jag inga felmeddelanden längre, skumt

[Simon G]

Jag får också detta felmeddelande, det funkar men felmeddelandet kommer.
Jag har också GAO som körs med risingsun enligt nedan .conf...

Code: Select all

deviceNode = "/dev/usb/ttyUSB0"
device {
  id = 1
  name = "Sov"
  protocol = "risingsun"
  model = "codeswitch"
  parameters {
    house = "1"
    unit = "1"
  }
}
device {
  id = 2
  name = "Kok"
  protocol = "risingsun"
  model = "codeswitch"
  parameters {
    house = "1"
    unit = "2"
  }
}
device {
  id = 3
  name = "Vardagsrum"
  protocol = "risingsun"
  model = "codeswitch"
  parameters {
    house = "1"
    unit = "3"
  }

Följande fel får jag:

Code: Select all

[/] # /usr/local/bin/tdtool --on 2
Turning on device 2, Kok - An error occurred when communication with TellStick

Vad är det för fel tro??
Tellsticken sitter i en QNAP NAS och jag försöker få HomeAutomation att funka, men det funkar inte förmodligen beroende på felet ovan?!

/Simon

[Simon G]

Ingen som känner igen problemet?
Jag har nu bytt brytare för att se om de hjälpte, kör nu Proove, men de beter sig exakt likadant som de gamla brytarna.

Är det något fel på usb-drivisarna på nåt vis? Hur kan man felsöka det i så fall?

Både usbserial.ko och ftdi_sio.ko ligger med i denna firmwaren.

[micke.prag]

Batch på TellStick? Version på mjukvaran?

[Simon G]

Stickan är en Batch 11 och jag har installerat Telldus-core 2.0.4...

[micke.prag]

Har du möjlighet att testa i en dator och se om du får samma fel där?

[error1]

I get the same error message on my white replacement tellstick (with antenna lead) that i got when i RMAed my old blue one that had range issues. This is with telldus-core from the unstable repository so i could get tellduscenter

I can't get dim commands to work, but turning devices on and off work. It does the same on two different computers (one running ubuntu 10.10 64-bit, the other 11.04 beta 64-bit)
Honestly i hadn't even noticed it until i tried setting up tellduscenter for the live service, and noticed you could make device groups now. When trying to toggle a group, only the first device receives a command.

Is it possible to run telldusd with debugging output? I tried running it with --nodaemon but got no text output from it.

I also tried reverting back to telldus-core from the stable repository but then the telldusd binary was suddenly missing from /usr/sbin/.
I'm gonna try a clean install of ubuntu 10.10 on a spare machine to see if it does the same if i start with stable telldus-core and then upgrade.

(sorry this post is in english, it's easier for me than trying to type a mishmash of norwegian and swedish!)

[error1]

OK, I've tested my tellstick on a fresh install of ubuntu. Using telldus-core from the stable repository, everything works fine. Installing from the unstable repository causes the "an error occurred" messages to appear. Does that mean it's an issue with the firmware version in my particular tellstick?

Dimming does work on both versions of telldus-core though, i just got the syntax wrong while testing it earlier, (i tried tdtool --dim --dimlevel 128 1 instead of the correct tdtool --dimlevel 128 --dim 1, and tdtool doesn't complain about it, it just exits silently.)

[micke.prag]

OK, I've tested my tellstick on a fresh install of ubuntu. Using telldus-core from the stable repository, everything works fine. Installing from the unstable repository causes the "an error occurred" messages to appear. Does that mean it's an issue with the firmware version in my particular tellstick?

In what order do you plug in TellStick /start telldusd?

[stefan.persson]

Could you try to run lsmod and see if ftdi_sio is loaded? In that case, if you unload it with rmmod (only try it if you don't need it for some other equipment), does the error message disappear?

[error1]

ftdi_sio was loaded, it's in use by the USB-UIRT ... i unplugged all the other eqipment and got the module unloaded with rmmod, but the error message from tdtool is the same.

However, stopping telldusd, unplugging the tellstick, starting telldusd and replugging the tellstick seems to have fixed the issue. What would be the reason for this?
I'm gonna try rebooting a couple of times to see if the issue comes back, but i can live with that workaround since it's an always-on computer anyway

... ok i did some more testing after replugging the usb-uirt, and it seems like just having other ftdi based usb devices connected cause it to not work? even with the ftdi_sio driver unloaded? Maybe that one time it worked was a lucky shot?