Announcement

Collapse
No announcement yet.

Strange behavior with Steinel 140-2 and Homesser

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Kernal69
    replied
    Hi
    Thanks for the answer.

    I only got 3 association for each Steinel device but i have found that it's the Association 2 that is the problem.
    If i remove it all begin to work.
    But if i do a "Full scan" the problem is back and i have to remove Association 2 again.
    WHY ? !
    And after the scan i got a new problem.
    Suddenly the Luminance for steinel disappeared and i can not get it back.
    And in the log in the scan says "Multilevel sensor report was not recieved"
    WHY ? !

    I am begining to get very tired of Homeseer becuase i think it works very poorly.
    The only the thing i do everytime is when working with Homeseer is looking for problem instead of doing somthing creative.
    Very bad !

    Best regards

    Leave a comment:


  • Martin75a
    replied
    I have the same problem. The only solution to get it started again is to shut down homeseer, pull out the z-wave stick. put it back in and start homeseer.
    Another thing I have seen is that there are many association done to this node that cannot be removed. It says that they are removed if click on Remove button. But if you go in again after they are still there. The only association that can be removed is to Homeseer itself.

    Group 3
    HomeSeer (ID: 1, Endpoint=1) Remove the association.
    HomeSeer (ID: 1, Endpoint=2) Remove the association.
    HomeSeer (ID: 1, Endpoint=3) Remove the association.
    HomeSeer (ID: 1, Endpoint=4) Remove the association.
    HomeSeer (ID: 1, Endpoint=5) Remove the association.
    HomeSeer (ID: 1, Endpoint=6) Remove the association.
    HomeSeer (ID: 1, Endpoint=7) Remove the association.


    Current Date/Time: 2019-05-01 09:07:57
    HomeSeer Version: HS3 Pro Edition 3.0.0.531
    Operating System: Microsoft Windows 10 Enterprise - Work Station
    System Uptime: 0 Days 0 Hours 47 Minutes 44 Seconds
    IP Address: 192.168.1.135
    Number of Devices: 559
    Number of Events: 272
    Available Threads: 400
    HSTouch Enabled: True
    Event Threads: 0
    Event Trigger Eval Queue: 0
    Event Trigger Priority Eval Queue: 0
    Device Exec Queue: 0
    HSTouch Event Queue: 0
    Email Send Queue: 0
    Anti Virus Installed: Windows Defender
    In Virtual Machine: No MFG: micro-star international co., ltd
    Enabled Plug-Ins
    1.0.0.131: Arduino Plugin
    2.0.27.0: BLRing
    4.8.0.0: BULLET
    0.0.0.26: drhsIpPlugIn
    3.0.1.13: Kodi
    30.0.0.38: RFXCOM
    3.1.0.28: Sonos
    3.0.6551.16959: UltraGCIR3
    3.0.6554.33094: UltraMon3
    3.0.1.252: Z-Wave

    Leave a comment:


  • Kernal69
    started a topic Strange behavior with Steinel 140-2 and Homesser

    Strange behavior with Steinel 140-2 and Homesser

    I bought a Steinel IS 140-2 outdoor motion sensor.
    It works well to a greater extent but it has a little strange behavior that I do not understand.
    I run it together with Homeseer and I have added the device and I get in motion and I can control the lamp.
    But if I set the light sensitivity on the device either via the steering wheel or via parameter to something other than the lightest, then the problems begin.
    For example, if I put the light sensitivity on some dark lux, then suddenly it is not possible to control the unit and the z-wave controller in the PC stops working.
    Homeseer says in the log "Only one system can connect to an Ethernet interface at one time. If 2 systems are connecting to your Z-Wave interface, HomeSee will not connect"
    And nothing else works on z-wave.
    But if I turn the light sensitivity back to the max again, everything works as it should again.
    It doesn't matter if I put the device to be a slave only.
    For me, this feels like the unit starts some type of controls and this crashes with the z-wave controller in the PC.
    Someone else who has been through something similar or has an explanation?
Working...
X