›
This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.

The Homey Community has been moved to https://community.athom.com.

This forum is now read-only for archive purposes.

Fibaro Motion Sensor (FGMS-001), not possible to add to Homey

124»

Comments

  • ingmaringmar Member
    ingmar said:
    ingmar said:
    Thanks ted, I appreciate it. I will try updating the settings again with your instructions. Basically, if there is just one motion sensor connected and only one sensor in total, I would be able to get temperature and/or lux each 15 minutes? I would be able to see that in the insights?

     thanks
    I don't know when you added the motion sensor to Homey (SW version / app version). 
    If it is not too much of a trouble, I would recommend to remove the sensor and re-add it to Homey and update the settings as advised; to have a clean slate ;) 

    If you set it to be updated every 15 minutes. It should provide an update every 15 minutes.
    Please note that in insights, the value will updated only if the value is different compared to the previous logged value. Throughout the day, with changing brightness and temperature, this should correspond to every 15 minutes.

    So, I did the removal, the official reset of the sensors, adding the sensors again, and added them back to the flows. Honestly, it is even worse now, even with the factory defaults. In the zwave log I see errors occurring like:

     ProcessSendData[190]: Error: TRANSMIT_COMPLETE_NO_ACK

    which leads to the GitHub issue: https://github.com/athombv/homey/issues/1333

    Still getting the error in transmission, but, insight data is correct now! and everything seems to work.
  • jimmy_zeropmjimmy_zeropm Member
    How do you guys experience the range of the motion sensor? I moved it to several places but BEST is 3-4 meters.. I wanted to use it's range to cover two entries in the living room but now it seems I have to buy two more sensors.. Bit disappointed...
  • casedacaseda Member
    One of my motion sensors trigger from 6 meters distance and 2,5 meters up, and triggers as soon as I walk from behind the outside door 99% of the time that 1% it is just before I closed the door behind my back again. 

    The rest of my motion sensor are not more then 4 meters away from entry points of its field of view
  • ingmaringmar Member
    edited March 2017
    ingmar said:
    ingmar said:
    ingmar said:
    Thanks ted, I appreciate it. I will try updating the settings again with your instructions. Basically, if there is just one motion sensor connected and only one sensor in total, I would be able to get temperature and/or lux each 15 minutes? I would be able to see that in the insights?

     thanks
    I don't know when you added the motion sensor to Homey (SW version / app version). 
    If it is not too much of a trouble, I would recommend to remove the sensor and re-add it to Homey and update the settings as advised; to have a clean slate ;) 

    If you set it to be updated every 15 minutes. It should provide an update every 15 minutes.
    Please note that in insights, the value will updated only if the value is different compared to the previous logged value. Throughout the day, with changing brightness and temperature, this should correspond to every 15 minutes.

    So, I did the removal, the official reset of the sensors, adding the sensors again, and added them back to the flows. Honestly, it is even worse now, even with the factory defaults. In the zwave log I see errors occurring like:

     ProcessSendData[190]: Error: TRANSMIT_COMPLETE_NO_ACK

    which leads to the GitHub issue: https://github.com/athombv/homey/issues/1333

    Still getting the error in transmission, but, insight data is correct now! and everything seems to work.
    But... do you guys also encounter the errors as: Error: TRANSMIT_COMPLETE_NO_ACK ?
    Because what I am seeing in the zwave log is:
    -Sensor detects movement and then showing the error
    -Homey is not activating the flow based on movement

    So, it worked for a day after resetting and re-adding the sensors, but now it's extremely buggy.

    Connectivity between sensor and homey is direct and a maximum of 3 meters.

    thanks
  • jimmy_zeropmjimmy_zeropm Member
    @ingmar I do, I see this coming back very often in my logs. Could this has something to do with the short blink I see on the sensor. Iow, when motion is detected there is a long blink, and sometimes I see a very short blink.. 
  • ingmaringmar Member
    jimmy_zeropm said:
    @ingmar I do, I see this coming back very often in my logs. Could this has something to do with the short blink I see on the sensor. Iow, when motion is detected there is a long blink, and sometimes I see a very short blink.. 
    hmm, could be, the short blink is the indication that motion is detected but the motion wait time is active. In my case I have it on 3 seconds, so after 3 seconds motion should be reported again. Within the 3 seconds i should get a short blink. Let me test that with the logging. 

  • TedTolboomTedTolboom Member
    @ingmar @jimmy_zeropm can you provide a section of the Z-wave log where the `Error: TRANSMIT_COMPLETE_NO_ACK` is shown.

    In principle, this is the response that Homey sends a command to a device (TRANSMIT_COMPLETE) but that there is not acknowledgement (NO_ACK) that the device executed this command.
    Specifically, it is relevant to which node Homey is sending which command.

    On the blincking: can you share a screenshot of the settings used?
  • ingmaringmar Member
    @ingmar @jimmy_zeropm can you provide a section of the Z-wave log where the `Error: TRANSMIT_COMPLETE_NO_ACK` is shown.

    In principle, this is the response that Homey sends a command to a device (TRANSMIT_COMPLETE) but that there is not acknowledgement (NO_ACK) that the device executed this command.
    Specifically, it is relevant to which node Homey is sending which command.

    On the blincking: can you share a screenshot of the settings used?
    [2017-03-10T10:39:50.288Z] Command start: getNetworkTopology
    [2017-03-10T10:39:50.441Z] Command end: getNetworkTopology
    [2017-03-10T10:40:06.715Z] Node[12]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40
    [2017-03-10T10:40:06.717Z] Node[12]: sendData to COMMAND_CLASS_SECURITY, params 0x8022ee980d94d38e43
    [2017-03-10T10:40:06.719Z] Command start: sendData
    [2017-03-10T10:40:06.728Z] ProcessSendData[2061]: To node: 12 with data: 0x988022ee980d94d38e43 and txOptions: ACK,AUTO_ROUTE
    [2017-03-10T10:40:06.756Z] Node[12]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40
    [2017-03-10T10:40:06.757Z] Node[12]: sendData to COMMAND_CLASS_SECURITY, params 0x800efed9c26eacdab5
    [2017-03-10T10:40:06.757Z] Command start: sendData
    [2017-03-10T10:40:06.792Z] Node[12]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40
    [2017-03-10T10:40:06.795Z] Node[12]: sendData to COMMAND_CLASS_SECURITY, params 0x803b3b143952a277d3
    [2017-03-10T10:40:06.796Z] Command start: sendData
    [2017-03-10T10:40:06.819Z] Node[12]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40
    [2017-03-10T10:40:06.820Z] Node[12]: sendData to COMMAND_CLASS_SECURITY, params 0x808311e1cc84b0bac9
    [2017-03-10T10:40:06.821Z] Command start: sendData
    [2017-03-10T10:40:06.846Z] Node[12]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40
    [2017-03-10T10:40:06.847Z] Node[12]: sendData to COMMAND_CLASS_SECURITY, params 0x80e3989215585db952
    [2017-03-10T10:40:06.848Z] Command start: sendData
    [2017-03-10T10:40:06.870Z] Node[12]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40
    [2017-03-10T10:40:06.871Z] Node[12]: sendData to COMMAND_CLASS_SECURITY, params 0x80419c71ef46b0bdbc
    [2017-03-10T10:40:06.872Z] Command start: sendData
    [2017-03-10T10:40:06.909Z] Node[12]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40
    [2017-03-10T10:40:06.910Z] Node[12]: sendData to COMMAND_CLASS_SECURITY, params 0x80623c04e4d06bc8f8
    [2017-03-10T10:40:06.910Z] Command start: sendData
    [2017-03-10T10:40:06.969Z] ProcessSendData[2062]: To node: 12 with data: 0x98800efed9c26eacdab5 and txOptions: ACK,AUTO_ROUTE
    [2017-03-10T10:40:06.983Z] Command end: sendData
    [2017-03-10T10:40:07.047Z] Node[12]: Received application command for COMMAND_CLASS_SECURITY, data: 0x813dd9feed92ff6a7137317748a30996d8c1f52219dd02078518fa50
    [2017-03-10T10:40:07.086Z] Node[12]: Decapsulated frame from COMMAND_CLASS_SECURITY to COMMAND_CLASS_NOTIFICATION, data 0x05000000ff070800
    [2017-03-10T10:40:08.495Z] ProcessSendData[2062]: Error: TRANSMIT_COMPLETE_NO_ACK
    [2017-03-10T10:40:08.503Z] ProcessSendData[2063]: To node: 12 with data: 0x98803b3b143952a277d3 and txOptions: ACK,AUTO_ROUTE
    [2017-03-10T10:40:08.509Z] Command end: sendData
    [2017-03-10T10:40:08.745Z] ProcessSendData[2063]: Error: TRANSMIT_COMPLETE_NO_ACK
    [2017-03-10T10:40:08.752Z] ProcessSendData[2064]: To node: 12 with data: 0x98808311e1cc84b0bac9 and txOptions: ACK,AUTO_ROUTE
    [2017-03-10T10:40:08.758Z] Command end: sendData
    [2017-03-10T10:40:09.080Z] ProcessSendData[2064]: Error: TRANSMIT_COMPLETE_NO_ACK
    [2017-03-10T10:40:09.095Z] ProcessSendData[2065]: To node: 12 with data: 0x9880e3989215585db952 and txOptions: ACK,AUTO_ROUTE
    [2017-03-10T10:40:09.105Z] Command end: sendData
    [2017-03-10T10:40:09.387Z] ProcessSendData[2065]: Error: TRANSMIT_COMPLETE_NO_ACK
    [2017-03-10T10:40:09.396Z] ProcessSendData[2066]: To node: 12 with data: 0x9880419c71ef46b0bdbc and txOptions: ACK,AUTO_ROUTE
    [2017-03-10T10:40:09.402Z] Command end: sendData
    [2017-03-10T10:40:09.601Z] ProcessSendData[2066]: Error: TRANSMIT_COMPLETE_NO_ACK
    [2017-03-10T10:40:09.609Z] ProcessSendData[2067]: To node: 12 with data: 0x9880623c04e4d06bc8f8 and txOptions: ACK,AUTO_ROUTE
    [2017-03-10T10:40:09.614Z] Command end: sendData
    [2017-03-10T10:40:09.953Z] ProcessSendData[2067]: Error: TRANSMIT_COMPLETE_NO_ACK
    [2017-03-10T10:40:09.960Z] Command end: sendData
    [2017-03-10T10:40:12.350Z] Node[12]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40
    [2017-03-10T10:40:12.351Z] Node[12]: sendData to COMMAND_CLASS_SECURITY, params 0x80e87431354f4dd043
    [2017-03-10T10:40:12.352Z] Command start: sendData
    [2017-03-10T10:40:12.359Z] ProcessSendData[2068]: To node: 12 with data: 0x9880e87431354f4dd043 and txOptions: ACK,AUTO_ROUTE
    [2017-03-10T10:40:12.394Z] Node[12]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40
    [2017-03-10T10:40:12.395Z] Node[12]: sendData to COMMAND_CLASS_SECURITY, params 0x8022f821c44caa6fb8
    [2017-03-10T10:40:12.395Z] Command start: sendData
    [2017-03-10T10:40:12.426Z] Node[12]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40
    [2017-03-10T10:40:12.427Z] Node[12]: sendData to COMMAND_CLASS_SECURITY, params 0x80bd081d719d6d810d
    [2017-03-10T10:40:12.427Z] Command start: sendData
    [2017-03-10T10:40:12.453Z] Node[12]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40
    [2017-03-10T10:40:12.454Z] Node[12]: sendData to COMMAND_CLASS_SECURITY, params 0x80f67d979c5369b3a8
    [2017-03-10T10:40:12.454Z] Command start: sendData
    [2017-03-10T10:40:12.505Z] ProcessSendData[2069]: To node: 12 with data: 0x988022f821c44caa6fb8 and txOptions: ACK,AUTO_ROUTE
    [2017-03-10T10:40:12.522Z] Command end: sendData
    [2017-03-10T10:40:12.575Z] Node[12]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40
    [2017-03-10T10:40:12.577Z] Node[12]: sendData to COMMAND_CLASS_SECURITY, params 0x80283c7c0fb1547808
    [2017-03-10T10:40:12.579Z] Command start: sendData
    [2017-03-10T10:40:12.648Z] Node[12]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40
    [2017-03-10T10:40:12.651Z] Node[12]: sendData to COMMAND_CLASS_SECURITY, params 0x805cbb36a2bb98baaf
    [2017-03-10T10:40:12.652Z] Command start: sendData
    [2017-03-10T10:40:12.682Z] Node[12]: Received application command for COMMAND_CLASS_SECURITY, data: 0x819ad9ae029def5ede2cb4cdf711301494ff408fe881754592e11c95e0
    [2017-03-10T10:40:12.708Z] Node[12]: Decapsulated frame from COMMAND_CLASS_SECURITY to COMMAND_CLASS_NOTIFICATION, data 0x05000000ff07000108
    [2017-03-10T10:40:14.038Z] ProcessSendData[2069]: Error: TRANSMIT_COMPLETE_NO_ACK
    [2017-03-10T10:40:14.048Z] ProcessSendData[2070]: To node: 12 with data: 0x9880bd081d719d6d810d and txOptions: ACK,AUTO_ROUTE
    [2017-03-10T10:40:14.059Z] Command end: sendData
    [2017-03-10T10:40:14.357Z] ProcessSendData[2070]: Error: TRANSMIT_COMPLETE_NO_ACK
    [2017-03-10T10:40:14.371Z] ProcessSendData[2071]: To node: 12 with data: 0x9880f67d979c5369b3a8 and txOptions: ACK,AUTO_ROUTE
    [2017-03-10T10:40:14.377Z] Command end: sendData
    [2017-03-10T10:40:14.595Z] ProcessSendData[2071]: Error: TRANSMIT_COMPLETE_NO_ACK
    [2017-03-10T10:40:14.603Z] ProcessSendData[2072]: To node: 12 with data: 0x9880283c7c0fb1547808 and txOptions: ACK,AUTO_ROUTE
    [2017-03-10T10:40:14.608Z] Command end: sendData
    [2017-03-10T10:40:14.912Z] ProcessSendData[2072]: Error: TRANSMIT_COMPLETE_NO_ACK
    [2017-03-10T10:40:14.922Z] ProcessSendData[2073]: To node: 12 with data: 0x98805cbb36a2bb98baaf and txOptions: ACK,AUTO_ROUTE
    [2017-03-10T10:40:14.927Z] Command end: sendData
    [2017-03-10T10:40:15.231Z] ProcessSendData[2073]: Error: TRANSMIT_COMPLETE_NO_ACK
    [2017-03-10T10:40:15.237Z] Command end: sendData

    This is just one movement after showing the diagram, BW WK (id 12), one meter away from homey.




  • casedacaseda Member
    edited March 2017
    @ingmar could your try to wake up your sensor manually nearby homey once and let it completely timeout on its awake state (blue led on to automatic off)
  • ingmaringmar Member
    caseda said:
    @ingmar could your try to wake up your sensor manually nearby homey once and let it completely timeout on its awake state (blue led on to automatic off)

    will do, and then check the logs?
  • jimmy_zeropmjimmy_zeropm Member
    Here's my input;

    [2017-03-10T18:19:39.913Z] ProcessSendData[661]: To node: 3 with data: 0x9880d1ea4195228f7cd8 and txOptions: ACK,AUTO_ROUTE
    [2017-03-10T18:19:39.935Z] Node[3]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40
    [2017-03-10T18:19:39.936Z] Node[3]: sendData to COMMAND_CLASS_SECURITY, params 0x80d45ff7dc5d72d533
    [2017-03-10T18:19:39.937Z] Command start: sendData
    [2017-03-10T18:19:41.085Z] ProcessSendData[662]: To node: 3 with data: 0x9880d45ff7dc5d72d533 and txOptions: ACK,AUTO_ROUTE
    [2017-03-10T18:19:41.091Z] Command end: sendData
    [2017-03-10T18:19:41.113Z] Node[3]: Received application command for COMMAND_CLASS_SECURITY, data: 0x81e35f809010b5354d1c5e1e7b0aac0f1f140834d16c2747e8cf8b32d9
    [2017-03-10T18:19:41.130Z] Node[3]: Decapsulated frame from COMMAND_CLASS_SECURITY to COMMAND_CLASS_NOTIFICATION, data 0x05000000ff07000108
    [2017-03-10T18:19:43.091Z] ProcessSendData[662]: Error: TRANSMIT_COMPLETE_NO_ACK
    [2017-03-10T18:19:43.106Z] Command end: sendData
    [2017-03-10T18:20:17.511Z] Node[3]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40
    [2017-03-10T18:20:17.512Z] Node[3]: sendData to COMMAND_CLASS_SECURITY, params 0x8008a85bf10484b6bf
    [2017-03-10T18:20:17.512Z] Command start: sendData
    [2017-03-10T18:20:17.519Z] ProcessSendData[663]: To node: 3 with data: 0x988008a85bf10484b6bf and txOptions: ACK,AUTO_ROUTE
    [2017-03-10T18:20:17.546Z] Command end: sendData
    [2017-03-10T18:20:17.574Z] Node[3]: Received application command for COMMAND_CLASS_SECURITY, data: 0x81889c19b7e1862604a364602adf09a03a809e089ad7bc3de1df8f16
    [2017-03-10T18:20:17.598Z] Node[3]: Decapsulated frame from COMMAND_CLASS_SECURITY to COMMAND_CLASS_NOTIFICATION, data 0x05000000ff070800

  • jimmy_zeropmjimmy_zeropm Member
    I'm also not sure about the temperature correction, and updates... If you look at my charts you see that the lux are nicely reported but the temperature is not. It is set to be logged. 

    When you look at the temperature on it's own it looks like;

    But when combined it seems a bit different;

  • jimmy_zeropmjimmy_zeropm Member
    edited March 2017
    I've found some interresting outcomes with the sensors motion detection range. I've marked the sensor in 4 even parts on the outside. I then turned the sensor bit by bit over his axis and suddenly I gained 2+ metres of detection range. I repeated that several times and the outcome is constantly the same. It seems that the baloonish shape the manual indicates is slightly incorrect. It is that shape but it's far more flat. Now I have a perfect wide coverage of the room, pointed from ceiling to floor in allmost a 45 degree angle. Really worth trying for everyone who is experiencing a poor range.
  • ingmaringmar Member
    I've found some interresting outcomes with the sensors motion detection range. I've marked the sensor in 4 even parts on the outside. I then turned the sensor bit by bit over his axis and suddenly I gained 2+ metres of detection range. I repeated that several times and the outcome is constantly the same. It seems that the baloonish shape the manual indicates is slightly incorrect. It is that shape but it's far more flat. Now I have a perfect wide coverage of the room, pointed from ceiling to floor in allmost a 45 degree angle. Really worth trying for everyone who is experiencing a poor range.
    See page 18, http://manuals.fibaro.com/content/manuals/en/FGMS-001/FGMS-001-EN-SG.pdf
  • jimmy_zeropmjimmy_zeropm Member
    @ingmar I've seen that but I think the horizontal thickness of the range is much more flat then the image shows..
  • CarloVCarloV Member
    Hi all,

    I am new to Homey, ut used to play around with other Z-wave stuff.
    My Fibaro Motionsensor FGMS-001, Firmware 3.2 (Z-Wave Plus) is not connecting to my brand new Homey Firmware Version: 1.5.6.
    I tried just about anything i read here, reset of the Fibaro, reset of Homey, putting the sensor right at the side of Homey, ... nothing seems to help.

    Anyone has a new idea?

    Thanks
Sign In or Register to comment.