I am up running with a enocean and a pi 3, but i am not able to get a baseID out of my enocean.
Anyone with a solution og where i can find one ? ( english / german) does not matter.
Zitatwith a enocean
With a enocean what? Enocean is a protocol. What do you have for hardware using EnOcean protocol?
Sorry for beeing unclear earlier
I have the TCM310 module with an pi3.
have follow the wiki on this pages and have been able to log some enocean activity, but i am not able to get or write the Base ID unto the TCM.
seems like there is problem communication to the hardware
Did you read Command Ref?
https://fhem.de/commandref.html#TCM
ZitatGet
TCM 120
- baseID
- Get the BaseID. You need this command in order to control EnOcean devices, see the EnOcean paragraph.
yes i have read it.... think there is some problem with my initial setup with the pi serial?
Set your TCM device on verbose 5. And then try get <TCMdevice> baseID and post the corresponding log and the result of a "list <TCMdevice>"
Internals:
BaseID 00000000
DEF ESP3 /dev/ttyAMA0@57600
DeviceName /dev/ttyAMA0@57600
FD 10
LastID 00000000
MODEL ESP3
NAME TCM_ESP3_0
NOTIFYDEV global
NR 20
NTFY_ORDER 50-TCM_ESP3_0
PARTIAL
STATE initialized
TYPE TCM
Readings:
2017-08-27 21:21:04 state initialized
Helper:
Attributes:
comType RS485
learningMode always
sendInterval 0
verbose 5
What does the FHEM log says when starting fhem?
it is so long but i will post the last part
Zitat von: fibbi am 27 August 2017, 21:33:34
Attributes:
comType RS485
Delete this attribute and try again, please.
2017.08.27 21:17:18 0: Server started with 31 defined entities (fhem.pl:13447/2017-02-19 perl:5.024001 os:linux user:fhem pid:523)
2017.08.27 21:21:00 0: Server shutdown
2017.08.27 21:21:03 1: Including fhem.cfg
2017.08.27 21:21:03 3: telnetPort: port 7072 opened
2017.08.27 21:21:03 3: WEB: port 8083 opened
2017.08.27 21:21:03 3: WEBphone: port 8084 opened
2017.08.27 21:21:03 3: WEBtablet: port 8085 opened
2017.08.27 21:21:03 2: eventTypes: loaded 62 events from ./log/eventTypes.txt
2017.08.27 21:21:03 3: Opening TCM_ESP3_0 device /dev/ttyAMA0
2017.08.27 21:21:03 3: Setting TCM_ESP3_0 serial parameters to 57600,8,N,1
2017.08.27 21:21:03 3: TCM_ESP3_0 device opened
2017.08.27 21:21:04 2: EnOcean Cryptographic functions are not available.
2017.08.27 21:21:04 1: Including ./log/fhem.save
2017.08.27 21:21:04 2: TCM TCM_ESP3_0 initialized
2017.08.27 21:21:04 1: usb create starting
2017.08.27 21:21:05 1: usb create end
same answer
Internals:
BaseID 00000000
DEF ESP3 /dev/ttyAMA0@57600
DeviceName /dev/ttyAMA0@57600
FD 10
LastID 00000000
MODEL ESP3
NAME TCM_ESP3_0
NOTIFYDEV global
NR 20
NTFY_ORDER 50-TCM_ESP3_0
PARTIAL
STATE initialized
TYPE TCM
Readings:
2017-08-27 21:52:29 state initialized
Helper:
telegramSentTimeLast 1503863585.39529
awaitCmdResp:
Attributes:
learningMode always
sendInterval 0
smartAckMailboxMax 0
verbose 5
LOG:
2017.08.27 21:52:29 2: TCM TCM_ESP3_0 initialized
2017.08.27 21:52:29 1: usb create starting
2017.08.27 21:52:30 1: usb create end
2017.08.27 21:52:30 0: Featurelevel: 5.8
2017.08.27 21:52:30 0: Server started with 31 defined entities (fhem.pl:13447/2017-02-19 perl:5.024001 os:linux user:fhem pid:1228)
2017.08.27 21:52:35 3: TCM get TCM_ESP3_0 baseID
2017.08.27 21:52:35 5: TCM TCM_ESP3_0 sent ESP: 5500010005700838
2017.08.27 21:52:35 5: SW: 5500010005700838
2017.08.27 21:52:37 2: TCM TCM_ESP3_0 Timeout reading response for get baseID
2017.08.27 21:52:54 3: TCM get TCM_ESP3_0 baseID
2017.08.27 21:52:54 5: TCM TCM_ESP3_0 sent ESP: 5500010005700838
2017.08.27 21:52:54 5: SW: 5500010005700838
2017.08.27 21:52:56 2: TCM TCM_ESP3_0 Timeout reading response for get baseID
2017.08.27 21:53:05 3: TCM get TCM_ESP3_0 baseID
2017.08.27 21:53:05 5: TCM TCM_ESP3_0 sent ESP: 5500010005700838
2017.08.27 21:53:05 5: SW: 5500010005700838
2017.08.27 21:53:07 2: TCM TCM_ESP3_0 Timeout reading response for get baseID
jump to the top
any chance that someone would be intrested in remote acces my pi?
Did you know this:
https://translate.google.de/translate?sl=de&tl=en&js=y&prev=_t&hl=de&ie=UTF-8&u=https%3A%2F%2Fwiki.fhem.de%2Fwiki%2FRaspberry_Pi_3%3A_GPIO-Port_Module_und_Bluetooth&edit-text=
(Sorry, I do not know if it is all up to date)
yes have tried that setuo and no luck ;(
Did you get it running? Check if you connected the EnOcean Pi module correctly. I've fried one module by misplacing it by one pin. :'(
Still not working. Have you got any solution? :)
Hello Fibbi,
Did you fix your problem?, I am not an expert in FHEM but maybe I can help you from the EnOcean module side and see if the module itself is the problem. The BaseID is saved in a configuration area of the chip's memory, It could happen that this area gets damaged or corrupted and since the TCM310 is not reprogrammable then there is nothing we could do... maybe we can check if this is the case (hopefully not!!!).
In this configuration area there is also other information about the Chip, like the chip ID, can you retrieve this information? (like mentioned before I am not a FHEM expert and I do not know if there is a command to do this), please try to retrieve other information like the SW etc.
You said the module is working, this means you can see EnOcean devices around, can you also send telegrams?
Let me know :) , regards