I understand that my entry here is a bit OT. Firstly I thought to open up a separate thread for but maybe it is easier found later on. If one is having the same kind of question.
I use the following devices (actually five):
And one channel here is a setpoint (marked yellow).
** Interestingly i configured the devices all in the same way. but one is showing a different value
I can confirm that the checkbox does not fully work anymore with M3. After the update, it first kept on working, but only since my browser had the old caches still in place. But after purging the caches to get access to the new developer sidebar, the checkbox does not work anymore. The āAdd Itemā command is still added to the list of commands, but the model does not show non-semantic items anymore.
As Bruce said, perhaps there isnāt much for you to upgrade now. But I can say definitively the longer you wait, the more work it will be too move to a new version should the need arise. If what you are running now works and as long as you donāt change anything (no system or os updates either) you might get many years out of it. but as soon as a third party changes their api, or a certificate expires, or the like you will largely be on your own unless you upgrade. The old bindingās ate no longer maintained and oh knowledge is fungable, there are fewer people who can help with old versions as time passes.
@Bruce_Osborne@rlkoshak thanks for taking time to respond to my questions and the points you make are very valid, especially as pertains to certificates and apiās such as the iCloud binding which I use in conjunction with the GPSTracker binding for geofencing and presence detection. Certainly those type of bindings, along with weather, are most likely to require more frequent updating and already have been moved to OH 3.0 in my test system which is federated using RemoteOpenHab and works amazingly well. My big issue is ISY/Insteon and to a lesser extent Panasonic and Epson where I have both a considerable monetary investment in hardware and use OH rules extensively to automate my household lighting, thermostat, sensors, leak detection, gates, garage doors, theater, etc. As you both point out, at the moment I am not missing anything by not moving to OH 3.0 and there is no urgency for me to migrate/federate my production system as long as my hardware remains viable and no major changes to the api are made, which I believe will be the case as these are well established technologies with a lot of legacy installations. In fact at the moment for this hardware there is no path forward to OH 3.0 anyway so my only option is to continue to run a 2.5.x install to support them. However, as I type this my thinking is evolving as to why and how best to move forward, so thanks again for sharing your perspectives.
Thatās great to see that this binding is being updated. I have a Panny Viera plasma. Do u think this is compatible? Is this going to be merged into an OH 3 build, or will it be a standalone/marketplace addon? Iād like to give it a shot if that is possible?
EDIT: Not sure how I missed it but I found the thread re Panasonic OH3 so I will dl and give it a try. Thanks.
Hi all.
I did the big jump today, from 2.x to 3.x. I was kinda nervous for everything breaking down, but the transition went really smooth! Big kudos for everyone involved in making this possible!
Currently Iām still fiddling around, trying to learn where to find everything in the new interface. Two small questions this far:
I get errors in the log about add-ons not existing anymore, like expire1, restdocs etc. Where do I need to remove those to make the warnings go away?
Minor UI glitch: The vertical scrollbar in the list of Things doesnāt work for me. The only way I can seem to scroll is using the keyboard up and down. This is in Firefox on Windows 10.
I am working on a test version of a binding. It seems that dropping the jar file in the addons folder does not automatically load it. Is this a bug? Or is there a work around?