Interesting. I played around a little bit with wireshark yesterday and the only thing I saw coming from my gateway was mdns.
I saw a lot of talk about multicast and IGMP on the HA forums. I have a somewhat more advanced setup than most probably have, pfSense router, Powerconnect 5324 switch, Unifi AP. Neither the switch nor AP should be blocking multicast from what I could tell, and the traffic should never be hitting the router.
Mine reports the port is closed also. At least I can stop going crazy now. Unfortunately this puts us at the mercy of waiting for a new firmware update. Or hoping someone can find a way to force it to enable. I haven’t found any info on downgrading the gateway firmware.
It looks like some over at HA have had luck getting it working after resetting the gateway. Not sure what’s changed since I’m sure we’ve all tried that several times over the last couple days, but fingers crossed.
Edit: I reset my gateway, reconnected to wifi, and turned developer mode back on and everything is working great now.
# nmap -sU -p 9898 192.168.0.22
Starting Nmap 7.01 ( https://nmap.org ) at 2017-08-30 01:49 CEST
Nmap scan report for 192.168.0.22
Host is up (0.0051s latency).
PORT STATE SERVICE
9898/udp open unknown
MAC Address: 34:CE:00:FA:5A:CF (Unknown)
Nmap done: 1 IP address (1 host up) scanned in 0.53 seconds
The issue is now fixed, without any firmware or Mi Home app update.
my gateway just arrived and it too refused to be found until i reset the gateway (hold down the gateway button for ~10s or so )..
After this it was discovered and i was able to add all the things.
Reliability was my main concern also when considering the Xiaomi sensors. I’ve only had mine for about a week, but so far they are working well. Hardest part is finding a position for the motion sensor to reliably trigger yet not have the cat constantly triggering it.
I have a motion sensor controlling my under cabinet lights and a couple of the round switches for bedroom lamps/lights (single/double click control respective lamps, long press controls main Wemo light). I installed one of my door sensors today and my testing shows it working well too. When arriving home and front door opens, lights turn on 20%. Just need to get Astro configured correctly so I can trigger them only when dark.
As a side note, persistence doesn’t seem to work for setting the motion timer. My thing shows the configured timeout after a reboot, but the behavior seems to revert to the default 120? seconds. Adding a startup rule to send the value to the item seems to fix it.
You probably mean the Aqara air conditioner hub? I have the normal one (https://www.gearbest.com/living-appliances/pp_344667.html). Don’t know if anyone has the Aqara version.
Regarding the 2 motion sensors. The Aqara version is the latest and van also report lux value. I have them both and they’re working great. At the moment I have almost all sensors which are available and they’re all performing great. Time will tell how long the batteries will last.
Hello,
is there somewhere a documentation about ACTIONS for smart plug ?
For example:
rule “Xiaomi Switch”
when
Channel “mihome:sensor_switch:iD:button” triggered
then
var actionName = receivedEvent.getEvent()
switch(actionName) {
case “SHORT_PRESSED”: {
ACTION
}
Also, it is possible to set days and time for triggers of occupancy sensor and smart plugs ?
rule “Xiaomi Cube”
when
Channel ‘mihome:sensor_cube::action’ triggered
then
var actionName = receivedEvent.getEvent()
switch(actionName) {
case “TAP_TWICE”: {
ACTION
}
}
end
I know the rules, what I mean is I never get it triggered,
that’s why I ask how to get it triggered.
I have tried tap or knock twice on cube with difference speed but never get it work
And now nmap returns :
