Can't display Device Config pages

[joegr]

Understood.

[sirmeili]

joegr please try v 3.1.0.20 in the beta section of the updater. I added a lot of logging. Make sure you have debug logging turned on and then go to the device config page. If it doesn't work, then please send me the logs it produces.

[joegr]

Sadly, attempting device config for the upstairs hub results in:

Sep-30 8:13:56 AM

Error

Posting back to plugin web page MeiHarmonyHub_Device_Config: Object reference not set to an instance of an object.-> Server stack trace: Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessag e(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(Mess ageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)

Attempting to alter any event using a device on the upstairs hub errors out on the event screen, but doesn't put anything in the log.

Here is your log from the point where I shut down the plugin to update it. After the update, I first looked at the config for the downstairs hub devices and verified that still worked.

[sirmeili]

joegr so I see that it worked up to some point. Am I right that it happened right when you selected the Device to get the list of commands?

[joegr]

joegr so I see that it worked up to some point. Am I right that it happened right when you selected the Device to get the list of commands?

I don't get as far as the actual device drop down. See attached.

After I select the problem hub, it goes no further.

[sirmeili]

That is odd because in the logs it showed you selected the device with ref 632 and it tried to list the commands. I'll add in more debugging. I've been moving my office to a temporary location in the house, but now I'm back up (I know...more excuses)

[joegr]

That is odd because in the logs it showed you selected the device with ref 632 and it tried to list the commands. I'll add in more debugging. I've been moving my office to a temporary location in the house, but now I'm back up (I know...more excuses)

Sorry for the confusion. I first selected the Downstairs hub, and then tried a device on it. That was 632. This verified that it was still working. After that, I selected the upstairs one, and that didn't go anywhere, still not working. That would be at about 8:13:56 in your log.

Here is a cut from your log of only trying to access the upstairs hub device config.

2020-10-08 21:12:10.788 -05:00 [INF] Page MeiHarmonyHub_Device_Config
2020-10-08 21:12:10.797 -05:00 [DBG] DeviceConfig.cs: Total Hubs 2
2020-10-08 21:12:10.799 -05:00 [DBG] DeviceConfig.cs: Hub Loop: Hub: 8b839c60dc27ae9adad8d66be1cd1087eaeabd0b; Device Ref: 620
2020-10-08 21:12:10.800 -05:00 [DBG] DeviceConfig.cs: Hub Loop: Hub: 8b839c60dc27ae9adad8d66be1cd1087eaeabd0b; Device Ref: 620; Hub Added to dropdown
2020-10-08 21:12:10.802 -05:00 [DBG] DeviceConfig.cs: Hub Loop: Hub: c9c7d2829a604caecfe366b42a6f22fd2a52846a; Device Ref: 628
2020-10-08 21:12:10.802 -05:00 [DBG] DeviceConfig.cs: Hub Loop: Hub: c9c7d2829a604caecfe366b42a6f22fd2a52846a; Device Ref: 628; Hub Added to dropdown
2020-10-08 21:12:13.893 -05:00 [DBG] Debug Message for Hub 8b839c60dc27ae9adad8d66be1cd1087eaeabd0b: Starting Heartbeat for hub 8b839c60dc27ae9adad8d66be1cd1087eaeabd0b
2020-10-08 21:12:13.893 -05:00 [DBG] Message Sent to Hub: <iq type='get' id='e6694018-c919-4abe-b182-6720297f066d_82'><oa xmlns='connect.logitech.com' mime='vnd.logitech.connect/vnd.logitech.ping'/></iq>
2020-10-08 21:12:13.975 -05:00 [DBG] Message received from Hub: <iq xmlns="jabber:client" />
2020-10-08 21:12:13.987 -05:00 [DBG] Message received from Hub: <iq id="e6694018-c919-4abe-b182-6720297f066d_82" type="get" xmlns="jabber:client"><oa xmlns="connect.logitech.com" mime="vnd.logitech.connect/vnd.logitech.ping" errorcode="200" errorstring="OK"><![CDATA[status=alive:uuid=8b839c60dc27ae9adad8d66be1cd1087eaeabd0b:i d=e6694018-c919-4abe-b182-6720297f066d_82:susTrigger=xmpp]]></oa></iq>
2020-10-08 21:12:13.987 -05:00 [DBG] Debug Message for Hub 8b839c60dc27ae9adad8d66be1cd1087eaeabd0b: Heartbeat success for hub 8b839c60dc27ae9adad8d66be1cd1087eaeabd0b
2020-10-08 21:12:14.111 -05:00 [INF] Page MeiHarmonyHub_Device_Config; Data selectedDeviceHub=&selectedDevice=&selectedCommand=&device_h ub=8b839c60dc27ae9adad8d66be1cd1087eaeabd0b&id=device_hub
2020-10-08 21:12:14.120 -05:00 [DBG] Posting back data on page (MeiHarmonyHub_Device_Config) with data: selectedDeviceHub=&selectedDevice=&selectedCommand=&device_h ub=8b839c60dc27ae9adad8d66be1cd1087eaeabd0b&id=device_hub
2020-10-08 21:12:14.121 -05:00 [DBG] DeviceConfig.cs: Total Hubs 2
2020-10-08 21:12:14.123 -05:00 [DBG] DeviceConfig.cs: Hub Loop: Hub: 8b839c60dc27ae9adad8d66be1cd1087eaeabd0b; Device Ref: 620
2020-10-08 21:12:14.123 -05:00 [DBG] DeviceConfig.cs: Hub Loop: Hub: 8b839c60dc27ae9adad8d66be1cd1087eaeabd0b; Device Ref: 620; Hub Added to dropdown
2020-10-08 21:12:14.125 -05:00 [DBG] DeviceConfig.cs: Hub Loop: Hub: c9c7d2829a604caecfe366b42a6f22fd2a52846a; Device Ref: 628
2020-10-08 21:12:14.125 -05:00 [DBG] DeviceConfig.cs: Hub Loop: Hub: c9c7d2829a604caecfe366b42a6f22fd2a52846a; Device Ref: 628; Hub Added to dropdown
2020-10-08 21:12:14.125 -05:00 [DBG] DeviceConfig.cs: Hub Passed in: 8b839c60dc27ae9adad8d66be1cd1087eaeabd0b
2020-10-08 21:12:14.125 -05:00 [DBG] DeviceConfig.cs: Total Hub Devices: 9; Hub: 8b839c60dc27ae9adad8d66be1cd1087eaeabd0b
2020-10-08 21:12:14.128 -05:00 [DBG] DeviceConfig.cs: Hub Device Loop: Device: 59556737; Device Ref: 623/623; Hub: 8b839c60dc27ae9adad8d66be1cd1087eaeabd0b
2020-10-08 21:12:43.894 -05:00 [DBG] Debug Message for Hub 8b839c60dc27ae9adad8d66be1cd1087eaeabd0b: Starting Heartbeat for hub 8b839c60dc27ae9adad8d66be1cd1087eaeabd0b
2020-10-08 21:12:43.894 -05:00 [DBG] Message Sent to Hub: <iq type='get' id='e6694018-c919-4abe-b182-6720297f066d_83'><oa xmlns='connect.logitech.com' mime='vnd.logitech.connect/vnd.logitech.ping'/></iq>
2020-10-08 21:12:43.903 -05:00 [DBG] Message received from Hub: <iq xmlns="jabber:client" />
2020-10-08 21:12:43.916 -05:00 [DBG] Message received from Hub: <iq id="e6694018-c919-4abe-b182-6720297f066d_83" type="get" xmlns="jabber:client"><oa xmlns="connect.logitech.com" mime="vnd.logitech.connect/vnd.logitech.ping" errorcode="200" errorstring="OK"><![CDATA[status=alive:uuid=8b839c60dc27ae9adad8d66be1cd1087eaeabd0b:i d=e6694018-c919-4abe-b182-6720297f066d_83:susTrigger=xmpp]]></oa></iq>
2020-10-08 21:12:43.916 -05:00 [DBG] Debug Message for Hub 8b839c60dc27ae9adad8d66be1cd1087eaeabd0b: Heartbeat success for hub 8b839c60dc27ae9adad8d66be1cd1087eaeabd0b
2020-10-08 21:13:13.895 -05:00 [DBG] Debug Message for Hub 8b839c60dc27ae9adad8d66be1cd1087eaeabd0b: Starting Heartbeat for hub 8b839c60dc27ae9adad8d66be1cd1087eaeabd0b
2020-10-08 21:13:13.895 -05:00 [DBG] Message Sent to Hub: <iq type='get' id='e6694018-c919-4abe-b182-6720297f066d_84'><oa xmlns='connect.logitech.com' mime='vnd.logitech.connect/vnd.logitech.ping'/></iq>
2020-10-08 21:13:13.906 -05:00 [DBG] Message received from Hub: <iq xmlns="jabber:client" />
2020-10-08 21:13:13.916 -05:00 [DBG] Message received from Hub: <iq id="e6694018-c919-4abe-b182-6720297f066d_84" type="get" xmlns="jabber:client"><oa xmlns="connect.logitech.com" mime="vnd.logitech.connect/vnd.logitech.ping" errorcode="200" errorstring="OK"><![CDATA[status=alive:uuid=8b839c60dc27ae9adad8d66be1cd1087eaeabd0b:i d=e6694018-c919-4abe-b182-6720297f066d_84:susTrigger=xmpp]]></oa></iq>
2020-10-08 21:13:13.916 -05:00 [DBG] Debug Message for Hub 8b839c60dc27ae9adad8d66be1cd1087eaeabd0b: Heartbeat success for hub 8b839c60dc27ae9adad8d66be1cd1087eaeabd0b
2020-10-08 21:13:43.904 -05:00 [DBG] Debug Message for Hub 8b839c60dc27ae9adad8d66be1cd1087eaeabd0b: Starting Heartbeat for hub 8b839c60dc27ae9adad8d66be1cd1087eaeabd0b
2020-10-08 21:13:43.904 -05:00 [DBG] Message Sent to Hub: <iq type='get' id='e6694018-c919-4abe-b182-6720297f066d_85'><oa xmlns='connect.logitech.com' mime='vnd.logitech.connect/vnd.logitech.ping'/></iq>
2020-10-08 21:13:43.933 -05:00 [DBG] Message received from Hub: <iq xmlns="jabber:client" />
2020-10-08 21:13:43.943 -05:00 [DBG] Message received from Hub: <iq id="e6694018-c919-4abe-b182-6720297f066d_85" type="get" xmlns="jabber:client"><oa xmlns="connect.logitech.com" mime="vnd.logitech.connect/vnd.logitech.ping" errorcode="200" errorstring="OK"><![CDATA[status=alive:uuid=8b839c60dc27ae9adad8d66be1cd1087eaeabd0b:i d=e6694018-c919-4abe-b182-6720297f066d_85:susTrigger=xmpp]]></oa></iq>
2020-10-08 21:13:43.943 -05:00 [DBG] Debug Message for Hub 8b839c60dc27ae9adad8d66be1cd1087eaeabd0b: Heartbeat success for hub 8b839c60dc27ae9adad8d66be1cd1087eaeabd0b


It resulted in this error in the HS log

Oct-08 9:12:14 PM

Error

Posting back to plugin web page MeiHarmonyHub_Device_Config: Object reference not set to an instance of an object.-> Server stack trace: Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessag e(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(Mess ageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)

And the same screen shot that I posted before.

[joegr]

620 is the hub I can't see device config on or change any events.
638 is the downstairs hub that I can do those things with.

[sirmeili]

Ok! that might help! So it appears to be just 1 hub. I wonder if it's something coming back from the hub? I'll dump the response out in the logs as well so I can see it.

[sirmeili]

joegr I think it might be possible that you have a device missing in the system. I've added an IF to catch this and then log that the device was not found. Can you down load .21 from the beta section and try again?

[joegr]

joegr I think it might be possible that you have a device missing in the system. I've added an IF to catch this and then log that the device was not found. Can you down load .21 from the beta section and try again?

Okay, we are making progress. It now lets me open the device config for the problem hub.

I stopped the plugin, updated the plugin, and restarted it. The attached log starts from that point.
I selected the bedroom hub, and then a device on that hub (It's the first time that I got the device drop down).
I then selected the downstairs hub and a device on that hub.

Next, I went to one of the events that I have using a device from the bedroom hub. Unfortunately, that still doesn't work.

[sirmeili]

Yes, sorry, I am focusing on the device screen first. I'm sure it's the same issue in both places though. Just a device missing in the system. I'll get an updates version out tonight.

The big question is, what would you prefer I do in this situation? If you're missing a device in HS, I could automatically recreate the device on startup if it's missing or I could just ignore it in scenarios like this.

[joegr]

Yes, sorry, I am focusing on the device screen first. I'm sure it's the same issue in both places though. Just a device missing in the system. I'll get an updates version out tonight.

The big question is, what would you prefer I do in this situation? If you're missing a device in HS, I could automatically recreate the device on startup if it's missing or I could just ignore it in scenarios like this.

I'm sure that either answer could be wrong. I guess that "recreate it" could be less wrong, provided that there is no danger that it might mistakenly create hundreds of devices...

[sirmeili]

I'm sure that either answer could be wrong. I guess that "recreate it" could be less wrong, provided that there is no danger that it might mistakenly create hundreds of devices...

What I"m hearing is make it a setting and let the user decide. Got it. I'll get something out tonight and attempt to fix the event stuff as well

[sirmeili]

I found the issue. My fix will work for now and I'll fix the action display and anywhere else I can find that has the bug. The issue is that you have devices that my guess you've removed from the hub and from HS, but they are still in your configs (Dev Refs 624, and 625). I'll get a version out tonight.