Page 8 of 9
Re: Python Plugin: ebusd
Posted: Wednesday 08 May 2024 17:37
by fantom
And after one day I see only:
Code: Select all
2024-05-08 17:14:51.885 Error: ebus hardware (13) thread seems to have ended unexpectedly
Re: Python Plugin: ebusd
Posted: Wednesday 08 May 2024 20:34
by Barberousse
Hello,
fantom wrote: ↑Tuesday 07 May 2024 13:38
1) not always temperature have correct device type (custom sensor instead temp sensor)
I see here
https://github.com/john30/ebusd-configu ... 15.f43.csv that HolidayRoomTemp is declared as D1C, I don't know the difference with temp, but ok, I will add that to plugin translation.
fantom wrote: ↑Tuesday 07 May 2024 13:38
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)
It should be contact type. Please check that you have 2.0.7 plugin version, try to delete the devices and go to plugin parameter and click on Modify, it will relaunch auto discovery, maybe it's because of a bug I fixed since.
fantom wrote: ↑Tuesday 07 May 2024 13:38
3) device with percentage, can be percentage type instead custom sensor
You're right, I never encountered percentage myself in my ebus configuration, I will try to add it to plugin translation.
fantom wrote: ↑Tuesday 07 May 2024 13:38
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.?
That's already something I do for pressure and temperature, I can extend that behavior to other data types we identify
Re: Python Plugin: ebusd
Posted: Wednesday 08 May 2024 20:36
by Barberousse
fantom wrote: ↑Wednesday 08 May 2024 17:37
And after one day I see only:
Code: Select all
2024-05-08 17:14:51.885 Error: ebus hardware (13) thread seems to have ended unexpectedly
How many devices do you have, what domoticz version? Do this still happen if you increase refresh rate?
Re: Python Plugin: ebusd
Posted: Wednesday 08 May 2024 20:51
by fantom
The newest version of domoticz .
About 500 devices from ebusd - I keep looking at what they are, that's why I didn't delete them.
Re: Python Plugin: ebusd
Posted: Wednesday 08 May 2024 20:57
by Barberousse
fantom wrote: ↑Tuesday 07 May 2024 13:38
1) not always temperature have correct device type (custom sensor instead temp sensor)
Could you send the content of
http://ipofebusddaemoncomputer:8889/data?def&write please?
Re: Python Plugin: ebusd
Posted: Wednesday 08 May 2024 21:13
by fantom
Barberousse wrote: ↑Wednesday 08 May 2024 20:34
fantom wrote: ↑Tuesday 07 May 2024 13:38
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)
It should be contact type. Please check that you have 2.0.7 plugin version, try to delete the devices and go to plugin parameter and click on Modify, it will relaunch auto discovery, maybe it's because of a bug I fixed since.
2.0.7
Re: Python Plugin: ebusd
Posted: Thursday 09 May 2024 9:09
by Barberousse
fantom wrote: ↑Wednesday 08 May 2024 20:51
The newest version of domoticz .
About 500 devices from ebusd - I keep looking at what they are, that's why I didn't delete them.
Please note that if you delete them, they will come back. You'll have to filter them first using the registers parameter, then delete them. Or create a new ebusd bridge hardware with registers containing the filter.
Re: Python Plugin: ebusd
Posted: Thursday 09 May 2024 9:17
by fantom
Yes. I deleted hardware and created again.
Re: Python Plugin: ebusd
Posted: Thursday 09 May 2024 17:32
by Barberousse
fantom wrote: ↑Thursday 09 May 2024 9:17
Yes. I deleted hardware and created again.
Indeed, I checked my code and deleting is not mandatory if the device type change, it's changed in Domoticz automatically.
I published a 2.0.8 version that map percentage devices, improve yes/no and on/off device type detection and add an option in read-only to prevent automatic adding of detected devices.
For the timed out devices, I think that this shows a real problem on this devices, for instance the eepromupdateactive you shown, on my boiler, I can't read it :
Code: Select all
telnet domotique 8888
Trying 192.168.0.105...
Connected to domotique.
Escape character is '^]'.
read -v -c mc monitoreeprominkonsinumber
ERR: invalid position
Do you have other examples of devices that time out, to check?
Re: Python Plugin: ebusd
Posted: Thursday 09 May 2024 18:18
by fantom
I looked at what happened after the changes.
I still see something like this
1) Maybe Fan device is better for 1/min
2) Domoticz have something like "counter" also. But I don't know how it works etc.
3) Who damages big numbers ? plugin or domotcz ?
Re: Python Plugin: ebusd
Posted: Thursday 09 May 2024 18:25
by fantom
Counter type, can storage a few types of data.
Re: Python Plugin: ebusd
Posted: Thursday 09 May 2024 18:33
by Barberousse
fantom wrote: ↑Thursday 09 May 2024 18:18
1) Maybe Fan device is better for 1/min
2) Domoticz have something like "counter" also. But I don't know how it works etc.
3) Who damages big numbers ? plugin or domotcz ?
1) I will check if other uses for 1/min unit before
2) I know counter quite well because I did some changes on it myself in Domoticz code. This is quite adapted to kWh for instance, but we have the same problem as other devices, the unit is missing to be sure to map data type correctly
3) Domoticz :
Code: Select all
read -v WaterpressureMeasureCounter
bai WaterpressureMeasureCounter =112
read -v PrEnergyCountHc1
bai PrEnergyCountHc1 =29915587
read -v FanMaxSpeedOperation
bai FanMaxSpeedOperation =5550
The plugin doesn't add the "+e07" itself
Re: Python Plugin: ebusd
Posted: Thursday 09 May 2024 18:33
by fantom
And maybe device on/off can have another type in domoticz ? "On/Off" instead "contact".
I'm not sure ...
Re: Python Plugin: ebusd
Posted: Thursday 09 May 2024 19:46
by Barberousse
fantom wrote: ↑Thursday 09 May 2024 18:33
And maybe device on/off can have another type in domoticz ? "On/Off" instead "contact".
I'm not sure ...
It depends if device is writable. If it is writable and you didn't set read-only in parameters, the device will be created as on/off. But you are free to change that by editing the device in Domoticz.
I published a version 2.0.9 which will create a fan custom sensor if type is 1/min. I didn't use counters because the way they work is very specific (you must maintain an absolute counter value, and add an increment at a regular basis).
Re: Python Plugin: ebusd
Posted: Thursday 09 May 2024 20:16
by fantom
Ok.
I also find in domoticz this "bug" with big numbers
https://www.domoticz.com/forum/viewtopi ... 60#p316760
Re: Python Plugin: ebusd
Posted: Thursday 09 May 2024 20:41
by fantom
Devices with sec and min can also be time device (like hour)
And devices like hh:mm and hh:mm:ss also can be time type ?
Re: Python Plugin: ebusd
Posted: Thursday 09 May 2024 20:44
by fantom
And i think this is bug. Domoticz shows the value incorrectly or plugin set bad value.
I don't know where these values (20, 30 etc) come from.
I think, svalue need to show this same what nvalue, or maybe text like "Mo-Fr" etc.
Edit: Ok. This nvalue is selector index * 10. That this is small bug for showing value I think.
Edit 2. But i don't know, what do You set in nvalue?
Re: Python Plugin: ebusd
Posted: Thursday 09 May 2024 21:34
by Barberousse
fantom wrote: ↑Thursday 09 May 2024 20:44
Edit: Ok. This nvalue is selector index * 10. That this is small bug for showing value I think.
That's the normal behavior, Domoticz show the Set Level in devices tables (index of selector switch x 10 as you guessed), but in the interface, you should have a selector switch positioned at the right value.
Re: Python Plugin: ebusd
Posted: Thursday 09 May 2024 21:42
by fantom
Yeah. I will try fix it.
And what do You set in nvalue?
And i don't know, why first value on list is empty
ps. Maybe this need to be general/selector ? nor switch with level.
Re: Python Plugin: ebusd
Posted: Thursday 09 May 2024 22:39
by Barberousse
fantom wrote: ↑Thursday 09 May 2024 21:42
And what do You set in nvalue?
And i don't know, why first value on list is empty
ps. Maybe this need to be general/selector ? nor switch with level.
I think nvalue is ignored.
I need to check for first value empty, it's weird.
This should be general selector, I think you have text because you begun in read-only mode. In next version, I will change automatically the switch type when switching from read-only to read/write and from read/write to read-only.