Ultra trigger to Topping D70 Pro | Wake up at night

The WiiM device turns on my DAC, preamp, power amp, and subwoofer every three days, which is very annoying. I solved this problem by using Home Assistant to create an automation. The automation checks the player status using the WiiM API and sends an IR command to my DAC to turn it off if the player is in “none” status and the other parts of my stereo system are on. The trigger system then turns off all the other parts.
I really don‘t know what this is all about.
The WiiM performs an automatic reboot every three days according to your records. Ok, might be.
On rebooting it will trigger connected devices. That‘s what it‘s supposed to do. Then it will fall into standy after the predifined time and again will also trigger the shut-off of the other devices. All of this is according to the rules.
What‘s the problem?
 
I really don‘t know what this is all about.
The WiiM performs an automatic reboot every three days according to your records. Ok, might be.
On rebooting it will trigger connected devices. That‘s what it‘s supposed to do. Then it will fall into standy after the predifined time and again will also trigger the shut-off of the other devices. All of this is according to the rules.
What‘s the problem?
This isn’t really a reboot; it’s something else.

And even if, according to you, this is a reboot and the device powers up and turns on the entire system, I have a 15-minute automatic shutoff configured, yet in this situation the entire system remains permanently on.

I complained because I returned from a vacation of more than a week and found that all the equipment in my home was left on.

So again, even if this is considered a reboot and I have a defined 15-minute shutdown time, it doesn’t cover or resolve anything.
 
This isn’t really a reboot; it’s something else.

And even if, according to you, this is a reboot and the device powers up and turns on the entire system, I have a 15-minute automatic shutoff configured, yet in this situation the entire system remains permanently on.

I complained because I returned from a vacation of more than a week and found that all the equipment in my home was left on.

So again, even if this is considered a reboot and I have a defined 15-minute shutdown time, it doesn’t cover or resolve anything.
I see. This is indeed not as it should be.
My system does not show this sort of behaviour.
 
I really don‘t know what this is all about.
The WiiM performs an automatic reboot every three days according to your records. Ok, might be.
On rebooting it will trigger connected devices. That‘s what it‘s supposed to do. Then it will fall into standy after the predifined time and again will also trigger the shut-off of the other devices. All of this is according to the rules.
What‘s the problem?
The issue seems to be that form some unknown reasons, the reboot done every three days at night automatically is different from a reboot you may ask the Ultra to perform via the WiiM Home App.

Via the app, all works as you expects.
When occurs 'by design's automatically, it leaves the connected devices on. Now reported by at least three different people.

Before the current DAC I had the Vibelink Amp and it did not had such behaviour, therefore I'll try to connect the DAC using same optical connection to see if this makes a difference vs the USB I use now. Just In case it does, trying to help support and other users with same issue identifying the root cause.
 
What I'm speculating is that during the night reboot/refresh instance the Ultra does not send any transition 12v - 0v via the trigger because it never sends the initial 12v. This because it does not start playing at any time not competing a full reboot including the input/output enablement. Missing this step, external devices that defaults to 'on' missing the 12v completely and requiring a transition 12v - 0v to go 'off' would remain active.

Devices just turning on when feeling the 12v and off when not feeling nothing would just remain quiet and off.

This is in line with the fact that sending trigger off via the app multiple times is not able to turn off connected devices manually switched on. It does only after you use it to turn the on.

If so, solution would be to ensure that any time trigger should switch off devices, should first check if already sending 12v and if not, first do so and the go back to 0v.

Just speculation.
 
What I'm speculating is that during the night reboot/refresh instance the Ultra does not send any transition 12v - 0v via the trigger because it never sends the initial 12v. This because it does not start playing at any time not competing a full reboot including the input/output enablement. Missing this step, external devices that defaults to 'on' missing the 12v completely and requiring a transition 12v - 0v to go 'off' would remain active.

Devices just turning on when feeling the 12v and off when not feeling nothing would just remain quiet and off.

This is in line with the fact that sending trigger off via the app multiple times is not able to turn off connected devices manually switched on. It does only after you use it to turn the on.

If so, solution would be to ensure that any time trigger should switch off devices, should first check if already sending 12v and if not, first do so and the go back to 0v.

Just speculation.
This is a compromise proposal until the team resolves the issue, but how about setting an alarm early in the morning to force the DAC and amplifier to turn off?

Set a silent alarm or a one-minute alarm with the volume at 0%, then have WiiM execute the off trigger. The method for setting a silent alarm is explained here.
 
This is a compromise proposal until the team resolves the issue, but how about setting an alarm early in the morning to force the DAC and amplifier to turn off?

Set a silent alarm or a one-minute alarm with the volume at 0%, then have WiiM execute the off trigger. The method for setting a silent alarm is explained here.
C l e v e r - will definitely give it a try.
 
I has my Ultra with an external DAC (Topping D70 Pro) via USB; it features a trigger in and out jacks. I connect them both so to wake up my Power Amp as well as I turn on the Ultra. I use a mono trigger cable to DAC and another one to Power Amp.
The setup works quite well and I tested turning on the Ultra (it wakes up all other devices) as well as waiting for the idle state (it turns off all other devices), plus used the new trigger control from WiiM Home app and all works as intended.

I noticed that some days - now everyday, once in few days but I didn't took exact note; let say once in a week or so - I wake up and the DAC and Amplifiers are turned on, with the Ultra still in standby. Is it possible that the nightly wakeup for firmware updates is an incomplete handling of the trigger that results in this outcome? It's the only idea that came to my mind.

Cheers.
I also have the topping D70 Pro connected to WiiM ultra via USB and this same thing is happening to me. However in my case after the automatic reboot only the DAC stays on. The difference in my situation is that I’m using a y-splitter on the ultra’s trigger instead of using the D70’s in and out trigger jacks. This set up functions flawlessly when using the app and when I reboot the ultra on my own, however every few days I find the DAC still on but the ultra and vibelink are both off. Thank you for starting this thread. It would be good if this issue could be resolved. I can submit a ticket if it would be useful.
 
in my case after the automatic reboot only the DAC stays on. The difference in my situation is that I’m using a y-splitter on the ultra’s trigger instead of using the D70’s in and out trigger jacks.
I was thinking on same approach but as it would maybe fix only partially the problem I'm keeping current pass through approach.
In all scenarios but the automatic activity at night every few days, it works flawlessy as well.
I'm pending a test during Optical out, will report here once I start testing.
 
I just submitted a ticket. I will report back with any feedback I receive.
Support team reached out via mail to me asking if the behaviour is aligned to the 3 days silent reboot cycle, which I confirmed.

I anticipated others are submitting tickets for the same issue, hopefully this can help highlighting impact and prioritizing it in their schedule.
 
Back
Top