Domoticz

corbin wrote:Is anyone using the "no_motion" updates? I could just ignore any messages that are not the 2 minute of no motion update:

Code: Select all

"data":"{\"no_motion\":\"120\"}"}

only other way I can think of to ensure "off" for the PIR is only sent once is to query the database for the current state each time a "no_motion" message is received.

Hi

this probleme isn't related to the PIR probleme that i contact you by PM, that another one, yeap it looks like the same, probleme : heartbeat change device status even if this is the same as previous one.

THere is a small difference between Update device status and change device status :
Update device status : update database but isn't use by event system to trigger blocky, lua, groupe or scene
Change device status : update device status on database an is used by event system to trigger blocky or Lua or Groupe or scene

I hoep this help you to understand the probleme.

I already understand the problem, thought about it when implementing the heartbeat and also the multiple no_motion messages from firmware update. You will see my change on github is ready to test.

EDIT, actually reading your response, I'm not sure I do understand what you mean. Will see how you go with testing it.

corbin wrote:
EDIT, actually reading your response, I'm not sure I do understand what you mean. Will see how you go with testing it.

With your last commit that all right motion sensor isn't updated to each heartbeat !! that perfect !

Now you have to do the same for all device (Cube, switch, wired and wireless, door) thanks for your work

corbin wrote:Is anyone using the "no_motion" updates? I could just ignore any messages that are not the 2 minute of no motion update:

Code: Select all

"data":"{\"no_motion\":\"120\"}"}

only other way I can think of to ensure "off" for the PIR is only sent once is to query the database for the current state each time a "no_motion" message is received.

Yes, would like that. I now use a vir switch for that, that is only set by the pir on and off, not the heartbeat. Your suggestion would eliminate the need for that so I can use the last update from the PiR itself

Prompt, whether the timer in Blockly (domoticz) to switch colors on xiaomi gateway?
Turn, turn off the turns and manage the colors do not have ... (

Sorry for my english )

Hello everyone,
I’ve been following this thread for some time now, and found it very interesting. I currently have many xiaomi devices: 1 gateway, 4 temperature sensors, 2 plugs, 1 switch, 1 cube, 1 presence sensor, 3 light bulbs and 2 door sensors. Although using another software platform would be so much better than the Mi home app in order to do the monitoring, automations and so on, my interest right now is to find a way of downloading the historic data. That means, I would like to have access to the historic data of temperature, door opening logs, presence etc. directly from the xiaomi gateway or servers, without needing a software on a computer or raspberry measuring all the time.
I know the information must be stored in someplace, so I’ve tried wireshark in order to find the information exchange between the gateway and the internet, the mobile phone connected to the wifi while retrieving the historic data etc., but so far I have not been able to access the historic information. I have managed to locate the heartbeats and some measurements, but not the history log. There must be a way, since the information has to reach the app when it shows the monthly temperature profile for example.
Any help would be so much appreciated!

Try decompiling the app and see how that it accesses the historic data: http://www.apkmirror.com/apk/xiaomi-inc ... -download/

But, why not just use Domoticz? you then have easy access to the historic data rather than relying on Xiaomi.

Hi

Don't know if this happens the same way to others, but I still get the door sensor open once in a while without the door is really open (sorry for my english!!!)

Now it happens exactly every hour.
I've tried to set the Xiaomi Gateway Data Timeout from Disabled to 30mins, but nothing changes.

Any suggestion?
Any suggestion on why it happens exactly every hour?

woody4165 wrote:Hi

Don't know if this happens the same way to others, but I still get the door sensor open once in a while without the door is really open (sorry for my english!!!)

Now it happens exactly every hour.
I've tried to set the Xiaomi Gateway Data Timeout from Disabled to 30mins, but nothing changes.

Any suggestion?
Any suggestion on why it happens exactly every hour?

Which FW did you have on your gateway ?

I'm with 1.4.1_143.0141 FW and i don't have this issue and Domoticz : Version: 3.6807

There is my log : 01:xx event is to get the cat out...

Hi deennoo

the gtw fw should be the same

Domoticz is on 3.6808

Here is the log with some time marked.


Strange thing is that some are On and some are Off.

PS: Just got another one while I'm writing, this time On.

Hi corbin, after update to v 3.6815, not working scripts (lua) for xiaomi wireless switch.

Spoiler: show

Code: Select all

2017-03-02 16:01:44.119 XiaomiGateway: not updating Domoticz for switch as no change from last state
2017-03-02 16:01:44.119 {"cmd":"report","model":"switch","sid":"158d000104efc8","short_id":23426,"data":"{\"status\":\"click\"}"}
2017-03-02 16:01:47.600 XiaomiGateway: not updating Domoticz for switch as no change from last state
2017-03-02 16:01:47.600 {"cmd":"report","model":"switch","sid":"158d000104efc8","short_id":23426,"data":"{\"status\":\"double_click\"}"}
2017-03-02 16:01:52.516 XiaomiGateway: not updating Domoticz for switch as no change from last state
2017-03-02 16:01:52.516 {"cmd":"report","model":"switch","sid":"158d000104efc8","short_id":23426,"data":"{\"status\":\"long_click_press\"}"}
2017-03-02 16:01:53.028 XiaomiGateway: not updating Domoticz for switch as no change from last state
2017-03-02 16:01:53.028 {"cmd":"report","model":"switch","sid":"158d000104efc8","short_id":23426,"data":"{\"status\":\"long_click_release\"}"}
2017-03-02 16:01:57.124 XiaomiGateway: not updating Domoticz for switch as no change from last state
2017-03-02 16:01:57.124 {"cmd":"report","model":"switch","sid":"158d000104efc8","short_id":23426,"data":"{\"status\":\"double_click\"}"}

In the domoticz gui all ok

woody4165 wrote:Hi

Don't know if this happens the same way to others, but I still get the door sensor open once in a while without the door is really open (sorry for my english!!!)

Now it happens exactly every hour.
I've tried to set the Xiaomi Gateway Data Timeout from Disabled to 30mins, but nothing changes.

Any suggestion?
Any suggestion on why it happens exactly every hour?

This problem came to me from version 3.6800

@hekm77, If you are compiling from my repo, try updating again.

For the false door sensor readings, please post the log output from the same time, might shed some light on what is triggering it.

corbin wrote:@hekm77, If you are compiling from my repo, try updating again.
For the false door sensor readings, please post the log output from the same time, might shed some light on what is triggering it.

Thank you. Now they are working. With the door sensor is also no problem

Regarding the false door sensor readings, starting with the new update, 3.6833, it seems that I don't get false notification.
I'll wait one or two days to get more data...

What about you @haholukr ?

@woody4165, unless you are compiling my repo, nothing should be different with Domoticz? I did have a pull request in that was soon cancelled due to other issues.

corbin wrote:Is anyone using the "no_motion" updates? I could just ignore any messages that are not the 2 minute of no motion update:

Code: Select all

"data":"{\"no_motion\":\"120\"}"}

only other way I can think of to ensure "off" for the PIR is only sent once is to query the database for the current state each time a "no_motion" message is received.

Not using it.. I find time based lua scripts, with device last change values much more efficient and powerfull then sticking with 120 seconds only..
If you want different value, this message is useless anyway IMHO..



Sent from my SM-N920G using Tapatalk

hekm77 wrote:Hi corbin, after update to v 3.6815, not working scripts (lua) for xiaomi wireless switch.

Spoiler: show

Code: Select all

2017-03-02 16:01:44.119 XiaomiGateway: not updating Domoticz for switch as no change from last state
2017-03-02 16:01:44.119 {"cmd":"report","model":"switch","sid":"158d000104efc8","short_id":23426,"data":"{\"status\":\"click\"}"}
2017-03-02 16:01:47.600 XiaomiGateway: not updating Domoticz for switch as no change from last state
2017-03-02 16:01:47.600 {"cmd":"report","model":"switch","sid":"158d000104efc8","short_id":23426,"data":"{\"status\":\"double_click\"}"}
2017-03-02 16:01:52.516 XiaomiGateway: not updating Domoticz for switch as no change from last state
2017-03-02 16:01:52.516 {"cmd":"report","model":"switch","sid":"158d000104efc8","short_id":23426,"data":"{\"status\":\"long_click_press\"}"}
2017-03-02 16:01:53.028 XiaomiGateway: not updating Domoticz for switch as no change from last state
2017-03-02 16:01:53.028 {"cmd":"report","model":"switch","sid":"158d000104efc8","short_id":23426,"data":"{\"status\":\"long_click_release\"}"}
2017-03-02 16:01:57.124 XiaomiGateway: not updating Domoticz for switch as no change from last state
2017-03-02 16:01:57.124 {"cmd":"report","model":"switch","sid":"158d000104efc8","short_id":23426,"data":"{\"status\":\"double_click\"}"}

In the domoticz gui all ok

As this a beta, you have take some time.

Corbin is trying to solve a issue about event trigger when heartbeat says Off even if device is already Off.
Your probleme now is that you switch send clik but as this already a previous state this can't be changed.
set an auto off time on edit panel (1seconde is good), and click to another state, and this will work

deennoo wrote:set an auto off time on edit panel (1seconde is good), and click to another state, and this will work

Thanks.

corbin wrote:@woody4165, unless you are compiling my repo, nothing should be different with Domoticz? I did have a pull request in that was soon cancelled due to other issues.

That's weird! Just updating official beta... From this morning it's working fine, no false notification and notification when door is open.