Originally posted by dcorsus
View Post
Announcement
Collapse
No announcement yet.
HS3 Sonoscontroller beta testing forum
Collapse
X
-
HW: HS3 w/ Win8.1 on ASRock C2550d4i. Digi AnywhereUSB, Hubport, Edgeport, UZB, Z-trollers, PLCBUS, SONOS, GC-100, iTach IP2SL, WF2IR, IP2IR, RFXtrx433, Harmony Hubs, Hue, Ademco Vista 128BP, NetAtmo, NetAtmo Welcome
Google Search for HomeSeer Forum
-
Originally posted by LeoS View PostYou might want to disable some of the error messages that get dumped in the log then, so ppl won't think the plugin is misbehaving... or were those error messages generated by HS3?
Which error messages did you see?
Dirk
Comment
-
Originally posted by dcorsus View PostWhich error messages are you referring to? There shouldn't be any, apart from one (about audioinputname conversion from string to bool), that I'm looking at.
Which error messages did you see?
Dirk
Code:Apr-23 00:47:41 Sonos Error Error in myDeviceFinderCallback_DeviceFound for zoneplayer = . Some crucial services are not on-line. The plug-in cannot work for this zone
This was the plugin's startup sequence:
Code:Apr-23 00:37:22 Sonos CreateSonosControllers: Created instance of ZonePlayerController for Zoneplayer = with index 6 Apr-23 00:37:21 Sonos InitIO Called for Instance = RINCON_000E5872361201400_MS and running on OS = Win32NT Apr-23 00:37:21 Info Plugin Sonos with instance RINCON_000E5872361201400_MS has connected. IP:127.0.0.1:53266 Apr-23 00:37:21 Sonos CreateSonosControllers: Created instance of ZonePlayerController for Zoneplayer = Media Room with index 5 Apr-23 00:37:19 Sonos DirectConnect called for Zone Media Room with device name = uuid:RINCON_000E582664C001400 and Model = ZP90 Apr-23 00:37:18 Sonos InitIO Called for Instance = RINCON_000E582664C001400 and running on OS = Win32NT Apr-23 00:37:18 Info Plugin Sonos with instance RINCON_000E582664C001400 has connected. IP:127.0.0.1:53219 Apr-23 00:37:18 Sonos CreateSonosControllers: Created instance of ZonePlayerController for Zoneplayer = Master Bedroom with index 4 Apr-23 00:37:16 Sonos DirectConnect called for Zone Master Bedroom with device name = uuid:RINCON_000E5854F02E01400 and Model = S5 Apr-23 00:37:15 Sonos InitIO Called for Instance = RINCON_000E5854F02E01400 and running on OS = Win32NT Apr-23 00:37:15 Info Plugin Sonos with instance RINCON_000E5854F02E01400 has connected. IP:127.0.0.1:53179 Apr-23 00:37:15 Sonos CreateSonosControllers: Created instance of ZonePlayerController for Zoneplayer = Study with index 3 Apr-23 00:37:13 Sonos DirectConnect called for Zone Study with device name = uuid:RINCON_000E5872361201400 and Model = S3 Apr-23 00:37:12 Sonos InitIO Called for Instance = RINCON_000E5872361201400 and running on OS = Win32NT Apr-23 00:37:12 Info Plugin Sonos with instance RINCON_000E5872361201400 has connected. IP:127.0.0.1:53137 Apr-23 00:37:12 Sonos CreateSonosControllers: Created instance of ZonePlayerController for Zoneplayer = Hall with index 2 Apr-23 00:37:10 Sonos DirectConnect called for Zone Hall with device name = uuid:RINCON_000E58306BE001400 and Model = ZP120 Apr-23 00:37:09 Sonos InitIO Called for Instance = RINCON_000E58306BE001400 and running on OS = Win32NT Apr-23 00:37:09 Info Plugin Sonos with instance RINCON_000E58306BE001400 has connected. IP:127.0.0.1:53095 Apr-23 00:37:09 Sonos CreateSonosControllers: Created instance of ZonePlayerController for Zoneplayer = Master Bathroom with index 1 Apr-23 00:37:07 Sonos DirectConnect called for Zone Master Bathroom with device name = uuid:RINCON_000E58C05A9201400 and Model = S1 Apr-23 00:37:06 Sonos InitIO Called for Instance = RINCON_000E58C05A9201400 and running on OS = Win32NT Apr-23 00:37:06 Info Plugin Sonos with instance RINCON_000E58C05A9201400 has connected. IP:127.0.0.1:53050
HW: HS3 w/ Win8.1 on ASRock C2550d4i. Digi AnywhereUSB, Hubport, Edgeport, UZB, Z-trollers, PLCBUS, SONOS, GC-100, iTach IP2SL, WF2IR, IP2IR, RFXtrx433, Harmony Hubs, Hue, Ademco Vista 128BP, NetAtmo, NetAtmo Welcome
Google Search for HomeSeer Forum
Comment
-
Originally posted by LeoS View PostHmm.. I'll have to dig around for the previous restarts, since my log is pretty messy right now. But on the last restart, Sonos seemingly started without errors, but it kept spewing this line:
Code:Apr-23 00:47:41 Sonos Error Error in myDeviceFinderCallback_DeviceFound for zoneplayer = . Some crucial services are not on-line. The plug-in cannot work for this zone
This was the plugin's startup sequence:
Code:Apr-23 00:37:22 Sonos CreateSonosControllers: Created instance of ZonePlayerController for Zoneplayer = with index 6 Apr-23 00:37:21 Sonos InitIO Called for Instance = RINCON_000E5872361201400_MS and running on OS = Win32NT Apr-23 00:37:21 Info Plugin Sonos with instance RINCON_000E5872361201400_MS has connected. IP:127.0.0.1:53266 Apr-23 00:37:21 Sonos CreateSonosControllers: Created instance of ZonePlayerController for Zoneplayer = Media Room with index 5 Apr-23 00:37:19 Sonos DirectConnect called for Zone Media Room with device name = uuid:RINCON_000E582664C001400 and Model = ZP90 Apr-23 00:37:18 Sonos InitIO Called for Instance = RINCON_000E582664C001400 and running on OS = Win32NT Apr-23 00:37:18 Info Plugin Sonos with instance RINCON_000E582664C001400 has connected. IP:127.0.0.1:53219 Apr-23 00:37:18 Sonos CreateSonosControllers: Created instance of ZonePlayerController for Zoneplayer = Master Bedroom with index 4 Apr-23 00:37:16 Sonos DirectConnect called for Zone Master Bedroom with device name = uuid:RINCON_000E5854F02E01400 and Model = S5 Apr-23 00:37:15 Sonos InitIO Called for Instance = RINCON_000E5854F02E01400 and running on OS = Win32NT Apr-23 00:37:15 Info Plugin Sonos with instance RINCON_000E5854F02E01400 has connected. IP:127.0.0.1:53179 Apr-23 00:37:15 Sonos CreateSonosControllers: Created instance of ZonePlayerController for Zoneplayer = Study with index 3 Apr-23 00:37:13 Sonos DirectConnect called for Zone Study with device name = uuid:RINCON_000E5872361201400 and Model = S3 Apr-23 00:37:12 Sonos InitIO Called for Instance = RINCON_000E5872361201400 and running on OS = Win32NT Apr-23 00:37:12 Info Plugin Sonos with instance RINCON_000E5872361201400 has connected. IP:127.0.0.1:53137 Apr-23 00:37:12 Sonos CreateSonosControllers: Created instance of ZonePlayerController for Zoneplayer = Hall with index 2 Apr-23 00:37:10 Sonos DirectConnect called for Zone Hall with device name = uuid:RINCON_000E58306BE001400 and Model = ZP120 Apr-23 00:37:09 Sonos InitIO Called for Instance = RINCON_000E58306BE001400 and running on OS = Win32NT Apr-23 00:37:09 Info Plugin Sonos with instance RINCON_000E58306BE001400 has connected. IP:127.0.0.1:53095 Apr-23 00:37:09 Sonos CreateSonosControllers: Created instance of ZonePlayerController for Zoneplayer = Master Bathroom with index 1 Apr-23 00:37:07 Sonos DirectConnect called for Zone Master Bathroom with device name = uuid:RINCON_000E58C05A9201400 and Model = S1 Apr-23 00:37:06 Sonos InitIO Called for Instance = RINCON_000E58C05A9201400 and running on OS = Win32NT Apr-23 00:37:06 Info Plugin Sonos with instance RINCON_000E58C05A9201400 has connected. IP:127.0.0.1:53050
Startup log looks normal.
Previous errors doesn't look normal, not sure what happened but there is no zone name in it. If you go to the Sonos Config screen and look at the device table, does that all look normal? No ghost entries?
Dirk
Dirk
Comment
-
Originally posted by dcorsus View PostStartup log looks normal.
Previous errors doesn't look normal, not sure what happened but there is no zone name in it. If you go to the Sonos Config screen and look at the device table, does that all look normal? No ghost entries?
Dirk
Dirk
Yes, there is a ghost entry... I've manually deleted it. That's weird, it was a duplicate of one of the other player, but without name. Everything else is dupe (udn, mac, ip, etc)HW: HS3 w/ Win8.1 on ASRock C2550d4i. Digi AnywhereUSB, Hubport, Edgeport, UZB, Z-trollers, PLCBUS, SONOS, GC-100, iTach IP2SL, WF2IR, IP2IR, RFXtrx433, Harmony Hubs, Hue, Ademco Vista 128BP, NetAtmo, NetAtmo Welcome
Google Search for HomeSeer Forum
Comment
-
Originally posted by rweber93 View PostI upgraded to the 3.1.0.1 PI and now I'm getting errors in the logs constantly. Anyone experience this after the upgrade?HW: HS3 w/ Win8.1 on ASRock C2550d4i. Digi AnywhereUSB, Hubport, Edgeport, UZB, Z-trollers, PLCBUS, SONOS, GC-100, iTach IP2SL, WF2IR, IP2IR, RFXtrx433, Harmony Hubs, Hue, Ademco Vista 128BP, NetAtmo, NetAtmo Welcome
Google Search for HomeSeer Forum
Comment
-
Originally posted by rweber93 View PostI upgraded to the 3.1.0.1 PI and now I'm getting errors in the logs constantly. Anyone experience this after the upgrade?
Dirk
Comment
-
Originally posted by rweber93 View PostHi Dirk,
Yes, I have tried multiple times restarting the PI and still get this error message. I also restarted my computer and restarted HS. Didn't fix the issue. I'm running Windows 8.1 and I did shut off the firewall and didn't help.
Dirk
Comment
-
Dirk,
I just noticed this error on startup of HS3:
Starting up....
4/25/2015 6:19:51 PM ~!~Error~!~SQL Exception adding record(s) to the LOG database(0): database disk image is malformeddatabase disk image is malformed, Code=11 SQL=
4/25/2015 6:19:51 PM ~!~Error~!~112 Log records failed to be written to the log database.
4/25/2015 6:19:54 PM ~!~Error~!~SQL Exception adding record(s) to the LOG database(0): database disk image is malformeddatabase disk image is malformed, Code=11 SQL=
4/25/2015 6:19:54 PM ~!~Error~!~10 Log records failed to be written to the log database.
4/25/2015 6:19:56 PM ~!~Error~!~SQL Exception adding record(s) to the LOG database(0): database disk image is malformeddatabase disk image is malformed, Code=11 SQL=
4/25/2015 6:19:56 PM ~!~Error~!~2 Log records failed to be written to the log database.
4/25/2015 6:19:59 PM ~!~Error~!~SQL Exception adding record(s) to the LOG database(0): database disk image is malformeddatabase disk image is malformed, Code=11 SQL=
4/25/2015 6:19:59 PM ~!~Error~!~2 Log records failed to be written to the log database.
4/25/2015 6:20:01 PM ~!~Error~!~SQL Exception adding record(s) to the LOG database(0): database disk image is malformeddatabase disk image is malformed, Code=11 SQL=
4/25/2015 6:20:01 PM ~!~Error~!~3 Log records failed to be written to the log database.
4/25/2015 6:20:04 PM ~!~Error~!~SQL Exception adding record(s) to the LOG database(0): database disk image is malformeddatabase disk image is malformed, Code=11 SQL=
4/25/2015 6:20:04 PM ~!~Error~!~2 Log records failed to be written to the log database.
4/25/2015 6:20:06 PM ~!~Error~!~SQL Exception adding record(s) to the LOG database(0): database disk image is malformeddatabase disk image is malformed, Code=11 SQL=
4/25/2015 6:20:06 PM ~!~Error~!~2 Log records failed to be written to the log database.
4/25/2015 6:20:09 PM ~!~Error~!~SQL Exception adding record(s) to the LOG database(0): database disk image is malformeddatabase disk image is malformed, Code=11 SQL=
4/25/2015 6:20:09 PM ~!~Error~!~2 Log records failed to be written to the log database.
4/25/2015 6:20:11 PM ~!~Error~!~SQL Exception adding record(s) to the LOG database(0): database disk image is malformeddatabase disk image is malformed, Code=11 SQL=
4/25/2015 6:20:11 PM ~!~Error~!~2 Log records failed to be written to the log database.
4/25/2015 6:20:14 PM ~!~Error~!~SQL Exception adding record(s) to the LOG database(0): database disk image is malformeddatabase disk image is malformed, Code=11 SQL=
4/25/2015 6:20:14 PM ~!~Error~!~2 Log records failed to be written to the log database.Startup Complete, 20 errors detected, check the log for more information.
Comment
-
Originally posted by rweber93 View PostDirk,
I just noticed this error on startup of HS3:
Starting up....
4/25/2015 6:19:51 PM ~!~Error~!~SQL Exception adding record(s) to the LOG database(0): database disk image is malformeddatabase disk image is malformed, Code=11 SQL=
4/25/2015 6:19:51 PM ~!~Error~!~112 Log records failed to be written to the log database.
4/25/2015 6:19:54 PM ~!~Error~!~SQL Exception adding record(s) to the LOG database(0): database disk image is malformeddatabase disk image is malformed, Code=11 SQL=
4/25/2015 6:19:54 PM ~!~Error~!~10 Log records failed to be written to the log database.
4/25/2015 6:19:56 PM ~!~Error~!~SQL Exception adding record(s) to the LOG database(0): database disk image is malformeddatabase disk image is malformed, Code=11 SQL=
4/25/2015 6:19:56 PM ~!~Error~!~2 Log records failed to be written to the log database.
4/25/2015 6:19:59 PM ~!~Error~!~SQL Exception adding record(s) to the LOG database(0): database disk image is malformeddatabase disk image is malformed, Code=11 SQL=
4/25/2015 6:19:59 PM ~!~Error~!~2 Log records failed to be written to the log database.
4/25/2015 6:20:01 PM ~!~Error~!~SQL Exception adding record(s) to the LOG database(0): database disk image is malformeddatabase disk image is malformed, Code=11 SQL=
4/25/2015 6:20:01 PM ~!~Error~!~3 Log records failed to be written to the log database.
4/25/2015 6:20:04 PM ~!~Error~!~SQL Exception adding record(s) to the LOG database(0): database disk image is malformeddatabase disk image is malformed, Code=11 SQL=
4/25/2015 6:20:04 PM ~!~Error~!~2 Log records failed to be written to the log database.
4/25/2015 6:20:06 PM ~!~Error~!~SQL Exception adding record(s) to the LOG database(0): database disk image is malformeddatabase disk image is malformed, Code=11 SQL=
4/25/2015 6:20:06 PM ~!~Error~!~2 Log records failed to be written to the log database.
4/25/2015 6:20:09 PM ~!~Error~!~SQL Exception adding record(s) to the LOG database(0): database disk image is malformeddatabase disk image is malformed, Code=11 SQL=
4/25/2015 6:20:09 PM ~!~Error~!~2 Log records failed to be written to the log database.
4/25/2015 6:20:11 PM ~!~Error~!~SQL Exception adding record(s) to the LOG database(0): database disk image is malformeddatabase disk image is malformed, Code=11 SQL=
4/25/2015 6:20:11 PM ~!~Error~!~2 Log records failed to be written to the log database.
4/25/2015 6:20:14 PM ~!~Error~!~SQL Exception adding record(s) to the LOG database(0): database disk image is malformeddatabase disk image is malformed, Code=11 SQL=
4/25/2015 6:20:14 PM ~!~Error~!~2 Log records failed to be written to the log database.Startup Complete, 20 errors detected, check the log for more information.
Dirk
Comment
-
Awesome! I checked on that log file and you were correct! After I renamed the old log file and restarted HS3, that fixed that issue. Now I'm just getting this error on startup:
Starting up....
4/27/2015 8:22:33 AM ~!~Error~!~Could not add Sonos to the plug-in list. Is this a duplicate? Check for two plug-ins with the same plug-in name.Startup Complete, 1 errors detected, check the log for more information.
and still getting the original issue which I believe is running up my log file and causing the other issue:
Apr-27 8:25:37 AM Sonos Error Error in myDeviceFinderCallback_DeviceFound for zoneplayer = Media Room. Some crucial services are not on-line. The plug-in cannot work for this zone
Apr-27 8:25:35 AM Sonos Error Error in myDeviceFinderCallback_DeviceFound for zoneplayer = Living Room. Some crucial services are not on-line. The plug-in cannot work for this zone
Apr-27 8:25:32 AM Sonos Error Error in myDeviceFinderCallback_DeviceFound for zoneplayer = Media Room. Some crucial services are not on-line. The plug-in cannot work for this zone
Apr-27 8:25:30 AM Sonos Error Error in myDeviceFinderCallback_DeviceFound for zoneplayer = Living Room. Some crucial services are not on-line. The plug-in cannot work for this zone
Apr-27 8:25:17 AM Sonos Error Error in myDeviceFinderCallback_DeviceFound for zoneplayer = Media Room. Some crucial services are not on-line. The plug-in cannot work for this zone
Apr-27 8:25:15 AM Sonos Error Error in myDeviceFinderCallback_DeviceFound for zoneplayer = Living Room. Some crucial services are not on-line. The plug-in cannot work for this zone
Apr-27 8:25:12 AM Sonos Error Error in myDeviceFinderCallback_DeviceFound for zoneplayer = Media Room. Some crucial services are not on-line. The plug-in cannot work for this zone
Apr-27 8:25:10 AM Sonos Error Error in myDeviceFinderCallback_DeviceFound for zoneplayer = Living Room. Some crucial services are not on-line. The plug-in cannot work for this zone
Apr-27 8:24:57 AM Sonos Error Error in myDeviceFinderCallback_DeviceFound for zoneplayer = Media Room. Some crucial services are not on-line. The plug-in cannot work for this zone
Apr-27 8:24:55 AM Sonos Error Error in myDeviceFinderCallback_DeviceFound for zoneplayer = Living Room. Some crucial services are not on-line. The plug-in cannot work for this zone
Apr-27 8:24:52 AM Sonos Error Error in myDeviceFinderCallback_DeviceFound for zoneplayer = Media Room. Some crucial services are not on-line. The plug-in cannot work for this zone
Apr-27 8:24:50 AM Sonos Error Error in myDeviceFinderCallback_DeviceFound for zoneplayer = Living Room. Some crucial services are not on-line. The plug-in cannot work for this zone
Apr-27 8:24:37 AM Sonos Error Error in myDeviceFinderCallback_DeviceFound for zoneplayer = Media Room. Some crucial services are not on-line. The plug-in cannot work for this zone
Apr-27 8:24:35 AM Sonos Error Error in myDeviceFinderCallback_DeviceFound for zoneplayer = Living Room. Some crucial services are not on-line. The plug-in cannot work for this zone
Apr-27 8:24:32 AM Sonos Error Error in myDeviceFinderCallback_DeviceFound for zoneplayer = Media Room. Some crucial services are not on-line. The plug-in cannot work for this zone
Apr-27 8:24:30 AM Sonos Error Error in myDeviceFinderCallback_DeviceFound for zoneplayer = Living Room. Some crucial services are not on-line. The plug-in cannot work for this zone
Apr-27 8:24:17 AM Sonos Error Error in myDeviceFinderCallback_DeviceFound for zoneplayer = Media Room. Some crucial services are not on-line. The plug-in cannot work for this zone
Apr-27 8:24:14 AM Sonos Error Error in myDeviceFinderCallback_DeviceFound for zoneplayer = Living Room. Some crucial services are not on-line. The plug-in cannot work for this zone
Apr-27 8:24:12 AM Sonos Error Error in myDeviceFinderCallback_DeviceFound for zoneplayer = Media Room. Some crucial services are not on-line. The plug-in cannot work for this zone
Apr-27 8:24:10 AM Sonos Error Error in myDeviceFinderCallback_DeviceFound for zoneplayer = Living Room. Some crucial services are not on-line. The plug-in cannot work for this zone
Apr-27 8:23:57 AM Sonos Error Error in myDeviceFinderCallback_DeviceFound for zoneplayer = Media Room. Some crucial
Comment
-
Originally posted by rweber93 View PostAwesome! I checked on that log file and you were correct! After I renamed the old log file and restarted HS3, that fixed that issue. Now I'm just getting this error on startup:
Starting up....
4/27/2015 8:22:33 AM ~!~Error~!~Could not add Sonos to the plug-in list. Is this a duplicate? Check for two plug-ins with the same plug-in name.Startup Complete, 1 errors detected, check the log for more information.
and still getting the original issue which I believe is running up my log file and causing the other issue:
Apr-27 8:25:37 AM Sonos Error Error in myDeviceFinderCallback_DeviceFound for zoneplayer = Media Room. Some crucial services are not on-line. The plug-in cannot work for this zone
If you go to the Sonos Config screen and look at the player table, can you post a screen shot of that? Are there any ghost players or players that have a udn that ends with _MS?
Dirk
Comment
Comment