Python Plugin: ebusd

[Barberousse]

I find out that there are no configuration files available for my hardware.
I have a controler wich is an examaster SBX00 and my roomthermostat is a exacontrol E7C00 (the configuration file for de wirelles version E7f unfortunately didn't work ).

You should ask for help on https://github.com/john30/ebusd-configuration, as long as ebusd doesn't work with your hardware, DomoticzEbusd plugin won't work either.

[softone13]

Hi,
At the beginning I would like to say "thanks, good job" to the author.
I've made simple blockly to automatically change "HwcOpmode" from "manual" to "auto" after x seconds. When I change status to "manual" the event starts but status is not changing to "auto" after x seconds. But when I press "auto" mode on the selector switch for HwcOpmode device it's working so it's configured properly. What is wrong?

[Barberousse]

Hi,
At the beginning I would like to say "thanks, good job" to the author.
I've made simple blockly to automatically change "HwcOpmode" from "manual" to "auto" after x seconds. When I change status to "manual" the event starts but status is not changing to "auto" after x seconds. But when I press "auto" mode on the selector switch for HwcOpmode device it's working so it's configured properly. What is wrong?

With blocky, when checking the level of a selector switch -> refer to level name, when setting the level -> refer to level value (this is NOT obvious). Example here: https://www.domoticz.com/forum/viewtopic.php?t=13317
To see possible levels, click on "edit" of your selector switch:

Screenshot_20200210_213009.png (16.42 KiB) Viewed 2248 times

Screenshot_20200210_213126.png (17.87 KiB) Viewed 2248 times

[softone13]

Thank you!

[kofec]

@Barberousse
First, thanks for creating this plugin - it is working great. I have a question regarding parameter "Read-only". If I set it to "True" what I should expect ?
I expect that we will only read from ebusd but never write.
In my case, the domoticz is reading the values of some parameters every 10 minutes. But there is also another script (in bash) which monitor ebusd.log and base on it update the values of some parameters. When external scripts update parameters (created by this plugin), this plugin is trying to write to ebusd (which was not expected by me).
so I modified one line:

Code: Select all

elif self.sCurrentCommand == "write" and (not (Parameters["Mode5"] == "True")):  

[Barberousse]

First, thanks for creating this plugin - it is working great. I have a question regarding parameter "Read-only". If I set it to "True" what I should expect ?
I expect that we will only read from ebusd but never write.

Until now, the "read-only" flag was used for instance to show in Domoticz a thermal setpoint as simple temperature sensor. But I didn't think that some scripts would try anyway to write values. I've added your check in version 1.4.3, and another one elsewhere in the plugin, thank you.

[Barberousse]

Hello,

Starting version 2 of the plugin, it will autodiscover every registers if you don't specify them.

[fantom]

Hi. I try run this plugin but I don't see any devices
I have clicked "allow add device for 5 minutes" in settings.

Log:

Code: Select all

2024-05-06 10:59:05.891 ebus: Look for field 3 in JSON data
2024-05-06 10:59:05.891 ebus: Look for field 0 in JSON data
2024-05-06 10:59:05.891 ebus: Look for field 0 in JSON data
2024-05-06 10:59:05.891 ebus: Look for field 0 in JSON data
2024-05-06 10:59:05.891 ebus: Look for field temp1 in JSON data
2024-05-06 10:59:05.891 ebus: Field number of register mc:tempdesiredhigh:temp1 is 0
2024-05-06 10:59:05.891 ebus: Look for field 0 in JSON data
2024-05-06 10:59:05.892 ebus: Look for field temp1 in JSON data
2024-05-06 10:59:05.892 ebus: Field number of register mc:tempdesiredlow:temp1 is 0
2024-05-06 10:59:05.892 ebus: Look for field 0 in JSON data
2024-05-06 10:59:05.892 ebus: Look for field 0 in JSON data
2024-05-06 10:59:05.892 ebus: Look for field time in JSON data
2024-05-06 10:59:05.892 ebus: Field number of register mc:time:time is 0
2024-05-06 10:59:05.892 ebus: Look for field 0 in JSON data
2024-05-06 10:59:05.892 ebus: Look for field bday in JSON data
2024-05-06 10:59:05.892 ebus: Field number of register mc:weekday:bday is 0
2024-05-06 10:59:05.893 ebus: Acquiring GIL for 'onMessageCallback'
2024-05-06 10:59:05.108 Status: ebus: Initialized version 2.0.3, author 'Barberousse'
2024-05-06 10:59:05.744 Error: ebus: Cannot find usable field for device bai:setmode:10
2024-05-06 10:59:05.745 Error: ebus: Cannot find usable field for device bai:setmode:11
2024-05-06 10:59:05.768 Error: ebus: Cannot find usable field for device f43:cctimer.friday:7
2024-05-06 10:59:05.770 Error: ebus: Cannot find usable field for device f43:cctimer.monday:7
2024-05-06 10:59:05.773 Error: ebus: Cannot find usable field for device f43:cctimer.saturday:7
2024-05-06 10:59:05.776 Error: ebus: Cannot find usable field for device f43:cctimer.sunday:7
2024-05-06 10:59:05.779 Error: ebus: Cannot find usable field for device f43:cctimer.thursday:7
2024-05-06 10:59:05.781 Error: ebus: Cannot find usable field for device f43:cctimer.tuesday:7
2024-05-06 10:59:05.784 Error: ebus: Cannot find usable field for device f43:cctimer.wednesday:7
2024-05-06 10:59:05.798 Error: ebus: Cannot find usable field for device f43:hctimer.friday:7
2024-05-06 10:59:05.801 Error: ebus: Cannot find usable field for device f43:hctimer.monday:7
2024-05-06 10:59:05.804 Error: ebus: Cannot find usable field for device f43:hctimer.saturday:7
2024-05-06 10:59:05.807 Error: ebus: Cannot find usable field for device f43:hctimer.sunday:7
2024-05-06 10:59:05.809 Error: ebus: Cannot find usable field for device f43:hctimer.thursday:7
2024-05-06 10:59:05.812 Error: ebus: Cannot find usable field for device f43:hctimer.tuesday:7
2024-05-06 10:59:05.815 Error: ebus: Cannot find usable field for device f43:hctimer.wednesday:7
2024-05-06 10:59:05.821 Error: ebus: Cannot find usable field for device f43:hwctimer.friday:7
2024-05-06 10:59:05.824 Error: ebus: Cannot find usable field for device f43:hwctimer.monday:7
2024-05-06 10:59:05.827 Error: ebus: Cannot find usable field for device f43:hwctimer.saturday:7
2024-05-06 10:59:05.830 Error: ebus: Cannot find usable field for device f43:hwctimer.sunday:7
2024-05-06 10:59:05.833 Error: ebus: Cannot find usable field for device f43:hwctimer.thursday:7
2024-05-06 10:59:05.835 Error: ebus: Cannot find usable field for device f43:hwctimer.tuesday:7
2024-05-06 10:59:05.838 Error: ebus: Cannot find usable field for device f43:hwctimer.wednesday:7
2024-05-06 10:59:05.845 Error: ebus: Cannot find usable field for device f43:setpoints.friday:3
2024-05-06 10:59:05.846 Error: ebus: Cannot find usable field for device f43:setpoints.monday:3
2024-05-06 10:59:05.847 Error: ebus: Cannot find usable field for device f43:setpoints.saturday:3
2024-05-06 10:59:05.848 Error: ebus: Cannot find usable field for device f43:setpoints.sunday:3
2024-05-06 10:59:05.849 Error: ebus: Cannot find usable field for device f43:setpoints.thursday:3
2024-05-06 10:59:05.850 Error: ebus: Cannot find usable field for device f43:setpoints.tuesday:3
2024-05-06 10:59:05.850 Error: ebus: Cannot find usable field for device f43:setpoints.wednesday:3
2024-05-06 10:59:05.865 Error: ebus: Cannot find usable field for device mc:hctimer.friday:7
2024-05-06 10:59:05.868 Error: ebus: Cannot find usable field for device mc:hctimer.monday:7
2024-05-06 10:59:05.871 Error: ebus: Cannot find usable field for device mc:hctimer.saturday:7
2024-05-06 10:59:05.874 Error: ebus: Cannot find usable field for device mc:hctimer.sunday:7
2024-05-06 10:59:05.877 Error: ebus: Cannot find usable field for device mc:hctimer.thursday:7
2024-05-06 10:59:05.879 Error: ebus: Cannot find usable field for device mc:hctimer.tuesday:7
2024-05-06 10:59:05.882 Error: ebus: Cannot find usable field for device mc:hctimer.wednesday:7
2024-05-06 10:59:05.886 Error: ebus: Cannot find usable field for device mc:setpoints.friday:3
2024-05-06 10:59:05.887 Error: ebus: Cannot find usable field for device mc:setpoints.monday:3
2024-05-06 10:59:05.888 Error: ebus: Cannot find usable field for device mc:setpoints.saturday:3
2024-05-06 10:59:05.888 Error: ebus: Cannot find usable field for device mc:setpoints.sunday:3
2024-05-06 10:59:05.889 Error: ebus: Cannot find usable field for device mc:setpoints.thursday:3
2024-05-06 10:59:05.890 Error: ebus: Cannot find usable field for device mc:setpoints.tuesday:3
2024-05-06 10:59:05.891 Error: ebus: Cannot find usable field for device mc:setpoints.wednesday:3
2024-05-06 10:59:06.113 ebus: Acquiring GIL for 'CPluginTransportTCP::handleRead'
2024-05-06 10:59:06.113 Queued asynchronous read aborted (192.168.1.2:8889), [2] End of file.
2024-05-06 10:59:06.113 ebus: Pushing 'DisconnectedEvent' on to queue
2024-05-06 10:59:06.144 ebus: Processing 'DisconnectedEvent' message
2024-05-06 10:59:06.144 ebus: Acquiring GIL for 'DisconnectedEvent'
2024-05-06 10:59:06.144 ebus: Disconnect event received for '192.168.1.2:8889'.
2024-05-06 10:59:06.144 ebus: Pushing 'onDisconnectCallback' on to queue
2024-05-06 10:59:06.144 ebus: Acquiring GIL for 'DisconnectedEvent'
2024-05-06 10:59:06.144 ebus: Processing 'onDisconnectCallback' message
2024-05-06 10:59:06.144 ebus: Acquiring GIL for 'onDisconnectCallback'
2024-05-06 10:59:06.144 ebus: Calling message handler 'onDisconnect' on 'module' type object.
2024-05-06 10:59:06.144 ebus: onDisconnect called
2024-05-06 10:59:06.144 ebus: Acquiring GIL for 'onDisconnectCallback'
2024-05-06 10:59:34.037 ebus: Pushing 'onHeartbeatCallback' on to queue
2024-05-06 10:59:34.087 ebus: Processing 'onHeartbeatCallback' message
2024-05-06 10:59:34.087 ebus: Acquiring GIL for 'onHeartbeatCallback'
2024-05-06 10:59:34.088 ebus: Calling message handler 'onHeartbeat' on 'module' type object.
2024-05-06 10:59:34.088 ebus: onHeartbeat() called
2024-05-06 10:59:34.088 ebus: Acquiring GIL for 'onHeartbeatCallback'

[Barberousse]

Hi. I try run this plugin but I don't see any devices
I have clicked "allow add device for 5 minutes" in settings.

Sorry but the log seems incomplete, could you post more, from "Search pattern is"? And you should have messages like "Add register" or "Cannot add register" at the end.

[Barberousse]

And by the way, I just uploaded a new version to improve a bit debug messages.

[fantom]

I waited 5 minutes

Code: Select all

2024-05-06 15:12:37.894 Status: New sensors allowed for 5 minutes...
2024-05-06 15:12:43.498 Status: ebus: Started.
2024-05-06 15:12:43.498 Status: ebus: Entering work loop.
2024-05-06 15:12:43.657 Status: ebus: Initialized version 2.0.3, author 'Barberousse'
2024-05-06 15:12:44.215 ebus: Look for field 2 in JSON data
2024-05-06 15:12:44.215 ebus: Look for field 3 in JSON data
2024-05-06 15:12:44.215 ebus: Look for field 4 in JSON data
2024-05-06 15:12:44.215 ebus: Look for field 5 in JSON data
2024-05-06 15:12:44.216 ebus: Look for field 6 in JSON data
2024-05-06 15:12:44.216 ebus: Look for field 7 in JSON data
2024-05-06 15:12:44.216 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.216 ebus: Look for field curve in JSON data
2024-05-06 15:12:44.216 ebus: Field number of register mc:heatingcurve:curve is 0
2024-05-06 15:12:44.216 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.217 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.217 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.217 ebus: Look for field yesno in JSON data
2024-05-06 15:12:44.217 ebus: Field number of register mc:isinbankholiday:yesno is 0
2024-05-06 15:12:44.217 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.217 ebus: Look for field yesno in JSON data
2024-05-06 15:12:44.217 ebus: Field number of register mc:isinholiday:yesno is 0
2024-05-06 15:12:44.217 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.217 ebus: Look for field yesno in JSON data
2024-05-06 15:12:44.217 ebus: Field number of register mc:isinimpactventilation:yesno is 0
2024-05-06 15:12:44.217 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.217 ebus: Look for field yesno in JSON data
2024-05-06 15:12:44.218 ebus: Field number of register mc:isinonedaybankholiday:yesno is 0
2024-05-06 15:12:44.218 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.218 ebus: Look for field yesno in JSON data
2024-05-06 15:12:44.218 ebus: Field number of register mc:isinonedayholiday:yesno is 0
2024-05-06 15:12:44.218 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.218 ebus: Look for field yesno in JSON data
2024-05-06 15:12:44.218 ebus: Field number of register mc:isinparty:yesno is 0
2024-05-06 15:12:44.218 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.218 ebus: Look for field yesno in JSON data
2024-05-06 15:12:44.218 ebus: Field number of register mc:isinsystemoff:yesno is 0
2024-05-06 15:12:44.218 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.218 ebus: Look for field percents in JSON data
2024-05-06 15:12:44.219 ebus: Field number of register mc:mixer1dutycycle:percents is 0
2024-05-06 15:12:44.219 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.219 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.219 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.219 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.219 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.219 ebus: Look for field temp in JSON data
2024-05-06 15:12:44.219 ebus: Field number of register mc:pstempdesired:temp is 0
2024-05-06 15:12:44.219 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.219 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.220 ebus: Look for field temp1 in JSON data
2024-05-06 15:12:44.220 ebus: Field number of register mc:setpoints.friday:temp1 is 0
2024-05-06 15:12:44.220 ebus: Look for field 1 in JSON data
2024-05-06 15:12:44.220 ebus: Look for field 2 in JSON data
2024-05-06 15:12:44.220 ebus: Look for field 3 in JSON data
2024-05-06 15:12:44.220 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.220 ebus: Look for field temp1 in JSON data
2024-05-06 15:12:44.220 ebus: Field number of register mc:setpoints.monday:temp1 is 0
2024-05-06 15:12:44.220 ebus: Look for field 1 in JSON data
2024-05-06 15:12:44.221 ebus: Look for field 2 in JSON data
2024-05-06 15:12:44.221 ebus: Look for field 3 in JSON data
2024-05-06 15:12:44.221 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.221 ebus: Look for field temp1 in JSON data
2024-05-06 15:12:44.221 ebus: Field number of register mc:setpoints.saturday:temp1 is 0
2024-05-06 15:12:44.221 ebus: Look for field 1 in JSON data
2024-05-06 15:12:44.221 ebus: Look for field 2 in JSON data
2024-05-06 15:12:44.222 ebus: Look for field 3 in JSON data
2024-05-06 15:12:44.222 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.222 ebus: Look for field temp1 in JSON data
2024-05-06 15:12:44.222 ebus: Field number of register mc:setpoints.sunday:temp1 is 0
2024-05-06 15:12:44.222 ebus: Look for field 1 in JSON data
2024-05-06 15:12:44.222 ebus: Look for field 2 in JSON data
2024-05-06 15:12:44.222 ebus: Look for field 3 in JSON data
2024-05-06 15:12:44.223 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.223 ebus: Look for field temp1 in JSON data
2024-05-06 15:12:44.223 ebus: Field number of register mc:setpoints.thursday:temp1 is 0
2024-05-06 15:12:44.223 ebus: Look for field 1 in JSON data
2024-05-06 15:12:44.223 ebus: Look for field 2 in JSON data
2024-05-06 15:12:44.223 ebus: Look for field 3 in JSON data
2024-05-06 15:12:44.223 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.224 ebus: Look for field temp1 in JSON data
2024-05-06 15:12:44.224 ebus: Field number of register mc:setpoints.tuesday:temp1 is 0
2024-05-06 15:12:44.224 ebus: Look for field 1 in JSON data
2024-05-06 15:12:44.224 ebus: Look for field 2 in JSON data
2024-05-06 15:12:44.224 ebus: Look for field 3 in JSON data
2024-05-06 15:12:44.224 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.224 ebus: Look for field temp1 in JSON data
2024-05-06 15:12:44.224 ebus: Field number of register mc:setpoints.wednesday:temp1 is 0
2024-05-06 15:12:44.225 ebus: Look for field 1 in JSON data
2024-05-06 15:12:44.225 ebus: Look for field 2 in JSON data
2024-05-06 15:12:44.225 ebus: Look for field 3 in JSON data
2024-05-06 15:12:44.225 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.225 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.225 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.225 ebus: Look for field temp1 in JSON data
2024-05-06 15:12:44.225 ebus: Field number of register mc:tempdesiredhigh:temp1 is 0
2024-05-06 15:12:44.226 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.226 ebus: Look for field temp1 in JSON data
2024-05-06 15:12:44.226 ebus: Field number of register mc:tempdesiredlow:temp1 is 0
2024-05-06 15:12:44.226 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.226 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.226 ebus: Look for field time in JSON data
2024-05-06 15:12:44.226 ebus: Field number of register mc:time:time is 0
2024-05-06 15:12:44.226 ebus: Look for field 0 in JSON data
2024-05-06 15:12:44.226 ebus: Look for field bday in JSON data
2024-05-06 15:12:44.226 ebus: Field number of register mc:weekday:bday is 0
2024-05-06 15:12:44.078 Error: ebus: Cannot find usable field for device bai:setmode:10
2024-05-06 15:12:44.079 Error: ebus: Cannot find usable field for device bai:setmode:11
2024-05-06 15:12:44.102 Error: ebus: Cannot find usable field for device f43:cctimer.friday:7
2024-05-06 15:12:44.104 Error: ebus: Cannot find usable field for device f43:cctimer.monday:7
2024-05-06 15:12:44.107 Error: ebus: Cannot find usable field for device f43:cctimer.saturday:7
2024-05-06 15:12:44.110 Error: ebus: Cannot find usable field for device f43:cctimer.sunday:7
2024-05-06 15:12:44.113 Error: ebus: Cannot find usable field for device f43:cctimer.thursday:7
2024-05-06 15:12:44.115 Error: ebus: Cannot find usable field for device f43:cctimer.tuesday:7
2024-05-06 15:12:44.118 Error: ebus: Cannot find usable field for device f43:cctimer.wednesday:7
2024-05-06 15:12:44.132 Error: ebus: Cannot find usable field for device f43:hctimer.friday:7
2024-05-06 15:12:44.135 Error: ebus: Cannot find usable field for device f43:hctimer.monday:7
2024-05-06 15:12:44.138 Error: ebus: Cannot find usable field for device f43:hctimer.saturday:7
2024-05-06 15:12:44.141 Error: ebus: Cannot find usable field for device f43:hctimer.sunday:7
2024-05-06 15:12:44.143 Error: ebus: Cannot find usable field for device f43:hctimer.thursday:7
2024-05-06 15:12:44.146 Error: ebus: Cannot find usable field for device f43:hctimer.tuesday:7
2024-05-06 15:12:44.149 Error: ebus: Cannot find usable field for device f43:hctimer.wednesday:7
2024-05-06 15:12:44.155 Error: ebus: Cannot find usable field for device f43:hwctimer.friday:7
2024-05-06 15:12:44.158 Error: ebus: Cannot find usable field for device f43:hwctimer.monday:7
2024-05-06 15:12:44.161 Error: ebus: Cannot find usable field for device f43:hwctimer.saturday:7
2024-05-06 15:12:44.164 Error: ebus: Cannot find usable field for device f43:hwctimer.sunday:7
2024-05-06 15:12:44.166 Error: ebus: Cannot find usable field for device f43:hwctimer.thursday:7
2024-05-06 15:12:44.169 Error: ebus: Cannot find usable field for device f43:hwctimer.tuesday:7
2024-05-06 15:12:44.172 Error: ebus: Cannot find usable field for device f43:hwctimer.wednesday:7
2024-05-06 15:12:44.179 Error: ebus: Cannot find usable field for device f43:setpoints.friday:3
2024-05-06 15:12:44.180 Error: ebus: Cannot find usable field for device f43:setpoints.monday:3
2024-05-06 15:12:44.181 Error: ebus: Cannot find usable field for device f43:setpoints.saturday:3
2024-05-06 15:12:44.182 Error: ebus: Cannot find usable field for device f43:setpoints.sunday:3
2024-05-06 15:12:44.183 Error: ebus: Cannot find usable field for device f43:setpoints.thursday:3
2024-05-06 15:12:44.183 Error: ebus: Cannot find usable field for device f43:setpoints.tuesday:3
2024-05-06 15:12:44.184 Error: ebus: Cannot find usable field for device f43:setpoints.wednesday:3
2024-05-06 15:12:44.199 Error: ebus: Cannot find usable field for device mc:hctimer.friday:7
2024-05-06 15:12:44.202 Error: ebus: Cannot find usable field for device mc:hctimer.monday:7
2024-05-06 15:12:44.205 Error: ebus: Cannot find usable field for device mc:hctimer.saturday:7
2024-05-06 15:12:44.208 Error: ebus: Cannot find usable field for device mc:hctimer.sunday:7
2024-05-06 15:12:44.211 Error: ebus: Cannot find usable field for device mc:hctimer.thursday:7
2024-05-06 15:12:44.213 Error: ebus: Cannot find usable field for device mc:hctimer.tuesday:7
2024-05-06 15:12:44.216 Error: ebus: Cannot find usable field for device mc:hctimer.wednesday:7
2024-05-06 15:12:44.220 Error: ebus: Cannot find usable field for device mc:setpoints.friday:3
2024-05-06 15:12:44.221 Error: ebus: Cannot find usable field for device mc:setpoints.monday:3
2024-05-06 15:12:44.222 Error: ebus: Cannot find usable field for device mc:setpoints.saturday:3
2024-05-06 15:12:44.223 Error: ebus: Cannot find usable field for device mc:setpoints.sunday:3
2024-05-06 15:12:44.223 Error: ebus: Cannot find usable field for device mc:setpoints.thursday:3
2024-05-06 15:12:44.224 Error: ebus: Cannot find usable field for device mc:setpoints.tuesday:3
2024-05-06 15:12:44.225 Error: ebus: Cannot find usable field for device mc:setpoints.wednesday:3
2024-05-06 15:17:38.499 Status: Receiving of new sensors disabled!...
2024-05-06 15:18:13.062 ebus: Connect
2024-05-06 15:18:13.112 ebus: onConnect for json called
2024-05-06 15:18:13.112 ebus: Find
2024-05-06 15:18:13.191 ebus: Good Response received from ebusd : length 236137

and with the newest version of plugin

Code: Select all

2024-05-06 17:27:43.632 ebus: Exclude mc:pstempdesired:temp based on exclude pattern and field id
2024-05-06 17:27:43.632 ebus: Look for register mc:pumpsavingstate:0 in JSON data
2024-05-06 17:27:43.632 ebus: Exclude mc:pumpsavingstate:0 based on exclude pattern and field id
2024-05-06 17:27:43.632 ebus: Look for register mc:setpoints.friday:0 in JSON data
2024-05-06 17:27:43.632 ebus: Exclude mc:setpoints.friday:0 based on exclude pattern and field id
2024-05-06 17:27:43.632 ebus: Look for register mc:setpoints.friday:temp1 in JSON data
2024-05-06 17:27:43.632 ebus: Field number of register mc:setpoints.friday:temp1 is 0
2024-05-06 17:27:43.632 ebus: Exclude mc:setpoints.friday:temp1 based on exclude pattern and field id
2024-05-06 17:27:43.632 ebus: Look for register mc:setpoints.friday:1 in JSON data
2024-05-06 17:27:43.632 ebus: Exclude mc:setpoints.friday:1 based on exclude pattern and field id
2024-05-06 17:27:43.632 ebus: Look for register mc:setpoints.friday:2 in JSON data
2024-05-06 17:27:43.632 ebus: Exclude mc:setpoints.friday:2 based on exclude pattern and field id
2024-05-06 17:27:43.633 ebus: Look for register mc:setpoints.friday:3 in JSON data
2024-05-06 17:27:43.633 ebus: Look for register mc:setpoints.monday:0 in JSON data
2024-05-06 17:27:43.633 ebus: Exclude mc:setpoints.monday:0 based on exclude pattern and field id

[Barberousse]

I waited 5 minutes

This is still incomplete, I don't understand why, I expected to see the search and the exclude patterns. What did you use in "Registers" configuration of the plugin? Lots of messages are excluded...

[fantom]

This is whole log.
And after few hours:

Code: Select all

2024-05-06 18:50:18.144 Error: ebus: Cannot find usable field for device mc:setpoints.thursday:3
2024-05-06 18:50:18.145 Error: ebus: Cannot find usable field for device mc:setpoints.tuesday:3
2024-05-06 18:50:18.146 Error: ebus: Cannot find usable field for device mc:setpoints.wednesday:3
2024-05-06 20:20:47.087 ebus: Connect
2024-05-06 20:20:47.138 ebus: onConnect for json called
2024-05-06 20:20:47.138 ebus: Find
2024-05-06 20:20:47.218 ebus: Good Response received from ebusd : length 235832
2024-05-06 20:20:47.218 ebus: Parsing JSON data
2024-05-06 20:20:47.405 ebus: No new messages to parse, will try again later
2024-05-06 20:31:17.073 ebus: Connect
2024-05-06 20:31:17.124 ebus: onConnect for json called
2024-05-06 20:31:17.124 ebus: Find
2024-05-06 20:31:17.211 ebus: Good Response received from ebusd : length 235832
2024-05-06 20:31:17.211 ebus: Parsing JSON data
2024-05-06 20:31:17.375 ebus: No new messages to parse, will try again later

[Barberousse]

This is whole log.

No, some messages are missing, with the last version 2.0.4, between "Parsing JSON data" and the first "Look for register xxx" I should have "Search pattern is xxx" and "Exclude pattern is xxx", I need them to help you, or you must give me the content you have in "Registers" parameters of the plugin. Or you can click on "Modify" in plugin parameters, and you should see in log some messages like "This plugin is compatible with Domoticz version 2024.1 onwards" and other messages about plugin parameters that you could post here, that would be helpful. And this will restart the "Parsing JSON data" where you will see the search pattern and exclude pattern.

[fantom]

full log attached
The first "Parsing JSON data" will probably appear in a few hours.
EDIT: It appear now.

[fantom]

Settings attached

[Barberousse]

Settings attached

Thank you, I think I'm able to reproduce your problem. Could you try version 2.0.5?

[fantom]

Yeah !
Now I see hundreds of devices
And i need to check, what is important.

Which ones are worth keeping and which ones should be deleted?
Is there a list somewhere that "translates" these names?
Some of them talk a little, but not completely.

[Barberousse]

Which ones are worth keeping and which ones should be deleted?
Is there a list somewhere that "translates" these names?
Some of them talk a little, but not completely.

I pushed a 2.0.7 version that fixes some discovery problems.
Which ones are important depends on what you need. My setup is:

read/write :

Code: Select all

broadcast:outsidetemp f47:RoomTemp f47:Hc1OPMode mc:InternalOperatingMode470 mc:Flow1Sensor mc:FlowTempDesired bai:FlowTemp bai:ReturnTemp bai:FlowTempDesired bai:StorageTemp f47:Hc1SFMode f47:Hc2SFMode bai:WaterPressure f47:Hc1HolidayStartPeriod f47:Hc1HolidayEndPeriod f47:Hc2HolidayStartPeriod f47:Hc2HolidayEndPeriod !:sensor$

read only :

Code: Select all

bai:HwcDemand f47:Hc1Pump mc:Hc2pDemand mc:IsInHoliday !:sensor$

[fantom]

I have a few proposal:
1) not always temperature have correct device type (custom sensor instead temp sensor)
2) many devices have state like on/off, yes/no. Maybe they also should be contact type instead general text ? Unless there may be a third state there (auto etc)
3) device with percentage, can be percentage type instead custom sensor
4) many devices send data to domoticz only one time at start hardware (or maybe very rarely). Domoticz checks how long ago the data was sent and marks in red that there is no contact with the device. Maybe you need to send this data even though ebusd haven't changed it, etc.?