• 10 dec 2017: forum version update. In case of issues use this topic.
  • 30 nov 2017: pilight moved servers. In case of issues use this topic.
Hello There, Guest! Login Register


[Fully Supported] Kaku Door sensor (AMST-606)
#31
I just bought the AMST-606 and experienced the same problems.
In pilight 3 it's working but in pilight 5 it isn't.
I switched to wo-rasp his version and that works, when is this going to be implemented in the master version?
 
Reply
#32
Yes, wo-rasp is currently reviewing my merges of his improvements.

Merged.
 
Reply
#33
Saw you pushed to development.. I just switched to development and can confirm it works now.
 
Reply
#34
Great Smile
 
Reply
#35
Tested with:
pilight-daemon version 5.0, commit v5.0-38-g1a859cb
Works with the Test data.
On the WEB GUI the status is not reported as OPEN/CLOSED but ON/OFF
 
Reply
#36
Hmm, can you maybe fix that with a nice pull request (in a separate branch and such) Wink
 
Reply
#37
Yes.
Should not be a Showstopper for the time being, as it affects the GUI presentation only.
 
Reply
#38
I'm trying to add a HomeEasy magnet switch which is compatible with Homewizard.
The type is HE852-HW, almost the same as Elro HE852.
In other topics I read that the HE852 doesn't appear in the web gui and that is what happens to me Smile
Tis is how my device looks:
Code:
"contact": {
                        "protocol": [ "kaku_contact" ],
                        "id": [{
                                "id": 16003,
                                "unit": 1
                        }],
                        "state": "closed"
                },

and here is the gui part:
Code:
"contact": {
                        "name": "Contact",
                        "group": [ "Living" ],
                        "media": [ "web" ],
                        "readonly": 1
                },

How can I get it visible?
 
Reply
#39
Not, you can use it in your rules.
 
Reply
#40
I'm having an issue with this sensor/protocol.
When the sensor is triggered the signal is successfully received by pilight.
But when I trigger a rule with it, the sent signals (from pilight) are not always (rarely) received by the lamp-receivers.
If I add a 3 second delay (with the timer protocol) the signals are received correctly.

My best bet is that the sensor is still sending out signals which interfere with pilights signals.
Are other people having this issue?

If yes, maybe there should be a default (configurable) delay in the protocol.
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  gs-iwds07 window sensor Loggisch 48 13,409 12-09-2019, 07:14 PM
Last Post: curlymo
  Digoo / Baldr / Nexus / Rubicson temperature/humidity sensor thielj 4 1,477 09-30-2019, 04:48 PM
Last Post: curlymo
  433MHz PIR sensor from Amazon ha_username 0 135 09-29-2019, 11:44 PM
Last Post: ha_username
  [Partially Supported] TFA / Conrad Weather Yves 184 12,731 03-31-2019, 05:22 PM
Last Post: curlymo
  [Fully Supported] DHT22 IcedEarth 86 32,218 11-18-2018, 09:33 AM
Last Post: curlymo
  Pearl weatherstation sensor for FWS-686 & FWS-665 chklump 13 4,872 08-12-2018, 05:34 PM
Last Post: fourty2
  TFA 30.3160 Pool Sensor wseifert 4 959 05-30-2018, 09:24 AM
Last Post: wseifert
  [Fully Supported] Arctech Old Martin 111 36,129 03-27-2018, 04:43 PM
Last Post: genfersee
Lightbulb BH1750 i2c digital illuminance sensor marcm 14 3,787 02-25-2018, 08:40 PM
Last Post: morph027
  [Fully Supported] Clarus Switches Marcin 69 25,054 01-30-2018, 07:10 PM
Last Post: Niek

Forum Jump:


Browsing: 1 Guest(s)