Originally posted by sirmeili
View Post
Announcement
Collapse
No announcement yet.
Logitech Local API Access - How to get the current version of the plugin to work
Collapse
This is a sticky topic.
X
X
-
Originally posted by Paul32 View PostSee error message in screenshot
Here's my error log which is pretty much identical to Paul32's
Jan-04 14:59:50 MeiHarmonyHub: Error The Connection to Hub with ID failed with stack trace: at System.Runtime.Serialization.Json.JsonSerializationReader.De serializeGenericCollection (System.Type collectionType, System.Type elementType) [0x00000] in :0 at System.Runtime.Serialization.Json.JsonSerializationReader.Re adObject (System.Type type) [0x00000] in :0 at System.Runtime.Serialization.Json.TypeMap.Deserialize (System.Runtime.Serialization.Json.JsonSerializationReader jsr) [0x00000] in :0 at System.Runtime.Serialization.Json.JsonSerializationReader.Re adObject (System.Type type) [0x00000] in :0 at System.Runtime.Serialization.Json.JsonSerializationReader.Re adRoot () [0x00000] in :0 at System.Runtime.Serialization.Json.DataContractJsonSerializer .ReadObject (System.Xml.XmlReader reader, Boolean verifyObjectName) [0x00000] in :0 Jan-04 14:59:50 MeiHarmonyHub: Error The Connection to Hub with ID failed with message: Expected element 'item', but found 'Harmony' in namespace ''. Error at (1,247)
Comment
-
This error is due to a third party library (Newtonsoft.Json) not parsing correctly on some linux Installs. I've verified the config coming back is correct, but it's not parsing it correctly (the same config will parse correctly on my windows machine). I will update the version of that library as I think there is a newer version and release it into the beta stream. I will report back once I have released it. I will try and get that done tonight for you all.
Comment
-
Originally posted by phoenix View PostOkay in my case it is caused by the Mono version. Once I updated Mono it is working. Thanks.
Comment
-
Originally posted by Paul32 View Post
I have: Mono JIT compiler version 3.2.8
As an aside, is this the linux version running a Pi or are you running the Pi version of HS3 (I want to keep track on which installs these issues happen).
Comment
-
Make sure you use Tools | Setup | Lab to export the events first before upgrade Mono. Then after Mono upgrade, use Import Events to import it back. Otherwise, all event triggers will be gone after upgrade from 3.2.8 to 5.x. I made that mistake to upgrade Mono without doing it. And then I had to roll it back to 3.8 to get my events back.
- Likes 1
Comment
-
Originally posted by sirmeili View Post
I think upgrading to mono 5 can fix this, but Obviously take a backup before doing it. Otherwise you might have to wait for me to try the new version of NewtonsoftJSON.
As an aside, is this the linux version running a Pi or are you running the Pi version of HS3 (I want to keep track on which installs these issues happen).
It is my "test" PI self made with HS3 Full (not a hometroller Zee)
I treid to upgrade mono, but no succeed yet
I did this lines:
sudo apt-get update
sudo apt-get upgrade
It was doing a lot!!
But still mono 3.2.8
But the good news is I enabled the plug-in on my running systeem (Self made HS3 Full SEL on Linux, with Mono JIT compiler version 5.4.1.6)
And it works
If you now how to upgrade mono, I can test it!
Comment
-
Originally posted by Paul32 View Post
Update:
It is my "test" PI self made with HS3 Full (not a hometroller Zee)
I treid to upgrade mono, but no succeed yet
I did this lines:
sudo apt-get update
sudo apt-get upgrade
It was doing a lot!!
But still mono 3.2.8
But the good news is I enabled the plug-in on my running systeem (Self made HS3 Full SEL on Linux, with Mono JIT compiler version 5.4.1.6)
And it works
If you now how to upgrade mono, I can test it!
Finaly i have: Mono JIT compiler version 5.10.1.20
And now it also works on my PI
Comment
-
mono --version
That will give you the mono JIT compiler version.
To upgrade Mono on the SEL follow HomeSeer's instruction below. But before doing so make sure to export events using Tools | Setup | Labs and click on Export Event to export it to a file on the HomeSeer. And after mono is upgraded and verified that version is 5.x use the Tools | Setup | Labs and click on Import Events to import it back. Otherwise all even triggers will be gone and you cannot edit to get it back. You have to create new ones.
Here's HomeSeer's own instruction on upgrade Mono
https://helpdesk.homeseer.com/articl...-sel-to-mono-5
It is probably better to perform the Mono upgrade using putty over ssh than using Linux tools over the web.
You can download putty client from https://www.chiark.greenend.org.uk/~...ty/latest.html
SSH to your homeseer and login as the same homeseer user. Then execute all the commands in the putty console instead of using Linux tools.
The mono version if you upgrade now should be
Mono JIT compiler version 5.18.0.225 (tarball Wed Jan 2 21:25:26 UTC 2019)
Comment
-
Hi Folks,
Where do we stand on this, now... I've been out of town and out of touch for over 2 weeks. My understanding is that .210 doesn't fix the issue after 1/1/2019 and I note that there is a new beta, which I have downloaded and installed. Am I good to go or do I still need to do something with the Harmony Hub?HomeSeer Version: HS4 Pro Edition 4.2.19.0 (Windows - Running as a Service)
Home Assistant 2024.3
Operating System: Microsoft Windows 11 Pro - Desktop
Z-Wave Devices via two Z-Net G3s
Zigbee Devices via RaspBee on RPi 3b+
WiFi Devices via Internal Router.
Enabled Plug-Ins
AK GoogleCalendar 4.0.4.16,AK HomeAssistant 4.0.1.23,AK SmartDevice 4.0.5.1,AK Weather 4.0.5.181,AmbientWeather 3.0.1.9,Big6 3.44.0.0,BLBackup 2.0.64.0,BLGData 3.0.55.0,BLLock 3.0.39.0,BLUPS 2.0.26.0,Device History 4.5.1.1,EasyTrigger 3.0.0.76,Harmony Hub 4.0.14.0,HSBuddy 4.51.303.0,JowiHue 4.1.4.0,LG ThinQ 4.0.26.0,ONVIF Events 1.0.0.5,SDJ-Health 3.1.1.9,TPLinkSmartHome4 2022.12.30.0,UltraCID3 3.0.6681.34300,Z-Wave 4.1.3.0
Comment
-
Originally posted by ewkearns View PostHi Folks,
Where do we stand on this, now... I've been out of town and out of touch for over 2 weeks. My understanding is that .210 doesn't fix the issue after 1/1/2019 and I note that there is a new beta, which I have downloaded and installed. Am I good to go or do I still need to do something with the Harmony Hub?
Logitech is supposed to roll this back into their main releases again (from my understanding). I don't know of we'll need to do anything or of updates will roll out automatically once it is mainstream again. I'm hoping they are smart about it.
Comment
Comment