Hello,
Just to start, i have this Gateway from fithplay the Home Area Manager.
When i'm looking on it i find different things and found a guide on domoticz. But can't really find myself in it cause some guidelines arent the same as mine... and i can not connect my gateway true usb.. needs to be true lan or WIFI and when i want to get in the gateway i need to enter http://mac-adress.local.
Hope you guys could guide me in the right direction.
Add Fithplay Gateway to Domoticz
Moderator: leecollings
-
- Posts: 3
- Joined: Tuesday 19 July 2016 20:06
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 3.8975 +
- Location: Gelderland, NL
- Contact:
Re: Add Fithplay Gateway to Domoticz
Hi wou5er and all others,
I have sort of the same problem (Using the Itho Daalderop spIDer system)
just to add more information:
the FithPlay Home Area Manager (just calling it FHAM for now) is nothing more then a Gateway running a Linux OS (and is having a lot of security holes ),
it makes a SSH tunnel from itself to the FithPlay server, the "Smart" part is done on there servers.
to the FHAM you can connect a Honeywell Evohome HGI-80, a EnOcean tcm310 USB or a P1 smartmeter and possibly in the future more
To continue an the Honeywell HGI-80 part (what i think you are aiming at),
I got a second HGI-80 to look what is happening in the communication between the FHAM and the room thermostat
when checking the log's i see the following:
using the standard way's i'm not yet able to include the second HGI-80 to the FHAM/temostat network.
anyone more ideas?
I have sort of the same problem (Using the Itho Daalderop spIDer system)
just to add more information:
the FithPlay Home Area Manager (just calling it FHAM for now) is nothing more then a Gateway running a Linux OS (and is having a lot of security holes ),
it makes a SSH tunnel from itself to the FithPlay server, the "Smart" part is done on there servers.
to the FHAM you can connect a Honeywell Evohome HGI-80, a EnOcean tcm310 USB or a P1 smartmeter and possibly in the future more
To continue an the Honeywell HGI-80 part (what i think you are aiming at),
I got a second HGI-80 to look what is happening in the communication between the FHAM and the room thermostat
when checking the log's i see the following:
Code: Select all
2018-03-04 15:54:02.697 Error: evohome: ACTUATOR_STATE: Error decoding command, unknown packet size: 6
2018-03-04 15:54:02.697 Error: evohome: unable to decode payload for command 3ef0
2018-03-04 16:03:38.304 Error: evohome: ACTUATOR_STATE: Error decoding command, unknown packet size: 6
2018-03-04 16:03:38.305 Error: evohome: unable to decode payload for command 3ef0
2018-03-04 16:13:13.913 Error: evohome: ACTUATOR_STATE: Error decoding command, unknown packet size: 6
2018-03-04 16:13:13.913 Error: evohome: unable to decode payload for command 3ef0
[...]
2018-03-04 18:34:44.086 Error: evohome: ACTUATOR_STATE: Error decoding command, unknown packet size: 6
2018-03-04 18:34:44.086 Error: evohome: unable to decode payload for command 3ef0
2018-03-04 18:44:19.684 Error: evohome: ACTUATOR_STATE: Error decoding command, unknown packet size: 6
2018-03-04 18:44:19.685 Error: evohome: unable to decode payload for command 3ef0
2018-03-04 18:50:14.220 evohome: WARNING unrecognised message structure - possible corrupt message '000000' (2)
2018-03-04 18:53:55.299 Error: evohome: ACTUATOR_STATE: Error decoding command, unknown packet size: 6
2018-03-04 18:53:55.300 Error: evohome: unable to decode payload for command 3ef0
2018-03-04 19:02:20.176 evohome: WARNING unrecognised message structure - possible corrupt message '00' (3)
2018-03-04 19:03:30.903 Error: evohome: ACTUATOR_STATE: Error decoding command, unknown packet size: 6
2018-03-04 19:03:30.903 Error: evohome: unable to decode payload for command 3ef0
2018-03-04 19:13:06.502 Error: evohome: ACTUATOR_STATE: Error decoding command, unknown packet size: 6
2018-03-04 19:13:06.502 Error: evohome: unable to decode payload for command 3ef0
[...]
2018-03-04 22:28:00.887 Error: evohome: ACTUATOR_STATE: Error decoding command, unknown packet size: 6
2018-03-04 22:28:00.887 Error: evohome: unable to decode payload for command 3ef0
2018-03-04 22:32:39.110 Error: evohome: ACTUATOR_STATE: Error decoding command, unknown packet size: 6
2018-03-04 22:32:39.110 Error: evohome: unable to decode payload for command 3ef0
2018-03-04 22:32:47.498 evohome: WARNING unrecognised message structure - possible corrupt message '00010000' (3)
2018-03-04 22:37:43.460 evohome: WARNING unrecognised message structure - possible corrupt message '000000' (3)
2018-03-04 22:42:14.702 Error: evohome: ACTUATOR_STATE: Error decoding command, unknown packet size: 6
2018-03-04 22:42:14.702 Error: evohome: unable to decode payload for command 3ef0
2018-03-04 22:51:50.317 Error: evohome: ACTUATOR_STATE: Error decoding command, unknown packet size: 6
2018-03-04 22:51:50.317 Error: evohome: unable to decode payload for command 3ef0
anyone more ideas?
Who is online
Users browsing this forum: No registered users and 1 guest