@PtP I presently use 4 hubs in my config with hundreds of sensors, binary sensors and switches. Without multiple hubs development I would have moved on to some other product. Pardon my ignorance but what is the ‘async’ thing?
I don’t think the HA will decay at the loss of being unable to only configure an integration from the UI
Since allowing HA to be configured from the UI, i think most people would agree HA has gone forward and not backwards.
@aidbish We’ll just agree to disagree shall we?
EDIT:
Answer me this…am I able to add comments like this in the UI sensor config?
##########################################
# END MQTT Ultrasonic Sensor
##########################################
##########################################
# Start Fronius Inverter Sensor Custom Component
##########################################
2 Likes
Saw this in my logs and the front end failed to load, then after a minute started working again
2020-04-10 10:34:34 ERROR (MainThread) [homeassistant.core] Error doing job: SSL handshake failed
Traceback (most recent call last):
File "/usr/lib/python3.7/asyncio/sslproto.py", line 625, in _on_handshake_complete
raise handshake_exc
File "/usr/lib/python3.7/asyncio/sslproto.py", line 189, in feed_ssldata
self._sslobj.do_handshake()
File "/usr/lib/python3.7/ssl.py", line 763, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1056)
2020-04-10 10:34:34 ERROR (MainThread) [homeassistant.core] Error doing job: SSL error in data received
Traceback (most recent call last):
File "/usr/lib/python3.7/asyncio/sslproto.py", line 526, in data_received
ssldata, appdata = self._sslpipe.feed_ssldata(data)
File "/usr/lib/python3.7/asyncio/sslproto.py", line 189, in feed_ssldata
self._sslobj.do_handshake()
File "/usr/lib/python3.7/ssl.py", line 763, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1056)
Just a short reply, we are 2 active developers (today) and I am the only one working on the base part of the integration. Of course there are a group of developers who are very helpful in reviewing the suggested patches (thanks a lot to all that help).
I decided a while ago to upgrade the modbus integration to make it work with my Huawei sun2000 inverter, One of the “old” developers suggested a change to async, and being a technical programmer I found it to be an interesting challenge.
We tested/reviewed and then retested for quite a while, however our configurations are no match compared to all the beta testers, so it is natural that there are problems.
I work hard, with a lot of help in testing etc from many beta testers (thanks for that), but please cut me a bit of slack to solve the problems.
Please keep testing that is the sole purpose of beta versions. Please look at the 2 open issues, where others and I try to keep everybody informed.
Thanks in advance
3 Likes
@wellsy Nice! Sounds like a fun setup!
A long time ago, I forget how long maybe 0.20’s HA used to be primarily synchronous. One thing happening at time. The backend started using async.io allowing for things to happen while other things were waiting for something to happen. Now on an integration level almost all components operate asynchronously. The Modbus component is now being moved to this.
1 Like
I thank you for your work @janiversen It appears that my config has larger issues with my modbus config or even somewhere else to the point that HA is unusable after installing 108.1 so I can’t help with beta testing unfortunately.
That’ll be where all the huge memory leaks…high CPU usage, have been coming into play since 0.100 or so right? First time I have even heard it mentioned, cheers for that!
@janiversen My post was to express gratefulness for what you and others are doing and to share with Modbus users your hard work. I will try to contribute more to resolving the issues on github. Thanks again! I am excited for this integrations transition.
1 Like
That is how I read it, thanks for the kind words.
Right now I have enough information about the serial problem and rtuovertcp. But if there are other issues (like the big configuration mentioned in an earlier post), please create an issue with log and configuration
We need to get all problems solved, but to do that they need to be known == create issue.
It is better to create an issue when in doubt, just my opinion 
2 Likes
I have been following your back and forth with aidbish and this issue you are now having is precisely why yaml and comments are needed. I was using ui when ever I could when I was first getting use to HA. When I ran into problems I had no idea why I did something a certain way and troubleshooting was impossible! Now I use yaml about 95% of the time and load everything from either !include or package. This way at any error I can comment it out and troubleshoot it easily.
4 Likes
@bschatzow My config is an absolute mess of comments and mechanisms to allow me to search more easily like why I have setup this or that and how they work, etc…Without that ability I would be in a very bad place. It is that way because my processes that HA controls are still in a prototype state across many of the individual functions. It simply MUST remain possible to do that in my case. Hence my present concerns.
2 Likes
I would like that also, but due to the way HAC is coded, this may be easier said than done!
1 Like
Thanks, that would explain why all my Alexa devices are not working right now, I was about to check the changes between 0.108.1 and 0.108.2 and jump to the wrong conclusion!
There is a work around for the Broadlink problem.
See:
It worked for me
2 Likes
I don’t use the Broadlink integration but it seems to me that if someone wants to rollback its underlying module, from version 0.13 to 0.12, then wouldn’t it simply be a matter of modifying the integration’s manifest.json file (and restarting Home Assistant)?
Worst case, the most recent Broadlink integration employs some code that relies on features found in the 0.13 module that are absent in 0.12 (and so what I suggested will fail). In that case, use the suggested solution in the link (i.e. revert to the the older version of the entire Broadlink integration by using it as a custom_component).
Anyone noticed that since 108, input booleans don’t remember the state anymore after a restart?
Is anyone experiencing delays with the HA app for both ios and android? I.e. especially opening the app and waiting for it to load ? Never had this issue with 0.107.X?
1 Like
And @Zamunda4Eva,
Why not store the commands in secrets and just call them with !secret bloncomd and !secret bloffcmd or whatever floats your boat ?
Or put them in an input_text and use that ?
Edit: I suppose that’s just moving text about, so no help really (sorry)