![]() ![]() > write-host $Manufacturer~$Product~$SerialNumber~$UUID > $UUID = (Get-WmiObject -Class Win32_ComputerSystemProduct).UUID ![]() > $SerialNumber = Get-WmiObject win32_baseboard | select-object -expand SerialNumber > $Product = Get-WmiObject win32_baseboard | select-object -expand Product This is the Windows PowerShell code I use to get it: > $Manufacturer = Get-WmiObject win32_baseboard | select-object -expand Manufacturer If you have a Lennox furnace with a variable speed blower and would like to keep the functionality, you don't have much of a choice.Īs painful as it is, you may want to replace the thermostat before it leaves you high and dry in the dead of summer or winter.I have several machines I have networked together and I use information about the motherboard to uniquely identify them. The price was painful (1000$), but that's consistent with the retail price range for this thermostat and certainly not my service provider's fault. Long story short, I had to put in an urgent call, and thanks to my reliable heating service provider who reacted very quickly, I got the thermostat replaced with an S30 the same day. The third time around, just as was about to declare another victory, I woke up the next morning to a blank white screen (it appeared that thermostat was still acting according to how it was programmed, but it was impossible to see what was going on on the screen or make any changes). I managed to fix the time problem twice by powering off the system and turning it back on after a few minutes. Firmware had not been updated in a while (unit was disconnected from wifi although it was an icomfort wifi). Time would arbitrarily jump from AM to PM or be offset consistently by several hours (interestingly the minute indicator would remain correct). Had exactly the same problem, popping up 5 years + 2 months after installation (it really feels that the unit was programmed to self-destruct after 5 years). This is a design flaw because (a) the thermostat should stick with a manually set time, rather than reset it based on a gateway, (b) the thermostat should use a better timeserver in any case, and allow its timezone to be set, (c) the server shouldn't refuse to connect simply because the thermostat time is wrong, and (d) the server should then either set the time correctly, or send a notification to the user to do so. The fuller test will come the next time my Internet connectivity is interrupted, or I reboot the Decos, since then we'll see if the correct timezone sticks. I've now executed the fix on the main Deco time setting (which it to change it, via the web client, to another region, and save that, and then back to the correct one, and save that), and since doing that the thermostat hasn't changed its time or lost connectivity to the server. ![]() The clue that this is the problem is that if I manually reset the thermostat's time to the correct time for my timezone, it immediately regains connectivity to the server. ![]() Second question is, why does this cause the thermostat to lose connectivity to the server? My guess is that the server does a time check, and if the thermostat's time is too far off what the server expects the server refuses to communicate. The clue that it's a timezone problem is that it's always the hour (and sometimes date) that's wrong, never the minutes. Turns out Decos have a problem which is that the initial timezone setting doesn't stick, so my main Deco apparently kept feeding the thermostat the GMT time rather than the Pacific timezone time, and the thermostat would overwrite the (correct) time I'd entered manually. I think there are two problems interacting, both of which strike me as design problems.įirst question is, where is the thermostat getting its time setting? It doesn't appear to be contacting a regular time server, and so I suspect that it's getting the time from the local gateway (in my case, the main TP-Link Deco in my home wifi mesh). So I had this problem too, namely that the thermostat kept resetting itself to GMT (that is, Zulu time), and then would become unable to communicate with the Lennox server, and therefore not be controllable via the iComfort app. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |