azeroth12
azeroth12
Reverting to 4.0.8 put me back in business.
Gotcha so we're in dependency hell here... Guessing bumping JS Socket.IO would be too easy an answer...
As an fyi I was lazy and just pulled the :dev branch into docker and all is well again. So the fixes do work just haven’t been released. Nothing mission...
I can't even log into their swagger online so it seems like maybe something is broken on Mieles end... After inputting client_id and client_secret I get redirected to a basic...
I tried to upgrade with these steps and can't get the new version to pass the test on the lambda side. My old zip file works fine, any ideas? Log:...
Did a straight copy of the sample and just updated my info. ``` { "url": "https://[url]:8123/api", "password": "[pass]", "ssl_verify": false, "expose_by_default": false, "exposed_domains": [ "alert", "automation", "climate", "cover", "fan", "group",...
1. Yes, just double checked. Original was the zip from the master branch. Re-downloaded 0.3.1 just to make sure. 2. Yes only the one trigger. Only weird thing I've seen...
Not much different with debug... ``` START RequestId: 64ca298f-5b93-11e7-92e5-993ce9fb27f1 Version: $LATEST [DEBUG] 2017-06-27T23:50:26.945Z 64ca298f-5b93-11e7-92e5-993ce9fb27f1 calling event handler for DiscoverAppliancesRequest, payload: {} type object 'allowed' has no attribute 'Control': AttributeError Traceback...
I've reverted back to the old version for now... haven't given this guy another go yet. Not really sure what the issue is...
Nice to know I'm not alone with the problem.