Tony,
I intentionally avoid those types of tstats, they
only work through cloud applications, for various
reasons I do not want that sort of thing being
under the control of someone's cloud system.
Now that I have found out how to deal with the
connection issue I no longer have problems
with it.
On Tue, 1 Feb 2022, King Beowulf wrote:
In Slackware 14.2, older audacity and pulse easily confuse each other.
Sometimes setting the playback hw:x,y confuses the heck out of
pulseaudio. Here I set:
Host = ALSA
Playback Device = pulse
Recording device = default: Front microphone:0
Thanks,
On 2/1/22 08:20, Rich Shepard wrote:
> On Tue, 1 Feb 2022, Rich Shepard wrote:
>
>> What have I missed?
> Still clueless on the source of the problem. However, aplay -L shows all
> available audio cards, sound-test produces its default sound, and mplayer
> produces output from the podcast .mp3 I
Update: I have a tentative taker for the Z820.
Neither of us are clear if that roped them into a talk!
BUT... they've put in their time. All good.
Michael
On 2/1/22 1:15 PM, Michael Dexter wrote:
Hey!
Perhaps against my better judgement, I bought one of these on sale:
Hey!
Perhaps against my better judgement, I bought one of these on sale:
https://www.newegg.com/p/288-00CG-00018?Item=9SIB14AFN61298
Product: ATOMSTACK A5 Pro Laser Engraver, 40W Laser Engraving Cutting
Machine for Metal and Wood, 5.5W Output Power, Compressed Spot CNC
Carving DIY Laser
I recently installed a Nest thermostat. The basic Nest thermostat would not
work based on the attached wires on our old thermostat unless I bought a extra
harness with a small box attached to it. The Nest Learning Thermostat would
work so got one for $50 off back in November. Given the cold
I recently installed a Nest thermostat. The basic Nest thermostat would not
work based on the attached wires on our old thermostat unless I bought a extra
harness with a small box attached to it. The Nest Learning Thermostat would
work so got one for $50 off back in November. Given the cold
On Tue, Feb 1, 2022, 2:08 PM Chuck Hast wrote:
> Tomas,
> Now that I know how to deal with it, I think it
> is worth it. I do not have to get up and go to
>
One good way to handle unknown devices like that is too create an interface
on your router for those devices and firewall it off from
Tomas,
Now that I know how to deal with it, I think it
is worth it. I do not have to get up and go to
the tstat to make a temperature change, I just
grab my phone or computer and do it, If I want
to reach it from the outside that is what VPN's
are for.
Most of the IoT devices (thermostats) are
Thanks for sharing this journey Chuck,
This is like inviting some real nasty individual home, who tries to get
more of his friends in all the time.
Put aside the network engineering challenge, I am rhetorically asking, is
this worth the hassle, risk, time to even consider these devices?
Diy
The actual fix was even easier, there is an advanced
page on the thermostat web page, you go there and
it has the address it is to aim its queries at, all I did was
change it to a local IP on my network and that cooked
it's goose. I now have had not time changes for almost
2 days, whereas before
On Tue, 1 Feb 2022, Rich Shepard wrote:
What have I missed?
Still clueless on the source of the problem. However, aplay -L shows all
available audio cards, sound-test produces its default sound, and mplayer
produces output from the podcast .mp3 I downloaded to the speakers and the
Yamaha
It's been a while since I last used audacity and I'm not able to fix why
it's not producing output to the Creative Pebble speakers, the Yamaha CM500
or MPOW HC headsets.
Music played with audacious has no problems so the issue is strictly
audacity and I've not found a solution in my web
13 matches
Mail list logo