Madgeni,
Thanks, seems I fixed issue on my side with ECONNRESET.

Hi Madgeni,

I got error on add "Controlicz" app in google home app (ghome mini).
Subscribed on monthly for testing.
Also another issue - ECONNRESET on "Devices" page, sometimes is ok after refresh.

@RichardBokker did you installed python3-pip with sudo? "sudo apt-get install python3-pip" If yes, pip3 cmd should be available 100% :) Then, cd xiaomi-mirobot # plugin folder virtualenv -p python3 .env # creating environment for python libs source .env/bin/activate # activating environment, only ...

@chrispazz

I'm on 3.8805 - my setup works perfect.
Many people have problems with the python plugin system on latest beta...

Hi,

You can use python-miio lib for IR and other devices which supported... Also you can modify this plugin for support IR.
I have an idea to do plugin which will support all devices which supports python-miio, but for this need to have all this devices for testing.

@Noka
Folder structure looks good.
Which version domoticz? Plugin for 8.153+. Also, maybe you has compiled domoticz without python support? I mean python was not installed when you compiled domoticz? Also need to restart domoticz after plugin installation.

@schulpr You can rename created devices as you want, plugin does not relying on name. First log was immediately after the reboot and log did not grow anymore and "sudo service ble_scanner status" is "active (running)"? Check what you not run 2 services on the one machine, or some other process maybe ...

Go to the plugin folder "bt-presence", then "git pull" Then "nano ble_scanner.sh" and uncomment lines + check path to log file: DAEMON_ARGS="$DAEMON_ARGS --log /home/pi/domoticz/plugins/bt-presence/ble_scanner.log" DAEMON_ARGS="$DAEMON_ARGS --loglevel debug"

@Noka

Did you add hardware with name 'Xiaomi Mi Robot Vacuum' in domoticz? If you did it - check the devices menu, all devices should be created anyway, with test or without. If test goed fine the plugin would works fine:)

@schulpr

Logging in file added. Just git pull updates and uncomment lines in ble_scanner.sh

In logs I see several attempts to startup and seems like hci0 was not ready. In the domoticz log I see a lot of lines with: Calling message handler 'onHeartbeat'. in Debug plugin mode this is ok. Plugin checks timeout expiration on each heartbeat. I will add debug logging in file as option for ble ...

Can you see which status when service not started:
sudo service ble_scanner status

Also then try to run "hciconfig" without "sudo" and check string "RUNNING" in output.

I tested on 2 dev machine the same set of plugins,
first with Ubuntu 16.04 with latest apt-get upgrades and latest beta - sometimes crashes
second with Ubuntu 16.04 without apt-get upgrades and latest beta - without crash for 4 days

@schulpr

ble_scanner.sh added as service?
If yes, try to update locally this line in ble_scanner.py to 10+ attempts.
https://github.com/mrin/domoticz-bt-pre ... er.py#L177
By default ~ 25sec (5 attempts * 5sec sleep) for check hci is RUNNING.

Python plugin for Beacon detection with multi-scanners:
viewtopic.php?f=65&t=20577

Maybe related: https://github.com/domoticz/domoticz/issues/1891

Seems there is only 1 way to support stable domoticz -> change connection type to TCP/IP for plugin and ble_scanner. UDP used as more easy way without any connections/reconnections etc...

@EddyG Check the old version of manual for plugin framework: https://www.domoticz.com/wiki/index.php?title=Developing_a_Python_plugin&oldid=9058 udpConn.Connect() is not right way, plugin should just listen incoming UDP packates. You cannot connect to udp:) this is not tcp/ip. Also check the ...

@EddyG

Checked today with 3.8153

'UDP/IP', 127.0.0.1:2221

The same on stable release.

Also added small fix for support old api domoticz plugin frameworj of stable release.

Plugin update 0.1.0

Whats new:
* Manage interface status (status and manage in realtime)
* new core lib for communication with mikrotik for work in non-blocking mode (uses native domoticz framework connection)