This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

EnOcean profile A5-20-01
#1
Hi,
We need to communicate and act on thermostatic valves EnOcean. The provider's documentation indicate to use the profile A5-20-01 but this one does'nt exists in the list. How can I do ? (signal kind : 0-100%)

Thank you for answer
Reply
#2
Hi,

Check this: https://forum.logicmachine.net/showthrea...61#pid4261

BR,

Erwin
Reply
#3
Hi
Based on Erwins lua-drivers I did an implementation of Thermokon SAB05 (https://www.thermokon.de/produkte/easyse...ren/sab05/) on a Wiser/SpaceLynk. I did some documentation too. But it's in German. Anyhow, if you are interested in this documentation I can dig it out and provide it in this forum.
Regards
Reply
#4
(15.11.2019, 16:26)Erwin van der Zwart Wrote: Hi,

Check this: https://forum.logicmachine.net/showthrea...61#pid4261

BR,

Erwin

Thanks for sharing your link !! I will try integrate it soon.
I have little questions anyway :
--> I found a little error in the driver I think : line 100 / "update" at valve position feedback adress in the Active Harvesting Status section ??
--> Variables "Adress" (16/2/x) : has this section to be substituted according to the equipment (We have several valves...) or should we duplicate the lua driver for each equipment ??
--> Blocking problem : mapping EnOcean to KNX is impossible without a profile... which one can I choose in the list for complete working ?

Thank you again for sharing your experience !

JSK
Reply
#5
This is a separate script not a profile. You need to use RAW profile in EnOcean tab. Script handles parsing of RAW value.
Reply
#6
(21.11.2019, 07:50)admin Wrote: This is a separate script not a profile. You need to use RAW profile in EnOcean tab. Script handles parsing of RAW value.
It's all explained in the header of the script (:

Line 100 is not a error, this is not a update to the drive status value but a KNX value update command, i use grp.update on purpose as i don't see any reason to post feedback to the KNX bus, if you need it on KNX then you should change it to grp.write

Yes you need a seperate event based script for each drive, so if you have 10 drives you need 20x 4 byte objects and 10x event based scripts, each event script is attached to the Enocean incomming 4 byte RAW value, and you need to set 10x the response 4 byte object to Enocean Outgoing.  The addresses needs to be matched to the objects you create...

BR,

Erwin
Reply


Forum Jump: