m4rky_m4rk
Publish time 1-12-2019 21:39:03
Hi, Do you think you will be able to replace MyHomeSuite for programming one day? I hate MyHomeSuite so an alternative would be good.The UI is old and annoying and mine now pauses for 30s every 5mins or so.. maybe my config files are too big ?
sxpert
Publish time 1-12-2019 21:39:04
we'll soon be able to program H4652, F411/2 and F411/4 devices
I don't have anything else at the moment...
sxpert
Publish time 1-12-2019 21:39:05
ok, almost there. I can now request a device to be scanned... and that updates the configuration on the integrated web site (that's a lot of javascript, damn it !)
now that I can change configuration parameters, programming is almost there
m4rky_m4rk
Publish time 1-12-2019 21:39:05
More progress with BTicino BUS and Alexa....Learning some java for the Openhab rules file:
Alexa announcements are done at a preset volume. After the announcement Alexa returns to the previous volume
Code: rule "Windy mode On"whenItem Windy_Switch changed from OFF to ONthenval current_volume_echo = Echo_Volume.statesendCommand(Echo_Volume,40)sendCommand(Echo_Speak,"High winds have been detected. The blinds will retract until it is calm again")Thread::sleep(8000)sendCommand(Echo_Speak,"High winds have been detected. The blinds will retract until it is calm again")Thread::sleep(6000)sendCommand(Echo_Volume,current_volume_echo)end
Some announcements are blocked during the night to avoid disturbance eg It has started to rain.
Code: rule "Wet On"whenItem Wet_Switch changed from OFF to ONthenif ((now.getHourOfDay >= 09) && (now.getHourOfDay
m4r4js73
Publish time 1-12-2019 21:39:06
Hi,
To sxpert,
:~# docker exec-it python3 python3 /usr/local/lib/python3.6/site-packages/automator.py
2018-06-06 15:55:32 Initializing configuration
2018-06-06 15:55:32 TLS initialized
2018-06-06 15:55:32 configuration file opened successfully
{'address': '192.168.1.40', 'port': 20000, 'session_key': 'K4ewNuje0c4vP8jo46eBX9hq2XUm1AQsSXc-wmAccag='}
2018-06-06 15:55:32 TLS unavailable
sessions setup
jinja2 setup
routes setup
{'message': 'Task exception was never retrieved', 'exception': OSError(99, "error while attempting to bind on address ('192.168.1.40', 20000): cannot assign requested address"), 'future':exception=OSError(99, "error while attempting to bind on address ('192.168.1.40', 20000): cannot assign requested address")>}
I want your Myhome element to node red, but I'm not understood how this works.
sxpert
Publish time 1-12-2019 21:39:07
thanks for the report, there are things that got ripped up when I redid the web server module.
for now you need a small config.json file, which I added a sample for in the git repo.
when you start it, it should enumerate your devices for you and put them in the conf.
then head to the http://localhost:8080 website for more goodies
Note: there is a bug in address parsing for the heating system which I have to fix...
m4r4js73
Publish time 1-12-2019 21:39:09
I have still the same error. If i add to config.json gateway address 192.168.1.27, the error still say about 192.168.1.40.
(on adr 27 is HM202, on adr 40 is F455)
sxpert
Publish time 1-12-2019 21:39:10
from the error message, it looks like you got the web server and the gateway confused
Code: { "web": { "address": "127.0.0.1", # this is the address automator's web server should respond to "port": 8080 # and the port }, "systems": [ { "gateway": { "address": "", # here goes the gateway address "port": 20000, # and the port "passwd": "" } } ]}
m4r4js73
Publish time 1-12-2019 21:39:11
I have little progress. After what I reinstall Python.
But the web is not working, (because Docker ... ?)
TLS is necesery ?
docker exec-it py3 /usr/local/bin/python3 /usr/local/lib/python3.6/site-packages/myhomepy-master/automator.py
2018-06-07 17:58:17 Initializing configuration
2018-06-07 17:58:17 TLS initialized
2018-06-07 17:58:17 configuration file opened successfully
{'address': '127.0.0.1', 'port': 8080, 'session_key': 'W6ciC-VCwCYNwd1_JKaLUtzxAAM_F44hRNs7s8d61Y8='}
2018-06-07 17:58:17 TLS unavailable
sessions setup
jinja2 setup
routes setup
------ serving on 127.0.0.1:8080 ------
session key b'[\xa7"\x0b\xe5B\xc0&\r\xc1\xdd\x7f$\xa6\x8bR\xdc\xf1\x00\x03?\x17\x8e!D\xdb;\xb3\xc7z\xd5\x8f'
site url :http://127.0.0.1:8080
sxpert
Publish time 1-12-2019 21:39:12
TLS is not implemented yet with the new web server (haven't had time to get to that), just ignore it for the moment.
when this will be done (probably a couple lines but I haven't looked into it) you give it a key and a cert, and it should chug along.
this statement is just a warning that things would be going unencrypted
at this point, you should be able to head to whatever IP docker is showing out, and use u / xxx for login (haven't done a user database yet either)
did it start querying your network for devices ?
Pages:
3
4
5
6
7
8
9
10
11
12
[13]
14
15