matchews
(Matchews)
July 11, 2023, 12:11pm
546
Here is the default list item widget config. It’s not just this one item. Every one of my items with command options is read only in the gui.
Item Config:
label: Filter Speed States
type: String
category: ""
groupNames:
- gHayward_Filter
groupType: None
function: null
tags:
- Point
Default List Item Widget Config
value: ""
config: {}
rlkoshak
(Rich Koshak)
July 11, 2023, 1:39pm
547
Has an issue been filed yet?
Based on the config the action looks correct.
Hint, it’s way better to click the Code tab and paste that with code fences compared to screen shots.
```
code goes here
```
matchews
(Matchews)
July 11, 2023, 4:10pm
548
Thanks Rich. I’ll post code next time. As for opening an issue, I’m running openHabian on bookworm on an intel NUC. I know this is frowned upon and could be my issue.
@michaeljoos ,
Are you running OpenHabian on a RasPi? If so, I can open an issue.
rlkoshak
(Rich Koshak)
July 11, 2023, 5:04pm
549
This shouldn’t have anything to do with how OH is installed. It’s a runtime issue, not an installation or deployment issue.
mstormi
(Markus Storm)
Split this topic
July 16, 2023, 10:55am
551
A post was split to a new topic: Zwave problem on new OH4 install
GunMaster
(Gunnar Fröwis)
July 16, 2023, 6:13pm
552
I’m runnig the OH 4.0.0.Mx milestone releases on Raspberry since they are available. Now on M4 sometimes back in between the milestones I noticed that rules took many seconds (maybe 5-8 secs) until they get executed for the first time.
Cannot remember that this problem existed for me with OH3.
For example when I press the “irrigation on” button in the ui nothing happens at first.
But it reads “RUNNING” in the rule for some really long seconds. As soon as the rule goes back to “IDLE” the irrigation switches to ON (i hear the clicking of the valve).
If I do the same a couples of times afterwards everything works fine. the rule executes instantly. (The valve clicks as soon as I press the button)
This is not a problem with this specific rule. The rules can be simple or long and complex the behaviour is the same.
Everytime I change a rule and it is called the first time the rule “hangs” in the “RUNNING” state and nothing happens for some seconds until its “IDLE” again. Executing again = instant.
This is very annoying when I alter a rule or make a new one because you have to wait each time until the code does what its intended to.
Would be glad if someone could help or is this by design?
That was a bug, it should be fixed in M5
GunMaster
(Gunnar Fröwis)
July 16, 2023, 6:58pm
554
Thanks for the information! Very appreciated
samtd
(Samuel)
July 16, 2023, 7:12pm
555
The version OH 4.0.0.M5 is release at Github.
However is missing in jfrog linux
1 Like
Kai
(Kai Kreuzer)
July 16, 2023, 7:39pm
556
You are absolutely right, I missed this by accident. It should now be there!
1 Like
helmar74
(Helmar)
July 16, 2023, 8:08pm
557
Hi,
just updated from M4 to M5 still the AVM Fritz Things are in state unknown:
getting this error in openhab.log:
2023-07-16 22:03:23.924 [WARN ] [ore.internal.thing.ThingTypeResource] - Cannot find channel type: system:electric-energy
It look’s like Milestone5 doesn’t fix the issue, that AVM Fritz 200/210 Sockets are in state unknown after updating.
I tried to readd the things, doesn’t help.
Automatic scan, doesn’t find the devices, if I delete them manually…
It was reported in #15155 but isn’t fixed yet
If anyone has an idea, what I can try, please tell me
J-N-K
(Jan N. Klug)
July 16, 2023, 8:20pm
558
Uh. That’s my fault. It’s electric-power
and electrical-energy
. That seems to be very inconsistent.
helmar74
(Helmar)
July 17, 2023, 4:36am
559
Hi thanks for the information.
Just to give you more details. This is a thing from OH 3.4.4 which is working well:
In OH 4.0.0 M5 channels are missing (e.g. energy):
One more strange thing. Some DECT200/210 are Unknown, some are Online. But also in the Online Things the channels above are missing:
I don’t get any Status changes (e.g. Temperature, Watt, kWh) in event.log for any of the DECT 200/210 Devices. It’s working well in OH 3.4.4
One line shown in openhab.log:
[WARN ] [ore.internal.thing.ThingTypeResource] - Cannot find channel type: system:electric-energy
If I delete a Thing and I do a rediscover, the thing doesn’t show up in Inbox.
I only can add them manually, which ends up in “unknown” Things.
For me it looks like there are more issues in the AVM Fritz binding
If there’s anything I can test or do, just ping me
helmar74
(Helmar)
July 17, 2023, 7:22am
560
J-N-K:
electric-power
I also compared thing-types.xml. On the left side the file of OH 3.4.4 Bundle, on the right side OH 4.0.0M5 Bundle:
It is really strange. For me it looks like no Device information runs between Fritzbox and Openhab…
Items for Incoming calls are working.
Fritzbox also shows, that the user, which is used in Openhab, is correct connected…
ubeaut
(Greg)
July 17, 2023, 9:37am
561
Milestone M5-1
Nashorn rules work but scripts do not work:
2023-07-17 19:35:47.502 [ERROR] [internal.handler.ScriptActionHandler] - Script execution of rule with UID ‘23d9c11913’ failed: org.graalvm.polyglot.PolyglotException: ReferenceError: “itemRegistry” is not defined
rlkoshak
(Rich Koshak)
July 17, 2023, 1:31pm
562
Scripts are rules. There shouldn’t be any difference.
How is this script called? Manually? From another rule? From a UI widget?
J-N-K
(Jan N. Klug)
July 17, 2023, 6:12pm
563
openhab:main
← J-N-K:avmfritz
opened 06:11PM - 17 Jul 23 UTC
<!--
Thanks for contributing to the openHAB project!
Please describe the goal … and effect of your PR here.
Pay attention to the below notes and to *the guidelines* for this repository.
Feel free to delete any comment sections in the template (starting with "<!--").
ATTENTION: Don't use "git merge" when working with your pull request branch!
This can clutter your Git history and make your PR unusable.
Use "git rebase" instead. See this forum post for further details:
https://community.openhab.org/t/rebase-your-code-or-how-to-fix-your-git-history-before-requesting-a-pull/129358
All PRs should be created using the "main" branch as base.
Important bugfixes are cherry-picked by maintainers to the patch release branch after a PR has been merged.
Add one or more appropriate labels to make your PR show up in the release notes.
E.g. enhancement, bug, documentation, new binding
This can only be done by yourself if you already contributed to this repo.
If your PR's code is not backward compatible with previous releases (which
should be avoided), add a message to the release notes by filing another PR:
https://github.com/openhab/openhab-distro/blob/main/distributions/openhab/src/main/resources/bin/update.lst
# Title
Provide a short summary in the *Title* above. It will show up in the release notes.
For example:
- [homematic] Improve communication with weak signal devices
- [timemachine][WIP] Initial contribution
# Description
Please give a few sentences describing the overall goals of the pull request.
Give enough details to make the improvement and changes of the PR understandable
to both developers and tech-savy users.
Please keep the following in mind:
- What is the classification of the PR, e.g. Bugfix, Improvement, Novel Addition, ... ?
- Did you describe the PRs motivation and goal?
- Did you provide a link to any prior discussion, e.g. an issue or community forum thread?
- Did you describe new features for the end user?
- Did you describe any noteworthy changes in usage for the end user?
- Was the documentation updated accordingly, e.g. the add-on README?
- Does your contribution follow the coding guidelines:
https://www.openhab.org/docs/developer/guidelines.html
- Did you check for any (relevant) issues from the static code analysis:
https://www.openhab.org/docs/developer/bindings/#include-the-binding-in-the-build
- Did you sign-off your work:
https://www.openhab.org/docs/developer/contributing.html#sign-your-work
# Testing
Your pull request will automatically be built and available under the following folder:
https://openhab.jfrog.io/ui/native/libs-pullrequest-local/org/openhab/addons/bundles/
It is a good practice to add a URL to your built JAR in this pull request description,
so it is easier for the community to test your Add-on.
If your pull request contains a new binding, it will likely take some time
before it is reviewed and processed by maintainers.
That said, consider submitting your Add-on in the Marketplace:
https://community.openhab.org/c/marketplace/69
Don't forget to submit a thread about your Add-on in the openHAB community:
https://community.openhab.org/c/add-ons
-->
openhab:main
← J-N-K:system-ct
opened 01:50PM - 17 Jul 23 UTC
These are only used by one binding at the moment and it's very inconsistent to h… ave power, voltage and current with the "electric" prefix and energy with "electrical".
<!--
Thanks for contributing to the openHAB project!
Please describe the goal and effect of your PR here.
Pay attention to the below notes and to *the guidelines* for this repository.
Feel free to delete any comment sections in the template (starting with "<!--").
ATTENTION: Don't use "git merge" when working with your pull request branch!
This can clutter your Git history and make your PR unusable.
Use "git rebase" instead. See this forum post for further details:
https://community.openhab.org/t/rebase-your-code-or-how-to-fix-your-git-history-before-requesting-a-pull/129358
All PRs should be created using the "main" branch as base.
Important bugfixes are cherry-picked by maintainers to the patch release branch after a PR has been merged.
If your PR's code is not backward compatible with previous releases (which
should be avoided), add a message to the release notes by filing another PR:
https://github.com/openhab/openhab-distro/blob/main/distributions/openhab/src/main/resources/bin/update.lst
# Title
Provide a short summary in the *Title* above. It will show up in the release notes.
For example:
- Introduce metadata for all add-ons
- Fix memory leak in ScriptedRuleProvider
# Description
Please give a few sentences describing the overall goals of the pull request.
Give enough details to make the improvement and changes of the PR understandable
to both developers and tech-savy users.
Please keep the following in mind:
- What is the classification of the PR, e.g. Bugfix, Improvement, Novel Addition, ... ?
- Did you describe the PRs motivation and goal?
- Did you provide a link to any prior discussion, e.g. an issue or community forum thread?
- Did you describe new features for the end user?
- Did you describe any noteworthy changes in usage for the end user?
- Was the documentation updated accordingly, e.g. the Core README?
- Does your contribution follow the coding guidelines:
https://www.openhab.org/docs/developer/guidelines.html
- Did you check for any (relevant) issues from the static code analysis?
- Did you sign-off your work:
https://www.openhab.org/docs/developer/contributing.html#sign-your-work
If your pull request contains a new contribution, it will likely take some time
before it is reviewed and processed by maintainers.
-->
Should fix the issues. After they are merged, pleas upgrade to the next snapshot to see if that really works.
helmar74
(Helmar)
July 17, 2023, 6:57pm
564
Hi
short question. Where can I download the snapshot version of the binding, once the fix is merged?