Page 4 of 9
Re: Python Plugin: ebusd
Posted: Saturday 17 February 2018 19:54
by pigloox
Hi,
I have a strange message sent back by dzvent when I modify a parameter of your plugin (modify button)
Code: Select all
2018-02-17 19:49:54.670 dzVents: Error (2.4.1): Discarding device. No last update info found: {["timedOut"]=false, ["rawData"]={"17.02.2018"}, ["changed"]=true, ["batteryLevel"]=0, ["lastUpdate"]="", ["deviceType"]="General", ["deviceID"]="", ["signalLevel"]=0, ["description"]="", ["subType"]="Text", ["lastLevel"]=255, ["baseType"]="device", ["id"]=563, ["switchTypeValue"]=0, ["name"]="Chaudiere - broadcast:vdatetime:1 - date", ["switchType"]="On/Off", ["data"]={["_state"]="17.02.2018", ["protected"]=false, ["hardwareType"]="ebusd bridge", ["icon"]="text", ["hardwareName"]="Chaudiere", ["hardwareTypeValue"]=94, ["_nValue"]=0, ["unit"]=3, ["hardwareID"]=16}}
Is this normal?
And another thing, I have these 2 registers that are detected as text sensor, should not they be switches?
Re: Python Plugin: ebusd
Posted: Saturday 17 February 2018 21:04
by Barberousse
pigloox wrote: ↑Saturday 17 February 2018 19:54
I have a strange message sent back by dzvent when I modify a parameter of your plugin (modify button)
Maybe related to still not resolved issue where svalue and nvalue cannot be sent to python plugin, but I'm not sure. Or it means that vdatetime is never updated, is it? Could you try again you script with debug enabled in ebusd plugin, and post log output?
pigloox wrote: ↑Saturday 17 February 2018 19:54
And another thing, I have these 2 registers that are detected as text sensor, should not they be switches?
It depends if they are read-only from ebusd perspective. Are they are writable (with command ebusctl write -c bai status02 xxxx") ? I don't think so, guessing by the name "status". I don't see theses registers in json data you sent yesterday.
Re: Python Plugin: ebusd
Posted: Thursday 22 February 2018 19:13
by fantom
1) On new domoticz beta, in this plugin is exists one bug: error when ry add device to domoticz (and add new devices is disabled in cofiguration)
2) It would be better if the data to domoticz were sent only when the value changed. Now for example for pump i have off, off, off, off, on, on, on, on etc
Fantom
Re: Python Plugin: ebusd
Posted: Friday 23 February 2018 11:19
by Barberousse
fantom wrote: ↑Thursday 22 February 2018 19:13
1) On new domoticz beta, in this plugin is exists one bug: error when ry add device to domoticz (and add new devices is disabled in cofiguration)
I don't understand, can you post the log, with debug enabled in plugin configuration?
fantom wrote: ↑Thursday 22 February 2018 19:13
2) It would be better if the data to domoticz were sent only when the value changed. Now for example for pump i have off, off, off, off, on, on, on, on etc
I will try something, but I'm not sure that I can't prevent "useless" update without turning devices in red (timed out devices) for the devices that doesn't change very often (pressure for instance).
Re: Python Plugin: ebusd
Posted: Friday 23 February 2018 11:37
by fantom
Ad 1)
2018-02-23 11:36:36.271 Error: (ebus) Device creation failed, Domoticz settings prevent accepting new devices.
2018-02-23 11:36:36.271 Error: (ebus) 'onMessage' failed 'KeyError'.
2018-02-23 11:36:36.271 Error: (ebus) ----> Line 841 in /home/pi/domoticz/plugins/DomoticzEbusd/plugin.py, function onMessage
2018-02-23 11:36:36.271 Error: (ebus) ----> Line 635 in /home/pi/domoticz/plugins/DomoticzEbusd/plugin.py, function onMessage
2018-02-23 11:36:36.271 Error: (ebus) ----> Line 551 in /home/pi/domoticz/plugins/DomoticzEbusd/plugin.py, function parseJson
Re: Python Plugin: ebusd
Posted: Friday 23 February 2018 23:25
by Barberousse
fantom wrote: ↑Thursday 22 February 2018 19:13
1) On new domoticz beta, in this plugin is exists one bug: error when ry add device to domoticz (and add new devices is disabled in cofiguration)
Should be corrected in version 1.2.1
fantom wrote: ↑Thursday 22 February 2018 19:13
2) It would be better if the data to domoticz were sent only when the value changed. Now for example for pump i have off, off, off, off, on, on, on, on etc
I made some tries, if I don't push values on regular basis (even if same values), the device becomes red in Domoticz and is considered timed out.
Re: Python Plugin: ebusd
Posted: Saturday 24 February 2018 11:55
by fantom
Ad2). Maybe for temperature etc red is showed. But for switch etc not.
Fantom
Re: Python Plugin: ebusd
Posted: Saturday 24 February 2018 17:53
by Barberousse
fantom wrote: ↑Saturday 24 February 2018 11:55
Ad2). Maybe for temperature etc red is showed. But for switch etc not.
You're right, it depends on device type. I'll see how to implement this, depending if my pull request is accepted:
https://github.com/domoticz/domoticz/pull/2173. I would prefer plugins to have complete control on timeouts.
Re: Python Plugin: ebusd
Posted: Saturday 10 March 2018 10:17
by Barberousse
fantom wrote: ↑Saturday 24 February 2018 11:55
Ad2). Maybe for temperature etc red is showed. But for switch etc not.
Version 1.2.2 prevents useless updates for switches and text
Re: Python Plugin: ebusd
Posted: Saturday 10 March 2018 22:33
by mozzarella
Barberousse wrote: ↑Saturday 10 March 2018 10:17
Version 1.2.2 prevents useless updates for switches and text
Hi Barberousse,
now it looks like devices are updated only in case of state change.
Not sure if this is a bug but i want button selector rather than selector menu. But on device state change there is also change selector style.
I changed SelectorStyle to "0" and now it updates only device state.
Code: Select all
dOptions = {"LevelActions": sLevelActions, "LevelNames": sLevelNames, "LevelOffHidden": "true", "SelectorStyle": "0"}
Only issue is in case of device protection, when trying to change state (in Selector style set to: Button set) there is no password prompt
but only "Wrong code" message. But it could be Domoticz issue.
Thanks for your great work.
Re: Python Plugin: ebusd
Posted: Saturday 10 March 2018 23:15
by Barberousse
mozzarella wrote: ↑Saturday 10 March 2018 22:33
now it looks like devices are updated only in case of state change.
That is the intended behavior
mozzarella wrote: ↑Saturday 10 March 2018 22:33
Not sure if this is a bug but i want button selector rather than selector menu. But on device state change there is also change selector style.
It was the intended behavior too, to prevent edit of connection between domoticz level values and names, style was reset at each update, but I didn't imagine your need, so I will roll back in version 1.2.3. Users will be able change level names, but if they loose track, they will have to delete the device and restart domoticz or the plugin, the device will be recreated with correct level values and corresponding names (but will loose history).
Be aware that next version will need very recent beta version of Domoticz to work properly.
Re: Python Plugin: ebusd
Posted: Saturday 10 March 2018 23:45
by mozzarella
Barberousse wrote: ↑Saturday 10 March 2018 23:15
It was the intended behavior too, to prevent edit of connection between domoticz level values and names, style was reset at each update, but I didn't imagine your need, so I will roll back in version 1.2.3. Users will be able change level names, but if they loose track, they will have to delete the device and restart domoticz or the plugin, the device will be recreated with correct level values and corresponding names (but will loose history).
Be aware that next version will need very recent beta version of Domoticz to work properly.
Not sure if I explain it correctly. I did not change level names. Only issue was with device appearance that changes every value update from:
to:
In the "Button set" mode this is not possible to change device state in case of password protect but it working in "Select menu: style
Re: Python Plugin: ebusd
Posted: Saturday 10 March 2018 23:52
by Barberousse
I was just explaining why I was forcing the style, but the problem you're describing has more to do with Domoticz itself than with the plugin. Try version 1.2.3 just published now (and upgrade Domoticz), and keep me in touch though.
Re: Python Plugin: ebusd
Posted: Sunday 11 March 2018 22:19
by mozzarella
Hi, plugin updated to 1.2.3 version. No issue with Selector style change during status update.
Still got an error in case of device protection. No entry in domoticz log according to this.
Re: Python Plugin: ebusd
Posted: Monday 12 March 2018 23:24
by mozzarella
Hi, play more with version 1.2.3. When I am trying to add new device I receive below error
Code: Select all
2018-03-12 23:11:09.213 Error: Expected: myVar = Domoticz.Device(Name="myDevice", Unit=0, TypeName="", Type=0, Subtype=0, Switchtype=0, Image=0, Options={}, Used=1)
2018-03-12 23:11:09.213 Error: (EbusdWW) 'CDevice_init' failed 'TypeError':''Description' is an invalid keyword argument for this function'.
2018-03-12 23:11:09.213 Error: Device creation failed, Device object is not associated with a plugin.
Domoticz Version: 3.8872
Re: Python Plugin: ebusd
Posted: Sunday 18 March 2018 17:37
by pigloox
Hi,
Since Beta 9052, i've this errors :
Code: Select all
2018-03-18 17:30:43.154 Error: Plugin: Connection Exception: 'resolve: Host not found (authoritative)' connecting to '192.168.1.19:8889'
2018-03-18 17:30:52.626 Error: (Chaudiere) Device Chaudiere - Temp Ext ID 560 DeviceID broadcast:outsidetemp:0 timed out
2018-03-18 17:30:52.633 Error: (Chaudiere) Device Chaudiere - Température départ ID 562 DeviceID bai:flowtemp:0 timed out
2018-03-18 17:30:52.656 Error: (Chaudiere) Device Chaudiere - broadcast:vdatetime:1 - date ID 563 DeviceID broadcast:vdatetime:1 timed out
2018-03-18 17:30:52.722 Error: (Chaudiere) Device Chaudiere - time ID 561 DeviceID broadcast:vdatetime:0 timed out
2018-03-18 17:30:52.754 Error: (Chaudiere) Device Chaudiere - bai:status01:0 - temp1 ID 564 DeviceID bai:status01:0 timed out
2018-03-18 17:30:52.762 Error: (Chaudiere) Device Chaudiere - bai:status01:1 - temp1 ID 565 DeviceID bai:status01:1 timed out
2018-03-18 17:30:52.768 Error: (Chaudiere) Device Chaudiere - Temp Ext Brute ID 566 DeviceID bai:status01:2 timed out
2018-03-18 17:30:52.775 Error: (Chaudiere) Device Chaudiere - Température retour ID 567 DeviceID bai:status01:3 timed out
2018-03-18 17:30:52.781 Error: (Chaudiere) Device Chaudiere - bai:status01:4 - temp1 ID 568 DeviceID bai:status01:4 timed out
2018-03-18 17:30:52.785 Error: (Chaudiere) Device Chaudiere - bai:status02:0 - hwcmode ID 569 DeviceID bai:status02:0 timed out
2018-03-18 17:30:52.806 Error: (Chaudiere) Device Chaudiere - bai:status01:5 - pumpstate ID 570 DeviceID bai:status01:5 timed out
2018-03-18 17:30:52.843 Error: (Chaudiere) Device Chaudiere - bai:status02:1 - temp0 ID 571 DeviceID bai:status02:1 timed out
2018-03-18 17:30:52.847 Error: (Chaudiere) Device Chaudiere - bai:status02:2 - temp1 ID 572 DeviceID bai:status02:2 timed out
2018-03-18 17:30:52.855 Error: (Chaudiere) Device Chaudiere - bai:status02:3 - temp0 ID 573 DeviceID bai:status02:3 timed out
2018-03-18 17:30:52.858 Error: (Chaudiere) Device Chaudiere - bai:status02:4 - temp1 ID 574 DeviceID bai:status02:4 timed out
2018-03-18 17:31:23.876 Error: (Chaudiere) Device Chaudiere - Température départ ID 562 DeviceID bai:flowtemp:0 timed out
2018-03-18 17:31:23.883 Error: (Chaudiere) Device Chaudiere - bai:status01:0 - temp1 ID 564 DeviceID bai:status01:0 timed out
2018-03-18 17:31:23.906 Error: (Chaudiere) Device Chaudiere - bai:status01:1 - temp1 ID 565 DeviceID bai:status01:1 timed out
2018-03-18 17:31:23.912 Error: (Chaudiere) Device Chaudiere - Temp Ext Brute ID 566 DeviceID bai:status01:2 timed out
2018-03-18 17:31:23.918 Error: (Chaudiere) Device Chaudiere - Température retour ID 567 DeviceID bai:status01:3 timed out
2018-03-18 17:31:23.924 Error: (Chaudiere) Device Chaudiere - bai:status01:4 - temp1 ID 568 DeviceID bai:status01:4 timed out
2018-03-18 17:31:23.930 Error: (Chaudiere) Device Chaudiere - bai:status02:0 - hwcmode ID 569 DeviceID bai:status02:0 timed out
2018-03-18 17:31:23.938 Error: (Chaudiere) Device Chaudiere - bai:status01:5 - pumpstate ID 570 DeviceID bai:status01:5 timed out
2018-03-18 17:31:23.946 Error: (Chaudiere) Device Chaudiere - bai:status02:1 - temp0 ID 571 DeviceID bai:status02:1 timed out
2018-03-18 17:31:23.952 Error: (Chaudiere) Device Chaudiere - bai:status02:2 - temp1 ID 572 DeviceID bai:status02:2 timed out
2018-03-18 17:31:23.958 Error: (Chaudiere) Device Chaudiere - bai:status02:3 - temp0 ID 573 DeviceID bai:status02:3 timed out
2018-03-18 17:31:23.964 Error: (Chaudiere) Device Chaudiere - bai:status02:4 - temp1 ID 574 DeviceID bai:status02:4 timed out
Ideas ?
Re: Python Plugin: ebusd
Posted: Sunday 18 March 2018 17:42
by Barberousse
pigloox wrote: ↑Sunday 18 March 2018 17:37
Ideas ?
What is your version of plugin?
Re: Python Plugin: ebusd
Posted: Sunday 18 March 2018 18:10
by pigloox
Barberousse wrote: ↑Sunday 18 March 2018 17:42
What is your version of plugin?
The Last, (downloaded this morning)
Re: Python Plugin: ebusd
Posted: Sunday 18 March 2018 18:12
by Barberousse
pigloox wrote: ↑Sunday 18 March 2018 18:10
The Last, (downloaded this morning)
And your refresh rate?
Re: Python Plugin: ebusd
Posted: Sunday 18 March 2018 18:18
by pigloox
10 seconds, I know it's little but it always worked before without any error
