If it helps anyone this is the routing that’s typically setup in a PDEG. Please ignore the 8008 routes as that’s for Control4. The idea is that port 50000 is used for remote access and any other TCP ports are for third party interfaces.
So shall I change the port in the device I have to 50000?
Not necessarily, it’s just the default in the PDEG. You just need to ensure whatever port you’re using is consistent with the interface that connect to it, if that makes sense.
I’ve got my 485 converter connected should I be able to start seeing data if I telnet to the port of the 485 converter?
Currently Im not seeing any new entries being created when I button on and off devices with auto configure turned on.
dynalite:
bridges:
- host: 192.168.1.210
port: 12345
autodiscover: true
polltimer: 1
So when I press a switch on Dynalite system I can see RX flash on the 485 > IP modules so I can see its getting some kind of data.
is there any new entities in Home Assistant?
Did you keep your IPto rs485 devise as DHCP or static IP?
remove the modbus tick
Just noticed your IP address is wrong, Keep it the same as your IP to RS485 device 192.168.0.201
Got it working the MODBUS TCP option off fixed the issue… they are appearing in HASS now… to the programming… I’m a bit confused as when I press keys they come in as presets not as channels?
can you share a screen shot? It should show as described in the documentation of Dynalite in Hassio (This is where the autodiscover option comes handy. If it is on, the component will track the Dynet network and every time a device is used, it will be added to Home Assistant. It will initially show as “Area 123 Channel 7”, but you can then add it to your configuration.yaml with the correct configuration.)
Yes this is possibly true if the devices are mapped as channels but mine seem to be programmed as presets?
That what I have under Devices, it is defined and I can add it to lovelace under unused
I’m not sure what you have wrong there
So any of the ones that it auto discovers are Area x Preset x any of the ones I’ve got names on are in the config file.
Be good to know if I can dim channels and control additional presets.
So for example I have a panel that has 3 keys
1 - On
4 - Off
8 - 50% Dim Preset.
Be great to some how have these as buttons or within HASS.
Area x Preset x it is defined in your dynalite system by the integrator, if you mean configuration.yaml file yes you need to configure it to accompany all your devices and presets / channel
I don’t know if you can change presets without the system builder software. Dim is possible as long as it was done by the physical buttons.
So got an intresting one - got buttons that are not showing up in autodiscover… how can i find these buttons? is it because they are presets? one things i’ve noticed is that once you add an area you don’t get to see the auto discover presets anymore either… so say i found a light in the kitchen and i can turn that light on and off but another light in the same area i think is being controlled by a preset not a channel so i am not finding this device in auto discover ?? i can see data when the key is pressed in telent to the 485 port and obviously the light turns on and off.
Did a hex dump of what i am capturing
Line 2 & Line 3 are a button that turns a light on and off that won’t discover in auto discover
but Line 4 will auto discover…
Is it possible to assign the raw hex to a command in hass to the dynet ?
So the
Here’s what the hex bytes mean from your message, and keep in mind that presets begin from ‘00’ as Preset 1(typically On) ‘03’ Preset 4(typically Off), and so on:
It is doing a Fade Channel/Area to Preset
Byte 0: 1C (this says it’s a logical message)
Byte 1: Area (area 9)
Byte 2: Channel (00 is channel 1)
Byte 3: 6B (this is the opcode for Fade Channel/Area to Preset)
Byte 4: Preset (this is odd being ‘01’, the programmer must have changed it)
Byte 5: Fade Time (64 equates to 2 seconds)
Byte 6: Join (do not change this)
Byte 7: Checksum (ignore this too)
When it’s a Preset to the whole Area and not controlling an individual Channel the bytes are different:
Byte 0 - 1C
Byte 1 - Area
Byte 2 - Fade Rate low byte (usually 100)
Byte 3 - Preset - 0 = P1, 1 = P2, 2 = P3, 3 = P4, A = P5, B = P6, C = P7, D = P8
Byte 4 - Fade Rate high byte (usually 0)
Byte 5 - Preset Bank - 0 = P1 – P8, 1 = P9 – P16, 2 = P17 – P24 etc.
Byte 6 - Join
Byte 7 - Checksum
I hope this helps.
Regards,
Thierry
@krezlic - you should be able to work out what the hex bytes represent and populate your configuration.yaml accordingly as @BinGraiban mentioned above…if I’m understanding your question correctly?
@tjd yep got it working by using the hex
If i wanted to add a dim in to this on off also? how is that done?
'18':
name: Bedroom
template: room
channel:
'2':
name: Nick Reading