Domoticz

Posted: **Saturday 26 December 2015 22:30**

Hi,

I use Domoticz version 3.530 on my Raspberry pi 2 witch controls the Z-Stick Gen5 of Aeotec. I am trying to control a Fibaro Dimmer 2 (fgd-212) but failing helplessly.
I have domoticz running manually in debug mode so I see some more logs, these go as follows:

Code: Select all

2015-12-26 22:02:35.647 Detail, Node003,   Received: 0x01, 0x09, 0x01, 0x41, 0x53, 0x9c, 0x00, 0x04, 0x20, 0x00, 0x5d
2015-12-26 22:02:35.647 Detail, 
2015-12-26 22:02:35.647 Info, Node003, Received reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO
2015-12-26 22:02:35.647 Info, Node003,   Protocol Info for Node 3:
2015-12-26 22:02:35.647 Info, Node003,     Listening     = false
2015-12-26 22:02:35.647 Info, Node003,     Frequent      = false
2015-12-26 22:02:35.647 Info, Node003,     Beaming       = true
2015-12-26 22:02:35.648 Info, Node003,     Routing       = true
2015-12-26 22:02:35.648 Info, Node003,     Max Baud Rate = 40000
2015-12-26 22:02:35.648 Info, Node003,     Version       = 4
2015-12-26 22:02:35.648 Info, Node003,     Security      = false
2015-12-26 22:02:35.648 Info, Node003,   Basic device class    (0x04) - Routing Slave
2015-12-26 22:02:35.648 Info, Node003,   No generic or specific device classes defined
2015-12-26 22:02:35.648 Info, Node003,   Mandatory Command Classes for Node 3:
2015-12-26 22:02:35.648 Info, Node003,     COMMAND_CLASS_WAKE_UP
2015-12-26 22:02:35.648 Info, Node003,   Mandatory Command Classes controlled by Node 3:
2015-12-26 22:02:35.648 Info, Node003,     None
2015-12-26 22:02:35.648 Detail, Node156,   Expected reply was received
2015-12-26 22:02:35.649 Detail, Node156,   Message transaction complete
2015-12-26 22:02:35.649 Detail, 
2015-12-26 22:02:35.649 Detail, Node003, Removing current message
2015-12-26 22:02:35.649 Detail, Node003, Notification: NodeProtocolInfo
2015-12-26 22:02:35.649 Detail, Node003, Notification: ValueAdded
2015-12-26 22:02:35.649 Detail, Node003, Query Stage Complete (ProtocolInfo)
2015-12-26 22:02:35.649 Detail, Node003, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Probe live=1
2015-12-26 22:02:35.650 Detail, Node003, QueryStage_Probe
2015-12-26 22:02:35.650 Info, Node003, NoOperation::Set - Routing=true
2015-12-26 22:02:35.650 Detail, Node003, Queuing (NoOp) NoOperation_Set (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x00, 0x00, 0x25, 0x0f, 0xce
2015-12-26 22:02:35.650 Detail, Node003, Queuing (Query) Query Stage Complete (Probe)
2015-12-26 22:02:35.650 Detail, 
2015-12-26 22:02:35.650 Info, Node003, Sending (NoOp) message (Callback ID=0x0f, Expected Reply=0x13) - NoOperation_Set (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x00, 0x00, 0x25, 0x0f, 0xce
2015-12-26 22:02:35.662 Detail, Node003,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2015-12-26 22:02:35.662 Detail, Node003,   ZW_SEND_DATA delivered to Z-Wave stack
2015-12-26 22:02:39.809 Detail, Node003,   Received: 0x01, 0x07, 0x00, 0x13, 0x0f, 0x01, 0x01, 0x9f, 0x7b
2015-12-26 22:02:39.809 Detail, Node003,   ZW_SEND_DATA Request with callback ID 0x0f received (expected 0x0f)
2015-12-26 22:02:39.809 Info, Node003, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep.
2015-12-26 22:02:39.809 Info, Node003,   Node 3 has been marked as asleep
2015-12-26 22:02:39.809 Info, Node003, Node not responding - moving QueryStageComplete command to Wake-Up queue
2015-12-26 22:02:39.810 Detail, Node003, Notification: Notification - NoOperation
2015-12-26 22:02:39.810 Detail, Node003, Notification: Notification - Node Asleep
2015-12-26 22:02:39.810 Detail, Node001, Query Stage Complete (Neighbors)
2015-12-26 22:02:39.810 Detail, Node001, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Session live=1
2015-12-26 22:02:39.810 Detail, Node001, QueryStage_Session
2015-12-26 22:02:39.810 Detail, Node001, QueryStage_Dynamic
2015-12-26 22:02:39.810 Detail, Node001, QueryStage_Configuration
2015-12-26 22:02:39.810 Detail, Node001, QueryStage_Complete
2015-12-26 22:02:39.810 Warning, CheckCompletedNodeQueries m_allNodesQueried=0 m_awakeNodesQueried=0
2015-12-26 22:02:39.810 Warning, CheckCompletedNodeQueries all=0, deadFound=0 sleepingOnly=1
2015-12-26 22:02:39.811 Info,          Node query processing complete except for sleeping nodes.
2015-12-26 22:02:39.811 Detail, Node001, Notification: NodeQueriesComplete
2015-12-26 22:02:39.812 Detail, contrlr, Notification: AwakeNodesQueried
2015-12-26 22:02:39.812  OpenZWave: Awake Nodes queried
2015-12-26 22:09:27.782 Info, Node003, Value::Set - COMMAND_CLASS_WAKE_UP - Wake-up Interval - 0 - 1 - 3000
2015-12-26 22:09:27.782 Detail, 
2015-12-26 22:09:27.782 Detail, Node003, Queuing (WakeUp) WakeUpCmd_IntervalSet (Node=3): 0x01, 0x0d, 0x00, 0x13, 0x03, 0x06, 0x84, 0x04, 0x00, 0x0b, 0xb8, 0x01, 0x25, 0x10, 0xe3
2015-12-26 22:09:27.782 Detail, 
2015-12-26 22:09:27.782 Detail, Node003, Queuing (WakeUp) WakeUpCmd_IntervalGet (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x84, 0x05, 0x25, 0x11, 0x51
2015-12-26 22:10:35.017  Error: OpenZWave: Internal Node ValueID not found! NodeID: 3 (0x03), instanceID: 0
2015-12-26 22:11:08.023  Error: OpenZWave: Internal Node ValueID not found! NodeID: 3 (0x03), instanceID: 0

So the most disturbing lines seem (to me) the last ones.
The thing is, when I check the ~/domoticz/Config/fibaro directory i do see: fgd212.xml so that would suggest that he would find the correct config. Can someone help me please?

Posted: **Sunday 27 December 2015 16:02**

see my other replies in my thread.

you also might want to check if the fgd212 config file is in your config, otherwise you need to upgrade domoticz

/usr/local/domoticz/Config/fibaro should contain a file called fgd212.xml

Posted: **Monday 28 December 2015 19:16**

Hi Gravityz,

thank you for taking the time to reply. I do seem to have an fgd212.xml file but perhaps there is something wrong with it? This is the md5sum of mine:
5818fc472d55370ace373b42052370b5 fgd212.xml
could you perhaps check if you have the same?

thx.

Posted: **Wednesday 30 December 2015 18:34**

Just installed the FGD212 device. With a push switch the dimmer is working perfectly and I can enable/disable/dimm the lights. Openzwave detects the FGD212 perfectly. The problem is that I cannot enable/disable/dimm the lights from Domoticz. Any idea what the problem could be?

This is the error message I'm getting in the log window:

2015-12-30 18:44:24.034 Error: OpenZWave: Node not found! (NodeID: 4119, 0x1017)
2015-12-30 18:44:28.209 Error: OpenZWave: Node not found! (NodeID: 4119, 0x1017)
2015-12-30 18:44:29.123 Error: OpenZWave: Node not found! (NodeID: 4119, 0x1017)

Which is a bit strange as the node ID in the Openzwave window is 23 (0x17).

: Screen Shot 2015-12-30 at 18.48.47.png (52.21 KiB) Viewed 2402 times

I'm using Domitcz Version 3.530 with OpenZWave USB Version: 1.3-523-gb258e9e on an Aeotec Z-Stick Gen5 USB stick.

Posted: **Wednesday 30 December 2015 19:00**

gwillems wrote:Hi Gravityz,

thank you for taking the time to reply. I do seem to have an fgd212.xml file but perhaps there is something wrong with it? This is the md5sum of mine:
5818fc472d55370ace373b42052370b5 fgd212.xml
could you perhaps check if you have the same?

thx.

The default fgd212.xml file I've on the v3.430 of Domoticz has indeed the same hash value as you provided above.
5818fc472d55370ace373b42052370b5 fgd212.xml.original
51561b5717cd815165425575a1dea7bc fgd212.xml

I pulled a new version from Github using the following command:
wget https://raw.githubusercontent.com/xs4/o ... fgd212.xml

And indeed it seems that this file is different, at least it give a different hash value.

I hope that with wget I pull the file in the correct format. Can somebody confirm this is the correct way of pulling a new version of the xml file?

Posted: **Wednesday 30 December 2015 19:48**

Strangely enough, the second dimmer of the same type I just added is working in one go with the xml file I pulled from the github.

Posted: **Wednesday 30 December 2015 19:59**

And I removed the first dimmer from Domoticz and added it again and it is working now.

I changed the "28. Scene activation functionality:" configuration back to "deactivated", maybe this was causing the problem as well.

My problems seems to be solved, hope this can help others as well. Good luck.

Posted: **Friday 01 January 2016 14:20**

i noticed that fgd212.xml has a BUG in it.
this is causing wrong settings for a couple of parameters

if you read through the file you see all the parameters go by(1-59)

notice the last line specifies 53 which in fact should be 59.

i am just starting of with Zwave and i can not believe i found that bug since it is so obvious

Domoticz

Problem with AEOTEC Z-stick gen5 and Fibaro fgd-212 dimmer

Problem with AEOTEC Z-stick gen5 and Fibaro fgd-212 dimmer

Re: Problem with AEOTEC Z-stick gen5 and Fibaro fgd-212 dimm

Re: Problem with AEOTEC Z-stick gen5 and Fibaro fgd-212 dimm

Re: Problem with AEOTEC Z-stick gen5 and Fibaro fgd-212 dimm

Re: Problem with AEOTEC Z-stick gen5 and Fibaro fgd-212 dimm

Re: Problem with AEOTEC Z-stick gen5 and Fibaro fgd-212 dimm

Re: Problem with AEOTEC Z-stick gen5 and Fibaro fgd-212 dimm

Re: Problem with AEOTEC Z-stick gen5 and Fibaro fgd-212 dimm