Halo 1.7 Firmware

[GregCAMS]

Has anyone received the 1.7 Firmware Update for the HALO Remotes?  I haven't and also restarted 3 of my remotes to see if that was required to get it updated.  Wasn't sure if this required a push update from the dealer or going to be OTA as previously promised with these remotes upon their original release

 

https://www.snapav.com/shop/en/snapav/whats-new-halo

 

TIA

[GregCAMS]

Found this for carrying out action.  In my case it did not do it OTA

 

[msgreenf]

Didn't know this went GA. Lots of fixes 

[GregCAMS]

dealer friend (not one of record) sent this to me when inquired.  I'll wait over a few days to see if the OTA between the 2 a.m. - 6 a.m. stated actually happens

[Topfox]

Nice. Just had the updates forced to my remotes. Looking forward to giving some of these a try

[GregCAMS]

20 minutes ago, Topfox said:

Nice. Just had the updates forced to my remotes. Looking forward to giving some of these a try

awesome @Topfox if you have any findings please post.  I'll wait to see when my push.  If not by Friday will ask integrator to do the manual firmware update

[J to the D]

Deleted

[msgreenf]

1 minute ago, J to the D said:

Mine has updated. Any idea what the blue dot next to the WiFi signal means?

New menu with what's new and release notes

[mbushardjr]

I noticed the blue dot last night. I was like what the heck is that I wonder. Found the menu for notifications and it listed a number of new things. I saw the version was 1.7 something. Guessing it auto updated the night before. 

[GregCAMS]

Got the blue dot - took a restart since the scroll wasn't working to get to the messages. 

[PaulAV9]

Anyone having issues after the update? My remote screen occasionally does not go off like it usually does after a small amount of time if its not moved. When this happens the odd behavior also carries over to when I put the remote on the charger. The ding chime is glitchy and dings several times. A reboot of the remote usually fixes things.

Is there somewhere to report bugs to or is that done by contacting my dealer and having them submit it to control 4?

[ChrisHenderson]

If your dealer is willing to submit a bug report, that's a great way to go, because they can get the log files from the remote. I'll ask someone on the Halo team about this and let you know what they say.

 

[PaulAV9]

Thank you very much Chris. I appreciate it.

It would be great if down the road there was a setting that the user could set for how long the screen stays lite before turning off. Squashing the bug of it not going off at all is most important obviously but figured I would also mention a "would be nice to have setting". My old Harmony touch remote could do that.

[ChrisHenderson]

I'll add that recommendation to the bug report. @PaulAV9 I asked someone on the Halo team and she said that she may have seen the same issue you are seeing, but it's hard to tell, because she's using a pre-production remote. She says that she'd need the logs to look into it further. Did you go through your dealer to report it? Alternatively, if your dealer can get the Halo remote logs, I could create the bug for you. Just let me know.

[ChrisHenderson]

@PaulAV9 Could you also include the date and time that you experienced the issue? That'll help us better diagnose the issue.

[Topfox]

Have definitely noticed a degradation of my WiFi connection from the remote since the update. Had zero WiFi issues before, but now my remotes all think they have a low signal strength. Nothing has changed on my home network, and other WiFi devices still detect strong signals. Again zero WiFi type issues pre update. 

[PaulAV9]

@ChrisHenderson Thank you for looking into this. I think I can get the logs from the C4 app on my iPad. Or is that something different than what you need? I see a spot on there in settings> support> support settings> view logs & email logs.

The exact date and time that it happened I am unsure of. I know it happened right after I noticed the update. It has happened twice since the last update. What I will do moving forward is write down the date and time when/if it happens again to help with trouble shooting.

[msgreenf]

Those are different logs

[PaulAV9]

@msgreenfThank you. @ChrisHenderson When it happens again I will note the date and time and I will get the logs from my dealer. That will save the Halo team from having to hunt through long logs and help them pinpoint things easier.

[dblessing]

On 3/16/2024 at 11:15 PM, Topfox said:

Have definitely noticed a degradation of my WiFi connection from the remote since the update. Had zero WiFi issues before, but now my remotes all think they have a low signal strength. Nothing has changed on my home network, and other WiFi devices still detect strong signals. Again zero WiFi type issues pre update. 

Same. I’ve had lots of network connection issues with both my Halo Touches since the update. Even tried factory reset. 
 

I had started a new thread about it at the beginning of March but just now saw this discussion. I’m glad to know it’s not just me. 

 

[GregCAMS]

So far the biggest issue is every Halo I have has an extended time of 'Waking from Sleep' message that was not there prior to firmware update.  Some are taking up to 30 seconds to reconnect/come online while others are a few seconds even when sitting within 5 feet or less of each other docked.  Have not seen an improvement in battery life so far and also having issues with losing connection requiring a restart on 2 of the remotes; the latter is happening every 3-4 days on average.

[dblessing]

Here is a log snippet from my device when it disconnected this morning. It seems somewhat unremarkable - just says the network became unavailable. I can see in UniFi where it disconnected at that time, but I don't see a similar blip on devices connected to the same AP. RSSI at disconnect was -59 dBm which should be acceptable.

What seems a bit more surprising for me is that a network issue is unrecoverable without a restart. Is it expected that there's no way to attempt reconnecting to restore it to working order?

 

2024-03-20 06:47:36.988 -0500 halo-touch-7bc072 [603] DEBUG: Battery level request
2024-03-20 06:47:37.071 -0500 halo-touch-7bc072 [603] DEBUG: [Battery] recieved level 48
2024-03-20 06:47:47.617 -0500 halo-touch-7bc072 [603] ERROR: HttpHandler_BrokerRequest - PocoException, Request failed: Net Exception : Network is unreachable, error code is: 101
2024-03-20 06:47:47.625 -0500 halo-touch-7bc072 [603] WARN: NetCommunications_director_ping - Ping failed
2024-03-20 06:47:47.636 -0500 halo-touch-7bc072 [603] ERROR: HttpHandler_BrokerRequest - PocoException, Request failed: Net Exception : Network is unreachable, error code is: 101
2024-03-20 06:47:47.640 -0500 halo-touch-7bc072 [603] WARN: NetCommunications_director_ping - Ping failed
2024-03-20 06:48:17.040 -0500 halo-touch-7bc072 [603] DEBUG: {
    "command": "AwakeStatus",
    "data": {
        "reason": "light_wakeup",
        "status": true
    },
    "type": "notify"
}

2024-03-20 06:48:17.775 -0500 halo-touch-7bc072 [603] ERROR: HttpHandler_BrokerRequest - PocoException, Request failed: Net Exception : Network is unreachable, error code is: 101
2024-03-20 06:48:17.782 -0500 halo-touch-7bc072 [603] WARN: NetCommunications_director_ping - Ping failed
2024-03-20 06:48:17.792 -0500 halo-touch-7bc072 [603] ERROR: HttpHandler_BrokerRequest - PocoException, Request failed: Net Exception : Network is unreachable, error code is: 101
2024-03-20 06:48:17.795 -0500 halo-touch-7bc072 [603] WARN: NetCommunications_director_ping - Ping failed
2024-03-20 06:48:34.942 -0500 halo-touch-7bc072 [603] INFO: Context_runDetails - Director status timeout
2024-03-20 06:48:34.949 -0500 halo-touch-7bc072 [603] INFO: NetCommunications_HangupAndFailWebServer - Manually trying to recover socket
2024-03-20 06:48:34.952 -0500 halo-touch-7bc072 [603] DEBUG: WsHandler_HangupPresumedDead - Closing socket that was presumed dead
2024-03-20 06:48:36.021 -0500 halo-touch-7bc072 [603] DEBUG: WsHandler_onClosed - On closed: 0
2024-03-20 06:48:36.989 -0500 halo-touch-7bc072 [603] DEBUG: OSCommunicationManageraskForBatteryLevel - [Battery] requesting level from the os
2024-03-20 06:48:36.996 -0500 halo-touch-7bc072 [603] DEBUG: Battery level request
2024-03-20 06:48:37.094 -0500 halo-touch-7bc072 [603] DEBUG: [Battery] recieved level 48
2024-03-20 06:48:37.955 -0500 halo-touch-7bc072 [603] DEBUG: WsHandler_onSocketDisconnected - Socket is disconnected
2024-03-20 06:48:38.463 -0500 halo-touch-7bc072 [603] ERROR: HttpHandler_BrokerRequest - PocoException, Request failed: Net Exception : Network is unreachable, error code is: 101
2024-03-20 06:48:38.464 -0500 halo-touch-7bc072 [603] DEBUG: C4MediaSessionManager_connection_observer - Stopping manager due to communication disconnect
2024-03-20 06:48:38.474 -0500 halo-touch-7bc072 [603] DEBUG: C4MediaSessionManager_stop - Stopping media manager
2024-03-20 06:48:38.472 -0500 halo-touch-7bc072 [603] WARN: NetCommunications_AuthenticateBroker - Authentication failed: code: 200   reason: Net Exception
2024-03-20 06:48:38.478 -0500 halo-touch-7bc072 [603] DEBUG: NavigatorApplication_initializeC4UICoreContext - Communication Status Changed: 0
2024-03-20 06:48:38.483 -0500 halo-touch-7bc072 [603] DEBUG: C4MediaSessionManager_connection_observer - Stopping manager due to communication disconnect
2024-03-20 06:48:38.487 -0500 halo-touch-7bc072 [603] DEBUG: C4MediaSessionManager_stop - Stopping media manager
2024-03-20 06:48:38.495 -0500 halo-touch-7bc072 [603] DEBUG: NavigatorApplication_initializeC4UICoreContext - Communication Status Changed: 2
2024-03-20 06:48:39.504 -0500 halo-touch-7bc072 [603] DEBUG: RemoteNavigatorApplication_onObserveConnectionStatusChanged - Connection Status: FAILED
2024-03-20 06:48:39.512 -0500 halo-touch-7bc072 [603] DEBUG: QMLDebug: opening popup 13
2024-03-20 06:48:39.542 -0500 halo-touch-7bc072 [603] DEBUG: [Popup Manager]pushPopup -  Pushed popup: Network message popup
2024-03-20 06:48:39.545 -0500 halo-touch-7bc072 [603] DEBUG: Analytics_startPerformanceTrace - Starting performance trace: Network Error Displayed
2024-03-20 06:48:39.555 -0500 halo-touch-7bc072 [603] DEBUG: LaunchDarklyEngine_shutdown - Shutting down engine
2024-03-20 06:48:39.557 -0500 halo-touch-7bc072 [603] DEBUG: LaunchDarklyEngine_readyCallback - Ready state changed: 3
2024-03-20 06:48:39.573 -0500 halo-touch-7bc072 [603] DEBUG: Communication is going to terminate
2024-03-20 06:48:39.576 -0500 halo-touch-7bc072 [603] DEBUG: Terminated is set on true
2024-03-20 06:48:39.578 -0500 halo-touch-7bc072 [603] DEBUG: NetCommunications_cleanup_communications - Cleaning up communications
2024-03-20 06:48:39.584 -0500 halo-touch-7bc072 [603] DEBUG: Context_shutdownPrivate - Application context shutting down...
2024-03-20 06:48:39.592 -0500 halo-touch-7bc072 [603] INFO: Context_shutdownPrivate - Application context shutdown.
2024-03-20 06:48:39.606 -0500 halo-touch-7bc072 [603] DEBUG: Context_initialize - Initializing application context...
2024-03-20 06:48:39.608 -0500 halo-touch-7bc072 [603] DEBUG: Broker_init_resume - broker_init_terminated_ is set on false
2024-03-20 06:48:39.611 -0500 halo-touch-7bc072 [603] WARN: QMLWarning: QCommandLineParser: option not defined: "DeviceModel"
2024-03-20 06:48:39.615 -0500 halo-touch-7bc072 [603] INFO: Context_~Context - destroying Context
2024-03-20 06:48:39.618 -0500 halo-touch-7bc072 [603] DEBUG: RemoteNavigatorApplication_onObserveConnectionStatusChanged - Connection Status: FAILED
2024-03-20 06:48:39.607 -0500 halo-touch-7bc072 [603] DEBUG: NewRelicEngine_run - Run Start
2024-03-20 06:48:39.613 -0500 halo-touch-7bc072 [603] DEBUG: Analytics_startPerformanceTrace - Starting performance trace: TotalConnectionTime
2024-03-20 06:48:39.621 -0500 halo-touch-7bc072 [603] DEBUG: RemoteNavigatorApplication_onObserveConnectionStatusChanged - Network error already pushed!
2024-03-20 06:48:40.992 -0500 halo-touch-7bc072 [603] ERROR: HttpHandler_BrokerRequest - PocoException, Request failed: Net Exception : Network is unreachable, error code is: 101
2024-03-20 06:48:40.993 -0500 halo-touch-7bc072 [603] DEBUG: C4MediaSessionManager_connection_observer - Stopping manager due to communication disconnect
2024-03-20 06:48:41.002 -0500 halo-touch-7bc072 [603] DEBUG: C4MediaSessionManager_stop - Stopping media manager
2024-03-20 06:48:41.000 -0500 halo-touch-7bc072 [603] WARN: NetCommunications_AuthenticateBroker - Authentication failed: code: 200   reason: Net Exception
2024-03-20 06:48:41.008 -0500 halo-touch-7bc072 [603] DEBUG: C4MediaSessionManager_connection_observer - Stopping manager due to communication disconnect
2024-03-20 06:48:41.010 -0500 halo-touch-7bc072 [603] DEBUG: C4MediaSessionManager_stop - Stopping media manager
2024-03-20 06:48:41.019 -0500 halo-touch-7bc072 [603] DEBUG: NavigatorApplication_initializeC4UICoreContext - Communication Status Changed: 0
2024-03-20 06:48:41.023 -0500 halo-touch-7bc072 [603] DEBUG: NavigatorApplication_initializeC4UICoreContext - Communication Status Changed: 2
2024-03-20 06:48:42.043 -0500 halo-touch-7bc072 [603] DEBUG: RemoteNavigatorApplication_onObserveConnectionStatusChanged - Connection Status: FAILED
2024-03-20 06:48:42.051 -0500 halo-touch-7bc072 [603] DEBUG: RemoteNavigatorApplication_onObserveConnectionStatusChanged - Network error already pushed!
2024-03-20 06:48:42.053 -0500 halo-touch-7bc072 [603] DEBUG: RemoteNavigatorApplication_onObserveConnectionStatusChanged - Connection Status: FAILED
2024-03-20 06:48:42.056 -0500 halo-touch-7bc072 [603] DEBUG: RemoteNavigatorApplication_onObserveConnectionStatusChanged - Network error already pushed!

 

[DanITman]

I've officially given up on these remotes.  There doesn't seem to be any hope for them.  They only work well if you are always pulling them right from the charger but its a crap shoot outside of that.  I'm going back to the neeos as I find it way easier to pick it up and in one click everything turns on and I'm good to go.  With the halos it takes up to two actions to get to what you want and this is after you wait for the remote to wake up.  If they could fix the speed issues and offer a similar interface to the neeo I will switch back.

 

[ChrisHenderson]

On 3/17/2024 at 6:57 AM, PaulAV9 said:

@msgreenfThank you. @ChrisHenderson When it happens again I will note the date and time and I will get the logs from my dealer. That will save the Halo team from having to hunt through long logs and help them pinpoint things easier.

Has it happened again, by chance?

[penn65000]

On 3/20/2024 at 6:11 PM, DanITman said:

I've officially given up on these remotes.  There doesn't seem to be any hope for them.  They only work well if you are always pulling them right from the charger but its a crap shoot outside of that.  I'm going back to the neeos as I find it way easier to pick it up and in one click everything turns on and I'm good to go.  With the halos it takes up to two actions to get to what you want and this is after you wait for the remote to wake up.  If they could fix the speed issues and offer a similar interface to the neeo I will switch back.

 

Yup I’m testing one and will wait for v2. Too many disconnects and lags and found a couple of times same issue as neeo re base not charging unless remote placed and re-placed perfectly.