Domoticz

https://github.com/sasu-drooz/Domoticz- ... issues/295

I erased persistent data and deleted the Zigate from the hardware tab so that I would start again fresh and capture the logs from the beginning.

After joining the Xiaomi temp sensor, it was working for about 15 minutes. Then I restarted the domoticz process and the values didn't update any more.

Is there anything in particular to search for in the logs or do I need to post the whole log file?

Here are the steps I followed:

• erase persistent data and "Update" button
  click the zigate and "Delete" button
  shutdown domoticz
  start domoticz from command line with logging enabled
  add the Zigate again, with join time = 255
  press and hold the button on my 3A smart socket (issue #294 ) and it joined
  tested turning the 3A smart socket and and off a couple of times from the web browser
  stopped domoticz
  started domoticz again
  tried to use the browser to control the smart socket, it says it is turning off but it doesn't work
  joined the Xiaomi temperature sensor
  left it running for 15 minutes, noticed it was updating the temperature regularly
  stopped domoticz
  started domoticz
  waited another 10 minutes, no temperature updates from the temp sensor and I still can't control the socket either

What do you mean by shutdown domoticz ? Do you mean you powered Off or it is only the domotciz service which has been stop ?

The question is mainly related to the Zigate in terms of did you Powered off Zigate ? There are on the zigate github some current discussion on losing Xiaomi devices after a power off .

Could you also let us know what is in the log, any activities ?

pipiche wrote: ↑Sunday 16 December 2018 13:37 What do you mean by shutdown domoticz ? Do you mean you powered Off or it is only the domotciz service which has been stop ?

I was running the process in the terminal and I killed it with Ctrl-C, waiting for it to shut down, e.g.

su -s /bin/bash domoticz
cd /usr/lib/domoticz
/usr/lib/domoticz/domoticz ....... (start process)
Ctrl-C

pipiche wrote: ↑Sunday 16 December 2018 13:37 The question is mainly related to the Zigate in terms of did you Powered off Zigate ? There are on the zigate github some current discussion on losing Xiaomi devices after a power off

No, I didn't power off the Zigate when doing those tests. I do power it off overnight usually, I am running it on my desk for testing during the daytime.

pipiche wrote: ↑Sunday 16 December 2018 13:37 Could you also let us know what is in the log, any activities ?

I attached the log when I made the first post in this topic but the attachment doesn't appear to be visible, is there an issue with the forum? I've attached it again below. When I attach it, I notice an exclamation mark appears under the "Status" heading but there is no message about what that means.

I put the logs into the Github issue:

https://github.com/sasu-drooz/Domoticz- ... moticz.log
https://github.com/sasu-drooz/Domoticz- ... stderr.log

as described in the Github issue, it looks like this was caused by the process trying to write to the directory where code is located (/usr/lib/domoticz/plugins/Domoticz-Zigate) which is read-only for the domoticz user, need to write the files elsewhere

@pocock a beta has been pushed on the zigate plugin github. This beta includes the possibility to customize the various folders.
Check: https://github.com/sasu-drooz/Domoticz- ... PluginConf

Hello,

I have the same issue as you had.

I did the git pull and I am in the beta branch.

Do I need to configure the PluginConf File? I do not really understand the parameters of that file...

Thank you in advance,
Jens

Here is where you can find information on the PluginConf

https://github.com/sasu-drooz/Domoticz- ... PluginConf

If you don't understand those parameters, please let us know where is the issue

Thank you for the quick answer.

currently, the PluginConf.txt contains:

{
'CrcCheck':'On'
}

Do I need to add the following text from the wiki?

{ 'allowStoreDiscoveryFrames':'0', 'logFORMAT':'0', 'logLQI':'0', 'allowRemoveZigateDevice':'0', 'allowForceCreationDomoDevice':'0', 'networkScan':'0', 'channel':'0' }

Does this help? Sorry for bothering..


edit: I am running domoticz on a raspberry pi, the domoticz script folder is under /home/pi/domoticz/plugins/Domoticz-Zigate/


edit2: apparently I am still on the stable branch. I will try to update to the beta branch.

edit3: Now it says:

{
'channel':'11,15,16,21,22',
'self.eraseZigatePDM':'0',
'vibrationAqarasensitivity':'medium',
'resetMotiondelay':'30',
'enablegroupmanagement':'0',
'allowRemoveZigateDevice':'0',
'allowStoreDiscoveryFrames':'0',
'logLQI':'0',
'logFORMAT':'0'
}

Is the issue solved right now?

Hello,

what is in the PluginConf.txt correspond to the default value parameters.

Could you clarify what your problem is ?

I'm also sceptical on the initial pluginconf.txt and I suspect that you were on the old version of the plugin . Didn't you have in the Log a message requesting you to upgrade ?

Ok:

I had the problem of the not communication xiaomi-devices.

I thought I was on the beta branch, but I was on stable. So now I updated to the beta. In order to make a clean install, and since I have not a lot of devices, I also resettet my network.

My question now is, if the problem of non-communication is solved with the default values and files in the beta branch, or if I have to change any settings in the config files

You can stay with the default values, it should work and it works on various end users .

As the lost of Xiaomi devices, it was more related to the version 3.0e of the Zigate firmware which was loosing Xiaomi and non-Xiaomi devices when rebooting the system or powering-off/on. There is a pre-3.0f which fix that issue.

You can either stay on stable 4.0.7 or beta (which is becoming mature).

Thank you very much for your response!

Official release 3.0f is available ....