ok, maybe i get it.
If I'm right you shouldn't see any logs from the actuator.
This is because in order to be able to generate continuous transmission of the measurements from the actuator
it is necessary to make the request using the correct WHERE.
Requests are currently limited to 6 central units (from 51 to 56),
even if the maximum number should be 255, which is hardly reasonable for a house.
I try to add the request for the first 6 actuators (from 71 to 76),
6 seems to me a reasonable number also to avoid unnecessary requests.
The decoding of the received packet should be working,
therefore the device relating to the actuator should appear in the list of devices.
For example if the actuator is 71 the device id will be 00001247.
I've already made this addition and created a pull request on the development branch.
You can already use my git to test, or wait for the change to be added to the domoticz beta.
Let me know if it actually works
OpenWebNet developing..?
Moderator: leecollings
-
- Posts: 6
- Joined: Thursday 21 November 2019 13:39
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2023.1
- Location: Italy
- Contact:
Re: OpenWebNet developing..?
Impressive support, really! Many thanks
In the meantime I was able to do some more trials...
As you wrote, I could see the 51, but the 71 and 72 were not updated,
until I checked it with the MyHome_Web app, then the new devices appeared in domoticz,
but they were only updated when I opened the app.
I was looking for a script to do the request continuously, but if you can implement it in the domoticz core, even better...
In my opinion, 6 central units should be definitely enough,
but for the actuators I would add a few more if possible, I am already using 5 of them
and possibly I would add some more.
How does the ID decode work? In fact I really got 00001247/48 for the first 2
Do you have any idea when the next Beta version will be released? Eventually when the next official version will be released?
Again, many thanks, that was really helpful and appreciated!
In the meantime I was able to do some more trials...
As you wrote, I could see the 51, but the 71 and 72 were not updated,
until I checked it with the MyHome_Web app, then the new devices appeared in domoticz,
but they were only updated when I opened the app.
I was looking for a script to do the request continuously, but if you can implement it in the domoticz core, even better...
In my opinion, 6 central units should be definitely enough,
but for the actuators I would add a few more if possible, I am already using 5 of them
and possibly I would add some more.
How does the ID decode work? In fact I really got 00001247/48 for the first 2
Do you have any idea when the next Beta version will be released? Eventually when the next official version will be released?
Again, many thanks, that was really helpful and appreciated!
-
- Posts: 87
- Joined: Tuesday 29 March 2016 16:41
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Location: Italia
- Contact:
Re: OpenWebNet developing..?
Perfect, you did the test that was needed and confirms what I thought.
The ID is calculated like this:
WHO = 18 (0x12) power management
WHERE = 51..56 (0x33..0x38)
WHERE = 71..76 (0x47..04C)
0x0000 + WHO + WHERE
so for example:
first central unit = 0x00001233
first Actuator = 0x00001247
The change I made was integrated into the beta this morning.
If you go to the 'https://www.domoticz.com/downloads/' page you will see that the beta is updated almost daily.
The stable version I have no way of knowing when it will be released.
How many actuators would you like?
I may make the change in the next few days.
The ID is calculated like this:
WHO = 18 (0x12) power management
WHERE = 51..56 (0x33..0x38)
WHERE = 71..76 (0x47..04C)
0x0000 + WHO + WHERE
so for example:
first central unit = 0x00001233
first Actuator = 0x00001247
The change I made was integrated into the beta this morning.
If you go to the 'https://www.domoticz.com/downloads/' page you will see that the beta is updated almost daily.
The stable version I have no way of knowing when it will be released.
How many actuators would you like?
I may make the change in the next few days.
-
- Posts: 6
- Joined: Thursday 21 November 2019 13:39
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2023.1
- Location: Italy
- Contact:
Re: OpenWebNet developing..?
OK, ID calculation is clear now.
In the next days I will install the beta release and give it a try.
So far, 6 actuators are enough for me, no urgency to update it,
but in general I would expect 8 or 10 could cover more applications.
Many thanks
In the next days I will install the beta release and give it a try.
So far, 6 actuators are enough for me, no urgency to update it,
but in general I would expect 8 or 10 could cover more applications.
Many thanks
-
- Posts: 6
- Joined: Thursday 21 November 2019 13:39
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2023.1
- Location: Italy
- Contact:
Re: OpenWebNet developing..?
I installed the beta release of Domoticz,
F522 devices are now updated every few seconds, very good.
I will let you know if I see any issue
F522 devices are now updated every few seconds, very good.
I will let you know if I see any issue
Re: OpenWebNet developing..?
hello everyone,
please help me to understand what represent:
- TEMPERATURE Actuator
- TEMPERATURE Valves
- AUXILIARY
- DRYCONTACT
and the way to know the OpenWebNnet address from Domoticz ID
I think DRYCONTACT is F411 but maybe I am wrong
Thank you to who help me
please help me to understand what represent:
- TEMPERATURE Actuator
- TEMPERATURE Valves
- AUXILIARY
- DRYCONTACT
and the way to know the OpenWebNnet address from Domoticz ID
I think DRYCONTACT is F411 but maybe I am wrong
Thank you to who help me
-
- Posts: 87
- Joined: Tuesday 29 March 2016 16:41
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Location: Italia
- Contact:
Re: OpenWebNet developing..?
Hi Dino,
I'll try to answer you:
1- Temperature Actuator:
indicate the status of the thermoregulation actuators, such as the F430 module.
2- Temperature Valve:
indicates whether the valve is in Conditioning or Heating mode
3- Auxiliaries:
these are auxiliary signals that can be used to inform you of alarms in progress, for example flooding or other.
They can also be used for other purposes, for example you can set the home alarm on/off.
If this interests you, you can see examples in this thread.
4- DRY-CONTACT:
these are the signals that are read by the contact interface modules, for example the 3477 or F428
The ID is more complex, I'll try to explain it in a slightly simplified way.
For all these types, the ID is in hexadecimal and consists of 2 parts:
- the upper part which indicates the type of device
- the lower part indicating the device number
When a device is added automatically, the name is always composed of:
- the description of the type of device
- the device number
This in order to facilitate the identification of the device.
The light number is composed of ZONE + LIGHT POINT.
So the devices will be identified like this:
I'll try to answer you:
1- Temperature Actuator:
indicate the status of the thermoregulation actuators, such as the F430 module.
2- Temperature Valve:
indicates whether the valve is in Conditioning or Heating mode
3- Auxiliaries:
these are auxiliary signals that can be used to inform you of alarms in progress, for example flooding or other.
They can also be used for other purposes, for example you can set the home alarm on/off.
If this interests you, you can see examples in this thread.
4- DRY-CONTACT:
these are the signals that are read by the contact interface modules, for example the 3477 or F428
The ID is more complex, I'll try to explain it in a slightly simplified way.
For all these types, the ID is in hexadecimal and consists of 2 parts:
- the upper part which indicates the type of device
- the lower part indicating the device number
When a device is added automatically, the name is always composed of:
- the description of the type of device
- the device number
This in order to facilitate the identification of the device.
Finally, the status of the F411 actuators falls within WHO=1 or lighting.Example 1:
ID 01F8000C
Top part: hex 01F8 indicates that it is a Temperature actuator
Bottom part: hex 000C = 12 Indicates that it is Temperature actuator number 12
Name: 'TEMPERATURE 12 Actuator'
Example 2:
ID 00090001
Top: hex 0009 indicates that it is an auxiliary
Bottom part: hex 0001 = 1 Indicates that it is the auxiliary number 1
Name: 'AUXILIARY 1'
Example 3:
ID 00190024
Top part: hex 0019 indicates that it is a DRYCONTACT
Bottom part: hex 0024 = 36 Indicates that it is DRYCONTACT number 36
Name: 'DRYCONTACT 36'
The light number is composed of ZONE + LIGHT POINT.
So the devices will be identified like this:
I hope this helps.Top part: hex 0001 indicates that it is a light
Bottom part: hex 0024 = 42 or Z=4 LP=2
Name: 'LIGHT 42'
So the full ID will be: 00010024
Who is online
Users browsing this forum: No registered users and 1 guest