Hello @massi,
First, thank you for your reply, support, and suggestions on resolving the issues.
I have good news! I managed my MyHomeServer1 (MHS1) work with the latest binding. I will try and detail to help others apply for the others with the same issue when moving beyond OH.4.1.1 and OpenWebNet’s latest binding.
After Massi’s reply, it was profoundly bugging me to find out why, while the documentation clearly states that A=0 should we WHERE=00, where is this set, and why it cannot be changed on MHS1?
I have been trying for more than three weeks, with lots of trial and error (lots of frustration and lots of heartbeats lost), to trigger a change of address until I struck gold.
The first time I tried was via MyHome_Suit (though if you read further, this is not needed), with the following steps (I was attempting to change A=0 P=9 to A=7 P=9 with the whole A=7 being unused):
- Updated switches to read A=7 linked to the actuator
- Send Config for the switch
- Update actuator from A=0 to A=7
- Send Config
- Diagnose the actuator (make sure it passes)
-
- Make sure lights work physically
- Go to my home control
- While the switch worked physically, I could not get it to work with my Control app, so I said the only solution was to delete it and see if that helped.
- Remove the actuator from all scenes (painful, I know)
- Delete Fully the Items (this is the primary action to ensure a new address gets assigned)
- Add the item back to the room/location (i.e., you have to set up a new item and link the actuator to the switch)
- Add the actuator to the scenes you deleted in point 9
- Go now to the Control app and add the light if needed
Interestingly enough, while I initially set the WHERE=79, it ended up with WHERE=21 (don’t ask me why (other than the fact that it was available); I reason that MHS1 decides the available address, with no option to force).
So, for the remaining eight items, I took a shortcut
- Go to my home+control app
- Remove the actuator from all scenes
- Delete Fully the Items (this is the primary action to ensure a new address gets assigned)
- Add the item back to the room (i.e., you have to set up a new item and link the actuator to the switch)
- Add the actuator to the scenes you deleted in point 2
- Go now to the Control app and add the light if needed
I did it one by one and not a bulk to be able to keep track if something fails (I did it over 2 days)
Interestingly, two items got new addresses, WHERE=10 (A=1 and P=0) and WHERE=20 (A=2 and P=0), which the new binding on OH4.3 did not like (this is a key issue with my MHS1 2-digit addresses). I witnessed the same behavior with the A=0 from P=1 to P=9 before and detailed in the abovementioned discussions.
Luckily, repeating the steps of deleting and adding gave new addresses that the binding liked, and they worked.
In summary, in MHS1, accessing the BUS or changing anything on it is impossible (not that I have figured it out yet, at least).
I noticed that anything with two digits in the address, for example, A=0 and P=2, will be broadcast on the MHS1 bus as Where=02 (does not work). On the other hand, A=0 and P=11 will be WHERE=0011 (works like a charm). In my view, this differentiation is the root cause of the issues with MHS1. For example, there is no way to enforce WHERE=02 to be sent on the bus as WHERE=0002.
Massi, I believe it would be good if you noted the above behavior of the 2-digit address on MHS1 for the future.
I am running the latest MHS1 firmware 2.84.09. I am now on OH4.3.2 and have been running smoothly for 24 hours.
I hope the above helps.
Thank you again @massi
Cheers,
Espresso