PlayBlub (Bluetooth Bulb) Python Plugin - Beta tester Wanted

Topics (not sure which fora)
when not sure where to post, post here and mods will move it to right forum.

Moderators: leecollings, remb0

deennoo
Posts: 784
Joined: Wednesday 10 December 2014 13:06
Target OS: Linux
Domoticz version: beta
Location: Bordeaux France
Contact:

PlayBlub (Bluetooth Bulb) Python Plugin - Beta tester Wanted

Post by deennoo »

Hi Geeks !

A new plugin is ready to born, this is a Python Plugin who drive Bluetooth Bulb from Mipow / Playbulb : http://www.playbulb.com/en/index.html

This plugin allow to drive all feature of the bulb, and get new bulb state if bulb status is change on andoid/ios app, this plugin is able to know if your bulb is on charge or not and batterie level for autonome devices.

New need now beta tester for it !

Plugin drive :

- Garden (fw : BTL400M_1.9)
- Candle (fw : BTL300_v5 et 6)
- Rainbow (fw: BTL300_V5)
- Color (fw : BTL100c_v6)
- Comet
- Smart
- Sphere

FW version can be found on Playbulb X app under config when your are connecetd to the bulb.

needed for test :
Domoticz on linux
BTLE dongle or rpi3
Knowing how install python3 for domoticz
Knowing how to install dep

i'm on the way to made the wiki for it, until this done, beta have to be "autonome".

Please send me a MP to apply.

Don't ask for other bulb here or other feature this is not the place, this plugin will be well documented, and give all tools to made other btle plugin for other device.

Howto is available here : http://www.domoticz.com/wiki/Plugins/PlayBulb
Last edited by deennoo on Sunday 26 March 2017 13:42, edited 1 time in total.
Domoticz stable 3.5877 for real & Domoticz beta for test
Rfxtrxe / RFLink / Milight / Yeelight / Tasmota / MQTT / BLE / Zigate
http://domo-attitude.fr
User avatar
Exe64
Posts: 2
Joined: Friday 31 March 2017 15:34
Target OS: Raspberry Pi / ODroid
Domoticz version: v3.5877
Location: Paris, France
Contact:

Re: PlayBlub (Bluetooth Bulb) Python Plugin - Beta tester Wanted

Post by Exe64 »

Hi !

Just registered on Domoticz and can't send you PM at this moment (it's seems there are some restrictions before being able to do it...).

I'm ok for the beta test. I've tried to install your plugin following the wiki how-to but i'm not able to find Mipow on the HardwareAdd page.

PlayBulb Comet Lightstrip
Raspberry Pi 3 with Raspbian
Domoticz v3.5877

(I'm french, not used to write in english ^^')
Domoticz on RaspberryPi3 with Raspbian
Blogger on https://www.geek-chronicles.com
deennoo
Posts: 784
Joined: Wednesday 10 December 2014 13:06
Target OS: Linux
Domoticz version: beta
Location: Bordeaux France
Contact:

Re: PlayBlub (Bluetooth Bulb) Python Plugin - Beta tester Wanted

Post by deennoo »

Hi mec

You need to use beta version for test it.

Which bulb Did you have ?
Domoticz stable 3.5877 for real & Domoticz beta for test
Rfxtrxe / RFLink / Milight / Yeelight / Tasmota / MQTT / BLE / Zigate
http://domo-attitude.fr
User avatar
Exe64
Posts: 2
Joined: Friday 31 March 2017 15:34
Target OS: Raspberry Pi / ODroid
Domoticz version: v3.5877
Location: Paris, France
Contact:

Re: PlayBlub (Bluetooth Bulb) Python Plugin - Beta tester Wanted

Post by Exe64 »

Hi,

I have a PlayBulb Comet.

I just upgrade my Domoticz install to v3.7212 (I'm currently testing Domoticz, nothing in production yet) and try to follow your HowTo but Mipow doesn't appear on the dropdown menu.

An idea ?
Domoticz on RaspberryPi3 with Raspbian
Blogger on https://www.geek-chronicles.com
User avatar
Mediacj
Posts: 74
Joined: Wednesday 11 February 2015 16:09
Target OS: Raspberry Pi / ODroid
Domoticz version:
Location: Netherlands
Contact:

Re: PlayBlub (Bluetooth Bulb) Python Plugin - Beta tester Wanted

Post by Mediacj »

I'am impressed how complete your plugin is! It is really nice! Thx!
I have installed it but I can't get it to work, this is what I get in the log:

Code: Select all

2017-04-03 18:35:35.572 (Playbulb 1) Exiting work loop...
2017-04-03 18:35:35.654 (Playbulb 1) Stopped.
2017-04-03 18:35:36.488 (Playbulb 1) Initialized version 1.0.1, author 'zaraki673'
2017-04-03 18:35:36.553 (Playbulb 1) Debug log level set to: 'true'.
2017-04-03 18:35:36.588 (Playbulb 1) 'Mode1':'1'
2017-04-03 18:35:36.588 (Playbulb 1) 'HomeFolder':'/home/pi/domoticz/plugins/mipow/'
2017-04-03 18:35:36.588 (Playbulb 1) 'Address':'ED:C6:4B:11:AC:E6'
2017-04-03 18:35:36.588 (Playbulb 1) 'Mode3':'0'
2017-04-03 18:35:36.588 (Playbulb 1) 'Port':'0'
2017-04-03 18:35:36.588 (Playbulb 1) 'Version':'1.0.1'
2017-04-03 18:35:36.589 (Playbulb 1) 'Name':'Playbulb 1'
2017-04-03 18:35:36.589 (Playbulb 1) 'HardwareID':'6'
2017-04-03 18:35:36.589 (Playbulb 1) 'Key':'MiPow'
2017-04-03 18:35:36.589 (Playbulb 1) 'Mode2':'0'
2017-04-03 18:35:36.589 (Playbulb 1) 'Mode6':'Debug'
2017-04-03 18:35:36.589 (Playbulb 1) 'Author':'zaraki673'
2017-04-03 18:35:36.589 (Playbulb 1) Device count: 8
2017-04-03 18:35:36.590 (Playbulb 1) Device:	1 - ID: 55, Name: 'Playbulb 1 - Status', nValue: 0, sValue: ''
2017-04-03 18:35:36.590 (Playbulb 1) Device ID:	'55'
2017-04-03 18:35:36.590 (Playbulb 1) Device Name:	'Playbulb 1 - Status'
2017-04-03 18:35:36.590 (Playbulb 1) Device nValue:	0
2017-04-03 18:35:36.590 (Playbulb 1) Device sValue: ''
2017-04-03 18:35:36.590 (Playbulb 1) Device LastLevel: 0
2017-04-03 18:35:36.590 (Playbulb 1) Device:	2 - ID: 56, Name: 'Playbulb 1 - Effect', nValue: 1, sValue: '20'
2017-04-03 18:35:36.591 (Playbulb 1) Device ID:	'56'
2017-04-03 18:35:36.591 (Playbulb 1) Device Name:	'Playbulb 1 - Effect'
2017-04-03 18:35:36.591 (Playbulb 1) Device nValue:	1
2017-04-03 18:35:36.591 (Playbulb 1) Device sValue: '20'
2017-04-03 18:35:36.591 (Playbulb 1) Device LastLevel: 20
2017-04-03 18:35:36.591 (Playbulb 1) Device:	3 - ID: 57, Name: 'Playbulb 1 - Red', nValue: 0, sValue: ''
2017-04-03 18:35:36.591 (Playbulb 1) Device ID:	'57'
2017-04-03 18:35:36.591 (Playbulb 1) Device Name:	'Playbulb 1 - Red'
2017-04-03 18:35:36.592 (Playbulb 1) Device nValue:	0
2017-04-03 18:35:36.592 (Playbulb 1) Device sValue: ''
2017-04-03 18:35:36.592 (Playbulb 1) Device LastLevel: 0
2017-04-03 18:35:36.592 (Playbulb 1) Device:	4 - ID: 58, Name: 'Playbulb 1 - Green', nValue: 0, sValue: ''
2017-04-03 18:35:36.592 (Playbulb 1) Device ID:	'58'
2017-04-03 18:35:36.592 (Playbulb 1) Device Name:	'Playbulb 1 - Green'
2017-04-03 18:35:36.592 (Playbulb 1) Device nValue:	0
2017-04-03 18:35:36.592 (Playbulb 1) Device sValue: ''
2017-04-03 18:35:36.593 (Playbulb 1) Device LastLevel: 0
2017-04-03 18:35:36.593 (Playbulb 1) Device:	5 - ID: 59, Name: 'Playbulb 1 - Blue', nValue: 0, sValue: ''
2017-04-03 18:35:36.593 (Playbulb 1) Device ID:	'59'
2017-04-03 18:35:36.593 (Playbulb 1) Device Name:	'Playbulb 1 - Blue'
2017-04-03 18:35:36.593 (Playbulb 1) Device nValue:	0
2017-04-03 18:35:36.593 (Playbulb 1) Device sValue: ''
2017-04-03 18:35:36.593 (Playbulb 1) Device LastLevel: 0
2017-04-03 18:35:36.594 (Playbulb 1) Device:	6 - ID: 60, Name: 'Playbulb 1 - White', nValue: 0, sValue: ''
2017-04-03 18:35:36.594 (Playbulb 1) Device ID:	'60'
2017-04-03 18:35:36.594 (Playbulb 1) Device Name:	'Playbulb 1 - White'
2017-04-03 18:35:36.594 (Playbulb 1) Device nValue:	0
2017-04-03 18:35:36.594 (Playbulb 1) Device sValue: ''
2017-04-03 18:35:36.594 (Playbulb 1) Device LastLevel: 0
2017-04-03 18:35:36.594 (Playbulb 1) Device:	7 - ID: 61, Name: 'Playbulb 1 - Speed', nValue: 0, sValue: ''
2017-04-03 18:35:36.594 (Playbulb 1) Device ID:	'61'
2017-04-03 18:35:36.595 (Playbulb 1) Device Name:	'Playbulb 1 - Speed'
2017-04-03 18:35:36.595 (Playbulb 1) Device nValue:	0
2017-04-03 18:35:36.595 (Playbulb 1) Device sValue: ''
2017-04-03 18:35:36.595 (Playbulb 1) Device LastLevel: 0
2017-04-03 18:35:36.595 (Playbulb 1) Device:	8 - ID: 62, Name: 'Playbulb 1 - Speed', nValue: 0, sValue: ''
2017-04-03 18:35:36.595 (Playbulb 1) Device ID:	'62'
2017-04-03 18:35:36.595 (Playbulb 1) Device Name:	'Playbulb 1 - Speed'
2017-04-03 18:35:36.595 (Playbulb 1) Device nValue:	0
2017-04-03 18:35:36.595 (Playbulb 1) Device sValue: ''
2017-04-03 18:35:36.596 (Playbulb 1) Device LastLevel: 0
2017-04-03 18:35:36.596 (Playbulb 1) Plugin is started.
2017-04-03 18:35:36.596 (Playbulb 1) Heartbeat interval set to: 60.
2017-04-03 18:35:46.016 (Playbulb 1) Calling message handler 'onHeartbeat'.
2017-04-03 18:36:46.023 (Playbulb 1) Calling message handler 'onHeartbeat'.
2017-04-03 18:37:13.276 User: Admin initiated a switch command (55/Playbulb 1 - Status/On)
2017-04-03 18:37:13.321 (Playbulb 1) Calling message handler 'onCommand'.
2017-04-03 18:37:13.321 (Playbulb 1) DEBUG : white before command is set 0
2017-04-03 18:37:13.321 (Playbulb 1) DEBUG : red before command is set 0
2017-04-03 18:37:13.322 (Playbulb 1) DEBUG : green before command is set 0
2017-04-03 18:37:13.322 (Playbulb 1) DEBUG : blue before command is set 0
2017-04-03 18:37:13.322 (Playbulb 1) DEBUG : mode before command is set 0
2017-04-03 18:37:13.322 (Playbulb 1) DEBUG : speed before command is set 0
2017-04-03 18:37:13.322 (Playbulb 1) DEBUG : onCommand called for Unit 1: Parameter 'On', Level: 0
2017-04-03 18:37:13.323 (Playbulb 1) handles send 0x16
2017-04-03 18:37:13.323 (Playbulb 1) Data send bytearray(b'\xff\xff\xff\xff')
2017-04-03 18:37:13.325 (Playbulb 1) handles send 0x16
2017-04-03 18:37:13.325 (Playbulb 1) Data send bytearray(b'\xff\xff\xff\xff')
2017-04-03 18:37:13.476 Error: (Playbulb 1) 'onCommand' failed 'IndexError'.
2017-04-03 18:37:13.477 Error: (Playbulb 1) ----> Line 399 in /home/pi/domoticz/plugins/mipow/plugin.py, function onCommand
2017-04-03 18:37:13.477 Error: (Playbulb 1) ----> Line 353 in /home/pi/domoticz/plugins/mipow/plugin.py, function onCommand
2017-04-03 18:37:13.477 Error: (Playbulb 1) ----> Line 533 in /home/pi/domoticz/plugins/mipow/plugin.py, function CheckStatus
As you can see he can connect and gets a heartbeat but when I swith it on I get a index error.

For your information I had to rename the plugunRGBW.py to plugin.py in the plugins folder before the Mipow/Playbulb appeared in the hardwarelist. Otherwise it didn't appear. On github it is called pluginRGBW.py.
deennoo
Posts: 784
Joined: Wednesday 10 December 2014 13:06
Target OS: Linux
Domoticz version: beta
Location: Bordeaux France
Contact:

Re: RE: Re: PlayBlub (Bluetooth Bulb) Python Plugin - Beta tester Wanted

Post by deennoo »

Exe64 wrote:Hi,

I have a PlayBulb Comet.

I just upgrade my Domoticz install to v3.7212 (I'm currently testing Domoticz, nothing in production yet) and try to follow your HowTo but Mipow doesn't appear on the dropdown menu.

An idea ?
OK which is your Fw ? Have you test all the option ?
Domoticz stable 3.5877 for real & Domoticz beta for test
Rfxtrxe / RFLink / Milight / Yeelight / Tasmota / MQTT / BLE / Zigate
http://domo-attitude.fr
deennoo
Posts: 784
Joined: Wednesday 10 December 2014 13:06
Target OS: Linux
Domoticz version: beta
Location: Bordeaux France
Contact:

Re: RE: Re: PlayBlub (Bluetooth Bulb) Python Plugin - Beta tester Wanted

Post by deennoo »

Mediacj wrote:I'am impressed how complete your plugin is! It is really nice! Thx!
I have installed it but I can't get it to work, this is what I get in the log:

Code: Select all

2017-04-03 18:35:35.572 (Playbulb 1) Exiting work loop...
2017-04-03 18:35:35.654 (Playbulb 1) Stopped.
2017-04-03 18:35:36.488 (Playbulb 1) Initialized version 1.0.1, author 'zaraki673'
2017-04-03 18:35:36.553 (Playbulb 1) Debug log level set to: 'true'.
2017-04-03 18:35:36.588 (Playbulb 1) 'Mode1':'1'
2017-04-03 18:35:36.588 (Playbulb 1) 'HomeFolder':'/home/pi/domoticz/plugins/mipow/'
2017-04-03 18:35:36.588 (Playbulb 1) 'Address':'ED:C6:4B:11:AC:E6'
2017-04-03 18:35:36.588 (Playbulb 1) 'Mode3':'0'
2017-04-03 18:35:36.588 (Playbulb 1) 'Port':'0'
2017-04-03 18:35:36.588 (Playbulb 1) 'Version':'1.0.1'
2017-04-03 18:35:36.589 (Playbulb 1) 'Name':'Playbulb 1'
2017-04-03 18:35:36.589 (Playbulb 1) 'HardwareID':'6'
2017-04-03 18:35:36.589 (Playbulb 1) 'Key':'MiPow'
2017-04-03 18:35:36.589 (Playbulb 1) 'Mode2':'0'
2017-04-03 18:35:36.589 (Playbulb 1) 'Mode6':'Debug'
2017-04-03 18:35:36.589 (Playbulb 1) 'Author':'zaraki673'
2017-04-03 18:35:36.589 (Playbulb 1) Device count: 8
2017-04-03 18:35:36.590 (Playbulb 1) Device:	1 - ID: 55, Name: 'Playbulb 1 - Status', nValue: 0, sValue: ''
2017-04-03 18:35:36.590 (Playbulb 1) Device ID:	'55'
2017-04-03 18:35:36.590 (Playbulb 1) Device Name:	'Playbulb 1 - Status'
2017-04-03 18:35:36.590 (Playbulb 1) Device nValue:	0
2017-04-03 18:35:36.590 (Playbulb 1) Device sValue: ''
2017-04-03 18:35:36.590 (Playbulb 1) Device LastLevel: 0
2017-04-03 18:35:36.590 (Playbulb 1) Device:	2 - ID: 56, Name: 'Playbulb 1 - Effect', nValue: 1, sValue: '20'
2017-04-03 18:35:36.591 (Playbulb 1) Device ID:	'56'
2017-04-03 18:35:36.591 (Playbulb 1) Device Name:	'Playbulb 1 - Effect'
2017-04-03 18:35:36.591 (Playbulb 1) Device nValue:	1
2017-04-03 18:35:36.591 (Playbulb 1) Device sValue: '20'
2017-04-03 18:35:36.591 (Playbulb 1) Device LastLevel: 20
2017-04-03 18:35:36.591 (Playbulb 1) Device:	3 - ID: 57, Name: 'Playbulb 1 - Red', nValue: 0, sValue: ''
2017-04-03 18:35:36.591 (Playbulb 1) Device ID:	'57'
2017-04-03 18:35:36.591 (Playbulb 1) Device Name:	'Playbulb 1 - Red'
2017-04-03 18:35:36.592 (Playbulb 1) Device nValue:	0
2017-04-03 18:35:36.592 (Playbulb 1) Device sValue: ''
2017-04-03 18:35:36.592 (Playbulb 1) Device LastLevel: 0
2017-04-03 18:35:36.592 (Playbulb 1) Device:	4 - ID: 58, Name: 'Playbulb 1 - Green', nValue: 0, sValue: ''
2017-04-03 18:35:36.592 (Playbulb 1) Device ID:	'58'
2017-04-03 18:35:36.592 (Playbulb 1) Device Name:	'Playbulb 1 - Green'
2017-04-03 18:35:36.592 (Playbulb 1) Device nValue:	0
2017-04-03 18:35:36.592 (Playbulb 1) Device sValue: ''
2017-04-03 18:35:36.593 (Playbulb 1) Device LastLevel: 0
2017-04-03 18:35:36.593 (Playbulb 1) Device:	5 - ID: 59, Name: 'Playbulb 1 - Blue', nValue: 0, sValue: ''
2017-04-03 18:35:36.593 (Playbulb 1) Device ID:	'59'
2017-04-03 18:35:36.593 (Playbulb 1) Device Name:	'Playbulb 1 - Blue'
2017-04-03 18:35:36.593 (Playbulb 1) Device nValue:	0
2017-04-03 18:35:36.593 (Playbulb 1) Device sValue: ''
2017-04-03 18:35:36.593 (Playbulb 1) Device LastLevel: 0
2017-04-03 18:35:36.594 (Playbulb 1) Device:	6 - ID: 60, Name: 'Playbulb 1 - White', nValue: 0, sValue: ''
2017-04-03 18:35:36.594 (Playbulb 1) Device ID:	'60'
2017-04-03 18:35:36.594 (Playbulb 1) Device Name:	'Playbulb 1 - White'
2017-04-03 18:35:36.594 (Playbulb 1) Device nValue:	0
2017-04-03 18:35:36.594 (Playbulb 1) Device sValue: ''
2017-04-03 18:35:36.594 (Playbulb 1) Device LastLevel: 0
2017-04-03 18:35:36.594 (Playbulb 1) Device:	7 - ID: 61, Name: 'Playbulb 1 - Speed', nValue: 0, sValue: ''
2017-04-03 18:35:36.594 (Playbulb 1) Device ID:	'61'
2017-04-03 18:35:36.595 (Playbulb 1) Device Name:	'Playbulb 1 - Speed'
2017-04-03 18:35:36.595 (Playbulb 1) Device nValue:	0
2017-04-03 18:35:36.595 (Playbulb 1) Device sValue: ''
2017-04-03 18:35:36.595 (Playbulb 1) Device LastLevel: 0
2017-04-03 18:35:36.595 (Playbulb 1) Device:	8 - ID: 62, Name: 'Playbulb 1 - Speed', nValue: 0, sValue: ''
2017-04-03 18:35:36.595 (Playbulb 1) Device ID:	'62'
2017-04-03 18:35:36.595 (Playbulb 1) Device Name:	'Playbulb 1 - Speed'
2017-04-03 18:35:36.595 (Playbulb 1) Device nValue:	0
2017-04-03 18:35:36.595 (Playbulb 1) Device sValue: ''
2017-04-03 18:35:36.596 (Playbulb 1) Device LastLevel: 0
2017-04-03 18:35:36.596 (Playbulb 1) Plugin is started.
2017-04-03 18:35:36.596 (Playbulb 1) Heartbeat interval set to: 60.
2017-04-03 18:35:46.016 (Playbulb 1) Calling message handler 'onHeartbeat'.
2017-04-03 18:36:46.023 (Playbulb 1) Calling message handler 'onHeartbeat'.
2017-04-03 18:37:13.276 User: Admin initiated a switch command (55/Playbulb 1 - Status/On)
2017-04-03 18:37:13.321 (Playbulb 1) Calling message handler 'onCommand'.
2017-04-03 18:37:13.321 (Playbulb 1) DEBUG : white before command is set 0
2017-04-03 18:37:13.321 (Playbulb 1) DEBUG : red before command is set 0
2017-04-03 18:37:13.322 (Playbulb 1) DEBUG : green before command is set 0
2017-04-03 18:37:13.322 (Playbulb 1) DEBUG : blue before command is set 0
2017-04-03 18:37:13.322 (Playbulb 1) DEBUG : mode before command is set 0
2017-04-03 18:37:13.322 (Playbulb 1) DEBUG : speed before command is set 0
2017-04-03 18:37:13.322 (Playbulb 1) DEBUG : onCommand called for Unit 1: Parameter 'On', Level: 0
2017-04-03 18:37:13.323 (Playbulb 1) handles send 0x16
2017-04-03 18:37:13.323 (Playbulb 1) Data send bytearray(b'\xff\xff\xff\xff')
2017-04-03 18:37:13.325 (Playbulb 1) handles send 0x16
2017-04-03 18:37:13.325 (Playbulb 1) Data send bytearray(b'\xff\xff\xff\xff')
2017-04-03 18:37:13.476 Error: (Playbulb 1) 'onCommand' failed 'IndexError'.
2017-04-03 18:37:13.477 Error: (Playbulb 1) ----> Line 399 in /home/pi/domoticz/plugins/mipow/plugin.py, function onCommand
2017-04-03 18:37:13.477 Error: (Playbulb 1) ----> Line 353 in /home/pi/domoticz/plugins/mipow/plugin.py, function onCommand
2017-04-03 18:37:13.477 Error: (Playbulb 1) ----> Line 533 in /home/pi/domoticz/plugins/mipow/plugin.py, function CheckStatus
As you can see he can connect and gets a heartbeat but when I swith it on I get a index error.

For your information I had to rename the plugunRGBW.py to plugin.py in the plugins folder before the Mipow/Playbulb appeared in the hardwarelist. Otherwise it didn't appear. On github it is called pluginRGBW.py.
Domoticz version
Python version
Bulb type
Fw version

Are importants information we need

File name will be change for the good one, thx.
Last edited by deennoo on Monday 03 April 2017 19:01, edited 2 times in total.
Domoticz stable 3.5877 for real & Domoticz beta for test
Rfxtrxe / RFLink / Milight / Yeelight / Tasmota / MQTT / BLE / Zigate
http://domo-attitude.fr
deennoo
Posts: 784
Joined: Wednesday 10 December 2014 13:06
Target OS: Linux
Domoticz version: beta
Location: Bordeaux France
Contact:

Re: RE: Re: PlayBlub (Bluetooth Bulb) Python Plugin - Beta tester Wanted

Post by deennoo »

Exe64 wrote:Hi !

Just registered on Domoticz and can't send you PM at this moment (it's seems there are some restrictions before being able to do it...).

I'm ok for the beta test. I've tried to install your plugin following the wiki how-to but i'm not able to find Mipow on the HardwareAdd page.

PlayBulb Comet Lightstrip
Raspberry Pi 3 with Raspbian
Domoticz v3.5877

(I'm french, not used to write in english ^^')
Have rename the .py file to plugin.py ?
Domoticz stable 3.5877 for real & Domoticz beta for test
Rfxtrxe / RFLink / Milight / Yeelight / Tasmota / MQTT / BLE / Zigate
http://domo-attitude.fr
User avatar
Mediacj
Posts: 74
Joined: Wednesday 11 February 2015 16:09
Target OS: Raspberry Pi / ODroid
Domoticz version:
Location: Netherlands
Contact:

Re: RE: Re: PlayBlub (Bluetooth Bulb) Python Plugin - Beta tester Wanted

Post by Mediacj »

deennoo wrote:
Mediacj wrote:I'am impressed how complete your plugin is! It is really nice! Thx!
I have installed it but I can't get it to work, this is what I get in the log:

Code: Select all

2017-04-03 18:35:35.572 (Playbulb 1) Exiting work loop...
2017-04-03 18:35:35.654 (Playbulb 1) Stopped.
2017-04-03 18:35:36.488 (Playbulb 1) Initialized version 1.0.1, author 'zaraki673'
2017-04-03 18:35:36.553 (Playbulb 1) Debug log level set to: 'true'.
2017-04-03 18:35:36.588 (Playbulb 1) 'Mode1':'1'
2017-04-03 18:35:36.588 (Playbulb 1) 'HomeFolder':'/home/pi/domoticz/plugins/mipow/'
2017-04-03 18:35:36.588 (Playbulb 1) 'Address':'ED:C6:4B:11:AC:E6'
2017-04-03 18:35:36.588 (Playbulb 1) 'Mode3':'0'
2017-04-03 18:35:36.588 (Playbulb 1) 'Port':'0'
2017-04-03 18:35:36.588 (Playbulb 1) 'Version':'1.0.1'
2017-04-03 18:35:36.589 (Playbulb 1) 'Name':'Playbulb 1'
2017-04-03 18:35:36.589 (Playbulb 1) 'HardwareID':'6'
2017-04-03 18:35:36.589 (Playbulb 1) 'Key':'MiPow'
2017-04-03 18:35:36.589 (Playbulb 1) 'Mode2':'0'
2017-04-03 18:35:36.589 (Playbulb 1) 'Mode6':'Debug'
2017-04-03 18:35:36.589 (Playbulb 1) 'Author':'zaraki673'
2017-04-03 18:35:36.589 (Playbulb 1) Device count: 8
2017-04-03 18:35:36.590 (Playbulb 1) Device:	1 - ID: 55, Name: 'Playbulb 1 - Status', nValue: 0, sValue: ''
2017-04-03 18:35:36.590 (Playbulb 1) Device ID:	'55'
2017-04-03 18:35:36.590 (Playbulb 1) Device Name:	'Playbulb 1 - Status'
2017-04-03 18:35:36.590 (Playbulb 1) Device nValue:	0
2017-04-03 18:35:36.590 (Playbulb 1) Device sValue: ''
2017-04-03 18:35:36.590 (Playbulb 1) Device LastLevel: 0
2017-04-03 18:35:36.590 (Playbulb 1) Device:	2 - ID: 56, Name: 'Playbulb 1 - Effect', nValue: 1, sValue: '20'
2017-04-03 18:35:36.591 (Playbulb 1) Device ID:	'56'
2017-04-03 18:35:36.591 (Playbulb 1) Device Name:	'Playbulb 1 - Effect'
2017-04-03 18:35:36.591 (Playbulb 1) Device nValue:	1
2017-04-03 18:35:36.591 (Playbulb 1) Device sValue: '20'
2017-04-03 18:35:36.591 (Playbulb 1) Device LastLevel: 20
2017-04-03 18:35:36.591 (Playbulb 1) Device:	3 - ID: 57, Name: 'Playbulb 1 - Red', nValue: 0, sValue: ''
2017-04-03 18:35:36.591 (Playbulb 1) Device ID:	'57'
2017-04-03 18:35:36.591 (Playbulb 1) Device Name:	'Playbulb 1 - Red'
2017-04-03 18:35:36.592 (Playbulb 1) Device nValue:	0
2017-04-03 18:35:36.592 (Playbulb 1) Device sValue: ''
2017-04-03 18:35:36.592 (Playbulb 1) Device LastLevel: 0
2017-04-03 18:35:36.592 (Playbulb 1) Device:	4 - ID: 58, Name: 'Playbulb 1 - Green', nValue: 0, sValue: ''
2017-04-03 18:35:36.592 (Playbulb 1) Device ID:	'58'
2017-04-03 18:35:36.592 (Playbulb 1) Device Name:	'Playbulb 1 - Green'
2017-04-03 18:35:36.592 (Playbulb 1) Device nValue:	0
2017-04-03 18:35:36.592 (Playbulb 1) Device sValue: ''
2017-04-03 18:35:36.593 (Playbulb 1) Device LastLevel: 0
2017-04-03 18:35:36.593 (Playbulb 1) Device:	5 - ID: 59, Name: 'Playbulb 1 - Blue', nValue: 0, sValue: ''
2017-04-03 18:35:36.593 (Playbulb 1) Device ID:	'59'
2017-04-03 18:35:36.593 (Playbulb 1) Device Name:	'Playbulb 1 - Blue'
2017-04-03 18:35:36.593 (Playbulb 1) Device nValue:	0
2017-04-03 18:35:36.593 (Playbulb 1) Device sValue: ''
2017-04-03 18:35:36.593 (Playbulb 1) Device LastLevel: 0
2017-04-03 18:35:36.594 (Playbulb 1) Device:	6 - ID: 60, Name: 'Playbulb 1 - White', nValue: 0, sValue: ''
2017-04-03 18:35:36.594 (Playbulb 1) Device ID:	'60'
2017-04-03 18:35:36.594 (Playbulb 1) Device Name:	'Playbulb 1 - White'
2017-04-03 18:35:36.594 (Playbulb 1) Device nValue:	0
2017-04-03 18:35:36.594 (Playbulb 1) Device sValue: ''
2017-04-03 18:35:36.594 (Playbulb 1) Device LastLevel: 0
2017-04-03 18:35:36.594 (Playbulb 1) Device:	7 - ID: 61, Name: 'Playbulb 1 - Speed', nValue: 0, sValue: ''
2017-04-03 18:35:36.594 (Playbulb 1) Device ID:	'61'
2017-04-03 18:35:36.595 (Playbulb 1) Device Name:	'Playbulb 1 - Speed'
2017-04-03 18:35:36.595 (Playbulb 1) Device nValue:	0
2017-04-03 18:35:36.595 (Playbulb 1) Device sValue: ''
2017-04-03 18:35:36.595 (Playbulb 1) Device LastLevel: 0
2017-04-03 18:35:36.595 (Playbulb 1) Device:	8 - ID: 62, Name: 'Playbulb 1 - Speed', nValue: 0, sValue: ''
2017-04-03 18:35:36.595 (Playbulb 1) Device ID:	'62'
2017-04-03 18:35:36.595 (Playbulb 1) Device Name:	'Playbulb 1 - Speed'
2017-04-03 18:35:36.595 (Playbulb 1) Device nValue:	0
2017-04-03 18:35:36.595 (Playbulb 1) Device sValue: ''
2017-04-03 18:35:36.596 (Playbulb 1) Device LastLevel: 0
2017-04-03 18:35:36.596 (Playbulb 1) Plugin is started.
2017-04-03 18:35:36.596 (Playbulb 1) Heartbeat interval set to: 60.
2017-04-03 18:35:46.016 (Playbulb 1) Calling message handler 'onHeartbeat'.
2017-04-03 18:36:46.023 (Playbulb 1) Calling message handler 'onHeartbeat'.
2017-04-03 18:37:13.276 User: Admin initiated a switch command (55/Playbulb 1 - Status/On)
2017-04-03 18:37:13.321 (Playbulb 1) Calling message handler 'onCommand'.
2017-04-03 18:37:13.321 (Playbulb 1) DEBUG : white before command is set 0
2017-04-03 18:37:13.321 (Playbulb 1) DEBUG : red before command is set 0
2017-04-03 18:37:13.322 (Playbulb 1) DEBUG : green before command is set 0
2017-04-03 18:37:13.322 (Playbulb 1) DEBUG : blue before command is set 0
2017-04-03 18:37:13.322 (Playbulb 1) DEBUG : mode before command is set 0
2017-04-03 18:37:13.322 (Playbulb 1) DEBUG : speed before command is set 0
2017-04-03 18:37:13.322 (Playbulb 1) DEBUG : onCommand called for Unit 1: Parameter 'On', Level: 0
2017-04-03 18:37:13.323 (Playbulb 1) handles send 0x16
2017-04-03 18:37:13.323 (Playbulb 1) Data send bytearray(b'\xff\xff\xff\xff')
2017-04-03 18:37:13.325 (Playbulb 1) handles send 0x16
2017-04-03 18:37:13.325 (Playbulb 1) Data send bytearray(b'\xff\xff\xff\xff')
2017-04-03 18:37:13.476 Error: (Playbulb 1) 'onCommand' failed 'IndexError'.
2017-04-03 18:37:13.477 Error: (Playbulb 1) ----> Line 399 in /home/pi/domoticz/plugins/mipow/plugin.py, function onCommand
2017-04-03 18:37:13.477 Error: (Playbulb 1) ----> Line 353 in /home/pi/domoticz/plugins/mipow/plugin.py, function onCommand
2017-04-03 18:37:13.477 Error: (Playbulb 1) ----> Line 533 in /home/pi/domoticz/plugins/mipow/plugin.py, function CheckStatus
As you can see he can connect and gets a heartbeat but when I swith it on I get a index error.

For your information I had to rename the plugunRGBW.py to plugin.py in the plugins folder before the Mipow/Playbulb appeared in the hardwarelist. Otherwise it didn't appear. On github it is called pluginRGBW.py.
Domoticz version
Python version
Bulb type
Fw version

Are importants information we need

File name will be change for the good one, thx.

Ok sorry here we go:

Domoticz: 3.7243
Python: Python 2.7.9 (python -V)
but also Python 3.4.2 (python3 -V)
Bulb: Playbulb Candle
Firmware: BTL300_v6

Something else in your wiki you mention: mkdir /home/user/domoticz/plugin/mipow
the username is missing: mkdir /home/user/pi/domoticz/plugin/mipow
deennoo
Posts: 784
Joined: Wednesday 10 December 2014 13:06
Target OS: Linux
Domoticz version: beta
Location: Bordeaux France
Contact:

Re: RE: Re: PlayBlub (Bluetooth Bulb) Python Plugin - Beta tester Wanted

Post by deennoo »

Mediacj wrote: Something else in your wiki you mention: mkdir /home/user/domoticz/plugin/mipow
the username is missing: mkdir /home/user/pi/domoticz/plugin/mipow
Which distro do you use ? correct dir on debian is /home/user/domoticz/plugins where user is you user name or pi if you use a rpi distro

what mean for a rpi user with raspbian : /home/pi/domoticz/plugins/Mipow not user/pi
Domoticz stable 3.5877 for real & Domoticz beta for test
Rfxtrxe / RFLink / Milight / Yeelight / Tasmota / MQTT / BLE / Zigate
http://domo-attitude.fr
User avatar
Mediacj
Posts: 74
Joined: Wednesday 11 February 2015 16:09
Target OS: Raspberry Pi / ODroid
Domoticz version:
Location: Netherlands
Contact:

Re: PlayBlub (Bluetooth Bulb) Python Plugin - Beta tester Wanted

Post by Mediacj »

My fault, it should be /home/pi offcourse

I use raspbian to.

I also get a error on the heartbeat:

Code: Select all

2017-04-04 16:37:57.023 (Playbulb 1) Calling message handler 'onHeartbeat'.
2017-04-04 16:37:57.402 Error: (Playbulb 1) 'onHeartbeat' failed 'IndexError'.
2017-04-04 16:37:57.402 Error: (Playbulb 1) ----> Line 407 in /home/pi/domoticz/plugins/mipow/plugin.py, function onHeartbeat
2017-04-04 16:37:57.403 Error: (Playbulb 1) ----> Line 364 in /home/pi/domoticz/plugins/mipow/plugin.py, function onHeartbeat
2017-04-04 16:37:57.403 Error: (Playbulb 1) ----> Line 533 in /home/pi/domoticz/plugins/mipow/plugin.py, function CheckStatus
zaraki673
Posts: 32
Joined: Thursday 19 January 2017 23:46
Target OS: Raspberry Pi / ODroid
Domoticz version: Beta
Contact:

Re: PlayBlub (Bluetooth Bulb) Python Plugin - Beta tester Wanted

Post by zaraki673 »

Hi Mediacj,

have you this issue on every heartbeat ? or just one time ?

i think it's just an init error in my code, i will see that ASAP ;)
User avatar
Mediacj
Posts: 74
Joined: Wednesday 11 February 2015 16:09
Target OS: Raspberry Pi / ODroid
Domoticz version:
Location: Netherlands
Contact:

Re: PlayBlub (Bluetooth Bulb) Python Plugin - Beta tester Wanted

Post by Mediacj »

zaraki673 wrote:Hi Mediacj,

have you this issue on every heartbeat ? or just one time ?

i think it's just an init error in my code, i will see that ASAP ;)
Hi,

Thx for your software!

Indeed yesterday there were no heartbeat error's, but the index error on switching was today and yesterday.
poudenes
Posts: 667
Joined: Wednesday 08 March 2017 9:42
Target OS: Linux
Domoticz version: 3.8993
Location: Amsterdam
Contact:

Re: PlayBlub (Bluetooth Bulb) Python Plugin - Beta tester Wanted

Post by poudenes »

Hi All,

In this site: http://www.domoticz.com/wiki/Plugins/PlayBulb they also talk about other bulb see last line:

"My bulb FW isn't on the list, can't controle it ? yes you can ! (need more works on it)
Let's speak about it on this topic : viewtopic.php?f=28&t=16843"


When we goto the topic on the first post you can read:
"Don't ask for other bulb here or other feature this is not the place, this plugin will be well documented, and give all tools to made other btle plugin for other device."

Can we talk or not talk for other PlayBulb devices? I have the BTL203M_V1.6
RPi3 B+, Debain Stretch, Domoticz, Homebridge, Dashticz, RFLink, Milight, Z-Wave, Fibaro, Nanoleaf, Nest, Harmony Hub, Now try to understand pass2php
deennoo
Posts: 784
Joined: Wednesday 10 December 2014 13:06
Target OS: Linux
Domoticz version: beta
Location: Bordeaux France
Contact:

Re: RE: Re: PlayBlub (Bluetooth Bulb) Python Plugin - Beta tester Wanted

Post by deennoo »

poudenes wrote:Hi All,

In this site: http://www.domoticz.com/wiki/Plugins/PlayBulb they also talk about other bulb see last line:

"My bulb FW isn't on the list, can't controle it ? yes you can ! (need more works on it)
Let's speak about it on this topic : viewtopic.php?f=28&t=16843"


When we goto the topic on the first post you can read:
"Don't ask for other bulb here or other feature this is not the place, this plugin will be well documented, and give all tools to made other btle plugin for other device."

Can we talk or not talk for other PlayBulb devices? I have the BTL203M_V1.6
Yes you can !


This was for guys who want to add Awox or yxz brand.

OK for your Fw, which modele is your bulb please ? Provid a link for a pictures is a good point to start
Domoticz stable 3.5877 for real & Domoticz beta for test
Rfxtrxe / RFLink / Milight / Yeelight / Tasmota / MQTT / BLE / Zigate
http://domo-attitude.fr
poudenes
Posts: 667
Joined: Wednesday 08 March 2017 9:42
Target OS: Linux
Domoticz version: 3.8993
Location: Amsterdam
Contact:

Re: PlayBlub (Bluetooth Bulb) Python Plugin - Beta tester Wanted

Post by poudenes »

great,

I have this one:

https://www.mipow.com/pages/playbulb-spot

to bad not experienced with programming so always hope someone can build script...
RPi3 B+, Debain Stretch, Domoticz, Homebridge, Dashticz, RFLink, Milight, Z-Wave, Fibaro, Nanoleaf, Nest, Harmony Hub, Now try to understand pass2php
deennoo
Posts: 784
Joined: Wednesday 10 December 2014 13:06
Target OS: Linux
Domoticz version: beta
Location: Bordeaux France
Contact:

Re: RE: Re: PlayBlub (Bluetooth Bulb) Python Plugin - Beta tester Wanted

Post by deennoo »

poudenes wrote:great,

I have this one:

https://www.mipow.com/pages/playbulb-spot

to bad not experienced with programming so always hope someone can build script...
Have you try each modèle already on the plugin ? Does no one works à bit ?

Envoyé de mon H60-L12 en utilisant Tapatalk
Domoticz stable 3.5877 for real & Domoticz beta for test
Rfxtrxe / RFLink / Milight / Yeelight / Tasmota / MQTT / BLE / Zigate
http://domo-attitude.fr
poudenes
Posts: 667
Joined: Wednesday 08 March 2017 9:42
Target OS: Linux
Domoticz version: 3.8993
Location: Amsterdam
Contact:

Re: PlayBlub (Bluetooth Bulb) Python Plugin - Beta tester Wanted

Post by poudenes »

No none of the lamps will work for a part.

Add them give the MAC address of Bulb, add the switches and try to do some effect, of color change... Status switch etc.
When i do a sudo hcitool lescan before adding in Domoticz i see the bulb:

2F:A6:4B:11:AC:E6 PLAYBULB
2F:A6:4B:11:AC:E6 (unknown)

After adding in Domoticz i can't see the bulb, because it has been linked maybe?

when go into Bluetoothctl i can scan as well and got this information:

[CHG] Device 2F:A6:4B:11:AC:E6 ManufacturerData Key: 0x494d
[CHG] Device 2F:A6:4B:11:AC:E6 ManufacturerData Value: 0x50
[CHG] Device 2F:A6:4B:11:AC:E6 ManufacturerData Value: 0x4f
[CHG] Device 2F:A6:4B:11:AC:E6 ManufacturerData Value: 0x57
[CHG] Device 2F:A6:4B:11:AC:E6 ManufacturerData Value: 0x00
[CHG] Device 2F:A6:4B:11:AC:E6 ManufacturerData Value: 0x00
[CHG] Device 2F:A6:4B:11:AC:E6 ManufacturerData Value: 0x00
[CHG] Device 2F:A6:4B:11:AC:E6 ManufacturerData Value: 0x00

[PLAYBULB]# list-attributes
Primary Service
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0001
00001801-0000-1000-8000-00805f9b34fb
Generic Attribute Profile
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0001/char0002
00002a05-0000-1000-8000-00805f9b34fb
Service Changed
Descriptor
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0001/char0002/desc0004
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Primary Service
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service000c
00001016-d102-11e1-9b23-00025b00a5a5
Vendor specific
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service000c/char000d
00001013-d102-11e1-9b23-00025b00a5a5
Vendor specific
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service000c/char000f
00001018-d102-11e1-9b23-00025b00a5a5
Vendor specific
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service000c/char0011
00001014-d102-11e1-9b23-00025b00a5a5
Vendor specific
Descriptor
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service000c/char0011/desc0013
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service000c/char0014
00001011-d102-11e1-9b23-00025b00a5a5
Vendor specific
Primary Service
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0016
0000ff0a-0000-1000-8000-00805f9b34fb
Unknown
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0016/char0017
00002a37-0000-1000-8000-00805f9b34fb
Heart Rate Measurement
Descriptor
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0016/char0017/desc0019
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0016/char001a
00001234-0000-1000-8000-00805f9b34fb
Unknown
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0016/char001c
0000fff7-0000-1000-8000-00805f9b34fb
Unknown
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0016/char001e
0000fff8-0000-1000-8000-00805f9b34fb
Unknown
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0016/char0020
0000fff9-0000-1000-8000-00805f9b34fb
Unknown
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0016/char0022
0000fffb-0000-1000-8000-00805f9b34fb
Unknown
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0016/char0024
0000fffc-0000-1000-8000-00805f9b34fb
Unknown
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0016/char0026
0000fffd-0000-1000-8000-00805f9b34fb
Fast IDentity Online Alliance (FIDO)
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0016/char0028
0000fffe-0000-1000-8000-00805f9b34fb
Alliance for Wireless Power (A4WP)
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0016/char002a
0000ffff-0000-1000-8000-00805f9b34fb
Unknown
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0016/char002c
0000fff5-0000-1000-8000-00805f9b34fb
Unknown
Primary Service
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service002e
0000180f-0000-1000-8000-00805f9b34fb
Battery Service
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service002e/char002f
00002a19-0000-1000-8000-00805f9b34fb
Battery Level
Descriptor
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service002e/char002f/desc0031
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Primary Service
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0032
0000fef1-0000-1000-8000-00805f9b34fb
CSR
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0032/char0033
c4edc000-9daf-11e3-8000-00025b000b00
Vendor specific
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0032/char0035
c4edc000-9daf-11e3-8001-00025b000b00
Vendor specific
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0032/char0037
c4edc000-9daf-11e3-8002-00025b000b00
Vendor specific
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0032/char0039
c4edc000-9daf-11e3-8003-00025b000b00
Vendor specific
Descriptor
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0032/char0039/desc003b
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0032/char003c
c4edc000-9daf-11e3-8004-00025b000b00
Vendor specific
Descriptor
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0032/char003c/desc003e
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0032/char003f
c4edc000-9daf-11e3-8005-00025b000b00
Vendor specific
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0032/char0041
c4edc000-9daf-11e3-8006-00025b000b00
Vendor specific
Primary Service
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0043
0000180a-0000-1000-8000-00805f9b34fb
Device Information
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0043/char0044
00002a25-0000-1000-8000-00805f9b34fb
Serial Number String
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0043/char0046
00002a27-0000-1000-8000-00805f9b34fb
Hardware Revision String
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0043/char0048
00002a26-0000-1000-8000-00805f9b34fb
Firmware Revision String
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0043/char004a
00002a28-0000-1000-8000-00805f9b34fb
Software Revision String
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0043/char004c
00002a29-0000-1000-8000-00805f9b34fb
Manufacturer Name String
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0043/char004e
00002a50-0000-1000-8000-00805f9b34fb
PnP ID
RPi3 B+, Debain Stretch, Domoticz, Homebridge, Dashticz, RFLink, Milight, Z-Wave, Fibaro, Nanoleaf, Nest, Harmony Hub, Now try to understand pass2php
deennoo
Posts: 784
Joined: Wednesday 10 December 2014 13:06
Target OS: Linux
Domoticz version: beta
Location: Bordeaux France
Contact:

Re: PlayBlub (Bluetooth Bulb) Python Plugin - Beta tester Wanted

Post by deennoo »

poudenes wrote:No none of the lamps will work for a part.

Add them give the MAC address of Bulb, add the switches and try to do some effect, of color change... Status switch etc.
When i do a sudo hcitool lescan before adding in Domoticz i see the bulb:

----
Characteristic
/org/bluez/hci0/dev_2F_A6_4B_11_AC_E6/service0043/char004e
00002a50-0000-1000-8000-00805f9b34fb
PnP ID
Thanks for this works, this really help to add this on the plugin, your the first who got this kind of bulb, so their is no other source.

Let dev work on it for now, be patient ok ?
Domoticz stable 3.5877 for real & Domoticz beta for test
Rfxtrxe / RFLink / Milight / Yeelight / Tasmota / MQTT / BLE / Zigate
http://domo-attitude.fr
poudenes
Posts: 667
Joined: Wednesday 08 March 2017 9:42
Target OS: Linux
Domoticz version: 3.8993
Location: Amsterdam
Contact:

Re: PlayBlub (Bluetooth Bulb) Python Plugin - Beta tester Wanted

Post by poudenes »

Cool !!! I can wait :D

In the iOS app these options i have:
Normal color picket
off - on (and brightness light) slider
Flashing (color switch, slow - fast)
Pulse (slow - fast)
Rainbow (slow - fast)
Rainbow Fade (slow - fast)
Candle (Color Switch)
RPi3 B+, Debain Stretch, Domoticz, Homebridge, Dashticz, RFLink, Milight, Z-Wave, Fibaro, Nanoleaf, Nest, Harmony Hub, Now try to understand pass2php
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest