Config setup screens disappeared after initial setup

[alexbk66]

That's all working now and with the grouping turned on it's all making sense.

Thanks for all the help!

My pleasure, podvodo

[podvodo]

Hi alexbk66

That's all working now and with the grouping turned on it's all making sense.

Thanks for all the help!

[alexbk66]

after I upgraded to the beta version a number of extra devices showed up on my list. The top ones are new, the bottom ones (with green icons) were there before.Is that expected?

The devices with the green icons are the root (parent) devices for each thermostat. All other devices should be grouped under the root, i.e.:
.


It looks like you have grouping disabled?

[alexbk66]

BETA 3.0.0.14 in updater - using System.Web.DataVisualization - works on Linux!

[alexbk66]

Great thanks: that did the trick regarding giving me access to the config tab again.

In the mean time I will try to get charts working on Linux, but probably it will require completely redoing the chart using different graphics library.

I will also open support ticket on Mono Github.

[podvodo]

Great thanks: that did the trick regarding giving me access to the config tab again.

[alexbk66]

See https://forums.homeseer.com/forum/th...ion-add-string

[podvodo]

I checked the version and I also have the old one 5.20

[alexbk66]

Possibly I haven't even tested Charts (from ver. 1.0.0.7) on Linux...
It's using System.Windows.Forms.DataVisualization.Charting assembly which seems to be different on Mono.
I have old Mono 5.20 though, may try to upgrade to latest 6.4.0

As a quick fix I can temporarily disable the charts if running on Linux.

[alexbk66]

What's your Mono version?

[alexbk66]

I'm using the linux version
I also attached a log of the errors

Thank you for detailed info.

1. The "Developer Mode" is only for Windows - on Linux you have console output anyway.
2. The good news - there's only one error now (about Charting), the second error (Error converting value {null} to type 'HeatmiserNeo.PROGRAM_MODE') is gone - Heatmiser changed slightly the comms protocol.
3. The Charting error is caused by .NET version mismatch. Again, good news - I can reproduce the error on my Linux VM, so should be easy to fix.

[podvodo]

Hi alexbk66

Thanks for getting back to me so quickly!

So I'm using the linux version (running on a raspberry Pi 3 B+). There are loads more errors (as you said) so I attached part of my logs - they are very repetitive though, so I suspect its the same errors being returned every time any of the devices are polled.

As to when it happened: as soon as I entered the IP for the Neo Hub during the configuration of the plugin and it successfully found all of the neo devices. I switched from the config screen to the Device management screen and then when I went back to the config screen the tabs were no longer there. And I have not been able to get them back since (even removing the plugin or downloading the BETA version didn't change anything). It feels like a value got set in a config file associated with the plugin somehow that now means it will not display those extra tabs (of course that could be utter nonsense...)?

Anyway, I downloaded the beta version and turned on developer mode as you suggested, but that didn't change the tabs I see (I included screenshots post these updates).



What I did notice is that after I upgraded to the beta version a number of extra devices showed up on my list. The top ones are new, the bottom ones (with green icons) were there before.Is that expected?



I also attached a log of the errors that I got after upgrading to BETA: [ATTACH]n1336294[/ATTACH]


Thanks again for your help!

[alexbk66]

my logs are plagued with error [327] messages (mainly two types for each of the created devices)
PS Happy to provide a dump of error messages if it would be helpful

Yeah, I checked the source code, there's enough error checking, so there should be more errors logged. So definitely more errors would be helpful.

And I guess you don't know when and why it stopped working? I will try to find out if Heatmiser pushed some new firmware update which could break comms.

[327] is actually the HomeSeer device id (your NeoHub device?)

[alexbk66]

Forgot to ask - are you on Windows or Linux?

[alexbk66]

Hi podvodo ,

[EDIT] Before anything, please try BETA 3.0.0.12. And please provide all errors.

Which plugin version are you using? If it's the released 1.0.0.9 - please try latest BETA 3.0.0.11 (in Beta section).

As first troubleshooting step can you please enable "Developer Mode" on PLUG-INS Manage page and then disable/enable the plugin. This will start the plugin with the console window, where you might be able to see more errors. Often this is caused by .NET version mismatch.



In any case, I will add more error handling and update the BETA version. It will be difficult for me to test the error handling (difficult to reproduce the error) - but hopefully should help you.