Hi, thanks for your answer.
Yes the percentage is inverted. The item is a rollershutter. The physical item is a Qubino Roller Shutter. I use still the OH 2.4 stable version.
The biggest problem atm that if i open or close the shutter, than it dont deliver the real value in % where it stay after the motor is off, and the power usage of the motor is not set back to 0 after the motor is off.
Here is a small copy from the log:
2019-07-29 10:57:44.340 [vent.ItemStateChangedEvent] - CurrentDate changed from 2019-07-29T10:56:44.351+0200 to 2019-07-29T10:57:44.351+0200
2019-07-29 10:58:01.696 [ome.event.ItemCommandEvent] - Item ‘Stairs_Shutter’ received command 50
2019-07-29 10:58:01.700 [nt.ItemStatePredictedEvent] - Stairs_Shutter predicted to become 50
2019-07-29 10:58:01.704 [vent.ItemStateChangedEvent] - Stairs_Shutter changed from 30 to 50
2019-07-29 10:58:03.272 [vent.ItemStateChangedEvent] - Stairs_Shutter changed from 50 to 21
2019-07-29 10:58:03.359 [vent.ItemStateChangedEvent] - Stairs_Shutter_Electric_Meter changed from 113.8 to 136.1
2019-07-29 10:58:03.362 [GroupItemStateChangedEvent] - Shutter_Electric_Meter changed from 113.8 to 136.1 through Stairs_Shutter_Electric_Meter
2019-07-29 10:58:44.341 [vent.ItemStateChangedEvent] - CurrentDate changed from 2019-07-29T10:57:44.351+0200 to 2019-07-29T10:58:44.352+0200
2019-07-29 10:59:44.341 [vent.ItemStateChangedEvent] - CurrentDate changed from 2019-07-29T10:58:44.352+0200 to 2019-07-29T10:59:44.353+0200
2019-07-29 11:00:44.348 [vent.ItemStateChangedEvent] - CurrentDate changed from 2019-07-29T10:59:44.353+0200 to 2019-07-29T11:00:44.353+0200
2019-07-29 11:01:44.343 [vent.ItemStateChangedEvent] - CurrentDate changed from 2019-07-29T11:00:44.353+0200 to 2019-07-29T11:01:44.354+0200
Yes, i used the autocalibration function and the invert percentage is set. the physical shutter is in the right position after the command, but the values which are showed in OH are wrong.
What type is the rollershutter ?
So the only problem left is wrong report of closure percentage ? (es macht keinen Spass, Leuten die Hilfe wollen alles aus der Nase ziehen zu müssen …)
Dann bitte frag eindeutig. Ich wurde gerne deine Frage beantworten, aber ich habe keine Ahnung, was du meinst unter “what type of rollershutter”
Sieht wie das hier aus.
Nee so läuft das nicht. Davon abgesehen daß man ja schon hätte darauf kommen können daß es um Config-Einstellungen geht und darum der Aktor gemeint gewesen sein muß, mußt Du solche Infos von Anfang an mitliefern.
Does the actuator send a zwave message with a report after you operate the shutter ?
Is your lifeline/association #1 pointing at the zwave controller ?
Sorry im a full newbie with this things. No it was associated to node1_1(dont know what this is) even if i changed that to controller before. Now i changed to controller again. I make a restart of openhab and Linux to see if the value stay and than i test the functionality again. I would report what i found out. Thanks for the advice. I would write soon
Make sure to use habmin rather than PaperUI to configure zwave devices.
To see messages, enable zwave debugging (and if you’re about to ask “how” now then go read the documentation please).
So the change is there just till i restart openhab. Not important if i set the association with Paper UI or with HABMIN, after i restart the openhab, in all association group except the first one stay node1_1, the first one is empty.
I copied the zwave log where i click the save button in habmin, maybe it helps. I hope i copied the right one:
There’s bugs in the display. Better use habmin as it’ll only updates changed parameters while PaperUI re-sets everything.
If I didn’t glance too fast it only contains association related messages. I’m looking for a shutter report. Did you change shutter state while recording the log ?
By this log i used the HABMIN.
No, the log is just about the setting the association, because after this i tried to restart the openhab and the association was gone again, so i tough maybe there is already a problem.
You wouldn’t see those msgs if the association didn’t work so it does as I said there’s a bug that can affect the display.
Now move on and generate a shutter report
The Shutter was on 100% so complet full, but showed a value of 56% and in off state a power usage of 111,7W.
By this position i sent a command to open to 50%. The shutter moved to the right position, but the value changed first from 56 to 50 and after this from 50 to 94(the value 94 shows a lot of time). The power consumption has changed from 111,7W to 138,9W and stayed there even after the motor is off and the power consumption should be 0W.
2019-07-29 14:47:18.703 [ome.event.ItemCommandEvent] - Item ‘Stairs_Shutter’ received command 100
2019-07-29 14:47:18.708 [nt.ItemStatePredictedEvent] - Stairs_Shutter predicted to become 100
2019-07-29 14:47:18.718 [vent.ItemStateChangedEvent] - Stairs_Shutter changed from 7 to 100
2019-07-29 14:47:20.287 [vent.ItemStateChangedEvent] - Stairs_Shutter changed from 100 to 56
2019-07-29 14:47:20.372 [vent.ItemStateChangedEvent] - Stairs_Shutter_Electric_Meter changed from 109.6 to 111.7
2019-07-29 14:47:20.376 [GroupItemStateChangedEvent] - Shutter_Electric_Meter changed from 109.6 to 111.7 through Stairs_Shutter_Electric_Meter
2019-07-29 14:47:52.231 [vent.ItemStateChangedEvent] - CurrentDate changed from 2019-07-29T14:46:52.202+0200 to 2019-07-29T14:47:52.202+0200
2019-07-29 14:47:56.220 [ome.event.ItemCommandEvent] - Item ‘Stairs_Shutter’ received command 50
2019-07-29 14:47:56.224 [nt.ItemStatePredictedEvent] - Stairs_Shutter predicted to become 50
2019-07-29 14:47:56.230 [vent.ItemStateChangedEvent] - Stairs_Shutter changed from 56 to 50
2019-07-29 14:47:57.799 [vent.ItemStateChangedEvent] - Stairs_Shutter changed from 50 to 94
2019-07-29 14:47:57.885 [vent.ItemStateChangedEvent] - Stairs_Shutter_Electric_Meter changed from 111.7 to 138.9
2019-07-29 14:47:57.888 [GroupItemStateChangedEvent] - Shutter_Electric_Meter changed from 111.7 to 138.9 through Stairs_Shutter_Electric_Meter
2019-07-29 14:48:52.234 [vent.ItemStateChangedEvent] - CurrentDate changed from 2019-07-29T14:47:52.202+0200 to 2019-07-29T14:48:52.204+0200
2019-07-29 14:49:52.235 [vent.ItemStateChangedEvent] - CurrentDate changed from 2019-07-29T14:48:52.204+0200 to 2019-07-29T14:49:52.205+0200
Here is the log from the time this happend: node9_1.txt (53.2 KB)
You are receiving reports but I don’t know why the actuator sends a wrong percentage. Eventually try calibrating again, try association #7 to controller (see manual) or go ask the manufacturer support.
Is it possible that a zWave actor delivers different values by the same command if absolut nothing changed? Not in Openhab and not in the actor settings?
Yesterday the item worked like this:
2019-07-30 21:11:35.759 [ome.event.ItemCommandEvent] - Item ‘Stairs_Shutter’ received command 25
2019-07-30 21:11:35.764 [nt.ItemStatePredictedEvent] - Stairs_Shutter predicted to become 25
2019-07-30 21:11:35.778 [vent.ItemStateChangedEvent] - Stairs_Shutter changed from 100 to 25
2019-07-30 21:12:02.236 [ome.event.ItemCommandEvent] - Item ‘Stairs_Shutter’ received command DOWN
2019-07-30 21:12:02.238 [nt.ItemStatePredictedEvent] - Stairs_Shutter predicted to become DOWN
2019-07-30 21:12:02.248 [vent.ItemStateChangedEvent] - Stairs_Shutter changed from 25 to 100
Than i went to sleep and today without any change it works like:
019-07-31 07:15:47.849 [ome.event.ItemCommandEvent] - Item ‘Stairs_Shutter’ received command UP
2019-07-31 07:15:47.853 [nt.ItemStatePredictedEvent] - Stairs_Shutter predicted to become UP
2019-07-31 07:15:47.865 [vent.ItemStateChangedEvent] - Stairs_Shutter changed from 100 to 0
2019-07-31 07:15:49.429 [vent.ItemStateChangedEvent] - Stairs_Shutter changed from 0 to 94
2019-07-31 07:15:49.516 [vent.ItemStateChangedEvent] - Stairs_Shutter_Electric_Meter changed from 0 to 146
2019-07-31 07:15:49.518 [GroupItemStateChangedEvent] - Shutter_Electric_Meter changed from 0 to 146 through Stairs_Shutter_Electric_Meter
After i restarted the Linux, the functionality from yesterday is back, and the % is shown, but no power consumption. that would be even ok, but if i use the wall switch, no value would delivered to openhab.
huh? Of course. Your log shows a ‘DOWN’ and later an ‘UP’ command is sent to the actuator so of course there’s different actions taken thus different outcome.
I just copied the wrong row, UP or DOWN or SET 20, if the same command was send, the info was different. Here are the same commands like where worked:
2019-07-31 12:07:49.082 [vent.ItemStateChangedEvent] - CurrentDate changed from 2019-07-31T12:06:49.077+0200 to 2019-07-31T12:07:49.078+0200
2019-07-31 12:08:08.444 [ome.event.ItemCommandEvent] - Item ‘Stairs_Shutter’ received command 25
2019-07-31 12:08:08.446 [nt.ItemStatePredictedEvent] - Stairs_Shutter predicted to become 25
2019-07-31 12:08:08.449 [vent.ItemStateChangedEvent] - Stairs_Shutter changed from 100 to 25
2019-07-31 12:08:10.013 [vent.ItemStateChangedEvent] - Stairs_Shutter changed from 25 to 94
2019-07-31 12:08:10.095 [vent.ItemStateChangedEvent] - Stairs_Shutter_Electric_Meter changed from 139.4 to 143.2
019-07-31 12:08:57.739 [ome.event.ItemCommandEvent] - Item ‘Stairs_Shutter’ received command DOWN
2019-07-31 12:08:57.741 [nt.ItemStatePredictedEvent] - Stairs_Shutter predicted to become DOWN
2019-07-31 12:08:57.748 [vent.ItemStateChangedEvent] - Stairs_Shutter changed from 25 to 100
2019-07-31 12:08:59.312 [vent.ItemStateChangedEvent] - Stairs_Shutter changed from 100 to 32
2019-07-31 12:08:59.395 [vent.ItemStateChangedEvent] - Stairs_Shutter_Electric_Meter changed from 0 to 144.6
This is not an answer to the command but a report. It will report the percentage at that moment in time, eventually the shutter is still moving i.e. has not reached the target position yet.
Btw enable ZWave debug and see openhab.log not events.log as you do.
