[dtomcat]

I noticed mine the same way the other day and forgot to check again. but sure enough my thermostat (on HAL iPhone app and HomeNet UI) reads 62 always... my home is 71 most of the time. looking right now... both read 62 and the Nest reads 71. Not sure if it's a software thing or not... only noticed it after recent update (not sure if it was present prior to). HALpro 6.1.37... just seen and update available. downloading update now and will post if it still reads 62.

[dtomcat]

Well I guess we'll never know... .39 doesn't allow me install it. it gets to backup portion of install then tells me it can't open oleaut32.dll and closes. no way to bypass it. I even rebooted the machine and closed all non system programs and services and still same results. guess i'm stuck on .37

[TimShriver]

try running the install with the Custom option and select HAL program files. It sounds like you have a conflicting control installed on your system.

Also there haven't been any changes to the Nest related code since the 6.1.21 build back in June. You can always check yourself by looking at the errata.

If you send me an email with your nest information, I can try it here and see what results I get looking at your nest stats...

Tim

[dtomcat]

Originally Posted by TimShriver

try running the install with the Custom option and select HAL program files. It sounds like you have a conflicting control installed on your system.

Also there haven't been any changes to the Nest related code since the 6.1.21 build back in June. You can always check yourself by looking at the errata.

If you send me an email with your nest information, I can try it here and see what results I get looking at your nest stats...

Tim

Tim,
Now that you say something... I may have changed my password! I'll feel dumb if that's the case... I'll follow up and let you know


as for the other issue I tried what you said and same results.


-Rob

[dtomcat]

Tim,
Finally got the install to work (had to do compatibility mode to windows xp sp3). Install went fine... after the install before doing anything with nest... nest temp was correct. I'll continue to monitor the temp to see if it is indeed updating again.


If it does, unfortunately I cannot rule out rebooting as the fix, or if the HAL update fixed it. (bad Troubleshooting... sorry). But for now all seems good.


-Rob

[dtomcat]

Update 2:
Nest still seems to be update on HAL... downfall I found is that HA-Bridge does not work nice with HAL anymore. worked perfect (zero flaws) on 6.1.37... on 6.1.39 I'm lucky if it works once with each reboot. when "testing" it inside the HA-Bridge... it works great. Alexa can find the devices find... but when I tell her to turn on/off something... she thinks about it for a bit... then says "OK"... but nothing ever happens. Shouldn't have messed with something running perfectly!!!! oh well... Can I get a link to .37 so I can hopefully go back to what I had? Thanks


-Rob

[dtomcat]

Update 3

Moved HA-Bridge to my Raspberry Pi. It will be its only Job! Works perfect again. Nest still updating correctly!

[TimShriver]

Originally Posted by dtomcat

Update 2:
Nest still seems to be update on HAL... downfall I found is that HA-Bridge does not work nice with HAL anymore. worked perfect (zero flaws) on 6.1.37... on 6.1.39 I'm lucky if it works once with each reboot. when "testing" it inside the HA-Bridge... it works great. Alexa can find the devices find... but when I tell her to turn on/off something... she thinks about it for a bit... then says "OK"... but nothing ever happens. Shouldn't have messed with something running perfectly!!!! oh well... Can I get a link to .37 so I can hopefully go back to what I had? Thanks
-Rob

Hi Rob,

Nothing changed in the HALws which is what the HA-Bridge uses. There are a number of users on 6.1.39 using the bridge with no issues... so I'm not sure what the problem might be. If you open the HA-Bridge UI, you can manually execute the commands with the test button. if they fire then the Bridge to HAL works and it is something from Alexa to the Bridge...

Tim

[DadGoneMad]

I had the same problem when I upgraded to v.39. I first thought it was some sort of permissions issue but could never resolve it. Instead what I did was log on with a (Win10) local account (instead of my admin account), then ran the installation (run with admin rights) and did not receive any oleaut32.dll error during installation. I do however seem to have some sort of issue that's surfaced where my HALUltra crashes repeatedly for about 10-12 times after starting. Then, after going through several WatchDog automatic restarts the crashing stops and it runs just fine. I have been trying to troubleshoot what the problem might be, the only error I see in WatchDog is "Alive Registry not set" or something along those lines. I will give tech support a call if I can ever work from home and able to be there for someone to help me determine root cause here. For Christmas I got an Amazon Echo and Dot, I configured the HA Bridge with very little issues at all. Seems to run great, am still learning how to create commands, but overall I like it a lot!