Hi Ron,
I've just pulled the latest trunk for domotiga, as you've put in experimental FS20 support via the CUL/CUN/CUNO.
I was able to defined my CUNO device, but under "Add Device" I can't select the CUNO device to connect to. How do I define a device?
Eager and willing to test.. my FS20 / FHT gear are ready for some bug-tracking
Jelle.
CUL/CUNO Support
Moderator: RDNZL
CUL/CUNO Support
If you can't fix it with a hammer, you've got an electrical problem!
Fibaro HC2, various z-wave switching, alerting, detection modules.
ELV FHT80b heating system.
Fibaro HC2, various z-wave switching, alerting, detection modules.
ELV FHT80b heating system.
- RDNZL
- Forum Moderator
- Posts: 1008
- Joined: Sun Sep 24, 2006 1:45 pm
- Location: Dordrecht, The Netherlands
- Contact:
Re: CUL/CUNO Support
I added the CUL interface to the sql scripts.
Look here domotiga.nl/projects/domotiga/repositor ... isions/638
If you are already at version 0.1.199 update manually with:
You can use the FS20 devicetypes which are already in the db, I will add EM1000 types later, you can add them yourself from modules editor.
Look here domotiga.nl/projects/domotiga/repositor ... isions/638
If you are already at version 0.1.199 update manually with:
Code: Select all
mysql -u root -p domotiga <upgrade/01198to01199.sql
Regards, Ron.
Re: CUL/CUNO Support
Thanks Ron,
I was stil on revision 637. I'll go test it.
Jelle
I was stil on revision 637. I'll go test it.
Jelle
If you can't fix it with a hammer, you've got an electrical problem!
Fibaro HC2, various z-wave switching, alerting, detection modules.
ELV FHT80b heating system.
Fibaro HC2, various z-wave switching, alerting, detection modules.
ELV FHT80b heating system.
Re: CUL/CUNO Support
Hi Ron,
Let me know what you prefer in debugging the workings of this newly added features.
I tried to add a lamp, but it came back with an interface error. Probably stating it can't find the CUL device?
----
2011/08/29 09:05:34 [Devices] Interface for device with name 'Zolderlamp' is '32'
2011/08/29 09:05:34 [Devices] Address for device with name 'Zolderlamp' is '51B730'
2011/08/29 09:05:34 [Devices] Unknown Interface 32 for device 'Zolderlamp'!
----
I've added an attachment with my added device in the overview.
I do get a positive connection with the CUL and it's showing wonderful messages of my FHT system. A few are missing though, but it could be malformed packets as well. the CUNO at some points does need a reboot .
Let me know what you prefer in debugging the workings of this newly added features.
I tried to add a lamp, but it came back with an interface error. Probably stating it can't find the CUL device?
----
2011/08/29 09:05:34 [Devices] Interface for device with name 'Zolderlamp' is '32'
2011/08/29 09:05:34 [Devices] Address for device with name 'Zolderlamp' is '51B730'
2011/08/29 09:05:34 [Devices] Unknown Interface 32 for device 'Zolderlamp'!
----
I've added an attachment with my added device in the overview.
I do get a positive connection with the CUL and it's showing wonderful messages of my FHT system. A few are missing though, but it could be malformed packets as well. the CUNO at some points does need a reboot .
- Attachments
-
- add-device-2011-08-29.png (44.2 KiB) Viewed 5764 times
If you can't fix it with a hammer, you've got an electrical problem!
Fibaro HC2, various z-wave switching, alerting, detection modules.
ELV FHT80b heating system.
Fibaro HC2, various z-wave switching, alerting, detection modules.
ELV FHT80b heating system.
Re: CUL/CUNO Support
The odd part, just continueing my testing....
when I switch the light manually, it does see it properly in the logfiles:
------------
2011/08/29 09:09:03 [CUL] FS20 message received with address: 51B730 (221234241411) command: Dim 9
2011/08/29 09:09:03 [Devices] Interface with name 'CUL Interface' has id '32'
2011/08/29 09:09:03 [Devices] Device with address '51B730' is 'Zolderlamp'
2011/08/29 09:09:03 [Devices] Device with address '51B730' and 'Zolderlamp' is a new device
2011/08/29 09:09:03 [Devices] ValueUpdate() called for device with id '39' and name 'Zolderlamp'
2011/08/29 09:09:03 [Devices] Device change triggered for device with id '39' and value1 'Dim 9'
2011/08/29 09:09:05 [CUL] < F51B73000E3
2011/08/29 09:09:05 [CUL] FS20 message received with address: 51B730 (221234241411) command: Off
2011/08/29 09:09:05 [Devices] Interface with name 'CUL Interface' has id '32'
2011/08/29 09:09:05 [Devices] Device with address '51B730' is 'Zolderlamp'
2011/08/29 09:09:05 [Devices] ValueUpdate() called for device with id '39' and name 'Zolderlamp'
2011/08/29 09:09:05 [Devices] Device change triggered for device with id '39' and value1 'Off'
2011/08/29 09:09:06 [CUL] < F51B73011E2
2011/08/29 09:09:06 [CUL] FS20 message received with address: 51B730 (221234241411) command: Dim 9
2011/08/29 09:09:06 [Devices] Interface with name 'CUL Interface' has id '32'
2011/08/29 09:09:06 [Devices] Device with address '51B730' is 'Zolderlamp'
2011/08/29 09:09:06 [Devices] ValueUpdate() called for device with id '39' and name 'Zolderlamp'
2011/08/29 09:09:06 [Devices] Device change triggered for device with id '39' and value1 'Dim 9'
-----------
Trying to recreate the lamp device, or trying to switch it after having it manually switched doesn't make it work. I still get the same interface 32 error.
when I switch the light manually, it does see it properly in the logfiles:
------------
2011/08/29 09:09:03 [CUL] FS20 message received with address: 51B730 (221234241411) command: Dim 9
2011/08/29 09:09:03 [Devices] Interface with name 'CUL Interface' has id '32'
2011/08/29 09:09:03 [Devices] Device with address '51B730' is 'Zolderlamp'
2011/08/29 09:09:03 [Devices] Device with address '51B730' and 'Zolderlamp' is a new device
2011/08/29 09:09:03 [Devices] ValueUpdate() called for device with id '39' and name 'Zolderlamp'
2011/08/29 09:09:03 [Devices] Device change triggered for device with id '39' and value1 'Dim 9'
2011/08/29 09:09:05 [CUL] < F51B73000E3
2011/08/29 09:09:05 [CUL] FS20 message received with address: 51B730 (221234241411) command: Off
2011/08/29 09:09:05 [Devices] Interface with name 'CUL Interface' has id '32'
2011/08/29 09:09:05 [Devices] Device with address '51B730' is 'Zolderlamp'
2011/08/29 09:09:05 [Devices] ValueUpdate() called for device with id '39' and name 'Zolderlamp'
2011/08/29 09:09:05 [Devices] Device change triggered for device with id '39' and value1 'Off'
2011/08/29 09:09:06 [CUL] < F51B73011E2
2011/08/29 09:09:06 [CUL] FS20 message received with address: 51B730 (221234241411) command: Dim 9
2011/08/29 09:09:06 [Devices] Interface with name 'CUL Interface' has id '32'
2011/08/29 09:09:06 [Devices] Device with address '51B730' is 'Zolderlamp'
2011/08/29 09:09:06 [Devices] ValueUpdate() called for device with id '39' and name 'Zolderlamp'
2011/08/29 09:09:06 [Devices] Device change triggered for device with id '39' and value1 'Dim 9'
-----------
Trying to recreate the lamp device, or trying to switch it after having it manually switched doesn't make it work. I still get the same interface 32 error.
If you can't fix it with a hammer, you've got an electrical problem!
Fibaro HC2, various z-wave switching, alerting, detection modules.
ELV FHT80b heating system.
Fibaro HC2, various z-wave switching, alerting, detection modules.
ELV FHT80b heating system.
Re: CUL/CUNO Support
Ron..... nice job! kudo's for you
"The was a long message here but as I understood the dev-talk is moved to the appropriate place"
To find it..... click it... http://www.domotiga.nl/projects/domotiga/boards/2
"The was a long message here but as I understood the dev-talk is moved to the appropriate place"
To find it..... click it... http://www.domotiga.nl/projects/domotiga/boards/2
Re: CUL/CUNO Support
A small status update, to compliment Ron on his fantastic work in this project:
- FS20 signals are all being received and send to the various devices. This works quite well!
- FHT messages are being received at the moment, but not properly logged. Most messages are being decrypted very nicely.
I'd say this is a huge step. I'm hoping to see nice logging for FHT in the future. And perhaps even a way to send commands to set up the entire heating controls.
Jelle
- FS20 signals are all being received and send to the various devices. This works quite well!
- FHT messages are being received at the moment, but not properly logged. Most messages are being decrypted very nicely.
I'd say this is a huge step. I'm hoping to see nice logging for FHT in the future. And perhaps even a way to send commands to set up the entire heating controls.
Jelle
If you can't fix it with a hammer, you've got an electrical problem!
Fibaro HC2, various z-wave switching, alerting, detection modules.
ELV FHT80b heating system.
Fibaro HC2, various z-wave switching, alerting, detection modules.
ELV FHT80b heating system.