Hi Markus.
On v4.0.1 I get the following error messages during a restart (binding release build):
2023-07-30 18:12:30.557 [WARN ] [core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'shelly:shellytrv:60a423dcc376' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
2023-07-30 18:12:30.562 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for thing 'shelly:shellytrv:60a423dcc376': {thing/channel=Type description shelly:deviceSchedule for shelly:shellytrv:60a423dcc376:device#schedule not found, although we checked the presence before.}
not sure what it means. Just wanted to bring this to your attention.
Auth with Plus/Pro devices fixed, now implementing RFC-based ohandling with http header attributes rather making auth part of the RPC message @DUSAG0211
various channel definitions have change, incl. device innerTemp, sensor temp, humidity, external sensor temp (add-on), relay voltage, current, supplyVoltage, currentWatts, lastPower1, accumulated*; please verify that units are correct and values are updated correctly. I’m using system: defined types rather than own definitions. Not for all channels, this requires refactoring of code and may break backward compatibility. You might need to delete and re-discover things, but first try it with the existing definitions.
Processing for Soap value boost was missing, now updating the boost channel. I still need to check the TRV targetTemp topic
@Spaceman_Spiff Did you created the DEBUG log? @Andy_Co This version def. has the vibration channel for motion, you might need to delete and re-discover your thing @mr.airworthy Please check the update, maybe this was related to the channel definitions @scheuerer This should fix HT humidity
Again, I kindly request you to support testing. Most of those issues could have been fixed before the 4.0 release. It’s hard to test The binding is supporting about 40 different devices, this make it hard to test all different configurations even @igi is doing a great job here.
Sorry Markus, it seems my problem with number:energy against number:power are not fixed in the latest DEV Binding from yesterday. When generating a new item still the wrong unit.
The same for humidity. I have had to delete the old item and create a new one that works.
In principal I have took my exisiting 4.0.1 system, deleted the binding, install the DEV binding, and restore my taken backup from the OH 3.4.4-1 system.
Thanks, this works now.
But I’m not sure if it is an Shelly-Binding issue or it is a gerneal OH issue.
In general the “TYPE” for the item itself with humidity is missing.
E.g. Temperature is there, but no humidity.
Did you tried the new DEV build, works fine for me and @igi
There is no dedicated humidity type (for whatever reason). It uses Number:Dimensionless (0…100%).
Yes I used the DEV build.
It would be very easy for us, to have by default the humidity as on own type, like temperature,
or why we have for temperature one, because those a also only values between - and + .