I my setup (just added a GREE Thing manually) I works as expected:
23:58:01.535 [ndlerExecutor-1] INFO smarthome.event.ItemCommandEvent:53 - Item 'gree_airconditioner_89893c25_swingUpDown' received command 3
23:58:01.536 [ndlerExecutor-1] INFO smarthome.event.ItemStatePredictedEvent:53 - gree_airconditioner_89893c25_swingUpDown predicted to become NULL
23:58:22.292 [ndlerExecutor-1] INFO smarthome.event.ItemCommandEvent:53 - Item 'gree_airconditioner_89893c25_swingLeftRight' received command 3
23:58:22.293 [ndlerExecutor-1] INFO smarthome.event.ItemStatePredictedEvent:53 - gree_airconditioner_89893c25_swingLeftRight predicted to become NULL
23:58:48.115 [ndlerExecutor-1] INFO smarthome.event.ItemCommandEvent:53 - Item 'gree_airconditioner_89893c25_mode' received command eco
23:58:48.115 [ndlerExecutor-1] INFO smarthome.event.ItemStatePredictedEvent:53 - gree_airconditioner_89893c25_mode predicted to become NULL
MidLeft etc. als Options, which will be mapped to Numbers. I selected MidUp from swingUpDown selection list, which gets converted to 3
<channel-type id="swingUpDown">
<item-type>Number</item-type>
<label>Swing Up/Down</label>
<description>Sets the vertical swing action on the Air Conditioner: OFF: 0, Full Swing: 1, Up: 2, MidUp: 3, Mid: 4, Mid Down: 5, Down: 6</description>
<state>
<options>
<option value="0">OFF</option>
<option value="1">Full</option>
<option value="2">Up</option>
<option value="3">MidUp</option>
<option value="4">Mid</option>
<option value="5">MidDown</option>
<option value="6">Down</option>
</options>
</state>
</channel-type>
Same with swingLeftRight. I selected MidLeft, which gets converted to 3.
and I selected mode=Echo, which will be mapped to âecoâ. So far it looks good for me
Keep in mind: The verticalXXX channel was renamed to swingUpDown, swingLeftRight and quiet are new channels (my quiet is NAN, because I have no unit so it doesnât get filled)
.
I remaped all channels. As Swing channels were renamed and I used the old one caused the problem that Angle change was not working. Now I configured both new channels and tried. Both are operational and device gives a beep that receive the order. I deactivated SwingLeftRight as it does nothing on my device. GreeSwingUpDown works as it was before the change. So all channels are up & running. I have also tried auto discovery and it works as well. I use VisualStudio to manage my channels/items. Auto Create Items from Channels worked what means that auto item creation has to work in PaperUI as well I guess. If you need some log pls let me know. I turned on Trace logging of Gree binding and I can send if you need.
Thanks for the feedback, good jonđ
Did you tried temp changes? There were a lot of mini changes (data types) requested by the review. There is a bunch of outstanding ones, then I hope the review is done and we get jnto 2.5.6đ
@markus7017 Unfortunately, I canât test the new version. Iâm using OH 2.4 and new version bundle doesnât work.
2020-06-02 14:31:59.219 [WARN ] [org.apache.felix.fileinstall ] - Error while starting bundle: file:/openhab/addons/org.openhab.binding.gree-2.5.5-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.gree [236]
Unresolved requirement: Import-Package: com.google.gson; version=â[2.8.0,3.0.0)â
Iâve already had several approaches to upgrade my OH to 2.5 but each ended in instability and a problem with various bundles. I will probably try the latest version OH soon and then check your bundle.
I fixed various issues in the language resources (incl. code page, turbo/dry mixup, missing translations due to typos in the properties file)
Channel quiet was changed to strong values: off/auto/quit, it should also accept 0-2 as NumberType
However, the discovery feature is now broken, I implemented a requested change, but as a result GREE doesnât show up in PaperUI:Inbox:Scan. Iâm waiting on feedback from the reviewer.
Nevertheless you could help moving forward
delete your thing
re-add it manually just specifying the IP address
check for proper language resources
check that all functions are working
try out the new quiet channel commands
That would help to speed up the process while Iâm waiting on the feedback with regards to auto discovery (I assume itâs a little change).
Everything works except:
2020-06-07 17:10:39.959 [WARN ] [rest.core.internal.item.ItemResource] - Received HTTP POST request at âitems/GreeQuietâ with an invalid status value âONâ.
2020-06-07 17:10:45.485 [WARN ] [rest.core.internal.item.ItemResource] - Received HTTP POST request at âitems/GreeQuietâ with an invalid status value âOFFâ.
I think I need to change the item. What are the suitable statuses?
I need to check language settings if you want, just let me know how.
it seems working:
2020-06-07 20:37:04.608 [ome.event.ItemCommandEvent] - Item âGreeQuietâ received command auto
2020-06-07 20:37:04.609 [nt.ItemStatePredictedEvent] - GreeQuiet predicted to become auto
2020-06-07 20:37:04.609 [vent.ItemStateChangedEvent] - GreeQuiet changed from off to auto
2020-06-07 20:37:05.710 [ome.event.ItemCommandEvent] - Item âGreePowersaveâ received command ON
2020-06-07 20:37:05.710 [nt.ItemStatePredictedEvent] - GreePowersave predicted to become ON
2020-06-07 20:37:05.712 [vent.ItemStateChangedEvent] - GreePowersave changed from OFF to ON
but not on my machine
So I think it should work on a device where this option is avaiable.
did Ou removed and re-added the thing
did you used the latest build, this was the last fix I made and you have to change your item type to String (the binding still accepts nunber)
Hi,
I did a test for v. 2.5.6
Autodiscovery works fine.
I tried to add my AC twice: manually and via discovery and always Quiet mode is recognized as Number not String.
One question regarding Wind speed - which commands need to be send?
2020-06-08 09:59:28.247 [ome.event.ItemCommandEvent] - Item 'gree_airconditioner_f4911ec4bc25_windspeed' received command 1
2020-06-08 09:59:28.251 [nt.ItemStatePredictedEvent] - gree_airconditioner_f4911ec4bc25_windspeed predicted to become 1
2020-06-08 09:59:28.255 [WARN ] [ng.gree.internal.handler.GreeHandler] - Invalid command value 1 for channel windspeed
2020-06-08 09:59:28.259 [vent.ItemStateChangedEvent] - gree_airconditioner_f4911ec4bc25_windspeed changed from 1.0 to 1
2020-06-08 10:19:05.964 [vent.ItemStateChangedEvent] - gree_airconditioner_f4911ec4bc25_windspeed changed from 1.0 to 1970-01-01T00:00:03.000+0000
java.lang.RuntimeException: {"error":"partial write: field type conflict: input field \"value\" on measurement \"gree_airconditioner_f4911ec4bc25_windspeed\" is type float, already exists as type string dropped=1"}
Openhab restart didnât help
Above issue was related to influxdb where windspeed measurement was previously created as String. After dropping a measurement, there is not such error any more, but seems that my AC doesnât react on Wind speed changes
